Database Info

[Q] Just another root question - 2.3.6

There's so much out there I have to ask it directly. I know it's got to be in the forum somewhere but I've read probably half dozen ways to do this and it's confusing.
I have a TMob Galaxy S 4g T959VUVKJ6 running T959VUVKJ6-CL694130 kernel (hope that means something to someone!) with 2.3.6 firmware that came with the phone.
How can I get rid of bloatware?
If I have to root first is there an ez way to do that, like SOC that works on my phone?
I rooted a previous phone but with an older firmware and used SOC. Looking for the same process if I can. Thanks in advance.

SOC V2.3.3 will work on GB. If you just want to root and keep the stock ROM that's your best bet.

rogerperk said:
How can I get rid of bloatware?
Click to expand...
Click to collapse
Check my signature for FB's debloater. You do need to be rooted & have CWM installed to use it.
rogerperk said:
If I have to root first is there an ez way to do that, like SOC that works on my phone?
Click to expand...
Click to collapse
SOC is one way, but given that you need to have CWM installed I would suggest using the third link in bhndven's [Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011].
After that, install [KERNEL]Subtly Modified Stock with CWM5 + Voodoo Lagfix [02/24] to get on the latest beta kernel. It has the latest CWM which resolves an issue with CWM 3 not being able to mount /system on Gingerbread.
rogerperk said:
I rooted a previous phone but with an older firmware and used SOC. Looking for the same process if I can. Thanks in advance.
Click to expand...
Click to collapse
SOC will work, just make sure you have the latest version. However, to debloat you need CWM so I would forgo SOC & install the stuff above.

Nope. I downloaded SOC 2.3.3, checked USB debugging, plugged in my phone, it didn't ask my anything about my card, turned on SOC, clicked Root, it went through Killing ADB Server, daemon not running, daemon started successfully, and sat there at Starting ADB Server. Tried several times but no joy. Is it me?

It said Not Responding.

I haven't used it to root in a really long time personally. I know others have gotten it to work recently. Maybe try a different usb port. Here's a guide with some info on it. Read down a little bit and you'll see it. Sounds like your doing it right. Do you want to stay on stock and just have root? Or will you be playing with custom ROMs?
http://forum.xda-developers.com/showthread.php?t=1470716

hechoen said:
I haven't used it to root in a really long time personally. I know others have gotten it to work recently. Maybe try a different usb port. Here's a guide with some info on it. Read down a little bit and you'll see it. Sounds like your doing it right. Do you want to stay on stock and just have root? Or will you be playing with custom ROMs?
http://forum.xda-developers.com/showthread.php?t=1470716
Click to expand...
Click to collapse
Same result. It stops responding. I'm probably going to keep it stock. I may do a custom ROM later but right now I can't get it to root. Can't figure it out.

You need to try a USB that you haven't used on your phone before. Follow the first link in my signature and go to the part about rooting. If fresh USB port doesn't work after following the guide it will probably be your USB cable.

lumin30 said:
You need to try a USB that you haven't used on your phone before. Follow the first link in my signature and go to the part about rooting. If fresh USB port doesn't work after following the guide it will probably be your USB cable.
Click to expand...
Click to collapse
Still no joy. I think this is just too hard to do, which brings me back to my original question. I'm sure some wizard will come up with a way to do this soon - just not now I guess. Thanks for the help though! I appreciate it. I guess I'll stay stock for awhile yet.

How could you have done what I said in that short of time? I think you aren't reading thoroughly and are waiting for a specific answer you want to hear.

Just follow the second link in my signature. You will be on rooted stock with CWM and the guide is DUMMY proof.

I think your right lumin....outside of the vibrant....this is the easiest phone to root.
Sent from my SGH-T959V,SGH-T959 using xda premium.

Another simple way to get rid of bloatware is to use titanium backup or root explorer.

Because I am sitting at my computer working on this so it wasn't that hard to do. I had SOC open, had already downloaded file manager, etc. I never got a USB port to work but I'm going to try it again. Once I get a moment to take a deep breath. I really do appreciate the help but I don't want to do alot to do that. I got spoiled with SOC.

lumin30 said:
Just follow the second link in my signature. You will be on rooted stock with CWM and the guide is DUMMY proof.
Click to expand...
Click to collapse
OK, I think it worked this time. The trick was to use IE and not Chrome apparently. It didn't go like the directions said but I ended up with a rebooted phone, lost all my apps and stuff, but with superuser on it so I assume I'm rooted and this won't start launching nuclear missiles or something. Thanks, Lumin! I appreciate your patience with me.

Hi. I have posted in another thread regarding problems with my Wind Mobile Samsung Galaxy S 4G (SGH-T959W), which seems to be similar to rogerperk's issues, although the phone is a different model. lumin30 responded to the post saying that my phone is not supported by XDA. Being a noob, I don't understand why my phone is not supported. It is still a Galaxy S 4G, is it not; albeit with different baseband.
My original post: http://forum.xda-developers.com/showthread.php?p=24678919#post24678919
Is there anyone out there that may be able to help? stephen_w, lumin30, FBis251? My main goal is to root it so I can use Titanium Backup and fix the random shut-down problems.
thanks,
Billy

billyckot said:
Being a noob, I don't understand why my phone is not supported. It is still a Galaxy S 4G, is it not; albeit with different baseband.
My original post: http://forum.xda-developers.com/showthread.php?p=24678919#post24678919
Click to expand...
Click to collapse
Billy even tho your phone is a SGS4G it is different from the T-Mobile phone. So our methods wont work. We dont know anything about your phone or even how to root it. You are probably stuck with a locked up phone.

Super One Click is not specific to our model phone. I will post a link to the website for you to read up on and determine if you want to try using it to root. I haven't read anybody messing their phone up with SOC - however, keep in mind you will not have a way to fix your phone if you do mess it up.

lumin30 said:
Super One Click is not specific to our model phone. I will post a link to the website for you to read up on and determine if you want to try using it to root. I haven't read anybody messing their phone up with SOC - however, keep in mind you will not have a way to fix your phone if you do mess it up.
Click to expand...
Click to collapse
I started to link him but in his initial post he states it wouldnt work. Maybe the newest version will do the trick tho.

Here it is either way - http://shortfuse.org/?p=193

[Q] trouble flashing PG59IMG.zip

I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh

more to it than flashing an hboot
read up on THIS

SurfRodder said:
I've been running CM9 for a few weeks now, but have decided that I want to get S-Off and open the phone's capability up some more... Anyway, I'm on a MT4GS:
HBOOT 1.45.0013
Nov 21 2011 build
Tried flashing this https://www.cx.com/mycx/share/O2W61....00_11.16.3504.20_2_release_245247_signed.zip
from weekendsr2short's mirror page (http://forum.xda-developers.com/showthread.php?t=1878329) of Blue6ix's stuff...(i tried autoflashing from the bootload/fastboot screen)
anyway, it loads up like it is going to actaully flash, but nothing changes on the Bootloader screen. The phone is unlocked via HTC's tool and is rooted. Any help is greatly appreciated! Please lemme know if any more info is needed.
Josh
Click to expand...
Click to collapse
If you're rooted, install a stock-based ROM and then use juopunutbear.

blackknightavalon said:
If you're rooted, install a stock-based ROM and then use juopunutbear.
Click to expand...
Click to collapse
OK, that's what I was hoping to do. I noticed in the JB instructions that it said I must be a stock RUU not a custom ROM or something to that effect. I am on CWM 5.Something so a rom flash is NP. Any recommended ROMs? I.e One that worked for you? I tried the wire trick about 100 times over the course of an hour or so(on cm9.1), but then reread the bit shout the rom again.
Thanks for all the responses so far!

Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)

demkantor said:
more to it than flashing an hboot
read up on THIS
Click to expand...
Click to collapse
Thanks, after reading that thread <again> it linked me the this http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Which I have Also already read,but noticed this time that I cannot be unlocked via HTC and still flash pg59imgs... so im off to relock, if the stock rom method doesn't work...

WeekendsR2Short said:
Any stock based ROM will do. I went with MikTouch myself and it worked like a charm! (on the 4th try so be patient....)
Click to expand...
Click to collapse
Awesome, thanks brotha

well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!

SurfRodder said:
well, one down, one to go. I have my phone all dialed in...now its time to fix my wife's... Thanks again Gents! (& Ladies, as applicable!)
edit: well, hers is done now... I ended up using another SD card, the original one I tried was kinda old, but the newer one I normally use worked on the 2nd try... didnt lose any data either... her sd card on the other hand was toasted and needed to be reformated... anyway, both phones are now S-Off!!
Click to expand...
Click to collapse
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!

WeekendsR2Short said:
Man, that's GREAT! Once you knew HOW, the process was nothing for you. That's a far cry from most. Way to go!
Click to expand...
Click to collapse
yeah, Ive been running root since my MT3G way back when...couldnt stand how laggy that thing was with all the bloat... wasnt even that great with CM6 but still night and day better than stock (=hooked on rooting). then upgraded to the MT4g and now this thing... was fairly concerned about all the extra hoops but wouldve just chosen another platform had I borked it...glad I didnt, saved me some funds!
On a related note, what radios are you guys running? Are there any issues between the GB radios and ICS ones? Im assuming so, but with the custom ROMs/kernels anything should be able to be overcome I'm hoping... I know I def. had issues on CM7 -> CM9 on the reg. 4G when swapping radios...

I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)

WeekendsR2Short said:
I don't generally swap my radios around since there are only two that I'm aware of. But I DID find that the new one (when I replaced my phone) seemed to lock a signal a bit quicker but for me the original radio gets MUCH better phone reception. Depends on your phone I suppose.
(you'll be glad you went with this phone though. basically a Sensation with a keyboard)
Click to expand...
Click to collapse
cool, I just flashed the older one today... been having really crappy recption on campus lately (esp. since switching from the MT4G) better reception is what I'd rather have... ill give this one a week or so and see if I think its any better... I like the phone a lot already... i still use the soft keyboard from time to time as I forget the other one is there, but it comes in really handy on certain sites...

Hello guys, I've been lurking the forums for hours trying to find a thread with an issue close to mine, and this is the closest I got. I followed all the necessary steps on the first page, but the problem I'm having is when I try to flash the PG59IMG.zip file, it says "Loading... PG59IMG.zip", but then it says "Checking....PG59IMG.zip" and afterwards it says "Wrong zipped image!" Any ideas what it could mean? I just want to get it back to stock. Any help is greatly appreciated.

THIS MAY HELP YOU

Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.

The third post in this thread
http://forum.xda-developers.com/showthread.php?p=27796375
It was made for the g2 so don't use the drivers in it, but it will at least give you an idea of what to do
Sent from my HTC Vision using xda premium

Hanenbow said:
Thanks for the link. It said I need to relock the phone in order to flash the image, but when i type "fastboot oem lock" into command prompt, I get a message saying 'fastboot' is not recognized as an internal or external command, inoperable program or batch file." I'm guessing this means my fastboot wasn't set up correctly, but I don't know where to go from here. As always, thanks again for any help or advice.
Click to expand...
Click to collapse
Does fastboot work like this
./fastboot oem lock
On my PC some of my fastboot commands need that.
Sent from my Freaked out JellyBean

Thanks so much for your help guys. I followed the instructions on the pathing link, and the phone is currently flashing the image. I'll post a final time once I can confirm everything is fine.

Help Pls, I think I've just Bricked my phone :(

I've installed the new CM10 on my P500, It's working just fine, the problem is I have no GSM reception, it doesn't detect my sim card. When I upgraded from my GingerBread Void version, I wiped the system clean, and I do believe (knowing what I know know) that I've erased everything, including my baseband.
I've been looking into the problem and it seems that I should have kept the base-band (or something).
I've downloaded the LGMDP and the V20 Baseband in order to try to rewrite it. But no dice. After I hit download the End window shows nothing but the IMEI, no Bluetooth ADDR, nothing, just the IMEI.
Also no NV2 file is generated.
Does anyone have a clue?

Does it boot but not ask for the PIN to unlock the SIM?
Sent from my LG-P500 using xda app-developers app

Yes, it boots just fine. The CM10 works brilliantly ), smooth and clean, but I have no GSM, it simply doesn't detect my SIM. If I try to make a call it says something like "no network detected"

In the "about phone" menu, the baseband reads "Unknown"

Ok, I've been reading some more and It would seem that the phone is not literally "Bricked". I think I have to flash a stock rom back in order to get the right baseband. Please correct me if I am wrong because this is what I am going to do when I get home, being that I'm at work right now I have no way of testing anything.

Well if it boots, you haven't got a high-tech brick. I had a similar problem recently although I didn't check in any of the menus like you said. I knew when it didn't ask for the pin. For some reason it wasn't detecting the STK.apk although it was there.
Have you got some kind of file explorer (root enabled) installed? If so, check /system/app to see if STK is there. If not then you need to put it there (get it from another ROM). And edit the permissions to RW-R--R--.
As it was there for me, I tapped it so it installed (as a user app) and then uninstalled it and rebooted and it was fine. I guess it just needed reminding that it is, first and foremost, a telephone.
Formatting everything through recovery shouldn't wipe your baseband but if you still get nothing there are tuts here about flashing BB.
Hope you get it solved.
Sent from my LG-P500 using xda app-developers app

Hmm, thank you, I'll be sure to check that.

If you were on Void before you transitioned to cm10, most probably you may just have to flash an "old BB fix" ( available in many threads in this forum, just search) as Void was for old BB & all the current new ROMS including CM10 are on new BB. Avoid new BB flashing thru LGMDP or any other means as far as possible. old BB fix can be used without any side effects on CM 9/10 based ROMS.
Sent from my LG-P500

Thanks for the advice, but I've already tried that last night, unfortunately it didn't help

digsf said:
Thanks for the advice, but I've already tried that last night, unfortunately it didn't help
Click to expand...
Click to collapse
If your using AmonRa recovery you have to mount system before you flash obb fix or it wont work.

At the moment I'm using Team Win recovery, but I'll definitely give that a try

At the moment I'm using Team Win recovery, but I'll definitely give that a try.

digsf said:
At the moment I'm using Team Win recovery, but I'll definitely give that a try.
Click to expand...
Click to collapse
Thanks 3ncrypt3d_droid, ur right. I missed mentioning that, & I use AmonRa too...

pmvyas said:
Thanks 3ncrypt3d_droid, ur right. I missed mentioning that, & I use AmonRa too...
Click to expand...
Click to collapse
Glad I could help

Thanks Jerry.
digsf - did this solve your problem ?

Not at the moment, I've finally gotten home, I'm working on it right now )

Brilliant, I've got it working, I'd like to thank all of you, especially WidowCranky and 3ncrypt3d_Droid who gave me the right clues . The permission wasn't set on my TeamWin recovery and the BBFix Update wouldn't work. Set the permission right, flashed the fix. Works perfectly. Thank you all very much. I am officially on Jelly Bean

Congrats & enjoy.
Sent from my LG-P500

digsf said:
Brilliant, I've got it working, I'd like to thank all of you, especially WidowCranky and 3ncrypt3d_Droid who gave me the right clues . The permission wasn't set on my TeamWin recovery and the BBFix Update wouldn't work. Set the permission right, flashed the fix. Works perfectly. Thank you all very much. I am officially on Jelly Bean
Click to expand...
Click to collapse
There is another work around for that issue also, just to keep from having to apply the baseband patch after flashing ROMs. Instead of flashing P500 ROMs, flash P509 ROMs instead. The hardware is identical, only difference is baseband. P509 will always be old baseband as they never got official GB support from LG. Just a thought. That's assuming the dev for the ROM you are using builds for P509 too. Again, just a thought.

Glad you got it working, glad I could help, even if only in a small way.
Enjoy JB.
Sent from my LG-P500 using xda app-developers app

[Q] Unauthorized software message ONLY when booting into recovery

This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?

Sleix said:
This is my first post ever here so I'm sorry if I'm breaking some rule (read the forum rules so I don't think I am) or if it's in the wrong subforum (although this does seem like a help & troubleshooting topic to me).
A little backstory is probably necessary.
I rooted my s3 (latest OTA update) via CASUAL (thread: http://forum.xda-developers.com/showthread.php?t=2332825) and it seemed like it worked for the most part, although it didn't boot into twrp like it should have and instead booted into normal recovery. I just assumed that it was because something went wrong with the recovery installation so I just thought "ok whatever."
Root access was there, and I assumed the bootloader was unlocked since I read several places that when it's unlocked, the initial samsung boot logo appears for about a second as opposed to several seconds when it's locked. So I just assumed all i needed was to reinstall a custom recovery and I was golden.
Installed ROM Manager, flashed CWM through the app, and rebooted the phone, and as it was booting into recovery I was greeted with the infamous "NO CUSTOM SOFTWARE ALLOWED PLEASE ALERT PAPA VERIZON IMMEDIATELY" warning.
I was about to flash back to stock through odin (which i regretted since I've had bad experiences in the past using it) when I figured out I could get the device to boot normally by clicking cancel in the download mode confirmation window, rebooting the phone normally. I guess it kept trying to reboot to recovery after every unsuccessful boot, which made it seem like it was softbricked to me.
Phone is operating normally now, and it should after another reboot as long as it doesn't try to go into recovery again (though I'm kind of afraid to even do that).
Is there any way without Odin I can fix my recovery and/or bootloader? I'm not sure what the problem is here and I don't think this sort of thing is a common searchable issue. Google/XDA search didn't bring up anything that sounded like someone had 100% the same problem I do.
Also on a semi-related note, does EZ-Unlock still work with this latest OTA? And if my bootloader is potentially unlocked already, would unlocking it again through EZ-Unlock break something?
Click to expand...
Click to collapse
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
That is really weird...
I was reading it and was going to suggest easy unlock v1.2,you will not break anything using that app.
If that still doesn't work, try to flash TWRP through goo manager and see if it somehow fixes your recovery issue.
It sounds to me that your Bootloader is unlocked though... But give it a shot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.

Sleix said:
Thanks for the quick response.
That was going to be what I tried first, that's why I asked about it.
I'll wait for a little more input before trying it though if it's really that weird of an issue.
Click to expand...
Click to collapse
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
It's just strange that you only get that message with recovery mode, it normally will not do that.
At the very worst, an odin back to stock is pretty easy. Just follow the same process, but use ez recovery instead of rom manager. It was made specifically for our phone, and never gives me any issues when installing recoveries.
I still think if you use ez unlock it'll probably fix the issue completely. Let me know if you figure it out. Good luck.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?

Sleix said:
Thanks. Used ez unlock to unlock the bootloader. It was previously labeled as "Unknown".
Downloading ez recovery right now. Do you think I need to reinstall my recovery just to make sure?
Click to expand...
Click to collapse
No, but it wouldn't hurt.
Use 1.2 of ez unlock, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
These are the most recent recoveries, download and flash in the ez recovery app if you need to.
http://forum.xda-developers.com/showthread.php?t=2096735
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
No, but it wouldn't hurt.
Use 1.2, versions 1.3 and 1.4 will give an unknown message. There have also been lots of reports saying that version 1.4 did not unlock their bootloader.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.

Sleix said:
Reflashed CMW (I used the version provided by ez recovery, please let me know if that's a problem) just in case and it worked like a charm. Thanks!
Also I did use version 1.2. I actually had it sitting on my phone's home screen before I made this thread.
It still showed up as "Unknown". Maybe that indicated the problem?
Regardless, this problem seems to have been fixed. Now it's time to do some research on verizon s3 roms.
Also another semi-unrelated note, it seems I tripped a flash counter somewhere along the line.
Is Triangle Away one of those apps that is just "open and press a button"? I've been kind of wary of using it since it has that huge warning in app's description.
Click to expand...
Click to collapse
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Before flashing anything, use a newer recovery image. The one provided by ez recovery is from last year, the newer versions are better written to prevent possible errors that come up with jellybean.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Glad to hear it's working! Strange issue but looks like you ironed it out.
Triangle away is the app you would use. You tripped it using the rooting method injecting your recovery through odin, it's a big warning because it messes with your boot partition. If it fails and borks your boot partition, then you'd have to jtag your phone to fix it.
I personally wouldn't use it unless I was turning in my phone for service or replacement. But the app has great reviews and not many reports of bricks.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'll keep that in mind, thanks again!
Any roms you'd recommend?

Sleix said:
I'll keep that in mind, thanks again!
Any roms you'd recommend?
Click to expand...
Click to collapse
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Read through the op's and decide based on what you're looking for.
Mostly stock, very stable:
Clean rom, bonestock, darthstalker x1.
More modified stocks, more buggy but can run very well:
Hyperdrive, axis, goodness, moar
AOSP isn't my cup of tea, but they are fast and lag free.
Make sure you update your recovery image first, I edited my last post but think you missed it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Will do. Thanks for pointing that edit out.

[SOLVED] Did I brick?

Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
EDIT: In case anyone has this issue searching threads, I just used Wug Toolkit to flash everything back to stock and then used the same Toolkit to unlock and root. TWRP isn't going to recognize a backup from a different phone. To my understanding, there is a way around that, but I didn't look into it. Oh, and apparently, don't flash the EFS partition lol

New Jer-Z said:
Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
Click to expand...
Click to collapse
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button

mpalomba3 said:
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
Click to expand...
Click to collapse
Oh, that reminds me, TWRP wasn't able to mount any of the directories, it seems. I think it can, now, but I remember seeing those errors in the log before I wiped everything. Thanks for that suggestion, i'll give it a shot.

No problem, report back if it works
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button

I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?

Odin is for Samsung devices
sent from my HAMMERHEAD neXus

New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701

El Daddy said:
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
OK!
So, I used the Wug toolkit to basically flash everything to stock, and then root it. I installed TWRP using the app and I tried using the app to restore from my earlier back up. So, it boots into recovery but nothing happened. Looking at the log, it says the TWRP isn't able to locate the files. Trying to just restore from recovery isn't helpful because when I hit "Restore" nothing pops up. As if the SDCard partition isn't being accessed. I can't see any of the files in any directory. Anyone have any ideas?

You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk

El Daddy said:
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I realize that now lol. Well, I fixed that, but now have a new issue. Any ideas for me?

Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk

El Daddy said:
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I had a copy saved on my desktop, so I transferred it back.

New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Sorry about that, I have a gs4 so I thought Odin was for all devices
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button

New Jer-Z said:
I had a copy saved on my desktop, so I transferred it back.
Click to expand...
Click to collapse
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk

housry23 said:
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Someone explained to me TWRP won't recognize a backup with a serial number from a different phone. So essentially, I will just have to forego it. I used Wug Toolkit to fix this issue and just flashed everything to stock and had the same toolkit unlock and root. Using ADB was a fail and cost me a whole afternoon lol