that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Well I guess the rest of us that followed Adam's thread and were easily unlocked and loading ROMs daily are magicians or something?
Try a different USB port and a different computer. I could not get it to work at all on one PC in Windows or Linux, but it worked first try as soon as I tried it on my laptop.
Yes you caught us it was all a huge conspiracy to get you to brick your phone. The hundreds of people that have said they used the program where all in on it.
Sent from my SCH-I605 using xda app-developers app
dmonger11b said:
Yes you caught us it was all a huge conspiracy to get you to brick your phone. The hundreds of people that have said they used the program where all in on it.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Dude, you weren't supposed to tell him!
Honestly if you can't run casual at this point, you shouldn't be doing it at all. I say this because when a "real" problem comes up you won't be equipped to handle it. Then you really will be SOL.
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
Honestly if you can't run casual at this point, you shouldn't be doing it at all. I say this because when a "real" problem comes up you won't be equipped to handle it. Then you really will be SOL.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
BINGO!!
Yea maybe try a different computer. I tried my laptop multiple times and it didn't work but once I did it on my surface pro it worked right away
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
ztotherad said:
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
Click to expand...
Click to collapse
It'd be easier to get a Linux boot able CD or make one than do all that...
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
It'd be easier to get a Linux boot able CD or make one than do all that...
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
yup definitely thought about that as well actually. in which i may just end up doing. is java 7 good to use with casual?
ztotherad said:
yup definitely thought about that as well actually. in which i may just end up doing. is java 7 good to use with casual?
Click to expand...
Click to collapse
That's what I have on my machine. I had no issues with casual, although that was several months ago.
It's not fair to be pissed at people who make the tools. You root at your own risk. Every post and every user will tell you that.
Sent from my SPH-L710 using xda app-developers app
WindroidApps said:
It's not fair to be pissed at people who make the tools. You root at your own risk. Every post and every user will tell you that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
this is so true! you do all this crap at your own risk. and I'm willing to take this risk, and not blame the awesome devs for your problems
5w3d15h said:
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Click to expand...
Click to collapse
I hear apple calling for thier long lost customer :good:
droidstyle said:
I hear apple calling for thier long lost customer :good:
Click to expand...
Click to collapse
that's the best line I've heard today.
If you go the Linux route, just be sure to update the lib files, as stated in the casual thread. Linux worked perfectly for me, and I am a complete noob at this stuff.
Sent from my SCH-I605 using Tapatalk 2
ztotherad said:
that's the best line I've heard today.
Click to expand...
Click to collapse
Haha sup man? Glad to see ya made the jump up to the note 2!
mcp2009 said:
Yea maybe try a different computer. I tried my laptop multiple times and it didn't work but once I did it on my surface pro it worked right away
Click to expand...
Click to collapse
ztotherad said:
definitely having the same problem, my solution: going to reinstall Windows 7 and see if that fixes my problems. if that doesn't then I'll just install a Linux distro on my computer and install java and see if i can get it to run that way. if anything I'll try it on another laptop running Windows xp or another till i get this **** to work. it honestly can't be that hard to unlock the note 2. maybe I'll try to root first and then try to unlock.. idk but i have faith in Adam and the other devs who've helped him and tested for him. I'll get it to work or die trying, because Verizon deserves that middle finger, big time.
anyway good luck on your journey!
Click to expand...
Click to collapse
Yep ive been through this to and finnally got it to work on my moms laptop. Our desktop is the only one I can use odin on and my moms laptop is the only one I can use casual on. When I have some spare time (or feel like it lol) im gonna try loading up a fresh install on windows 7 on 1 of my spare hard drives and see what happens from there. But for now im not really woried about it, just gonna roll with the flow.
Sent from my SCH-I605 using Tapatalk 2
5w3d15h said:
that CASUAL does not work. Oh wait, let me guess, I don't have the right (1 of how many different ones suggested) usb driver, right? And I'm not in ADB, right? And I haven't tried different cables, and ports, and CADI on its own, and zadig, and usbdeview, and pulling the battery when it stalls in download mode (when CASUAL was still recognizing the phone, now neither CASUAL nor ODIN connect to it)? Sorry for the sarcasm, but I'm incredibly frustrated here. How does "one click" turn into a week of trying and trying and trying, and not only not making progress, but seemingly moving backwards where now I can't even get programs to connect? Is there something less messy, contradictory (seriously, the dev thread says "stock anything" but when trying the battery pull and reboot it goes off on me: OMFG WHAT THE HELL ARE YOU DOING? I WARNED YOU! YOU NEED TO ROOT FIRST.) way to unlock? Or a more concise thread of troubleshooting CASUAL (And please, I don't need a link to the same dev thread I just referenced, again.)?
Click to expand...
Click to collapse
I feel your pain but hang in there and keep trying. It took me 3 days and several hours to find the right combination that finally worked. If you follow the dev thread for a few days, you'll see that most everyone having problems eventually gets it to work through a combination of trial and error and support from the devs.
If you haven't already, try the driver suggestions in the last several pages of the dev thread. This seems to be helping quite a few others. Another thing to try is running the Casual jar file from an admin command prompt instead of double clicking the file. This worked for me.
Related
Hey guys,
New to the tbolt and lovin it. I've looked around and am sure the answer is no, but..... Im not gonna have access to a computer that I can use to root for awhile, any ways that I can possibly root this beast with out a computer? Software is version 2116059.
First you need to downgrade anyway and the link that used to be on here is no longer showing up. But
Sent from my ADR6400L using XDA
famester said:
First you need to downgrade anyway and the link that used to be on here is no longer showing up. But
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
So you are saying that this can be done w/o computer?
Sent from my ADR6400L using XDA
Not that I know of. Sorry girlfriend wouldn't leave me alone and forgot to finish. You need the computer to get s off
Sent from my ADR6400L using XDA
famester said:
Sorry girlfriend wouldn't leave me alone and forgot to finish.
Click to expand...
Click to collapse
Thats what she said?
Thanks for the reply, tis the answer I feared.
Sent from my ADR6400L using XDA
Unless you're comfortable with using adb, know how to find or compile adb for ARM CPUs and have a tablet or device that allows usb host mode, then you're going to need a computer. As you need a computer to actually attempt to do that and cross compiling is a pain, that will likely not be an option.
Honestly, I wouldn't even bother doing that myself. Just a pain in the ass when it takes like 10 minutes to do on a PC without that versus some hours and a prayer.
Also you dont need to install anything to use adb on a PC, just the files for it. You could do this on a internet cafe pc, a friend's or a school computer. I mean if you can't find a computer through some means with given that, then I hope you're currently working for the Peace Corps in Sub-Saharan Africa and there's no electricity or phone lines.
yareally said:
Unless you're comfortable with using adb, know how to find or compile adb for ARM CPUs and have a tablet or device that allows usb host mode, then you're going to need a computer. As you need a computer to actually attempt to do that and cross compiling is a pain, that will likely not be an option.
Honestly, I wouldn't even bother doing that myself. Just a pain in the ass when it takes like 10 minutes to do on a PC without that versus some hours and a prayer.
Also you dont need to install anything to use adb on a PC, just the files for it. You could do this on a internet cafe pc, a friend's or a school computer. I mean if you can't find a computer through some means with given that, then I hope you're currently working for the Peace Corps in Sub-Saharan Africa and there's no electricity or phone lines.
Click to expand...
Click to collapse
Thanks for the info man. Was having an issue coming up with a computer, just moved to Philly and dont know alot of people. I was able to find one, good thing too, android phones are not nearly as fun when unrooted.
trainriderben said:
Thanks for the info man. Was having an issue coming up with a computer, just moved to Philly and dont know alot of people. I was able to find one, good thing too, android phones are not nearly as fun when unrooted.
Click to expand...
Click to collapse
Yeah you should be able to just grab adb from some random post on xda and run it and you'll be all set for what you need to root the manual way by downgrading and such. No install needed on the pc as long as you have a pc that runs windows, osx or linux. Just stick it on a usb stick or something and run. If you have issues, just post here again.
If you're using windows, then this should have everything you need in it to use adb without installing it:
http://www.mediafire.com/download.php?a3sx25laka08g0n
You'll just need to go to the directory you unzip it from and run adb in it from the command line.
So, I've been trying for months to fix this thing. Read every post I could find so I wouldn't have to ask for help. Yet here I am. On my knees.
The lowdown:
-Fascinate was not previously rooted.
-Odin will not recognize it.
-Had some issues with the drivers b/c of windows 8, but was able to install from zadig using advanced startup options to bypass driver verification.
-Tried to flash back to stock gingerbread with Heimdall 3 times. Said it was successful everytime. I did use the same usb port that I used for the drivers and it is on the motherboard. And I used stock cable.
-When I try to boot up the phone after flash attempts, some text scrolls across the screen and it says something about "data wipe not successful." It scolls quickly, so I'm not sure what all it says. (One of my first attempts invloved trying to install cwm, so maybe that's why scrolling txt? It looks similar)
-Now, it boots to the little android dude with a white box and an arrow pointing out of it. I'm developing murderous feelings towards him.
In conclusion, I am a noob but have tried to educate myself as much as possible. Please be gentle.
Any ideas out there?
Have you followed this guide? http://forum.xda-developers.com/showthread.php?t=1238070
Read through this.
Sent from my SCH-I500 using xda app-developers app
noobchef said:
Have you followed this guide? http://forum.xda-developers.com/showthread.php?t=1238070
Read through this.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
I'm assuming you're referring to section 5? I have read through that guide, but odin doesn't recognize the phone.
OK. Last time that happened to me it was a cable issue. I had to use a cable i got from a store. Try to put it in download mode and plugging it into the wall before your computer.
Sent from my SCH-I500 using xda app-developers app
The older androids are much easier to brick, the newer ones have more sophisticated bootloaders and other controls to make it less likely to brick. By the time you're hard-bricked, I've seen recovery from there but it's not looking great. You'd probably need some hardware based solution like jtag or the unbrickable. Check my post a few days ago about a really bad experience with that -- don't make my mistakes.
Thanks for the replies. I have a couple other cables, so I'll give them a try and also try dl mode in wall before the computer. I probably won't buy another cable since I'm due for an upgrade in a couple months and am surviving with a continuum (yikes!).
@ yunoworkandroid So much for the unbrickable fascinate, right? lol
If not, why not? Go do it. I ask because it seems lately a ton of threads are getting dirtied up with people and issues with firmware..and one thing a lot of them have in common is S-On..so I ask, why?
Little tech skill, no confidence
om4 said:
Little tech skill, no confidence
Click to expand...
Click to collapse
This is what I first thought..but, anyone in a rom thread has at least HTC Dev unlocked and flashed a recovery via fastboot. No more skill is required to S-Off. I think folks might be afraid of bricking? So I guess that would also raise the question, of all the folks who have S-OFf, how many bricked in the attempt? I bet not many actually hard bricked with no fix.
It so doesn't take much skill to watch a YouTube video and follow along. But throw in the word Linux and most users will cower in fear lol
I'm s-off. I can tell you why most people who are s-on are(I see it over and over again on forums with people questioning obtaining s-off).....because of the list of official requirements for Dirty Racun/Lazy Panda. I know this because I just went through it 2 weeks ago. A lot of people are on Win 7 64 bit and do not want to go through the hassle of creating a boot disk/usb drive for 32 bit or Ubuntu. I myself tried the Ubuntu method but not having ever used that OS I could not figure out opening a terminal within a folder LOL. Luckily my work PC is Win 7 32 bit and I have free time during the day. Sure some people have gotten away with using Win 7 64-bit anyway, but when the creator of the program is telling you if you do that they won't offer any help, it's very off putting. Another weird requirement that snagged me by overlooking it while mid install is the SD card size. Luckily I had an old 2gb card nearby. If I did not I would probably not go out of my way to buy an sd card to just obtain s-off. So in essence having requirements that IMO are outdated compared to what A LOT of people are running these days is why. That said I truly appreciate the work put in for giving us the ability to flash radios.
I am S-OFF. I didn't think I could do it. It's my first android device ever, and I've never rooted. I am no expert when it comes to computers, but I am good at following directions and doing research. I didn't know a lick about linux till I got this device and started doing some research. I found a handy rooting guide online which took step by step from initial unlocking to S-Off using DiryRacun and BabyRacun. I followed it and didn't have one issue doing it. I even used Windows 7 64bit to do it, not 32bit as recommended
I will say that it requires careful reading and each step has to be followed patiently, but its quite doable.
om4 said:
It so doesn't take much skill to watch a YouTube video and follow along. But throw in the word Linux and most users will cower in fear lol
Click to expand...
Click to collapse
I think maybe you hit the nail on the head in regards to the linux aspect. It's just my opinion that the headaches that can arise from being S-On can be far worse than the small effort to s-off. Even if you need to create a bootable Ubuntu CD and learn how to open a terminal in linux (ctrl, alt, T).
Open terminal - ctrl+alt+t
Enable temporary superuser permissions - sudo "account password" ex sudo reboot (press enter, type password)
List structure (directory) - ls
Change directory - cd /"folder or directory structure" ex. From home to desktop "cd Desktop" (same directory) ex. "cd /home/videos/TV show" (outside current directory)
Move up a level - cd ..
Fastboot and adb commands are run with ./ ex ./fastboot reboot
Pretty much all distributions have a terminal commands list packed into the help files these days. Some differ but they all perform the same functions.
Funny. I'm s-off. never used ubuntu before in my life. I was able to make a live CD and go s-off with NO PROBLEM. I was able to open a terminal and cd to the right directory. Untar works EXACTLY like unzip. I really don't see a problem for people that insist on rolling the dice and using win 7 64. it took me exactly 1 minute to make a bootable CD. again NO UBUNTU or LINUX experience prior to this at all. Stop fearing the Linux people.
I'm s-on and the reason I'm not s-off is because of the stupid 2-16gb sd card req.
I'm using a SanDisk 64gb so no.
Sent from my EVO using xda premium
rawintellect said:
Funny. I'm s-off. never used ubuntu before in my life. I was able to make a live CD and go s-off with NO PROBLEM. I was able to open a terminal and cd to the right directory. Untar works EXACTLY like unzip. I really don't see a problem for people that insist on rolling the dice and using win 7 64. it took me exactly 1 minute to make a bootable CD. again NO UBUNTU or LINUX experience prior to this at all. Stop fearing the Linux people.
Click to expand...
Click to collapse
This is exactly what I'm getting at. No offense to those that are S-on, but it's just so easy to S-off and it seems by the numbers more problems arise that are difficult to fix while S-On..more work even. Just to update firmware gotta relock, take an OTA, unlock, reroot, etc..instead of just flashing an update zip. Or Rom flashing requiring extra steps to write the kernel if the developer doesn't implement the script to do it for you. Just seems like time and effort wasted when an hour of time can take care of it.
Sent from my EVO using Tapatalk 2
raclimja said:
I'm s-on and the reason I'm not s-off is because of the stupid 2-16gb sd card req.
I'm using a SanDisk 64gb so no.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
4 bucks. amazon. :/
http://www.amazon.com/Sandisk-2GB-Micro-Sd-Card/dp/B000N3LL02
I'm more of a visual learner. If someone made a step by step video on YouTube I would have S-OFFed a while ago. Also if my windows laptop was 32bit I would have also and yes I know people say 64bit works but I'm not a gambler.
Sent from my Blazing fast LTEvo!
mulhiny said:
This is what I first thought..but, anyone in a rom thread has at least HTC Dev unlocked and flashed a recovery via fastboot. No more skill is required to S-Off. I think folks might be afraid of bricking? So I guess that would also raise the question, of all the folks who have S-OFf, how many bricked in the attempt? I bet not many actually hard bricked with no fix.
Click to expand...
Click to collapse
I bricked the **** out of my phone first try around lol
Dont use usb 3.0
Sent from my EVO using xda app-developers app
jesuscash said:
I bricked the **** out of my phone first try around lol
Dont use usb 3.0
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Usb 3.0 had the blue on the inside right? I think my laptop has 2-3.0 & 1-2.0.
Sent from my Blazing fast LTEvo!
jesuscash said:
I bricked the **** out of my phone first try around lol
Dont use usb 3.0
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You say first try, so I'm guessing you s-off'd your replacement without issue? Probably using the correct usb port this time? Lol.
Sent from my EVO using Tapatalk 2
S-OFF - LazyPanda I bricked my phone the first time also but used the unbricker from unlimited.io which was ubuntu (no windows option for that). I had zero experiance with Linux it took about 5 minutes to unbrick my phone then ran LazyPanda again from my PC :victory:
bigdaddy619 said:
S-OFF - LazyPanda I bricked my phone the first time also but used the unbricker from unlimited.io which was ubuntu (no windows option for that). I had zero experiance with Linux it took about 5 minutes to unbrick my phone then ran LazyPanda again from my PC :victory:
Click to expand...
Click to collapse
Bigdaddy, did you brick due to something wrong in the method or did you miss something? Just curious.
Sent from my EVO using Tapatalk 2
mulhiny said:
Bigdaddy, did you brick due to something wrong in the method or did you miss something? Just curious.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I didn't have all my ducks in a line it's been a while so don't remember the exact cause there were suggested methods within the LP thread 3-4 posts that broke it down step by step I probably just missed one of the steps. Once unbricked I went to those posts and and made sure everything was working before trying again and it took about 3 minutes and bingo done
mulhiny said:
You say first try, so I'm guessing you s-off'd your replacement without issue? Probably using the correct usb port this time? Lol.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I was able to unbrick via racunhunter lol
took about 3 minutes to unbrick.
Long story short, using 2 different computer, 2 different USB cables, and several different USB ports, I cannot get either casual or odin to detect my phone. The computers themselves recognize it, but neither program will. I have spent hiurs going through threads and try whatever I have found but nothing has changed this. Please help, I'll answer any questions you have regarding this as I'm sure more info is neccessary, but at this point I just don't know what to do and am about to go back to my DNA if I can't get this straightened out. Thanks for any help/suggestions.
jewboy69 said:
Long story short, using 2 different computer, 2 different USB cables, and several different USB ports, I cannot get either casual or odin to detect my phone. The computers themselves recognize it, but neither program will. I have spent hiurs going through threads and try whatever I have found but nothing has changed this. Please help, I'll answer any questions you have regarding this as I'm sure more info is neccessary, but at this point I just don't know what to do and am about to go back to my DNA if I can't get this straightened out. Thanks for any help/suggestions.
Click to expand...
Click to collapse
Have you installed Kies? If so try uninstalling it and then redownloading and reinstalling. Thats what worked for my friend with his N2, maybe it'll help you.
Alsoif you're on WinXP it Casual wont work from what I have gathered.
Sent from my SCH-I605 using XDA Premium HD app
nope...
I have uninstalled/reinstalled kies, and the 2 computers I've used are running win7/8. Thanks but it's gotta be something else.
shangrila500 said:
Have you installed Kies? If so try uninstalling it and then redownloading and reinstalling. Thats what worked for my friend with his N2, maybe it'll help you.
Alsoif you're on WinXP it Casual wont work from what I have gathered.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
jewboy69 said:
I have uninstalled/reinstalled kies, and the 2 computers I've used are running win7/8. Thanks but it's gotta be something else.
Click to expand...
Click to collapse
Some computers just don't play well with Odin, Casual, Hemidall, and/or the Note 2. On my work computer I've done everything under the sun to get it going with Casual, and it just fails on one item or another. However a second computer at work and one of my home computers work like a champ. You might just have two bummer machines for the process. When it does work, it is a thing of beauty.
If I were you I wouldn't go back to the DNA. I really love that phone, but I haven't once regretted switching to the Note 2. Once you get used to the size, things like the stellar battery life and availability of customization options come into focus.
Sent via Note2 with XDA Premium
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
jparnell8839 said:
Ok, so please forgive me for this. I'm used to Samsung devices, and rooting/custom recovery is as simple as "Download this, flash through Odin, Easy as pie".
So I have my brother's P769. He had rooted it, but was unsure how to install CWM on it. Me, being completely ignorant of unlocking the bootloader, was able to get CWM on it and flash CM10.2. Which, of course, gave me the LG Security Error. Been stuck for many a day trying to get back to V20F_00. It doesn't help that there is ABSOLUTELY NO WAY to install the omap4 drivers in Windows 8.1, and reserving USB devices to Virtualbox is a pain in the (insert desired graphical descriptor here:_______).
So, I am just trying to clarify the steps to get my brother the CyanogenMod he so desires.
From Stock:
Root device
Unlock Bootloader
Install CWM
Flash CM from CWM
Is this a correct assumption?
Click to expand...
Click to collapse
Welcome JP,getting a break from the Blaze. I've had this beast for a week and I'm ready to crush the phone. So far I've been able to root and remove T-Mobile bloatware.
I've tried to unlock the boot loader many times and no luck. I've read thru the guides and the result is the same.
I sitting patiently to see if the devs can solve the mystery of the bootloader. I can't wait for the day so I can leave the stock Rom. Hope all is well
Sent from my LG-P769 using xda app-developers app
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
thehritzinator said:
I've had this phone almost a year. As far as the unlocking bootloader goes, it seems like some p769s just aren't unlockable, no matter what method used. Mine is one of those. It may never be able to be unlocked. Just throwing that out there.
THIS link will show you the most common way to unlock the bootloader. It has simple directions and even a video. The only problem is that it doesn't work on some devices, such as mine, so just be wary. And many people in the thread have managed to get results by modifying the instructions, but others have not had any luck.
Good luck! Hope yours works
Click to expand...
Click to collapse
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
LaDY Vengeance said:
Welcome to the dark pits of xda hell....LMAO! :sly:
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol thanks! I'm starting to believe it
flyers00 said:
This is as bad as when I had the Cliq XT , that was a beast as well. That was a replacement phone as well. Hopefully the devs can crack it
Click to expand...
Click to collapse
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
jparnell8839 said:
That's the link I found, and thought "There's no way it's that complicated!"
HTC uses a dev key. I don't remember Moto's method, but it was simple. Samsung is ridiculously simple. Why is LG so complicated? This has only re-enforced my idea of "Never get an LG"
Lol thanks! I'm starting to believe it
This is the worst phone, as far as modding goes, I've ever seen. I haven't experienced many devices, but geez. Heck, hacking a SGS2 i777 with a faulty USB board was easier than this, and I couldn't even access recovery without ADB commands (because it thought a USB cable was plugged in even when it wasn't, was going to download mode) and couldn't enable ADB (because it thought a cable was plugged). I had to use SQLite hacks to force ADB to enable.
However, I've never let anything stop me before. I'm a world-champion Googler, and so I will crack this will probably take me a while, but meh.
Click to expand...
Click to collapse
Congrats on coming into teh darkside. I know you are world class Googler and if you find something or come up with something, I am in to help the cause. I was a guinea pig with the Blaze so why not here. Good luck with your Google skills