Develop Bugs

[GUIDE][All-In-One]LG Optimus Me P350

So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide​
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit

great guide good job

Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!

to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy

antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...

Updated adding unyaffsmbn tool... Thanks antdking!

Added Volume tweak for speaker to sound harder.

Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me

dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:

Guys We have got Official Support From XDA Please Move This Thread To Our Device Section

Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183

Great Guide Man! Thanks a lot.

[GUIDE]: ROOT / BL-Unlock / Install Custom Recovery - LG Optimus G E970/1/3

INTRODUCTION
THIS IS A DETAILED GUIDE TO SHOW YOU HOW TO ROOT, BOOTLOADER-UNLOCK AND INSTALL CUSTOM RECOVERY AND ROMS ON YOUR LG OPTIMUS G E970/1/3 with a Windows PC. I will add to/edit it as necessary, and will probably beautify it a bit soon enough as well.
Disclaimer: This has worked successfully for many people on these devices, including myself on the E971. Having said that, I’m not responsible for any explosions or any other form of destruction you may end up with as a result of using this guide!
Click to expand...
Click to collapse
The Dropbox files I’ve linked here are from my own account, so rest assured everything is safe. I will be posting mirrors soon (or replacing if necessary).
A full list of “thanks” will be at the end.
PLEASE follow all the instructions carefully. I will try to help as much as I can, but I am in no way a developer. Just a guy who loves messing with stuff, especially these awesome devices. The #lg-optimus-g IRC chanel is always great help along with great folks here.
---
PRE-GAME CHECKLIST
COMPUTER PREP – Install the following before proceeding any further. If you know for sure you’ve got these taken care of, go ahead to the next section.
1) ADB/FASTBOOT/APX DRIVER - DOWNLOAD: https://www.dropbox.com/s/v7duwo5l09dky8n/Universal_Naked_Driver_0.72.zip
- This driver, in part, is needed for your phone to properly communicate with the PC for our needs. That goes for any Android device, so this is definitely a must have. For more details and discussion/help > http://forum.xda-developers.com/showthread.php?t=1996051​2) LG DEVICE DRIVER - DOWNLOAD: https://www.dropbox.com/s/dho1z4hdkyezkgp/LGUnitedMobileDriver.zip
- Just like most USB devices, your phone relies on this to communicate with your PC.​3) Make sure you have 7Zip, WinRAR, WinZIP or another similar application installed on your computer to be able to extract archives.
- Download 7zip here: http://www.7-zip.org/download.html​
PHONE PREP - you will need the USB cable, and your phone needs to have internet connection for the bootloader unlock section. I recommend having JellyBean installed already, the OTA upgrade method is fine with stock before you use this guide. I haven't tried or had any info on anyone else trying this with stock Ice Cream Sandwich, so I'm not sure about the compatibility there.
MEAT AND POTATOES
-ROOT-
1) Download the root package here > https://www.dropbox.com/s/fib80m6q9jzcj4t/ZV9-ZVB-Universal-Root.zip > and extract it to a folder.
2) Connect your phone to your computer with the USB cable and CHANGE THE CONNECTION TYPE TO “CHARGE ONLY” IN NOTIFICATIONS. This is important for the next step.
3) Open the folder you extracted to and double click the batch file “CurrentRoot” or “CurrentRoot.bat”.
4) The on-screen instructions are pretty clear for this part. To sum it up:
a. You’ll need to wait for the phone to be recognized, then you’ll be asked to change the USB mode to “MTP” - you must do this in order to proceed. Press Enter.
b. You may see some error and “daemon” messages along the way here. Don’t be alarmed by those, focus on the prompts.
c. Once you see “uid=0(root) gid=0(root)” you will be prompted to press Enter again. If you don’t get that, reboot your computer and repeat from step 2.
d. At the end, you should see a message that says you’ve been properly rooted. Press any key to continue, your phone should automatically be rebooted (if not, manually do so).
e. Open your app drawer and run the app called SuperSU and ensure it runs with no errors. *IF YOU DON'T HAVE SuperSU IN YOUR APP DRAWER, DOWNLOAD/INSTALL/RUN IT FROM THE PLAY STORE!*
f. You can download any root-required app from the Play Store (Root Checker is easy if you can’t think of one) to verify that you are properly rooted. Congratulations!​
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).​
JOB WELL DONE. NOW WHAT DO YOU DO?
The very first thing I recommend you do is BACKUP YOUR EFS PARTITIONS!! Head over to this thread by autoprime on XDA: http://forum.xda-developers.com/showthread.php?t=2161611&highlight=efs - this is important to have in case things go wrong down the road.
Now you have the freedom to do quite a bit, most notably install custom ROMs. It’s important to read through the entire original post of a ROM’s thread. The developer has put everything there for a reason, follow it to the tee! Methods of installation for ROMs may slightly vary. Use the files they link only and don’t stray from their installation instructions.
A loose reference to the most common method is:
a. Wipe data/factory reset
b. Wipe cache
c. Wipe dalvik cache
d. Install ROM file
e. Install GApps file
f. Wipe data/factory reset again (usually good measure regardless)
g. Reboot system​
USEFUL INFO AND LINKS (more to come)
I cannot stress how crucial backups are. Back EVERYTHING up, and keep them in more than one place. Much, much better safe than sorry. Titanium Backup is your best friend, check it out.
http://forum.xda-developers.com/showthread.php?t=2010624 - Guide to unbrick your phone! This worked well for me when I bricked back in the day!
http://forum.xda-developers.com/showthread.php?t=2181103 - Thread for original root method, good for help.
---
THANKS!
- carrett (original guide that, in part, inspired this one)
- 1wayjonny (original thread for ADB/FB/APX driver)
- fiddy619 (original thread for root method)
- thecubed (project FreeGee - enough said)
- Shelnutt2 (project FreeGee - enough said)
- kentek (source for awesome LG driver)
- autoprime (author of the EFS backup guide and general LG OG God status)
- Paulicat (responsible for much of my (yet limited) wisdom regarding this device)
+ Anyone directly or indirectly responsible for anything in that list who I've left out.
+ Sorry to anyone else I've missed, please send me a quick message and I'll add you in, and I will add in as I go if I remember more.
+ The awesomeness of the #lg-optimus-g IRC channel and everyone in it - check it out on http://webchat.freenode.net!

Reserved.

Thank you very much, This worked perfectly on my phone. It was a rogers branded phone.
also I recoment rebooting your computer and at least haveing mtp used once,
btw my os is XP and if you need to push any apps to the phone bring up a dos prompt and type adb install .apk

thank you for this well written topic
any ideas if these tools work on E977?

thanks a lot you save my hearts life. for real man. whoaa
Bmvery guides I actually can't get the lex program to work when I connected my phone in download mode. But I tried LG test tool and it worked. Luckily.thanks a lot. I almost had an heart attack when I can't fixed it or in other words solve the problem.:good

Thanks for this well-written guide. Unfortunately I cannot even gain root access so far. When I run currentroot.bat I keep getting device not found device not found errors. Please help me if you can. Thanks.

Will this work on the LG E975 (Intl)
Hi,
Great guide, very detailled!
But I want to buy the optimus G thats in my country the E975, and I can't find it almost anywhere, if all these guides will work on this model.
Please help me if you can
Greetings from The Netherlands

Is menu in FreeGee has gone? I could not find SLB Method in app?

pyramid said:
Is menu in FreeGee has gone? I could not find SLB Method in app?
Click to expand...
Click to collapse
+1 how do u unlock now ?

SBL location...
pyramid said:
Is menu in FreeGee has gone? I could not find SLB Method in app?
Click to expand...
Click to collapse
Click on the box that says CWM-6.0.4.7 you should get a message that gives you an option to select an unlock (either Classic or MAKO). MAKO is the replacement for SBL, and it worked just fine for my device. :laugh:

Ok, help. I recently switched from my Samsung Galaxy 3 to this Optimus G I got. I downloaded all the necessary files, but when i connect the phone to the usb connector. I get nothing suggesting that anything is plugged in. Like even a prompt to look for drivers so i can install the universal drivers. Any help is greatly appreciated BTW, running PC Windows 7 64 bit and Another laptop Windows 7 32 bit. Any help is appreciated.
-Carlos

ok. So Im going in and manually adding hardware. When I do that for the universal naked driver, it asks me to choose the device. It has a Nexus 4 adb device, nexus 7, asus transformer, htc interface, and samsung interface. I am lost Which one would I choose for the E970? Any help would be greatly appreciated. I can't wait to get this LG rooted. Please help.
-Carlos

My phone is not supported
hv6478 said:
INTRODUCTION
THIS IS A DETAILED GUIDE TO SHOW YOU HOW TO ROOT, BOOTLOADER-UNLOCK AND INSTALL CUSTOM RECOVERY AND ROMS ON YOUR LG OPTIMUS G E970/1/3 with a Windows PC. I will add to/edit it as necessary, and will probably beautify it a bit soon enough as well.
The Dropbox files I’ve linked here are from my own account, so rest assured everything is safe. I will be posting mirrors soon (or replacing if necessary).
A full list of “thanks” will be at the end.
PLEASE follow all the instructions carefully. I will try to help as much as I can, but I am in no way a developer. Just a guy who loves messing with stuff, especially these awesome devices. The #lg-optimus-g IRC chanel is always great help along with great folks here.
---
PRE-GAME CHECKLIST
COMPUTER PREP – Install the following before proceeding any further. If you know for sure you’ve got these taken care of, go ahead to the next section.
1) ADB/FASTBOOT/APX DRIVER - DOWNLOAD: https://www.dropbox.com/s/v7duwo5l09dky8n/Universal_Naked_Driver_0.72.zip
- This driver, in part, is needed for your phone to properly communicate with the PC for our needs. That goes for any Android device, so this is definitely a must have. For more details and discussion/help > http://forum.xda-developers.com/showthread.php?t=1996051​2) LG DEVICE DRIVER - DOWNLOAD: https://www.dropbox.com/s/dho1z4hdkyezkgp/LGUnitedMobileDriver.zip
- Just like most USB devices, your phone relies on this to communicate with your PC.​3) Make sure you have 7Zip, WinRAR, WinZIP or another similar application installed on your computer to be able to extract archives.
- Download 7zip here: http://www.7-zip.org/download.html​
PHONE PREP - you will need the USB cable, and your phone needs to have internet connection for the bootloader unlock section. I recommend having JellyBean installed already, the OTA upgrade method is fine with stock before you use this guide. I haven't tried or had any info on anyone else trying this with stock Ice Cream Sandwich, so I'm not sure about the compatibility there.
MEAT AND POTATOES
-ROOT-
1) Download the root package here > https://www.dropbox.com/s/fib80m6q9jzcj4t/ZV9-ZVB-Universal-Root.zip > and extract it to a folder.
2) Connect your phone to your computer with the USB cable and CHANGE THE CONNECTION TYPE TO “CHARGE ONLY” IN NOTIFICATIONS. This is important for the next step.
3) Open the folder you extracted to and double click the batch file “CurrentRoot” or “CurrentRoot.bat”.
4) The on-screen instructions are pretty clear for this part. To sum it up:
a. You’ll need to wait for the phone to be recognized, then you’ll be asked to change the USB mode to “MTP” - you must do this in order to proceed. Press Enter.
b. You may see some error and “daemon” messages along the way here. Don’t be alarmed by those, focus on the prompts.
c. Once you see “uid=0(root) gid=0(root)” you will be prompted to press Enter again. If you don’t get that, reboot your computer and repeat from step 2.
d. At the end, you should see a message that says you’ve been properly rooted. Press any key to continue, your phone should automatically be rebooted (if not, manually do so).
e. Open your app drawer and run the app called SuperSU and ensure it runs with no errors. *IF YOU DON'T HAVE SuperSU IN YOUR APP DRAWER, DOWNLOAD/INSTALL/RUN IT FROM THE PLAY STORE!*
f. You can download any root-required app from the Play Store (Root Checker is easy if you can’t think of one) to verify that you are properly rooted. Congratulations!​
-UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-
This section is done through an app, right in the Play Store thanks to Project FreeGee (XDA thread for thanks - http://forum.xda-developers.com/showthread.php?t=2001655). If you can, make sure to go there and give thanks to thecubed (and Shellnutt2) for this amazing app and all their efforts. Please get the $1 version if you can as well, it’s beyond worth it.
Head on over to the Play Store and download the app “FreeGee **ROOT Required**” or do it on your PC - https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=en ($1 – if you can this would be the one to go for) OR https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en (free version). Run the app and grant it root permissions. FOLLOW THESE INSTRUCTIONS CAREFULLY!
1) In the app, ignore the main buttons and click Menu > SBL Unlock method.
2) Click “Get Unlock Code” – a browser window will open up. Here will be a hardcore disclaimer by Shelnutt2, and it should be taken seriously since there IS a possibility of something going wrong. The chances are EXTREMELY SLIM, but the disclaimers have to be put in place.
3) Enter your name (username for forums is the best way to go), click the checkbox, enter the CAPTCHA, and click “Submit”.
4) The next page will have your code. Copy it and go back to the FreeGee app.
5) Paste the code into the field and click “ok”. You should get a confirmation message that you’ve enabled the SBL Unlock method.
6) On the app’s main screen, click “Unlock my phone” and wait for the download to finish.
7) You’ll be asked to choose a recovery version. I personally use ClockworkMOD, but many people like TWRP. It shouldn’t make a difference at the end of the day, you can look into both and decide if you’d like. Choose one, and proceed through all the dialogue boxes, accepting everything. Your phone will eventually reboot.
8) To verify this was done properly, after the reboot you can reboot again into recovery mode. The easy way to do this is to download QuickBoot from the Play Store and use that. Otherwise:
a. Power off your phone
b. Press and hold the PWR button, while holding down the VOL-UP/VOL-DOWN buttons at the same time (I’ve seen VOL-UP/PWR as instructions, I haven’t been able to get it to work myself like that but YMMV).
c. You’ll see a black screen with some small writing in the bottom-left corner. Nothing will actually respond on-screen at this point, don’t worry.
d. Press VOL-DOWN twice, then press PWR.
e. Your custom recovery should now boot up. Here, you can backup your current software (DO THAT RIGHT AWAY), reboot the phone into whichever mode you want, and install custom ROMs (more and that after the break).​
JOB WELL DONE. NOW WHAT DO YOU DO?
The very first thing I recommend you do is BACKUP YOUR EFS PARTITIONS!! Head over to this thread by autoprime on XDA: http://forum.xda-developers.com/showthread.php?t=2161611&highlight=efs - this is important to have in case things go wrong down the road.
Now you have the freedom to do quite a bit, most notably install custom ROMs. It’s important to read through the entire original post of a ROM’s thread. The developer has put everything there for a reason, follow it to the tee! Methods of installation for ROMs may slightly vary. Use the files they link only and don’t stray from their installation instructions.
A loose reference to the most common method is:
a. Wipe data/factory reset
b. Wipe cache
c. Wipe dalvik cache
d. Install ROM file
e. Install GApps file
f. Wipe data/factory reset again (usually good measure regardless)
g. Reboot system​
USEFUL INFO AND LINKS (more to come)
I cannot stress how crucial backups are. Back EVERYTHING up, and keep them in more than one place. Much, much better safe than sorry. Titanium Backup is your best friend, check it out.
http://forum.xda-developers.com/showthread.php?t=2010624 - Guide to unbrick your phone! This worked well for me when I bricked back in the day!
http://forum.xda-developers.com/showthread.php?t=2181103 - Thread for original root method, good for help.
---
THANKS!
- carrett (original guide that, in part, inspired this one)
- 1wayjonny (original thread for ADB/FB/APX driver)
- fiddy619 (original thread for root method)
- thecubed (project FreeGee - enough said)
- Shelnutt2 (project FreeGee - enough said)
- kentek (source for awesome LG driver)
- autoprime (author of the EFS backup guide and general LG OG God status)
- Paulicat (responsible for much of my (yet limited) wisdom regarding this device)
+ Anyone directly or indirectly responsible for anything in that list who I've left out.
+ Sorry to anyone else I've missed, please send me a quick message and I'll add you in, and I will add in as I go if I remember more.
+ The awesomeness of the #lg-optimus-g IRC channel and everyone in it - check it out on http://webchat.freenode.net!
Click to expand...
Click to collapse
my lg optimus L90 D415 is no supported, any help??

alexcool9595 said:
my lg optimus L90 D415 is no supported, any help??
Click to expand...
Click to collapse
I don´t know if you can read, but it clearly says "ON YOUR LG OPTIMUS G E970/1/3"
It's not made for your phone.

[ROOT][UNROOT][CWM RECOVERY][STOCK KERNEL][STOCK RECOVERY] Google ADT-1 Android TV

Hello All,
Root
If on stock, uprooted (ever), go to method 1. If not, keep reading.
Now, in the latest Molly CF-AutoRoot, it flashes a modified kernel to gain root that causes OTA updates (i.e. impending 5.0.1) to fail, this was due to the fact that until a couple days ago, the modified kernel was necessary. Chainfire found a way to fix it without modifying the kernel and implemented it in SuperSU 2.37. If you are rooted, used CF-Auto Root, and wish to retain root, but regain the stock kernel for OTA's, simply follow root method 2.
Method 1
To Root from stock LPX13D, Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices, and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected.
8. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery!
9. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
10. Select "Install Zip from sideload"
11. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
12. (On ADT-1) Select "**Go Back**"
13. Select "Reboot to system"
14. Select "No" when asked to restore Root, as this's feature does not work yet.
15. Profit!
Method 2
To Root from CF-auto rooted LPX13D and regain stock kernel (This will not restore Build.prop and other system changes!), Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
- stockbootlpx13d.img
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices", and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected
8. Run "fastboot flash boot stockbootlpx13d.img"
9. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery! Then you must run "fastboot reboot recovery"
10. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
11. Select "Install Zip from sideload"
12. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
13. (On ADT-1) Select "**Go Back**"
14. Select "Reboot to system"
15. Select "No" when asked to restore Root, as this's feature doe snot work yet.
16. Profit!
Unroot
Requirements:
- stockbootlpx13d.img
- recovery.img
1. Enter the SuperSU app, and go to Settings ==> Full Uproot, and verify your choice. (Stop here if you didn't use CF-auto root)
2. Plug your ADT-1 into your PC and run the command "cd desktop", then "adb reboot bootloader", then "fastboot flash boot stockbootlpx13d.img"
3. Run "fastboot flash recovery recovery.img"
4. Then "fastboot reboot"
5. Un-Profit!
To take an OTA Update
If you followed this guide correctly, just unroot from within SuperSU as shown in Step 1. Of the unroot section. It will leave you 100% stock. Then take the OTA.
Downloads
Stock Boot Image LPX13D (stockbootlpx13d.img): https://www.dropbox.com/s/vayt67s513v9z8u/stockbootlpx13d.img?dl=0
Stock Recovery Image LPX13D (recovery.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
CWM Recovery Img (cwm_molly_recovery_lpx13d.img): https://www.dropbox.com/s/8evaum04mv843dp/cwm_molly_recovery_lpx13d.img?dl=0
SuperSU 2.37.zip: http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Optional: Install Leanback Launcher from here to allow launching sideloaded apps: https://play.google.com/store/apps/details?id=eu.chainfire.tv.sideloadlauncher&hl=en
Happy Modding!
Credits:
Chainfire: The super amazing SuperSU, and the awesome CF-Auto Root, thank him!
GTAVHacker: Used CWM Recovery Image as a base, thank him!
Myself: Stock Images, and the guide.

npjohnson said:
CWM Recovery (cwr_molly_recovery_lpx13d.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
Click to expand...
Click to collapse
Thanks for this! Should the file on dropbox be named cwr_molly...? When I go to the download it simply says recovery.img.

good work
This is awesome, thanks for sharing, I'd really like to see TWRP ported as well, they allow OTA installs/mtp, adb sideloads & more, this is a great step in the direction of seeing custom roms

OP download links updated. My apologies.

Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.
Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.
CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.
CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP

I cant seem to get this to work. I tried using just the boot option and it just reboots into the bootloader. I tried the flash as well and recovery never boots. Any chance the problem is that this is for the ADT1 (molly) and not the Nexus Player (Fugu)?

The title of the post indicates ADT-1. You need to make sure any modification you do is appropriate for the device you have. The ADT-1 uses and Android processor/chip set while the Nexus Player uses an Intel processor/chip set.

Is there not a subforum for the adt1?

hmmmm CWM

jscat1 said:
Is there not a subforum for the adt1?
Click to expand...
Click to collapse
No there is not! I know, it sucks, but until that changes, looks like we are setting up shop on the fugu forums. XD

thanks so much for this. the ADT-1 needs more love on xda

twrp
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section

defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
Thanks man. TWRP is actually gonna be more than it is worth. CWM should work just fine, it actually has better support for keyboard.
I'll mess with it. Did you build the kernel with the ADT-1 and x86 architecture in mind?

defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?

mkaymuzik said:
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
Click to expand...
Click to collapse
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.

npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
im working on a new tree. open to anyone to contribute and add things. created a github organization for this purpose
https://github.com/adt1-dev
PS: im new to this and learning on the way.
Edit: are your sources on github?

npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
If you're referring to the builds I released on GTVHacker forums for CWM recovery on the ADT-1, I didn't build the kernel or use any Android TV or ADT-1 source (it wasn't even available when I had started). I just used generic CM Android 4.4, reused the kernel and fstab from the stock ADT-1 recovery, and made a few changes to the default generic BoardConfig.mk.

Any plans on making recovery for nexus player? Just curious

Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks

illuminerdi said:
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
Click to expand...
Click to collapse
You can just download the factory image and extract it. Here is a little tutorial if you are unsure how to extract.

[GUIDE] LineageOS 17.1 ROM for Galaxy A50 Android 10 Q

The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo

Thanks. So this is GSI? Bugs?

Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN

Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain

DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)

I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans

hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?

I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany

well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/

Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse

I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6

Will this image work with the SM-A505G version?

USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?

OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.

InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.

OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel

the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP

hey man, the project is being upgraded? Tanks for your time

InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware

I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.

How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root-Update

Ready to Unlock, Root, and Update factory images on your Pixel 6 Pro?
There are some really good guides by V0latyle here, and by roirraW "edor" ehT here which are great for veteran/regular users who are really familiar with adb/fastboot and the commands, steps used in the unlocking, rooting environment.
This step by step is for people like ME who are not adb/fastboot gurus, who need every step spelled out so we don't brick our over-priced flagship devices
* * *P L E A S E READ THIS FIRST B E F O R E UPGRADING TO ANDROID 13* * *
What You Need On Your PC:
Factory Image
MAGISK - Canary 24310
SDK Platform Tools & USB Drivers (first time installation)
(additional files I use: optional)
Working SafetyNet @Pekempy
Kirisakura Kernel @Freak07
*** MAKE SURE YOU EXTRACT THE CORRECT BOOT.IMG FILE TO PATCH IN MAGISK ***
-download latest factory image, unzip the MAIN image.zip, then unzip the SECONDARY image.zip , copy the contents of the SECOND image.zip into the same platform tools folder that has the fastboot application in it, then open the image.zip you just copied into the fastboot folder and copy the boot.img and paste it somewhere on your PC.
Device Setup PRIOR To Starting Fastboot:
Settings>About phone>Build Number (click build number until you see YOU ARE NOW A DEVELOPER)
Settings>System>Advanced>Developer Options
Enable OEM Unlocking & USB Debugging & USB Configuration> enable FILE TRANSFER
Unlock the Bootloader, Update Factory Image, and Get Root:
1- Boot your device into bootloader/fastboot (hold power / vol down)
2- Connect USB cable to device and PC ( have diff USB cables available for troubleshooting)
3- From address bar in the platform tools folder where the fastboot application is located on your PC, type CMD to open command prompt window
4- Type FASTBOOT DEVICES, if you see a serial number(s) you are ready, if you don't, verify you've properly set up platform tools folder, change cable, check command, try again)
5- TO UNLOCK BOOTLOADER- type fastboot reboot bootloader (***YOUR DATA WILL BE WIPED***)
6- Type fastboot flashing unlock
7- Type fastboot reboot bootloader
IF UPDATING TO ANDROID 13 FOR THE FIRST TIME IT IS HIGHLY RECOMMENDED YOU FLASH THE 13 BOOTLOADER TO BOTH SLOTS BEFORE UPDATE (read warning at top of page) Follow step 7a to accomplish updating both slots to the Android 13 bootloader:
7a. Type fastboot flash bootloader --slot=all <bootloader image in platform tools>
PRIOR TO FLASHING THE FACTORY IMAGE:
-if you want a clean install, WIPING ALL DATA, skip to step #8
-if you want to SAVE data, edit the FLASH ALL.bat file, REMOVING the -w (leaving just ONE space between the remaining text) and SAVE the file (reopen file to verify -w is removed)
Disabling Verity and Verification isn't required except for use with some custom kernels, but just rooting those custom kernels with the latest Magisk Stable v24.1 or higher should make them not require disabled Verity and Verification anymore. click HERE for more
8- Flash the factory image by typing FLASH-ALL
9- After the install, it will reboot into system, let everything settle, skip start up options and get to where you can download the latest MAGISK apk on your device (downloads folder)
***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***
10- Connect your device and PC and put the extracted BOOT.img file (from the CURRENT factory image you are flashing FOUND IN THE SECOND ZIP FOLDER) that you placed on your PC, put it on your mobile device where you can easily find it (I created a folder FILES TO FLASH)
11- Install Magisk (use Canary 24310 linked above), follow instructions to allow files like this to be installed) ***DISABLE MAGISK MODULES as some have reported issues caused by some active modules***
12- Open Magisk and choose SELECT AND PATCH FILE (select the BOOT.img you just put on your device
13- Copy the new PATCHED BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC
14- Boot device into fastboot/bootloader, connect device and PC
15- Type CMD in address bar and verify fastboot connection (step 4)
16- Type fastboot reboot bootloader
17- Type fastboot flash boot --slot=all (drag and drop patched boot.img here) OR type in the file name magisk_patched-xxxxxxxxxx.img)
18- Reboot into System
UPDATE Factory Image WITHOUT Wiping Data:
1- Within the Platform Tools folder, find the FLASH-ALL (.bat) file
2- Open it with text editor and remove the -w (keep ONE space between remaining text, SAVE file, reopen to verify -w is removed)
3- Verify FASTBOOT DEVICES by typing CMD in the address bar of the same platform tools folder
4- Type FLASH-ALL
5- Let it boot into system and settle for a minute
6- Patch the boot image (follow steps 10, 12 -18 above)
*** Thanks to V0latyle, roirraW "edor" ehT, and Lughnasadh for the foundations of these instructions! ***
Please let me know if any part of this process is incorrect, has been updated, or is no longer necessary

This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?

dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
+1
Your guide is exactly what I have been summarizing in one of the threads already.
They keypoint now is on how to apply monthly updates without wiping the phone all the time while also still getting root

Az Biker FTW! Good to see you here buddy! (I remember you from the Pixel 2/4 XL forums)

Thanks @Az Biker! I'll update the OP of my thread to link to this thread just as soon as I can find the time.

dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
I've never done the OTA method, so I don't have a step by step for that. Sorry.

How can I re-lock the bootloader?
I'm getting a "command error" with fastboot flashing lock

dipole said:
This is great, it's been like 7 years since I last rooted. Can you also do one for OTA step by step?
Click to expand...
Click to collapse
You can find the OTA sideload method here...
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!

Morgrain said:
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Click to expand...
Click to collapse
Did you see the responses about this subject starting here?
Personally, I haven't had a problem with the way they're doing the forums now. The Quick Filters at the top have been good enough for me when I want to concentrate on one of those particular types of posts.
FYI, although I'm a proponent of the new way, I'm not particularly against the old way. That's what I got used to, too, but things change.

roirraW edor ehT said:
Did you see the responses about this subject starting here?
Personally, I haven't had a problem with the way they're doing the forums now. The Quick Filters at the top have been good enough for me when I want to concentrate on one of those particular types of posts.
FYI, although I'm a proponent of the new way, I'm not particularly against the old way. That's what I got used to, too, but things change.
Click to expand...
Click to collapse
Good to know. Nope, I did not notice that. And I don't really like the filters. I'm used to , uhm, use XDA on my PC with multiple monitors, and the old style forums allowed me to just middle mouse button Press every sub forum, enabling me to open all of them in separate browser threads in the course of a second, which made quickly tabbing / shifting through sections /threads extremely quickly / efficient, at least for someone used to that kind of usage. Now I'm stuck with the heck load of filters and that just slows down the way I browse by factor three, if not more.
This new system is also quite confusing. Back in the days whenever you open a sub forum, you had an easily distinguishable sort of sticky threads. Now it just feels all cluttered together. It made browsing XDA less fun and it just feels tedious.

vibrantliker said:
How can I re-lock the bootloader?
I'm getting a "command error" with fastboot flashing lock
Click to expand...
Click to collapse
Check to be sure you only have one space between each word, and no typos.
I believe fastboot oem lock will work as well.
Make SURE you are running a stock, factory image before doing this (just in case you weren't aware).

Morgrain said:
...use XDA on my PC with multiple monitors, and the old Style forums allowed me to just middle mouse button Press every sub form to me to open all of them in separate browser threads, which made quickly tabbing / shifting through sections /threads extremely quickly, at least for someone used to that kind of usage.
Click to expand...
Click to collapse
Ha! Now that you've reminded me, I used to do the exact same thing here (I too middle mouse button, in general, a lot). Maybe it's been beneficial to me that I've barely had any activity on XDA for the last five years, and especially the last three years.

Thank you, however readability is very bad on a light background. Please change font color.

Tomatot- said:
Thank you, however readability is very bad on a light background. Please change font color.
Click to expand...
Click to collapse
Changed the font to "brown", let me know if that helps with the light theme.
I'm on Xda-dark and hadn't thought about the readability using light theme, thanks!

Az Biker said:
Changed the font to "brown", let me know if that helps with the light theme.
I'm on Xda-dark and hadn't thought about the readability using light theme, thanks!
Click to expand...
Click to collapse
I thought of that, that's why I dared to mention it.
It's better indeed!

Morgrain said:
Maybe it makes more sense to combine and improve upon existing tutorials, instead of creating a load of new ones. It's getting a bit confusing here, ESPECIALLY since we don't have any sub-threads/forums.
Why is that, anyway? it makes sifting through threads here a nightmare, since you have to scroll through dozens of threads to find one that suits your interest. Instead of just giving us, like, an overview labeled "mods", "kernels", "camera", "discussion", "flame" - like, in every other previous XDA Pixel forum?!
Click to expand...
Click to collapse
Sorry for the late response.
FILTER TABS (new way) vs Sub Forums (old way):
Look at it this way:
You're grocery shopping online, and you want to browse the candy bar selection. The store has candy bars in several areas, not just in one place, so now you have to look through pages and pages of all the available product.
Rather than try to scroll through everything in the store to just find the candy bars, you click the CANDY BAR filter tab, and ONLY the candy bars are visible now.
So even though they aren't technically in one single area of the store, you can only see the candy bar selection on your page.
That's how the new forum works. Want to only see Development threads? Click the DEVELOPMENT tab at the top of the device forum.

@Az Biker
could you please make the guide for update factory image with out wiping. and keep root. please please please.

Lw00d said:
@Az Biker
could you please make the guide for update factory image with out wiping. and keep root. please please please.
Click to expand...
Click to collapse
That would be awesome. Just looking around for that as well.

Is it possible to get root without wiping? Currently I only have the bootloader unlocked and I'm on .036