Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
obones said:
Hello all,
I'm trying to remove the bootsound for my Desire and so followed the instructions in thread 675580, page 3 (can't post direct URL because I'm a new user)
I replied there saying it does not work but after rereading carefully, I think it's because I tried the command while not being in recovery mode.
I then went around and read a few threads to figure out how to enter this mode. I thus followed the instructions in thread 6710092, reply number 4 in the part about "How to flash ROM".
I can get up to step 6 just fine. I even have the black screen with red triangle showing up. I then try the next step, that is running "recovery-windows.bat"
Unfortunately, adb-nilezon says it did not find any device and so errors out in the three steps inside the batch file.
The only option that I was able to find to get back the phone in a workable state was to remove the battery.
I noticed a behavior of the phone that is not mentioned in the above thread, so maybe I did not do something right.
In Step 5, right after I plug the desire to the PC, Windows says it has found a new device and complains it could not find the driver. I tried to have it search for drivers, but it could not find anything and thus aborted the install.
Along with this, in step 6, right after I press the power button to select Recovery, the phone seems to "reboot" as it shows the white HTC boot screen and it vibrates.
Is it possible that I am missing a part of the correct install?
I read all replies to the mentioned tutorial thread, some users have the same problem so I created a Gold card, which I believe I did right. But this did not change my situation.
When not in recovery mode, I'm able to use USB Debugging to connect to the phone and send my test applications via adb just fine.
Many thanks for your time and patience
Olivier
Click to expand...
Click to collapse
Not sure if you do or not but do you need to have Htc Sync installed for the drivers?
I do have HTC Sync installed
Are you rooted? You need root to do this. If you are then why not use fake flash or unrevoked to enter recovery.
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
obones said:
No I'm not, but the message in thread 675580 says there is no need for it, hence my tries here.
I'd rather not root my device if I don't have to, for the time being that is.
Click to expand...
Click to collapse
Recovery-windows.bat won't work unless you are rooted. The screen with the red triangle isn't actually recovery mode. The .bat file you would run pushes the recovery to the phone.
If you are not going to root, then you can get an app from the market that puts your phone on silent as you switch it off, and then back to normal when it's booted. This disables the boot sound. It's called silent boot I think.
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
obones said:
Well then, I'm missing something from the other thread (675580) as I can't get the command to work.
I'll wait over here for any comments.
Thanks
Click to expand...
Click to collapse
try fake flash? ive never used it so i duno if u need to be rooted
Fake flash needs root. No custom recovery will work without root. Quite simply, if you are not rooted you will not have write access to /system
please help.
i try to install froyo rom.
after flash FroYo_inkreDroid (14.07.2010) rom (throught standart flashrom procedures by update.zip) the device will not boot into os. i try update modem and after this the device win not booting to recovery mode.
i try press both combination (back key + power and volume down + power). the result of both combination is: 7 short vibro signals and black screen.
please help me, how me recovery my device.
thnx and sorry for my english.
your going to have to root it.
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Edit:
Rooting this device has been made possible by GT35pro. See posts below.
same problem
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
CWM installed and rooted the HDC galaxy note 2 MAGE / MEGA
rebmoe said:
omg i have the exact same problem, did you get a solution? PLEASE i need to root it so bad
Click to expand...
Click to collapse
I just created the cwm recovery and root. The link is on my blog. The zip file is password protected so be sure to get it from my blog page.
http://gt35pro-mobile-gadgets.blogspot.sg/2013/02/cmw-recovery-english-and-root-for-hdc.html
After you have clockwork mod recovery, use it to flash the root access into the phone.
Have fun!
KristN91 said:
Hi guys!
Just recently I bought the "HDC Galaxy Note 2" off of fastcardtech. I got it a few days ago, am fairly pleased with it except for the slight miscalibrated touch screen. There are some apps on various markets aiming to fix this by re-applying new calibrations. The problem is that you'll have to be rooted in order to run them.
The phone comes with a built-in calibration setting, called "Als_ps calibration", which you can utizile to correct the sensor. Alas, it only corrects the phone's recognition of obstacles placed above it, so that you accidentaly wouldn't press any undesired button during a call.
Phone: http://www.fastcardtech.com/Galaxy-Note-2-Mega
Here's what I've done so far!
Enabled USB-debugging and installed USB-drivers. [MT65xx_USB_Driver.zip]
Tried the bin4ry root method, normal mode. [Root_with_Restore_by_Bin4ry_v18.zip]
This method:
http://forum.xda-developers.com/showthread.php?t=1886460
Everything works just fine until the phone reboots. Bin4ry is then unable to mount or copy the last files needed to apply root permission, see attached picture.
I have attached my specs in a screenshot, nevermind the quality, t'was done by another crap-camera! Sorry ;]
Any kind soul who can help me root this thing?
Click to expand...
Click to collapse
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
londonflu said:
Kristen, where you able to re-calibrate after rooting; I just ordered this phone last week so I want to be prepared if need be.
Click to expand...
Click to collapse
The one I got did not have that screen calibration problem. Everything works good. Anyway, root is available now.
Superb!
Thank you for sorting this out!
-KristN91
Extra Guide
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
S_ft_need_download_all_fail (4050)
I'm trying for several days, but always get this error in the flash tool: S_FT_NEED_DOWNLOAD_ALL_FAIL (4050)
Tried on Windows 7 x64, Windows 7 x32 and Windows XP SP3 (x32). Only on the Windows XP computer I was able to make a backup with Flash Tool using the Read Back option.
When I try to flash the red bar goes to 100% then the error message shows...
Does anyone get this error aswell, and did someone manage to solve this?
Please help, I'm in desperate need for root because I need touch screen calibration.
Thnx!!
YES! SUCCES!! I managed to root my HDC Mage :laugh: Did use another method though, check http://forum.xda-developers.com/showthread.php?t=2160490 if you are interested.
Anyway, now back to calibrating the touchscreen. What tools are good do fix touchscreen issues? I already tried http://forum.xda-developers.com/showthread.php?t=934500, but I still am not satisfied.
Thnx :good:
Just curious, if anyone that owns an HDC, is actually located in the USA?
londonflu said:
Just curious, if anyone that owns an HDC, is actually located in the USA?
Click to expand...
Click to collapse
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Nope, the Netherlands. Why do you ask?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Because I tried to order 5 different phones from China including Fastcardtech; they couldn't ship for some reason; even got an empty box from ZOPO mobile. I ended up buying the BLU here in the US, I'm kind of glad it happened, since now I have an N'vidia Tegra 4 CPU, that runs circles around the dual-core phones.
I did order one more phone on ebay from China, been waiting for 2 weeks now. MAKES ME WONDER IF THEY EVEN ACTUALLY SHIP TO THE US AT ALL?
Thank to Paypal I was able to get refunded everytime.
KristN91 said:
Follow the link provided by GT35pro in his first post.
To everyone attempting this flash;
!! First of all, copy the Superuser.zip to the root of your internal phone memory or external SD Card.!!
* Use a high-quality mini-USB cable (The one that comes with your phone should work just fine)
* Connect your MEGA to your pc, without the battery inserted.
(This device will connect and disconnect, when it's visible, be sure to grab it and follow the next step)
* Make sure that you have the right drivers for MTK65xx preloader "mtk65xx Vcom driver" and install them through the Device Manager.
* Insert your battery again, with the cable still connected, and install the second MTK65xx preloader.
* Disconnect phone from pc and remove the battery
* Start up Smart flash Tool and select the scatter file included in the package.
* Now, select and tick the checkbox for Recovery only. Smart Flash Tool will complain about the flash, due to it not containing all the appropriate files needed for a "secure boot". Nevermind that pop-up and proceed with downloading.
* Start Download
* Insert the battery and connect your phone to your pc, with that, the flashing should start.
* Boot Phone into recovery mode (pwr button and vol - or vol +) and install superuser from ZIP-file.
* After reboot you should be rooted.
///////////////
Fun Fact!
I actually managed to install a pre-rooted HDC S7100 rom on my MEGA.
The port isn't 100% accurate
-Invalid IMEI, this was fixed by Talkingmobile's guide; " how to write imei number for MTK 65XX " -Just google it!
-Auto-rotation is unavailable, no fix yet.
-Als_pl calibration is unavailable (resulting in active screen during call)
Besides that, the rom is arguably better than the MEGA's original N7100 rom, in terms of visual presentation.
Smooth transitions, vivid and vibrant colors would be a good example of aspects that would come out as improved over the original rom.
Interested in the S7100 rom? Just PM me and I'll provide the link.
Cheers!
Click to expand...
Click to collapse
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
thank you
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
farazafs said:
I took out the battery then connect it to the pc and open device manager, it show mtk65xx preloader then the phone disconnect its self and connect back every two seconds is there a way to fix this pls
Click to expand...
Click to collapse
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
jg77 said:
Did you install all necessary drivers?
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 08:21 AM ---------- Previous post was at 08:17 AM ----------
Did you install all necessary drivers? How does sp flash tool respond when you download the recovery?
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
farazafs said:
I can Install all necessary drivers, when I Power OFF phone and connect it to my PC, in device manager it can show MT65xx Preloader (Com 9) connected n within 3 sec it can be disconnected.... in SP Flash Tool i can select recovery then press download button... then again i can connect phone, it's give me some 80xx error. it's mean that device not connect.
Click to expand...
Click to collapse
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
jg77 said:
An 80Xx error does not always mean device not connected. It can also mean there is something not right in the scatterfile (error 8038). You should take a look at the sp flash tool logfiles. You can post them here so I can have a look.
Click to expand...
Click to collapse
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
farazafs said:
Attached snapshot given below... always when I tried to flash Recovery from SP Flash Tool it's only give me this error.
Click to expand...
Click to collapse
There is something wrong in the layout of the scatterfile. Can you post the logiles of sp flash tool? Just zip them all together.
I have had the exactly the same error with my HDC Mage. I just had to rename a small section of the scatterfile and then it was all good.
Hi all I'm a noob so apologies if this is the wrong place but Im having serious issues unlocking the bootloader on my xperia play. I want to unlock it as I'm having issues connecting to the wifi. A search of the internet shows no help as my wifi doesn't even turn on whilst my searches seemed aimed towards those whos wifi was on but not connecting to visible routers. I've done a factory reset and re installed up to date software using sonys pc companion but had 0 Joy. I've tried various routers such as those at works and cafe but nothing.
After a while of searching for answers I decide to try unlocking the phone for custom firmware just to see if it work but Im either overlooking something or am just a failure. I visit the unlockbootloader.sonymobile.com/ webpage and start to follow the somewhat confusing 16 steps.
1. First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu. I follow the instruction no problem and move to step 2.
2. In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked. I do and the phone says it can be unlocked. I do and the phone says it can be unlocked.
3. On your computer, click Continue at the bottom of this page to start the unlock boot loader process.
4. Read through the information in the pop up window and click Yes, I’m sure, if you are still confident you want to unlock the boot loader.
5. Read through and accept the legal terms. Click I Accept.
6. Enter your name, a valid email adress and the first 14 digits of your phone’s IMEI or MEID number (remove the last digit if necessary). Click Submit. You can view the IMEI or MEID number by entering *#06# on your phone.
7. The unlock boot boot loader key will be sent to your email. Save it for later use. I follow ructions and now have the unlock key sat in my inbox.
8. Download and install the latest Android SDK from developer.android.com. I followed the link downloaded and installed the program leaving its folder on the desktop but the folder it came is called adt-bundle-windows-x86_64-20130219 not sure if that matters.
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager. I followed the link and unzipped a sing file called " android-winusb.inf" and leave it on the desktop for safe keeping. Google usb is installed as revision 7.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager. I take the file from my desktop and drag it to theadt-bundle-windows-x86_64-20130219 folder go to sdk > extras > google and finalyy went in to usb_driver folder and pasted android_winusb.inf-file, there I was prometed and chose to replace the orginal.
11. Turn of the phone. So I did.
12. On your phone, push and hold the Fastboot button at the same time as you connect the phone to the computer with a USB-cable. The Fastboot button may differ between different phone models. See the Fastboot buttons page for more information on what button use on your phone. From research I figured the fast boot button was the search button. I plug in the cable and the blue led shows on the top of the phone. The computer also makes an unusual connection noise (beeps 3x) but shows no pop ups asking what I wanted to do with connected device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file. [COLOR="Blue"]This is the point where Im BAFFLED. I have no clue what to do. At no point was I asked for drivers. Looking online Im not the only one to have been confused at this point but Im yet to find an answer that I understand to solver the problem. Its something to do with using device manager to solect s1 boot fastboot and install the driver manauly by searching for it on the pc but I cant for the life of me figure the full process out. [/COLOR]
Step 14, 15, and 16 seem self explanatory but if no one can help with step 13 I'm screwed. Any help would be appricated. I'll worry about the installation of custom firmware later, there are hundred of how instructions on how to do it so Im sure Ill have a bit more success if I can get that far. Ive been going at this all night so thanks in advance for any help.
I am writing this because I couldn't seem to find a guide to solve my issue of my Galaxy Nexus being completely bricked. It was literally dead, or so I thought. The first part of this guide will tell you how to recover from the following situation:
Before we begin, here are the names of the programs and files used:
Odin3
Android ADK
CF-Root-GGN_YAKJU_ICL53F-v5.1
Stock Galaxy Nexus ROM
OMAP
Situation 1:
The first situation is where your screen has gone completely black. You can't boot into anything and nothing is displayed on the screen. Your computer no longer recognises the device. It is literally a brick. If you are in this situation, please follow the solution 1 and 2 else skip to situation 2.
Solution to situation 1:
I was googling everywhere for a solution to this and it appeared that it was not a common problem and those who did face the problem simply returned their phone on warranty. It is now an old phone but I still like it (will be upgrading to nexus 5 in the next few weeks). I didn't want to waste such a good phone and just have it sit there so I researched.
My solution to this problem is omap. I would post a link but unfortunately I do not have the permissions (for the download link I will be uploading later).
Please note that I do not take any credit for any program used in this guide and I am simply putting together several other guides so that future users who have this problem can access them all in one place.
Here is the step by step guide:
1) Open OMAPFlash. Navigate to usb_drv_windows. *Right click on omap_winusb.inf and click install*.
2) Navigate to usb_drv_android. *Right click on android_winusb.inf and click install*.
*Note: On Windows 8 (8.1), you will have to allow all certificates to be installed.
3) Double click on the omap4460_tuna_hs_pro.bat and run it accordingly. You will have to disconnect the device and remove battery. Connect the device and then count to 5. Re-insert the battery.
4)Omap will now start doing its thing and you will be given situation 2.
Situation 2:
This situation is where you have a phone connected to a yellow exclamation mark which is connected to a computer. Mind my ASCII Art, but here is what it looks like: [] - - /_\ - - [ ]. You can't do anything with this either but ODIN (google it) will pick it up. This is a good thing. You won't be able to boot into recovery mode or download mode which makes it hard to flash a ROM to it or fastboot it. You will need CF-Root-GGN_YAKJU_ICL53F-v5.1 (Google it). Here is the step by step guide:
Solution To Situation 2
1) Open ODIN3. Select the CF-Root-GGN_YAKJU_ICL53F-v5.1 as the PDA file. If your phone is not being recognised (should say added! in the log), simply disconnect device, remove battery, reconnect device and then place battery back in and hold down the power + vol up + vol down buttons.
2) Press start. The log will start filling up and it should say DONE! You now have bootloader.
3) Now you will need to find the stock ROM for the galaxy nexus (google it). Now you will need to extract that the contents into your adb file (from the android sdk installation which hopefully you have,
4) Put your device into bootloader mode. Run the fastboot flash-all batch file that should be included with the custom ROM.
5) Your phone will now start doing stuff and constantly rebooting in and out of bootloader mode.
6) You should now have the stock ROM installed.
Again, I am sorry that I cannot post links but I do not have permissions due to lack of posts. I know this is an old phone but this guide may still be useful to someone. Also, feel free to ask any questions or point out any mistakes I have made.
no need that android adk. setup correctly adb & fastboot just enough. i think this type of threads already here..
* yeah.. but no sticky guide. maybe good to go. better make ' how to prevent gnex from bricks'
omap flash.exe ~
http://forum.xda-developers.com/galaxy-nexus/general/bricked-gnex-brought-to-life-t1760787
odin ~
http://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
I probably already know the answer to this but I want to make sure: can this procedure be applied to the Verizon Toro?
Update: Phone isn't responding to this fix... It was a long shot maybe in a week or two it'll turn on...
I'll write up a tutorial for us Toro kids... Thank you guys!
Sent from my VS980 4G using Tapatalk
The instructions to root the LG Optimus G Pro are posted in other threads and multiple pages on the web.
And I thank the folks who have done all the hard work to make that possible.
So tonight I finally got around to using those instructions and found that, as usual, a few key things were either left out or given in the wrong order, which inevitably is going to make some folks say "It doesn't work!" because, as written, it doesn't quit work.
So here's an edited version of the instructions from other folks, with the stumbling points cleared up and made into YnGlitch for dummies like me, so you'll get it right the first time. I hope. This worked on an AT&T branded phone, btw. Clarifications and comments in red.
1. (Optional if you have another means of un-RARing) Download and install 7-zip from here
2. Download and install LG USB Drivers from here.
(THE LINK IS http://www.lg-phones.org/lg-optimus-g-pro-usb-drivers.htmlWithout )
these drivers, your computer won't be able to effectively communicate with your phone. This is vital for the steps we will be taking.
3. Enable USB debugging by going to Settings->(General)->Developer options" and checking the box next to "USB debugging." You will get warnings. You can probably ignore them. This setting will allow you to run commands on your phone from your computer (via USB). For more info on the Android Debug Bridge, click here.
4. Download and extract (using 7-zip (or whatever)) the root exploit from here.
5. Connect your phone to the computer with your USB cable.
6. Put the phone into "Charge Only" mode at Settings->General->PC connection->USB connection type
7. Open CurrentRoot.bat and follow its prompts. See below. You will need to change from "Charge Only" to "Media sync (MTP)" mode. The setting is in the same place.[Change to Media Sync before running currentroot.bat]
Phone will reboot when this finishes running, wait it out.
8. Run SuperSU (now in your apps drawer) [that's the APPS folder on the phone, not APPS: DOWNLOAD folder] it and make sure it works. This program allows others to gain access to superuser privileges. For more info on rooting and what kind of stuff it lets you do, click here and/or use Google.
Thanks to XDA User carrett for this.
Thanks for your thread but you might wanna add the links for rooting(such as the link for currentroot.bat) . Also, just to check, does this work with KitKat?
Sent from my LG-E988 using XDA Free mobile app
yes, the links will be helpful