Related
hi all. i just purchased a Ployer Momo8 tablet and it came with Android 4.0 and ICS. i really like the tablet, especially for the extremely low price of $150. my question is, does anyone know of any custom ROMS for this tablet, because it needs serious optimization. especially considering that i have an rooted EVO running a Team Nocturnal ROM fully loaded, so my EVO runs circles around this tablet. i've searched google for custom ROMS for this tablet, but come up with nothing, especially for the 4.0.
Thanks all.
I have this tablet, really nice tablet. A lot of us have downgraded back to 2.3.4 everything seems to work on gingerbread.
I haven't seen any roms, I did put together a recovery for 2.3.4 version. Momo9 seems to have a lot going for it, that's an 7" version of this tablet.
Anyway good luck
Vampirefo
vampirefo said:
I have this tablet, really nice tablet. A lot of us have downgraded back to 2.3.4 everything seems to work on gingerbread.
I haven't seen any roms, I did put together a recovery for 2.3.4 version. Momo9 seems to have a lot going for it, that's an 7" version of this tablet.
Anyway good luck
Vampirefo
Click to expand...
Click to collapse
how do i downgrade to 2.3? does anyone have the stuff necessary to perform the downgrade with some instruction? i've never downgraded before, only upgraded. i'm sick and tired of the force closes on 4.0.
Here is a custom rom, I made a few changes to it so it can be installed on momo8 via my recovery.
http://bit.ly/ykpLXn
Before you install make sure you back up your data and system via my recovery.
once they are backed up place this zip in the zip folder on your sdcard.
if you created directories you should find on your sdcard a folder called momo8, inside that folder are three more folders. backup, updates, zip
this goes in zip folder.
you need to go to advanced options select wipe system, then you can install zip you would need to press home to go back to main screen from there choice install zip follow onscreen instructions. as with backing up wait a bit after zip is installed before pressing home to go to main screen.
If you want to wipe your data, you can do that as well, you would need to wipe data first before wiping system or come back after you installed zip then wipe data.
the custom rom came from this thread.
http://www.slatedroi...-new-firmwares/
---------- Post added at 07:00 PM ---------- Previous post was at 06:56 PM ----------
You can get recovery from here
http://www.youtube.com/watch?v=bz_i9Wk9eR8
or from here
http://www.slatedroid.com/topic/28879-momo8-business-edition/page__gopid__330892#entry330892
downgrade software here
http://bit.ly/xPzDgu
video here, it's for upgrade same instruction but above image is 2.3.4 instead of 4.0
http://www.youtube.com/watch?v=l-cB1Ya11Z4
issues with tablet
First off, I just bought this thing and it is PAINFULLY slow. After doing some research, I have decided I want to downgrade it to 2.3.4 however, I believe that a lot of folks posting tutorials do not use english as their first language. That said, I downloaded this phoenixprousb, which is definately not in english, and it requires an img and a key. I managed to find a fresh IMG, but no one seems to mention anything about a key.
Does anyone know anything about what they mean by .key and is there an easier better way to do this? The only tutorial I can find requires a .key which they dont include.
nachinc said:
First off, I just bought this thing and it is PAINFULLY slow. After doing some research, I have decided I want to downgrade it to 2.3.4 however, I believe that a lot of folks posting tutorials do not use english as their first language. That said, I downloaded this phoenixprousb, which is definately not in english, and it requires an img and a key. I managed to find a fresh IMG, but no one seems to mention anything about a key.
Does anyone know anything about what they mean by .key and is there an easier better way to do this? The only tutorial I can find requires a .key which they dont include.
Click to expand...
Click to collapse
A key? You are about to brick your tablet that is for momo9c which will brick your tablet.
vampirefo said:
A key? You are about to brick your tablet that is for momo9c which will brick your tablet.
Click to expand...
Click to collapse
Then what is this http://www.slatedroid.com/topic/26606-how-to-guide-flashing-updated-firmwarerom-to-ployer-momo9c/
Which is supposed to be the same process for all ployer tablet referenced here
http://www.pandawillforum.com/showt...mware-for-Ployer-MOMO8-business-edition/page2
?
Again, Does anyone have a solution? Anyone?
nachinc said:
Then what is this http://www.slatedroid.com/topic/26606-how-to-guide-flashing-updated-firmwarerom-to-ployer-momo9c/
Which is supposed to be the same process for all ployer tablet referenced here
http://www.pandawillforum.com/showt...mware-for-Ployer-MOMO8-business-edition/page2
?
Again, Does anyone have a solution? Anyone?
Click to expand...
Click to collapse
It's your tablet, brick it if you want, I wont bother trying to stop you anymore.
I just dont understand why there are two seperate processes when they are supposed to be the same procedure. I have livesuite open and its asking me to press PVP for 10s..
PVP?!
God I hate these tabs
SO i managed to flash the tab over to the 2.3.4 clean version listed here but now market doesnt work. Any solutions?
nachinc said:
I just dont understand why there are two seperate processes when they are supposed to be the same procedure. I have livesuite open and its asking me to press PVP for 10s..
PVP?!
God I hate these tabs
SO i managed to flash the tab over to the 2.3.4 clean version listed here but now market doesnt work. Any solutions?
Click to expand...
Click to collapse
Try flashing a clean original 2.3.4. from Ployer site. Use google translator to find download section and type MOMO8A to find the right firmware. It works perfectly on my tab.
Hi guys, i haven't found any MOMO8 theards, so I have to ask here.
I have flashed firmware for LY-F1,but now I can't flash MOMO8 firmware back.
I have tried LiveSuit,all the Phoenix tools but no luck.
Please help me!
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
MORE INFO: I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help
kitu34 said:
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
Click to expand...
Click to collapse
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Are you sure?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
Are you sure it doesn't matter? But why would Rom Manager mention that? That means it is misleading the user and the user can think esp a newbie that his is a old baseband therefore he will not go with the new baseband and land in trouble.
More Info In Case It Is Helpful
I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGMDP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
Edit: Corrected typo -- it's LGMDP.
____________________
Sent from the moon.
Thanks a lot! So kind of you
Syd_M said:
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGDMP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
____________________
Sent from the moon.
Click to expand...
Click to collapse
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
On what basis you say that?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
kitu34 said:
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
Click to expand...
Click to collapse
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
kitu34 said:
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
Click to expand...
Click to collapse
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
grigtm said:
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
Click to expand...
Click to collapse
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
kitu34 said:
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
Click to expand...
Click to collapse
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Confused
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
This is the first step after rooting.Ok
Fastboot mode is Home + Power i just have to do that? Like in rom manager we could do backup of stock can we do all that also with this?
Actually i read at two places how to go step by step,when to backup,going into recovery and wiping & reset the phone then again into recovery and navigate to the zip file of the rom and extract.But i do not know if it is same with Android flash recovery.
New Words For Me...........OMG why i came here hehehe
Syd_M said:
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
Click to expand...
Click to collapse
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
One more important thing
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
I have LG United Mobile driver already installed,that is enough?
kitu34 said:
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
Click to expand...
Click to collapse
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Thanks alot for the concern
Syd_M said:
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Click to expand...
Click to collapse
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
kitu34 said:
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
Click to expand...
Click to collapse
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Stuck in fastboot mode
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
Click to expand...
Click to collapse
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
kitu34 said:
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
Click to expand...
Click to collapse
power off, boot into rom, and verify if recovery was flashed, if not do it again and not from RomManager
I just followed the instructions at XDA
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Click to expand...
Click to collapse
Instructions said to hold these buttons that's it.Now i read somewhere here to do it after LG logo. Fastboot mode started, udc_start()
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...
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!
Ok so here's the situation: I originally modded the K1 tablet years ago and completely forgot what i did, everything was fine until yesterday when for some reason it was off, when I went to turn it on it loaded into the OS but would immediately power off. I went into TWRP (version 2.8.7.0) and made a backup of my OS in that state. Dumped onto my computer (where I have a backup from 2015 as well), wiped my tablet (Dalvik Cache, System, Cache, Data) and grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod from this guide:
https://forum.xda-developers.com/sh...-cyanogenmod-12-shield-tablet-lte-na-t3055043
and this stock rom from: https://forum.xda-developers.com/sh...rom-hyperstock-mra58k-shield-k1-v1-5-t3522897
however my tablet just indefinitely hung at the nvidia shield splash screen.
Honestly ive been at this for 4 hours and I just want a working tablet. I've gotten lost in firmware updates and some "blob" which i still don't fully understand. I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something. (preferably Lineage because I've read good things but I'll settle for a working tablet at this time)
Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too... I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem) or something because everything i touch is making this worse. I need an idiot proof step by step on how to fix this....
WhenSuddenly said:
grabbed a bunch of different ROMs from here to give a shot..... Here's where the problem is: The only bloody roms I actually got to install are Cyanogen mod
Click to expand...
Click to collapse
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
WhenSuddenly said:
I've gotten lost in firmware updates and some "blob" which i still don't fully understand.
Click to expand...
Click to collapse
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
WhenSuddenly said:
I've reached a level of frustration where i'm willing to just throw money at the problem (despite being fairly poor). If anyone wants to make $10 PM me your discord information and if you get a working OS the money is yours I'm sure we can work out some transfer or something.
Click to expand...
Click to collapse
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
WhenSuddenly said:
Well after trying tg to follow the simple advice of "update TWRP" I somehow broke it and now it hangs at the nivdia screen when I try to do that too
Click to expand...
Click to collapse
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
WhenSuddenly said:
I feel like i'm having a huge problem finding files for the original shield tablet (the one they sent out the replacement for due to the battery problem)
Click to expand...
Click to collapse
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.
redpoint73 said:
What happens when you try to flash other ROMs? Is there an error message (if so, what is the specific error?) or otherwise what is the result?
What ROMs did you try (other than the ones named). Were they stock based ROMs, or AOSP? If AOSP, did you flash gapps as required?
Not sure what this means. Did you try to flash a stock recovery. If so, what happened, or where did you get stuck?
Or is this related to one of the custom ROMs you tried to flash?
Don't really expect or need the money. Sounds like you need it more! The whole point of these forums, is for folks to share and help each other. Most often, without the exchange of money. Many of us (myself included) have benefitted from the free contribution of others. So I'm happy to "pay it forward" and help (if I can), without compensation.
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
What happened exactly? You tried to flash TWRP by fastboot (or otherwise?). Did it say the process was successful, or no (if there was an error message, what did it say?).
So when you try to boot to recovery, it just hangs on the logo screen? Can you still get to bootloader?
What kinds of files are you looking for (the lack of specifics is killing me - and my attempt to help you - can you tell?)? Custom ROMs and TWRP, there is no difference between the "pyro" original Shield tablet, and the (2nd gen) K1.
Click to expand...
Click to collapse
Lol ok Sorry for the lacking in specifics so I'll try again from the top to answer all your questions: Regarding the ROMs I tried I just went down the list of all the popular ones on the xda form as it is presently (so Bliss, CM13, Resurrection Remix, Lineage, and a modified version of the stock rom which I can't find anymore)
when I tried to flash these through TWRP they all bounced back with an error (this was after a clean wipe). I can't elaborate further on that as I can't access TWRP any longer on the device but the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13. So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu. On my PC end (running windows 7) when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Sorry for the brief spastic posting I got very frustrated the other day with the tablet but can now look at it with fresh eyes.
Link to the reddit: https://www.reddit.com/r/LineageOS/...d_tablet_original_lineage_failing_to/eh71q5t/
WhenSuddenly said:
the only thing that said was flashed correctly was CM13. Technically speaking this CM13 should still be flashed to the device but I was getting help in a reddit post from Lineage OS (I'll link below) that gave me the advice to update TWRP to the latest version. I got the image file to install through my current TWRP and it said it was installed correctly. However when I tried to reboot my tablet into TWRP it just hung at the Nvidia screen. It also does this when I try to access the OS which should be running CM13.
Click to expand...
Click to collapse
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
WhenSuddenly said:
when I plug in the tablet I can see fastboot in device manager but I tried accessing it through the command menu and couldn't find the device.
Click to expand...
Click to collapse
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
WhenSuddenly said:
So to recap when in the recovery menu whenever I access OS or bootloader I just get it hanging on the Nvidia screen, and when I hit fastboot it just takes me back to the same 4 option menu.
Click to expand...
Click to collapse
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.
redpoint73 said:
Updating TWRP is good advice. Some of the newer ROMs will often not be compatible with older versions TWRP (and can very well be the cause of the errors when flashing the ROMs). And v2.8.7 is a few years old, at this point.
When you flashed CM13, did you also remember to flash gapps (Google apps) in TWRP immediately after? This is mandatory for most AOSP type ROMs (such as CM13). And not booting to OS is an expected result after forgetting to flash gapps.
My recommendation at this point, would be to flash current version TWRP again using fastboot. Of course, you need to connect the PC by fastboot to accomplish that. Which brings us to your related issue:
So what is the exact response when you enter the command: fastboot devices
Does it just hang, or some error message (tell us the specific error message, if there is one).
Make sure your tablet is in bootloader-fastboot mode ("fastboot" should be highlighted or selected - I forget exactly what that looks like on this device, but it is sometimes portrayed with the word FASTBOOT highlighted in red, at the top of the bootloader screen).
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
I think you mean: "in the bootloader menu whenever I access OS or recovery I just get it hanging"
Without bootloader, the screen would not even come on. It would be a paperweight.
Click to expand...
Click to collapse
Sorry for the incorrect terminology its been a while since I've been in the android modding scene.
Anyway when I access the bootloader on my tablet I get the 5 option menu of continue, fastboot protocol, recovery mode, reboot, poweroff. When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
https://drive.google.com/open?id=1zS7FjUB754iSnWal18ch4EiFtHykM0fD
(clearly seeing that I'm having trouble uploading a picture to this website you can tell how far my skill level has degraded in 5 years)
WhenSuddenly said:
When I hit fastboot protocol on the menu it loops back to the same bootloader menu, I have no determinable way of telling if this is fastboot receptive or not. Now on the windows end of things this is what I'm seeing
Click to expand...
Click to collapse
Selecting fastboot shouldn't change much, as to the appearance of the screen. It should be the same bootloader screen (with options) but should have some indication of "fastboot" being the selected mode. Usually near the top of the screen. I can't say exactly what it should look like, as I haven't used my Shield in a long time (since last summer, when I broke the screen).
If you can confirm the tablet is indeed in fastboot mode (take a photo, and post if, if you like) and still no response to the command "fastboot devices" (no quotes), then something may be wrong with the connection. Try another USB port on the computer, or try another cable.
Also, make sure you have the drivers installed on your PC (first item on the following webpage): https://developer.nvidia.com/gameworksdownload#?search=shield tablet