Related
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]LG G2[/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. [/SIZE]
[SIZE=+1]Q1: How do I root my G2?[/SIZE]There are several root methods depending on what android version you're on:
IOroot (Jellybean 4.2x/KitKat 4.4x)
New Root Method for LG Devices (Lollipop 5x)
[Japanese L-01F] Root your L-01F [HOWTO]
[SIZE=+1]Q2: How do I restore my phone to stock?[/SIZE]Visit the Back to stock thread. This has detailed instructions on how to flash factory firmware. If you have bricked your device or are trying to fix software issues then this is the go to method.
[SIZE=+1]Q3: Can I recieve OTA updates while my phone is rooted?[/SIZE]Short answer, no. If you have any modified files at the root level of your device this will break OTA. You may have to flash the stock firmware before you take an update.
[SIZE=+1]Q4: My phone won't connect to my PC. How do I fix this?[/SIZE]You might be experiencing driver issues. To resolve it take the following steps:
Download the LGUnitedMobile driver here
Open programs and features and delete the currently installed drivers
Launch the exe file of the drivers that you downloaded and let it install
Reboot your PC and try connecting your phone again.
If your still not connecting then try using PDAnet drivers. Again, delete the LG drivers you installed and launch PDAnet on your PC. Let the drivers install and try again.
[SIZE=+1]Q5: I have a f320/ isai/l-01f . Where is the development for my variant?[/SIZE]These variants aren't as widely supported as the other ones unfortunately. Many ROM devs support the f320 but the ISAI and l-01f don't get as much love. There are dedicated threads for these variants here:
LG isai LGL22 Central Index - TOT&DLL | KDZ | Root | Recovery | ROM | Discussion
AOSP for Japanese G2 L-01F
[SIZE=+1]Q6: Is it possible to sim unlock the Sprint G2?[/SIZE]Yes. See these threads:
Sim Unlock ZVG lollipop
Permanent SIM Unlock for LS980 (OTA, APN) JB 4.2.2, KK 4.4.2
[SIZE=+1]Q7: How do I flash a custom recovery?[/SIZE]If you are coming from stock you need to root your device first (see Q.1). Here are the recovery methods based on android version:
KitKat
Use Autorec from this thread. Pick the correct one for your variant.
Lollipop
Use the Autorec app from the playstore. You can find them here. There is a separate app for each variant so pay close attention to which one you use.
Launch the app and follow the instructions to reboot to recovery.
Jellybean
There are several methods of doing this. Here is the easiest one:
[RECOVERY] [TWRP] [FLASHIFY] Quick & easy[SIZE=+1]Q8: What is ADB and fastboot?[/SIZE]ADB stands for Android Debug Bridge. These are the android tools developed by Google for developers and users to connect devices to a PC and send commands to it. There's a detailed guide to ADB here.[SIZE=+1]Q9: What is Bump!!!?[/SIZE]Bump is a bootloader exploit developed by team Codefire. It's purpose (in a nutshell) is to allow KitKat bootloaders to load custom boot (kernel) and recovery images to allow the flashing of custom ROMs.
By bumping a boot.img the tool signs it using it's magic keys to trick the bootloader into thinking that it is, in fact an official boot.img.[SIZE=+1]Q10: I bricked my phone and it is now in fastboot mode. How do I fix this?[/SIZE]There are several ways to fix it. If you have download mode you can flash a stock image (see Q.2). You can also use the fastboot tools to flash over the damaged partitions (see Q.8).
@somboons has developed a utility called SRK Tools which has a function to fix fastboot mode, and do many other useful things. You can find his tool here.[SIZE=+1]Q11: I rooted my device and now I need to RMA it. Is there any way to unroot/hide root?[/SIZE]If your device is rooted then there will be a root flag in download mode. This will be there even if you unroot from within superuser.
To remove all traces of root you will need to flash the stock firmware again (see Q.2)[SIZE=+1]Q12: What is a bootstack and why is it important?[/SIZE]A bootstack is a set of partition images that are needed for android to boot. In the case of the G2 partitions need to be slightly modified because the LP bootloader will not load custom images. In other words, if you want to flash a custom recovery and ROM, you need a KK bootloader and bumped kernel and recovery images. Autorec does this automatically or you can flash your own hybrid bootstack [SIZE=+1]Q13: My phone is dead or my PC recognises my phone as QHSUSB_BULK/Qualcomm 9006/8 or security error. How do I fix this?[/SIZE]These errors occur when your device has mismatched/corrupt or missing partitions. This can occur by flashing the wrong ROM, Autorec or bootloader. (eg. nuking your bootloader will give you a security error.) In the case that you still have download mode, you can just flash a stock image to fix it. If your phone is not booting into any mode but it's recognized by your PC then pay attention to device manager to see how windows sees your phone. For QHSUSB_BULK see here and here.
Alternatively you can use the Srk Tools. For qualcomm 9006 see here For Qualcomm 9008 or if your phone is not recognized by PC (windows/mac OR linux) and does not boot then you may need to follow this guide to revive your phone.[SIZE=+1]Q14: How do I enter recovery with the button combination?[/SIZE]If you have a custom recovery you use the button combination to factory reset.
Power off the device
Hold volume down and power button until you see the LG logo
For JB/KK Hold volume down and power
For LL Hold volume down and volume up
Enter at the factory reset screen
[SIZE=+1]Q15: What is an EFS and why is it important?[/SIZE]Your EFS partition contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code and the very main IMEI address, radio settings, programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, etc. An EFS cannot be replaced. It is unique to every device and it is highly recommended that you back it up soon after rooting your device. See this thread for a how to. EFS Partition Backup and More [All G2 Variants[SIZE=+1]Q16: I updated my phone and now the touch screen is erratic and my IMEI is gone. What is happening?[/SIZE]This scenario is common to G2's that are refurbished with mixed parts of many G2 variants. Typically the vendor has used a motherboard from any random G2 variant and packaged it as a d802. It is fixable however, see this thread for more details on how to identify your model. You must get the real model number which is written on the bottom of the mainboard and then flash a stock image accordingly. Restoring your IMEI is trickier though. It is easy if you have previously taken an EFS backup (see Q.15). You can flash the EFS backup zip or use dd to restore modemst1 and 2.
Without an EFS backup you cannot restore a lost IMEI. There are methods that claim to work and they are worth exploring but there is nothing that is definitely known to restore a lost IMEI.*Forum Rules | New Users Guide | XDA Tour | Report PostsA special thanks to everyone who contributed to the production of this FAQ
Judgment Came....
There are a lot of people joining xda on daily basis, and there are a lot of repetitive questions being asked which fill up Development threads. Point them here. Feel free to ask or answer questions. Idea of this thread is to get users to help other users with their problems/questions. Please do not spoon feed, but rather point in the direction where that user can find an answer and educate himself
I do have the G2 fortunately, in order to make XDA a better place, I thought I'd open up a help thread for those who need it. I will be able to give lots of help to fellow G2 users. Hopefully some of the experienced G2 users help out on this thread, because it'd make everything easier. Thanks!
First thing first. I strongly advise you to read THIS thread before posting ANYTHING on XDA.
Then, have a quick look at the names of threads in post no2, you might find what you need right away.
For ROM issues please do mention in your post about:
ROM name
ROM version and base
kernel version and its settings
any mods applied on top of it
flashing "style" aka dirty or clean
something like this
...and be sure you have asked before on the ROM thread unless you have less than 10 posts on XDA
Third. The second post will be used to link to threads for some of the most common problems+fixes. You'll be surprised how much time and frustration it will save you in the future.
ASK ANY QUESTION HERE,adb, drivers, superCID, problems, mods etc...... You will either get an answer or will get pointed in the right direction.
No abuse towards noobs tolerated here! No question is stupid in this thread.
***I feel that a little OT is healthy to the success of this type of thread. The people here who help the most will develop a comradery therefore OT is allowed within reason. Common sense will be applied ***
HALL OF FAME
People who contributed most to this thread and helped countless number of people with their problems/questions. In no particular order.
@cuks
@xanthrax
@Sunandroid
@XxZombiePikachu
@z3pp3lin
@raptorddd
@Art Vanderlay
Special thanks:
Undercover
Xanthrax
XxZombiePikachu
Sunandroid
Thanks for this thread and I do need help here.
So I have barely unplugged three in a half hours ago from full charge and I have 79 percent right now. 21 percent drop in three hours. That's a ton.
I have the 12b rom which I manually got since I'm rooted and couldn't update via Verizon. And flashed the pure audio 2 mod but that's it
Sent from my VS980 4G using xda app-developers app
---------- Post added at 02:04 PM ---------- Previous post was at 02:04 PM ----------
I even hibernated everything through greenify
Sent from my VS980 4G using xda app-developers app
Hard reset it
Would i need to flash a jellybean baseband to go to stockish 4.2.2 from 4.4.2 with savoca boot,img recovery and kitkat baseband? Or am i good to just flash back?
Sent from my LG-D802 using XDA Premium HD app
wadamean said:
Thanks for this thread and I do need help here.
So I have barely unplugged three in a half hours ago from full charge and I have 79 percent right now. 21 percent drop in three hours. That's a ton.
I have the 12b rom which I manually got since I'm rooted and couldn't update via Verizon. And flashed the pure audio 2 mod but that's it
Sent from my VS980 4G using xda app-developers app
---------- Post added at 02:04 PM ---------- Previous post was at 02:04 PM ----------
I even hibernated everything through greenify
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
So you're using a custom rom right? In that case I'd suggest a full wipe then a clean flash followed by flashing PA or Banks gapps. I use those steps on my Nexus 4 and Nexus One (I don't have a G2), but I've never run into any battery issues
brainbeatuk said:
Would i need to flash a jellybean baseband to go to stockish 4.2.2 from 4.4.2 with savoca boot,img recovery and kitkat baseband? Or am i good to just flash back?
Sent from my LG-D802 using XDA Premium HD app
Click to expand...
Click to collapse
Well, I'm no expert at G2 stuff, but if your kitkat rom includes a different radio, then I would suggest that you do flash the jb baseband. Don't mark my words, double check the rom thread just to be sure
g2 framework
is it possible to embed g2 original framework in aosp roms so we can install original g2 apps with no problems?
Hi,
I'm searching for a new phone to buy and this one caught my eye. I have 3 questions.
Is there anything (bad) I should know about the phone before buying it? All the good points are well advertised and easily available to read about on the internet, but the bad things only surface after you used the phone yourself for a while. (No need to mention back buttons though).
Making a custom kernel on non-nexus devices is always a tad (or more) harder, I hear. Are there already (very) stable kernels available like you can expect to see on a nexus device?
Is there any G2 developer looking into/developing Ubuntu Touch for this device? I'm interested in Ubuntu for Android you see, and it'd be awesome if I can use it on this phone like on my gnex.
lugiank said:
is it possible to embed g2 original framework in aosp roms so we can install original g2 apps with no problems?
Click to expand...
Click to collapse
It's be very hard to accomplish that as porting manufacturer specific stuff is quite difficult.
Sent from my Nexus 4 using Tapatalk
I've got a Brazilian D805 here in India. Can someone please tell me if there is a date when KitKat is being rolled out?
I don't understand Brazilian and most of the translated entries are ambiguous.
Advanced Q: can I flash a D802 KitKat ROM for the D805? Is there a thread when I can follow the same?
flashed a nightly rom stuck in boot loop no recovery
I flashed the newest cm 11 nightly rom plus the gapps for the lg g2 ls980 with sprint. I cannot get it to recovery but i can get into download mode. ive tried the lg mobile support tool but it get stuck on downloading software. At this point i really just want to get the phone working again, i dont care how. please help it is the only phone that i have.
I have a european G2 (greek) on rooted stock and custom twrp recovery. If i want to update OTA do i have to revert to stock before updating? Can you tell me how to do that?
Στάλθηκε από το LG-D802 μου χρησιμοποιώντας Tapatalk
Wifi Hotspot and other questions
I purchased a Sprint LG G2. It has been rooted and unlocked. Unfortunately, the person I bought it from doesn't know much about the rooting process that was followed and he just followed instructions given to him by a friend. As far as I can tell, there is no custom ROM on the device. Here are my questions:
- At this moment, there is no Wi-Fi Hotspot option on my device. I'm planning to follow the instructions from here: http://forum.xda-developers.com/showthread.php?t=2675280. But this link is for non-activated devices. Question is: How do I know if my phone has or has not been activated?
- If I do decide to follow the instructions in the above link, what would be the best way to backup my device first? Would you recommend Titanium Backup?
- The 3G connection on the phone seems to be awfully slow. Is this a 'Unlocked Spring G2' issue? Is there anything I can do to fix it?
Thank you in advance for all your help.
HELP.. deleted my stock LG camera app
Hello all,
In a quest to improve everything about my phone I seem to have completely deleted my camera app!!! I was attempting to apply the upgrade to the software that can be found here: http://forum.xda-developers.com/showthread.php?t=2471900. I changed the names of the files and permissions exactly as said, rebooted, and poof the camera app was gone. I have since downloaded a third party app to replace it, but I'd like to have the stock app back. No, I did not back up immediately before, I know STUPID!
Any help?? There are great third party apps and I can get by, but thought I'd try.
Thanks!
Djalaal said:
Hi,
I'm searching for a new phone to buy and this one caught my eye. I have 3 questions.
Is there anything (bad) I should know about the phone before buying it? All the good points are well advertised and easily available to read about on the internet, but the bad things only surface after you used the phone yourself for a while. (No need to mention back buttons though).
Making a custom kernel on non-nexus devices is always a tad (or more) harder, I hear. Are there already (very) stable kernels available like you can expect to see on a nexus device?
Is there any G2 developer looking into/developing Ubuntu Touch for this device? I'm interested in Ubuntu for Android you see, and it'd be awesome if I can use it on this phone like on my gnex.
Click to expand...
Click to collapse
For what you are seeking, nexus devices will be your best bet. They have the easiest developing because of not needed custom code. I really like the G2, but for me, the kitkat update was a bust (battery wonky, lots of random reboots, audio issues), so I went back to stock rooted JB. Very nice device that is very stable, but I don't care about AOSP, if I did, I would have gotten N5. Almost everything can be done through being rooted and xposed modules these days.
android_nashville said:
Hello all,
In a quest to improve everything about my phone I seem to have completely deleted my camera app!!! I was attempting to apply the upgrade to the software that can be found here: http://forum.xda-developers.com/showthread.php?t=2471900. I changed the names of the files and permissions exactly as said, rebooted, and poof the camera app was gone. I have since downloaded a third party app to replace it, but I'd like to have the stock app back. No, I did not back up immediately before, I know STUPID!
Any help?? There are great third party apps and I can get by, but thought I'd try.
Thanks!
Click to expand...
Click to collapse
are you rooted, on a custom ROM? If you are on custom ROM you can just reflash ROM without wiping data and it will be added back. If stock, maybe someone can make you an apk you can install or the files can be pushed via adb.
nrfitchett4 said:
are you rooted, on a custom ROM? If you are on custom ROM you can just reflash ROM without wiping data and it will be added back. If stock, maybe someone can make you an apk you can install or the files can be pushed via adb.
Click to expand...
Click to collapse
Yea, I am rooted but am stock. I have a stock camera APK but when I try and install it just says "App Not Installed" over and over again. Reset permissions, put in privat_apps folder and no lock. May just have to live with third party... Camera Zoom Fx and Procapture are both good. Thanks!!
android_nashville said:
Yea, I am rooted but am stock. I have a stock camera APK but when I try and install it just says "App Not Installed" over and over again. Reset permissions, put in privat_apps folder and no lock. May just have to live with third party... Camera Zoom Fx and Procapture are both good. Thanks!!
Click to expand...
Click to collapse
You would probably have to push it via adb.
something along the lines of
adb push camera.apk /system/app
chmod 644 /system/app/camera.apk
reboot device
If you have an adb folder, put the camera.apk in the root of it, then run the commands. Should work.
You could also have a look at xdabbeb's camera mod. Might be able to get that to install.
http://forum.xda-developers.com/showthread.php?t=2548974
nrfitchett4 said:
For what you are seeking, nexus devices will be your best bet. They have the easiest developing because of not needed custom code. I really like the G2, but for me, the kitkat update was a bust (battery wonky, lots of random reboots, audio issues), so I went back to stock rooted JB. Very nice device that is very stable, but I don't care about AOSP, if I did, I would have gotten N5. Almost everything can be done through being rooted and xposed modules these days.
are you rooted, on a custom ROM? If you are on custom ROM you can just reflash ROM without wiping data and it will be added back. If stock, maybe someone can make you an apk you can install or the files can be pushed via adb.
Click to expand...
Click to collapse
nrfitchett4 said:
You would probably have to push it via adb.
something along the lines of
adb push camera.apk /system/app
chmod 644 /system/app/camera.apk
reboot device
If you have an adb folder, put the camera.apk in the root of it, then run the commands. Should work.
You could also have a look at xdabbeb's camera mod. Might be able to get that to install.
http://forum.xda-developers.com/showthread.php?t=2548974
Click to expand...
Click to collapse
Awesome, will give this a try.
---------- Post added at 03:35 PM ---------- Previous post was at 02:56 PM ----------
nrfitchett4 said:
You would probably have to push it via adb.
something along the lines of
adb push camera.apk /system/app
chmod 644 /system/app/camera.apk
reboot device
If you have an adb folder, put the camera.apk in the root of it, then run the commands. Should work.
You could also have a look at xdabbeb's camera mod. Might be able to get that to install.
http://forum.xda-developers.com/showthread.php?t=2548974
Click to expand...
Click to collapse
OK, I installed xabbebs update and it seemed to go fine, but no camera app still. I looked in settings->manage apps and camera is there!! Just no icon... any advice on how to get Camera back in my app drawer??? It just seems to be hidden.
---------- Post added at 04:06 PM ---------- Previous post was at 03:35 PM ----------
Finally fixed it. Turns out just moving the LGCamera.apk to system/apps instead of priv_apps did the trick. Thanks again for hte help!
miyagi241 said:
How is the buttons in the back?
Click to expand...
Click to collapse
They are so awesome and comfortable
Sent from my VS980 4G using xda app-developers app
Hi,
I really would need some help, think I kind of did a stupid thing yesterday. :crying:
I bought a secondhand LG G2 d802 a few month back and been very happy with it. I live in Singapore and yesterday I remembered that I had read that LG would realse the KitKat update for LG G2 in Singapore in mid March.
I went in under phone settings and serched for LG updates and it was a an upgrade on around 500Mb. I got really exited and started to download it. After it downloaded it restarted the phone but then open up an app called TWRP, and no mater how I try to rebot the phone it always comes back into TWRP.
What i kind of have understood is that my phone was/is rooted and I guess that didn't go well with trying doing a stock upgrade. I have been using stock android 4.2 so not had any custom roms installed.
My question: is there any way to either role back to my prev version (4.2) or install 4.4 without loosing my data (pictures, don't really care about the apps)?
(I have tried to find where the phone downloaded the update to run it through the install feature in TWRP but can't find the zip file. I can't enable the OTG port in TWRP so not sure how I would be able do run another ROM either)
Hope someone can help me!
Thanks,
Sandra
So it looks like your phone has a custom recovery installed and you tried to install the stock OTA. What you can do is either KDZ back to stock or flash a custom ROM. I would just flash a custom stock ROM. Easier and less steps.
Good luck!
Sent from my LG-D801 using XDA Premium 4 mobile app
mackster248 said:
So it looks like your phone has a custom recovery installed and you tried to install the stock OTA. What you can do is either KDZ back to stock or flash a custom ROM. I would just flash a custom stock ROM. Easier and less steps.
Good luck!
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi mackster248,
Yes that's correct, that was my thought as well but in TWRP under mount I can't enable OTG usb. So I cant read any ROM from any external source and I dont have any saved on the phone either so how would I be able to do that?
Thanks,
Sandra
laSandris said:
Hi mackster248,
Yes that's correct, that was my thought as well but in TWRP under mount I can't enable OTG usb. So I cant read any ROM from any external source and I dont have any saved on the phone either so how would I be able to do that?
Thanks,
Sandra
Click to expand...
Click to collapse
You can use the lg mobile support tool to flash a stock rom after going into download mode on the g2 (holding volume up and press power on). Don't flash Kitkat since there's no root option yet.
I don't see a way to keep your pictures though.
You can use the terminal in TWRP to nuke the fota partition and restore normal boot.
http://forum.xda-developers.com/showthread.php?t=2451696
laSandris said:
Hi mackster248,
Yes that's correct, that was my thought as well but in TWRP under mount I can't enable OTG usb. So I cant read any ROM from any external source and I dont have any saved on the phone either so how would I be able to do that?
Thanks,
Sandra
Click to expand...
Click to collapse
Ahhh, I see. You'll have to KDZ back to stock then. I think someone already posted the link, but if you need help let me know and I'll try to see what I can do. I have the T-Mobile D801 so I'd have to see if it's the same process for your D802.
Worked like a charm! Felt like an idiot when this happened to me. Good thing I backed up all data before trying the KK update. Thanks!
laSandris said:
Hi,
I really would need some help, think I kind of did a stupid thing yesterday. :crying:
I bought a secondhand LG G2 d802 a few month back and been very happy with it. I live in Singapore and yesterday I remembered that I had read that LG would realse the KitKat update for LG G2 in Singapore in mid March.
I went in under phone settings and serched for LG updates and it was a an upgrade on around 500Mb. I got really exited and started to download it. After it downloaded it restarted the phone but then open up an app called TWRP, and no mater how I try to rebot the phone it always comes back into TWRP.
What i kind of have understood is that my phone was/is rooted and I guess that didn't go well with trying doing a stock upgrade. I have been using stock android 4.2 so not had any custom roms installed.
My question: is there any way to either role back to my prev version (4.2) or install 4.4 without loosing my data (pictures, don't really care about the apps)?
(I have tried to find where the phone downloaded the update to run it through the install feature in TWRP but can't find the zip file. I can't enable the OTG port in TWRP so not sure how I would be able do run another ROM either)
Hope someone can help me!
Thanks,
Sandra
Click to expand...
Click to collapse
i have the same with the one you got and here is the fix for you
Here’s the easy fix:
Method 1: Using ADB access, plug in your phone and run this:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Now you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
Method 2: Using TWRP’s "terminal command" option to run this:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You’ll have to type that whole thing out, and be very careful with spaces and punctuation. One wrong letter and you could nuke your LG G2.
Hello everyone on the XDA community.
This is my first post here ..!
To begin excuse my very bad English, I used a translator to do this. Second, moderators apologies if it is not the right place, I ask a little patience and if you need to edit or move the topic, are in every right to do so.
Thanks in advance.
WARNING: This method has been tested by me, but do not hold me responsible for lost data on their devices or if they suffer irreparable damage. The method should be used with caution, following the steps explained below and must possess knowledge of the use of the tools used. USE AT YOUR OWN RISK.
Tools to be used:
BLU Phone Drivers
Universal ADB Drivers
SP Flash Tools v5.1436.00.000
Studio C D536U V08 5.0 Generic Stock Rom
Kingo Root
Easy Magic TWRP Installer for MediaTek
The first step and most important is: BACKUP, support all device data if possible make a backup of the complete ROM Stock, since in case of a "sudden death" can use this to revive the device. In the XDA Developers forums are methods to do this kind of support.
Steps that I have followed for an update ROM Stock, rooting and subsequent installation of custom recovery:
If you have any drivers installed for your BLU device uninstall them before seeing step 2.
Install the device driver for BLU
ADB drivers installed Universal
Enable USB debugging on development options
Download and install the ROM Stock mentioned above using the following::
Open SP Flash Tool.
Click scatter-loading then select the scatter file inside the ROM you downloaded (must be unzipped of course).
Change "Download" to "Firmware upgrade" (under scatter-loading file).
Click in "Download" button.
Take battery out of your phone and insert it again. make sure your phone does not turn on (If phone has an internal battery then just make sure the phone is off).
Plug in your phone to your PC.
The green check mark means you're good to go.
After installing the new ROM Stock, or if you were already using that version of the ROM Stock must install the Kingo Root, then connect your device and the program will recognize it immediately. The whole process is very simple and takes very little time, stay tuned to the screen of your device for confirmations.
Already having installed and running ROM Stock and rooting and undamaged device, run the program TWRP Setup, this will create the MTK-TWRP folder on your desktop, in it we find the TWRP.exe program which execute and follow the steps described in THIS POST.
And with that we have our rooting device with a new version of ROM Stock and custom recovery.
FINAL NOTE: In my case after installing the new version of ROM Stock did a search for update from the device, and found a new version: BLU_D536U_V10_GENERIC. The downloaded and installed before proceeding with the routing and the installation of custom recovery.
I hope you can use this guide and is very useful for everyone.
Best regards.
New Link Added 16/04/2015https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
tttony said:
Thanks for the guide, but the rom Studio C D536U V08 5.0 Generic Stock Rom in the mega link, is not available, can you upload?
Click to expand...
Click to collapse
Hi.
The following directory on the website of Mega contains all the Stock ROM for BLU devices, look inside the folder named "STUDIO SERIES" the "STUDIO 5 C - D536" folder, there you can download the ROM Stock V8 Generic.
https://mega.co.nz/#F!TplRURRI!LyAuAlNIBND_AOgu3bx6tQ
BLU Phone Drivers [link broken]
SP Flash Tools v5.1436.00.000 [link broken]
I have a bricked BLU Studio 5.0 C D536L. Can I flash this rom and files?
I don't know if D536U and D536L are the same devices (maybe L and U only a local id).
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Need a pointer or two.
vampirefo said:
I just got this phone from Walmart, even though I didn't use your method to root, as my rom is newer than the rom you provide, mine rom is BLU_D536U_V11_GENERIC seemed pointless to downgrade, I did download your Studio C D536U V08 5.0 Generic Stock Rom as it contained a file I needed to manually root my device.
I use Linux not windows, so the splash tool doesn't help, none the less I was able to root without any problems, using the one file from Studio C D536U V08 5.0 Generic Stock Rom.
Thanks
Vampirefo
Click to expand...
Click to collapse
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Your device is different than mine, I don't know anything about your phone.
Sent from my BLU STUDIO 5.0 C using Tapatalk
rwilcher said:
Hello. I have the same phone and conundrum. Sure would appreciate any pointers you could throw my way about successfully rooting this critter. It's a BLU Studio 5.0 Ce D536 Unlocked Dual SIM 5.0 Phone Android KitKat CellPhone.
There was a sale on ebay selling this new for 68.00 so I bit the bullet and bought it. Sure would appreciate it. I use both Linux and windows so I can relate. Any pointers would be great,Thanks!
Click to expand...
Click to collapse
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Root BLU Studio 5.0 C success
vampirefo said:
Post 3 seems to have files for your phone, should be able to use those files to root your device.
I had to build a custom recovery for my device, I built Carliv 3.3 recovery and TWRP 2.6.8.0 for my device.
Sent from my BLU STUDIO 5.0 C using Tapatalk
Click to expand...
Click to collapse
Thanks for that. Worked but was scary. Had to change shorts afterwards
Brick/Loop in Recovery.
Hey alakentu, thanks for this great thread. I have a problem at the moment: My, Studio BLU Studio 5.0 C (D536U), boots into the recovery and that is all. If I select Factory Mode it gets stuck on the BLU boot animation. I need to flash a new ROM through the original recovery and I need help with this. Can somebody help me ?
I'll give it a try
I have a 5.0C that has one SIM disabled. The SIM was filled with a platic blank that was glued down. I plan on backing up the custom Digicel ROM (D526 I think) and try to load the D536U stock ROM. I assume that if the hardware isn't customized, the stock ROM will have the code that enables and controls the two SIMS. :fingers-crossed:
I rooted and updated my previously locked phone to the V11 generic ROM. The generic ROM:
1. enabled the SIM that was blocked from the OEM.
2. unlocked both SIM slots.
The upgrade was well worth the trouble that I had with properly loading the USB drivers on my Windows 8 PC.
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
jmvaught said:
Same exact quandary here as @blackvitriol. Sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
jmvaught said:
Same exact quandary here as @blackvitriol. My d536u (Studio 5.0 C) sticks at the Blu splash screen. Is there an RUU mode of sorts with this device? If so, how do I access it without being able to fully boot this device?
Sent from my HTC6535LVW using XDA Free mobile app
Click to expand...
Click to collapse
i threw away that phone and bought a LG Tribute. Best decision ever. Also, thanks for teaching me this new word: quandary
jmvaught said:
SOLVED!! (Not that this is an active thread or anything)
So, in ALL of my research I didn't find one single instruction to fix the bootloop, corrupted ROM issue I had. Many claimed to be able to fix this issue, but all fell short because of ONE SINGLE error in the command line. I know, that's all it takes, BUT it may be difficult to figure out (as it was for me). This is all assuming you have your drivers installed and at the very least Minimal ADB/Fastboot functioning.
1. download the factory image (zip, rar, whatever) and UNPACK it somewhere you can easily find in Windows.
2. place the boot.img and system.img files in the same folder as adb.exe and fastboot.exe
3. put your device in Fastboot by doing the following:
a. press and hold Vol Up AND Power until you see the LCD flicker dark (you'll know it when it happens about 3 seconds into holding. Nothing else will happen yet. Nothing will appear on your LCD.)
b. press Vol Up twice and then Vol Down
*you should see three lines pop up in white text on your screen and it should show Fastboot beneath that. If not, pop that battery out and start over. It may take practice to get it right.
4. open a command window in your adb/fastboot folder.
5. Type the following:
fastboot devices
(your device should show up after you hit enter)<---don't type this
fastboot flash boot boot.img
(you should get some action on your device showing it flashed OK as well as in your command window)<---or this
fastboot flash /system system.img
(you should see it working on your device's LCD counting up from 0% to 100%)<---or this
fastboot reboot
(now wait and watch your device come back to life)<---or this
So what's different here from the other instructions out there? You're flashing the system partition by typing "/system system.img" instead of "system system.img"
Any questions, feel free to ask. Have a good one and good luck.
If I've helped you in any way and you want to help support my kids' college fund, please consider buying me a cup of coffee.
Click to expand...
Click to collapse
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Ivy.Crystal said:
Question/Comment...& Thank you.. However I am attempting to sideload adb style ROM from my BLU 5.5 to another's BLU 5.0 C D536u. Any non USB, PC Solutions? Last night we attempted to back up my system to an SD but failed. Pls I've spent hours researching I've installed the Necessary apps (from what I've read), pls help. Thanks again tho for posting this very useful info
Click to expand...
Click to collapse
Why are you trying to put 5.5 rom on 5.0?
Sent from my Venue 8 3830 using Tapatalk
I'm trying to find the 5.0 stock ROM to download it to my SD so the other person can put it in that way.
Or if u can just help me figure out how to get the 5.0C out of bootloop using my phone? Pls
Sent from my BLU STUDIO 5.5 C using Tapatalk
Anyone install the new update? My phone shows v14 is available, date 9/9/2015.
Sent from my BLU STUDIO 5.0 C using Tapatalk
N00b w/ "new SGH-I337 that is running original kernel & 4.2.2 & needs to be updated
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
SilkRoadDog said:
I am going to apologize from the start. I've read through a lot of threads here and have ended up more confused (and somewhat scared lol). I am a tad more skilled than average when it comes to PCs but I'm a complete mess when it comes to phones!
For various reasons, I like my old ATT Samsung S4 SGH-I337 but am hard on them and need to replace them about every 2 years (I usually wear out the power port among other things). I buy a replacement, copy over my apps, etc, maybe run a minor update and I'm good to go. This time, I bought a "new" open box S4 on Ebay for a great price but when I went to install all my apps, discovered that it was STILL (since it was "brand new") running Android 4.2.2 and the original kernel from the release in 2013! Ok, no big I thought, I will just run the ATT update and I will be good. Nope. Too far out of date and no one at ATT or Samsung is willing to help. I did learn that if I can get 4.4.4 on the phone, then I should be able to update it via ATT to 5.0.1 but I can't even find those files (or at the least any links to them that are still any good!)
Due to life issues, it is critical that I get this phone updated ASAP. Please, can someone spell out step by step in N00b-speak where I can get the needed files and how I update this phone to 5.0.1 or better? I'd really rather not root it if I can avoid it but will do what is needed. I'll buy you a beer (or reasonable beverage of your choice! )
Samsung Galaxy S4 (ATT) SGH_I337
Android 4.2.2
Baseband ver: I337UCUAMDL
Kernel ver: 3.4.0-453947
[email protected]#1
Sat April 27 17:06:05 KST 2013
Click to expand...
Click to collapse
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
StoneyJSG said:
I too was lucky enough to snag a S4 off ebay with the original kernel still on it. So with that said....do NOT update your phone! You're on the very special Android 4.2.2 jelly bean MDL bootloader! If you update, you will lose the ability to boot AOSP ROMs and install a custom recovery like TWRP.
AOSP ROMs can take you past Android 5.0.x lollipop and give you Android 6.0.x marshmallow or 7.0.x nougat. You can also boot custom touchwiz ROMs that will take you to Android 5.0.x lollipop. Use the towel root app to root the phone and then freeze any OTA with the titanium backup app. You can also benefit from my guide here:
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
Click to expand...
Click to collapse
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
SilkRoadDog said:
Thank you for your reply. So I root it, then where do I go from there? How do I know what ROM is what and which one will give me at the least what I had on the old phone (less bloatware would be nice but right now I am so up a creek that I would be ok with stock)? Also, do you have good links to the tools you recommend? One issue I have been having searching here is that the 3-4-year-old posts here have sketchy or dead links.
Click to expand...
Click to collapse
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
StoneyJSG said:
No problem, I always try to help when possible. After rooting you can follow my guide to get Loki doki installed. Then you can install a custom recovery like TWRP or clock work mod. My guide gets you clock work mod recovery installed but it's an old version. I use it though and it works fine for me. If you want TWRP recovery, you will have to search the web on how to install it with loki doki.
After a custom recovery is installed you can choose to boot touchwiz based ROMs or AOSP based ROMs like cyanogen mod. Custom touchwiz ROMs will look just like stock only modified (deodex, debloated, etc.) and AOSP ROMs will look like bone stock Android only with added features.
You can find AOSP ROMs in the original Android development forum here in the s4 forums. You can find touchwiz ROMs in Android development which is right under original Android development forum. Sorry, but I don't have any links to tools handy except for the link to my guide which I posted above in my last post. I use golden eye ROM on my s4 which is a stock based touchwiz ROM on Android 5.0 lollipop.
When booting ROMs, be sure that they do not have a bootloader update or else it'll override everything and will patch the loki doki exploit and lock down everything for good.
Click to expand...
Click to collapse
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
SilkRoadDog said:
Thank you so much for the reply. While I am very grateful, with all due respect, I understood only about half of it. Here is the deal. I'm an older guy N00b with chronic pain issues under an extreme amount of stress, and my cognitive abilities are not what they should be. There was a step by step guide posted back in 2015 that is what I need but most of the links are bad or sketchy. Like I said above, I really need something along the lines of "go here and here to get this software and put it in "X" place. Then press these keys and do "Y", then press those keys and do "Z". I'm really sorry to be so difficult but I am trying my best to get it.
Click to expand...
Click to collapse
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Your instructions say " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you." Do I do that before "loki doki installed and clockwork mod recovery."? If so, where is a good source for them? If not, when do I do I install them?
".
StoneyJSG said:
I gotcha, no problem. Okay so what's the status of your phone now? Rooted? Not rooted? To root, goto https://towelroot.com on your phone and click the big red thing in the middle of the page. Make sure you have a Wi-Fi or data connection to the internet, as this will root your phone. Then goto https://galaxys4root.com/galaxy-s4-...tt-or-verizon-galaxy-s4-sgh-i337sch-i545/amp/ to get loki doki installed and clockwork mod recovery. You can also install TWRP recovery instead of clockwork mod recovery, I THINK this is the link: https://galaxys4root.com/galaxy-s4-...rp-on-rooted-galaxy-s4-using-goo-manager/amp/
Galaxys4root.com is a reputable site ran by Mr. HIGH ON ANDROID himself, Xedomax aka Max Lee. The tools you need should be on his site for download and the links shouldn't be dead. He also has a YouTube channel with videos on how to do different things with your phone. My guide I wrote that I linked before, has step by step instructions on how to root and install a custom recovery and how to boot custom ROMs.
Click to expand...
Click to collapse
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
SilkRoadDog said:
Ok, It's not rooted yet so I will start down the path laid out. What do you recommend as a source for Touchwiz (wth is that anyway? lol) ROMs? I don't know enough about Android 6.0.x marshmallow or 7.0.x nougat to make the call there but I do want to be able to access the Google apps and play store as before.
Click to expand...
Click to collapse
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
SilkRoadDog said:
Ok, forget anything I typed here in the last hour lol. Somehow there were two locals and I was in the wrong one. So far so good. So back to the other question above. " " Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you."" I still need to do that, right? if so, where do I find those apps?
Thank you so much.
Click to expand...
Click to collapse
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
StoneyJSG said:
Touchwiz is the "skin" user interface that Samsung puts on top of Android. It is the stock SAMSUNG rom. Just Google touchwiz then Google stock Android, you'll see a difference. I like touchwiz so I am running a custom ROM called "Golden eye". You can download it from the Android development forum here in the S4 section. Other people like stock Android. The magic of being on the MDL bootloader is that you can boot touchwiz and bone stock Android ROMs. Most custom ROMs both stock Android and touchwiz based will let you access Google apps and the play store.
---------- Post added at 10:36 PM ---------- Previous post was at 10:21 PM ----------
You can get all those app except towel root on the play store. Once installed you can use ES file explorer to back them up to apk files then use the my files app that's on ya phone to move them to your SD card for use with your new ROM or keep them where they are since my guide tells you how to keep your data in tact...well for touch wiz ROMs anyway.
Click to expand...
Click to collapse
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
SilkRoadDog said:
Since this is a "new" phone and I have nothing to back up yet, do I need to run a backup or can I follow your guide from that point, clean things up and install the ROM of choice?
Click to expand...
Click to collapse
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
StoneyJSG said:
It's always good to make a backup in case anything goes wrong with your phone down the road you can get back to where you started without having to flash the MDL stock Rom in ODIN by connecting your phone to your computer. You should though keep a copy of ODIN and the MDL bootloader .tar ODIN file. However, it's entirely optional to make a back up so you could just follow the guide from that point and clean up for a ROM install if you don't want to make a backup.
You can also boot a ROM and then make a backup after you have everything set up. You can back up the stock Rom or any ROM you boot/install. That's the magic of having a custom recovery like TWRP or clock work mod.
Click to expand...
Click to collapse
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
SilkRoadDog said:
Unfortunately, since I already started the install before seeing this, I have no idea what I backed up or where it is. :crying:
First off, I want to thank you so much for the help. I owe you and would like to buy you a beer or the like. I have my phone back now! There were issues with the Golden Eye install (it froze at the Samsung logo for over an hour) and I had to wipe everything and start over then I was able to get it up and running. Is this the right one? https://forum.xda-developers.com/showthread.php?t=2313469
Quick question: Do you know if that ROM supports an external SD card larger than 32gig?
I am having some issues and so far am not thrilled with this ROM and am wondering if it's the right one or if I screwed up. It hasn't been worked on since 2015 and the dev is hasn't been responsive in years. On my phone, it's really buggy. It boots slow, apps hang when loading, a few don't work right, the screen can flash or freeze and TouchWiz keeps crashing like it was doing at the end on my old phone's life. Any ideas as to why?
Click to expand...
Click to collapse
If you made a nandroid backup with TWRP recovery or clockwork mod recovery, then the backup file will be on your phone SD card or internal memory. Use the my files app to find it. It should be under a folder called TWRP or clockwork mod.
Hey no problem man, I know how it is to goto a forum and have 87,000 people view your post yet nothing is said. Yes that link is the correct link to golden eye ROM. When booting a ROM for the first time it will get stuck at the Samsung logo for awhile, this is normal but it shouldn't be more than 20 minutes. I think the S4 can handle SD cards up to 128GB, it might only be 64GB though.
Very odd golden eye ROM is giving you issues, I have only had one problem with it and that was the text message app acting up every so often. When you booted golden eye did you use the Aroma installer so it just asks you questions and you pick what you want? If not wipe and start over using aroma, it's built into the ROM. Also be sure to tell Aroma you want to use the "imperium kernel". That's the kernel I am using. Golden eye ROM doesn't have a bootloader update in it, so you'll stay on MDL and not have to worry about your phone patching the loki exploit.
I think you can also use the hybrid max kernel, but I don't think it's in the Aroma installer so if you want it you will have to download it from the forums here and flash it separately.
Another thing you can try is just "nuking your phone" as explained in my guide that wipes everything and gives you a nice clean install. The only reason I included the "keep your data" method in my guide is because I just stumbled upon it by doing it on my phone.
If all else fails and as a last ditch effort, you could send the phone to me and I will see if I can get it up and running with golden eye ROM, then send it back. No guarantees though as I'm no developer or anything, just a guy that knows the basics of Android ROMs and root.
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
SilkRoadDog said:
Final report. It turns out the problems I've been having were related to the SU Super App. There have been complaints about the recent version. I thought that it was a corrupt install of Golden Eye so got a clean DL from another mirror and was getting ready to start all over. This time I was going to follow the dev's install instructions step by step instead of yours and his. However, I couldn't install TWRP as he instructed. It hung at 100% and never completed. I thought that maybe Super SU was the issue there so I uninstalled it and all of my other problems went away! So happy. Thank you for everything. I do owe you a drink!
Click to expand...
Click to collapse
Hey glad it finally worked out for you. You will need superSU though, try a different version of it and that might fix the issue you're having with the latest version. That is unless you have the kingroot super user app, then you can use that but it's not as good as superSU. I had problems with it authorizing my root apps so I got rid of it and installed superSU. No problem glad to help and no thanks needed but if you really wanna buy me a beer go for it lol.
Is this do-able with out unlock.bin??
I've tried using adb/fastboot. ADB reports the device OK; fastboot can't see the device.
I've tried all manner of drivers to load........ I know there are separate drivers for adb and fastboot.
This is driving me nuts.
Finally, are there different SUB-variants of the 996?? One generic and one US Sprint??
Thanks
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
ROMSG said:
You must use dirtysanta to root
[Guide][Tutorial] Root TWRP LG V20 using Dirtysanta[Most Variants][Noobfriendly]
Good day, Here's the modified dirtysanta method to root LG V20 and install TWRP. This guide will help you in rooting your device with much easier situation. Before you begin: (Your phone's internal storage will be wiped or simply formatted or...
forum.xda-developers.com
Click to expand...
Click to collapse
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Graf_Eberstein said:
The only issue with that response: The DirtySanta thread you link to lists the following devices, admonishing that any others will get bricked:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
- USS996 (BPT, UCL)
- Canadian (H915)
Unless there's a typo in it, the USS996 is NOT the same as the US996. The US996 is a carrier unlocked US variant. The other US996 is locked to US Cellular. A bit of clarity is necessary here...
Click to expand...
Click to collapse
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. I did some fairly general "looking" for that ROM elsewhere, found a couple of articles when Google-searching, but haven't had a chance to check those out (that will have to wait until tomorrow). If it turns out that there is no alternate link to the ROM, are there any other ways of getting it, short of looping @Tilde88 in?
Graf_Eberstein said:
Thank you! I am looking that over. One question I do have for you: Is that dump backup needed for anything beyond the EFS to get the IMEI? Asking only because I was able to extract the IMEI already. I'm not physically working on this till the weekend, so I'm going to read up/download stuff in the interim and go from there. If I end up with questions (and I just might from the bit I've read so far*), I'll append this post or reply to it.
* This is an example of where the uncertainty sets in: "For official US996 model owners that do not want to void their warranty, follow the Dirtysanta Sprint(LS997) method but make sure to flash a US996 Stock rom instead." I'm assuming "official" applies to an actual V20 model US996, regardless of carrier/unlock status. I'm extrapolating that the H915 is an US996 with a differently configured kernel. Since the LS997 is only mentioned separately, is the 997 a CDMA version of the (GSM) 996?
LTE is inferred, GSM is for distinction, so I'm assuming the 915 and 996 are GSM devices. I also know Sprint is/was a CDMA carrier. CDMA hardware would infer different modules would be loaded by the kernel, than for GSM, and could therefore hang or brick the device. At least that's where the rail line used by my train of thought takes me. Or, does the difference between CDMA and GSM versions not matter?
You are correct about the broken links: Tilde88's US996 100% Stock deODEXEd Rom, which is listed in the linked article, is a bad link. Since I haven't gotten past the first post yet, I'm going to see if I can find that elsewhere and report back.
Click to expand...
Click to collapse
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Darnrain1 said:
Sometimes downgrading your firmware to root your phone will corrupt your EFS on the phone and you have to restore it to get cell service working again or to bring back your IMEI number.
There are four files that are your EFS.
With the phone powered off, hold the down vol and plug in usb to computer to restore EFS.
fastboot flash fsg fsg_COM6
fastboot flash misc misc_COM6
fastboot flash modemst1 modemst1_COM6
fastboot flash modemst2 modemst2_COM6
fastboot reboot
Click to expand...
Click to collapse
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Graf_Eberstein said:
Thank you.
FYI, I just amended my prior response (above) re. the ROM as well.
Click to expand...
Click to collapse
Your welcome,
Stock Oreo Rom, flash in order But there are a lot more roms for the Lgv20 you can look around if you want.
LG V20 ROMs, Kernels, Recoveries, & Other Developm
US996 DIrtysanta Rom
ezV2020 kernel for Oreo link
Magisk-v21.4.zip
Latest version of twrp link
Darnrain1 said:
I found this some of the Links are broken.
V20 [H915|US996] DirtyElf Bootloader Unlock and Root guide
Firmware
US99610f_00_1205.kdz
usb drivers for windows
Terminal Emulator for Android "f-droid Download APK at bottom of page"
Before you flash the KDZ to downgrade your firwmare make a DUMP backup of ALL files first it will have your EFS and that's very very important it has your IMEI number. You don't need to dump system or cache.
Click to expand...
Click to collapse
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Graf_Eberstein said:
Ok, so I finally got to where I'm able to run that dump backup. I've been at it for the better part of 8 man hours, and it keeps crashing. Finally got everything backed up except SYSTEM IMAGE. Whenever I try to back up that segment, the backup crashes. You said I don't need to do this against CACHE, which I get. There's both a SYSTEM and a SYSTEM IMAGE, so now I'm wondering if you meant the latter instead of the former... If not, how do I get past this obstacle?
FWIW, I'm writing to an otherwise empty, brand new 32 GB Class 10 card. Initially I was using a surplus 16 GB card, then realized that I was coming up around 4 GB short, and pegged the failure on that. But the same happens on the larger card. In case it matters, the backup gets to about 60% before failing...
Click to expand...
Click to collapse
Your phone is rooted great.
DUMP backup with LGUP. Might not be to late. Just hold vol up and plug in usb to phone and computer. Go into LGUP and choose DUMP all files. You don't need to dump system or cache. This will save all the files on your computer. Back the files up like google drive or something.
Take battery out and put back in. Then you want to boot into twrp and do a format.
Then your ready to install an OS on your phone. Why don't you check out my rom I made it's stock Oreo debloated. There are some good guides on there also you can follow. link
If you need any more help just ask. I don't mind.
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Graf_Eberstein said:
I just wanted to thank you for the guidance to date. Great news: After many fits, starts, wrong turns, interruptions, and muckups both real and imagined, my V20 now has Oreo Lemondrop installed, and I presume it is also rooted.
With the initial hurdle overcome, it's time for new questions (see photos for the first three):
* The device reports no S/N. Normal?
* The OS reports no kernel version. Normal?
* The device still boots to the red triangle before loading Lemondrop. I was under the impression that would go away now, or am I wrong?
* A lot of games and other crud is being installed by Mobile Services Manager. Is that because I missed something?
The latter may not matter much: I'm going to move the SIM from my regular phone to the V20 to see if it will make/receive calls. If it does, it'll get a SIM of its own, so I can use it as a second line. If it doesn't work (I've seen posts about bands not working, etc), I'll be done with it altogether.
However, should the phone work, what'll make this whole enterprise a complete success, will be to install a more current Android release; I'm expecting 10 or 11, but would be tickled if it's 12 or 13. But first things first...
Click to expand...
Click to collapse
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Darnrain1 said:
Yeah no SN and no Kernel is normal. It's also normal to have the boot screen come up, it's because your phone is rooted now.
I have to run Oreo because LTE is not working in crDroid or Lineage os. There are proprietary drivers that are in Oreo to make LTE work and they are not in any other android os. But if all you need is 4G then maybe another os would work for you. In the USA they did away with 4G only LTE now. So I thought I would make the Lemon Drop rom, if I have to use Oreo why not make it fast. Plus most everything works in Lemon Drop. Like second screen and so on. I have used crDroid before it's good I will link the files for you.
Update: I found and removed Mobile Services Manager in the latest version of Auto_Debloat. Thanks for bringing this to my attention.
crDroid 11 just format and flash in twrp reboot.
also flash Magisk-v21.4.zip so you can have root.
you may have to flash twrp also I am not sure, it's been awhile before I install crDroid. You can always flash twrp in fastboot mode if you have to.
Take Care.
Click to expand...
Click to collapse
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Graf_Eberstein said:
Thank you again, and you're welcome for the bit on the Mobile Services Manager. My apologies for the lag in responding too; real life got in the way for a bit there. I'll look into your suggestion as I get a chance and will report back.
Click to expand...
Click to collapse
Not a problem. Because I only have an H910 I didn't get all the bloatware on other lgv20 phones. But that Mobile Services Manager is a huge bloatware that installs more bloatware. So I thought I would try and find it and remove it in the latest version. You can update Auto_Debloat and it should get rid of that Mobile Services Manager for you. All you have to do is just flash the new version in twrp and reboot.