So it seems my phone is not connecting to 4g.... I have fresh 3.4 and stock kernel.. I did a complete dalvik clear and wipe and installed 3.4 and then the radio that's listed.. I get that same message when trying to connect to 4g as my subject says... it says connecting to sprint for about 3 sec. Then right away disconnecting... my dad's phone with the same rom is connecting just fine... anyone have ideas? Thanks
Sent from my PC36100 using XDA App
Uninstall switchpro, or if you want to keep it, use only that to turn 4g on. Once you turn it on with switchpro, you can turn it off and back on through settings again.
If you don't have switchpro installed, ignore the above.
Sent from my blah blah blah blah
dude, if fachadick's suggestion doesnt work, you are screwed. if you have a backup made with AMON RA RECOVERY (clockwork recovery wont do ****) that you made before flashing the radio, wipe and restore. flashing radios has been known to totally erase or mess with your rsa private keys. without these, there is no possible way to connenct to 4g. this is like your password to your bank account, and you just forgot it. either tough it out and help the other rsa-losers test, or return your evo. only two options. there have been no solutions found besides restoring a working backup (it only successfully backsup the wimax about half the time) from AMON RA RECOVERY ONLY and hope for the best. that sucks
dk
Dude don't even tell me that.. first off this is the first time I'm hearing about this... why wouldn't there be a major warning about this? And I'm not talking about some.message everyone says with their Roms... I'm talking about a message everywhere that says there's a chance you will lose 4g forever installing Roms or radios, I mean who in their right.mind would evvveeeerrrrr take a chance.like that? I mean would you? The whole point of this phone is the 4g....
BTW I do have switch pro, and tried to toggle the 4g and still no luck....
dkdude36 said:
dude, if fachadick's suggestion doesnt work, you are screwed. if you have a backup made with AMON RA RECOVERY (clockwork recovery wont do ****) that you made before flashing the radio, wipe and restore. flashing radios has been known to totally erase or mess with your rsa private keys. without these, there is no possible way to connenct to 4g. this is like your password to your bank account, and you just forgot it. either tough it out and help the other rsa-losers test, or return your evo. only two options. there have been no solutions found besides restoring a working backup (it only successfully backsup the wimax about half the time) from AMON RA RECOVERY ONLY and hope for the best. that sucks
dk
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Its official... I unistalled the pro widget and saamme thing.. I cannot express how angry I am right now.. this is pissing.me off so bad.. and againn I ask, who in their right.mind would ever mess with Rome and radios if it PERMANENTLY breaks a phone?
I really need someone to help me figure out my options .. should I smash it on the ground and get a refurbished? Should I revert back to stock and try and return it? Very confused right now
Sent from my PC36100 using XDA App
fastfed said:
Its official... I unistalled the pro widget and saamme thing.. I cannot express how angry I am right now.. this is pissing.me off so bad.. and againn I ask, who in their right.mind would ever mess with Rome and radios if it PERMANENTLY breaks a phone?
I really need someone to help me figure out my options .. should I smash it on the ground and get a refurbished? Should I revert back to stock and try and return it? Very confused right now
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It's only updating the radio that has a chance of breaking wimax, not roms, so did you update your radio?
I'm on the phone now, or I'd point you to the link, but do a search for rsa keys. What you're looking for are some commands to plug into adb or terminal emulator to determine weather your keys are still there. It's something like
grep RSA /dev/mtd/mtd0
but I know I'm missing a part of it. If it says begin rsa private key and end rsa private key at the end of the data it spits out at you, you're still good. If not, hopefully you have an amonra backup stashed away somewhere.
Also, did you reboot after uninstalling switchpro?
Sent from my blah blah blah blah
Yes I updated the radio... don't you all do that too? If you look at freshs rom there is a radio thatsbsupposed to go with it...
Sent from my PC36100 using XDA App
Wimax radios can break your wimax. Not the other ones. Its somethin that randomly happens. I dont mess with them.
8pen from my supersonic on the xda app.
fastfed said:
Yes I updated the radio... don't you all do that too? If you look at freshs rom there is a radio thatsbsupposed to go with it...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Search xda for vender tree.xml in the evo forums. Sometimes this has issues. I had the same problem and needed to delete the tree.XML. doing this refreshes a new one on reboot. Search foe it cause I'm on my phone. If you didn't use unrevoked way back when its not necessarily broken. Idk why all these people are telling you that without doing further investigations
I have updated every single wimax radio with no issues. These radios flash with ruu s when you're not rooted so in theory there should be no problems.
ok I tried getting the terminal emulator, and I put the code in that I found
cat /dev/mtd/mtd0 | grep RSA
but it comes back as denied, or error..
I don't even wanna mess with SDK package for ADB you mentioned..
any other way to test?
THANKS
I've been asking people for ages what my problem is with 4G. I rooted, and started flashing ROM's immediately, and can only get 4G to work on my original backup with AMON RA...
There has to be a way to tell if it's messed up or not, and what our options are.
barnacles10 said:
Search xda for vender tree.xml in the evo forums. Sometimes this has issues. I had the same problem and needed to delete the tree.XML. doing this refreshes a new one on reboot. Search foe it cause I'm on my phone. If you didn't use unrevoked way back when its not necessarily broken. Idk why all these people are telling you that without doing further investigations
I have updated every single wimax radio with no issues. These radios flash with ruu s when you're not rooted so in theory there should be no problems.
Click to expand...
Click to collapse
LOL I was at a hockey game, FREAKING OUT reading that..
I never messed with ANY radio except the one thats on Fresh's main post..
I did try kings#11 kernel, and when I updated to fresh 3.4, I cleared cache, Cleared dalvik, did a complete wipe, installed 3.4, then installed the radio..
THAT was it..
I am trying to do this test deal, but I seem to not be doing it right.
fastfed said:
LOL I was at a hockey game, FREAKING OUT reading that..
I never messed with ANY radio except the one thats on Fresh's main post..
I did try kings#11 kernel, and when I updated to fresh 3.4, I cleared cache, Cleared dalvik, did a complete wipe, installed 3.4, then installed the radio..
THAT was it..
I am trying to do this test deal, but I seem to not be doing it right.
Click to expand...
Click to collapse
All the radios I use are fresh posted too. Like I said. Search xda for the vender.tree.xml 4g issue and see if that fixes it for you
Your gonna have to use adb to get some of this done.
8pen from my supersonic on the xda app.
i actually remembered the code right, but forgot the superuser part - if your using terminal emulator, type su and hit enter first so you get the #, then type
grep RSA /dev/mtd/mtd0
you should get the begin private key and end private key at the end (I think you may need to have busybox for this to work though)
Barnacles is right though - there was a lot of talk that it was the (wimax?) radios breaking 4g, But I don't know that it was ever proven - sorry about the hearsay. I just knew it didn't happen when flashing a rom.
I think what he's advising is using root explorer to get to /data/misc/wimax. In that folder you'll see a file that looks like xxxxxxxxxxxxxx.tree.xml - set root explorer to mount r/w and rename that file to xxxxxxxxxxxxxx.tree.xml.old (just in case you need it later for any reason). It will rebuild the xml when you reboot and turn on wimax again. I thought this only helped for wimax that was stuck in scanning though, unless he's referring to something else...
Sitting in my car 5 miles from where I live with my dads phone in hand.and.messing with.my phone. He has 4g up and running.. I just did a complete reset. Earased everything reinstalled. Fresh 3.4 and still nothing.. I just renamed the tree.XML to old.. my phone is resetting.now.. waiting......nope same ffffiiiing thing... wtf this reallllly blows
Sent from my PC36100 using XDA App
And now the market keeps force closing.. took me forever to get the terminal emulator.. I put in that key and.I got a bunch of stuff that says RSA-request. Reply.reject a bunch of times... I'm losing it with this pos phone
Sent from my PC36100 using XDA App
in the terminal emulater type
su
grep RSA /dev/mtd/mtd0
if it says a bunch of lines with
BEGIN RSA PRIVATE KEY
END RSA PRIVATE KEY
(there are some wired dashes and stuff, but you get the idea)
at the end, you are safe, and need to mess with the MAC address key thing. if not, then either get a new evo (sprint customer service ) or join the XDA RSA KEY LOSS TESTERS!!! and try to find a permanent solution.
there was almost a wave of people losing thier keys, in which clockworkmod was baisically banned for not backing up wimax.img. this is y u should ALWAYS USE AMON. i hope this even distantly helps. there are a few threads on how to fix a broken MAC (only if your command outputs BEGIN RSA... END RSA... STUFF)
DK
Who knows anymore.. I'm tired and have a headache.. its so depressing when we all try so hard with our phones.. a passion to have fun with.. I must of done everything from a.to z with.my old windows.phone and.never once broke something permanently... thanks all for the help.. going to bed now ;(
Sent from my PC36100 using XDA App
See I can't even sleep that's how.much this **** pisses me off ... here is a screen shot of the terminal program
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PC36100 using XDA App
Related
Hey guys so after flashing a rooted 3.29 ROM and the latest WiMax/Radio/PRI, my 4G is not working. It will turn on fine and then say Connecting to Sprint then Authenticating to Sprint and then it goes back to Scanning. It should connect fine because I'm in an area with GREAT 4Gband it worked fine here before updating all that ****. If anyone can help that'd be awesome as I love my 4G. I'm no noob so it's especially frustrating but I can imagine people are having similar issues. Thanks in advance.
You know what? I saw this same problem happening over in Freshhh's thread and some people are reporting that updating their PRL and profile fixed the problem. Maybe give that a shot and see if it works?
beatblaster said:
You know what? I saw this same problem happening over in Freshhh's thread and some people are reporting that updating their PRL and profile fixed the problem. Maybe give that a shot and see if it works?
Click to expand...
Click to collapse
I tried that but no dice. Basically it looks like it's going to connect but it doesn't - it starts with "Connecting to Sprint" then goes to "Authenticating to Sprint," then "Disconnecting," and finally "Scanning."
I found out that I had a bad MAC address so I fixed it, but it still isn't working. I'm so frustrated at this point.
Your RSA Key has been altered...only know fix is finding one of YOUR backups of wimax.img in /sdcard/nandroid...sorry
snandlal said:
Your RSA Key has been altered...only know fix is finding one of YOUR backups of wimax.img in /sdcard/nandroid...sorry
Click to expand...
Click to collapse
What do I do with the wimax.img from one of my nandroids? I have a nandroid of when it was working (I think)
I found this post that seems to show you whether you're super screwed or not. I just realized I'm having the same problem now too with 4G. Unfortunately I didn't realize it was happening last Saturday when I was in a 4G area. Hmmm..... I'm gonna have to make time to go back to my parent's house and try to fix this. Anyway, if I come across something I'll let you know Mack.
Mack,
Have you tried to flash back to RUU 1.47 and going back to stock? I've read here (post 7) that that might do the trick. I was thinking the same thing as well but I'm looking for some proof that it's gonna work. What really sucks is that I actually have to go to a 4G area tonight but I got business there and can't work on the phone as the same time. Talk about being tempted to blow off responsibilities.....
beatblaster said:
Mack,
Have you tried to flash back to RUU 1.47 and going back to stock? I've read here (post 7) that that might do the trick. I was thinking the same thing as well but I'm looking for some proof that it's gonna work. What really sucks is that I actually have to go to a 4G area tonight but I got business there and can't work on the phone as the same time. Talk about being tempted to blow off responsibilities.....
Click to expand...
Click to collapse
I hear you on that - I've actually heard that once you lose wimax keys then they're gone, nothing you can do really =/ I'm still investigating
Take your wimax.img and flash it in a PC36IMG.ZIP and let it flash. Guaranteed wimax will work if your rsa keys are in it and you mac is correct
AmonRA recovery seems to be key to preventing borked 4G...if you have any nandroids that you made while 4G was working w/ AmonRA version 1.8 recovery, you can flash it and it will restore your RSA certs.
4G fixed, flashed an old nandroid wimax.img
snandlal said:
Take your wimax.img and flash it in a PC36IMG.ZIP and let it flash. Guaranteed wimax will work if your rsa keys are in it and you mac is correct
Click to expand...
Click to collapse
Thank you for that little tid bit.
After flashing the newest radio and pri my 4g got borked. It would connect and then immediately drop. After a PRL update and reboot it wouldn't even connect anymore, just scan and then turn off. I went to go restore from an earlier nandroid only to find out i had some bad checksums on the two recent nandroids I had made with 1.8 and therefore it wouldn't restore. Arg! Even though I had 4 other nandroids, they were made with 1.7 and I'm guessing that wimax support wasn't added till 1.8. Then I found here that I could just take the individual wimax.img file out, move it to a PC36IMG.zip file and then flash using bootloader. That fixed it! 4G is working like a champ again.
Many thanks to you and everyone whose posts I've been scanning for a glimmer of hope the past 5 hours. Weeeeee!
Well I found time to work on my 4g issues while I was in northwest indiana today and all I did was flash to the newest fresh rom and my 4g came back. Gotta be honest though - I was a little terrified there for a second. RA recovery FTW baby!
Sent from my PC36100 using XDA App
snandlal said:
Take your wimax.img and flash it in a PC36IMG.ZIP and let it flash. Guaranteed wimax will work if your rsa keys are in it and you mac is correct
Click to expand...
Click to collapse
Just found out that my RSA keys are gone...so I'm ****ed. I do have insurance but really don't want to pay the $100 deductible. I may just have to try to trade my Evo for an Epic now
AmonRA FTW as usual!
Guys... I'm having the same issue but it seems that i have also lost the ability for the phone/GPS to find its location.
Also, my nandroid backup does not have a wimax.img
Can anybody please shed some light?
EVO 2.2 stock Rom rooted with Unrevoked
Ok... just did the prl update and got GPS/location working again.... I'll post updates for 4g soon.
my 4g got borked too! not sure where to go...my mac address is missed up though going to try and fix that and see if i can get 4g back anybody else recommend anything?
Yeah... I could not get it fixed. Luckily I had a nandroid backup so I put it back and now everything is back to normal...except I still have the old PRI and radio :-(
evo4ger said:
my 4g got borked too! not sure where to go...my mac address is missed up though going to try and fix that and see if i can get 4g back anybody else recommend anything?
Click to expand...
Click to collapse
If you don't have Amon and don't have a nandroid on Amon then you're probably **** out of luck - at least that was the case with me. I'm waiting on my new Evo replacement to come in the mail.
evo4ger said:
my 4g got borked too! not sure where to go...my mac address is missed up though going to try and fix that and see if i can get 4g back anybody else recommend anything?
Click to expand...
Click to collapse
i had to fix my wimax mac address and it's fixed and sticking to the right mac, but i still can't get 4g, now trying to flash to stock 1.47... ugh
Keri
My power button seems to be stuck. I'll push it and instead of powering off the screen, it acts like a long press and goes to the power off menu. I've noticed it with any of the roms I'm using too. Any ideas?
Sent from my PC36100 using XDA App
It's also not working when the screen is in sleep mode. Takes like seven presses for the unlock screen to show
Sent from my PC36100 using XDA App
Your power button is bad need to take it to sprint. Hardware issue fixed 0004 and 0003
I was afraid of that. So when the screen is sleeping it works fine now. Trying to get an awake screen to sleep is nigh impossible. Am I just SOL and have to unroot and take it into a service center?
Sent from my PC36100 using XDA App
richdogg112 said:
I was afraid of that. So when the screen is sleeping it works fine now. Trying to get an awake screen to sleep is nigh impossible. Am I just SOL and have to unroot and take it into a service center?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Pretty much just don't try to fix it your self other wise you will void your warranty. I never had that issue just a squeaky button on the past. I have a brand new evo right now tho no problems.
What are your radios and prl? Did you mess with the latest leaked radios ? If not then it is a power button issue not hard to unroot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm testing out MIUI and checking how to update my PRL. But that's the current stuff. Thanks for your help by the way. Just did some research and I'll have to flash back to a sense based rom to update it which won't be hard at all to test that
Sent from my PC36100 using XDA App
I have used miui before cool rom. Looks like your using old prl. Update that. See if that fixes it what recovery are u using. Try amon 2.3
Amon is sweet for me I never have issues using it. Wipes everything correctly .
Using clockwork right now. I'll update the prl and get amon. I'll keep you posted on the result. In Ryder's eternal prophecy thread I found a zip that I keep on my sd that deletes everything so I run that too along with clockworks.
Sent from my PC36100 using XDA App
richdogg112 said:
Using clockwork right now. I'll update the prl and get amon. I'll keep you posted on the result
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My guide has the link for it.
If all still fails I would try the latest Sprint lovers rom it updates everything for you radios and such. If still a no go then your button is messed up.
richdogg112 said:
Using clockwork right now. I'll update the prl and get amon. I'll keep you posted on the result. In Ryder's eternal prophecy thread I found a zip that I keep on my sd that deletes everything so I run that too along with clockworks.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No need for it amon does it for you when you click on wipe scroll down on each part you wanna wipe and it will do it. No need for a script.
So I'm in clockwork (yes yes, I know, I'm about to switch over in three seconds if that's what it takes) and when I try to install the radio file from my sd it's giving me an installation aborted message.
"Amend scripting is no longer supported. Please switch to Edify scripting to create working update zip packages."
I have no idea what that means...
Update, until I find the time to take my phone in, I downloaded "No lock" which lets me turn the screen on from sleep mode with my volume buttons, then I downloaded "Screen off and Lock" which puts a command in my notification menu that if I click on it, it will make the phone sleep
K all you need is amon 2.3 rename it PC36IMG.ZIP boot into bootloader and it will install . To update prl just need a sense rom. Hope you get it fixed
Ok so I've unrooted and taking my phone in tomorrow. Should I wipe my SD too? I have my clockwork folder with backed up roms and other things that point to me having rooted.
richdogg112 said:
Ok so I've unrooted and taking my phone in tomorrow. Should I wipe my SD too? I have my clockwork folder with backed up roms and other things that point to me having rooted.
Click to expand...
Click to collapse
To be on the safe side i would tranfer everything to the computer. Then wipe the sd just in case.
Sent from My Nissan S14
I used Astro to go through and delete the folders. Didn't have time before work to copy them all over. I'll keep my fingers crossed
richdogg112 said:
I used Astro to go through and delete the folders. Didn't have time before work to copy them all over. I'll keep my fingers crossed
Click to expand...
Click to collapse
Next time just take it out, they dont need. (I used to be a tech)
I was looking for a spare micro SD around my place but I couldn't find one in time. Tech has my phone right now I'm about to go check on it in about an hour. Thanks for the heads up for next time though.
Follow up:
Either I deleted all signs or they didn't care. Either way they had to order another Evo and it will be here in a couple days. Thanks again for all the replies and can't wait to get my other Evo so I can root again. This standard look is for the birds.
Hey guys,
my name is Josh and I've looked online all over for a solution, if you happen to have one please notify me asap becaues im stumped!
Anyways, heres the deal.
A while back I installed a ROM im not sure which one it was but it was one i had to flash a new Radio & Wimax. With that being said, I didnt really realize it until a day late but my 4G was stuck on "Toggling still in progess, please wait..." i ignored it thinking it'd go away eventually or after a reboot and new rom etc.
3 roms later... still no difference. right away i know it was not the rom or a hardware issue (considering i got this phone less then 2-3 months ago and its in MINT condition.
*getting to the point. I've looked online hearing about all these RSA keys getting messed up from flashing radios improperly, (proof that im a total FROOB) So i downloaded the RSA Key tester from the market place and it tells me i have RSA keys, now im not sure if this tell me they are working but they obviously arent. after a ton of data resets, rom reflashes, etc. my 4g now is not stuck turning on or toggling in process, but is now going from "turning on" to "unable to start 4g" it doesnt even search for a 4g signal or show anything else that ive showed. im willing to do whatever it takes to fix this. ive tried doing a back up of my RSA keys and i used the terminal emulator to do so. i have the OEM file but not sure what to do now.
Another thing that stumps me is that i have installed the same rom on my co-workers phones without flashing the new radio & wimax like the rom told me to do, and their phones work flawlessly.
Lastly, I am new to these forums (obviously first post) Do you guys know of anyway to fix this 4G epidemic? If i have stated any above information incorrectly please inform me and it wont happen again.
Thanks in advance for any type of info guys.
Install terminal from the market.
Launch.
Type su
Press enter
Type wimax_mtd
Press enter
Does it load? If it loads then it'll tell you the wimax version. Don't copy and post it here.
Otherwise, it'll give you an issue that it can't load it
Sent from my PC36100
Thanks for the quick reply!
It gave me an ERROR reading the WiMAX partition
and was stopped after checking the "Firmware version () ..............."
I also forgot to add this in, I was fed up with this earlier i was working on this for like 5 hours and i found the "format wimax" option in the clockworkmod recovery and i hit it, and at the reboot i got stuck in a bootloop and had to reset everything, i dont know if this did anything to my Wimax.
When you "format wimax", doesn't it wipe your wimax partition?
I could be wrong about that, since I try to not mess with wimax stuff.
Before I read your last post, I was going to suggest flashing an older wimax version. Run the key checker app again and see if it gives you the same outcome. If it says that your keys are missing, see if you can find a nandroid from before you had the problems that includes a wimax.img. If you have one, restore it.
If the problem persists after restoring, then try flashing an older wimax version.
Sent from my PC36100 using Tapatalk
jasmnjosh said:
Thanks for the quick reply!
It gave me an ERROR reading the WiMAX partition
and was stopped after checking the "Firmware version () ..............."
I also forgot to add this in, I was fed up with this earlier i was working on this for like 5 hours and i found the "format wimax" option in the clockworkmod recovery and i hit it, and at the reboot i got stuck in a bootloop and had to reset everything, i dont know if this did anything to my Wimax.
Click to expand...
Click to collapse
Try reflashing the WIMAX piece and download here. Here's the thread.
Boot to recovery and flash the file....MAKE SURE THAT YOU HAVE A LOT BATTERY LIFE LEFT AND DO NOT PULL THE BATTERY. LET IT DO IT'S THING.
Then reboot. Run the terminal app and commands and tell us what happens. By the way, I'm not yelling, I just wanted to emphasize it
---------- Post added at 04:23 AM ---------- Previous post was at 04:21 AM ----------
plainjane said:
When you "format wimax", doesn't it wipe your wimax partition?
I could be wrong about that, since I try to not mess with wimax stuff.
Before I read your last post, I was going to suggest flashing an older wimax version. Run the key checker app again and see if it gives you the same outcome. If it says that your keys are missing, see if you can find a nandroid from before you had the problems that includes a wimax.img. If you have one, restore it.
If the problem persists after restoring, then try flashing an older wimax version.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar problem with another Evo and the check version just crapped out. I flashed the WIMAX and it worked fine right after. Hopefully the same happens to him.
@spyd312
Okay, is it alright to do the flash while the phone is plugged in because im in the yellow for battery :X
Another thing is, should i update my profile before i flash the wimax or after? or should i not do it at all?
plainjane said:
When you "format wimax", doesn't it wipe your wimax partition?
I could be wrong about that, since I try to not mess with wimax stuff.
Before I read your last post, I was going to suggest flashing an older wimax version. Run the key checker app again and see if it gives you the same outcome. If it says that your keys are missing, see if you can find a nandroid from before you had the problems that includes a wimax.img. If you have one, restore it.
If the problem persists after restoring, then try flashing an older wimax version.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Luckily i have about 3 backups before the Wimax ever messed up and of course before i "formatted wimax" It could wipe the Wimax partition because thats what was missing when ran the check in the terminal but i will boot my phone up and check for the RSA keys again, and if they're not found ill try flashing the Wimax and see what goes through then.
*EDIT: Ouchh my RSA keys are not found. Should i do a nand restore to before i formatted my wimax or just flash the wimax now? im torn between 3 steps.
[ ] Flash Wimax now, w/ Missing RSA Keys.
[ ] Nand Restore then flash Wimax
[ ] Nand Restore / Update Profile then Flash Wimax
Which one would you guys recommend? Again sorry I have made this so difficult. I R NUB
*2ND EDIT: My RSA keys were present before i formatted my Wimax.
Okay, is it alright to do the flash while the phone is plugged in because im in the yellow for battery :X
Wait until you're half-way because it won't charge in recovery.
Another thing is, should i update my profile before i flash the wimax or after? or should i not do it at all?
No need.
Luckily i have about 3 backups before the Wimax ever messed up and of course before i "formatted wimax" It could wipe the Wimax partition because thats what was missing when ran the check in the terminal but i will boot my phone up and check for the RSA keys again, and they're not found ill try flashing the Wimax and see what goes through then [/QUOTE]
I don't think you lost your keys. I think your wimax is just temporarily hosed. Get that sucker juiced and hopefully it works out.
Sent from my PC36100
spyd312 said:
Okay, is it alright to do the flash while the phone is plugged in because im in the yellow for battery :X
Wait until you're half-way because it won't charge in recovery.
Another thing is, should i update my profile before i flash the wimax or after? or should i not do it at all?
No need.
Luckily i have about 3 backups before the Wimax ever messed up and of course before i "formatted wimax" It could wipe the Wimax partition because thats what was missing when ran the check in the terminal but i will boot my phone up and check for the RSA keys again, and they're not found ill try flashing the Wimax and see what goes through then
Click to expand...
Click to collapse
I don't think you lost your keys. I think your wimax is just temporarily hosed. Get that sucker juiced and hopefully it works out.
Sent from my PC36100[/QUOTE]
After Flashing the new Wimax my 4G is now scanning and connected
Too bad the 4G signal in my bed is 1 bar haha. Thanks so much guys I really appreciate it. Oh and before I forget :/ The Wimax checker still says I am missing my RSA keys. I still have my back up of my rsa_OEM is there a way to flash that on here somehow?
*EDIT: Bad signal right now being said, i went outside to test if it'd actually connect, but it just Scans and Scans until says 4G is disconnected. Hmm any clue?
jasmnjosh said:
I don't think you lost your keys. I think your wimax is just temporarily hosed. Get that sucker juiced and hopefully it works out.
Sent from my PC36100
Click to expand...
Click to collapse
After Flashing the new Wimax my 4G is now scanning and connected
Too bad the 4G signal in my bed is 1 bar haha. Thanks so much guys I really appreciate it. Oh and before I forget :/ The Wimax checker still says I am missing my RSA keys. I still have my back up of my rsa_OEM is there a way to flash that on here somehow?[/QUOTE]
That's great dude. That's weird how the checker is wrong lol. If it ain't broke, don't fix it. Please hit the Thanks.
Sent from my PC36100
What does it say when you use terminal?
Sent from my PC36100
Read my edit, 4G wont connect, just keeps Scanning till it Disconnects. Before disconnecting it will say Connecting to sprint.. then quickly Disconnect and start Scanning once more to then Disconnect again. And i know i get 4G inside my house and definitely in my city. Just not in my bed lol Any idea what this could be?
---------- Post added at 06:07 AM ---------- Previous post was at 06:03 AM ----------
Gives me a crap load of info, Everythings an OK, a Pass and Match. The Properties, Partition, Version, Tag are OK. Says total time was 1.6 seconds. Says "Dump all properties in Flash ....... OK"
I just saw your reply so I'm removing my comment
The info you got is good. That means you're not hosed. I don't know why you can't connect outside though
Sent from my PC36100
Should i try Updating my Profile, PRI or Radio? Or maybe reflash my rom? or maybe go back to stock RUU? I'm willing to do whatever it takes.
jasmnjosh said:
Should i try Updating my Profile, PRI or Radio? Or maybe reflash my rom? or maybe go back to stock RUU? I'm willing to do whatever it takes.
Click to expand...
Click to collapse
Try restoring to a backup when everything worked
Sent from my PC36100
Tried restoring everything and no luck man. =/ I have no idea what to do again lol
If the radio is successfully flashed and the wimax_mtd displays correctly, but you're still unable to connect, then I don't know what else you can try. If your nearest sprint store has 4G, then I would drive next to it and try it out. If it still doesn't work. Then hopefully you have warranty and state that you 4G doesn't work. You'll have to restore everything to S-on etc.
I do have warranty, but to go through that hassel is going to be a headache i just know it :/ I can do it by this weekend maybe. Im going to look online for a few solutions first. I know i can live without 4G but thats not a feature to go without =/ So theres no way to just completely set everything to default (wimax/radio/rsakeys)? i have a feeling if i find a way to get my Keys back it'll work
jasmnjosh said:
I do have warranty, but to go through that hassel is going to be a headache i just know it :/ I can do it by this weekend maybe. Im going to look online for a few solutions first. I know i can live without 4G but thats not a feature to go without =/ So theres no way to just completely set everything to default (wimax/radio/rsakeys)? i have a feeling if i find a way to get my Keys back it'll work
Click to expand...
Click to collapse
In your recovery folder (Clockwork or Nandroid), do you have a file called wimax? If not, then you should check other backups until you find one that does. Then restore that ROM. Hopefully you've been restoring from a backup that didn't have the wimax partition backed up.
You should try this too
Thread:
Link
Sent from my PC36100
Download wimax key checker from the market. If your keys are intact update profile with your 4 g on even though it is not connected.
Sent from my PC36100
So I am on my fourth ICS rom and haven't had any problems with a brick. I jumped on xda a today ans daw this http://www.xda-developers.com/android/determine-your-devices-hard-brick-risk-with-got-brickbug/
Now I download the app and it told me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now is this due to a brick bug or just people doing something stupid?
As long as you follow OP directions and flash from el26 cwm kernel, you will be OK.
Sent from my SPH-D710 using Tapatalk
I'm staying away until ics is an official release, but that's just me being safe than sorry.
I see you flashed Venums latest rom. I tried it out last night but just wasn't feeling it. Any time you flash anything there is a chance of a brick. Keep that in mind and you will be fine. Do your homework check the md5 then flash. If you are not sure then don't flash and remember qbking77 probably has a youtube video already so watch it.
someguyatx said:
I see you flashed Venums latest rom. I tried it out last night but just wasn't feeling it. Any time you flash anything there is a chance of a brick. Keep that in mind and you will be fine. Do your homework check the md5 then flash. If you are not sure then don't flash and remember qbking77 probably has a youtube video already so watch it.
Click to expand...
Click to collapse
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
oscarthegrouch said:
I'm staying away until ics is an official release, but that's just me being safe than sorry.
Click to expand...
Click to collapse
I will tell you something about Samsung and there official releases. When I had my cappy they keep saying there will be an update for froyo and before you know it I was flashing GB and still no release. Lol
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I am glad your laughing. I guess when Google engineers ran into the bug they were doing something stupid? I guess when they had Samsung write new firmware for eMMC chips going into the GNex it was because they were doing something stupid. I guess when all the Kernel and recovery developers bricked their phones and they couldn't even be jtag'd they were doing something stupid. Actually technically when you develop you know their are risks, but this risk is not something anyone expected. It is a permenant bug that will always be with your phone, things will be done to avoid it. But the danger isn't going away. Even after the OTA, as we are finding out there is still the danger of the calls being made from CWM zips, etc.
Just keep hitting factory reset in ICS, quickest way to do it and it still may take a few tries. If you think its perfectly okay that the Galaxy Note was push an update that causes random bricks when people factory reset thats fine. But you can't tell them they were doing something stupid when Samsung never emailed them to say "Don't factory reset".
Its a hard cold fact that sooner or later one of the times mmc_erase() is called with the flag MMC_CAP_ERASE corruption will occur at the wearlevelfs level which can only be fixed by vendor specific commands not available to even repair centers.
4 roms? I did a few the wrong way. But 4 roms altogether? Many of us are around 30 and thats unique not reflashes. Probably around 200 total flashes myself just for ICS on this device. I am home on CM9 now which means only a couple a week from now on i think.
RainMotorsports said:
I am glad your laughing. I guess when Google engineers ran into the bug they were doing something stupid? I guess when they had Samsung write new firmware for eMMC chips going into the GNex it was because they were doing something stupid. I guess when all the Kernel and recovery developers bricked their phones and they couldn't even be jtag'd they were doing something stupid. Actually technically when you develop you know their are risks, but this risk is not something anyone expected. It is a permenant bug that will always be with your phone, things will be done to avoid it. But the danger isn't going away. Even after the OTA, as we are finding out there is still the danger of the calls being made from CWM zips, etc.
Just keep hitting factory reset in ICS, quickest way to do it and it still may take a few tries. If you think its perfectly okay that the Galaxy Note was push an update that causes random bricks when people factory reset thats fine. But you can't tell them they were doing something stupid when Samsung never emailed them to say "Don't factory reset".
Its a hard cold fact that sooner or later one of the times mmc_erase() is called with the flag MMC_CAP_ERASE corruption will occur at the wearlevelfs level which can only be fixed by vendor specific commands not available to even repair centers.
4 roms? I did a few the wrong way. But 4 roms altogether? Many of us are around 30 and thats unique not reflashes. Probably around 200 total flashes myself just for ICS on this device. I am home on CM9 now which means only a couple a week from now on i think.
Click to expand...
Click to collapse
I hear you dude.I am just saying if this is a known bug and ppl are still flashing ROMs with high risk of bricking. That is stupid. Not everyone has the money to get another phone if they brick. But it is the way the game goes. Thanks for the info I didnt know it was really all that bad. Looks like I will be going back ti el26 everytime I flash.
Edit and that still sucks,and this only ics? is GB safe?
Sent from my SPH-D710 using Tapatalk 2
Even though the app reports bricking probabilities, you shouldn't assume any firmware rev is safe. Per the EMMC lockup discussion thread, fwrev 0x25 (which brickbug reports as "probably safe") has a separate data corruption issue. Until there's a definite solution, if you're flashing ICS ROMs, you should follow the forum instructions and flash back down to EL26 w/ CWM and then back up or you're risking a brick.
EDIT: Flashing to an ICS ROM from EL26 w/ CWM is as safe as any regular flashing operation though, and speaking as someone that dragged their feet to flash up to ICS - it's worth taking the leap now if you're okay with a couple of hiccups (Blu Kuban here). Incredible experience and fairly easy to go back and forth if you take nandroid and titanium backups.
One again thanks to all for all the info. I had some phones that I tought were just unbrick able. I use to try everything on my cappy and the jig what the bomb. lol
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
I hear you dude.I am just saying if this is a known bug and ppl are still flashing ROMs with high risk of bricking. That is stupid. Not everyone has the money to get another phone if they brick. But it is the way the game goes. Thanks for the info I didnt know it was really all that bad. Looks like I will be going back ti el26 everytime I flash.
Edit and that still sucks,and this only ics? is GB safe?
Click to expand...
Click to collapse
Was talking to Chris41G last night he detailed some of the paths that were likely to brick still. SFHUB has been working on ways for developers to make their Recoveries and CWM Zips safe. Even with recoveries that are safe to wipe with some zips can still trigger the bug.
As far as GB goes, Calk's format all has a known safe updater binary. The cap erase flasg was not enabled on our GB kernel but as was also found out is still apparently safe if enabled. I cant remember what command it is but on ICS something like makeext4fs() is now called and is part of the problem. But only code compiled against the library that uses that even calls it.
We were all messing with leaks and its all our fault if something happens. We all have instructions and if someone doesn't read or follow them then yeah that is stupid. However the Galaxy Note was pushed ICS OTA without a workaround (which the GS2 i9100 has) and people were able to brick by just factory resetting which seems to be one of the easiest ways.
Googles engineer Ken Sumrall said the area for the /Data partition being the one to go was because it was written to more often, more chances. This thread - http://forum.xda-developers.com/showthread.php?t=1644364 has more information than I can even explain but may also be a hard read. They found the problem with the eMMC firmware while developing the Gnex, the prototypes had the same eMMC firmware as our phone. This can be update at the factory but not by the end user. The corruption occurs at a lower level than is presented as writable storage and can not be fixed by JTAGing firmware. It is possible for some super bricks to be partitioned around, others not.
ODIN is safe too by the way so if your ODINing your leaks no real worries there, there was some question as to calls made by Mobile ODIN which i flashed the EL26 kernel probably 25+ times with.
RainMotorsports said:
Was talking to Chris41G last night he detailed some of the paths that were likely to brick still. SFHUB has been working on ways for developers to make their Recoveries and CWM Zips safe. Even with recoveries that are safe to wipe with some zips can still trigger the bug.
As far as GB goes, Calk's format all has a known safe updater binary. The cap erase flasg was not enabled on our GB kernel but as was also found out is still apparently safe if enabled. I cant remember what command it is but on ICS something like makeext4fs() is now called and is part of the problem. But only code compiled against the library that uses that even calls it.
We were all messing with leaks and its all our fault if something happens. We all have instructions and if someone doesn't read or follow them then yeah that is stupid. However the Galaxy Note was pushed ICS OTA without a workaround (which the GS2 i9100 has) and people were able to brick by just factory resetting which seems to be one of the easiest ways.
Googles engineer Ken Sumrall said the area for the /Data partition being the one to go was because it was written to more often, more chances. This thread - http://forum.xda-developers.com/showthread.php?t=1644364 has more information than I can even explain but may also be a hard read. They found the problem with the eMMC firmware while developing the Gnex, the prototypes had the same eMMC firmware as our phone. This can be update at the factory but not by the end user. The corruption occurs at a lower level than is presented as writable storage and can not be fixed by JTAGing firmware. It is possible for some super bricks to be partitioned around, others not.
ODIN is safe too by the way so if your ODINing your leaks no real worries there, there was some question as to calls made by Mobile ODIN which i flashed the EL26 kernel probably 25+ times with.
Click to expand...
Click to collapse
Yeah i just bought moble odin pro
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
manufan721 said:
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
Click to expand...
Click to collapse
[/url][/IMG]
manufan721 said:
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
Click to expand...
Click to collapse
well dude this comment was not at you and when I said something stupid I mean stupid I had a cappy has my 1st android phone and I flashed rom from other phone and just doing stupid stuff,but we had home made jigs that unbrick anything. It didn't matter, plus a dev should test a non stable rom them self. Any mod, theme, I mean anything I post I test myself to ensure nothing well happen to anyone's phone.Sorry if I got you panties in a bunch'but come on dude read every post you took this the wrong way'but yeah no hard feeling man. Good luck to you, and not bricking your phone again.
rwright64 said:
[/url][/IMG]
Click to expand...
Click to collapse
Lmfao
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
well dude this comment was not at you and when I said something stupid I mean stupid I had a cappy has my 1st android phone and I flashed rom from other phone and just doing stupid stuff,but we had home made jigs that unbrick anything. It didn't matter, plus a dev should test a non stable rom them self. Any mod, theme, I mean anything I post I test myself to ensure nothing well happen to anyone's phone.Sorry if I got you panties in a bunch'but come on dude read every post you took this the wrong way'but yeah no hard feeling man. Good luck to you, and not bricking your phone again.
Click to expand...
Click to collapse
Good answer bro..no hard feelings on my end either.. if i did take this the wrong way then i apologize for it..
Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/sprint/freegee/FreeGee-0.5_Sprint.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...
Thanks to all of u guys for all your hard work!
Here is some proof, this is fully working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the blurry images, took these from my old OG Evo... But can say its fully unlocked!!!
Nice work thecubed, and shellnut2 on this, thanks for keeping our freedom alive!!!
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Tyederian said:
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've already run the OTA, and had no issues unlocking, or rooting after the OTA...
I am so excited! I cannot wait to get this thing unlocked! :victory:
Sweet super excited
Awesome! Will be donating to the team on pay day thanks guys!
Sent from my PG86100 using xda premium
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Wow! Many thanks to all the devs for their hard work and to the beta testers for their willingness to let their phones be guinea pigs. Very much looking forward to this!
Sent from my LG-LS970 using Tapatalk 2
jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
$55 they charged me $99 and some tax on top of it. how did you pull that off?
Super sweet you guys are awesome!!
Christmas came early this year.
Sent from my LG-LS970 using xda app-developers app
New build is up!
Fixed a typo in my code haha
awesome job, big thanks to everyone.
And I second that $55 question.
jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
How on earth did you get it for $55?
tabormeister said:
How on earth did you get it for $55?
Click to expand...
Click to collapse
Had signed up for phone freedom to get $50 gift card back in February.
So I just ran this and had a couple little panic moment!!
1. While reading the script, SU poped up and I missed the "Grant SU" button on the phone. I still got the backup folder but nothing was in it. I then thought it worked, rebooted, and nothing.
The second time I ran this, I got to the "Grant SU" button in time and all went GREAT!!! This time I had files in the backup folder.
2. When I rebooted into recovery, I tried to make a backup. I hit the backup button and got some message that said "Can't mount backup path". So i tried the backup to internal SD and it worked.
Figured I'd write this in case anybody else had the same moment's I did.
The files on the backup folder are very differnt from what I'm used to so hopefully I did it correctly. I noticed there was an option in CWM to choose the backup format after I'd made my backup, so I'm not sure which format is correct for Restore. I guess I used the default which is .dup.
Thank you very much dev's for this!!!!!:laugh:
---------- Post added at 05:54 AM ---------- Previous post was at 05:25 AM ----------
DO NOT use the camera!!!! It'll crash your phone!!!
I read about it in the ATT section just now, but it's too late for me. So I guess we have this bug also.
OK...so not quite a crash. Held the volume down button and power together and got it to reboot.
Now we just need to have a way to recover our phones if/and/or when we do crash our phones. I know the devs are working on this, as obviously they are the bomb!!!
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Shelnutt2 said:
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Click to expand...
Click to collapse
I'm sure hoping you're referring to my post above. I get alittle wiggy if I don't have a way to fix my phone myself.