[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2] T-Mobile LG V10[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: What is ADB (Android Debug Bridge) and what is it for?[/SIZE]
There is much to learn, please view everything in the threads OP, here is a very good guide [GUIDE] ADB Workshop and Guide for everyone
Check this also [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 thanks to @Snoop05
[SIZE=+1]Q2: How to enable "developer options"?[/SIZE]
Go to->Setting->General->About Phone->Click 5 times on Build number
After this you will see a pop up message saying that you are now developer. Go back to General tab and you would see Developer Option tab above about device. Check Enable OEM Unlock and USB debbuging.
[SIZE=+1]Q2: How to unlock my bootloader and installing custom recovery?[/SIZE]
[TOOL][BOOTLOADER][RECOVERY][KlicKiT][Jan.01.16]
[SIZE=+1]Q3: What are my choices on a custom recovery?[/SIZE]
Thanks to @KAsp3rd [Recovery][LG-H901] Updated Unofficial TWRP 2.8.7.1
[SIZE=+1]Q4: How do I root my device?[/SIZE]
Thanks to @Chainfire SuperSu
Check this great info also by @bdorr1105 Root Guide for the T-Mobile LG V10
[SIZE=+1]Q5: How to restore to stock if my phone bricked?[/SIZE]
Thanks to @TheJesus [LG-H901] Stock .img Files (Boot, System, and Recovery)
Thanks to @mikeyinid [LG-H901] Stock Images, Device Restore
[SIZE=+1]Q6: How can I Sim-Unlock my phone ?[/SIZE]
Call T-Mobile and request to unlock the Sim-Card using device unlock app that came pre-installed from T-Mobile. Get your IMEI number ready. You need to wait 40 days to be T-mobile user if the phone financed or lease, but you can unlock it right away if you purchased the phone out right without contract. I did it and use it on ATT network with no problem. Thanks to my buddy @markbencze that confirmed it in HERE and @Warrior1975 that also confirmed it in HERE
[SIZE=+1]Q7: I have AT&T Sim-Card what is the (APN) Access Point Name that I need?[/SIZE]
Name: att
APN: pta
Proxy: Not set
Port : Not set
User name: Not set
Password: Not set
Server: Not set
MMSC: http://mmsc.mobile.att.net
MMS proxy: proxy.mobile.att.net
MMS port: 80
MCC: 310
MNC: 410
Authentication type: None
APN type: default,mms,supl,hipri,fota
APN protocol: IPv4/IPv6
Enable/disable APN: APN enabled
Bearer: Unspecified
[SIZE=+1]Q8: Am I required to backup my ROM before flashing anything else?[/SIZE]
No you're not, but it is definitely a good idea and always recommended because if you don't do a backup and then something goes wrong, it means that you'll lose all your apps, data etc. It just saves a lot of hassle.
[SIZE=+1]Q9: How to get a logcat if I'm asked for it?[/SIZE]
Here is a link for learning how to make a Logcat[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
[SIZE=+1]Q10: What does MD5 checksum mean??[/SIZE]
MD5 digests have been widely used in the software world to provide some assurance that a transferred file has arrived intact. For example, file servers often provide a pre-computed MD5 (known as Md5sum) checksum for the files, so that a user can compare the checksum of the downloaded file to it. So this tool are to make sure that you would get same file as the developer uploaded file. Download MD5 TOOL CHECKER
[SIZE=+1]Q11: What is the best ROM/kernel/modem??[/SIZE]
Honestly, there is no "best". It's all based on personal choice. For example; I may like heavily customizing my ROMs where as you may like it to look at stock as possible. The best thing you can do is to just test out different ROMs/kernels/modems and see which you prefer.
[SIZE=+1]Q12: How do I restore a Nandroid Backup?[/SIZE]
Enter TWRP recovery mode again and look for the ‘backup and restore’. Select restore and everything should go back to normal in a few minutes.If you choose the ‘Advanced Restore’ option, you can select which component of the backup to restore – like the boot, system, data or cache .... Reboot to system. Your system is now restored and is exactly same as the time when the backup was made.
*
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
[List of Supporters][Help Thread][Jan.07.2016]
T-Mobile LG-V10 Help Thread and List of Supporters
Please read the FAQ found Here, before asking any questions.
It is quite possible your question may have already been answered
Welcome to the T-Mobile LG-V10 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. To see a list of supporters, see here
List of supporters
... @ted77usa
... @markbencze
... @Rydah805
... @WizeGuyDezignz
... @bdorr1105
... @ZDeuce2
... @TheJesus
... @Warrior1975
Click to expand...
Click to collapse
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligable of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just shoot me a PM!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligable for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette
delete please
I've noticed that Google Now opens kind of slowly on this phone. You may start typing in the search bar, then it will reload and the keyboard will disappear, then you'll have to tap twice to get it back. Finally then you can type and search. I'm just wondering if this is the app or is it only on this phone that it does that..
I haven't flashed a ROM, just rooted the odexed stock ROM.
Sorry to sound noobish just wondering if it's possible to flashfire the marshmallow update? since I don't have access to a pc at the moment
Does anyone know where I can get the default lg apps from
Sent from my LG-H901 using XDA Free mobile app
Been having some bluetooth issues lately. A device will pair then suddenly music will stop playing through bluetooth and play through speakers instead usually after a few minutes, even though the device and phone are still paired. I have seen this occur with multiple bluetooth devices and across 3 different roms. Any ideas?
numel007 said:
Been having some bluetooth issues lately. A device will pair then suddenly music will stop playing through bluetooth and play through speakers instead usually after a few minutes, even though the device and phone are still paired. I have seen this occur with multiple bluetooth devices and across 3 different roms. Any ideas?
Click to expand...
Click to collapse
Did u try flashing another kernel?
R800x_user said:
Sorry to sound noobish just wondering if it's possible to flashfire the marshmallow update? since I don't have access to a pc at the moment
Click to expand...
Click to collapse
I used flashier on lollipop but not sure on marshmallow
Lmax579 said:
Does anyone know where I can get the default lg apps from
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
Did u try LG store?
Sent from my SM-N920T using Tapatalk
ted77usa said:
Did u try flashing another kernel?
Click to expand...
Click to collapse
I've tried stock, EYG Kernel, and the mods by warbeard_Actual. Same issues with all. Usually the issue shows up after a few weeks of usage in each rom, so I doubt it's hardware failure.
Edit: I've figured out the case. When my data connection drops, my bluetooth seems to flip out too. Which brings me to another issue. I've been having data drops close to every 30 minutes now, sometimes more than that. My family who is also on tmobile are not having these issues, so it's no issue with the towers. Not sure what's causing my data drops.
Running Eliminater74's newest ROM, when I text my GF's stock V10, she tells me I'm double-sending every text message. Any way to fix that?
Maticks said:
Running Eliminater74's newest ROM, when I text my GF's stock V10, she tells me I'm double-sending every text message. Any way to fix that?
Click to expand...
Click to collapse
@Maticks
Do u try flashing stock Mms.apk? Never happened to me before.... maybe ask on the Eliminater74's rom thread ..... u might get help or maybe known bug.
Sent from my SM-N920T using Tapatalk
ted77usa said:
Do u try flashing stock Mms.apk? Never happened to me before.... maybe ask on the Eliminater74's rom thread ..... u might get help or maybe known bug.
Click to expand...
Click to collapse
Do you have a source for me for MMS.apk? Also, btw, I'm on Tmobile LG V10.
Maticks said:
Running Eliminater74's newest ROM, when I text my GF's stock V10, she tells me I'm double-sending every text message. Any way to fix that?
Click to expand...
Click to collapse
Have not experienced this issue or seen any other posts about it. Are other people getting double texts from you or just her? Have you tried another messaging app to test and see if that also replicates this issue? I always tell people to use Textra for messaging. Maybe try that or any of the other countless text apps.
Sent from my LGE V10 using XDA Labs
Hello to all,
Respected members I have a LG v10 T-Mobile version with MM 6.0 stock version. I bought the phone today only. I have rooted many phones without any issues or trouble. Today when I used the method described in this thread [ http://forum.xda-developers.com/tmobile-lg-v10/development/tool-t3283944 ]. Now the problem is that I followed all the instructions up to the letter & everything was going ok.
I clicked the install.bat file the phone rebooted in download mode then it displayed that welcome to fastboot & there were a few options. On pc it in the CMD window which opened when I clicked install.bat file
which was present in the zip file I downloaded from the post it was displaying that waiting for device for I think may be 2 or 3 minutes. The it closed after 5minutes & I was seeing a black screen with 2 options with fast boot heading on top. The first option is to press the power button for 10 seconds to restart the phone or press fast reboot from adb. The problem is that I clicked both up & down volume keys after keeping the power key pressed for 10 seconds or more but nothing happened. The screen stayed for atleast 40 mimutes. Now the problem is that When I took the battery out of the phone to restart it booted & then after
lg mobile logo it displays that software not Recognize or Recognition failed. Can anyone please tell me what to do or that it is bricked or not. At the moment there is no bootloop or anything else. The phone is still connected to the pc with usb cable & is in firmware update mode. One more thing I wanted to respected members is that can I remove the phone or not. The phone is connected since 3 hours. I am at the moment download original stock firmware for T-Mobile v10 which MM 6.0. Any help or suggestion is greatly appreciated.
The phone booted to main screen & everything works fine. I also did a hard factory reset. It starts now but the only thing is that it displays that Phone software cannot be checked for corruption. It displays this for atleast 7 seconds & then the boots normally. What should I do. Should I flash the stock tmobile MM6.0 again through LG flash tool. PLease any suggestions r greatly appreciated.
leoforever said:
Hello to all,
Respected members I have a LG v10 T-Mobile version with MM 6.0 stock version. I bought the phone today only. I have rooted many phones without any issues or trouble. Today when I used the method described in this thread [ http://forum.xda-developers.com/tmobile-lg-v10/development/tool-t3283944 ]. Now the problem is that I followed all the instructions up to the letter & everything was going ok.
I clicked the install.bat file the phone rebooted in download mode then it displayed that welcome to fastboot & there were a few options. On pc it in the CMD window which opened when I clicked install.bat file
which was present in the zip file I downloaded from the post it was displaying that waiting for device for I think may be 2 or 3 minutes. The it closed after 5minutes & I was seeing a black screen with 2 options with fast boot heading on top. The first option is to press the power button for 10 seconds to restart the phone or press fast reboot from adb. The problem is that I clicked both up & down volume keys after keeping the power key pressed for 10 seconds or more but nothing happened. The screen stayed for atleast 40 mimutes. Now the problem is that When I took the battery out of the phone to restart it booted & then after
lg mobile logo it displays that software not Recognize or Recognition failed. Can anyone please tell me what to do or that it is bricked or not. At the moment there is no bootloop or anything else. The phone is still connected to the pc with usb cable & is in firmware update mode. One more thing I wanted to respected members is that can I remove the phone or not. The phone is connected since 3 hours. I am at the moment download original stock firmware for T-Mobile v10 which MM 6.0. Any help or suggestion is greatly appreciated.
The phone booted to main screen & everything works fine. I also did a hard factory reset. It starts now but the only thing is that it displays that Phone software cannot be checked for corruption. It displays this for atleast 7 seconds & then the boots normally. What should I do. Should I flash the stock tmobile MM6.0 again through LG flash tool. PLease any suggestions r greatly appreciated.
Click to expand...
Click to collapse
Looks like the thread you used was for lollipop rather than Marshmallow? Sounds like you got it booting up now tho, so if you wanna root, jjst make sure to use a guide for rooting Marshmallow 6.0 [emoji106]
Sent from my LG-H901 using XDA-Developers mobile app
I've got a fun one.
I'm not sure what happened exactly, but after failing to install a kernel for 6.0 MM for my V10, I've lost a bunch... But still have a perfectly working phone?
fast charge, Fastboot, ADB... LG Up and LG Bridge don't recognize my phone anymore, and Windows 10 reports it as "Unknown USB Device (Device Descriptor Request Failed)" in the Device Manager.
I've tried multiple PCs, multiple cables, tried it on my Raspberry Pi and MacBook Pro too... No dice.
I still have TWRP working, I've still got my root going, and I do have xposed framework installed...
The heck did I do that I can't seem to undo?! Help!
Can someone please help me? I just got a T-Mobile LG V10 off eBay. It said the phone would just reboot and apps were crashing. His wife was due for a upgrade so she just got a SGS7. Will I got there's phone working I unlocked the bootloader but am still having some trouble flashing TWRP. But my real problem is that the phone has no sound and the mic isn't working. Everything else works great. Even vibration.
Any help would be much appreciated!
Thank you!
Any Way Out of Brick?
Hello guys I really need your help please. My LG v10 h901 bricked and it was on Tizen v5 custom rom, prior to that it never gave a problem - not even once.
I just received a call with my phone while driving and after a while? I realize no activity. I check & see that it is stuck on the "your device software can't be checked for corruption"
If I remove the battery, put it back & connect the charger, it charges & shows charge progress.
I can get into the factory reset using hardware keys but I can't get to TWRP.
I removed the sdcard and everything seems to be intact without corruption.
There was this one time it got in for some few minutes then restarted to verification stage.
I can get into download mode but in the device manager I see LGE AndroidNet USB Serial Port, It also shows up as LGE AndroidNet USB Modem. I've tried many things including flashtool, lgup and uppercut to no avail.
It doesn't overheat.
Bootloop or just maybe os/recovery failure??
I've tried everything here and on several websites to no avail. I thought of any modification I made to the phone prior to the problem & realize the evening before the bootloop, I installed "Swipe" & "All in One Gestures" to get full immersive look.
On the swipe, there was a time I got a warning & cos I was driving I believe I selected Ok.
Today, I was doing the same setup on my G3 then the warning came up and I read it carefully & selected cancel. I have a feeling that's my problem (it isn't the expected LG bootloop).
It is still stuck on the verification stage . When I checked on flashtool, I realized is no IMEI.
Tried to use fastboot to flash recovery.img boot.img aboot.img and laf.img I got from the tot I flashed TWRP with but it isn't seeing the phone.
Thanks Guys!!!
NB:
Got fastboot to work, see device and reboot command works but all other commands to erase or write images (boot & recovery) had error FAILED(recovery: unknown command)
CC:
@ted77usa
@markbencze
@Rydah805
@WizeGuyDezignz
@bdorr1105
@ZDeuce2
@TheJesus
@Warrior1975
zayidhs said:
Hello guys I really need your help please. My LG v10 h901 bricked and it was on Tizen v5 custom rom, prior to that it never gave a problem - not even once.
I just received a call with my phone while driving and after a while? I realize no activity. I check & see that it is stuck on the "your device software can't be checked for corruption"
If I remove the battery, put it back & connect the charger, it charges & shows charge progress.
I can get into the factory reset using hardware keys but I can't get to TWRP.
I removed the sdcard and everything seems to be intact without corruption.
There was this one time it got in for some few minutes then restarted to verification stage.
I can get into download mode but in the device manager I see LGE AndroidNet USB Serial Port, It also shows up as LGE AndroidNet USB Modem. I've tried many things including flashtool, lgup and uppercut to no avail.
It doesn't overheat.
Bootloop or just maybe os/recovery failure??
I've tried everything here and on several websites to no avail. I thought of any modification I made to the phone prior to the problem & realize the evening before the bootloop, I installed "Swipe" & "All in One Gestures" to get full immersive look.
On the swipe, there was a time I got a warning & cos I was driving I believe I selected Ok.
Today, I was doing the same setup on my G3 then the warning came up and I read it carefully & selected cancel. I have a feeling that's my problem (it isn't the expected LG bootloop).
It is still stuck on the verification stage . When I checked on flashtool, I realized is no IMEI.
Tried to use fastboot to flash recovery.img boot.img aboot.img and laf.img I got from the tot I flashed TWRP with but it isn't seeing the phone.
Thanks Guys!!!
NB:
Got fastboot to work, see device and reboot command works but all other commands to erase or write images (boot & recovery) had error FAILED(recovery: unknown command)
CC:
@ted77usa
@markbencze
@Rydah805
@WizeGuyDezignz
@bdorr1105
@ZDeuce2
@TheJesus
@Warrior1975
Click to expand...
Click to collapse
I no longer have this device and cannot be much help but i do wish you luck
This was 6 devices ago for me, aside from switching to Samsung devices and now the Google Pixel XL, I have no idea how to fix that issue. Sorry.
Sent from my Pixel XL
Related
I picked up this device from walmart for $29.99 with the intentions of learning some new development stuff.I
thought for 30 bucks there's gonna be a lot of these little "duallies" running around why not a cheap candidate?
So far as i can tell there is little info found about this device so I'm looking to collect what little is known about
it in one place in hopes to get a jump on it. First things first, I am responsible for my own actions as you are yours.
If your not sure ask or simply dont do, some of this stuff can brick your device!
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
dont forget to install supersu
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
and busybox afterwards!
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
*RECOVERY*
Downloaded "TWRP Manager" from play store.
twrp settings, I enabled the sd card patch.
Install twrp\device name :l34c\version i instaled: openrecovery-twrp-2.8.4.0-l34c.img
click install... wait... things will pop up..... things will go away... wait some more...
finally a dialogue that states sucess.
***ISSUES HAVE BEEN REPORTED OF LOSING RECOVERY OR THE ABILITY TO ENTER IT AFTER
A WIPE AS WELL AS PROBLEMS BACKING UP AND OR RESTORING.
I have "injected" twrp manager into the system using titanium backup (link2sd will work also). This seems to
prevent any issues I have read about previously mentioned. Also I have successfully preformed backups as
well as restores, both before and after wiping. I have not figured out how to enter twrp recovery upon boot
yet, so be careful of what you do!
*SAFE TO REMOVE APPS*
yet to come
I use "titanium backup" from the play store, still trimming.I can get it down to about 230MB
available "free" ram at the moment but not consistently.
Ok had an issue with a task manager improperly reporting free available ram... true availability was
around 150mb free. There are apps that have to be replaced when removed, for example a launcher
for a launcher but some do not. Again I'm still trimming and experimenting, right now my system rom
around 244mb free. Most every thing I have done has been on the phone its self without the need of a P.C.
*STOCK BACK UP*
Yet to come
Any candidates for a true stock rom? Ive hacked the crap out of this one so far without the need of a back up... i know tisk tisk tisk!
I'm going for a debloated deodexed stock rom, hopefully!
*DRIVERS*
The only ones I could find that actually work. The Verizon drivers mentioned for the g2, not surprising since it runs on vz towers!
http://forum.xda-developers.com/showthread.php?t=2432476
*TETHERING*
using the android wifi tether 3.3beta2
https://code.google.com/p/android-wifi-tether/
all settings untouched except
device profile
lg optimus 3d
device access does work as well as encryption
*XPOSED*
Does work, im using 2.6.1.
*DPI*
The app I'm using for safe keeping to test dpi settings
https://play.google.com/store/apps/details?id=com.oumugai.densityadjuster
200 not working
170 works
160 native
150 works
140 works
130 works
120 works (looks good)
110 works
Temporarily went back to native dpi for debloating purposes. Will revisit later.
After messing with DPI settings I'm having a"contacts has stopped working " when tapping on the phone app.
DPI set to 120 when I noticed. All dpi switches affect lg home launcher
so you will need another launcher.
ok so far thats what i got. whats the nexts step to a stock AOSP rom?
questions and/or constructive comments wecome
reserved
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Any chance you know how to get it in diag mode? I need to connect it to DFS but can't without diag. Thanks for your help!
DrPhant0m said:
I've got a few of these that are bootlooping. They show the LG logo, and then TracPhone Wireless splash screen infinitely in a loop.
Two questions.
1 - Is there any way to recover them? I'm hoping for some sort of a dev tool that I could flash a stock image or something (like Odin is for Samsung phones)
2- When these phones started bootlooping, I installed TWRP on the other Fuels that I have, thinking that I didn't want it to happen to them. My understanding of the TWRP that's installed from TWRP manager doesn't flash a modified boot image, so you can't enter TWRP from a powered off (or in my case, bootlooping) phone. Is that correct? I flashed a custom boot image from elsewhere that allows me to tap vol up at the LG logo to boot to TWRP. Any idea if this is enough of a safeguard to in the even of similar boot loops?
Click to expand...
Click to collapse
My apologies for the delayed response. I have a lot going on in life.
As for recovering them, use the device you have closest to stock to make a backup. Do this before you attach your account or put any thing in to it after a "fresh wipe". To the best of my knowledge there isnt a tool like odin available, i could be wrong though. You can push a back up to the looping devices via adb. in order to do this you must have previously enabled usb debugging. The instructions are available on the web, i my self dont know how to do this. If you can establish an adb connection im sure you can command it to boot into twrp. For setup and testing use one of the devices that doesnt have a problem to establish adb. There is a little info on another thread i created about investigating the boot process the link is in my signature for the defy. Please be patient with me as i have two jobs and a single father, im not a hacker or developer. just a normal guy that is fascinated by my little robot willing to learn any thing. now that I know this thread is becoming active Ill monitor a little closer. Also if there is any thing i can help with ill be glad to do so. Im wanting to get a second fuel just for dev and learning purposes.
Recovery
Is there a way to access recovery on the lg fuel? I am stuck in a boot loop because I disabled the home screen service as well as other things that I did not pay attention to. I do not have a custom recovery installed.
I've never been able to boot to recovery by way of button press. Seems like there's a way to get into boot loader mode though. Just can't remember off the top of my head, I'm at work now and don't have the fuel with me. I'll see what I can figure out in a few hours when I get home. In the mean time you can try button combos upon boot to include the home button. If we can get ADB talking to it there's a chance I can send you copies of the files needed. Give me more details of what you have done just before the boot looping.
Sent from my ALCATEL A564C using XDA Free mobile app
I bought the optimus fuel a few months ago and i've been using it primarily for a music player/run keeping devices during my jogs. I turned off mobile data and i've noticed that i still see signal bars on the top notification area - does this mean that the radios are still on?
I was wondering if there was some way to completely disable the cellular radios so that i could conserve battery life inbetween days where I don't run?
Thanks!
This is a pretty cool app....
https://play.google.com/store/apps/details?id=com.latedroid.juicedefender
Airplane mode and then turn WiFi back on does the trick. "Radios off" = ton more juice
Has anyone found out anything else for this little phone? I have the LG Optimus Fuel. Had it for a few months now. I rooted it as soon as I got it and uninstalled a few system apps like the LG keyboard, the default SMS app and Chrome along with 2 or 3 other Google apps. It's still running fine.
I installed TWRP recovery and a custom boot image so I could boot into recovery by pressing the up volume button. Works great. I made a full system backup and saved it to my external SD card and saved it to my Debian laptop.
Right now I'm just looking for a custom ROM for this little phone but can't find one. I'd love to get Cyanogenmod on this phone but there are none. I'd port it myself but I'm not able to at the moment.
reemobeens19 said:
...
*ROOT*
These are the instructions I followed to root.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
...
Click to expand...
Click to collapse
I'll expand on the above link because no one can view all of the info in that thread w/o registering for that site [PITA].
Load towelroot (www.towelroot.com). Upon running towelroot, press "welcome to towelroot v3" 3-times (quickly). Change 1337 0 1 0 4 0 to 1337 0 0 0 4 0 (change only the ONE to a ZERO), click "make it ra1n" and you're rooted. :good:
This was verified on an L34C running Android 4.4, Kernel 3.4.0+, build KRT16S.L34CV10c, Sw ver L34CV10c.
YMMV; IANAL
My apologies for the inconvenience, I was unaware for the need to register.
What I would like to do with the L34C is find a ROM with all the phone functionality removed, and few to no Google Apps (let me just add the ones I need). I am not planning on using it as a phone (I still have my old Casio flip-phone, need nothing else). My intention was to experiment with creating a PalmPDA "replacement", something small to carry around for addresses, notes/memos, calendar (you know, the stuff you used to do on PalmOS), and in addition figure out how to do record-level synchronization **locally** (as in I don't need to send my data to some dirt-floor shack in Bangalore just to have it sent back to a device 2 feet away from my computer). Additionally, would line to use it as a basic portable media player. Essentially, trying to re-create the Palm LifeDrive on Android.
To my knowledge there are no roms available for this device. Your best bet in my opinion is to remove apps 1 by 1 after rooting. Google each and find out what the risk and severity of removing them are. I have donated my device to a less fortunate fellow employee. So as of now I'm unable to help with testing. This method is what I do for all of my devices until I'm finally happy with its performance and functionality. Think of Android as the swiss army knife of the computer world, you can do just about any thing with it, you just gotta figure out what tools are useful to you and the ones you can do with out, then you gotta ask Google witch ones Android can function with out. I hope you find what your looking for in the little robot, its a really neat world inside there!
I hate to bump an old thread but, I also don't it necessary to start a new one, at least not yet anyway but, I too am looking for a way to flash stock ROM. I have LG34Cs to use as a reference..
Where is the link to exposed framework at for this phone?
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.
Here is working twrp 3.1.1 if anyone interested:
Code:
mega.nz/#!I0lhAYAY!fRbQtQjYFI2kiJOD0FSEBPnBJm0JZxpiBaw52kyOfQE
majexuj said:
All official twrp 3 images are broken on official site. Last good working was 2.8.7.0.]
Click to expand...
Click to collapse
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Mac23 said:
What does broken mean in detail? Do I risk to brick my L34C when I flash official twrp 3 images?
Click to expand...
Click to collapse
Broken as in doesn't boot into recovery. The phone will still boot into android, assuming you have a working system, and within android with root you can flash a working recovery image over a broken flash with the dd command on the twrp device info page (twrp.me/lg/lgoptimusfuel.html). So no real risk of brick, just possible inconvenience that might require a battery pull.
I built twrp 3.2.1 with same sources but I have not tested it since my battery seems to have completely died and the phone won't boot with usb power alone.
Here is link anyway in case anyone is interested:
Code:
mega.nz/#!ssExSY7S!_B3FcAmclzRwCKTX461Tl_QhpdwwK0tmvhL-6zkKLRw
---
This will save you 8-12 hours of your time if you are lucky. This means that it also includes the meaningful links of 8-12 hours of searching. Sentences in italic are important. 1 link is for the Odin official website, the rest are re-links back into XDA.
The device in question is a SM-925T Tmobile S6 Edge.
The problem was this. I rooted my phone and messed around with Greenify and the Play store. To prepare for rooting, I allowed unknown downloads, unlocked the bootloader, and turned my security lock off (I had set it to a finger print lock). After I was done rooting, I immediately locked the bootloader again(<--A mistake that caused my bootloop/ soft-brick). After I was finished messing with the above apps (Greenify, etc), I wanted my phone to restart. So I held the Power button and selected restart, while I was on the lock screen (may not be important). I noticed that it took a long time to restart, and upon closer examination, I noticed another error under the "kernel is not seandroid enforcing" (which appears to be natural for rooted phones). The error was "Custom Binary blocked by FRP Lock". It was a new error. I investigated this new problem using the internet , and this dude was panicking like hell, but he didn't appear to fix his problem. He did hint that returning to the bootloader to its locked state was a mistake. Looked a bit more and this guy pointed to another thread, which introduced me to flashing and more importantly his fix, which was to flash the stock 5.1.1 image through odin. He used this link, which contains all the stock firmware for the majority of the new Samsung S6 and S6 edge versions. To make a long story short, most of these fixes involved flashing your firmware to the stock version. So I went to the Odin Website, and downloaded every version, as a couple threads have said that different versions worked for them. Here is a thread with everything you need for Odin. Now, after sorting through and finding micro USB cables that are detectable by Odin, an important step because Odin might develop a pattern of detecting then failing to detect your device through that cable, and testing all the usb 2.0 ports, I was ready, and had Odin with my stock firmware. Odin kept saying "NAND Write", then in the next line "FAIL". This was annoying as Odin wouldn't detect my device again unless I unplugged it, restarted it to download mode, then restarted Odin before plugging it back in. I got confused and found links for somehow fixing the .tar files, stock roms, .pit files (DO NOT MESS AROUND WITHOUT KNOWING WHAT THOSE THINGS DO), and other threads/websites that say to boot into recovery mode , factory reset, then wipe your cache. I could only do that once. After me messing around with all of the above file variants and supposed fixes to help with my issue, I couldn't boot into recovery mode, it got stuck on the "Samsung Galaxy S6 Edge" logo. It did not fix the NAND write failing. There however, are a lot of websites allowing you to download stock software for your phones, and I don't think I can link them as it might break a rule. Surprisingly, some have claimed that using a stock file for another device worked to fix their problem. This thread, which convinced me to use Smart Switch when it failed for everyone else, was very useful, although I recommend downloading Smart Switch from the official website of Samsung. None of the Odin flashing had worked so far, including the Roms and .pit files so I tried Smart Switch. I opened it, and upon selecting the "more" tab on the upper right corner, a bunch of tabs drop down. One should be "Emergency Software recovery and initialization". I had to find my S / N (Serial) number, and I was very confused on how to obtain that number as I was locked out. But to obtain it, do the same process to boot into download (hold volume down, home key, and power key), but stay on the prompt and don't go to the screen that has the word download in the middle. Don't do anything other then reaching the prompt confirming if you want to install a custom ROM. Then, press the home key and it should show your S / N number along with your IMEI number. Once I imputed the code I saw on my phone into Smart Switch, it told me to connect the device. Now, by this time, I realized that Odin only detects my device if it is actually in the download screen. Why shouldn't my computer? I booted into Download on my phone and followed the steps on my computer, making sure that the computer can recognize my phone while it is using a valid USB port and Cable. And after some waiting, for me, my problem was fixed and I could use my phone again, it reverted to it's out-of-box state. I hope this drawn out but very specific explanation helps you guys. It's my first post And also, this thread confirms that you can use a USB hub for flashing(at least for ROMS), Smart Switch, and for rooting.
Thank you for this detailed account, however nothing of the above has worked for me. Odin won't flash the firmware of 5.0.2 (and I tried 5.1.1) and Smart switch does not recognize the device to do anything. BTW phone has been rooted for months and last night decided to turn on its FRP lock randomly and now I'm stuck. Any help would be greatly appreciated.
Explain throughly what you have tried. Especially different ports, cables, and computers. Did you have the right device drivers? Did you do anything else?
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Xalmey said:
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Click to expand...
Click to collapse
press vol down home keys and power key once you get to the first blue screen release vol and power keep holdind home but I already tried smart swich didn't help
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
EsperaKing said:
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
Click to expand...
Click to collapse
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
callumbr1 said:
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
Click to expand...
Click to collapse
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
EsperaKing said:
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
Click to expand...
Click to collapse
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
callumbr1 said:
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
Click to expand...
Click to collapse
Thank you for you reply.
Please can you tell me where I can find such software or how to do it clearly! I know how to use Odin but I don't know how to exclude user_data to be wiped. Thank you
Bonafid3 said:
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Click to expand...
Click to collapse
Thank you thank you thank you!!! This is exactly what I was looking for I had just rooted my note 4 running 6.0.1 and had no idea what the oem option was as no rooting method talked about it at all so naturally as soon as i added my Google account phone restarted and locked up.
Kies was the answer I needed as frp lock was active in download mode and my factory reset in recovery failed everytime but running Kies firmware upgrade and entering my model and serial number it installed perfectly in download mode with frp lock still active saved me alot of hassle ?
I recently rooted my Lg G stylo (Metro). I was messing around with the Clockwork Mod Recovery. Long story short, I had to reboot into recovery but I keep getting a "Secure Booting Error" "Error code 1003". It keeps restarting over and over again and the same message keeps popping up. The screen doesn't pass the logo, it just shuts down after the error message shows up. repeat
There is no way to access the homescreen or anything. I trying to factory reset by holding the VOLUME DOWN + POWER KEY. It works. I get a menu that says Perform a factory reset , [Yes/NO]. When i click yes, the reset begins but after a while it shuts down and continues to repeat the same message. "Secure booting Error". "Error Code 1003". I have also been able to acces download mode where the screen would say firmware update/Usb. But idk what to do after that. Im pretty sure its not bricked since it still turns on.
Did you unlock the bootloader before you rooted or did you use one-click rooting apps to root your phone?
I have the same problem
mnunez12 said:
Did you unlock the bootloader before you rooted or did you use one-click rooting apps to root your phone?
Click to expand...
Click to collapse
The way mine happend is I tried installing twrp image with flashify and I know I installed it under the wrong one I clicked in the option above recovery anyways now I'm stuck on that.... So please help my warranty is over don't want to get a new phone.
Did figure how to recover phone?
ProblemMaker said:
The way mine happend is I tried installing twrp image with flashify and I know I installed it under the wrong one I clicked in the option above recovery anyways now I'm stuck on that.... So please help my warranty is over don't want to get a new phone.
Click to expand...
Click to collapse
i have the same problem
As a new owner of an LG G Stylo MS631 (the Metro PCS model) I had the same issue just yesterday when working with GameTheory's Katana ROM and he pointed out that when the Secure Booting Error Code 1003 shows up it's because you have to go into the Developer Options (tap the build version 7 times under Settings - About phone - Software Info, back out two steps and then find the new setting just above About phone) and check the box next to "Enable OEM unlock" - this doesn't unlock the bootloader but it does allow you to use tools like TWRP without hassles or some of the reboot to recovery apps.
If you're getting the error and you can't get past it in any respect, you're going to need to flash the factory KDZ to get it truly useful again. That's what I ended up doing because there simply was no other way to get recovery or anything else working.
Flash the KDZ back to pure stock, go into the Developer Options and enable that option (Enable OEM unlock) and then go about rooting/flashing TWRP/etc.
Good luck...
FIXED
br0adband said:
As a new owner of an LG G Stylo MS631 (the Metro PCS model) I had the same issue just yesterday when working with GameTheory's Katana ROM and he pointed out that when the Secure Booting Error Code 1003 shows up it's because you have to go into the Developer Options (tap the build version 7 times under Settings - About phone - Software Info, back out two steps and then find the new setting just above About phone) and check the box next to "Enable OEM unlock" - this doesn't unlock the bootloader but it does allow you to use tools like TWRP without hassles or some of the reboot to recovery apps.
If you're getting the error and you can't get past it in any respect, you're going to need to flash the factory KDZ to get it truly useful again. That's what I ended up doing because there simply was no other way to get recovery or anything else working.
Flash the KDZ back to pure stock, go into the Developer Options and enable that option (Enable OEM unlock) and then go about rooting/flashing TWRP/etc.
Good luck...
Click to expand...
Click to collapse
Thanks. I finally fixed it thanks to this!!!!!
how do I flash the kdz back to pure stock if I can't get past the error message? Please help, thank you!
T mobile kdz file ?
soccereclipse087 said:
how do I flash the kdz back to pure stock if I can't get past the error message? Please help, thank you!
Click to expand...
Click to collapse
Did you get a answer? Also where can I find the kdz file?
Hello, I just soft brick my MS631 this morning. I had the phone rooted perfectly fine withthe katana ROM. Then, I stupidly use the reboot recovery option that is baked into the ROM withough developer options enabled and OEM chec (I forgot). Now, I get the looping Secure Booting Error 1003. If, I do the factory reset step (hold power and vol down) I get to the factory reset options, but when I select YES, it'll go through the loop again. HELP please, as I A) cant afford another phone right now and B) don't want to go back using my Windows 640 LTE phone with MetroPCS.
botbro86 said:
Hello, I just soft brick my MS631 this morning. I had the phone rooted perfectly fine withthe katana ROM. Then, I stupidly use the reboot recovery option that is baked into the ROM withough developer options enabled and OEM chec (I forgot). Now, I get the looping Secure Booting Error 1003. If, I do the factory reset step (hold power and vol down) I get to the factory reset options, but when I select YES, it'll go through the loop again. HELP please, as I A) cant afford another phone right now and B) don't want to go back using my Windows 640 LTE phone with MetroPCS.
Click to expand...
Click to collapse
I did a similar thing. Go to HERE and follow GameTheory's unbrick guide. If you have problems downloading the KDZ like I did, then try getting it HERE
I actually did GT steps right after this post. Im now back on Katana and learned from my mistakes lol
I accidentally used king root without developer mode enabled
I also bricked my phone to the point of it being unusable. I am running on boost mobile and I am using android marshmallow 6.0. My phone said it was rooted after using the 1 Click root app and I went to start it and it now says 'security ERROR MODDED 1003'. I am stressed out at this point and I have reset it via developer menu about 3 times to no avail. I am familiar with rooting and roms but I'm not really used to using code. I'm stock everything and I am running on Boost mobile. If anyone can find a boost rom for me to use it may be possible to put my phone in download mode. I do have an sd card if it is needed to load a zip on. Please help me get my phone booted again! I believe a sprint KDZ may work but I can not find one for download anywhere. Thanks !
This may happened to me too. I am on the Boost version as well. I used the king root app to root the phone then I tried to install the adaway app. When the app told me to reboot the phone, I clicked okay but I hit the secure bootloop. I didn't even try to install a recovery. How do I fix this?!?!?!
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
Micgizel said:
I also bricked my phone to the point of it being unusable. I am running on boost mobile and I am using android marshmallow 6.0. My phone said it was rooted after using the 1 Click root app and I went to start it and it now says 'security ERROR MODDED 1003'. I am stressed out at this point and I have reset it via developer menu about 3 times to no avail. I am familiar with rooting and roms but I'm not really used to using code. I'm stock everything and I am running on Boost mobile. If anyone can find a boost rom for me to use it may be possible to put my phone in download mode. I do have an sd card if it is needed to load a zip on. Please help me get my phone booted again! I believe a sprint KDZ may work but I can not find one for download anywhere. Thanks !
Click to expand...
Click to collapse
This may happened to me too. I am on the Boost version as well. I used the king root app to root the phone then I tried to install the adaway app. When the app told me to reboot the phone, I clicked okay but I hit the secure bootloop. I didn't even try to install a recovery.
What if you cant get the phone to do anything outside of the boot loop?
br0adband said:
As a new owner of an LG G Stylo MS631 (the Metro PCS model) I had the same issue just yesterday when working with GameTheory's Katana ROM and he pointed out that when the Secure Booting Error Code 1003 shows up it's because you have to go into the Developer Options (tap the build version 7 times under Settings - About phone - Software Info, back out two steps and then find the new setting just above About phone) and check the box next to "Enable OEM unlock" - this doesn't unlock the bootloader but it does allow you to use tools like TWRP without hassles or some of the reboot to recovery apps.
If you're getting the error and you can't get past it in any respect, you're going to need to flash the factory KDZ to get it truly useful again. That's what I ended up doing because there simply was no other way to get recovery or anything else working.
Flash the KDZ back to pure stock, go into the Developer Options and enable that option (Enable OEM unlock) and then go about rooting/flashing TWRP/etc.
Good luck...
Click to expand...
Click to collapse
i have tried holding down the volume down button and the power button at the same time but it doesnt do anything.. it makes the error code disappear for a split second and then it just comes back, it doesnt go into a normal boot option.. it doesnt go into a recovery mode of any kind to download anything to it.. can you help?
sherryf said:
i have tried holding down the volume down button and the power button at the same time but it doesnt do anything.. it makes the error code disappear for a split second and then it just comes back, it doesnt go into a normal boot option.. it doesnt go into a recovery mode of any kind to download anything to it.. can you help?
Click to expand...
Click to collapse
I wish I could offer some help but I haven't owned an LG Stylo since I made that post - I literally sold that one the following day. Hopefully someone else might be able to provide some assistance.
Good luck...
br0adband said:
I wish I could offer some help but I haven't owned an LG Stylo since I made that post - I literally sold that one the following day. Hopefully someone else might be able to provide some assistance.
Good luck...
Click to expand...
Click to collapse
Thank you so much for responding to me even though you couldnt help. . i appreciate that..
is there a way to fix it
arbyn said:
I did a similar thing. Go to HERE and follow GameTheory's unbrick guide. If you have problems downloading the KDZ like I did, then try getting it HERE
Click to expand...
Click to collapse
Sorry for the bump on this thread. I followed the unbrick guide mentioned here, and all seems like a GO... except a lost service. Screen Lock says "No Service", but I am receiving text messages from contacts.
lg ls770 (boost)
Lg stylo ls770 boost
My stylo is showing the same error 1003 and on bootloop. Can someone help me figure out where to go to get the fIles to restore it back to stock.
PM or email me if you can help TIA
help
the issue im running into using the tutorial to flash the metro kdz is it says it got disconnected from the server. any ideas?
Evidently I don't have enough posts to post in the proper section (I think), so I'm posting here to raise my post-count, and also explain a situation so someone might be able to point me on my way.
I had originally posted about my S3 that had seen a bad update, but I'm editing the post to keep it up to date.
The initial problem was that I was unable to update my recovery or my OS because of an error from the latest recovery image. The phone was exhibiting strange behavior (auto-connecting to mobile data even when the feature was turned off completely), so I restored my initial update of the factory ROM when I first put TWRP on it a year ago.
The ROM was successfully restored, but all processes would crash immediately when the user unlocked the device, and the phone no longer appeared connected to ADB.
I found that I was able to see the device in ADB (and windows explorer), if it was allowed to boot into Android completely, connected, but still locked. I copied another image to the device, rebooted to recovery, and was able to flash the latest (14.1) LineageOS onto it.
Upon first boot the phone reported that it had no carrier. It seems to have retained all the correct carrier settings (APN, carrier name, etc), but if I got to Carrier Settings under Data Usage/Cellular Networks/... it reports "com.android.phone has stopped" :/
Several hours after sitting idly, the phone appeared to connect to the sprint network correctly, and is now working normally with the exception that the com.android.phone component will crash whenever Carrier Settings is accessed.
Thanks for peoples answers and suggestions.
artician said:
Evidently I don't have enough posts to post in the proper section (I think), so I'm posting here to raise my post-count, and also explain a situation so someone might be able to point me on my way. I had originally posted about my S3 that had seen a bad update, but I'm editing the post to keep it up to date. I was able to flash the latest LineageOS onto my S3. I'm running 14.1. Upon first boot the phone reported that it had no carrier. It seems to have retained all the correct carrier settings (APN, carrier name, etc), but if I got to Carrier Settings under Data Usage/Cellular Networks/... it reports "com.android.phone has stopped" :/. I am currently looking for a more stable LineageOS build to replace this nightly one with. Any other tips would be welcome! Many thanks in advance.
Click to expand...
Click to collapse
First of all... Which d2 device do you have (d2vzw, d2att, d2spr, etc...)?
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
I think it would be best to find out which phone you have and flash the corresponding stock rom via odin if possible. Having a solid base to work from is essential.
If you have no luck with custom roms then it'd be advisable to go back to stock and start over.
Beamed in by telepathy.
I thought I'd posted, but I have the d2spr.
About 2 hours after I flashed the new OS and left the device sitting, it connected itself to the sprint network and has been functioning normally since. Thank you guys for moving, reading and replying to my post!
artician said:
I thought I'd posted, but I have the d2spr.
About 2 hours after I flashed the new OS and left the device sitting, it connected itself to the sprint network and has been functioning normally since. Thank you guys for moving, reading and replying to my post!
Click to expand...
Click to collapse
Patience is a virtue...
Beamed in by telepathy.
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
OnePlus will not do anything due to the warranty being void...
DM me. I can work this out with you. I ran into a similar problem.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
Tried sending it for repair but had the op guy look up my imei and ITS A DAMN DEMO PHONE I GUESS!? Cant return it, bought off amazon refurbrished and due to my anger problems i shattered the screen but other than that i shouldnt of been sold a damn demo phone from the start.
T3CHN0T33N said:
OnePlus will not do anything due to the warranty being void...
Click to expand...
Click to collapse
they would repair it, they even repair tmobiles version and metro and all but it really ticked me that amazon refurbrished sold me a demo phone or the phone is now thinking its a demo phone somehow..
Springles2 said:
DM me. I can work this out with you. I ran into a similar problem.
Click to expand...
Click to collapse
Never discuss in DMs! This person has illegitimate intentions.
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
it's not against the rules it's just not a good idea to do
T3CHN0T33N said:
it's not against the rules it's just not a good idea to do
Click to expand...
Click to collapse
Thank you for the advice! Just wanted to see if I could legitimately help!
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
illegitimate intentions, lol what are you trying to say? didnt know my intentions had any type of rules to be followed.
if oneplus sends people on the daily unlock codes in order to unlock their bootloaders on their phones, shouldnt people be able to explore some other OS's and things of that sort? My intentions were to TEST out GSI's that developers worked hard on to work with certain devices and provide some feedback and hopefully come along one that i can use on the device as a daily.
This is Forums, know your place. I think we are all a lil illegitimately intentional at times dont ya think?
no offense.
Springles2 said:
Thank you for the advice! Just wanted to see if I could legitimately help!
Click to expand...
Click to collapse
Thanks for your gratitude.
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
jerryhou85 said:
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
Click to expand...
Click to collapse
Thank you for explaining it to others who might need it
Also, will never ask for anyone’s personal info or financial info or anything to do with their identity. That is their information and have no interest in knowing more than their username on here
Maatt_OG said:
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
Click to expand...
Click to collapse
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Maatt_OG said:
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Click to expand...
Click to collapse
Please write something up on how you did it! It could save someone!
Springles2 said:
Please write something up on how you did it! It could save someone!
Click to expand...
Click to collapse
Well at times it would just bootloop nonstop after using the msmtool, but then tried entering safe mode and that was a success but remembered each time it went to turn on the wifi to set up the phone it would freeze and bootloop no matter what,
So from emergency call find your way into permission manager , from there you can open settings app, disable location and anything that would trigger wifi to turn on , airplane mode is on remember this, you need to turn it off withput having the wifi kick on. Disabling some modem/network apps or that has anything to do with wifi, location, carrier, modem that you can disable, do it. Once you're able to turn airplane mode off successfully you can get passed the wifi part of the phone setup and use your mobile data instead, or what I did is use gnirehtet , you can find it on GitHub. Install on PC, make sure you enable USB debugging and have the default USB config set to USB tether, not hotspot .extract zip to platform tools, Move the apk file from gnirehtet zip to your phone, run the provided command from the zip and you'll get a request to allow debugging on your phone from PC, once you do that. You'll finally be able to update your n200 T-Mobile phone to Android 12 which is the only way I found to do this. Make sure you update to Android 12 and not another android 11 before turning wifi on or anything else or you will have to start ALL OVER. Done it twice it's a pain in the arse
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
I was going to say keep discussion in the open in case any future people come across the same issue. If there's one thing I hate is coming across the same issue as my issue on stack overflow or elsewhere and OP from 7 years ago saying, "Never mind, I figured it out."