Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
LOBBS said:
Exactly what I was looking for! I ended up on the G2 when my wife decided she didn't like it and I was waiting on the M8 to switch us from VZW to T-Mobile. She put it on KK in the few days she had it. I've always had HTCs and know my way around them quite well. This will go a long ways towards helping do the same on LG.
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
utesred said:
I hope it works out for you. I was looking at the M8 myself, but decided to go for the G2 last week. The battery combined with the cost was more than enough to sway me. I was surprised at how rough it was to root myself, coming from an HTC sensation and having rooted a Samsung Note 10.1 2014.
Let us know when you go for it, and how it goes for you.
Click to expand...
Click to collapse
I'm loving the G2 so far. It was my back-up choice in case there was something I really didn't like about the M8 so I'm not exactly suffering here. My ultimate goal is to get on an AOSP ROM so I really just need to get back to JB so that I can get root and recovery.
Sent from my LG-D801 using XDA Premium 4 mobile app
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
Click to expand...
Click to collapse
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
18.4009 said:
Thank you sooo much! Just what the doctor ordered!
---------- Post added at 10:25 PM ---------- Previous post was at 09:54 PM ----------
Dang it. Tried you method to the letter but it fails at 49% on the LG and 47% on the pc. once I reboot and factory reset it boots back into kitkat 4.4.2
Click to expand...
Click to collapse
Damn, that's a bummer! I'm assuming that it's failing while flashing the .kdz, right?
Sorry I can't be of much help on this one. Only thing I could suggest is to try it again. Maybe something went wrong? Make sure you've got the correct files and everything. You probably already know all of that, though.
I hope it works for you the second time around...or at least, the IORoot gets updated to work with our devices soon.
Yeah something has changed since my flash to stock kitkat. When I attempt to boot into recovery it isn't there (that's why ioroot25 won't work) but anyways. I think for one reason or another I am stuck...But that being said I work 12 hour night shifts and its my last night off with nothing to do.. So will attempt this again in a few different scenarios.
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
I used the 'C' .kdz file.
The 'G' one is another update. It is still 4.2.2, I believe.
Use d80110c
deepac said:
Hello guys, for rooting back from 4.4.2 to 4.2.2 on a Tmobile d801, do you use the d80110c_00 kdz or the d80110g_00 kdz ? I am not sure what the differences are either.
Click to expand...
Click to collapse
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
missiveusa said:
To avoid issues, you must use the D80110C .kdz. Users reported screen artifacts (lines) when using D80110G.
Click to expand...
Click to collapse
I may be wrong, but I don't think that the screen artifacts are caused by the D80110G. Using the same process, I went to the 80110C and tried flashing various roms afterwards. I got the artifacts on every other rom, except for the KK stock rom I used above.
From what I've seen and read from other users with the artifacts, they appear only on KK roms, with certain TMobile G2s. It seems that all phones that came with 80110G or 80110A preinstalled have issues.
Of course...I could be completely mistaken. That's just what I've noticed.
Give it time, root will happen for KitKat on T-Mobile.
I hope so, I spent all day yesterday trying until I just gave up. Guess its the waiting game for me.
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
2strokenut said:
For anyone having trouble downgrading using the KDZ method, just use the TOT method instead. It works perfect.
Click to expand...
Click to collapse
Can you please direct me toward a tutorial that has the TOT method? I tried to find one online but was not able to. I have a D801. The KDZ method doesn't work for me.
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
The biggest issue I have had in this whole downgrade, root, twrp, flash, is loosing twrp. I have tried multiple ways, but every single time I upgrade to 4.4.2 I lose custom recovery.
I even flashed twrp 2.7.0.0 over 2.3.6.2, but I have had no luck.
I have yet to try Flashify, but that will be my next move. I am Loki'd out lol
Help
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
utesred said:
Hi everyone. After scouring the forums here for hours, multiple failed attempts, and tons of misery; I've finally successfully rooted my T-Mobile G2 on 4.4.2.
As many are finding, people who have bought their G2 recently are having colorful lines whenever you try to turn on your screen when on KitKat Roms. This method fixes that (with this ROM only).
This is for people who are currently running the latest firmware (D80120A_00). I assume it'll also work with newer updates, but I can't make any promises.
---
As we've all seen, IORoot does not work on 4.4.2 on Tmobile devices for some reason. To get around that, we need to downgrade our devices to stock firmware. We will be following hyelton's guide, and lrwjr1964's discovery.
--Downgrade to 4.2.2--
First, navigate to hyelton's guide. Download the 4.2.2 stock firmware, from his link. On his Storage Cow site, navigate to the TMobile G2 folder, and then download the D80120C_00.kdz file. This is our stock firmware that we will be flashing to our device. You will also need to navigate to the link to the R&D Flash tool. The file is the LGMOBILEAX file. Install the LG Mobile Support tool. Launch the tool.
Next, we will be using lrwjr1964's discovery (post 2902 in the same thread). Plug in your phone, install any drivers needed, and let it get connected. Once you're all good to go, click 'options' in the top right hand corner, and then 'upgrade recovery'. What this will do, is download the latest D80120A_00.kdz file, and install it to your phone. How the program works, is it downloads the file to your computer, then transfers the file and flashes it. What we are going to do, is interrupt that process, insert our .kdz, and let it flash for us. Pretty nifty, huh?
You'll want to watch it super closely as it downloads. As soon as it finishes, yank the usb out of your phone. (I've done this twice without consequence. I don't make any guarantees, though.) This interrupts the file transfer, and throws you an error screen. Navigate to the folder "C:\ProgramData\LGMOBILEAX' . ProgramData is a hidden folder, so you'll need to make hidden folders visible. Rename your D80120C file exactly to what the file name of the other file is. Then, copy it over. Once it's finished, replug in your phone, let it connect, and let it resume the process. When it finishes, your phone will be running 4.2.2. How sweet is that?
--Root 4.2.2--
Now, this should work just as you're used to if you've done this before. Autoprime explains how to do this really well, so take a look at his thread here
--Install TWRP--
Again, if you've done this before, you're right at home. If not, WACOMalt has a thread you should check out here Make sure you download the correct .img for your phone. The Tmobile one. There's many different methods of flashing TWRP, but using the app Flashify worked easiest for me. It's on the Google Play store, and makes flashing it a cinch.
--Install KitKat and Re-Root--
This is one step you want to be careful with. Mess this one up, and you could be back at page one. SmiLey497 has the stock rom here. Ensure you not only snag the rom itself but get the SU file in the 'attached files' section.
Copy both files onto your phone, and boot to TWRP. You can do this easily from within the Flashify app.
Within TWRP, you need to do a standard wipe. After that, flash the ROM file first, and then the SU file after. DO NOT reboot your phone in between the files. If you do, you'll have just flashed the rom you had two hours ago when you began, and still not have SU. Once you do have them both flashed, reboot your phone and you're done.
--Celebration--
Congrats!! Your phone should now be running 4.4.2, and you should have root access. Go have some fun. Watch some Community, go for a jog, take a nap, eat dinner...do something FUN! You've earned it.
-----
I hope this guide is helpful. It very possibly could not work for you, or even mess up your phone. As far as I know, only myself and lrwjr1964 has used this method. I have very limited developing knowledge, so I likely won't be able to help with any too technical problems. Still, I'll be around to help as I can.
If this works for you, comment to let others know.
The best of luck!
utesred
Click to expand...
Click to collapse
The problem I think I am having, is in the Flashing TWRP guide, the t-mobile version, even though it states ver 2.6.3.3, its actually 2.6.3.2. I can not get TWRP to stick for the life of me.
---------- Post added at 03:48 PM ---------- Previous post was at 03:41 PM ----------
tpaxadpom said:
I've tried your method, replaced the file it was loaded onto phone and the phone is now stock in boot load. It displays T-mobile icon and keeps resetting itself.
Click to expand...
Click to collapse
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
frigginmike said:
hold the power button down until the screen goes blank, then press and hold the power and volume rocker down. when the LG logo appears release both buttons and quickly press and hold both power and volume rocker down. This will allow a factory (hard reset) and will get you out of the boot loop.
Click to expand...
Click to collapse
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo played in the infinite loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
tpaxadpom said:
I've tried your method but it doesn't work. Thanks for suggestion though. I had to put the phone in download mode (volume button down and then plug the usb), then I used LGLauncher.exe to recover it. I have tried the method described by OP twice. Both times I ended up with t-mobile logo playe in the infinity loop.
I've renamed t-mobile USA D80110C_00.kdz to D80120A_00.kdz and overwritten the file. In the original instructions it says D80120C_00.kdz file but I believe OP meant D80110C_00.kdz as D80120C_00.kdz is not available at the posted link.
Click to expand...
Click to collapse
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
frigginmike said:
its sort of tricky due to the weird button placement, but that method works, 100%. May have to do it multiple times. I only know this, because I have returned to stock on this device about 25 times trying to get TWRP and root to stick when upgrading to KitKat. lol
Click to expand...
Click to collapse
So I've looked on the related thread post 2901 (not 2902 as it says in OP), the reset is required. I've tried your method to reset and also one mentioned here but the phone continues to stay in the boot loop. This LG G2 is a PITA to get rooted.
Never mind. You are right. I've tried again your method and it worked. Performing reset now...
Related
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
Let me first say thank you bcuz I'm just trying to get my boys phone updated from jb an he's got the st version but I can't find a recovery anywhere, so I'd u could even just inform me on where to get the recovery I'd be good lol
soupysoup said:
Let me first say thank you bcuz I'm just trying to get my boys phone updated from jb an he's got the st version but I can't find a recovery anywhere, so I'd u could even just inform me on where to get the recovery I'd be good lol
Click to expand...
Click to collapse
Your Welcome, and I want to apologize for not answering right away i'm still trying to get xda setup on my phone. I have school most of the day and will only be available at nights. But you say you only want recovery? Download an app called ez-recovery for VZW Galaxy S3 on the play store. Yes this is the Verzion Galaxy S3 Variant but it works for this device because of where it uses uses Verizon towers. Then once you download the app, open it up and flash the clockworkmod recovery, not the touch or twrp. Let me know your results You might come across some failed to mount SD card errors in the recovery menu. If you do it doesn't take a lot to fix..
I've been looking for this for some time now
Jbeat69 said:
Your Welcome, and I want to apologize for not answering right away i'm still trying to get xda setup on my phone. I have school most of the day and will only be available at nights. But you say you only want recovery? Download an app called ez-recovery for VZW Galaxy S3 on the play store. Yes this is the Verzion Galaxy S3 Variant but it works for this device because of where it uses uses Verizon towers. Then once you download the app, open it up and flash the clockworkmod recovery, not the touch or twrp. Let me know your results You might come across some failed to mount SD card errors in the recovery menu. If you do it doesn't take a lot to fix..
Click to expand...
Click to collapse
I've managed to gain root and flash recovery for verizon sch-i535. would just like to know if that's correct and also need flash image and I also still looking for a compatible ROM. I've been to scared to download and install one.
Very interested!!
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
I have been driving myself crazy trying to find this information. I would be very grateful to you for the information on flashing the firmware and upgrading to KitKat 4.4 on the SCH S968C. It's impossible to get the info from ST or Samsuck.
Thanks
dijjay said:
I have been driving myself crazy trying to find this information. I would be very grateful to you for the information on flashing the firmware and upgrading to KitKat 4.4 on the SCH S968C. It's impossible to get the info from ST or Samsuck.
Thanks
Click to expand...
Click to collapse
here for the latest roms and fixes for this device
http://forum.xda-developers.com/showthread.php?t=2516498&page=30
Sent from my SCH-S968C using Tapatalk
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
i use this model and have been surfing these forums for some links to the stock rom since samsung doesn't provide it on their website. I was going to try to flash it back to stock but to be honest i have no idea what im doing and could use all the help i can get.
I've looked all over and watched and listened and read, and other than using oneclickroot to root my sch-968c, I'm too apprehensive on doing anything else before I know better. It's using 4.1.2 jellybean and theres a few things that I'd like my phone to be able to do considering its cost. I want to get KitKat 4.4 on my Galaxy s3. Samsung doesn't offer support, Straight Talk doesn't offer support. I understand its up to me to make this happen but I'd appreciate any help! Thanks!!
edit: So I havent used oneclickroot yet, I needed to download a samsung driver. I did use odin to flash a rom onto my device properly, but I'm pretty sure all i did was put exactly what I had on before it. Maybe I need to look for a custom rom, but I have a hard time finding the right sources. I need to look for a custom rom for sch-s968c with 4.4 kitkat? Need someone to tell me otherwise...
sch s-968c update os , help please
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
this would be awesome
Jbeat69 said:
Before I go on to give tutorial, I want to see how many people actually use this phone and if it's common enough for me to give the tutorial. I've noticed many people have tried to flash this phone and always end up bricking it or doing something wrong. I have successfully flashed it, no brick and everything working. I would love to give tutorial, but before I do so I must see how many actually need it. :good:
Click to expand...
Click to collapse
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
Droidriven said:
here for the latest roms and fixes for this device
http://forum.xda-developers.com/showthread.php?t=2516498&page=30
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
dijjay said:
I have been driving myself crazy trying to find this information. I would be very grateful to you for the information on flashing the firmware and upgrading to KitKat 4.4 on the SCH S968C. It's impossible to get the info from ST or Samsuck.
Thanks
Click to expand...
Click to collapse
Hi, Did you ever find the rom? I rooted my phone successfully, after much ado with tedious searching all night...any info would be appreciated. thank you!
saucyredhead said:
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
this would be awesome
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
GS3 SCH S-968c its h2, I am trying to update the os to at least 4.4 so I can download an app that currently is'nt compatible with the 4.1.2 jellybean, for my husband. I just rooted it, using odin, first time messing with a phones insides...intimidating but I figured it out. lots of bad information for this phone...can anyone please help me figure out how and where to go to download the update for th os? thank you so much!
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Hi, Did you ever find the rom? I rooted my phone successfully, after much ado with tedious searching all night...any info would be appreciated. thank you!
Click to expand...
Click to collapse
Most of the ROMS from 4.4 and newer require using a SIM and some extra setup to get mobile data(3G) and stock MMS(photo/audio/video messages) working.
Fortunately for you I have a copy of a CM11 4.4 Kit Kat ROM that doesn't require a SIM for mobile data(3G) to work, the only down side is that you can't use the stock MMS app, you'd have to use some kind of 3rd party texting app such as GoSMS or Textra or Chomps or a similar app.
If you want to have working stock MMS then you'll need a CDMA SIM card.
A GSM SIM will not work. A SIM from AT&T/T-mobile or any network under them won't work, neither will the AT&T/T-mobile SIMs from the Straight Talk BYOP activation package, it has to be CDMA.
I can help you painlessly get the SIM set up and APNs configured correctly so that MMS works. Any CDMA Verizon 4G/LTE(you'll need a previously activated SIM if you use a Verizon SIM, it won't work if it's a never been activated SIM from Verizon) or a Tracfone CDMA SIM will work, or any of Tracfone's subsidiary networks (Total Wireless/Net10/Straight Talk/etc..)
As for ROMs, I suggest one of the following:
1) the d2vzw CM11 4.4 that I have a copy of along with a SIM(you'll have working stock MMS and won't need anything extra) it's a rock solid ROM with the SIM setup correctly and uses less battery than the newer ROMs.
2) d2vzw OctOS 5.1.1 if you can find it, it will need a SIM also to have working mobile data and stock MMS.
3) d2vzw OctOS 6.1.1 if you can find it, needs SIM also.
As for there being bad information out there about this device. I've been posting accurate information about this model number for 3 years or more. I've posted information about this model all over the internet. It is all accurate and works, some information is old and no longer necessary due to processes and methods changing but it isn't "bad" information. The old information can still be used, it just involves more steps and has been simplified over time due to improvements in development for this device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Need to upgrade to at least Android 4.2
"Fortunately for you I have a copy of a CM11 4.4 Kit Kat ROM that doesn't require a SIM for mobile data(3G) to work, the only down side is that you can't use the stock MMS app, you'd have to use some kind of 3rd party texting app such as GoSMS or Textra or Chomps or a similar app."
Can you help me? You seem to be very knowledgeable about this phone. My husband just bought a new Galaxy and he gave his old S3 to our seven year old grandson who is one of those kids who loves and understands all things electronic. He has been craving an Android device for some time now. (He already has an iPod touch).
My husband returned the phone to factory settings today and I brought it over to a very excited grandson. My daughter said she was going to use her gmail account to set up the phone and then create an additional account from her account that she could use parental controls on. Alas, this feature only works if you have at least version 4.2 or higher, and this Straight Talk Model S968C has version 4.1.2
This phone will not be connected to a cellular service, just wifi. He doesn't need to be able to send or receive MMS or even texts. He mostly wants to create videos and and download and use some of his favorite apps from Google Play, and use the web (with restrictions that my daughter will set. It won't help to create a separate Gmail account for him because setting restrictions will still not be possible due to the Android Version.
Is there a relatively easy way to do this? I've never done anything like this to a phone before but I'm pretty tech literate and understand most of the terms.
Thank you very much for any help you can provide to me.
Lesa
lirn44 said:
"Fortunately for you I have a copy of a CM11 4.4 Kit Kat ROM that doesn't require a SIM for mobile data(3G) to work, the only down side is that you can't use the stock MMS app, you'd have to use some kind of 3rd party texting app such as GoSMS or Textra or Chomps or a similar app."
Can you help me? You seem to be very knowledgeable about this phone. My husband just bought a new Galaxy and he gave his old S3 to our seven year old grandson who is one of those kids who loves and understands all things electronic. He has been craving an Android device for some time now. (He already has an iPod touch).
My husband returned the phone to factory settings today and I brought it over to a very excited grandson. My daughter said she was going to use her gmail account to set up the phone and then create an additional account from her account that she could use parental controls on. Alas, this feature only works if you have at least version 4.2 or higher, and this Straight Talk Model S968C has version 4.1.2
This phone will not be connected to a cellular service, just wifi. He doesn't need to be able to send or receive MMS or even texts. He mostly wants to create videos and and download and use some of his favorite apps from Google Play, and use the web (with restrictions that my daughter will set. It won't help to create a separate Gmail account for him because setting restrictions will still not be possible due to the Android Version.
Is there a relatively easy way to do this? I've never done anything like this to a phone before but I'm pretty tech literate and understand most of the terms.
Thank you very much for any help you can provide to me.
Lesa
Click to expand...
Click to collapse
Go to settings>about>build number, tell me if it has H1 or H2 on the end of that number.
If you have H1 I can make it very easy for you with just a couple of apps, a good internet connection and about 30-45 minutes.
If you have H2 you'll need a PC, about 1.5 hours and a good USB cord.
Or you can skip all of that and just go straight for the PC method, it works on H1 and H2. You'll probably need to get familiar with the tool that is involved in the process so that you'll know how to restore the device if there are issues later on. The device will be rooted(stock devices do not ship with root access), root means the system partition has been "unlocked" to write permissions, which means the daughter/grandson could inadvertently delete the wrong thing and render the device inoperable.
Of course, you could also remove root from the device, then he wouldn't be able to modify the system partition, he could install and modify/customize everything else though. But that can, in some cases, also cause issues, which then requires flashing the stock firmware via PC or using custom recovery to restore a backup or reinstall your ROM.
This device has the potential to do many things, there are a lot of custom 4.4 and newer operating systems for this device, each with their own flavors of UI and features. If you're not going to have the device activated on a network then you can probably use any of the 4.4+ ROMs without the SIM, probably all the way up to the newest 7.1 or newer builds. Maybe even the new Android Oreo 8.0+ if they build it for this device, someone probably will, the OctOS team still builds new ROMs weekly for this device. If he likes Pokemon Go you might have issues with it seeing that the device is rooted or you might have GPS issues on this device. They can be solved in most cases though.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Upgrading s3
The build number ends in H1.
I wouldn't want it to be easy for him to accidentally render it inoperable.
I have a good internet connection and the time to do this, if you can take me step by step through it. I'm a visual learner, I learn very well from watching videos of people doing things, so I really need clear step by step written instructions. Do you have the time to help me? That would be SO great!
And if it's just as easy to install a more up to date version of the OS, of course I'd rather do that! (and my grandson would be thrilled!)
Thank you so much!
Droidriven said:
Go to settings>about>build number, tell me if it has H1 or H2 on the end of that number.
If you have H1 I can make it very easy for you with just a couple of apps, a good internet connection and about 30-45 minutes.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
---------- Post added at 03:23 AM ---------- Previous post was at 03:17 AM ----------
He probably doesn't care about Pokemon Go. he likes to create his own emojis, make videos with visual and sound effects, use graphics programs, stuff like that. Also loves music and likes to download apps to create his own music. The more photography and graphics stuff he can do the happier he'll be.
I just want him to be able to use it and he can't without the parental restrictions in place. Whatever you recommend, I'll try.
It's H1, cool. You'll be amazed how easy this is. You'll be doing all of this, except downloading your ROM and Google apps, directly from the device.
Use PC to download these files then connect the S3 to PC and copy them to external SD card.
1) download this file, it's the last release of Octos 6.0.1 marshmallow(there is also 7.1.1 available but I haven't used it so I can't verify stability), it's a very good ROM, I used it for over a year on this device, store it on an external SD card as a file by itself, not in a folder.
https://basketbuild.com/filedl/devs...lease/d2vzw/OCT-M-R3-6.0.1-20161025-d2vzw.zip
2) Go to http://opengapps.org/, select:
ARM
6.0
Micro
Then click the red download circle. This is the Gapps(the stock Google apps) package that you need to flash with the ROM, they are flashed separately because they can't be included in the ROM file. Place this file on the SD card with the ROM file, as a file by itself, not in a folder.
Now, on the device:
1) Go to system settings>security> unknown sources and enable it (it will prompt you warning that it can be dangerous to install apps from unknown sources, you only need it to install the Towelroot app to root on the device).
Also, go to system settings>about>build number, tap it repeatedly until you see the message saying you are a developer, this unlocks developer options, go back to system settings>developer options>USB debugging and enable it.
2) using the devices mobile browser, go to https://towelroot.com/ and tap the big red lambda symbol to download the Towelroot app. (you might get a warning about the site being dangerous, don't worry, this is because Google sees the Towelroot app as a virus because it can be used to modify your system partition which is actually what you want, you will be removing root when you're done but right now you need it)
3) Drag down the notification in status bar for the app that you downloaded, tap on it and install the app, once installed, open it, tap the "make it rain" button, you'll be rooted in about 10 seconds, you can uninstall the Towelroot app now, it isn't needed anymore.
4) Go to PlayStore and search for "SuperSU", install it, open it, it will ask you to update binaries, when it asks which method, choose "normal", reboot the device if it doesn't do it automatically. (if you get a prompt asking you to grant superuser permission while doing this, grant it, this is what allows you to write to /system)
5) when the device reboots, go to PlayStore, search for "TWRP Manager", install it, open it(grant superuser permission if prompted at any time while using TWRP Manager)
Now you're ready to follow my guide, starting from the ***FLASHING WITH TWRP MANAGER*** section.
When you get TWRP installed, skip to the ***BACKING UP YOUR STOCK ROM** section and continue from there, you can ignore all the stuff about SIM and APNs. I recommend doing a clean install of your ROM, coming from stock to custom ROM usually causes a bootloop, clean install avoids this. After you get your backup created, read the troubleshooting section in post #2 of my guide, it explains how to perform a clean install, just make absolutely sure that you create your stock backup before you do it. You will be wiping the operating system and everything on the device out before installing the new ROM, don't worry, everything is still safe in the backup you created. This is similar to wiping a PC and reinstalling Windows, the device won't boot without OS so you must flash the new ROM before trying to reboot the device. Sounds scary but it's really simple.
https://forum.xda-developers.com/ga...de-to-flashsetup-sim-apn-cm-cm-based-t3351290
After you get the device signed in with Google, you can go ahead and remove root permission from the device. To do this, open the SuperSU app, open its app settings menu, find the option to "cleanup for unroot and uninstall", it will remove root. Reboot the device and you should be done. You're ready to setup for the grandson.
Just make sure you charge the battery to full before you start flashing the ROM and Gapps, if the battery dies before it is finished, it will damage the device and it's a headache to fix yourself.
If you have questions I'm here.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Thank you!
Thanks so much. I have cleared the rest of my afternoon to attempt this.
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
Did I mention this S3 is from Straight Talk? When I look at a list of supported devices for TWRP, it doesn't list ST as one of the S3s supported. Just want to make sure before I start.
lirn44 said:
Thanks so much. I have cleared the rest of my afternoon to attempt this.
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
Did I mention this S3 is from Straight Talk? When I look at a list of supported devices for TWRP, it doesn't list ST as one of the S3s supported. Just want to make sure before I start.
Click to expand...
Click to collapse
The Verizon S3 d2vzw and the Straight Talk S3 d2tfnvzw are the same device, they use the same TWRP and ROMs. That is all explained in the guide that I created, starting from the top of the thread. My guide has pretty much everything you need to know about this device as far as what you can flash, how to flash it and how to get it set up correctly.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Guide
---------- Post added at 09:09 PM ---------- Previous post was at 08:23 PM ----------
I'm having a little trouble with downloading towelroot to the phone. Found the link/lambda symbol fine. When I tap it to download and swipe down the notifications, it just shows that it's in progress. This went on for about ten minutes before I canceled it and tried again. It's now been about three minutes and it's doing the same thing. I have a very fast internet connection with Xfinity so it's not that. Just keep canceling and trying? (I even tried holding down the lambda symbol and saving the link--same problem). The phone is fully charged. I have unknown sources checked and also USB debugging.
ADDENDUM: I've tried this a few times now. I tried using Chrome to see if that would help--it didn't. The download is in progress for about ten minutes, then says download failed no matter what browser. I've double and triple checked all the settings are correct.
Is it possible to download it to my laptop and transfer it to the phone?
ADDENDUM: finally got it!
Thanks.
Sorry to have so many questions! I appreciate your help.
flashing recovery
Got to the point of using TWRP Manager. Selected device ( Verizon S3 d2vzw) and it downloaded the file and asked if I wanted to flash the recovery and said please make sure the bootloader is unlocked. (I didn't see that in the guide but will go back and look again). I said yes. I got an error message:
Something went wrong
flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now?
I'm just going to leave the phone on until I get your opinion of how I should answer that question. Reboot or no?
Thank you!
lirn44 said:
Got to the point of using TWRP Manager. Selected device ( Verizon S3 d2vzw) and it downloaded the file and asked if I wanted to flash the recovery and said please make sure the bootloader is unlocked. (I didn't see that in the guide but will go back and look again). I said yes. I got an error message:
Something went wrong
flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occurred. Would you like to attempt rebooting to recovery now?
I'm just going to leave the phone on until I get your opinion of how I should answer that question. Reboot or no?
Thank you!
Click to expand...
Click to collapse
I've never had issues using TWRP manager.
Are you sure that you have rooted the device before trying TWRP manager? There is an option in TWRP manager that will show you the "installed recovery" that you have currently on the device, it should tell you whether you have stock recovery or custom. Don't reboot until you're certain that it has flashed the recovery. If it did something wrong before, it might not reboot, slight chance but possible. Still fixable if it doesn't, just more junk to do to get there.
Can you find the folder that TWRP manager downloaded the recovery.img file to? If so, you can install the Flashify app from Playstore, also linked in my guide. Then use it to flash the recovery.img from the folder that TWRP manager downloaded it to. I mention in my guide to use Flashify if you have issues using TWRP Manager.
This should be a simple process, I've done this many times. Since you're having issues, I'd rather have some form of faster communication. Do you know how to use Google hangouts? If you have Firefox on PC you can install the hangouts add-on in Firefox, then I can text in real time to make this much simpler to walk you through. I can send you a PM here with my Gmail address, use it to find me in hangouts and start a conversation thread.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
THANK YOU!
Well, all these hours later, with your amazing patience, I have Android 6.0.1 running on my old Galaxy S3 from Straight Talk!
I can't thank you enough! My grandson is going to be ecstatic!
Thank you again for spending so much time taking me through it step by step!
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
twtoned said:
I was trying to find a custom recovery, or any recovery that will work on my lg realm. I boot recovery and it gives me a error message so im guessing its either wiped out or blocked...any ideas out there on how to correct or replace it
Click to expand...
Click to collapse
Looking for one as well. I have not found one.
Recovery is actually preinstalled
I found this just tooling around. Use your favorite file browser, I used
Total commander. /system/vender/itson
The zip file is there. Hope this helps. (Rooted LG ls620)
Could you explain in a little better detail on what you mean Enigmatic177... I'm pulling my hair out Hehe
If anyone makes or finds a working recovery please post it.
Itson is a zip file that was installed after last update it has the basics to unlock the boot loader. I unpacked it used Rom toolbox pro rebooted to RECOVERY did regular reboot system upgraded.
A couple if bit mapp errors 11111. Then I basically flashed CWM.
Before you do this the partitions change from ext2-ext4. I'd advise
Backing them up.
LG Realm & exceed 2 TWRP recovery/fastboot files
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
TWRP recovery help L620 LG Realm
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
I think i know what seems to be the problem. I think i might have accidentally replaced the boot img with the twrp recovery img. i did not make a backup before this happened. is there anything i can do to make my phone boot up to its normal image? thanks
Nope. It is officially a paperweight and no one I know of has access to the stock ROM either.
Sent from my LGLS620 using XDA Premium 4 mobile app
Hey
Has anybody found a custom rom?
Finally. Easy as pie
Ok, I downloaded an image (w5c_twrp_bumped.img)
put that img on the root of my sd card
downloaded Rashr from the google play store
opened rashr and tapped 'recovery from storage', navigated to external sd and tapped the image and tapped
ýes please'
flashed it. after the flash the phone rebooted into the twrp recovery.
then just rebooted back into the system
worked perfectly.
im new here im not allowed to post outside links yet, just google "w5c_twrp_bumped.img" should take you to a link for a download of that recovery
i got twrp now as a custom recovery. on my lg realm.
That_One_Person760 said:
hello I followed the steps in the read me file and i succeeded in installing twrp although im having troubles booting up to my system os. when i power on my device it takes me straight to twrp. i have a feeling i might of missed a step. i tried creating a backup but i cant because i noticed my screen turns off fast. do you think you might know what might be the problem why i cant boot up to my os? thanks!
Click to expand...
Click to collapse
You have the bumped recovery so all i can say if u messed up is to flash a stock rom u can find on google i had to re flash mine a few times messing with root
right on, thanks for the info. I had no problems at all. it all fell in place like i was hoping. The Realm is the easiest device Iv ever rooted, flashed, and messed with. Well, as far as rooting and flashing a custom recovery. dunno bout roms though. Im sure its simple?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
OK, I grabbed and extracted this. I used Flashify to simply flash the recovery (w5c_twrp_bumped.img) and it works like a dream on my LG Realm.
OTOH, trying the same on an Exceed 2 gets me TWRP, but it cannot mount much of anything and the backup fails. After failing, it tells me "No OS found, continue?" I continue and get the message "Appears your device has no Root, install now?' I am absolutely certain I have root, or wouldn't even be able to run Flashify, so I continue and it simply boots into the OS just fine. Perhaps the readme isn't complete, as I see the following file in the extracted folder (resources.zip) with no explanation of why it's there. It "appears" to be a flash-able zip that installs "itson" (whatever THAT is). Note that the Realm has this in the /system/vendor/itson, yet the Exceed 2 doesn't.
Have you actually used this on an Exceed 2? And if so, what am I missing here?
The_android_Modder said:
No computer needed!!!
Lg realm & exceed 2 twrp custom recovery/fastboot downloade
All you need to do is follow the steps in the read me and you will have the recovery or fast boot to do as you please! Make sure u do a backup!!!!!!
I spent countless hours trying to do this and i finaly got it to work
Now all we need is them roms please make some if you can wold like cm12!
Sorry for not spacing the link im a newb so i cant post links yethttps://mega.co.nz/#!FVQ0GSaI!525LBPtwo696CvZrjY032tKkfS7aaURG-xATm2uzWhw
Click to expand...
Click to collapse
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
petermg said:
Link is DEAD. Any chance you can reupload this file? I can't make heads or tails of some of this thread and I don't want to destroy this phone. Thanks!!!
Click to expand...
Click to collapse
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
fathergweedo said:
I'll do you one better. Just forget about the post you replied to, as it's convoluted as hell. Install TWRP 2.8.6 from here. Ignore the big red warning about the Realm, as he evidently hasn't updated the OP. You can view my notes regarding the Realm in this reply. Tested several times and verified working better than anything else available. Easiest recovery to install I've ever dealt with (all done with an .apk). The option to access via cold boot (battery pull procedure) is something to behold
Be sure to thank the developer, even if you need to create an account to do so. Very VERY nice work!
Click to expand...
Click to collapse
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
petermg said:
THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Before you replied I installed the version 2.8.5 from here:
http://androidforums.com/threads/twrp-2-8-5-0-for-realm-ls620-and-exceed-2-vs450pp.908704/
Is 2.8.6 better? Looks like the 2.8.5 can't be booted into via key combo from power off? Are there any other differences? I just used the Rashr flash tool from the market to flash 2.8.5. Worked flawlessly. This is actually my mom's phone and it wanted to do a system upgrade but I wanted to back it up first so that's the reason I wanted a recovery.
Pretty cool though, this recovery installs just via an APK!!!? That's amazing!
I'm tempted to install this on her phone next time she comes over... it should be fine right?
Thanks again!!!!!!!!!!
Click to expand...
Click to collapse
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
fathergweedo said:
That one will cold boot with the battery pull procedure too. A little further down that thread you'll see I modded it to work correctly with the Exceed 2 in addition to the Realm. I like the 2.8.6 better if only that the dates of the backup are correct now. The 286.apk will work fine and overwrite your current recovery. If you leave it installed, you can always open it and reboot to recovery from within the app. If I have more time I'll post a screenshot, but running late for work. I think the screen dimming/timeout issue was fixed as well, but I haven't verified that. I normally disable that in TWRP anyway, as I like to monitor what it's doing during a backup/restore in case of errors.
Click to expand...
Click to collapse
THANKS!!!! I'll make it a point to flash that to my mom's phone next time I get the chance!
Ok guys, almost first post here, now that its in the right spot. My galaxy tab 2 10.1 model GT-P5113TS is having an issue that I can't seem to find on any site including this one.
Little background, this problem first started several months ago. My wife ran the battery completely dead on the tab, we didn't have a "samsung" charger and couldn't get it to charge up. Bought new charger, got it charged, and ever since then, the screen will work for anywhere from 15-20 seconds to 3 or 4 minutes, then just stops working. Hitting the power button will turn the screen off, hitting it again brings up the lock screen, but the screen will still not recognize any touches. The side buttons still work, just not the touch screen.
Letting the tab sit for a couple hours is the ONLY thing that gets the touch screen working again. But it will only work for a minute or two again before it stops working... again... I tried a soft reset several times to no avail. Kind of forgot about the tab, left it for a few months. Picked it up yesterday after charging it and still no different than a couple months ago. I tried the factory wipe/reset several times using the power and volume buttons and it made no difference. Usually the screen won't stay responsive long enough to make it through the whole set up process.
I'm pretty new to digging into these things. I'm not afraid to give it a shot, since the thing is useless in its current state. But most of the lingo and abbreviations are new to me. If anyone can point me towards a solution, I'd be VERY grateful! I'll do my best to answer any questions to help as well.
PS, we bought it used off ebay, so no warranty. It worked fine for almost a year before this started.
Bump for a little help? Thanks in advance! :good:
Edit: Should also mention that it's 100% unmodified/stock. I haven't rooted it or been inside it or anything. Very open to trying about anything since like I mentioned, it's useless to me as it sits currently.
You can't do much with the screen the way it is, your best bet is to root and flash a custom rom.
Look in development for a root method and install a custom rom using Odin. Check out You tube for videos on the matter you should find several.
Pp.
Help!
PanchoPlanet said:
You can't do much with the screen the way it is, your best bet is to root and flash a custom rom.
Look in development for a root method and install a custom rom using Odin. Check out You tube for videos on the matter you should find several.
Pp.
Click to expand...
Click to collapse
For me th einstalled custom CM11 rom nighlty boots but seems to drop all kinds of android processes. Ik keeps showing all kinds of zip files in the download area. Installed apps can be deeted but are back after reboot. Can't find sd-ext.
Installing stock of custom rom with Odin goes ok for a while but fails all te time.
Is there a low level kind of remedy?
Thanks!
Can you get into recovery?
Use any previous nandroid.
You do have nandroid b/u's ?
Pp.
PanchoPlanet said:
Can you get into recovery?
Use any previous nandroid.
You do have nandroid b/u's ?
Pp.
Click to expand...
Click to collapse
Yeah, I can boot into recovery where it gives me the options to install from SD card etc. And I have to use the power and volume buttons to navigate the options. Thats how I tried the factory reset the first time, to no avail.
I don't have any other backups or anything to try. Where would I go about finding something to use?
Your only option is to reflash your rom or the stock firmware in order to fix the issue.
Use Google to search for the stock firmware, you will have to root again and install CWM.
Pp.
PanchoPlanet said:
Your only option is to reflash your rom or the stock firmware in order to fix the issue.
Use Google to search for the stock firmware, you will have to root again and install CWM.
Pp.
Click to expand...
Click to collapse
Is there an easy to follow how-to for rooting it somewhere? Ideally a way that doesn't involve using the touch screen, since mine is obviously on the fritz.
I'm assuming to reflash the stock files, I'll need to (figure out what files) save them to the SD card then select the restore from SD card option in the recovery menu?
I'm a noob to this stuff, so not familiar at all with the abbreviations and what not. (What is CWM?) But I'm fairly competent if things are broken down to the basic steps and what not.
Well looks like I'm answering my own questions a little bit, but it looks like I can download the VRoot program onto my computer, along with the Samsung USB drivers, and use that program to root the tablet..... correct?
Then download Odin to flash the files?
Not familiar with Vroot, need to look it up.
The first thing you need to do is flash the stock Samsung firmware in Odin (using download mode ) . Afterwards you run your tablet for a while, 2 to 3 hours and make sure it's OK (touch screen wise) , then you can root and flash roms.
Pp.
So I don't need to root it to flash in the firmware, just if I were to flash a rom? Sounds simple enough.
Next (noob) question. Does the firmware have to match with the version of android running on the tablet? I'm not sure what version is on it, I'll have to look after work. Or can I just get the latest firmware update for my model and use that? Looks like for my model there's a version 4.2.2 that says Canada. That seems to be the newest one out there. Is that what I'll want to use?
Follow this video and you should have success. They have an apparent source for the firmware, otherwise you have to download from Samsung and that can take days.
Pp.
http://m.youtube.com/watch?v=A40XVvPPbe0
After watching video there are further steps to fully wipe and factory restore , you don't have to go this far unless you want to make tab new like out of the box.
Pp.
Over the weekend I found a site that had the correct factory firmware, and I was able to download it, install Odin, and flash the firmware into my tablet. I followed the steps for the beginning portion of that video posted and was able to get it done. I then wiped all data and the cache and now I'm happy to report that its back to working like it should! Basically saved me from trashing a $200+ tablet!
Thank you guys so much for the help! And thanks to everyone that makes this site possible. Awesome to have people with this level of knowledge in one place and so willing to help!
:good::good:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!
Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon