Related
Beautifully working VU2.39. Then decided to add new lock ring. Totally messed up phone.
Restored with ROM Manager to prior situation, but have totally lost phone radio (and therefore phone, 3g etc.) Have tried restoring many times, tried airplane mode, wiped cache...all with no solution.
Shows no service, no CDMA or other option exists in settings, phone info shows:
Signal Strength =0
Mobile Network Type unknown
Service state= out of service
What did I do here??? How to fix???
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
lair12 said:
Have now done factory reset and called Verizon. They tried to change manual codes but to no avail. Seems my radio got fried by applying the Captain America launch ring. Is this possible that that was the cause. Worked perfectly before I patched this today.
Help! I don't want a new phone as it will come with 2.3.4 not rootable.
Click to expand...
Click to collapse
2.3.4 is definitely rootable. And I don't think a ring would change that much. Have you tried flashing a New radio?
Sent from my Incredible 2 HD using XDA App
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
lair12 said:
I tried flashing new radio. No difference.
I just can't believe that the sense link patch would have actually physically damaged the radio and killed the system, but I cannot get anything to "activate" the radio. In manual program mode ##778, the display settings say "radio version 1.09.01.0622", so the software should be there. But it cannot find the hardware.
I have matched my NAM settings and Home SID to the same as my wife (her phone is fine).
Click to expand...
Click to collapse
Try flashing this Radio. It's the last one on the list.
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
lair12 said:
No difference whatsoever! So what do you think has happened and how and why? How could flashing the Captain America htc unlock ring have caused such destruction?
Any how could it fry or totally immobilize the radio? I really do not want to replace the phone, but am giving up hope for a solution. It's got to be either something very simple, or the radio did get fried.
And I still don't see where I can unlock and root 2.3.4 on this forum or at the Revolutionary site.
Click to expand...
Click to collapse
Well...... Was the lockring made for your specific ROM and phone? If not, that may be why.
Have you tried any other ROMs to make sure it's not just something interfering in the ROM itself?
To root 2.3.4, you have to downgrade the hboot v.98 to v.97 following these steps found here.
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
lair12 said:
Link came from here: http://forum.xda-developers.com/archive/index.php/t-1135020.html
SHould this have bricked the radio??
Can you resend root 2.3.4 link, as the one above goes back to the radio instructions.
Many thanks.
Click to expand...
Click to collapse
Post edited so the link for 2.3.4 root should work. But, yeah, that's for Thunderbolt, not the DINC2. Try flashing another ROM or full wipe/reflash of VU 2.39. Don't apply any mods until you find out if it works, and see if someone can port the lockring to the DINC2.
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
lair12 said:
Wiped twice regular and dalvik, installed the clean ROM for phone I had saved. DEAD Radio. Bummer, but thanks for you help.
Mobile Network Type= unknown
Service State= out of service
This has not changed with any fixes I have tried.
Click to expand...
Click to collapse
What about the .722 radio?? Earlier you said you had the .622 radio which is an older one. If that doesn't work, boot into hboot and factory reset (I think this works). Then you'll probably have to re-root. Otherwise, you can get a new phone, and root via the downgrade.
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
lair12 said:
Absolutely no solutions anywhere. Tried everything twice! New phone on the way. Very frustrating situation.
Click to expand...
Click to collapse
Sorry to hear that.... Let us know how the rooting goes.
Sent from my Incredible 2 HD using XDA App
Hi all I have just registered on xda but i'm using it from quite a while.
I'm using htc wildfire bought from my friend fresh from box it was in Era operator currently t-mobile. My operator is Orange. I was using my phone with stock rom for about 10months and decided to root it and flash custom rom. I used guide from this site and after bricking it second attempt was successful. So I was using CM7 installing apps and all over. And now i have really serious problem. My phone tells me there is no service.
What I done trying to repair:
Changing 2g to 3g and back.
Restart
Factory reset from menu
Factory reset from CWM
Battery pull
dialing *#*#4636#*#*
re flashing radio
Installing newer version of CM7
Some of methods seems to work for about 1-3days. But now none of them is working...
Please help
Groofy said:
Some of methods seems to work for about 1-3days. But now none of them is working...
Please help
Click to expand...
Click to collapse
which method seem to work temporarily? What radio do you currently have? Did you try to flash a different radio? (you could find radios here: [REF/GUIDE] [29/07] The Complete Wildfire Index - xda-developers)
eventcom said:
which method seem to work temporarily? What radio do you currently have? Did you try to flash a different radio? (you could find radios here: [REF/GUIDE] [29/07] The Complete Wildfire Index - xda-developers)
Click to expand...
Click to collapse
Ok thanks for really fast reply.
temporarily seem to work factory reset. dialing *#*#... also seemed to work for some time.
My radio is Radio_13.55.55.24H_3.35.20.10 that one was original and i flashed the same version, but I'm not sure if this is the problem.
Now I'm using my old phone so sim card is good.
EDIT:
My wifi is not working. Possible reason: I was playing with reverse tethering and one method via wifi required to put wpa-suplicant or something like that. Maybe this file also corrupted rest of services? GPS works fine...
Groofy said:
Ok thanks for really fast reply.
temporarily seem to work factory reset. dialing *#*#... also seemed to work for some time.
My radio is Radio_13.55.55.24H_3.35.20.10 that one was original and i flashed the same version, but I'm not sure if this is the problem.
Now I'm using my old phone so sim card is good.
EDIT:
My wifi is not working. Possible reason: I was playing with reverse tethering and one method via wifi required to put wpa-suplicant or something like that. Maybe this file also corrupted rest of services? GPS works fine...
Click to expand...
Click to collapse
well, doesn't look to be the radio - but that's just guessing. Did you get those problems directly after rooting and installing CM7 or did it work initially?
eventcom said:
Did you get those problems directly after rooting and installing CM7 or did it work initially?
Click to expand...
Click to collapse
After rooting and installing CM7 everything was perfect that was about 4 months ago. Problems with cell service started when i changed my sim card to surf over internet, and then i used notification bar application 2g/3g to force 3g. And since then I have problems, somewhere i read there could be problem with sim connection. Now i'm using my htc without sim card and when i dial *#*#4636 in gsm disconnects: DATA State DcInactiveState disconnected with last try at 00:59 fail because No Error. And What I noticed when i wanted to change network type in this menu it was returning always to previous state... What is interesting my phone tells me that signal strength is: -79dBm 19asu.
Groofy said:
After rooting and installing CM7 everything was perfect that was about 4 months ago. Problems with cell service started when i changed my sim card to surf over internet, and then i used notification bar application 2g/3g to force 3g. And since then I have problems, somewhere i read there could be problem with sim connection. Now i'm using my htc without sim card and when i dial *#*#4636 in gsm disconnects: DATA State DcInactiveState disconnected with last try at 00:59 fail because No Error. And What I noticed when i wanted to change network type in this menu it was returning always to previous state... What is interesting my phone tells me that signal strength is: -79dBm 19asu.
Click to expand...
Click to collapse
i suggest to carefully check your APN settings and try out the different modes for mobile data (force wcdma might fail in some conditions if I'm correct - check prefer and the other modes, too, if they'll do)
Swyped from my HTC Wildfire (Buzz)
eventcom said:
i suggest to carefully check your APN settings and try out the different modes for mobile data (force wcdma might fail in some conditions if I'm correct - check prefer and the other modes, too, if they'll do)
Swyped from my HTC Wildfire (Buzz)
Click to expand...
Click to collapse
APN settings are correct. I checked them on orange site, on many forums and tried them all. Currently my phone runs wdcma preffered. Now i'm about 20-30m from the transmitter. And still "no cervice". Any other ideas? Somebody told me to install stock rom and then install cm7 on it. But i have no idea how to do it. I can't remember i wrote this before but wifi is working. Sim card is good but i'm using it on nokia 6030. I tried even to put some paper to push harder sim card to better contact and no result.
Hmm, so if you double checked the apn settings and you did activate data in settings/network& wireless and if the SIM seems to be ok it's indeed a good idea to flash a different radio... look at the index thread linked above - all the files and information there. Try the radio that ends with 18.25 (bear in mind to use clockworkmod 2.5.x for flashing).
If that still doesn't work, just flash the current one again to see if that will do (radio problems usually are caused by the missing possibility to wipe or format the radio partition itself).
Crossing fingers
Swyped from my HTC Wildfire (Buzz)
eventcom said:
Hmm, so if you double checked the apn settings and you did activate data in settings/network& wireless and if the SIM seems to be ok it's indeed a good idea to flash a different radio... look at the index thread linked above - all the files and information there. Try the radio that ends with 18.25 (bear in mind to use clockworkmod 2.5.x for flashing).
If that still doesn't work, just flash the current one again to see if that will do (radio problems usually are caused by the missing possibility to wipe or format the radio partition itself).
Crossing fingers
Swyped from my HTC Wildfire (Buzz)
Click to expand...
Click to collapse
Sorry still no result.
Hope you have more ideas...
Have you tried to restore the backup of your stock rom with the new sim?
This may solve the problems associated with Sim Toolkit
If everything works you just have to do a clean install of CM7
is an attempt, but if you do not know what else to do ... (I would try) :silly:
quack75 said:
Have you tried to restore the backup of your stock rom with the new sim?
This may solve the problems associated with Sim Toolkit
If everything works you just have to do a clean install of CM7
is an attempt, but if you do not know what else to do ... (I would try) :silly:
Click to expand...
Click to collapse
Hmm that could work but there is problem... I don't have backup of my stock rom...
New solution
Ok. My friend have htc wildfire on stock ROM. I would like to make copy of his ROM. I know i need to s-off his phone, push revolutionary recovery, and just make backup? If I'm thinking right this would give me zip of his ROM that I can copy to my SD-card and install it like other ROMs?
Thanks in advance for repy.
Groofy said:
Ok. My friend have htc wildfire on stock ROM. I would like to make copy of his ROM. I know i need to s-off his phone, push revolutionary recovery, and just make backup? If I'm thinking right this would give me zip of his ROM that I can copy to my SD-card and install it like other ROMs?
Thanks in advance for repy.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=33351487
If you are s-off then download the first rom in this post, drop it on your sd card and rename it to PC49IMG.zip then boot into hboot and let it update. When your phone boots up again it will be stock but still s-off so you won't need to mess about unlocking everything again.
Sent from my GT-I9100 using Tapatalk 2
Used stock ROM. Installed. Tried all the radios in the meantime and still no signal.
God please say that You have more ideas.
imo it's broken gsm module (antenna). try to flash some other roms, maybe it will work.
PS, widze ze kolega z Polski napisz na priv to sprobujemy cos wymyslic
Wysyłane z mojego HTC Wildfire za pomocą Tapatalk 2
Hi all, so I'm in quite the predicament. I can't seem to reestablish a mobile connection via Verizon at all since I've overwritten the stock ROM with Cyanogen. I have Inc2, now loaded with CM7, awaiting some help.
First I unlocked the bootloader and flashed CWM Recovery.
Next I flashed Build 4 CM10 http://forum.xda-developers.com/showthread.php?t=1934288 <--check it out here.
I couldn't establish any network connection whatsoever. So i wiped and flashed CM9 with the hopes it would be more stable. http://forum.xda-developers.com/showthread.php?t=1932573 <--again check that one out.
Again, no network connection. Lastly, I reverted to CM7 (because it was the last stable release directly from Cyanogen). http://wiki.cyanogenmod.org/index.php?title=Vivow_Info <--looky here.
I've searched far and wide, trying everything possible. From simply switching on/off airplane mode to manually typing in the Verizon APN. I just can't establish network connection now...and the kicker - I forgot to backup the stock ROM so I'm currently stuck. Please help
This thread may be of some help. Didn't do me much justice however. http://forum.xda-developers.com/showthread.php?t=1691017
Bumping. Somebody please help...Also if anyone has a stock ROM they could share, that'd do fine as well. I'm curious if stock ROM would re-enable the radio (if that's the actual problem).
Sane116 said:
Bumping. Somebody please help...Also if anyone has a stock ROM they could share, that'd do fine as well. I'm curious if stock ROM would re-enable the radio (if that's the actual problem).
Click to expand...
Click to collapse
You don't need to bump a thread after 30 minutes -.-
nitsua98 said:
You don't need to bump a thread after 30 minutes -.-
Click to expand...
Click to collapse
Goes to show how desperate I'm becoming.
Have you tried changing your mobile network? Settings > more> network mode
Been there. You can try different radios from here, but BE CAREFUL. Take the following precautions:
Because you're on Verizon, only download 'x.x.01.xxxx' radios.
After putting the ZIP file on the SD card, verify the MD5 hash to ensure the file didn't get corrupted during download or during transfer to the SD card.
Plug the phone into your charger before installing. You don't want it shutting off during install.
Don't flash the same radio that your phone already has installed.
If all else fails, try the stock 2.3.3 RUU from HTC. If you can find a working download link to that, please share.
Airo18 said:
Have you tried changing your mobile network? Settings > more> network mode
Click to expand...
Click to collapse
I've tried everything in the books. Manually setting my APN according to the Verizon settings. Also did trial and error booting and rebooting each network type to no avail.
A few things I noticed in the CM9 ROM (maybe bugs?):
The preferred network mode typically defaults to GSM/WCDMA upon reboot
The APN I create often disappear upon reboot.
Mobile Networks>Network Operators will either search endlessly or sometimes find both AT&T and T-Mobile as options, both of which won't actually connect as I have a Verizon SIM.
And in response to Slinkwyde:
To verify the MD5 hash, what needs to be done more specifically? (I'm learning as I go ) Did flashing a radio do the fix for you? I'll try this suggestion and post results.
Sane116 said:
I've tried everything in the books. Manually setting my APN according to the Verizon settings. Also did trial and error booting and rebooting each network type to no avail.
A few things I noticed in the CM9 ROM (maybe bugs?):
The preferred network mode typically defaults to GSM/WCDMA upon reboot
The APN I create often disappear upon reboot.
Mobile Networks>Network Operators will either search endlessly or sometimes find both AT&T and T-Mobile as options, both of which won't actually connect as I have a Verizon SIM.
And in response to Slinkwyde:
To verify the MD5 hash, what needs to be done more specifically? (I'm learning as I go ) Did flashing a radio do the fix for you? I'll try this suggestion and post results.
Click to expand...
Click to collapse
Verizon sim? What country are you in, are you using gsm?
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
Verizon sim? What country are you in, are you using gsm?
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Yes, verizon sim card. I'm in the USA. And I believe I am supposed to be using GSM but I don't fully comprehend the differences between each type. However I have tried setting each type in system settings>mobile networks with no data showing at any point.
Sane116 said:
And in response to Slinkwyde:
To verify the MD5 hash, what needs to be done more specifically? (I'm learning as I go ) Did flashing a radio do the fix for you? I'll try this suggestion and post results.
Click to expand...
Click to collapse
Yes, flashing a radio worked for me. The simplest way would be to use an MD5 checker app. Use the app to make sure the file on your SD card matches the MD5 value given in the radio thread I linked to.
One more precaution: Don't ever flash the same radio version that your phone is already using. That caused problems with the original Incredible and might also cause problems with the Incredible 2. To see what radio version you have, go to Settings and look around in About phone, Phone info, or something to that effect. "Baseband" is another word for radio.
Sane116 said:
Yes, verizon sim card. I'm in the USA. And I believe I am supposed to be using GSM but I don't fully comprehend the differences between each type. However I have tried setting each type in system settings>mobile networks with no data showing at any point.
Click to expand...
Click to collapse
Short version: For Verizon, you want CDMA with EvDO.
Longer overview: CDMA vs GSM, and what it means for the Incredible 2
Verizon Wireless and Sprint use CDMA. AT&T and T-Mobile use GSM. CDMA is popular in the United States, but around the world GSM is far more common. All GSM phones use SIM cards, but most CDMA phones don't. The two kinds of CDMA phones that do have SIM cards are world phones (phones with both CDMA and GSM) and LTE phones (faster data speeds).
The Incredible 2 is a world phone (without LTE) and comes with a Vodafone SIM for overseas travel. This Vodafone SIM also has Verizon Wireless branding on it. The Verizon Wireless company is jointly owned by Verizon and Vodafone, a European carrier based in the UK. Verizon world phones have to be unlocked to use AT&T or T-Mobile, because Verizon doesn't want their customers switching to a competitor.
SIM cards make it easy for GSM users (not you) to use their carrier account in another phone. They can just swap the SIM. For CDMA carriers (such as Verizon), swapping service to a different phone requires contacting the carrier.
Sane116 said:
Yes, verizon sim card. I'm in the USA. And I believe I am supposed to be using GSM but I don't fully comprehend the differences between each type. However I have tried setting each type in system settings>mobile networks with no data showing at any point.
Click to expand...
Click to collapse
You don't need the sim card at all then, you're CDMA. If you're not on it already i would recommend flashing the latest ics firmware, it can be found in the ICS leak ROM thread posted by nitsuj17 , it includes the newest radio
Sent from my Incredible 2 using xda app-developers app
Jeremy is referring to this thread: http://forum.xda-developers.com/showthread.php?t=1846304
Note that he's specifically suggesting that you install the ICS firmware. You don't have to install the ROM.
jeremytn86 said:
You don't need the sim card at all then, you're CDMA. If you're not on it already i would recommend flashing the latest ics firmware, it can be found in the ICS leak ROM thread posted by nitsuj17 , it includes the newest radio
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Slinkwyde said:
Jeremy is referring to this thread: http://forum.xda-developers.com/showthread.php?t=1846304
Note that he's specifically suggesting that you install the ICS firmware. You don't have to install the ROM.
Click to expand...
Click to collapse
Okay so what you both are suggesting are to just install the firmware, assuming I am already running the CM9 ROM? Because the firmware includes the radio. And this is done by renaming the firmware to PG32IMG and flashing it through hboot? Would this be an easier course of action than installing a radio alone? My phone is S-ON and if I'm correct, S-OFF needs to be active to install a radio.
Yes, you can install the firmware to get the radio, and the file name needs to be PG32IMG.zip for hboot. S-OFF is generally required for this sort of thing, yes.
Slinkwyde said:
Yes, you can install the firmware to get the radio, and the file name needs to be PG32IMG.zip for hboot. S-OFF is generally required for this sort of thing, yes.
Click to expand...
Click to collapse
Thanks so much guys, you've been more than helpful. Now to get some work done...I'll post results either tonight or tomorrow once I've finished. Wish me luck!
Put the battery cover back on. It'll instantly drop sig. when not installed.
TA4S
I'm currently trying to downgrade Inc2 so I can S-Off in order to flash either new firmware or radio. I am following this http://forum.xda-developers.com/showthread.php?t=1726134 and cant seem to download the necessary RUU 2.3.3 for Inc2. It seems as if the downloads link is dead. Can anybody link to such a file? I cant seem to find one anywhere.
EDIT: Found a stock (or as close to stock I could find) ROM for INC2 >> http://d-h.st/I2g
Also, I may have a potential reason as to why I'm having this ***** of a problem. I originally unlocked bootloader using the HTCdev tool. At the time it was my understanding that the process did not matter as long as the results were the same. However it seems now that using their tool makes it so you can't flash radios and need to extract and separately flash ROM kernels. So does this mean flashing any of the CM ROM's I tried never included the radio portion?
Just stabbing at ideas. Feel free to verify/call me out.
Sane116 said:
Also, I may have a potential reason as to why I'm having this ***** of a problem. I originally unlocked bootloader using the HTCdev tool. At the time it was my understanding that the process did not matter as long as the results were the same. However it seems now that using their tool makes it so you can't flash radios and need to extract and separately flash ROM kernels. So does this mean flashing any of the CM ROM's I tried never included the radio portion?
Just stabbing at ideas. Feel free to verify/call me out.
Click to expand...
Click to collapse
Roms NEVER include a radio, its always separate. something weird has happened to you, I'm sure flashing new radio would fix it for you but you're dev unlocked which is gay Lol. When you flashed the cyanogen ROMs did you pull kernel and flash like you were supposed to, if not i can't believe you got it to boot but that may be a problem also.
Sent from my Incredible 2 using xda app-developers app
jeremytn86 said:
Roms NEVER include a radio, its always separate. something weird has happened to you, I'm sure flashing new radio would fix it for you but you're dev unlocked which is gay Lol. When you flashed the cyanogen ROMs did you pull kernel and flash like you were supposed to, if not i can't believe you got it to boot but that may be a problem also.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
If it helps, here is the process that I have used every time I flash anew ROM, working every time (excluding the radio of course.http://www.youtube.com/watch?v=ujFWZbgj6bY
Because I HAD (I actually just reverted back and am currently getting S-OFF to flash a radio) the HTCdev unlock, I manually booted the boot.img after entering recovery and wiping/formatting all the necessary things. Skimming the video might give you a better idea.
However I'm now hoping S-OFF will allow me to reroot, flash CWM, CM9, and of course a radio. Currently in the process of trying to run Revolutionary.
Since the new Jelly Bean bootloaders have shown up, I see a lot of people talking about updating them. There are a few things I would recommend to do when flashing them. The first is the small, but present, danger that you can hard brick your phone. And I mean the "Need jtag to make it work" hard brick. Typically the cause of these bricks is an error or interruption of communications between the device and the computer. The other is mismatched or outright improper bootloaders.
Below is a list of things to decrease the possibility of permaborking. Keep in mind that following this list will not 100% remove the danger of flashing bootloaders, but will increase the chances of a successful flash.
Flashing bootloaders is dangerous. They are one of the few things that has the possibility of hard bricking your phone. For that reason, here are some good things to do to prepare for flashing them.
Have a good, reliable data cable. Interruption of communication between your phone and pc will most likely cause a hard brick with bootloaders.
Use a usb port on the back of your computer (or #1 on a laptop). Communication, again.
Have a jig. Not much help if you hard brick, but if you soft brick its very nice to have.
I personally flash bootloaders from a good laptop with a fully charged battery. If there is a power outage, the battery in the laptop will have saved my phone.
When flashing bootloaders,or anything with Odin, don't touch your phone after you connect it in dl mode until the phone reboots. Goes back to the communication issue.
For problems/tips on connection issues, look HERE
To determine which bootloader you have, check out this app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
To check your bootloader version
(thanks to KorGuy123 for the link)
For those that like to use Terminal Emulator, just type this:
HTML:
su
getprop ro.bootloader
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
xlj1000 said:
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Flashing Bell Galaxy S3 Bootloader on AT&T phone
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
If it's not the exact bootloader for your phone, don't flash it.
mrhaley30705 said:
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Click to expand...
Click to collapse
Maybe use Mobile Odin?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
mrhaley30705 said:
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
Click to expand...
Click to collapse
Awesome, gotcha. Learn something new every day.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mi modelo is i747m telcel mexico which should flash
Obridgenut said:
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
Click to expand...
Click to collapse
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it,
As for the other guy having an issue, you can update your phone over Kies. Your issues sound like its a bad rom you put on your phone. And you can never brick your phone. Its what people to say to scare you to get you to use their methods.
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
osmxgohan said:
mi modelo is i747m telcel mexico which should flash
Click to expand...
Click to collapse
The correct firmware from your provider should have bootloader in then
andy_d0 said:
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
It's possible that the ota update to jelly bean pushed the latest bootloader to your phone.
TheStrokerace said:
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it, ]
The AT&T SGH-I747 does not offer the option to toggle LTE off under the Settings Menu, as do the Bell, Telus etc SGH - I747Ms. And although I can and have flashed all sorts of different ROMs, the AT&T modem is RAT locked and I so far have been unsuccessful flashing any modems other than AT&T modems. I am not sure whether this is a software issue or whether it is to do with the AT&T bootloader, hence the question about flashing a Bell bootloader. Any time that I try to flash a non-AT&t MODEM, I temporarily lose my IMEI number and the phone will not work at all. But there is a work around by entering into the Phone Control settings as discussed on xda, ( http://forum.xda-developers.com/showthread.php?t=2116346) which I have been using successfully.
Click to expand...
Click to collapse
I don't think changing the bootloader will change that for you.
mrhaley30705 said:
I don't think changing the bootloader will change that for you.
Click to expand...
Click to collapse
OK, Thanks anyway for your help.
How can I tell what version my bootloader is?
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
ubuntujason said:
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
Click to expand...
Click to collapse
Install this, hit check, goto second screen and it'll say bootlader
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Easiest way to check is install terminal emulator.
Type
su
Grant it permission
Now type:
getprop ro.bootloader
These commands are case sensitive, so type carefully
hello guys
need yout help, tried searching google for sulotion but came up empty.
ive rooted the lg g4 h815(android 6.0-V20c-SEA) before via iroot pc but after factory reset its returned to be unrooted.
when i try to root again its keep failing because of debugging issue (the software keep telling me its not in debugging altough it is)
i think the problem is when i do usb debugging - connecting to pc the option is checked in the check box but it turns gray.whats the problem is? how can i fix it ?
thank you in advance
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, if the the G4 Factory Reset protocol deletes the system partition, and then reinstalls it, then this would explain why/if you lost root, I do not know if that's the protocol though. If iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
I recommend wiping Data, Cache and Dalvik from TWRP next time, if that's not what you did this time. :good:
Williquah said:
If you mean the USB debugging option is checked but gray when your phone is plugged in, that is normal, you cannot change that option when you're plugged in via usb.
I'm not familiar with iroot personally, I could take a look if you need though, but maybe revoke usb debugging authorizations through dev options then accept the pc's key fingerprint once again to "kickstart" iroot.
If you've rooted before through iroot on the same software version you're on now, it should work again without too much effort. Also maybe try switching to MTP (Media Sync) or PTP (Camera sync), or between the both until something happens.
That's all I can think of ATM, I'll probably go check out iroot right now, and think a little more and come back, but I wanted to give you a quick enough response. I wish you the best of luck though!
Edit: Forgot to mention that sometimes SuperSU may get uninstalled from factory reset, although I've never heard of that, if iroot roots and injects SuperSU as the root manager, try reinstalling it possibly.. unless you are 100% positive you are somehow completely unrooted. (Use a root checker to check if you still got it)
Click to expand...
Click to collapse
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
mikmikush said:
thank you for the quick response...
I tried the revoking and debugging again - but nothing.
i will try the mtp ptp thing (when i get home after work)
and will love to hear from you if you have another solution but thank you so much
Click to expand...
Click to collapse
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Williquah said:
No problem at all, I really do hope to fix this for you. Are you on the same software version as you were when you first rooted?/Which version is that?
Another thing I thought of, is your computer. Is it the same one that you used the first time? Do you have full admin access on it? Do you have all the LG drivers on it?
Do you have ADB/Fastboot fully installed on it? Obviously these are the first things you probably think about when you think about root, but I'm just making sure nothing is slipping by, you know?
Depending on what software version you're on, maybe we should try another root method if nothing works.
The last thing I'd say is to backup all your data/internal and flash the firmware you want to root on, but I really don't think we need to go that far.
P.S. I own a VS986 (VZW version of the G4) so I can only go to certain extents to reproduce/"debug" the problem you are having. Keep me updated!
Click to expand...
Click to collapse
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
About phone ????
mikmikush said:
ok step by step
model number h815
I rooted it a year ago or so , but i dont remember which pc (mine or my perents) and or version (mom's phone now its papa's ).
I would love to install international rom but since i bricked my note 4 years ago(don't judge was 16 years old girl without pation and expirience ) and just succsedd installing a new rom with my mate 8 , im afraid and still searching a suitable rom.
the drivers installed and it says that ADB/Fastboot fully installed on it (i will duoble check it when i get home )
all the data is backed up from papa's galaxy s5 hench the factory restart (we all moved from one phone to another haha)
sorry for any lang mistakes and for the long response
Click to expand...
Click to collapse
Sorry for forgetting the whole reason you're in this problem is because of a factory reset lol, of course you have your data backed up. And trust me, I understand about the brick, I really messed up my G3 2 years back. Thanks also for the device pictures, could you post a shot of "About Phone=>>Software Info". That would be great!
Funny thing I just did that same phone rotation thing very recently XD
Lol love rotation, here
mikmikush said:
Click to expand...
Click to collapse
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Williquah said:
Well, it seems that the factory reset must also have deleted the system partition, then reinstalled it with the most updated version.. which is not good for the current situation.
Notice Security Patch Level is "2016-01-01" and you're running Android M 6.0, means that the software you're on is very recent, if not the most recent. I did some looking around just now, but I couldn't turn up anything that achieved successful root on "V20c-SEA-XX", which is what you would need.
Technically you could try the stock firmware KDZ for your device, which should be 5.1.1, then flash it with like LGUP, but I seriously don't recommend that unless you find a thread that confirms a working downgrade from V20c-SEA, because if the qfuse does not match between firmware versions, you could easily end up with a hardbrick.
Here is the link to your stock firmware, in case you find that it is safe to downgrade from 20c-SEA to 10b-SEA:
http://storagecow.eu/index.php?dir=Xda/LG+G4/H815/
You could try this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
I'm not sure it will work, but I can't imagine it'd harm you, since it's LG official.
You could also try to fill the checkbox "OEM Unlock", and then try to unlock the bootloader via fastboot. I am not sure if this could possibly cause harm if it does not work properly, so try this at your own risk.: http://oneplus.wonderhowto.com/how-...all-custom-recovery-root-oneplus-one-0156099/ (It's all the same commands even though it says for OnePlus One device. If you happen to unlock the bootloader using fastboot, do not go on to Step 2 on that page)
If nothing works, you could subscribe to this thread: http://forum.xda-developers.com/g4/help/rooting-h815-v20c-sea-xx-t3371107
Or these may be helpful at some point: https://www.reddit.com/r/lgg4/comments/4dk9xt/lg_g4_h815_sea_v10e_kdz/
http://forum.xda-developers.com/g4/general/finally-h815-v10c-sea-xx-t3211920
https://www.reddit.com/r/AndroidQue...rading_lg_g4_h815_sea_with_locked_bootloader/
https://www.reddit.com/r/lgg4/comments/4aa1pi/root_question_h815_v20cseaxx/
http://forum.xda-developers.com/sitesearch.php?q=H815 V20c-SEA
Here's the LGUP software if you ever need: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
I know alot of the links and such you can do by yourself, and may not be super helpful yet, but it should give you the information you need. And if root is not achievable yet on your software version, be patient, even on Marshmallow devices are being rooted even with locked bootloaders.
I apologize for such a long wait time + post! I wish you good luck again! :good:
P.S. You should include your current software version in your OP (Android 6.0 - V20c-SEA) so people more knowledgeable than I may be able to help you even more.
Click to expand...
Click to collapse
Thank you thank you! You are awesome.
I will follow the links later and reply ...
I will ???? thank you
@mikmikush You're welcome, my pleasure!
Williquah said:
@mikmikush You're welcome, my pleasure!
Click to expand...
Click to collapse
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
its like my problem?
what did u do?
mikmikush said:
ok
i think i find the problem- the adb is not working
i followed to unlock bootloader of lg, { https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS }
and when do this step:
"Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window."
it says failed to start daemon - error cannot connect to daemon.....
and i cant trace lg id.
any sugestion?
Click to expand...
Click to collapse
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
CrazyLegenD said:
I have SEA device too, not being able to be unlocked via LG's official bootloader unlock tutorial
Click to expand...
Click to collapse
H815 SEA?/Same software version and error?
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
htr5 said:
Complete root guide for H815 EU http://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Williquah said:
Alright, so I guess it does have something to do with your adb. First off, check your Firewall, make sure you allow adb through and out your Firewall, also maybe temporarily disable your Antivirus whilst using adb, or allow a connection through it if you can. Try turning off USB Tethering through your G4. Try going to Task Manager and ending the adb process tree, it should then try to restart itself. Don't use a wireless adb connection.. if you were trying that, although I didn't think you were.
In "short" order,
1. I would firstly suggest allowing access through your firewall/antivirus, or really I would disable both for now just in case
2. Then try killing the adb process tree in Task Manager
3. Try the adb commands: "kill-server", "start-server"
4. Install any device driver you would possibly need
5. Reinstall adb and fastboot, maybe just install entire SDK-Tools package if you don't have it already
-- If adb is not recognizing your device, which is why you can't track your id, then you can simply enter "adb devices" and it will list your device whenever your error is fixed.
That's all I can think of ATM, I'll post this now but I'll still be thinking of other options. Let me know what happens. Fingers crossed.
(You are starting the command window in your adb directory right?)
---------- Post added at 07:39 AM ---------- Previous post was at 07:36 AM ----------
H815 SEA?/Same software version and error?
Click to expand...
Click to collapse
Williquah said:
We're working on H815 SEA though.
Edit: Your guide is for EU v20d, she's on v20c on the SEA, do they use the same exact software? Is there a pending update for her?
Click to expand...
Click to collapse
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
mikmikush said:
i stopped the firewall and tried killing the adb process tree in Task Manager
done "kill-server", "start-server"
Install any device driver you would possibly need- i think i installed everything but im not sure though
done - Reinstall adb and fastboot, maybe just install entire SDK-Tools package
when i try adb devices - daemon fail
im frustrated
Click to expand...
Click to collapse
Trust me, I understand your frustration, I'm going to make a guide for you in the next 6 hours or so.
Try a different computer if you can, I haven't had adb fail but many other tools sometimes work
on different computers for me. I've also heard "Dell PC Suite" should be uninstalled as it could cause adb hang ups,
if you have it. @htr5's guide might work for you if you have a software update available, I'm not sure though since it's not specifically for your device.
Regardless, I'm sure you will need to use adb soon, so we have to fix that.
I will try to make that guide asap, I obviously can only do so much, again, since I don't have your device, hopefully it will help though. I highly suggest trying on a fresh/different computer though.
Edit: Try USB 2.0 if you were using a 3.0 port (3.0 ports have the SS along with the usb "logo")
USB 2.0 is on the right:
"H815 SEA Root/General Guide"
@mikmikush
It does seem that you can treat your SEA device very similarly to the EU common version, in ways such as flashing KDZ's and rooting.
I cannot confirm this, but mentions in this thread: http://forum.xda-developers.com/g4/help/safe-root-h815-v10b-sea-variant-t3184152 make it seem like it should be okay.
Aoi_sora9x said:
I'm a SEA variant holder here.
It's fine, you can use the Low Effort Root method. You can also flash the EU open KDZ without any problem.
You lose VoLTE, but to me it doesn't matter so I don't really care.
I'm running the latest 10E ATM, and it's much much better than 10B, so flash away.
Click to expand...
Click to collapse
Yes, that post is for v10b, but it should also work for v20d/v20c. (Not the Low Effort Root method) - You will be working with EU software v20d.. while you are with SEA v20c,
so it's up to you if you want to try this, but it's the closest I can come right now. Thank @htr5 because I believe he has all of this in his guide, and I'll probably send you to his guide halfway through.
You may lose some features or brick your device by flashing firmware/software made for other devices. Trust your instinct!
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install adb setup from here this includes necessary adb drivers, adb itself, and fastboot.
2. Install LG Mobile Driver
3. Download LGUP tool from here (This is for restoring your device to stock if you softbrick via KDZ)
Follow this thread if/when you need to.
4. Here contains a KDZ for EU v20C, which I'm 99.9% sure will match your current software, even though it says for EU.
5. Here contains every partition including the KDZ for 20d by @autoprime, which will be necessary if you decide to root from @htr5's guide (v20d Root Method)
6. Once again, try to unlock the bootloader officially through LG, if you are successful, you can follow @htr5's 20d Root Guide here
7. Be careful and let me know how it goes
@autoprime Mentions that there is "NO anti-rollback qfuse used in this update" (20d) so if you flash the 20d KDZ and it works, I believe you should then be able to downgrade successfully to an earlier firmware version - without worrying about qfuse - and root using a Lollipop (5.0/5.1) method if you can't get anywhere on Marshmallow (6.0). - This I'm not 100% positive about, again, but it is my thinking.
Please thank anyone I mentioned and anyone who's link I provided, they all deserve it!