Is my phone bricked? - T-Mobile LG V10 Q&A, Help & Troubleshooting

Okay I've never bricked a phone (lucky maybe) ever with all the phones I've owned. However I think my v10 is bricked? How can I tell?
Symptoms for diagnosis for the experts here at XDA, it keeps rebooting -bootloop at LG startup screen and never goes into recovery. Once in a 100 times makes it into TWRP (power button and volume down) but as soon as I click the screen it bootloop again. I can get into fastboot (volume down USB) and have tried sending a boot.img and recovery.img several times so far and still not holding TWRP recovery. ADB also won't show a device only fastboot device command shows the phone.

I had a Samsung phone once that behaved similarly, just kept on rebooting no matter what I did(didn't sit there forever, it would actually keep shutting down and trying to boot, repeatedly). Same in download mode. I sent it in and they replaced the digitizer, I believe. Could be the same, but keep trying everything!
Sent from my LG-H901 using XDA-Developers mobile app

Even though stays on
YrrchSebor said:
I had a Samsung phone once that behaved similarly, just kept on rebooting no matter what I did(didn't sit there forever, it would actually keep shutting down and trying to boot, repeatedly). Same in download mode. I sent it in and they replaced the digitizer, I believe. Could be the same, but keep trying everything!
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah I thought something like that, but because it doesn't do a reboot when I get into recovery or download (can stay on indefinitely) I thought it might be something else.

How did it get into this condition? Were you flashing something?
Sent from my LG-H901 using XDA-Developers mobile app

Just happened
YrrchSebor said:
How did it get into this condition? Were you flashing something?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope just happened. Was traveling outside USA and when it registered it did this. Didn't work when came back to the USA so figured maybe try to reinstall software (thinking it might be that) again to fix. So thinking maybe your theory of a hardware failure is possible. and maybe should just try to get an exchange.

webfrm said:
Nope just happened. Was traveling outside USA and when it registered it did this. Didn't work when came back to the USA so figured maybe try to reinstall software (thinking it might be that) again to fix. So thinking maybe your theory of a hardware failure is possible. and maybe should just try to get an exchange.
Click to expand...
Click to collapse
ah ok, sounds like it wasn't your fault, so an exchange should hopefully be in order. keep us posted

Related

[Q] Was it an official move?

I'm just wondering if any of you guys can confirm (or deny) that the newer Samsung Vibrant models were manufactured to not respond to the volume rocker during reboots, thereby disabling manual reboots into recovery or download modes.
Does anyone know if this was an official move by T-Mo or Samsung, or if this was just a defect with a certain batch of Vibrants, such as those stamped with the 10.07 date? Have any official statements been made? Any resolutions?
I'm simply curious...feel free to respond with pertinent threads that I may have missed discussing the matter. It just seems like there's a small handful of us who aren't able to manually reboot (I've seen a small handful of threads, but no solid explanations or resolutions), and I'm sort of interested if anyone knows any solid reasoning behind this anomaly.
Can't really say for sure. All I know is that my replacement Vibrant that I received from T-Mobile in the beginning part of last week boots into recovery and download mode just fine. I was actually worried when I read those threads and tried it out for myself, and yeah, both are fine.
Could be a defect, or I could have possibly received an older-dated unit.
MMcCraryNJ said:
Can't really say for sure. All I know is that my replacement Vibrant that I received from T-Mobile in the beginning part of last week boots into recovery and download mode just fine. I was actually worried when I read those threads and tried it out for myself, and yeah, both are fine.
Could be a defect, or I could have possibly received an older-dated unit.
Click to expand...
Click to collapse
I'm hoping that it's more of a defect if anything...somehow, I hope that it being a manufacturer's defect would help my case in asking T-Mobile for a replacement Vibrant, despite the fact that I can't get past the "Phone--!--Computer" screen.
I've got my fingers crossed, and the fact that this is a fairly uncommon occurrence is mildly reassuring.
well, so far me and my girlfriend's phone aren't able to get into recovery or download mode through the volumn switch method. We got both phones last week, 8/25 shipped out from tmobile. The date on the phones are 8/13/2010 The only way to root was using the one click with adb.
My phone doesn't go into recovery either but o just use the rom manager when I need to get into it.
Sent from my SGH-T959 using XDA App
DaSmittyman said:
My phone doesn't go into recovery either but o just use the rom manager when I need to get into it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That's nice but sometime when it's starting up, you WANT to be in Recovery mode without relying on ROM Manager. Mines can both go into download and recovery
Try this: power down, when you get the charge batt.graphic hold down vol up/down+power you'll see the batt icon blink a few times let go, you ahould enter recovery then.
Sent from my SGH-T959 using XDA App

Motorola Photon 4g Please Help. RSD protocol

I have the motorola photon 4g and I've yet to find a thread that says exactly what my phone is doing.
My phone has been stopping at the motorola screen and saying RSD protocol startup, none of my buttons are stuck and I've tried to put it in flashboot and it just wont do it. I've tried holding the volume up and power button and holding the power button and volume down. I jsut don't know what else to do.
The phone is completely stock, no roots or anything. I just want a working phone because I'd rather not switch back to an lg rumor touch.
What did you try to get it into Fastboot mode?
Edit: Never mind, I see you are running a separate thread on this one...
.cruiser said:
What did you try to get it into Fastboot mode?
Edit: Never mind, I see you are running a separate thread on this one...
Click to expand...
Click to collapse
I only tried because on all the many forums I've seen on various with people with similar issues with photons and oither droids, people were telling them to do a factory reset or bring it to flashboot, I just want my phone fixed.
You left out the part about dropping it in the toilet in this thread. It worked fine before that. So my guess its water damaged. You really dont need 2 threads for the same issue.
Sent from my MB855 using xda app-developers app
Water damage or not, I'm still going to try and fix it. It obviously will turn on, I just need a way to either restart the phone or get it past that screen.
caitybmccall said:
I have the motorola photon 4g and I've yet to find a thread that says exactly what my phone is doing.
My phone has been stopping at the motorola screen and saying RSD protocol startup, none of my buttons are stuck and I've tried to put it in flashboot and it just wont do it. I've tried holding the volume up and power button and holding the power button and volume down. I jsut don't know what else to do.
The phone is completely stock, no roots or anything. I just want a working phone because I'd rather not switch back to an lg rumor touch.
Click to expand...
Click to collapse
are you unable to boot into recovery?
If you are familiar flashing motorola with rsd lite then flash it with "(198_6)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US" sbf file via rsd lite, it will return back to stock.
there is a thread on xda.just explore....
caitybmccall said:
Water damage or not, I'm still going to try and fix it. It obviously will turn on, I just need a way to either restart the phone or get it past that screen.
Click to expand...
Click to collapse
Water damaged or not you probably broke it by dropping it in the toilet...so..water damaged...get a replacement..
Sent from my MB853 using XDA
deepak251146 said:
are you unable to boot into recovery?
If you are familiar flashing motorola with rsd lite then flash it with "(198_6)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM-release-keys-signed-Sprint-US" sbf file via rsd lite, it will return back to stock.
there is a thread on xda.just explore....
Click to expand...
Click to collapse
I've looked for it a bunch and all the things I've seen on here don't give me the correct download and send me somewhere else.
caitybmccall said:
I've looked for it a bunch and all the things I've seen on here don't give me the correct download and send me somewhere else.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=(198_6)-1FF-su...-1_SUN-198_6-CM-release-keys-signed-Sprint-US
Sent from my MB853 using XDA
na7q said:
http://lmgtfy.com/?q=(198_6)-1FF-su...-1_SUN-198_6-CM-release-keys-signed-Sprint-US
Sent from my MB853 using XDA
Click to expand...
Click to collapse
I've tried that before I even found this site, none of the downloads that I've found are correct and they download something completely opposite of what I want so that was no help honestly.
My phone has insurance, I'll just get a new one.
Thanks anyways.
caitybmccall said:
I've tried that before I even found this site, none of the downloads that I've found are correct and they download something completely opposite of what I want so that was no help honestly.
My phone has insurance, I'll just get a new one.
Thanks anyways.
Click to expand...
Click to collapse
Stuck in a goddamn bootlook after SBF'ing at least 10 times. Any ideas how to fix this POS phone?
Bootloop is not reason for flashing sbf.
Wipe data!
MikeyLee said:
Stuck in a goddamn bootlook after SBF'ing at least 10 times. Any ideas how to fix this POS phone?
Click to expand...
Click to collapse
Not a "pos phone". You need to read stickies, read threads and become familiar with your phone before modifying it. If done so you would know that SBFing would not cause a bootloop , you obviously chose to RSD in the first place for a reason.
Now, for the spoonfeed:
Try to boot into recovery, if you can, wipe data and do a factory reset. If you can't access recovery, make sure you have the latest drivers and try with multiple computers.
Sent from my Motorola Electrify using Tapatalk 2

[Q] Is my phone permabricked?

So last night, when going to charge my phone, I notice that turning the screen on wasn't bringing me to my lockscreen. Instead it was a black screen with a line in the middle. It looked like the screen off animation got stuck on the screen. So I rebooted it and it was fine.
Today, I wake up and it won't respond at all. Holding the power button does nothing, it doesn't look like it's charging either. I know that I have it set up to run lagfix at night, could that have been the cause of this? Is there any way to come back from a brick?
shmallow said:
So last night, when going to charge my phone, I notice that turning the screen on wasn't bringing me to my lockscreen. Instead it was a black screen with a line in the middle. It looked like the screen off animation got stuck on the screen. So I rebooted it and it was fine.
Today, I wake up and it won't respond at all. Holding the power button does nothing, it doesn't look like it's charging either. I know that I have it set up to run lagfix at night, could that have been the cause of this? Is there any way to come back from a brick?
Click to expand...
Click to collapse
Yup, there is a way to fix this. Visit your local Sprint store and have it replaced. Hope you have insurance, if not its $50. Gods peed to you.
MeestaAytch said:
Yup, there is a way to fix this. Visit your local Sprint store and have it replaced. Hope you have insurance, if not its $50. Gods peed to you.
Click to expand...
Click to collapse
No insurance. :crying:
After plugging the device into the computer, it says QHSUSB_DLOAD. So I guess that confirms it was from lagfix.
shmallow said:
No insurance. :crying:
After plugging the device into the computer, it says QHSUSB_DLOAD. So I guess that confirms it was from lagfix.
Click to expand...
Click to collapse
Well you're going to have to pay the $50 then. And yea its from the "lagfix". That "lagfix" is really just TRIM. It's disabled off CM10.2 currently for this exact reason. It's been having a grand ole time causing a brickfest.
MeestaAytch said:
Well you're going to have to pay the $50 then. And yea its from the "lagfix". That "lagfix" is really just TRIM. It's disabled off CM10.2 currently for this exact reason. It's been having a grand ole time causing a brickfest.
Click to expand...
Click to collapse
I thought even if you had insurance you had to pay to get a replacement? Isn't only the in-store repair free?
shmallow said:
I thought even if you had insurance you had to pay to get a replacement? Isn't only the in-store repair free?
Click to expand...
Click to collapse
You only pay the deductible if the phone is lost or stolen. For hardware failure, with TEP, there should be no charge for a replacement device.
Jtag might be another alternative, as well. Shoot XDA member Zarboz a PM for more info.
Sent from my EVO using XDA Premium 4 mobile app
PM'd Zarboz. But is there any way for me to unbrick it myself? I'd really like to leave going to sprint or mailing my phone away as a last resort. I've found a few unbricking tutorials, but they say that they're only for bricks that occur when going S-Off. Would it be crazy to try one of those anyway?
shmallow said:
PM'd Zarboz. But is there any way for me to unbrick it myself? I'd really like to leave going to sprint or mailing my phone away as a last resort. I've found a few unbricking tutorials, but they say that they're only for bricks that occur when going S-Off. Would it be crazy to try one of those anyway?
Click to expand...
Click to collapse
It won't work. You're not the first person to have this type of brick. It occurs as a result of faulty hardware, which can only be replaced, or flashed directly with JTAG (and even then, you'd still have the same hardware, and be prone to the same issue again).
I guess you missed the part in the Lagfree app OP that mentions the "brick bug."
Captain_Throwback said:
It won't work. You're not the first person to have this type of brick. It occurs as a result of faulty hardware, which can only be replaced, or flashed directly with JTAG (and even then, you'd still have the same hardware, and be prone to the same issue again).
I guess you missed the part in the Lagfree app OP that mentions the "brick bug."
Click to expand...
Click to collapse
Well, no, I saw it. I thought I would be fine because I only saw the affected devices as samsung ones. Thanks for the input though. I'll just replace it or wait until I can upgrade.
shmallow said:
Well, no, I saw it. I thought I would be fine because I only saw the affected devices as samsung ones. Thanks for the input though. I'll just replace it or wait until I can upgrade.
Click to expand...
Click to collapse
Might help if you go to the thread and mention that this device appears to be affected as well, otherwise more may suffer your fate.
Bricked??
Yesterday I restored a backup that I've been running for mounths, restored fine and no issues. Today I got a text went to unlock the device, had snow like an old tv with no signal. I pressed home and got the lock screen but there was major screen tear and the device was very slow to respond. I managed to get to twrp recovery and there was also screen tear/snow and the middle 2/4 was not there and non responsive, so couldn't wipe, fix perms or restore any thing. Tried that a few times, now the only response I get is I hold the power button for 10-15 seconds, capasitive buttons flash, let go of button, half a second later there is a quick vibration and black screen. I can't get in to the bootloader or recovery. Am I hosed?? tia Also when I charge it the light doesn't go on
I too had this issue, but my phone went white then turned off and never turned
Back on. It was a hardware failure. They replaced mine for free.
Sent from my EVO using xda premium
I plugged the device after a while and the orange light comes on like it is charging?? Is that a good sign?? I try adb commands but it came up device not found. Any suggestions?
robbo10 said:
I plugged the device after a while and the orange light comes on like it is charging?? Is that a good sign?? I try adb commands but it came up device not found. Any suggestions?
Click to expand...
Click to collapse
Let it charge for a good long while, then try to power it up.
Sent from my EVO using XDA Premium 4 mobile app
FinZ28 said:
Let it charge for a good long while, then try to power it up.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK i'll try that, the phone was at 90% when all this happened idk??
mammothjojo88 said:
I too had this issue, but my phone went white then turned off and never turned
Back on. It was a hardware failure. They replaced mine for free.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I still had insurance I would do this, but I'm not sure a new Evolte is worth $50 to me, especially with my upgrade around the corner. I'll just have to say farewell to this phone. It was a good run.
FinZ28 said:
Let it charge for a good long while, then try to power it up.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let charge for a while it booted and got stuck on the splash screen but the coloring was off. I plugged it in to the computer ran "adb devices" and it found it said recovery and a long number. I tried "adb reboot bootloader" black screen and that was it.
Sent from my PC36100 using xda app-developers app
robbo10 said:
Let charge for a while it booted and got stuck on the splash screen but the coloring was off. I plugged it in to the computer ran "adb devices" and it found it said recovery and a long number. I tried "adb reboot bootloader" black screen and that was it.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Looks like an issue with the screen. If you have TEP I'd take it to Sprint and let them look at it. Shouldn't cost you anything to get it replaced.
Sent from my EVO using XDA Premium 4 mobile app
Wow, you guys were right, you do get a free replacement.
At first, I was set on just living with my mother's old SG4G, but I couldn't stand how outdated it was. The screen looked meh, and I couldn't even install Chrome on it. So I was ready to pay the $50 to replace it, went to sprint with my evolte, and the guy there said he could only service active phones. So he changed my active phone back to my evolte, and added insurance to it. So I walked in with a broken phone without insurance, and left with a new phone for free. I'd say that's a lucky day.
Thanks for your advice guys, you guys just got me a new phone for free.

[Q] P769 Bricked without root or other alterations

Hey all, my brother bought an LG P769 for T-Mobile from Walmart, he's never been the type to modify any of his technology, so he used his phone like it was out of the box, no root, no bootloader unlocking, or anything. One night, he gets a security error, his hone turns off, and he can no longer turn it on. The soft buttons don't light up, its not the battery, no moisture damage, and the phone is literally useless. He tried calling LG support, they won't replace it for some reason, as far as I know it was running 4.2, though I'm not sure (he's not here to ask, and I doubt he remembers)
Tried the hard reset, no luck.
Tried to do the offline fastboot method, I installed drivers correctly, and selected option 5, and this time it lights up the soft keys, but it never loads the security error screen, so I can't enter s.w upgrade mode. I've tried pressing 5, waiting the 5 seconds with it plugged in and leaving it plugged in without the battery, leaving it plugged in with the battery, and putting the battery in at different times during the 5 seconds and removing it afterwards, none of them boot to the security error screen.
Tried the LG Mobile Support tool, doesn't recognize my device, even though I installed the drivers directly from the tool.
What do I do?
bump
If you can't return it to Walmart and you are out of other options, you can send it in for repair by starting here: https://www.lg.com/us/support/repair-service/schedule-repair
I recently bricked my rooted P769 trying to update to V20H and ended up sending it for repair. They fixed it within a week and sent it back with a note saying they replaced the flash memory. Same phone, remaining warranty still good, now on V20H. Works fine so far.
How much did it cost you?
Sent from my Nexus 4 using XDA Premium 4 mobile app
gerbetta33 said:
How much did it cost you?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The phone is only 4 months old so still covered under parts and labor warranty. It only cost me shipping charges to send it to Texas.
Megado said:
The phone is only 4 months old so still covered under parts and labor warranty. It only cost me shipping charges to send it to Texas.
Click to expand...
Click to collapse
id prefer a fix that would not involve paying or waiting, if possible. bumping for other suggestions
gerbetta33 said:
bump
Click to expand...
Click to collapse
Sounds like a hardware issue... Get it turned in and ask for a replacement at T-mobile.
Sent from my LG-P769 using Tapatalk 2
Hello
I have a similar problem. What if the computer can recognize the phone? When I plug the phone into the computer, I see OMAP4430 under unknown devices. I heard that a dead phone can be revived through fastboot or kdz updater, is that true? I tried following directions on different forums, but some directions ask that usb debugging is turned on but my phone is dead and I can't do that. When I followed some of the fastboot directions, I was only able to install the driver once and couldn't install it a second time.
yeah, USB debugging was a roadblock for me too.
Sent from my Nexus 4 using XDA Premium 4 mobile app
gerbetta33 said:
yeah, USB debugging was a roadblock for me too.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wonder if there is a way to turn it on through the computer. Or just a whole other solution that doesn't need it to be turned on.
bump, still not fixed. ive exhausted every guide on here, nothing works.
gerbetta33 said:
bump, still not fixed. ive exhausted every guide on here, nothing works.
Click to expand...
Click to collapse
Did you try this method http://forum.xda-developers.com/showthread.php?t=2546571
His phone got brick, partition not found error in fastboot, before he recover it.
artit said:
Did you try this method http://forum.xda-developers.com/showthread.php?t=2546571
His phone got brick, partition not found error in fastboot, before he recover it.
Click to expand...
Click to collapse
i tried as best i could. the instructions are unclear. its not working.
gerbetta33 said:
i tried as best i could. the instructions are unclear. its not working.
Click to expand...
Click to collapse
More than likely the hardware just went out, if all you can use is the unofficial fastboot. If that's not the case maybe, just maybe the x & u images (from lelus fastboot tool) are corrupt. Re-download the fastboot zip and compare (md5 sum) x & u bin files. If one of the images are corrupt it won't boot or respond to anything.
Sent from my LGMS769 using XDA Premium 4 mobile app
UPDATE: still not working
however, using omap4boot-for_optimus-v1.21 i was able to get the capacitive buttons to light up on the front of the device. haven't noticed anything else as far as success with flashing anything.
the steps i took:
1. installed the fastboot drivers as instructed.
2. I ran omap4boot-for_optimus-v1.21 selected option 5, plugged in my phone, the buttons lit up, and it said to unplug the device and wait for S/W recovery mode, which never popped up.
what do i do?
Try this worked for me after trying everything in about 10 min. http://forum.xda-developers.com/showthread.php?t=2585161

[Q] Samsung Mega sgh -i527 Intermittent touch issues

Hey Guys/Gals!
I (stupidly) jumped into rooting too quickly. It's a great option for really getting the true potential out of your android IMO, but I (having no knowledge of the possible issues of rooting) really messed me up here.
I have a Samsung Mega SGH - I527 and I have no clue what version of android it was originally running.
Basically, one day I was on base with my cell phone in my pocket, and this was about a week after i rooted with a program I believe was called "kingo". I went to pull it out of my pocket, and the screen was not responding to touch. I wasn't doing anything unusual and there aren't any signs of damage of any physical kind. I freaked out on the spot, and realized it must have been the root.
I rebooted the phone, and touch came back. I rejoiced, then freaked out as about 15 - 30 seconds later, the touch went bad again.
It then stayed not working until I rebooted again, and again, and again, until I managed to get to the Factory Reset settings in that little tiny window of time.(a small note while on this subject: not every reboot got me that little bit of time to use the touch, and the amount of time i had to use the touch screen was never consistent from what i could tell.)
From here on out, just troubleshooting steps already tried:
- factory reset on phone in phones UI (did not fix)
- factory reset on phone with bootloader menu (did not fix)
- using Odin 3.07 to put supposed stock firmwareback on the device (did not fix)
- took apart phone to make sure digitizer/lcd cable was seated properly on the motherboard (did not fix)
Any Ideas? just trying to do something that makes this thing NOT a $500 shiny paperweight :'(
feel free to email me @ [email protected] if you have any further questions or info that could help out here!
PS: sorry if this is a repost, I didn't find anything related to this specific topic in forum
I would say your problem is with the hardware and not software. Now what the problem is and how to fix it, I haven't a clue. I would suggest that you contact Samsung.
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app
dparrothead1 said:
I would say your problem is with the hardware and not software. Now what the problem is and how to fix it, I haven't a clue. I would suggest that you contact Samsung.
Click to expand...
Click to collapse
The only thing is, the phone is /really/ new.. i never abused it, and I'm thinking that its a software issue. I know its possible i broke/failed the hardware, but i really think its the case that the root i did messed it up. Do you know if there are any other more power ful ways to restore the chipset back to originality than using odin to load it back?
Have you unrooted?
Sent from my SAMSUNG-SGH-I527 using XDA Premium 4 mobile app
Yes. Is there a better rooting program than Kingo that I could possibly try?
mikemou said:
Yes. Is there a better rooting program than Kingo that I could possibly try?
Click to expand...
Click to collapse
If you have unrooted and its within a year, get a warranty replacement.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Roger, But they can ultimately tell bc even though I unrooted, the device still says "Custom" when you first boot it up. Is that a Problem? Should I just push Factory firmware back to the device with Odin before I contact them?
mikemou said:
Roger, But they can ultimately tell bc even though I unrooted, the device still says "Custom" when you first boot it up. Is that a Problem? Should I just push Factory firmware back to the device with Odin before I contact them?
Click to expand...
Click to collapse
I had rooted and unrooted several times thinking maybe root was the cause. Unrooted, saved everything on Kies, hardcore factory reset and sent that bad boy back when I got my new. Not a word from them.
My Mega never touched Odin
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
hardcore factory reset, you say?
Maybe you're just referring to opening the boot loader and clearing the cache and doing a FR, but just to make sure... What exactly did you do?
mikemou said:
hardcore factory reset, you say?
Maybe you're just referring to opening the boot loader and clearing the cache and doing a FR, but just to make sure... What exactly did you do?
Click to expand...
Click to collapse
Ha ha...I think if I could open the bootloader, I would be a GOD. Back up everything to Kies, then go into the 3e rcovery......factory reset
Sorry for delay. Working 2 jobs keeps me working a lot
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Roger that, so does this make me god? :laugh: jk jk but I'll try it out. I'm going to give this whole replacement a whirl :3
Hi im new to the android rooting realm ive had many a jailbroke iphones but new to this. So I bought my mega off Craigslist guy said it had been rooted but did full factory reset apparently that doesnt take root off anyway its still rooted but all the stuff that was said to be musts to use the root access says its not compatible, such as rom manager, titanium back up and HC-ktools. So is there a way to maje it compatible or specific program for the sgh-I527? Please help. Thank yiu for your time

Categories

Resources