Root method for Alcatel OneTouch Conquest 7046t - Upgrading, Modifying and Unlocking

Looking for any information and help on rooting this device. Thanks in advance.

jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I managed to root this device today using king root. The first try failed. I ran it a second time and got it to work. I installed titanium backup which gave a warning that the superuser binary was functional but may cause problems. I installed supersu from the play store and tried to update the binary, which failed, even after a restart. Not sure what that means, perhaps someone more knowledgeable can tell me. I also installed other root apps, SD maid pro and rom toolbox pro, both of which seem to function as they should. I have yet to confirm root with a root checker but I intend to shortly. Hopefully this information will help with further development of this device.

The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
sosthenisRR

King root
King root version 4.5.0 works for Alcatel one touch conquest thank you very much. Titanium backup doesn't like the manager and anticipates problems and recommends superSU. I was unable to install the binary normally but haven't tried using the cwm or twerp option. Busybox 26 installed and I'm new to xda and will continue on the subject.

sosthenisRR said:
The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
Click to expand...
Click to collapse
Success! thank You

Yep, that method works great. I was looking for a.method to.root this device. The only difference was I used this link to switch from KingRoot to SuperSU
androidmtk.com/replace-kinguser-with-supersu
Thanks for the OP

Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?

Need stock rom!!
bmk072 said:
Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?
Click to expand...
Click to collapse
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one

mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
same thing here, except I can't boot into recovery or download. fflashcustom custom twrp from the aforementioned. still won't boot into recovery, hangs at the alacatel logo. what I did was hold down volume and power til it reboots 3&4 times, than it seems to boot back to a android. I even tried the factory restore and it wouldn't do that either. *shrug* imma hafta do more research and find out wtf. but ya, that should fix your sh*t. also. and haven't found the boost stock rom yet either. it's a custom rom, it's not actually lollipop.

Alcatel Onetouch Conquest 7046t rooting, etc.
jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I couldn't find the Alcatel Onetouch Conquest 7046t listed in the list of devices on this site at all, other than in a few posts. Maybe people don't think it's a worthy device to work on? Anyway, enough of that rant, what I would like to contribute here is that I tried using kingroot for my old Motorola xt912 which I had install Dirty Unicorns KitKat ROM on successfully, but lost root on. First it said it couldn't root it, then, after trying again, said it could. I started receiving alerts from Avast staying it has detected viruses, and it seemed to install it's own version of super user, when I already had the one by chain installed.. Which struck me as suspect activity and rose yet more red flags.
I also find it suspect that the users posting here on this thread seem to only be newbies.
Any thoughts or feedback is greatly appreciated. Thanks for reading.
P.S. .. And yes, I am interested in rooting this phone, debloating it, installing custom rooms, etc.

mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work...
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app

I'm not a newbie y
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....

mistaweeks said:
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....
Click to expand...
Click to collapse
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app

CVAngelo said:
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
i tried rooting the new alcatel the same exact way ( usb debugging was enabled both times) and ended up bricking it....i was doing this for my friend...we ended up just going to boost and telling them that there was a defect in the phone they gave him the day before and told them to give him the moto e ( which has so much developement on it its insane)
anyways my friend just gave me the other bricked alcatel one touch conquest and said that if i can fix it i can have it. so i no longer have a duplicate device to work with . can i even flash a stock rom with the original recovery ? im going to try to download the program from alcatels website like you said and see if that works
then if i get it working im going to get the program you were talking about where u said i can make a clockworkmod recovery for it....

CVAngelo said:
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods

mistaweeks said:
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods
Click to expand...
Click to collapse
Uh oh! I think I see the problem here. The Conquest runs a QUALCOMM chip! All along, I've been running with the assumption that this Alcatel was running the MTK chipset. Everything I've described here is thus for naught! Those tools, like SPF and MTK Droid, only work with phones that use the MTK platform. They will not even recognize the Conquest.
My sincere apologies, but I don't even know what tools would even work with this sucker. Oh my God... I'm beside myself with embarrassment...I can't believe I made such a serious mistake.
Sent from my Nexus 7 using XDA Free mobile app

Root Alcatel conquest 7046t
Kingroot rooted mine

can the phone work with GSM sim card. i have one piece which is locked i guess coz am overseas and it doesn't work says invalid simcard

Mcrome1018 said:
Kingroot rooted mine
Click to expand...
Click to collapse
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app

CVAngelo said:
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Mine all works, ad away, root browser etc no clue for firmware though

Related

How Can I Root my Motorola Defy?

How Can I Root my Motorola Defy? all the other threads are from last years, any new way to root it?
I have used SuperOneClick... Rooted my Defy I recently bought then I un-rooted ha ha. That was just so easy that I'm kind of leary about it, so I'm looking for more ways to root than just one click software.
Z4Root
http://forum.xda-developers.com/showthread.php?t=833953
I can confirm that this works on the defy.
1 . Copy the apk over via usb.
2. Then install some kind of file manager from th market
3. You will have to turn on Settings -> Applications -> Unknown Sources
The problem is once you do this ROM MANAGER reports the wrong device so I am not confident to let it flash the recovery image.
If you figure out how to get a recovery image on there let me know.
I suspect flashrec.apk (http://code.google.com/p/flashrec/downloads/list) would work but didn't get a chance to try it before the owner of the Defy left.
Well I re-rooted again after some more searching... Just to have root.
SuperOneClick 1.7 (after root, reboot, than update busybox)
I have yet to try ROMs as I want to make sure I can recover from unforeseen flash failure 110%
On my spare time I try to read up on backing up stock firmware and trying to decide best backup method.
Also I read some where about using defy recovery for flashing... Could be wrong.
But so far all I did was overclock my defy from 300/600/800 to 300/600/1200 on stock firmware. If you want more info on my stock rom pm me, should goto my phone.
Willing to be experiment as long as my phone keeps working.
Sent from my MB525 using XDA App
root motorola defy
Hi, rooting your device is really easy, you just download "Superoneclick" on your pc, connect your device through USB cable and select "Debug USB" from Settings-Apps-development...then just click on "root" and after a short while...rooted!
It should work!

Phone Bricked, can anyone help please??

so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Penley94 said:
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Click to expand...
Click to collapse
The key here is going to be getting back into recovery. Have you tried getting into Download Mode? If you saw the LG logo then you SHOULD be able to get into download mode. Make sure the phone is completely powered off. Connect the USB to your pc but before you connect the other end to your phone, hold volume up then connect it. You should see "Download Mode" on the screen. You will see other directions for download mode but for me this always works, usb to pc, hold volume up then plug the phone in while still holding the volume up. If you can get into Download Mode you can flash a teenybin to get back into recovery following the guide in this thread here.
Currently even if you can get into Download Mode adb might not recognize your phone(at least it never did for me). Once you flash a teenybin using LGNPST, you should be able to get into Recovery. Once in Recovery you can use adb to pull your files off of the phone and onto your computer. I use it from a linux terminal but there are guides available for Windows if that's what you use. The adb guide should be easy to find on xda(just search) so I haven't linked to it. Once adb is set up on your computer AND you can get into Recovery you can use the command 'adb pull /data/media' without quotations and it will copy the contents of your internal storage to your pc. However if you can get into recovery you do have other options for just getting the phone back up and running. This guide here should also help.
If you are familiar with irc(internet relay chat) you can hop onto freenode and enter the #lg-optimus-g channel. As soon as you enter the channel you will see "Need Help? You won't read this but..." followed by a link. All the files for LGNPST, teenybins, and in depth tutorials on fixing a soft brick will be found there. I hope this helps you and hooray for me because this is my 200th post!
PS - If you can't get into Download Mode then your secondary bootloader is gone and there isn't anything you can do(to my knowledge). However, like I said, if you saw the LG logo at all, Download mode should still be an option. Also keep in mind these instructions are for the Sprint(ls970) lg optimis g. I believe the keys are flipped on AT&T/International models(Volume Down when you plug it in to get to Download Mode).
HPTesla said:
The key here is going to be getting back into recovery. Have you tried getting into Download Mode? If you saw the LG logo then you SHOULD be able to get into download mode. Make sure the phone is completely powered off. Connect the USB to your pc but before you connect the other end to your phone, hold volume up then connect it. You should see "Download Mode" on the screen. You will see other directions for download mode but for me this always works, usb to pc, hold volume up then plug the phone in while still holding the volume up. If you can get into Download Mode you can flash a teenybin to get back into recovery following the guide in this thread here.
Currently even if you can get into Download Mode adb might not recognize your phone(at least it never did for me). Once you flash a teenybin using LGNPST, you should be able to get into Recovery. Once in Recovery you can use adb to pull your files off of the phone and onto your computer. I use it from a linux terminal but there are guides available for Windows if that's what you use. The adb guide should be easy to find on xda(just search) so I haven't linked to it. Once adb is set up on your computer AND you can get into Recovery you can use the command 'adb pull /data/media' without quotations and it will copy the contents of your internal storage to your pc. However if you can get into recovery you do have other options for just getting the phone back up and running. This guide here should also help.
If you are familiar with irc(internet relay chat) you can hop onto freenode and enter the #lg-optimus-g channel. As soon as you enter the channel you will see "Need Help? You won't read this but..." followed by a link. All the files for LGNPST, teenybins, and in depth tutorials on fixing a soft brick will be found there. I hope this helps you and hooray for me because this is my 200th post!
PS - If you can't get into Download Mode then your secondary bootloader is gone and there isn't anything you can do(to my knowledge). However, like I said, if you saw the LG logo at all, Download mode should still be an option. Also keep in mind these instructions are for the Sprint(ls970) lg optimis g. I believe the keys are flipped on AT&T/International models(Volume Down when you plug it in to get to Download Mode).
Click to expand...
Click to collapse
Thank you for the response, i just tryed to get in to download mode and it went in to it fine. I would try to do all that to repair it but I dont want sprint to see that its rooted and it I cant have it be fixed when the new phone comes in, the only thing that i want is to get my files from it. Is there any way that I can just do that but leave the phone the way it is? (Not booting up passed the lg logo) I want the new phone because my current Optimus G's battery is going pretty bad I think and I would like a new one.
Penley94 said:
Thank you for the response, i just tryed to get in to download mode and it went in to it fine. I would try to do all that to repair it but I dont want sprint to see that its rooted and it I cant have it be fixed when the new phone comes in, the only thing that i want is to get my files from it. Is there any way that I can just do that but leave the phone the way it is? (Not booting up passed the lg logo) I want the new phone because my current Optimus G's battery is going pretty bad I think and I would like a new one.
Click to expand...
Click to collapse
There are plenty of ways to get it stuck at the lg logo, sometimes it happens just from dirty flashing a rom, sometimes because you install a rom without wiping dalvik/cache. But you should know if you are on Sprint, one of the reasons I stick with them(even though their coverage is horrible in my area) is because rooting DOES NOT void your warranty with Sprint. They will warn you against it but they are the only carrier that allows rooting and will still fix your phone. Here is some info on that here. They won't advertise it but it's the truth. But bricking your phone intentionally is pretty easy I think. After getting back your data, just go into recovery and start deleting stuff you normally wouldn't. It's similar to opening up your car's hood and saying "This looks important" and ripping it out, lol. At this point that's what I would do, fixing your rooted phone is within their warranty, replacing it(which is what you want) I'm not 100% on. Although the post I linked to, says even ordering a replacement on a rooted phone is covered. Its in a reply on that page, you'll see another link. So you could get your info, use a different LGNPST file to set your phone back to factory(which will relock the bootloader and lose root) and then you can do what you did to get there in the first place or root it and start deleting important files with a root explorer to get it back to being stuck. Hope this helps.
HPTesla said:
There are plenty of ways to get it stuck at the lg logo, sometimes it happens just from dirty flashing a rom, sometimes because you install a rom without wiping dalvik/cache. But you should know if you are on Sprint, one of the reasons I stick with them(even though their coverage is horrible in my area) is because rooting DOES NOT void your warranty with Sprint. They will warn you against it but they are the only carrier that allows rooting and will still fix your phone. Here is some info on that here. They won't advertise it but it's the truth. But bricking your phone intentionally is pretty easy I think. After getting back your data, just go into recovery and start deleting stuff you normally wouldn't. It's similar to opening up your car's hood and saying "This looks important" and ripping it out, lol. At this point that's what I would do, fixing your rooted phone is within their warranty, replacing it(which is what you want) I'm not 100% on. Although the post I linked to, says even ordering a replacement on a rooted phone is covered. Its in a reply on that page, you'll see another link. So you could get your info, use a different LGNPST file to set your phone back to factory(which will relock the bootloader and lose root) and then you can do what you did to get there in the first place or root it and start deleting important files with a root explorer to get it back to being stuck. Hope this helps.
Click to expand...
Click to collapse
Oh wow I never knew that but that helps a lot thanks for the help, the sprint guy said theydid a master reset or hard reset or soemthing like that, does that mean it deleted all my pictures and everything? And i understand what you mean to rebrick it that's pretty simple. When i get my new optimus is there a new root out for the update? And what roms do you prefer?
Penley94 said:
Oh wow I never knew that but that helps a lot thanks for the help, the sprint guy said theydid a master reset or hard reset or soemthing like that, does that mean it deleted all my pictures and everything? And i understand what you mean to rebrick it that's pretty simple. When i get my new optimus is there a new root out for the update? And what roms do you prefer?
Click to expand...
Click to collapse
If they did a hard reset it is possible that it wiped everything but not a definite. I purchased my phone from Best Buy and was on zvb. When the zvc update came through it messed my phone up(which is why you don't take OTA's once rooted without further knowledge/modifications) so I took it to Best Buy and they said they did a hard reset to fix it. It worked, my phone booted back up and my internal was fine. However, that's Best Buy and they barely know what they are doing so it may have been a soft reset, I am not 100% sure. As for a new root for the update, I received another phone shortly after because the glass back on mine broke and Best Buy replaced it with a whole new phone. It was on zvc and I used an app named Framaroot with the Gandalf exploit option and it worked fine for me. I have heard of others having issues with that method but for me, it worked and has stuck.
Fiddy619's universal root method seems to be the preferred way for our phone, look in the general section here for a thread by engine95 to see what I mean. After I rooted with Framaroot I then used FreeGee and unlocked the bootloader then made a total nandroid backup of my stock in TWRP before going further. I also copied the backup to my PC just in case.
As for my preferred roms, if we are talking about Android 4.4 both Vanir and PSX are my personal favorites. However as you can tell from my signature I am still using stock zvc android 4.1.2. I have flashed just about every rom available for our phone but my daily driver is stock that I have modified manually(different kernel, removed bloat ware, minor modifications and tweaks, etc). For android 4.3 I have had the best experience with CM10.2 and cfxe. I have not tried CM11(based on 4.4) for awhile but it seems to have overwhelming support - Cyanogenmod usually does.
Really when it comes to roms it's personal preference. They are all very similar with different tweaks/additions. As for which one is the most stable that is also a tricky question. Even though we have the same model of phone, I have seen how picky they can be from one to the other. My roommates have the EXACT same phone, installing CM10.2 worked fine for two of us, but one lost GPS and I had to fix it.
My best advice for when you get your new phone is to backup your working stock and then have fun flashing different things making sure you follow the instructions per rom exactly. It's always a good idea after making your backup(if planning to install another rom) to wipe everything except your internal storage and do a clean install of the rom and gapps. Then, test it for a day or so because sometimes it takes time to settle in. It's a shame that Optimus DE gave you issues, it was rock solid for me, again, these phones are picky! But one of the main reasons I stayed with stock is because the AOSP based cameras leave much to be desired when compared to the LG camera. Again it's just personal preference because some don't like the lg camera.
If you have any other issues or questions I will be glad to help if I can. A lot of the people you see who are active on the forums are very knowledgeable, as long as you ask politely most will be glad to help.
HPTesla said:
If they did a hard reset it is possible that it wiped everything but not a definite. I purchased my phone from Best Buy and was on zvb. When the zvc update came through it messed my phone up(which is why you don't take OTA's once rooted without further knowledge/modifications) so I took it to Best Buy and they said they did a hard reset to fix it. It worked, my phone booted back up and my internal was fine. However, that's Best Buy and they barely know what they are doing so it may have been a soft reset, I am not 100% sure. As for a new root for the update, I received another phone shortly after because the glass back on mine broke and Best Buy replaced it with a whole new phone. It was on zvc and I used an app named Framaroot with the Gandalf exploit option and it worked fine for me. I have heard of others having issues with that method but for me, it worked and has stuck.
Fiddy619's universal root method seems to be the preferred way for our phone, look in the general section here for a thread by engine95 to see what I mean. After I rooted with Framaroot I then used FreeGee and unlocked the bootloader then made a total nandroid backup of my stock in TWRP before going further. I also copied the backup to my PC just in case.
As for my preferred roms, if we are talking about Android 4.4 both Vanir and PSX are my personal favorites. However as you can tell from my signature I am still using stock zvc android 4.1.2. I have flashed just about every rom available for our phone but my daily driver is stock that I have modified manually(different kernel, removed bloat ware, minor modifications and tweaks, etc). For android 4.3 I have had the best experience with CM10.2 and cfxe. I have not tried CM11(based on 4.4) for awhile but it seems to have overwhelming support - Cyanogenmod usually does.
Really when it comes to roms it's personal preference. They are all very similar with different tweaks/additions. As for which one is the most stable that is also a tricky question. Even though we have the same model of phone, I have seen how picky they can be from one to the other. My roommates have the EXACT same phone, installing CM10.2 worked fine for two of us, but one lost GPS and I had to fix it.
My best advice for when you get your new phone is to backup your working stock and then have fun flashing different things making sure you follow the instructions per rom exactly. It's always a good idea after making your backup(if planning to install another rom) to wipe everything except your internal storage and do a clean install of the rom and gapps. Then, test it for a day or so because sometimes it takes time to settle in. It's a shame that Optimus DE gave you issues, it was rock solid for me, again, these phones are picky! But one of the main reasons I stayed with stock is because the AOSP based cameras leave much to be desired when compared to the LG camera. Again it's just personal preference because some don't like the lg camera.
If you have any other issues or questions I will be glad to help if I can. A lot of the people you see who are active on the forums are very knowledgeable, as long as you ask politely most will be glad to help.
Click to expand...
Click to collapse
Okay Im going to try some new roms out when I get my new phone, I would like to try out an AOSP Kitkat Rom but I couldnt get one to flash last time I tryed but I will figure that out later when I get it. Now back to my Bricked Optimus, I want to try the teenybin method although I dont understand the directions... the second step tells me to flash but how can I do that without recovery? and it doesnt say anything about entering in download mode which is the only thing I can do, am I forgetting something? And thank you for the help Tesla I really appreciate it, Ive had more assistance from you than anyone else.
Penley94 said:
Okay Im going to try some new roms out when I get my new phone, I would like to try out an AOSP Kitkat Rom but I couldnt get one to flash last time I tryed but I will figure that out later when I get it. Now back to my Bricked Optimus, I want to try the teenybin method although I dont understand the directions... the second step tells me to flash but how can I do that without recovery? and it doesnt say anything about entering in download mode which is the only thing I can do, am I forgetting something? And thank you for the help Tesla I really appreciate it, Ive had more assistance from you than anyone else.
Click to expand...
Click to collapse
Are you a windows user? The teenybin isn't flashed from recovery it is flashed from a tool called LGNPST which is a Windows program. I am going to private message you a link. It will have links for downloading and installing LGNPST on your PC. It says that you will lose all your data but if you are using the teenybin you shouldn't. It's LG's tool for flashing firmware and gives that warning regardless of what you flash. And you're welcome, coming from an EVO 4G this phone is very different and plenty of people have helped me - just paying it forward.
HPTesla said:
Are you a windows user? The teenybin isn't flashed from recovery it is flashed from a tool called LGNPST which is a Windows program. I am going to private message you a link. It will have links for downloading and installing LGNPST on your PC. It says that you will lose all your data but if you are using the teenybin you shouldn't. It's LG's tool for flashing firmware and gives that warning regardless of what you flash. And you're welcome, coming from an EVO 4G this phone is very different and plenty of people have helped me - just paying it forward.
Click to expand...
Click to collapse
Hey I got in to recovery through the Teenybin although the reset that they did deleted all of my stuff so Im kinda bummed:/ but its okay cause I got my new Optimus today and its brand new so Im happy with it. Thanks again for all of the help. Thats funny that you used to have an EVO 4G because I had it for so long and thats the phone I switched back to when my LG got bricked, but let me tell you Im glad to be back to the Optimus haha the EVO 4G is just way to slow anymore. Now that I have this new Optimus which root method should I go with? Its currently runnning ZVB (4.1.2) should I update the software? It says theres a software update available but I know that sometimes they dont have roots out for those updates so how should I start with this process again with the new phone in your opinion? I havnt done this in forever (going on a year) so I cant really remember everything that I had to do.
Penley94 said:
Hey I got in to recovery through the Teenybin although the reset that they did deleted all of my stuff so Im kinda bummed:/ but its okay cause I got my new Optimus today and its brand new so Im happy with it. Thanks again for all of the help. Thats funny that you used to have an EVO 4G because I had it for so long and thats the phone I switched back to when my LG got bricked, but let me tell you Im glad to be back to the Optimus haha the EVO 4G is just way to slow anymore. Now that I have this new Optimus which root method should I go with? Its currently runnning ZVB (4.1.2) should I update the software? It says theres a software update available but I know that sometimes they dont have roots out for those updates so how should I start with this process again with the new phone in your opinion? I havnt done this in forever (going on a year) so I cant really remember everything that I had to do.
Click to expand...
Click to collapse
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly what he said, framaroot was quick and easy for me, but the lgog is so damn picky and fiddy seems to be the preferred method so use it just to be safe. I had zero issues with framaroot but I think I've just been lucky. And definitely update to zvc before doing either. I'd also update prl and profile for good measure.
That sucks that you lost all of your data, they must have actually did a hard reset where as BestBuy told me they did a hard reset and actually did a soft reset. But it's BestBuy so I never expect much. I softbricked my lgog the day after I got it using the GAIO tool(before finding out about FreeGee) and they fixed it with a soft reset. The guy called the manager over and the manager asked me if I tried unlocking the bootloader and I played dumb. My exact words were "What the hell is a bootloader?" and he immediately fixed it. But I was shocked anyone at BestBuy would even know that. Lmao.
As for my EVO, the micro usb port broke so I was charging it for two months like MacGyver, literally stipped the usb charging wire and hooked it straight into the positive/negative terminals in the battery while turned off! It was a fire hazard but it did the trick, lol. And luckily it had external sd(my one big gripe about the lgog) so I could still get my stuff off of it even without usb. I did love that phone, but you're right, it's incredibly slow now compared to the wonderful lgog.
And as always you are quite welcome!
---------- Post added at 07:39 PM ---------- Previous post was at 07:30 PM ----------
Penley94 said:
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
Click to expand...
Click to collapse
I think the reason I say framaroot is bc its also super easy, install the app, pick gandalf exploit and it will do it's thing - done without ever connecting to a pc. But @engine95 is right, fiddy is more stable so use that. As for TWRP, I love 2.5.0.0 but for KK roms you have to use the one that comes with updated FreeGee, TWRP 2.6.3.x because of the SELinux changes Google made with 4.4. TWRP 2.6 was unstable originally but has since become just as stable as 2.5 according to most. OpTimuS DE was rock solid for me, as for getting some of the G2 apps, I'm not certain. It's doable but I don't know how difficult it would be because I've never tried to install them elsewhere. And I already gave you my choice of best current KK roms but today I found out a few guys are trying to get OMNI official for us. When that happens I think I will be switching to OMNI because they have been producing some impressive commits/tweaks that you won't find elsewhere. Just look through xda news to see what I mean, OMNI is on a roll!
Penley94 said:
The fiddy universal looks easier to me so I will probably use that although its not very Important which ever one is better I will use, and what recovery do you think is better? I used TWRP before but is the other one any better? I will probably go with that anyways Im just trying to get some opinions in. And what ROM do you use? I think Im gonna start out with the stock rooted ROM but theres still some stuff I want from the DE ROM like the G2 keyboard and other features from the G2, is there any way I can get those? And have you had any experience with the KitKat ROMs? Those interest me too
Click to expand...
Click to collapse
I prefer TWRP just because that has always been our best one since the beginning. Now that all the versions of the OG are coming together though both are fine.
I like stock, but Lrod's OpTimuS 5.0 is my daily. The G2 adds he made got me hooked.
If your gonna try to pull some stuff from DE, check with Lrod. He's made alot of changes to a lot of files making it difficult. For me at least.
I've ran all the KK Roms and I liked them all. PSX is probably my favorite though. I liked Liquid in its early days, pre KK. I'm not sure it's up to KK yet.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
I prefer TWRP just because that has always been our best one since the beginning. Now that all the versions of the OG are coming together though both are fine.
I like stock, but Lrod's OpTimuS 5.0 is my daily. The G2 adds he made got me hooked.
If your gonna try to pull some stuff from DE, check with Lrod. He's made alot of changes to a lot of files making it difficult. For me at least.
I've ran all the KK Roms and I liked them all. PSX is probably my favorite though. I liked Liquid in its early days, pre KK. I'm not sure it's up to KK yet.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again, I think you're right on all fronts. Liquid was smooth(heh) but it hasn't been long since we received an official 4.3 so I don't think they're up to 4.4. And same goes for the G2 apps, sometimes it's as simple as pulling an apk out of a zip and pushing it to system/apps and changing permissions but I think Lrod did a lot of work to get the G2 apps working on our phone because they required certain dependencies/modified frameworks.
engine95 said:
Let your phone update before rooting and unlocking. You should end up with ZVC.
Then, you have a choice on rooting. @HPTesla will say Framaroot. I'd say use fiddy Universal root.
Then DL FreeGee from the Playstore, use the"mako" version of TWRP/CWM, your choice, I'd do with TWRP and you'll be unlocked.
Back it up in recovery and you'll be good to go.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay so I rooted it through fiddys universal root but when I try to go on to FreeGee it just doesnt want to open for me? Ive tryed a lot of times and I get nothing it will either send me to the playstore to an app called busy box or will sometimes restart my phone, Im confised I have no clue what to do? I tryed to uninstall and reinstall and nothing I installed the busybox app but it said I didnt have root permission or there was a problem getting the root or something like that.
Penley94 said:
Okay so I rooted it through fiddys universal root but when I try to go on to FreeGee it just doesnt want to open for me? Ive tryed a lot of times and I get nothing it will either send me to the playstore to an app called busy box or will sometimes restart my phone, Im confised I have no clue what to do? I tryed to uninstall and reinstall and nothing I installed the busybox app but it said I didnt have root permission or there was a problem getting the root or something like that.
Click to expand...
Click to collapse
You have to root before unlocking.
Make sure your phone has at least 70 percent charge or more!!
Go to Settings: Settings>Security>Unknown sources checked: Settings>Developer Options>USB Debugging checked, Settings> Display>Screen Timeout - at least 5 min
from fiddy thread.
Directions
1. Unzip the zip file
2. Make sure USB Debugging is on, and you are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt. (Can now be run as admin if you wish, Still works running as regular user tho. Thanks robisodd)
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done.
You shouldn't have any issues.
If you do, then try Framaroot. http://forum.xda-developers.com/showthread.php?t=2130276 and follow those directions.
Follow this. http://forum.xda-developers.com/showthread.php?t=2050582 It has all the info on rooting and unlocking
Edit. You may have to root as admin/not admin, try both.
Edit #2 Also, do not use USB 3.0 ports. They are iffy for this stuff. LGNPST included
engine95 said:
You have to root before unlocking.
Make sure your phone has at least 70 percent charge or more!!
Go to Settings: Settings>Security>Unknown sources checked: Settings>Developer Options>USB Debugging checked, Settings> Display>Screen Timeout - at least 5 min
from fiddy thread.
Directions
1. Unzip the zip file
2. Make sure USB Debugging is on, and you are in Charge only Mode
3. Run the CurrentRoot.bat, wait for the prompt. (Can now be run as admin if you wish, Still works running as regular user tho. Thanks robisodd)
4. Change to MTP Mode
5. Just ignore when your computer asks how to view files on your device.
6. Press enter in the CMD prompt to continue.
7. Done.
You shouldn't have any issues.
If you do, then try Framaroot. http://forum.xda-developers.com/showthread.php?t=2130276 and follow those directions.
Follow this. http://forum.xda-developers.com/showthread.php?t=2050582 It has all the info on rooting and unlocking
Edit. You may have to root as admin/not admin, try both.
Edit #2 Also, do not use USB 3.0 ports. They are iffy for this stuff. LGNPST included
Click to expand...
Click to collapse
Okay i will try this later when i have access to a computer, but the last root i tryed told me it was successful although it didnt restart my phone or anything it just said it was in the command prompt. I will try again cause i dont think it did anything. But i have a question about roms, i am most likely going to flash the DE 5.0 again because i like it with the g2 keyboard and i kind of like the lg feel to it but the only problem is google play music always gives me an error when im playing songs and it always has. I heard aosp roms dont have that problen so in your opinion what is the most stable aosp rom with all features working like gps and everything??
Penley94 said:
Okay i will try this later when i have access to a computer, but the last root i tryed told me it was successful although it didnt restart my phone or anything it just said it was in the command prompt. I will try again cause i dont think it did anything. But i have a question about roms, i am most likely going to flash the DE 5.0 again because i like it with the g2 keyboard and i kind of like the lg feel to it but the only problem is google play music always gives me an error when im playing songs and it always has. I heard aosp roms dont have that problen so in your opinion what is the most stable aosp rom with all features working like gps and everything??
Click to expand...
Click to collapse
AOSP SuperNexus has been getting good reviews here in the forums but I haven't tried it yet. I would give that one a shot though. I'd flash GAPPS standard with it instead of GAPPS core as well. This is just generally speaking with any of the AOSP roms.
The directions @engine95 gave you for fiddy are spot on(as usual ), specifically having the phone in charge only mode instead of mtp. I think a lot of people have missed that step and it won't work in mtp. Using usb 2.0 is another good tip.
And if your phone didn't reboot, you probably arent rooted. Easiest way to check that you are rooted is by going into the app drawer and seeing either Superuser or SuperSu app. If it's there, you're rooted, if not, it didnt work. If it said it worked but didnt reboot, Im assuming you rebooted manually? It sounds silly but sometimes it's as simple as that. But again, after rebooting if one of those apps arent there, you are not rooted.
EDIT: I've never tried rooting with fiddy without being in charge only mode, Im wondering if being in mtp may install supersu/superuser app but not the binary? Probably not but I could be wrong. Just wondering if there is any possible way that the app could be there but you still wouldn't have root privileges. For me, if the app is there, I'm rooted but I don't pretend to know everything(far from it, lol).
EDIT#2: Once you are rooted and recovery is installed, here is the link to SuperNexus.
EDIT#3: And I can't stress this one enough....after rooting and unlocking the bootloader, before flashing ANYTHING, make a full backup of your stock AND copy the TWRP folder(with your backup in it) to a computer, JUST IN CASE! That way you will always have a backup elsewhere, even if something goes wrong with your phone's internal storage. Better safe than sorry!!! And it's also best to copy the entire TWRP folder.
@HPTesla You're on a roll!
Go with everything he's said.
I don't use Google music ,so I'm of little help there.
Almost every ROM has its quirks, and it's just a matter of finding the one that does what you need/want.
Our devs have given us a lot of options. And I know, I sure appreciate them.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Penley94 said:
so yesterday i installed the new optimus de rom and it started up fine and everything was okay, then today i realized my 3g wasnt working and usually thats no big deal because all i have to do is restore my efs in the app FreeG (I think thats what its called, I might be wrong). Well right after i did that, i hit restart phone and it turned off then wouldnt come back on. Then i finally got to the LG symbol but it will turn off then the screen will be on but will just show black. I cant boot in to recovery nor can i do anything on it at all, when i plug it in the charger it says "battery.png is missing, battery: 75%". I took my phone in to sprint and they did a reset although that didnt do anything so there sending me a new one. Now my question is, is there any way I can open up my phones folder so i can get my pictures and everything that was on it? My pics were very important to me and i dont want to lose them, thats all i need so if some could help me get them that would be much appreciated, thanks.
Click to expand...
Click to collapse
I ran OpTiMuS for a long time and every time I would try new roms, decide I didn't like or whatever and go back, I'd always have to 1. Dial ##72786# 2. Let it self activate sometimes twice, but usually just once before I would pick up 3g/4g. May have just been my phone but you may try that out if you go back to optimus De. Over all, my favorite stock like rom though.
Sent from my Optimus G using XDA Premium 4 mobile app

Failed root attempt left tablet at the Samsung screen

I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly:

gprorecovery.apk

Where can it be found?
Found and installed. Now just have to figure how to get into recovery?
edekalil said:
Found and installed. Now just have to figure how to get into recovery?
Click to expand...
Click to collapse
1) If you have ADB, connect, allow adb and adb reboot recovery
2) Hardware key combo: Volume Up & Power until LG screen appears, then Volume Down twice, then Power (yeah, looks like game cheat code but it really works)
I thought I had the drivers loaded because I could see my phone in explorer but I must not have the drivers loaded.now how can I find the adb drivers and how do I set them up? Every time I think I am getting somewhere I get thrown way back again. All I want to do at this time is reload the firmware so I can access the ext sd card witch was lost while trying to root and install cwm. I am about to throw this **** aginest the wall wall that way this will be fixed for good.
Use LGUnifiedDriver, it should install both adb and LG drivers
Where can I get a clean download of it? I am running windows 8.1 . I do have a pc with windows xp as well just havent used it in a while.
LG's support site I think, I still use old version, from first time I've flashed something via LGFlashTools.. You can download that and LG Support Tool from there too.
I have the lg support tool installed as well as the lg pc suite and lg flash tool. I will give it a shot using the lgunifidedriver. I wonder when I origanly tring to root and install cwm and then lost the ability to access the ext sd and not being able to boot into recovery. Could it have made my phone not recognizably? I can see the phone in win explorer when plugged in. The pc does not recognize it in device manager. It says it has no drivers.
Other than that the phone works normal (makes calls,receives calls,and such.).
edekalil said:
I have the lg support tool installed as well as the lg pc suite and lg flash tool. I will give it a shot using the lgunifidedriver. I wonder when I origanly tring to root and install cwm and then lost the ability to access the ext sd and not being able to boot into recovery. Could it have made my phone not recognizably? I can see the phone in win explorer when plugged in. The pc does not recognize it ino device manager. It says it has no drivers.
Other than that the phone works normal (makes calls,receives calls,and such.).
Click to expand...
Click to collapse
That sounds like Windows problem more. You don't have any of those all-in-one driver packs for Android devices installed? How did you root it?
Well I read to use lg support tools to install drivers then used geefree app to root checked with root checker witch said it was rooted ok then used gprorecovery.apk to put cwm on it. Witch said it installed sussfully. After I had it done I noticed I could not access the ext sd card nor boot into cwm. I read on anouther android forum about a felle who had the same issues and someone said the geefree app caused the issues with the ext sd and not booting into recovery.the phone all works fine except for the issues. I figured if I could return back to stock 4.4.2 witch it is on now it should be back to stock and I could try again from the beginning. I also read something about not using a 3.0 usb in windows 8.1 to use a 2.0 usb port. I'll have to see what usb port is what on my laptop. I hope this is all making sense.
edekalil said:
Well I read to use lg support tools to install drivers then used geefree app to root checked with root checker witch said it was rooted ok then used gprorecovery.apk to put cwm on it. Witch said it installed sussfully. After I had it done I noticed I could not access the ext sd card nor boot into cwm. I read on anouther android forum about a felle who had the same issues and someone said the geefree app caused the issues with the ext sd and not booting into recovery.the phone all works fine except for the issues. I figured if I could return back to stock 4.4.2 witch it is on now it should be back to stock and I could try again from the beginning. I also read something about not using a 3.0 usb in windows 8.1 to use a 2.0 usb port. I'll have to see what usb port is what on my laptop. I hope this is all making sense.
Click to expand...
Click to collapse
Return it back to Jellybean if possible, use old Jellybean root metod available in the forums, install Freegee and flash TWRP from there, and later update it to newer TWRP on forums. Freegee is a step you can't avoid because it's the only way we can unlock our phones (that I know), and their TWRP doesn't support SDCard (not sure about CWM, but I think it also had that problem, it was long time ago I've used it). E980 can get a bit shady, but it's a great phone, so don't lose your patience yet.
Thanks for the info. I belive I have the drivers installed now, I can see the phone in the device manager of windows and it looks to be good. I will keep you informed as to how it go's.
Sent from my LG-E980 using XDA Free mobile app
Well I got the drivers loaded last night and dod tht lg flash tools tot program to put it back to 20g rather than 20h. Got root and installed cwn just need to see what it takes to get philz if so the first time it did not take. Anyway all is working except my xda apps. Other than that all is good so far as soon as I can figuer and get the phillz working I will search for some roms to put on it. The problem wsa the loose nut behind the steering wheel. I had the phone plugged into a 3.0 usb not a 2.0 and my IT friend helped me with how to deal with windows 8.1 so now I am sorry for all of my aggrovating all with my crazy rantting. So Thanks to all for putting up with me. And thanks to youSquirl man.
edekalil said:
Well I got the drivers loaded last night and dod tht lg flash tools tot program to put it back to 20g rather than 20h. Got root and installed cwn just need to see what it takes to get philz if so the first time it did not take. Anyway all is working except my xda apps. Other than that all is good so far as soon as I can figuer and get the phillz working I will search for some roms to put on it. The problem wsa the loose nut behind the steering wheel. I had the phone plugged into a 3.0 usb not a 2.0 and my IT friend helped me with how to deal with windows 8.1 so now I am sorry for all of my aggrovating all with my crazy rantting. So Thanks to all for putting up with me. And thanks to youSquirl man.
Click to expand...
Click to collapse
You're welcome, I'm glad I've helped.
About Philz recovery, I think you have full info on it's thread. If you need some more help, I'm around somewhere
Thanks again.

Need help badly. No OS cannot boot passed twrp/cwm

Hello. Ive been 3 days with no phone now and am at my wits' end. I converted to developer, and in trying to clean install a ROM, messed something up...badly.
I can flash TWRP or CWM both through Odin, but no roms work at all. All of them get stuck at system.img.ext4 for about 10 minutes and then it fails. I cant flash anything through recovery, either, because neither recovery program can read my SD card for some reason. Ive read up on similar issues, but all of the fixes involve formatting the SD card through a functioning ROM, which isnt a possibility for me. I am desperate at this point...very desperate. Also, Ive tried the XDA IRC rooms but i'm not sure if i even join them correctly, as for days i cant get even a single letter response from any of the listed participants. Ive gotta be doing something wrong. Any help would be greatly appreciated. At this point i dont care if i lock my bootloader forever i just NEED a working phone.
Smartswitch doesnt work because it wont recognize my device, and when prompted for a S/N, nothing works...ive tried everything from the IMEI to the SIM s/n from the original package sleeve.
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
8wrlobo said:
SOLVED:. talked to Samsung reps and confirmed that the note4 in fact has no serial number and that function if the recovery tool doesn't work for them. Did a day or researching on ADB stuff, which was new to me, and got cm13 successfully working via side load. After that, cm formatted the memory card to he readable, and all seems right in my note4 world for now.
Click to expand...
Click to collapse
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
slowpoke2006 said:
So what exactly did you do been trying to get a rom to work on mine that I did the dev convert on. I was on the latest ota update. Got it rooted and flashed a different kernel got it to boot on stock firmware but can't get any other rom to install and boot.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
8wrlobo said:
Yeah Odin and sd card options all fell flat on their faces for me...I never did figure out the system.img.ext4 hangup I got from odin.
In the end, I used Odin (3.9 iirc) to flash twrp. Flashing two or cwm both never gave me any trouble. From there, I downloaded the cm13 latest build from the thread here and followed this guide (http://forum.xda-developers.com/showthread.php?t=2317986). Sideload failed for me as well, but I was able to push the rom to my phone.
I downloaded a adb/fastboot program (https://androidmtk.com/download-minimal-adb-and-fastboot-tool) and in the x86 program files folder for it, made a new folder called FML lol and moved the ROM zip folder into it. Then did
abd push ___________.zip /sdcard/_________.zip. (note that I don't remember exact adb commands...it had been hours of frustration. Definitely consult the experts (not me) here before trying what I did. In the end it worked great. Good luck.
It was my first experience with adB stuff and tons of trialife and and error but I sure learned tons after all the research and frustration.
Click to expand...
Click to collapse
OK so once you were able to get the rom pushed to your phone it installed fine? I just can't get them to install and boot right. What version were you on and did you do safe updates? Guess I'll have to start a new thread on it
Sent from my SM-N910V using XDA-Developers mobile app
I was/am at PA1. I did the smartswitch emergency recovery to stock PA1 and then redid the developer conversion, before having a hangup and wiping everything with twrp...like everything (BAD idea). That is what caused all my odin and sd card woes to begin with.

Categories

Resources