Related
I ahve been running mightyrom on my tp2 with Cricket. I let it get wet, (a wet towel got thrown on it), and now I have a tri color with errors when turning it back on. I was actually relieved to see something, cause it took a day of it sitting on an AC to get it to do ANYTHING.
Now, the error reads Microp(led) wrong plat (0x0). I figure I lost everything, but now am just trying to salvage the phone.
So the question is, where do I start from here?
I would be happy just to get it working again, but its not a normal starting point and I don't want to do more harm not knowing where to start
Now I have another question as well, just because I'm greedy I'm probably being foolish, but nonetheless, I'll ask it. Would there be any benefit to moving towards android? I know I have been able to save desktops, and hard drives using linux, would this make it easier, harder, etc....?
I did look through the forums, but this seems to be a kind of unique starting point, and the android is new to me as well.
Thanks in advance for any help, and thanks for all the help in the past.
Nick
nickyjpd said:
I ahve been running mightyrom on my tp2 with Cricket. I let it get wet, (a wet towel got thrown on it), and now I have a tri color with errors when turning it back on. I was actually relieved to see something, cause it took a day of it sitting on an AC to get it to do ANYTHING.
Now, the error reads Microp(led) wrong plat (0x0). I figure I lost everything, but now am just trying to salvage the phone.
So the question is, where do I start from here?
I would be happy just to get it working again, but its not a normal starting point and I don't want to do more harm not knowing where to start
Now I have another question as well, just because I'm greedy I'm probably being foolish, but nonetheless, I'll ask it. Would there be any benefit to moving towards android? I know I have been able to save desktops, and hard drives using linux, would this make it easier, harder, etc....?
I did look through the forums, but this seems to be a kind of unique starting point, and the android is new to me as well.
Thanks in advance for any help, and thanks for all the help in the past.
Nick
Click to expand...
Click to collapse
First off this is in the COMPLETELY wrong forum. This is the Android port forum, not the Windows Mobile ROM forum. Please for future reference double check you are posting in the correct forum.
If you are still getting boot loader (tri color screen) then not all hope is lost. You need to get the stock TP2 rom for whatever company's TP2 you have (tmobile, att, etc) not a cooked rom the STOCK rom, from the TP2 Wiki. if you can get your phone to at least connect to USB (when on the tri color screen it will say "usb" on the very bottom if its got a working connection) then you may be able to run the stock rom to save it.
It could still be broken tho, water damage is a funny thing sometimes.
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Next time you should really be careful when installing ROMs................. Make sure they are supported by your phone............... That's all the advice I can give.
Your only options now is to try a USB jig or sending it to a support center so...
Yup, you need to make sure the ROM you want is supported.. other than our dev section, everything else you will find is for the i9100.
Completely different phone.
I think your only options are jig or warranty
Sent from my SGH-T989 using XDA App
Yeah - this happens when you flash a ROM for a totally different device.
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
You can also try using ODIN to flash a stock tar and ROM back - it's not really bricked - but you'll need to do some reading to hopefully avoid such disastrous results again
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
Click to expand...
Click to collapse
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Sent from my SGH-T989 using XDA App
TJBunch1228 said:
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Click to expand...
Click to collapse
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
How many times in these forums does it say don't flash if you don't know what you are doing. If you don't know what you are doing ask questions. Maybe bricking your phone will teach you a lesson.
are you able to go into Download mode with a USB Jig?
(you can always make your own if you can add up enough spare resistor to amount 301k)
if you can then you can try flashing the stock Odin ROMs
erangalp said:
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Click to expand...
Click to collapse
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
Hmm - well let's see... a simple Google search to compare the phones would tell you that it's definitely not the same device. A little more reading might be in order though...
1. different screen sizes
2. different SoC (system-on-chip, i.e. processor)
3. different basebands/radios
4. etc.
All of those combine to a different device.
Now as relating to ODIN - I honestly don't see why you couldn't get into ODIN. A jig might help but I doubt it.
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
With very little research....
Galaxy S2 (International) - i9100
Dual-core 1.2GHz ARM Cortex-A9 processor, Mali-400MP GPU, Exynos chipset
T-Mobile/Telus Galaxy S2 - T989/D
1.5 GHz Scorpion dual-core processor, Adreno 220 GPU, Qualcomm APQ8060 Snapdragon chipset
This difference in specification should be the FIRST thing keeping you away from flashing a i9100 ROM on a T989...
erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Well - how about this answer given above which does in fact provide the answer for you:
jerdog said:
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
Click to expand...
Click to collapse
How can you know what you don't know? I have previously rooted my galaxy S2 and installed various ROMs without a problem. I now have this new T-mobile device since I switched carriers. I could I know that what worked for my previous Galaxy S2 won't work for this one? why should I "be taught a lesson"?
I would really appreciate if someone could give me a helpful answer - I can't use ODIN to flash since I can't boot up the device in any mode. Is there any way to make ODIN recognize a bricked device? the computer does make the USB connected sound for a sec there. Please guys, anything helpful instead of telling me how "should've known", because really, if I could I would. Nobody here ever had a faulty ROM installation?
erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Jerdog covered the differences in hardware for you. In fact it was exactly above your post explaining that you were unaware of the differences in hardware. 95% of us here are not devs... All you gotta do is read. There are dozens of threads already from folks who have already made your mistake. Read read read. And if you think you've read enough, read more. The difference in processor is one of the most commonly known and discussed things about this phone. Good luck with your phone.
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Sent from my SGH-T989 using XDA App
This thread happens 30 times a day, very annoying. People will never learn
Sent from my SGH-T989 using xda premium
TJBunch1228 said:
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Click to expand...
Click to collapse
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
If you just assumes it was the same, that basically means you are.clueless and don't even know anything about the phone, in other words, you should not be flashing if you don't know what you are doing
Sent from my SGH-T989 using xda premium
Yup, it's unfortunate - people try to flash VR onto their device, then find it's not compatible...
If there's something I can do to the zip to prevent it flashing on these devices, I will gladly do it, but since they bear the SGS2 name, the standard check for "galaxys2" likely won't help us...
If you try the jig, it SHOULD in theory work, if the hardware is fine. But I have no experience of this, it's a case of stabbing blind in the dark
erangalp said:
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
Click to expand...
Click to collapse
Hey - we all make mistakes - and you own up to it - that's a good thing.
I wouldn't personally recommend taking it back for a warranty exchange and playing dumb. If you can go without your device for a few days go on eBay and get a jig. Try that and then flash with ODIN back to stock. It's better than driving up the overall costs for others (trickle-down) for something you did yourself.
My $0.02.
hi there, i am new to smartphones, had a week to play, so i can get around..
i want to root my phone, but there are so many different versions, and i don't want it to become a brick.
not sure if this is all the info i need to give - but i can supply more if needed.
samsung galaxy nexus gt-i9250.... (on the box)
2G GSM, 3G UMTS,(on there website, where I bought it)
mobile network type HSDPA:9, baseband version i9250XXKK6 (on the phone)
can you give me a link (prefer this site) - that is applicable for my phone.. thanks
Are you sure you really want to root it? What's the reason? If you do I would suggest more reading, all the answers you need are already there.
nazar7 said:
hi there, i am new to smartphones, had a week to play, so i can get around..
i want to root my phone, but there are so many different versions, and i don't want it to become a brick.
not sure if this is all the info i need to give - but i can supply more if needed.
samsung galaxy nexus gt-i9250.... (on the box)
2G GSM, 3G UMTS,(on there website, where I bought it)
mobile network type HSDPA:9, baseband version i9250XXKK6 (on the phone)
can you give me a link (prefer this site) - that is applicable for my phone.. thanks
Click to expand...
Click to collapse
Yours is the GSM model, everything you need will be for maguro.
Roms, recoveries etc.
Don't flash things that say toro or toroplus.
Use search to find stuff yourself.
Use my sig.
And as stated, follow GSM outlines.
thanks guys/gals, will do it tomorrow
it helps a lot....
someone asked the reason - security and restrictions for apps (like allowing them to access wifi, but not mobile usage) - basically giving me more control over what happens
Edit - what gives, i just got "congradulations, you are the melbourne winner for today" - and it just took over the whole page??
nazar7 said:
thanks guys/gals, will do it tomorrow
it helps a lot....
someone asked the reason - security and restrictions for apps (like allowing them to access wifi, but not mobile usage) - basically giving me more control over what happens
Edit - what gives, i just got "congradulations, you are the melbourne winner for today" - and it just took over the whole page??
Click to expand...
Click to collapse
Its a pop up ad. Welcome to the internet.
nazar7 said:
Edit - what gives, i just got "congradulations, you are the melbourne winner for today" - and it just took over the whole page??
Click to expand...
Click to collapse
lmfao. You're really clueless, huh?
Don't root your phone until you are ready. It doesn't sound like you are yet.
Sent from my Galaxy Nexus using xda premium
I absolutely agree.
It's almost 100% certain that you will end up breaking this phone within 3 years or less.
Then again, I am a 17 year old with a serious addiction to tampering and modifications...
Just letting you know that it IS possible to make a stupid mistake, then have a phone that has a faulty recovery parition with no way to flash because the battery is too dead and it won't charge because your /system parition is wiped clean.
Personally, I have a insurance program from Sprint because my father is a smart man and doesn't trust me with $800 demo phones and tablets lol
What i'm trying to say is that it's much easier to go "Woops. I hardbricked it. Time to wait for a replacement and pay $35", than "Woops. I hardbricked it. Time to shell out $500 for another phone."
rsjc741 said:
I absolutely agree.
It's almost 100% certain that you will end up breaking this phone within 3 years or less.
Then again, I am a 17 year old with a serious addiction to tampering and modifications...
Just letting you know that it IS possible to make a stupid mistake, then have a phone that has a faulty recovery parition with no way to flash because the battery is too dead and it won't charge because your /system parition is wiped clean.
Personally, I have a insurance program from Sprint because my father is a smart man and doesn't trust me with $800 demo phones and tablets lol
What i'm trying to say is that it's much easier to go "Woops. I hardbricked it. Time to wait for a replacement and pay $35", than "Woops. I hardbricked it. Time to shell out $500 for another phone."
Click to expand...
Click to collapse
The not charging issue...
You can fix that by splicing up a USB cable.
Lulz. (Seriously, though)
nodstuff said:
Its a pop up ad. Welcome to the internet.
Click to expand...
Click to collapse
chancy319 said:
lmfao. You're really clueless, huh?
Click to expand...
Click to collapse
nope, just expected more from such a tech forum....
have installed a ad blocker now (new laptop)
not a noob to computer, just very careful
**** Update ****
Jubakuba
have tried both methods for adb - (for dummies and C something)
http://forum.xda-developers.com/showthread.php?t=1529058
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows (tried this one first)
and both times, it wont recognize the phone ?? my laptop see's it -just not adb
with this one http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
on 13&14 it says "on success" - but it wasn't successful
my computer can see the nexus for files, ADB just can't see it ??
I get down to 17 - but i want to check with you first....
when it says "You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark. "
there is no ADB - but there is a device (the nexus) with a yellow exclamation..
if i update this driver (as it tells me to - 19) but i have to right click on the yellow exclamation - which is the phone
wont i change the driver on the phone instead of the computer?? (i am using windows 7 - and usb debugging is ticked)
i wish i took a photo, it would have made it much easier (maybe it is a problem with the screen locking on the phone??)
sorry, forgot to mention, this was the first time my phone has been connected to the computer (maybe that has something to do with it)
any help appreciated
http://forum.xda-developers.com/showthread.php?t=1664791
read the part where i am stuck on the drivers.
Hi I'm trying to root my KF2. What I really want to do is to install some emulators on it. I plan on getting a custom kernel, rom, etc. for it but don't know which one to use.
I'm looking for something that's lightweight, doesn't consume too much RAM or internal memory.
Sooo.... any suggestions?
Also just FYI, I don't have the factory USB cable. I'm using a third party one, not sure if that matters.
-Thanks
Read the sticky
http://forum.xda-developers.com/showthread.php?t=2228539
Also.. No idea what you mean by "3rd party" cable. A factory cable is a factory cable no matter the source. Not to be confused with a NORMAL usb cable.
There aren't that many roms to choose from, but i recommend reading EVERYTHING you can before doing anything. The KF2 isn't like other devices.
--
Sent from my mind to your screen.
mindmajick said:
Read the sticky
http://forum.xda-developers.com/showthread.php?t=2228539
Also.. No idea what you mean by "3rd party" cable. A factory cable is a factory cable no matter the source. Not to be confused with a NORMAL usb cable.
There aren't that many roms to choose from, but i recommend reading EVERYTHING you can before doing anything. The KF2 isn't like other devices.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
I'm using a Sony Ericsson cable, not the one that came with the Kindle, does that matter?
Xperia Player said:
I'm using a Sony Ericsson cable, not the one that came with the Kindle, does that matter?
Click to expand...
Click to collapse
Again. Read the sticky or you WILL brick your device. Seriously. Many experienced users already have.
READ THE WHOLE THING. Question 19 in the sticky answers that.
Edit: really. Read it all. Skipping to the answer will only help you so much.
--
Sent from my mind to your screen.
mindmajick said:
Again. Read the sticky or you WILL brick your device. Seriously. Many experienced users already have.
READ THE WHOLE THING. Question 19 in the sticky answers that.
Edit: really. Read it all. Skipping to the answer will only help you so much.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
When you say the KF2 isn't like other devices, it really makes me regret getting a Kindle
Lol. Nothing to regret. The hardware is solid. The bootloader is locked down, is all. You just have to be more careful with this device than, for example, a sony xperia phone.
I love my kindle. It's really a great device.
--
Sent from my mind to your screen.
mindmajick said:
Lol. Nothing to regret. The hardware is solid. The bootloader is locked down, is all. You just have to be more careful with this device than, for example, a sony xperia phone.
I love my kindle. It's really a great device.
--
Sent from my mind to your screen.
Click to expand...
Click to collapse
I bought it on impulse, and with the intentions of rooting/modding it (easily) boy was I wrong.
Got it for $60 cash and a $20-30 item I no longer wanted, he was supposed to include the Kindle USB cord but couldn't find it and gave me a Motorola phone charger instead -.-
He's a pretty close friend, he told me he'd give it to me once he finds it, but that may be awhile...
Anyway, a little off subject there...
I read the ENTIRE sticky. Learned a few things but overall not too much.
Is there an idiots guide to rooting/modding this thing? I don't want to screw up, looks like people are bricking these things permanently & I don't want to fall victim of that.
Any advice or tutorials would be awesome.
Thanks.
A fast boot or a factory cable is a cable that has pins shorted in it to force the kindle into a sort of download more that comes without an ui..
These have to bee special bought, they don't come with the kindle.
You don't have to have one but if you goof you'll most likely need it
For rooting it's pretty easy I just did one using a thread a few threads below this one you'll see my name thanking the guy who supplied the link
http://forum.xda-developers.com/showthread.php?p=40170244 As to what rom no clue
Sent from my GT-P3110 using xda app-developers app
Xperia Player said:
I bought it on impulse, and with the intentions of rooting/modding it (easily) boy was I wrong.
Got it for $60 cash and a $20-30 item I no longer wanted, he was supposed to include the Kindle USB cord but couldn't find it and gave me a Motorola phone charger instead -.-
He's a pretty close friend, he told me he'd give it to me once he finds it, but that may be awhile...
Anyway, a little off subject there...
I read the ENTIRE sticky. Learned a few things but overall not too much.
Is there an idiots guide to rooting/modding this thing? I don't want to screw up, looks like people are bricking these things permanently & I don't want to fall victim of that.
Any advice or tutorials would be awesome.
Thanks.
Click to expand...
Click to collapse
I'm not allowed to answer your question posted in the "[Root][Working 10.2.4]" thread, hence posting here.
Before you continue with rooting, you may want to make sure your adb drivers are correctly installed.
Here's how you can do that:
- Abort the "RootQemu.bat" batch file
- At the command prompt (assuming the directory you copied the QemuRoot file to is your current directory) enter "adb devices"
- If not already running, the adb daemon needs to be started first, hence it will most probably respond with
"* daemon not running. starting it now *"
"* daemon started successfully *"
- Once the daemon is started, adb will try to connect to your devices via the adb drivers, which you need to have installed in a first step.
- If the drivers are properly installed and adb can connect to your device, above-mentioned command should return something similar as
"1234567880 device"
- If you are only getting "List of devices attached", then the adb drivers are not or not correctly installed
In this case you will need to go back to reading some more, get the drivers and/or learn how to properly install them.
Hope this helps. Good luck!
Good news everyone (not a futurama pun)
I have successfully rooted & installed Google Play on my KF2!
Is there an easy way to change the launcher or ROM & move things from my internal memory to the cloud? Like for example I got a few things from the Google Play store and they go straight to my device, while other apps go to the cloud.
EDIT: How come my Kindle doesn't show up in My Computer when I connect it to my PC?
Thanks for the help so far.
Xperia Player said:
Good news everyone (not a futurama pun)
I have successfully rooted & installed Google Play on my KF2!
Is there an easy way to change the launcher or ROM & move things from my internal memory to the cloud? Like for example I got a few things from the Google Play store and they go straight to my device, while other apps go to the cloud.
EDIT: How come my Kindle doesn't show up in My Computer when I connect it to my PC?
Thanks for the help so far.
Click to expand...
Click to collapse
Kindlefree is an app that can help get you started on the Amazon ROM. Just make sure you are on a KF2 before flashing anything. Easiest way to tell is by the software version.
Anything 10. Will be a KF2.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Backstory: I have just switched over to Sprint from ATT, due to a growing need to save money on my family plan. As such, I had to sell my Nexus 4 and get an Optimus G (HTC One was sold out ) Picked this phone for it's extreme similarity to the N4, which I liked quite a bit. Brought home my new device and immediately set about rooting and unlocking it. I have been around this particular block many times since my first rooting and ROMing experience with the HD2 back in '10. I am relatively adept at this and don't typically get put off by it being more or less difficult than the last time. For example, I had an HTC Rezound that required a length or wire to touch two contact points together during a script run to unlock the bootloader. That was fun! Point is, this ain't my first rodeo. I researched the threads pretty thoroughly, and although I wanted to use shadow's AIO root/unlock, it sounded from the posts that it was outdated due to recent updates that hadn't been implemented. Sooooo, I went with engine's root/unlock. I followed the instructions carefully, installed and utilized Freegee(after running the rooting script, which was successful), got to the 'YAY' screen, and went about the reboot to recovery process, and poof! - brick city. What sucks is that I see all over where people have had seemingly the same problem (no boot past the LG splash screen). The thing is, everyone else seems to be able to get a download mode or fastboot or both, thereby making some form of 'recovery' possible, even without an actual recovery program being in place. I cannot. I was unable to do anything with the device, and after many hours of trying, I took the damn thing to Sprint and got another(always root and ROM on the first day, that way you can blame the crappy product instead of your crappy ability to follow directions ). Now, I have never been too proud to admit when I screw up, but I was very careful about reading and following the instructions and took my time. This isn't to say it couldn't still be user error; it almost always is. But, the fact that my problem was so similar to so many others, but no one else had documented a problem like mine really bugged me. Anyway, I got a new one and have been researching LGNPST and teenybins way of rooting/unlocking. I have already installed all the drivers and software and am ready to go. But, I gotta be honest, I am leery. I don't care about taking another phone back to Sprint, but just don't want the hassle. I am nervous because it seems that these devices are very finicky and there are many posts in all of the root/unlock threads with people who can't seem to get theirs handled. This is compounded by the fact that my friggin device refuses to go into either download mode or fastboot mode. I have followed the instructions for this as well (vol down and pwr for download - all three and plug at the same time for fastboot) I can't accomplish either task with this device. WTF. I have no problem doing the noobie dance if I am somehow screwing this process up, but I can't see how. I have some experience at this; I have owned an HD2, a Sensation 4G, a Rezound, a G2X, a GSII Skyrocket, a Nexus 4, and this. All have been rooted and unlocked successfully, except one of the LGs, see below. I have had issues getting this done before, but never like this. I also have some experience compiling builds, so I am not a pro by any means, but I have a pretty good idea how to go about these things when I change devices. What I would like is some factual and specific tips, steps, and/or advice. I have read all of the threads about these, so simply mirroring the current steps listed is not much help right now. I also have some questions, regardless of whether or not some of the 'purists' will troll my possibly noobie style thoughts :
Why the hell can't I get into download or fastboot? If this is something that is actually happening and not just my user error, it would definitely be a reason for unlock failure and potential bricking, right?
Is it absolutely neccesary to unlock after root? I know that the two almost always go hand-in-hand, but nevertheless I think it is a legitimate question.
Is this just a problem with LG devices? I had a G2X for about a week, and went through 3 of them trying to get the damn thing rooted and unlocked. I literally could not do it, and after the third one even TMobile was tired of it. The gave me a Sensation that I had rooted and ROMed in about an hour. I had no issues with my N4, and to be honest I was nervous as hell getting that badboy set up. smooth sailing....
I know that most eveyone swears by the LGNPST method, but there have been reported failures through this method as well. Can I get anything more than just opinion about the best way to accomplish this with a minimum of bloodshed?
I would appreciate as much advice and discussion as possible, because I can't be the only one and we have to be able to figure this out once and for all.........
One other question: Why the hell am I having so much trouble extracting the .bin files on my laptop? I have 7zip, archive manager, and winzip. All three have the settings refecting .bin files being formatted with each file manager, and none will recognize the .bin files. I have an HP DV7 dual-core, running W7 Ultimate. SOLVED: Desktop at work showed these files properly as .bin. Don't know why my laptop won't........
UPDATE: I was able to get into download mode by pressing both vol buttons while plugged in. I was also able to gain root using fiddy619s Universal root and held it after reboot. For all the good it does... can't use font installer. hmph. Can alter root files though, so progress is being made
UPDATE: I am able to get OEM system recovery by holding dn and pwr until 'buttons' light up, then releasing pwr but not dn until recovery shows. Still can't get anything from holding up and pwr. Tried unplugged and plugged in; no love. From what I have read, you HAVE to be able to access fastboot to be able to complete this process, sooooo........
BMP7777 said:
Backstory: I have just switched over to Sprint from ATT, due to a growing need to save money on my family plan. As such, I had to sell my Nexus 4 and get an Optimus G (HTC One was sold out ) Picked this phone for it's extreme similarity to the N4, which I liked quite a bit. Brought home my new device and immediately set about rooting and unlocking it. I have been around this particular block many times since my first rooting and ROMing experience with the HD2 back in '10. I am relatively adept at this and don't typically get put off by it being more or less difficult than the last time. For example, I had an HTC Rezound that required a length or wire to touch two contact points together during a script run to unlock the bootloader. That was fun! Point is, this ain't my first rodeo. I researched the threads pretty thoroughly, and although I wanted to use shadow's AIO root/unlock, it sounded from the posts that it was outdated due to recent updates that hadn't been implemented. Sooooo, I went with engine's root/unlock. I followed the instructions carefully, installed and utilized Freegee(after running the rooting script, which was successful), got to the 'YAY' screen, and went about the reboot to recovery process, and poof! - brick city. What sucks is that I see all over where people have had seemingly the same problem (no boot past the LG splash screen). The thing is, everyone else seems to be able to get a download mode or fastboot or both, thereby making some form of 'recovery' possible, even without an actual recovery program being in place. I cannot. I was unable to do anything with the device, and after many hours of trying, I took the damn thing to Sprint and got another(always root and ROM on the first day, that way you can blame the crappy product instead of your crappy ability to follow directions ). Now, I have never been too proud to admit when I screw up, but I was very careful about reading and following the instructions and took my time. This isn't to say it couldn't still be user error; it almost always is. But, the fact that my problem was so similar to so many others, but no one else had documented a problem like mine really bugged me. Anyway, I got a new one and have been researching LGNPST and teenybins way of rooting/unlocking. I have already installed all the drivers and software and am ready to go. But, I gotta be honest, I am leery. I don't care about taking another phone back to Sprint, but just don't want the hassle. I am nervous because it seems that these devices are very finicky and there are many posts in all of the root/unlock threads with people who can't seem to get theirs handled. This is compounded by the fact that my friggin device refuses to go into either download mode or fastboot mode. I have followed the instructions for this as well (vol down and pwr for download - all three and plug at the same time for fastboot) I can't accomplish either task with this device. WTF. I have no problem doing the noobie dance if I am somehow screwing this process up, but I can't see how. I have some experience at this; I have owned an HD2, a Sensation 4G, a Rezound, a G2X, a GSII Skyrocket, a Nexus 4, and this. All have been rooted and unlocked successfully, except one of the LGs, see below. I have had issues getting this done before, but never like this. I also have some experience compiling builds, so I am not a pro by any means, but I have a pretty good idea how to go about these things when I change devices. What I would like is some factual and specific tips, steps, and/or advice. I have read all of the threads about these, so simply mirroring the current steps listed is not much help right now. I also have some questions, regardless of whether or not some of the 'purists' will troll my possibly noobie style thoughts :
Why the hell can't I get into download or fastboot? If this is something that is actually happening and not just my user error, it would definitely be a reason for unlock failure and potential bricking, right?
Is it absolutely neccesary to unlock after root? I know that the two almost always go hand-in-hand, but nevertheless I think it is a legitimate question.
Is this just a problem with LG devices? I had a G2X for about a week, and went through 3 of them trying to get the damn thing rooted and unlocked. I literally could not do it, and after the third one even TMobile was tired of it. The gave me a Sensation that I had rooted and ROMed in about an hour. I had no issues with my N4, and to be honest I was nervous as hell getting that badboy set up. smooth sailing....
I know that most eveyone swears by the LGNPST method, but there have been reported failures through this method as well. Can I get anything more than just opinion about the best way to accomplish this with a minimum of bloodshed?
I would appreciate as much advice and discussion as possible, because I can't be the only one and we have to be able to figure this out once and for all.........
One other question: Why the hell am I having so much trouble extracting the .bin files on my laptop? I have 7zip, archive manager, and winzip. All three have the settings refecting .bin files being formatted with each file manager, and none will recognize the .bin files. I have an HP DV7 dual-core, running W7 Ultimate.
Click to expand...
Click to collapse
Welcome to the Optimus G. It sounds like you got a phone that needs the "Special Unlock". This is not a method available to the general public. You will need to go to IRC and ask Shelnutt2 for it. Good luck!
Stories like this make me not want to root/unlock.
I know the basics, but I dont know much beyond that. I would feel pretty stranded if some sort of soft-brick, etc occurred.
Rooting my OG EVO was simple as simple could get.
Mindspin_311 said:
Stories like this make me not want to root/unlock.
I know the basics, but I dont know much beyond that. I would feel pretty stranded if some sort of soft-brick, etc occurred.
Rooting my OG EVO was simple as simple could get.
Click to expand...
Click to collapse
I'm just as nervous, but I'm not gonna let this damn thing get the best of me. Already made some progress. As I figure it out, I plan to offer another listing for how to accomplish this goal. I don't think we need YET ANOTHER thread about it though. Probably ask one of the others to add whatever makes mine work to their existing OP. I think part of the problem is too many different ways to do this that are only verified as working by a few; or many up until a recent time. Maybe the latest LG update is part of it as well.....
I know this feel all too well. On my third LGOG and I was able to properly rot/unlock. I'm more of a visual learner so learning using text only was a pain in my ass(weird right?) But I am way to skeptical to flash a new ROM and the ROM I want to use(Paranoid Android) was just recently ported so I'll stick with Stock rooted for now.
KUmike said:
Welcome to the Optimus G. It sounds like you got a phone that needs the "Special Unlock". This is not a method available to the general public. You will need to go to IRC and ask Shelnutt2 for it. Good luck!
Click to expand...
Click to collapse
Actually not anymore, since I rewrote the freegee app, it's built into it. On the main screen press menu -> sbl unlock. Follow the directions, read everything, then after you enter the code, unlock like normal. This method is guarnteeed to always work, however there is some additional risks involved and only a small subset of optimusg owners need it, that is why it is not the default method.
BMP777 said:
vol down and pwr for download - all three and plug at the same time for fastboot
Click to expand...
Click to collapse
That is wrong, it's vol up + vol down + have the usb plugged in + power and they will get you to download mode. Fastboot mode is only avaliable when unlocked and that is vol down + power .
Tried the Freegee again but the softbrick was the result. I didn't find the sbl unlock, it must be in the paid version. Waiting for a new bank card to come in the mail is the only reason I haven't coughed up the buck. Was able to get into download mode easily and restore using LGNPST. No fastboot or recovery access though......back to the drawing board. Makes me wonder if the last one was really broken or I was too dumb to figure it out.
BMP7777 said:
Tried the Freegee again but the softbrick was the result. I didn't find the sbl unlock, it must be in the paid version. Waiting for a new bank card to come in the mail is the only reason I haven't coughed up the buck. Was able to get into download mode easily and restore using LGNPST. No fastboot or recovery access though......back to the drawing board. Makes me wonder if the last one was really broken or I was too dumb to figure it out.
Click to expand...
Click to collapse
I believe the SBL unlock method in the freegee app is there, you just have to hit the menu button (I think).
Ran LGNPST again and acheived unlock. Good to go.
BMP7777 said:
Ran LGNPST again and acheived unlock. Good to go.
Click to expand...
Click to collapse
Glad to hear it, and fyi as in the description on the play store, the free and paid versions are 100% the same minus the name change.
I was considering trading my Note 2 for two OG's but reading this scares me a lil. Is it really that bad to root this thing?
Sent from my SPH-L900 using xda app-developers app
RayTrue04 said:
I was considering trading my Note 2 for two OG's but reading this scares me a lil. Is it really that bad to root this thing?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Nope not at all. Rooting and unlocking is pretty easy for 99% of the phones out there.
Shelnutt2 said:
Nope not at all. Rooting and unlocking is pretty easy for 99% of the phones out there.
Click to expand...
Click to collapse
Have you ever owned an Evo? Rooting and unlocking is not always easy lol
Sent from my SPH-L900 using xda app-developers app
RayTrue04 said:
Have you ever owned an Evo? Rooting and unlocking is not always easy lol
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
By phones I was meaning optimus g's
Sent from my LG-LS970 using xda app-developers app
Rooting this device is easy. Unlocking was a bit more detailed but in the end, just as easy. Still not certain if my issues were genuine or user error, but I will assume it was me. Make sure you read the instructions over and over before you begin. I have been doing this for a long time so I may have gotten caught up in thinking I knew all there was to know and not paying close enough attention to the details. Thanks to fiddy619, engine95, and especially Shellnutt2 for making these tools and taking time to offer assistance. Use fiddys tool for rooting, then buy and install Freegee for unlocking. If you have issues with Freegee, use the two-button plug method of accessing download mode(press and hold both volume buttons while plugging in the USB), and then use the LGNPST tool with teenybins for unlocking and/or repairs. These are the steps that worked for me without hassle; your experience may vary......