can someone help? i want to update tot he 4.0 but i need to relock my bootloader to have it work. i dont know how since im pretty noob at this
Provided u still have the folder u used to unlock, boot ur phone into fastboot (vol dn + power) connect it to ur pc with a USB cable, then from the command prompt in the folder where fastboot.exe is, type: "fastboot oem lock" without the quotations. Good luck!
Sent from my HTC Raider X710e using xda premium
ah damn i dont think istill have it
is there another way?
oh nvm i think i do i have it i just need to look for it
thank u so much haha im so happy right now
i have one more question when i did it it said this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so idk if it worked
i tired to update and it still didnt work
anyone have a copy of this fastboot.exe file..
i dont seem to have it anymore.. need to relock also so i can install the file.
---------- Post added at 01:55 AM ---------- Previous post was at 01:27 AM ----------
an4564 said:
i have one more question when i did it it said this
so idk if it worked
i tired to update and it still didnt work
Click to expand...
Click to collapse
Mine just did the same thing...
---------- Post added at 02:01 AM ---------- Previous post was at 01:55 AM ----------
OK, so i went back in to try again, came up saying its locked..
lets see how it go's.
i tired it a few times idk if its gonna work
mine comes up saying locked now, but when i go to install it powers down and then go's into the bootloader.. hmmm
i still havent seen the update yet
i tired it a bunch of times and nothing ever comes up
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
an4564, what device do you have, what network are you on, and what exactly are you attempting to achieve, what does "nothing ever comes up" mean to the rest of us who are not mind readers
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
i have the htc vivid for AT&T and am trying to get the ics update. i relocked my bootloader and typed in the *#*#682#*#* code and waited for the notification to come up but it never does. i have tired it multiple times
woodsytattooman said:
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
Click to expand...
Click to collapse
oh is this the update that was put out today?
an4564 said:
oh is this the update that was put out today?
Click to expand...
Click to collapse
No it is not. I don't know if there is a RUU for the newest ics.
davidcampbell said:
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
Click to expand...
Click to collapse
i am trying to update my Velocity with the OTA ICS update, i relocked the bootloader, restarted the phone, initiated the install, it gets to the point of restarting and instead of starting the install Fastboot comes up..
Related
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
plotgee said:
When I first turn on it'll stay stuck in HTC white screen logo till battery dies.
If I hold volume rocker and power button to try to factory reset it'll try to initiate but then show and a phone logo with red exclamation mark.
I am almost positive i can restore this phone to working order because i remember a while back i put a galaxy s3 into similar condition and restored it using a program.. Ive been out of this stuff for a while so i forgot how i did it with the s3.
I WAS GIVEN THIS HTC AND IT WAS LIKE THIS WHEN I GOT IT.
Click to expand...
Click to collapse
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
projectisaac said:
Don't worry, this problem has cropped up before, and you're right, it is fixable. This is most commonly attributed to some weirdness with the boot.img flashed to your phone. Firstly, do you have a Vivid, Velocity, or Raider? And what provider does it use (e.g. AT&T)?
The first thing you'll want to try and do is pop out the battery, put it back in, then hold "volume down" and "power" until you get to the bootloader (it sounds like you've already gotten there):
You'll notice in the top portion, mine says "unlocked". Yours may say this, but may also say "locked" or "re-locked".
First thing's first; you'll want to download FASTBOOT (http://www.mediafire.com/download/9ylow29klhccc0x/Fastboot.zip)
and the HTC drivers (this is what I had in my flashing folder, so I upped it to mega: https://mega.co.nz/#!CV5RxY7L!Z_VNph4KoGyYKJJjoUCGPAFZ7xZPOWRbvH2UKsCXCi0)
just run the htc drivers and follow directions, nothing too major. Extract the contents of "fastboot.zip" to somewhere that's easy to access and remember (such as c:\FASTBOOT).
We're not going to do anything yet, this is just preparation.
If your bootloader is "locked" or "re-locked", then you can try restoring the original firmware with RUU. You'll want to read this thread first though:
http://forum.xda-developers.com/showthread.php?t=1562890
Always need to be careful.
If you are "unlocked", then you need to boot your phone into the bootloader, select "fastboot" (by pressing power when "fastboot" is highlighted), and connect the phone to your computer via a data usb cable. Then, open a command prompt window, and type in: "<c:\FASTBOOT\fastboot.exe> oem lock", where <c:\FASTBOOT\fastboot.exe> is replaced with the location of your fastboot.exe.
I would recommend flashing the recovery image located in the thread I linked to just before (follow instructions provided), and only THEN applying an RUU update. Which RUU you apply is dependent on which device you have.
If anything is unclear, or you have any questions, PLEASE ask in reply to this post; it's better to go slowly and be sure of what you're doing.
sidenote:
I noticed you said you had previously owned an S3 and managed to fix the problem with that; if you are pretty familiar with flashing roms, you can also try to flash a custom ROM and see if that fixes your problem (guides should be on Vivid General or Q&A).
Click to expand...
Click to collapse
I have the vivid , and yes it says *** locked ***
I downloaded and installed everything you listed above and I am currently going through RUU process as I type this..
Thanks, I hope this works.
Fingers crossed here. Let me know what happens.
Sent from my Vivid 4G using xda app-developers app
Alright! So apparently this solution worked (got a PM from OP)!
I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://forum.xda-developers.com/showthread.php?t=2559715
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Return to stock
steveh_131 said:
I had a heck of a dilemma this past week.
I have the N900A that I rooted using Kingo Root. No safestrap or new roms, just rooted. I obviously had the 'Custom' icon.
At day 20, my phone wouldn't charge any more or be recognized by USB. I tried everything. Factory reset, cleaned the port, cleaned the cables, new cables. Nothing helped. And it would have to be warranty exchanged through AT&T, but the warranty was voided because of root. I couldn't use Kingo to unroot, because the PC wouldn't recognize it.
I was able to find a workaround, using this:
http://rootzwiki.com/topic/110386-return-to-stock-mj5-works/
In fact, I really only used the third step. I didn't download or flash the rom. By some miracle, the PC would connect to the phone when it was in download mode. I used Odin to flash those four files, rebooted, and the custom icon was gone.
I'm hoping that this has removed all trace of root from the phone. The knox counter is still at zero.
I thought I would post this in case anyone else had a similar problem.
Click to expand...
Click to collapse
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
asilva54 said:
its on here too
http://forum.xda-developers.com/showthread.php?t=2559715
Click to expand...
Click to collapse
Thank you, didn't see that when I searched last time.
ZOMBIExM4STER said:
Ok so, only doing step 3 returns the device to complete stock? I would do all the steps, but I don't really understand all of them.
Click to expand...
Click to collapse
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
steveh_131 said:
Thank you, didn't see that when I searched last time.
I believe the rest of the steps serve to load the MJ5 version ROM onto the device (in case you've installed a newer one or something). Since I already had the stock ROM, they proved unnecessary for me. I just used Odin to flash those 4 files and since the icon disappeared, I stopped there.
Click to expand...
Click to collapse
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
ZOMBIExM4STER said:
I'm on stock too, I want to do this because I'm having problems with the keyboard. The whole process is really confusing to me, do you think you can help me out?
Click to expand...
Click to collapse
I will try, but I am not an expert by any means. I tinker, but hopefully these other more experienced guys will chime in if I say something incorrect.
1. Download odin from here: http://www.firmware-files.com/download.php?id=1&token=QDXtLX5r3hLhxpTt604CYR6zP9twKSmr
2. Extract odin to a folder on your computer
3. Download these four files:
http://www.firmware-files.com/download.php?id=8&token=1QMc777QYjZgceInVMKs1HlcxAWv2wrU
http://www.firmware-files.com/download.php?id=7&token=6AfQkrv4S1mjr2oClQdwHp62lZpT8BK5
http://www.firmware-files.com/download.php?id=6&token=rXopUUlOTAGrBAQfksBLl1lKu52xIjl0
http://www.firmware-files.com/download.php?id=15&token=5CYaBqGOCoJSQMM6K7WECGlLDK4NYWTT
4. These four files will be zipped. You need to extract the zip files somewhere onto your computer. Each file should have a .tar.md5 extension once you extract them.
5. Power off your phone. Put it into download mode. To do this:
Power off your phone completely'
Hold down the home button, volume down button and power button all at the same time
When the screen comes on, let go of the buttons
It will give you a warning. Press the volume up button to proceed to download (odin) mode.
6. Run the Odin3 v3.09.exe application (that you extracted in step 2)
7. Now that odin is running and hopefully connected, you need to specify the four files that you extracted to be downloaded. You should end up with a screen that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8. Click start and let it run until it is finished. Once it is finished, hold down the power button to power off your phone then do the same to turn it back on. The custom icon should be gone.
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Rukbat said:
First thing I do after rooting is Wanam and turn off the Custom - just in case something like this happens. If the phone later blows up, factory reset if possible and walk it in for an exchange. Then if, when it blows up, even Odin can't see it, there's still no lock on the screen.
Click to expand...
Click to collapse
Doesn't factory reset delete the Xposed framework?
With AT&T you can't do a walk-in exchange after 14 days - pretty scary to mail it in for exchange and risk a $650 charge when they discover you rooted it.
I had the icon turned off with Wanam, but it came back.
steveh_131 said:
Doesn't factory reset delete the Xposed framework?
Click to expand...
Click to collapse
I could probably write an accounting program for an agency as large as the US government (or have fixed the health insurance site - doing something for half a century does pound some knowledge into even rock hard heads like mine), but when it comes to Android, I'm one of the learners, not one of the teachers. You know the answer to this question better than I do. I'd assume it does. I've made a lot of stupid assertions over the years, so ...
I downloaded a course that I may start reading one of these days, so I might yet learn enough to write a "Hello, World" app for Android. (Programmers know what I'm talking about - the difference between being able to develop a program and being able to code something to run in a particular environment - and the only internal environment I know in Android is where the battery and cards go.)
With AT&T you can't do a walk-in exchange after 14 days
Click to expand...
Click to collapse
SSSSSSHHHHHHHH!!!!!!! You weren't supposed to tell them that. I hope they didn't read this thread, and I hope the very nice lady who gave me the phone I'm using now doesn't get into trouble. (I'm not talking about walking in and saying "I don't like this phone, may I have a different one, please?" I'm talking about walking in during the warranty period and saying "could you please make my phone work?" and being told that they'll have to give you another phone. The only thing I'd trade my N3s for is N3s with unlocked bootloaders. I just want to see something other than comets revolving around Samsung's name.)
I had the icon turned off with Wanam, but it came back.
Click to expand...
Click to collapse
Mine stayed off - for the 3 or 4 days that the hardware didn't die on me. Then ... well, maybe Samsung has a way to read melted silicon, or whatever it did to make itself electrically invisible, but I'm not going to worry about it.
Wanam will keep the icon hidden but once you factory reset the phone I believe it deletes the xposed framework and the icon comes back.
I could be wrong about that, but that is my understanding.
I don't think you'd ever fool the warranty department that way, unfortunately, which is why I used this method.
Sent from my SAMSUNG-SM-N900A using Tapatalk 2
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
ryant100 said:
after doing just step 3 did you run a root check to see if that was gone? also what was the state of your phone after only doing step 3....meaning custom on dl mode and lock on boot screen....just wondering cause the files are so small to think that it would completely return to stock (like day 1)
Click to expand...
Click to collapse
No custom and no lock. I didn't run a root check, not even sure how.
The files are small because you're not flashing an entire ROM. My ROM was still stock.
Yah, so as the title says, ima show you how to root ur lg l90! The only reason im doin this is because @gdjindal's guide didn't work fer me. That runs v10e or higher WITHOUT DOWNGRADING. I'm not really sure if this works on previous firmwares, but let me know if it does :good:.
Firstly, the original tutorial is here: 1x1a.com/how-to-root-a-lg-optimus-l90-d415-10e.html
Code:
WARNING
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app
failed. Please view the original guide BEFORE looking at this
abridged version! YOU are choosing to make these
modifications, and if you point the finger at me
for messing up your device, I will laugh at you.
Download the files attached.
First things first: make sure you have USB debugging enabled (can be found in dev options in settings app) Install the drivers you downloaded.
Then, you should connect your phone to your PC/laptop (must be able to run batch files) in MTP (or your PTP equivalent) If prompted for USB debugging permissions on your phone, hit allow.
Now for the actual rooting.
Open the root script zip file, and extract it wherever you like. Extract the Drivers in this zip file and run the exe within. Then, open the folder and select the LG Root Script Batch file. Now just sit back and relax.
If you get a message saying that the serial port could NOT be found, then disconnect your phone and turn it off. Then WITHOUT TURNING IT ON, hold up the volume button and push in the USB cord. This should fix the problem. Once the process completes restart your phone manually.
Worked for me on a LG L90 D514 v10e . Thank you, as no other method would work.
I can confirm that this works as well, for D41510e firmware. Huge thanks, even though I jumped through all kinds of circles to get this device rooted lol(mainly due to the fact that none of my PC's run windows) Needless to say, I couldn't get the batch file to work via cmd prompt and WINE, so I had to do a fresh windows install. I'm going to try to write a shell script for any linux users out there that might run into the same problems as I did. If I have any success, I'll upload for the OP to include in original post. Thanks again!
Confirmed working on LG L90 D145 TMOBILE running official lollipop, with a tiny amount of editing to the batch file.
Nice !!!
CaptivateKing said:
I can confirm that this works as well, for D41510e firmware. Huge thanks, even though I jumped through all kinds of circles to get this device rooted lol(mainly due to the fact that none of my PC's run windows) Needless to say, I couldn't get the batch file to work via cmd prompt and WINE, so I had to do a fresh windows install. I'm going to try to write a shell script for any linux users out there that might run into the same problems as I did. If I have any success, I'll upload for the OP to include in original post. Thanks again!
Click to expand...
Click to collapse
Your very welcome on the guide. Never really superused linux before, got it on an old computer to make it run faster after xp got discontinued. Hope you can write the shell script and send me the modified files. The best of luck! :highfive:
silentpoke said:
Confirmed working on LG L90 D145 TMOBILE running official lollipop, with a tiny amount of editing to the batch file.
Nice !!!
Click to expand...
Click to collapse
Please sent me the edited batch file! Thanks in advance! :fingers-crossed:
Confirmed for D415 Lollipop
This method also worked to root the Lollipop update. Thank you. (I hate bloatware.) Anyone who is looking for a how and is already rooted with a custom recovery, just use Rashr or Flashify to flash the laf.img file again and use LG Flash Tool (2014 at least) to flash the D41520b_00.kdz to update to Lollipop, then use this method to root.
View attachment 3258647 View attachment 3258648
can someone help
can someone help me i did the script and im on lollipop i can acess supersu but i cant verify the root via root checker pro or use SCR pro. and my phone reboots to the tmobile logo
G33KSQUAD said:
Please sent me the edited batch file! Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
1 thing edited because it couldn't find my phone
I had to manually enter in what com port my phone was on, I used lg flash tools to determine, I edited the com ports while script was running and hit save, and boom phone rooted in like 30 sec.
I Don't have Developer Options !
Errrrr, uhh ... sorry. Ahem ... I meant to say I don't have 'Developer Options or a Debugging defeat switch in my D415's settings.
Thanking you in advance,
New Guy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CaseyRockStar said:
I Don't have Developer Options !
Errrrr, uhh ... sorry. Ahem ... I meant to say I don't have 'Developer Options or a Debugging defeat switch in my D415's settings.
Thanking you in advance,
New Guy
Click to expand...
Click to collapse
Just go to about phone, software info, then repeatedly click on build # 7 times. It should say, congrats, you're a dev now!. Then go back to the main settings page and open the dev options. Icon should be like {} symbols. Then enable usb debugging, and click yes if it asks for authorisation when run the batch!
Keep an eye on Windows driver updates
Thanks for this! Just a note to keep an eye on the Windows driver notification in the taskbar. A lot of the hangups were that you had to stop checking Windows Updates for Drivers. Once I clicked that, the downloaded drivers were installed quickly and the script moved along.
Works!
At first I started to get scared because i had to retry the manual download and it says 0% and the computer is trying to connect and for the longest time i thought i did something wrong but it seems to be working!
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
cliemonster said:
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
Click to expand...
Click to collapse
Does it not detect it when you disconnect the USB, put phone in DL mode, and reconnect to USB? Should automatically detect the com port when you do that
Sent from my LG-D415 using XDA Free mobile app
cliemonster said:
I keep getting stuck at the Download screen. It doesn't ever seem to detect a com port. I guess I'll keep trying to see if something magically starts working lol
Click to expand...
Click to collapse
You may have to manually select your com port. Typically it's COM 41, sometimes 23, though.
xanscorp said:
You may have to manually select your com port. Typically it's COM 41, sometimes 23, though.
Click to expand...
Click to collapse
Thanks for the advice. I'll give that a try!
Nope... it just does not want to recognize it. As soon as I put it into download mode my computer just refuses to see it. I tried putting those com ports in manually and nothing. Maybe its a cable problem. I'll see if anything changes with a different cable.
Figured it out... it was the drivers. I thought I had the right set, but when I installed the drivers again from this post, all worked like a charm. I am now happily rooted, and thanks for all the good advice.
Successfully rooted today. It didn't detect the port automatically for me either, but following the instructions to hold volume up during boot got it there. I posted screen shots of the script and my phone. I thought the script failed because you can see where it says Special command ##, it was stuck there for several minutes and my phone showed no progress but it showed rooted in red letters. This might have been because I ran this script at a different time thinking it failed (originally from this guide http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951), but I forgot to run the supersu app once the phone rebooted.
Quick question. I ran it and it was fine up until it looked for a COM port. I manually put it in download mode, and it told me it was missing MSVCR100.dll
I downloaded it, I used one in Sys32, and I get an error when Send_Command.exe gets executed. Any help would be appreciated. This is a clean install of Win7 and I only used the attached drivers.
This work on lg g4?
first off this is just a quik refrence guide to do it seems to be loads of confussion on how.
the guide is my work nothing else so later on ill post links to all the pages with all the download links so you can thank all respective rom makers and people that created the files and such.
Disclaimer i am on zv6 rooted so i have not tested myself. just put the guide together as one would flash anything to our love to hate g4s.
if issues with rom i dont have a clue again as i am not on zvb. goto rom thread.
so lets get started
first you need to download this this is the zvb .tot
your firmware just incase things go bad.
http://rwilco12.com/downloads.php?dir=Files/Devices/LG G4 (LS991)/Stock ROMs/ZVB
im assumming you already have lgup or i personally use the old lg flash tool its all personal prefrance this is just for restoring orig firmware incase of bad things.
also download this this is the zvb global rom for sprint g4.
https://cloud.spryservers.net/index.php/s/Vos5F0J9iL3ouxj
also download this this is the send commands and ports.bat for command prompts to know what to do.
http://downloads.codefi.re/thecubed/lg_g4/lef/LG_Root.zip
so first on phone enable usb debugging in dev options
i have many firmwares and so ive put all my lg stuff in a lg file ofcoarse for easy accsess.
so unzip the lg root zip to a easy known folder and spot on pc.
after degug open file where lg root is and in a bare spot in folder dont hover over n e file hold shift and left click youll see open command promt here.
click it.
once prompts open type abd devices you should get the dialouge on phone about always accepting this computer or whatever it is click accept.
type adb devices again to make sure pc sees it as adb device and not offline.
once it sees adb device unzip mellowmallow rom .img and put on root directory of internal sd card same root as all the folders like ringtones downloads music and such.
so theres the first steps.
so reboot ure phone into dl mode turn off hold vol up and plug into pc
back in command prompt type
ports.bat this is to see what com number ure device is u want the number with the one that has diag in it not modem
so then type
Send_Command.exe \\.\COM after com type the port that is ure diag in my case currently mine is 14 so for example it would be Send_Command.exe \\.\COM14
as i said the number will change depending on ure pc.
im not running my promt so i dont know exactly what it will say but u will see ure command promt change.
now ure ready and be sure this is correctly entered i just copy and paste for safety then no mistypes.
this is the dd comand to install rom in download mode.
dd if=/data/media/0/MellowMallow_LS991ZVB_v1.01_Global.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
wait about 5 min or so youll see a little pound sign when u do its done some people say to type leave and the phone will reboot but it dosnt work for me have the time so i just unplug and pop the battery. reboot and in theory you should be good to go.
now remember im on zv6 and i am rooted so i have not tested said rom and will not not losing root over testing.
if ne more info is needed just let me know.
OK downloaded drivers,on one place of phone saying ls996zvb the other is saying v10a what do I go with
Sent from my LGLS996 using Tapatalk
Woody Herald said:
OK downloaded drivers,on one place of phone saying ls996zvb the other is saying v10a what do I go with
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
Zvb
Woody Herald said:
OK downloaded drivers,on one place of phone saying ls996zvb the other is saying v10a what do I go with
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
Be sure to follow the instructs in the mellow mallow thread perfecty or u can tbrick ure device
hes got a flashing guide
i didnt know that the sendcommand didnt work on zvb there is a special procedure to follow to open it up
Ok update i didn't have enough data to do The work you sugested sorry sir but I got data on my phone no root and a lot of stress here are a few pic to prove it.along with help from some patient people we took this one to the ropes
Thanks a lot "Mad scientist" for the time you have taken with me" BIG HAND SHAKE" also to a lol friend called QSM Here R Those pics
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..... Now to the Hard part Any one want to hold my coat tails while I jump off and try to root my baby here lol. Need the HAND!![emoji12]
TheMadScientist420 said:
Be sure to follow the instructs in the mellow mallow thread perfecty or u can tbrick ure device
hes got a flashing guide
i didnt know that the sendcommand didnt work on zvb there is a special procedure to follow to open it up
Click to expand...
Click to collapse
Sent from my LGLS996 using Tapatalk
Woody Herald said:
Ok update i didn't have enough data to do The work you sugested sorry sir but I got data on my phone no root and a lot of stress here are a few pic to prove it.along with help from some patient people we took this one to the ropes
Thanks a lot "Mad scientist" for the time you have taken with me" BIG HAND SHAKE" also to a lol friend called QSM Here R Those pics
..... Now to the Hard part Any one want to hold my coat tails while I jump off and try to root my baby here lol. Need the HAND!![emoji12]
Sent from my LGLS996 using Tapatalk
Click to expand...
Click to collapse
Im hoping a root method does come out. New stuff everyday.
In time a exploit should and could be found. Ive been looking at the new method on the sprint g5.
Again no twrp but anythings better than nothing
I have a android emulator on my pc that i try to get to mimic the g4. To test stuff but it only goes so far.
I know I shouldn't be exploring with my flex but I had no choice
Sent from my LGLS996 using Tapatalk
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Once again you the MAN!
Sent from my LGLS996 using Tapatalk
To start this journal I will begin by stating, I am not actually sure if it will be possible to finish this journal; from what I have read there can be quite a number of obstacles with international versions of the OPPO, some of which can be quite troublesome, but I thought it would be an interesting and hopefully helpful (for my self and anyone else wanting to do the same) way of going through the process with such a modern device.
The device arrives tomorrow, I wanted to get the initial post in without knowing precise details about the device.
I will update this primary post with the journal entries and post into the main thread when I update it going forwards
-- Entry 1 29/01/2022 00:21 (Dellivery today at some point!)
So far I have found out that cpw means car phone warehouse, which used(still is?) a store in the uk, 'EE' a network provider in the UK releases of the Oppo x3 find pro are apparently identical to releases from this store.
I have asked the user who informed me of this if they could possible put any information they are aware of within this thread.
Also, I will be doing the unboxing and initial looking at what it is via youtube I hope this is ok? I could not see a way to embed video onto this platform!
-- Entry 2 29/01/2022 10:53 (Delivery)
This is just a few images of the arrived device, simply unboxed and put on charge nothing has been set on the device what so ever.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also note that this image showing the build number is by @alvydas it is not from my device yet! just some more information to add to the journal, this is believed to be the same as mine should show later on when I decide to video/start the phone up
Also for note the CPH (Possible related to CarPhoneWarehouse) prefix in the build number)
-- Entry 3 29/01/2022 13:11 (Turning on, Bootloader unlock, USB Debugging enabled)
Youtube video:
- May still be processing the HD version in google HQ!
-- Entry 4 30/01/2022 10:53 (Getting sorted)
Ok so we can't root it and we can't change the boot laoder .... however we can get novo launcher to start by default! The pro version at least!
Not exactly an amazing feat but hey its progress, I also removed the gmail mail application as I preffer outlook (mainly because I have 3 email accounts):
And boy .... you can really remove everything including:
130|OP4F57L1:/ $ pm uninstall --user 0 com.oppo.launcher
The coloros launcher its self X_X, so it seems you cannot get root, but there is no protected package, you can remove ANYTHING.
so this bodes the question .... other than wanting lineage OS of course, how thin can we get it ....
-- Entry 3 10/02/2022 10:53 (Hackery and cleaning)
.... So there is no fastboot on the international model, it is simply not there I even got EE them self to confirm this.
However, I have made some progress in discovering a way to get to the qualcomm flashable download mode, that is it will show up as a:
One of those (if you have the Qualcomm drivers installed), some information I put in the forum about this mode was this:
1) Turn the phone off (shutdown)
2) Hold the power button and the Vol up/down (I Forget which) down all the way through the phone starting, you will feel a little Bzzzzz
3) you will be presented with a menu probably in chinese, this is because you held down the power button and it auto selected the first language (its not a biggie), just press the back touch screen button in the top left <--
4) Select english (or chinese if you preffer!)
5) you will be presented with a menu that has 3 options, Format, Reboot, .... something else ...
6) Select none of the options! look to the bottom of the screen you will see a version mine was v12 o3 v1.2 - double tap this
7) you will get a warning you are entering 'customer service mode', and wallah .... you will get the device show up in device manager.
I was going to shoot a video of this, I still might! but its rather redundant at this point as I am now at a brick wall, I need to figure out how to deal with this mode, can I flash something to it .... how?
I am scrubbing the phone of all the bloatware I can and to be honest I have it pretty damn clean .... but still the fastmode is elusive and what else could be loaded onto this lovely phone.
Entry 1 added - nothing really important
Entry 2 added, initial unboxing simply for charging, video to come soon: looking for details!
The CPW in the build number is more of a guess than anything else we all could be wrong
alvydasd2 said:
The CPW in the build number is more of a guess than anything else we all could be wrong
Click to expand...
Click to collapse
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
PaulGWebster said:
@alvydasd2 Soon see! I hope you do not mind but I included your image in the journal at the top.
Click to expand...
Click to collapse
Yh that's fine
Entry 3 uploaded, many thanks @alvydasd2 We do have slightly different builds it seems!
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Also have to figure out if all the fancy camera things will work with a custom rom, such as the microscope mode and all the advanced functionalities
Maybe the best initial tangent is to simply root the phone and remove any bloatware as well as installing novolauncher, followed by re-rooting it
That way I will not lose the ability to use the special camera functions and in turn still receive updates, I believe I can actually freeze certain packages too so they are effectively immutable, so they show up but can never run or be changed ... hmmm
PaulGWebster said:
So now next up I believe its rooting the phone should be fun, also I beleive there is a way to root a phone but hide it from applications like paypal ... would love to find more out on this
Click to expand...
Click to collapse
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
alvydasd2 said:
Rooting ain't gonna be easy on this phone that's if you can unlock the bootloader which is pretty much impossible unless you have a Chinese variant of the phone or somehow figure out a way to root it without unlocking the bootloader would be a miracle
Click to expand...
Click to collapse
Check the youtube video, I appear to have lol ... though I did notice that going into the recovery menu is all in chinese ... so I assume its the chinese version:
The only problem being ... I have no idea idea what this menu says -_-
I guess that is tomorrows episode though, connecting it via ADB+TWRP
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
alvydasd2 said:
Usually first thing when you open recovery is choosing a language idk why English wasn't there and btw the difference between the builds is you're running lower firmware so if you try to update it you should get the same build number as me and if u had the Chinese version your model would have been PEEM00 or something like that
Click to expand...
Click to collapse
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
PaulGWebster said:
ah ha I held the button down to long it auto selected chinese somehow I pressed back and got the recovery options ... not seeing TWRP though ... and when I do a TWP fastboot it does not boot into the bootloader...
The OEM Bootloader though is saying its unlocked in dev options
Click to expand...
Click to collapse
Oppo has a weird bootloader cuz it can only be unlocked with an app that only works on Chinese version and to access fastboot u need a unlocked bootloader
just read this .... so there is no way to even fastboot the device https://forum.xda-developers.com/t/...access-for-oppo-phones-starting-2016.3348114/
I wonder if you could flash on the chinese version of the firmware
it seems that the device is really a 'realme gt 5g' .... trying to verify this
PaulGWebster said:
it seems that the device is really a 'realme gt 5g' .... trying to verify this
Click to expand...
Click to collapse
It's not -_-