Develop Bugs

Bricked Your SII? Your life isn't over.

After the numerous amount of times that I bricked my phone, I could definitely say that I didn't need the help of others or T-Mobile.
Here is the "grand daddy" rule of rooting.
------------------ALWAYS BACK UP YOUR PHONE-------------------
If my friend didn't say that I would have definitely been screwed. A few days after I bought this phone I found out all of the features that it has to offer, so it seemed. Wifi Tethering? Yes I always wanted that, until I found out that you have to pay $14.99 a month. Clueless, I found out about rooting and the wonders it could do for your phone.
Okay lets get to the point. So if you are reading this, you probably bricked your phone or you are a nerd who is proofreading what I am saying to pick out the bad on what I wrote. I'm not hating on nerds neither am I one, but nerds run the world. Thanks to all ROM and Kernel makers. You rock! ANYWHO! If you bricked your phone, then don't panic. Honestly, don't panic. My friend teased me to the amount of times I did so and after the second time of bricking it, I didn't worry.
So I bricked this phone so bad that I the same screen popped up everytime I took the battery out. If this is you, connect your phone to your computer with your USB and use ODIN to rebrick it again. Trust me it will work. We noobs need to do more research, which I do. Go to Galaxy S2 root dot com. (Just get rid of the spaces It worked for me. and just following the directions again (not including putting your phone into download mode and whatnot) worked for me. Just plug in your phone, open ODIN and follow the rest of the instructions and it should work fine.
Rules for backing up? Sure thought you would never ask.
Back up your current ROM first:
-Turn off phone and hold the up and down volume key while holding the power button.
-When you feel the phone vibrate let go of the power button, but hold on to the volume buttons.
-Options come up, use the volume keys to move up and down and the power. keys to select.
- Go to these. Backup and Restore>Backup.
You are done. Don't turn off your phone while backing up though.
Now go to the reference site about and learn how to root it. After you do, come back to this site, but go into Android Development and you will find roms you can choose from that will fit to your liking.
It's easy..
Download the ROM to your SD card.
Do the procedure that will take you into download mode explained above.
Go to install from sd card and choose the file you want to download.
Got any questions? I'm considered a noob because I joined yesterday. I can still help though. I loved the video that you have to watch before you register. I think I'm about to log out and watch it again.

Welcome to Xda. Great to have you on board

Is this a clever way to advertise a webpage? BTW, if you read.. it is generally very difficult to brick a phone..

I think backup is only available if you have CWM, not stock recovery. At least I don't see that option on my stock phone after booting to recovery

vinterchaos said:
Is this a clever way to advertise a webpage? BTW, if you read.. it is generally very difficult to brick a phone..
Click to expand...
Click to collapse
you know, I suppose it could be.. I didn't even think about it, guess I give people the benefit of the doubt

Plus we already got stock .tar file to flash through odin now. And yeah, this phone is pretty much impossible to brick. Either using superoneclick or original rooting method, so easy..
DMolina ツ

Sorry, it is not. When I got my phone last month, it was going to hell and back trying to get rooting instructions. That site helped me a lot and it really worked for me. I'm just helping someone else who still needed more information on rooting/bricking their phone.

New To Android, but bricked my phone?

Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks

When you rooted did you NANDROID backup ? If not go into recovery and clear cache and then go into advanced and wipe delvik cache. reboot
If that fails go back into recovery and do a factory reset and you should be ok.

touchdownadrian said:
Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1727401

This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone

z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
I disagree as long as you are willing to learn from the mistake all is good. I had a Samsung Exhibit II and deleted touch wiz launched (I was using go launcher) later I would do a factory reset and well... learned that system files do not get restored when you do a factory reset...oops
Sent from my SGH-T999 using xda premium

I agree, we all were NOOBS at some point. That's the one thing I love about XDA is that with patience and the help of the users any noob can learn how to mod their devices. One piece of advice that I can offer is before you do any type of modding is READ and keep on READING. I have bricked the first device I ever rooted because I did not READ the forums as they are meant to be read.

z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium

Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium

not fair
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:

touchdownadrian said:
Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.

TheSeanTeam said:
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.
Click to expand...
Click to collapse
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.

lordazoroth said:
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.
Click to expand...
Click to collapse
Same here. It took me months of researching on my vibrant before flashing my first rom (bionix 1.6 by teamwhiskey). As I progressed, I did brick left and right but I always managed to bring it back to life with my prior knowledge. Now I'm eagerly waiting for my computer to be done downloading the root files and get started.
Sent from my SGH-T999 using xda app-developers app

Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999

Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
+++++++1 on that.... DAMN talk about headaches....

dmarco said:
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
:good::good:

Yeah one of the only other IMPORTANT thinks i could add would be always do a factory reset before flashing roms.. some people like to flash "dirty" i wouldnt recommend it cause you will ALWAYS have issues maybe not in a hour but guaranteed you will... but knowledge is power dude.. i two read for about 36 hours before rooting my phone.. i rooted my wifes phone days after a rooted mine back in the day it only took like 15 mins.. another thing let phone sit 10 mins before ya play with it... gotta let the cache settle... the ten min wait is well worth it.. ive been doing it that way since the vibrant bro.. happy flashing and welcome..

I read constantly things change hourly like when that new leaked kernels came out for sgs2 and the emmc was trashed never to come back from a brick again. To anyone that cares if you love your phone read more than just the root and flash stuff learn what makes your phone tick from the factory hardware software and added crap from your carrier it all play's a part in the end result. Its as easy as you make it.
Sent from my SGH-T999 using Tapatalk 2

Nabeel10 said:
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999
Click to expand...
Click to collapse
Ive passed down two vibrants (both rooted) to my sons so they can learn to flash roms and everything else that comes from the joys of root.
Sent from my SGH-T999 using xda app-developers app

[Q][HELP]S3 Hard Bricked after Flashing Illusions

I FIXED IT
Here's the Link to my Guide.
http://forum.xda-developers.com/showthread.php?t=2369125
Okay, So here's what I did.
I flashed the latest Illusions ROM for my S3 and the Slim AIO 7 for 4.2.2 (since Illusions is based out of SLIM, AOKP, PA, CM, ETC). Then TWRP 2.6.0.0 said that SuperSu wasn't installed (what the heck?!?!?) and it prompted me to install su so I was like "What the heck, why not" so I swiped for yes. Then the screen went black for a good 20 minutes. I got worried, did a battery pull and tried to but straight to recovery... no bueno. Same for booting to dl mode. I plugged my phone in to my computer without the battery and the red LED comes on for 10 seconds and then it dies. It prompted windows to install the QHUSB_DL driver and it failed. WHAT THE HECK JUST HAPPENED?!?
Is there anything I can do to unbrick it?
Do I have to JTAG/JIG or what? If so, can anyone direct me to it? (Last resort)
I'm on the MD4 bootloader and modem.
I really need to get this phone fixed before I go to basic on the 23rd of July.
Other info: Yes, I already went to the local Sprint store (not to get a replacement. That would be irresponsible of me considering my S3 is built by me from the MoBo on up) to get help on flashing it back to stock.

Jtag is the only way and you need to send it to someone who does that.
Sent from the future via Tapatalk 4

deBricker said:
Okay, So here's what I did.
I flashed the latest Illusions ROM for my S3 and the Slim AIO 7 for 4.2.2 (since Illusions is based out of SLIM, AOKP, PA, CM, ETC). Then TWRP 2.6.0.0 said that SuperSu wasn't installed (what the heck?!?!?) and it prompted me to install su so I was like "What the heck, why not" so I swiped for yes. Then the screen went black for a good 20 minutes. I got worried, did a battery pull and tried to but straight to recovery... no bueno. Same for booting to dl mode. I plugged my phone in to my computer without the battery and the red LED comes on for 10 seconds and then it dies. It prompted windows to install the QHUSB_DL driver and it failed. WHAT THE HECK JUST HAPPENED?!?
Is there anything I can do to unbrick it?
Do I have to JTAG/JIG or what? If so, can anyone direct me to it? (Last resort)
I'm on the MD4 bootloader and modem.
I really need to get this phone fixed before I go to basic on the 23rd of July.
Other info: Yes, I already went to the local Sprint store (not to get a replacement. That would be irresponsible of me considering my S3 is built by me from the MoBo on up) to get help on flashing it back to stock.
Click to expand...
Click to collapse
I take it that post I linked to in my thread didnt work then?
And FYI
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

What was the name of the file for Illusion ROM?
Sent from my SPH-L710 using xda app-developers app

Notorious said:
What was the name of the file for Illusion ROM?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
FML, I made a noob mistake. Flashed a i9300 Illusion Rom. But I got it from the link on the page. It's Illusion i9300 4.2.2 07132013

billard412 said:
I take it that post I linked to in my thread didnt work then?
And FYI
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Click to expand...
Click to collapse
No. Looks like I'm going back to my ogEvo. Won't be able to use that service until after the Navy is done with me. FML. I still can't believe I made a noob mistake. -_____- I have never bricked a phone and this is ironic because i usually de-brick phones... not brick 'em.

Have you looked at this thread
[HOW TO] Unbrick your Sprint phone from flashing an International gsm boot imag

jdelano said:
Have you looked at this thread
[HOW TO] Unbrick your Sprint phone from flashing an International gsm boot imag
Click to expand...
Click to collapse
I JUST FIXED IT! LOL. I'm in the middle of Barnes and noble and I just fixed it. I'll put down directions for a HOW TO for my method, but it involves having Linux.
HARD BRICK FIX W/O THE JTAG!
and I'll have to give credit. I finally figured out how to dd that file that was posted by (I don't have his username atm) but yeah! I got it to work. His method needs a little more instruction.

Just booted to DL mode

Yeah, if I may, please don't make a guide thread for that. It will only encourage people to flash international roms.
Sent from my S3 on Sense 5 (you jelly?)

glad to hear you got it working.

CNexus said:
Yeah, if I may, please don't make a guide thread for that. It will only encourage people to flash international roms.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
Yes, well, some people would like the convenience of not having to send their phone off and spending 60 dollars to get it fixed. And there are many ways to hard brick an S3 and I think that this would be a convenient way of fixing their phone.
Mine was a legit mistake. I'm a veteran flasher of ROMs and everyone does slip up.

deBricker said:
Yes, well, some people would like the convenience of not having to send their phone off and spending 60 dollars to get it fixed. And there are many ways to hard brick an S3 and I think that this would be a convenient way of fixing their phone.
Mine was a legit mistake. I'm a veteran flasher of ROMs and everyone does slip up.
Click to expand...
Click to collapse
Well if you do something like that, you should own up to it and pay the $60 bucks to get it fixed. International roms don't magically wind up on your flashing queue in recovery.
I obviously can't stop you from posting anything, but just keep that in mind.
Good day.

CNexus said:
Well if you do something like that, you should own up to it and pay the $60 bucks to get it fixed. International roms don't magically wind up on your flashing queue in recovery.
I obviously can't stop you from posting anything, but just keep that in mind.
Good day.
Click to expand...
Click to collapse
Yes, well. I can't exactly do that since I'm in the Navy and I'm going to be gone for the next two months. I prefer to find a method BEFORE paying the 60 dollars to unbrick. Dude, this to help everyone. YES I MADE A MISTAKE. We all do. I understand its frustrating. Even I get frustrated. But why should I pay 60 dollars to have someone else fix my phone when I can fix it myself? I'm not a noob at flashing.

deBricker said:
Yes, well. I can't exactly do that since I'm in the Navy and I'm going to be gone for the next two months. I prefer to find a method BEFORE paying the 60 dollars to unbrick. Dude, this to help everyone. YES I MADE A MISTAKE. We all do. I understand its frustrating. Even I get frustrated. But why should I pay 60 dollars to have someone else fix my phone when I can fix it myself? I'm not a noob at flashing.
Click to expand...
Click to collapse
It's a fine line we walk... We here at XDA want to be helpful to "noobs," but we also want to express the importance of reading and critical thinking before acting.
This argument came up a month or two ago. There's an easy way to make the ROMs check the phone model prior to flashing. This would be a great way to prevent hard-bricks, as the installation will abort on the wrong device. The issue that arises is two-fold:
1) There are many Devs and not all will implement this device check.
2) People will start getting lazy with their flashing, as it seems "idiot proof."
We are actually seeing this with the newest CM10.1 releases. Despite it being clearly spelled out in installation threads (if they read the last 3-4 pages of the thread), a lot of people are trying to flash them without updating their bootloader. They then get the infamous system 7 error. I was answering threads one after the next with people asking the exact same question about the system 7 error. A simple 5-minute perusal of the forums (or even just the CM thread) would've yielded the results, but people don't want to put in the "hard work."
In the case of hard-bricks and your guide, I don't fully agree with CNexus (it happens from time-to-time, but he's a quality guy and dev). If it works a good percentage of the time, I think it's a valuable tool that can help a lot of people. That being said, one of the "good" things about a hard-brick is that people generally learn their lesson after one. I've seen people here on XDA that hard-bricked their device (due to carelessness), had to get it JTAG-ed, then came back to become advocates for reading the posts/directions thoroughly. It's amazing how $60 and losing your phone for a week will make people a lot more sober about flashing a Rom.
I don't doubt for a minute that having an "easy" fix for hard-bricks will reduce the impact of this lesson.
That being said, I also believe that having this guide is a good thing. My recommendation would be to rewrite the beginning of the guide to include a strong disclaimer about the dangers of flashing a Rom not meant for your device. I understand that you're trying to take the approach of "hey, we are all noobs at times, it's not that big of a deal," but I think it'll reinforce the lazy mentality of a good number of flashers.
Just my two cents. I'm glad you were able to fix your phone and to find a way to boot into download mode from the SD card so you can rewrite the bootloader partition from Odin.

Why did I get another Android phone?

I was so excited to get a different phone. I had been contending with the insufferable Galaxy Note 2 for 9 months. I really believed that getting the LG Optimus G Pro would be great.
Now I come to find out that there is this locked bootloader? yes before you even start typing: I already know about Freegee. I put it on my phone, it did its work. I have CWM on my phone. I cannot install a different rom. It aborts every time.
And nobody here can help. Its not like you don't see my posts. You see them. You just see them and decide to go on to something more interesting figuring that someone else will help the poor guy.
Hey guess what. I took programming in college. Only one course in VB but I did take it. And I've put up several websites back in the day. ("back in the day is a United States colloquialism")
My point is, even though I have a bit of experience with computers (linux distros, html, visual basic) I still can't figure out the quagmire that is Android.
Once the iPhone 6 comes out, I really have no reason to stick with Android anymore. I mean, if rooting and rom-ing the phone is more boringly laborious than jailbreaking, then what is the point of Android?
For example, lets say I do clear the hurdle and then flash a rom so I can get decent sound? THEN my wifi won't work. Or Some other crucial functionality will be fubar-ed. Okay okay... you say you have a fix for that? Well when its all said and done, the time/energy costs just aren't worth it, now is it?

0 #!*! Given ?

That's interesting because I never took any classes and have never had a problem rooting or doing Roms on any android phone. Sorry your experience has been bad but my questions have always been answered by somebody in the related thread. I would try asking again in the ROM's thread to see what is happening.
Sent from my LG-E980 using XDA Premium 4 mobile app

G pro is the note 2 killer...... Just follow instructions of any op to the T and you should be fine.... It's simple lol
2SHAYNEZ

I agree. I don't post often but I really do hate Apple. Android kicks Apple's you know what many times over. Talk about being locked down.... If I've ever had a problem with a Rom someone has always helped me figure it out. Sorry about your problems though.
sent from my lgog pro. I just had to go bigger.

@Perry2547,
If CWM doesn't work then try TWRP, even i had problems with CWM.either install it from freegee or install this
copy this to sd card and then flash it in CWM and reboot.

I believe the OP just wanted to start a thread...
So you all may ignore him

Thanks @sukesh.
I tried the twrp you linked to and now my phone will let me flash.
Unfortunately, Camera has stopped.

Close thread please.
2SHAYNEZ

I don't even remember how I rooted this phone... I know I found a thread that had comprehensive instructions, links, etc and believe it was as simple as downloading/extracting an executable file on my PC and plugging the phone into USB at the right moment. I've flashed CM, stock 4.4, Slim and always find my way back to stock 4.1.2, modded to my liking. If you can't flash something in a custom recovery, it's likely your phone is protecting you from failure to completely read/follow a prior mod or a prerequisite to the ROM/Mod you wish to flash.
Sent from my LG E980 via Tapatalk Pro (and stupid-fast LTE)

But seriously y'all, I'm just glad I have another two hours if battery life left. That means I will vhave to recharge this phone only 3 more times today.
Unfortunately, Camera has stopped.

I too just got new lg ogp phone. Been trying to customize it to my liking for the past 3 days and night. All I can say about android is it is not for everybody. Sure, you can use it as it is when you first get it as a stock device, and it will work as advertise. But there is a reason that you try modifing it regardless of breaking the manufacturer's warranty (yes, once you start rooting it, you violate the agreement.) You have personality of the kind that thinks you can fix anything by yourself. Nothing wrong with that, I'm in same personality group too, many Android owners are. After all, what is the point if you can't modify the phone to your liking? Might as well get an Iphone right? Sadly though, it seems the new android trend is just heading the way of iphone, where users have to be protected from harming themselves. I noticed all the difficulties when I tried to root this LG phone, as compared to the phone I had two years ago. But android users are a persistent lot, more securities mean inventing more ways to break them. If you have problem installing ROM, try cm11 nightly build, it works for me. Post the specific problems and situations. We should be able to help each other. After all, android owners are together in a special community where we can relate to each other because of ideas we have for our phones. My advice to you is make sure you have the newest recovery and you are properly rooted. I can't use the script method where you run a msdos batch file. Since atnt suppose locked the boot.img file or something. Had to use a program called root master.
Sent from my LG-E980 using XDA Premium 4 mobile app

Nobody gives a damn, get life!

Antigen said:
Nobody gives a damn, get life!
Click to expand...
Click to collapse
Haha
2SHAYNEZ

hawkwind212 said:
I too just got new lg ogp phone. Been trying to customize it to my liking for the past 3 days and night. All I can say about android is it is not for everybody. Sure, you can use it as it is when you first get it as a stock device, and it will work as advertise. But there is a reason that you try modifing it regardless of breaking the manufacturer's warranty (yes, once you start rooting it, you violate the agreement.) You have personality of the kind that thinks you can fix anything by yourself. Nothing wrong with that, I'm in same personality group too, many Android owners are. After all, what is the point if you can't modify the phone to your liking? Might as well get an Iphone right? Sadly though, it seems the new android trend is just heading the way of iphone, where users have to be protected from harming themselves. I noticed all the difficulties when I tried to root this LG phone, as compared to the phone I had two years ago. But android users are a persistent lot, more securities mean inventing more ways to break them. If you have problem installing ROM, try cm11 nightly build, it works for me. Post the specific problems and situations. We should be able to help each other. After all, android owners are together in a special community where we can relate to each other because of ideas we have for our phones. My advice to you is make sure you have the newest recovery and you are properly rooted. I can't use the script method where you run a msdos batch file. Since atnt suppose locked the boot.img file or something. Had to use a program called root master.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly.
If android is going to be locked down, what is the point? With iPhone bringing in 3rd party keyboards and phablet size phones, might as well go with them instead of utilitarian design devices made by dictator led countries where creativity is frowned upon.
Unfortunately, Camera has stopped.

Perry2547 said:
Exactly.
If android is going to be locked down, what is the point? With iPhone bringing in 3rd party keyboards and phablet size phones, might as well go with them instead of utilitarian design devices made by dictator led countries where creativity is frowned upon.
Unfortunately, Camera has stopped.
Click to expand...
Click to collapse
Oh lawdy... Then go to iPhone buddy .. Lol see ya
2SHAYNEZ

But Apple has been implicated in planned obsolescence as well.
Does that matter to you?
To me, it makes me a bit upset that I could work on my vehicle twenty years ago, but now it's not possible. Planned obsolescence.
Make everything sweepstakes m disposable. Lock it down too. Keep every one buying the upgrades.
Unfortunately, Camera has stopped.

Are you still having problem installing the ROM? You have never tell us what kind of problems you ran into specifically. You just ventted your frustration here, nobody wants to hear that. If you want people to help, describe the issue. Go to this site and download the program vroot.
http://www.mobilepoint.us/2013/10/android-root-master-one-click-vroot.html#.U9XRXYfwJGo
The program is in Chinese, so you may want to watch youtube videos on the master root program first. Do a factory reset, clean wipe, run master root program, and hopefully you should be able to install the recovery. Once the recovery is properly installed, you can install the custom rom. Since there aren't many, I suggest you try cyanogenmod.
Sent from my LG-E980 using XDA Premium 4 mobile app

hawkwind212 said:
Are you still having problem installing the ROM? You have never tell us what kind of problems you ran into specifically. You just ventted your frustration here, nobody wants to hear that. If you want people to help, describe the issue. Go to this site and download the program vroot.
http://www.mobilepoint.us/2013/10/android-root-master-one-click-vroot.html#.U9XRXYfwJGo
The program is in Chinese, so you may want to watch youtube videos on the master root program first. Do a factory reset, clean wipe, run master root program, and hopefully you should be able to install the recovery. Once the recovery is properly installed, you can install the custom rom. Since there aren't many, I suggest you try cyanogenmod.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got a ROM to install. I indicated so in the thread. It was the E988 rom on the E980 thread.
I do a lot of whining and complaining but its for the best.
I hope that the complaining I did about Samsung's crappy products has saved a few people from buying...that is the only way that company will learn their lesson. Why pay $800 for a device only to get screen burn in.
But I never ever never ever BRICKED my Note 2.
I've bricked this OGP more times than I can count.
We should have the options to remove the locked boot loader. I would gladly sign an agreement acknowledging the risks.
We're going backwards. We're not making progress.
Same things is happening in desktop/laptop computers. I had to do something unusual to remove the UEFI on a Windows machine I bought last year just to install Lubuntu.
Speaking of Lubuntu, I had an ASUS Netbook with Windows 7 and an Atom processor. Needless to say, it ran slow. So I installed Lubuntu. Then , wow, the device ran so fast and smooth, and the already good battery life got three times better.
Why can't we have an option like that for our smartphones? I want to run the equivalent of Lubuntu on my OGP.
And another thing: Why are some custom roms dimming the display? Is it to make it appear as if the rom is giving better battery life?
Peace out bro.. but yeah, I'm not stopping my rants. If you don't like what I've got to say, simply don't read it.

This phone is not much more difficult to root than any Samsung phone I used. Also why didn't you do research before buying the phone? It was stated clearly that the boot loader was locked. However since day one of purchase I was able to follow a thread and have my phone rooted in ten minutes. It is really not that hard. Now there are a bunch of one click roots. This phone installs custom Roms every time with ease for me. I am no expert but I can read instructions. If you follow them, 99% of the time things will work. I love android for the fact that I have options. I am running a rooted stock ROM now but I love knowing that in ten minutes time I can have a new ROM flashed. This community has been so helpful and responsive.
Sent from my LG-E980 using XDA Premium 4 mobile app

need help with this damn phone

I'll just put this simply. I've got a splitting headache and I've been staring at various web pages for hours trying to (unsuccessfully) unlock the bootloader on my g4 so I can install twrp and root the thing. I'm about ready to kill someone. don't know who, nobody is around.
anyway.. I need a guide on how to transform my LG G4 US99120c US Cellular mobile device running Android 6.0 Marshmallow from a battery-draining eyeball-paining bright white piece of techno-trash into a rooted device with custom recovery that I can use on a regular basis without experiencing severe migraines because I can't delete stuff off the SD card due to carriers being pricks about released phones.
yes, I've tried google. Yes, I've tried searching the forums. If I hadn't done that already I wouldn't be posting here. please don't waste my time with "try the search feature".. I'm here because this is my last viable option for getting the damn thing working right. Please don't just link me to some random instruction manual either. I have bad luck with links.
If anyone does write me with help, write it for an idiot. Normally I'm pretty good at picking things up quickly but I seem to have come down with something the past couple days so I'm also a bit under the weather.. right around the idiot quotient.
I don't want to downgrade, I don't want to install half a dozen things or flash my whatchamacallit (got arrested last time I did that). I want to root the device, and possibly install xposed so I can change everything thats sharp white to a dull black. I do not want to do anything else at all but make calls, text, watch vids, listen to music and play the occasional game.
Thank you very much for your time, and a colossal chunk of gratitude for anyone who wants to take up this task.
FTR: I'm a former samsung user, so if you need to make comparisons I suggest using those. I'll understand 'em.

Jofreidr said:
I'll just put this simply. I've got a splitting headache and I've been staring at various web pages for hours trying to (unsuccessfully) unlock the bootloader on my g4 so I can install twrp and root the thing. I'm about ready to kill someone. don't know who, nobody is around.
anyway.. I need a guide on how to transform my LG G4 US99120c US Cellular mobile device running Android 6.0 Marshmallow from a battery-draining eyeball-paining bright white piece of techno-trash into a rooted device with custom recovery that I can use on a regular basis without experiencing severe migraines because I can't delete stuff off the SD card due to carriers being pricks about released phones.
yes, I've tried google. Yes, I've tried searching the forums. If I hadn't done that already I wouldn't be posting here. please don't waste my time with "try the search feature".. I'm here because this is my last viable option for getting the damn thing working right. Please don't just link me to some random instruction manual either. I have bad luck with links.
If anyone does write me with help, write it for an idiot. Normally I'm pretty good at picking things up quickly but I seem to have come down with something the past couple days so I'm also a bit under the weather.. right around the idiot quotient.
I don't want to downgrade, I don't want to install half a dozen things or flash my whatchamacallit (got arrested last time I did that). I want to root the device, and possibly install xposed so I can change everything thats sharp white to a dull black. I do not want to do anything else at all but make calls, text, watch vids, listen to music and play the occasional game.
Thank you very much for your time, and a colossal chunk of gratitude for anyone who wants to take up this task.
FTR: I'm a former samsung user, so if you need to make comparisons I suggest using those. I'll understand 'em.
Click to expand...
Click to collapse
ill lay it on wasy for you......... you cant unlock bootloader. you cant install twrp and you cant root MM. not unless bootloader unlocked. wich your phone cant be unlocked..
root only on locked bootloader on LP.
there isnt a way and there will never be one.. to bypass and be able to install twrp..

well that explains why fastboot refuses to acknowledge the existence of the phone. I guess.
never say never tho m8, geohot should be proof enough of that for you. looks like I can't downgrade either.
guess I'll have to stick with my s5.

Jofreidr said:
well that explains why fastboot refuses to acknowledge the existence of the phone. I guess.
never say never tho m8, geohot should be proof enough of that for you. looks like I can't downgrade either.
guess I'll have to stick with my s5.
Click to expand...
Click to collapse
there was a bounty of like 3000 dollars to whoever unlock it.. no one did it.. i said i might never be one.. thats waht everyone says samething.