Hello All!
I decided to install CM 11 a few days ago and then thought I'd like to go back to Fire OS. I followed the instructions as much as I could from the thread on here to revert back but I have ran into a problem. I could only get 4.6.1 installed but obviously, 4.6.3 is out and my phone can see it's there to download (and it does (try to) download - every time I restart my phone). When the download finishes the phone says there is an error and it can't update but then I can search for the update and so on. I have tried doing it the way Amazon suggest from my PC but to no avail.
I can only assume that this has something to do with the fact I went from 4.6.3 to CM 11 and then back to 4.6.1 and the phones still sees itself has partially being on 4.6.3?
Any help is much appreciated!
Thanks
doing it the way Amazon suggest from my PC but to no avail
Click to expand...
Click to collapse
That means you downloaded the 4.6.3 BIN image and tried sideloading it via ADB?
If not, take a look at this (scroll down to the paragraph "Recovery / Sideload Factory Images")
I think OTA update is useless at this point but using the Amazon stock recovery is very reliable, I used it many times in the beginning for testing purposes.
Just give us some details when you encounter problems, e.g. driver missing when connected to PC, etc. ... and don't forget your backup for important apps & app settings.
I tried doing this before and the CMD does not show as any devices being connected. I have it in debugging mode and plugged it in but Windows did not see it even though the phone shows as being connected. Also, just in case I tried using the command you send and it just says "* cannot read 'update.bin' *".
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
{
"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"
}
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
It seems that on Windows 10 it works/looks different. I updated the driver that was suggested but I had another one which also needed updating which I have just done and appears to now let the cmd see the device properly and also allowing me to sideload.
Device manager does not see it as an Android device but as a Samsung device. Not sure why this is unless the device drivers used were Samsung ones but I guess that is irrelevant now. I will post my results once the update has finished.
Also, thanks for the help with this. Your information did help and with a bit of tweaking, it appears to have worked.
Thanks for mentioning so early that you use Windows 10, that makes it so much easier for me. :laugh:
Nah, but it looks like you will be good from here on out...
Btw. by sideloading the image, it will erase "everything" on your device, so you get clean system without leftovers, just like you hoped for.
Can you add the link for the thread you used to revert back from CM11 to FireOS?
paulalva05 said:
Can you add the link for the thread you used to revert back from CM11 to FireOS?
Click to expand...
Click to collapse
The link is actually in the first reply but I have put it below anyway!
http://forum.xda-developers.com/showpost.php?p=61271723&postcount=2
Bingo Bronson said:
You have the phone connected while booted up in Fire OS OR booted up in recovery mode like the guide suggests?
Sounds like you're missing ADB drivers / Windows failed to change the drivers when phone is connected in ADB recovery mode. Indicators:
• Windows did not "see" the phone
• The command line in CMD doesn't work without proper ADB configuration
If you boot up your phone in recovery mode / ADB mode, you will need additional ADB device drivers for your Windows system.
The regular (Amazon / Kindle) USB driver that is used when you connect your phone to the PC won't work, it's simply not the same method.
That's why your phone "disappears" as soon as you (re)boot into recovery / ADB sideload mode.
Open your "device manager" (assuming, you're using Windows as your main OS) and check for your device with missing drivers.
Try this tool (& driver) ADB, Fastboot and Drivers
Maybe you need to manually check for the "new" device and update the drivers:
Open the device manager while your phone is connected in recovery mode.
Look for its entry in the device list.
Remove it (Deinstall it).
Then "scan for hardware changes":
The device should appear in list the again, it will install the needed driver automatically (best case scenario)
or
you will have to update the device drivers manually:
You can even use (old) "Google USB drivers", I successfully tested google drivers from 2010 on Win 7 x64 with this phone in ADB mode.
If everything worked as planned, it should look like this: next to your device name, it will say "sideload":
Click to expand...
Click to collapse
Hi, thank you for the detailed instruction. My pc can recognize and show the name of my firephone, just like what you showed in the image. But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
iHuyou said:
But when I type "adb sideload update.bin", it still says "cannot read update.bin" What can I do now? Thank you so much.
Click to expand...
Click to collapse
Validate the MD5 checksum, maybe your downloaded image is corrupted...
Is the update.bin file in a different directory?
Bingo Bronson said:
Validate the MD5 checksum maybe your downloaded image is corrupted...
Click to expand...
Click to collapse
Hi, Bingo Bronson, thank you for your reply. What I downloaded from the link in your original post is a WinRAR ZIP archive. When I open it, there are multiple file and folders in there. There is a file called boot.img, should I change its name to update.bin and sideload it? But it is only 8Mb. Can you give a little more detailed instruction? Thanks
iHuyou said:
[...] is a WinRAR ZIP archive. But it is only 8Mb. Can you give a little more detailed instruction? Thanks
Click to expand...
Click to collapse
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
edit: Slight misunderstanding, luckily iHuyou found the solution by himself. :victory:
This is the direct download link from Amazon for the latest GSM unlocked version: http://fire-phone-updates.s3.amazon...update-fire-phone-35.4.6.3_user_463001620.bin
An here is the direct download link from Amazon for the latest AT&T version: http://fire-phone-updates.s3.amazon...HC5/update-kindle-32.4.6.5_user_465000520.bin
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Bingo Bronson said:
Whoops, I think you took a wrong turn there somewhere, too many files, what to choose...!?!
I don't know which version you had installed, so just pick the link according to your initial Fire OS version. Reply again if you have further questions. :good:
Click to expand...
Click to collapse
Thanks again, Bingo Bronson. I figured it out. The bin file has to be in the same directory as the adb file, otherwise adb cannot find the bin file therefore cannot read it. I have successfully sideloaded 4.6.5 following your post. Thank you!
Blank Screen amazon fire phone
Hello Guys i need help with my amazon fire phone, I tried to revert back from cm11 to stock rom (http://www.android.gs/downgrade-amazon-fire-phone-to-stock-fire-os-3-5/) using this site's method i got error sideloading from stock recovery then i tried it from safe strap recovery and it went successful but before sideloading update.bin from safestrap recovey i wiped and i did not know what options i selected but now my fone wont boot only black screen and when i connect it to pc it shows 3,4 partitions and says format, format... what went wrong ?
Related
Please do not hot link to my download. Link to the post and please don't use my work without asking.
Version 0.6.5 is available at the website.
- Updated the Recovery to TWRP 2.2.2.1 for the Kindle Fire
Version 0.6.4 changes
- Changed Kindle Fire recovery to TWRP.
- Updated Kindle Fire bootloader to FireFireFire 1.4a
- Added Kindle Fire recovery and bootloader updater for user who just want to update to the latest versions.
BreakDroid is a work in progress. My goal is to make a tool for Mac users that will root several different android phones and tablets as well as install the android sdk (adb).
It is very important to note that I only made the tools to automate these processes. All the developers of the root exploits and recoveries are listed below.
Current supported Devices-
Kindle Fire - Tested Version 6.2.2., 6.3 & 6.3.1
Galaxy Nexus - Seems to work. Tested with version 0.4.2+
Galaxy Note - Needs more testers - Will only work on some notes.
Droid Razr - Should also work on other Droid branded phones
All phones that can be rooted by GingerBreak
All phones that can be rooted by psneuter
All phones that can be rooted by zergRush - has been tested and works on many devices. vCheck the comments on the download page.
The Website
Screenshot
{
"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"
}
Credits -
This app and all the scripts were made by @northmendo
jcase was great support for questions and he is the reason we have root on the Kindle Fire thanks to burritoroot.
-Doomlord on xda built the Kindle Fire recovery.
Dan Rosenberg for the motofail exploit - @djrbliss
Revolutionary Team for zergRush http://revolutionary.io/
I think credit for psneuter goes to scotty2
c-skills for GingerBreak
Pokey9000 for fbmode - used to root Kindle Fire 6.3
Bootloader Credits go to
- Pokey9000: For the original build. Hard to dev at all w/o a way of getting to recovery.
- eldarerathis: Menu code was used from the Extended FIREFIREFIRE github
- Icemank121: All splash/menu screens
- Hashcode: For this build
There is a list of devices that can be rooted by zergRush in the ReadMe
If this helped you please hit the thanks button
I downloaded the android SDK app, extracted it, renamed it to android-sdk, ran the first script to run the SDK. I assumed it worked but not sure. Then ran the usb script, but got this error: http://i.imgur.com/NGl04.png
Also, when I go to terminal and enter "adb", I get "-bash: adb: command not found".
What am I doing wrong?
*Edit!!*
Got it working. Needed to fully install the ADK (follow instructions and install the tools relevant to your device. Mine was the 2.3.3).
THe commands need to be ran as ./adb whatever (instead of just adb whatver)
Plug in your device and type adb reboot and see if your device reboots?
If not something is wrong. Go to the Android sdk folder open it and reply with a list of what's there. Also make sure that the Android sdk folder is in your home folder.
Sent from my kindle fire using xda premium
northmendo said:
Plug in your device and type adb reboot and see if your device reboots?
If not something is wrong. Go to the Android sdk folder open it and reply with a list of what's there. Also make sure that the Android sdk folder is in your home folder.
Sent from my kindle fire using xda premium
Click to expand...
Click to collapse
The issue was that the Android SDK has moved adb. It's now in the platform-tools directory instead of just "tools". I recommend updating your script to reflect that.
FlyRyan said:
The issue was that the Android SDK has moved adb. It's now in the platform-tools directory instead of just "tools". I recommend updating your script to reflect that.
Click to expand...
Click to collapse
I fixed it. Thanks. I guess I was tired and uploaded the old version of my script.
i searched home folder but couldnt find it on my mac
squishy5 said:
i searched home folder but couldnt find it on my mac
Click to expand...
Click to collapse
Your home folder is the one with your name. The path is
/Users/whateverUnamedIT
Over in the Kindle Fire Utility thread, I posted a Mac version:
http://forum.xda-developers.com/showthread.php?p=21369040#post21369040
Should take care of everything automatically.
Glad some one finally did a write up for mac took me days to root on mine good work.
eratosthene said:
Over in the Kindle Fire Utility thread, I posted a Mac version:
http://forum.xda-developers.com/showthread.php?p=21369040#post21369040
Should take care of everything automatically.
Click to expand...
Click to collapse
Awesome. I will check that out for sure.
I did this and was cool. Then I found KFU for Mac and figured I'd get it working just in case. But now I can't get the adb root command to work. Says it's not available in production builds (or something like that). I would post in the KFU thread, but I figured there would be more mac knowledge here. Any ideas? Tried running burrito root again, but no help. Obviously it was working right for a while cuz I've rooted this thing twice. Why won't it work now?
Shermanballz said:
I did this and was cool. Then I found KFU for Mac and figured I'd get it working just in case. But now I can't get the adb root command to work. Says it's not available in production builds (or something like that). I would post in the KFU thread, but I figured there would be more mac knowledge here. Any ideas? Tried running burrito root again, but no help. Obviously it was working right for a while cuz I've rooted this thing twice. Why won't it work now?
Click to expand...
Click to collapse
I have a couple question in order to help.
What version is your Kindle running?
Why have you had to root so many times?
Running 6.2.2 I had rooted it on 6.2.1 and then it updated itself to 6.2.2 and I had to do it again.
OP, if you want you can add this to the post for installing twrp.
http://forum.xda-developers.com/showthread.php?t=1411299
Shermanballz said:
Running 6.2.2 I had rooted it on 6.2.1 and then it updated itself to 6.2.2 and I had to do it again.
Click to expand...
Click to collapse
Ok. I hadn't update for 6.2.2 It should be up to date now. Give it a try and let me know.
adbirdie said:
OP, if you want you can add this to the post for installing twrp.
http://forum.xda-developers.com/showthread.php?t=1411299
Click to expand...
Click to collapse
I'll check it out. Thanks.
Help
I did the Adb install. but i keep getting the "device not found" error every time i try to run any commands. any hehlp?
Did you update the android sdk when the update tool popped up? If not you can re-run the too. Download the version here. If that is not the case download and run this. Then reboot the computer.
Deleted....
Problem installing TWRP via Kindle Fire Utility (for Mac)
Ignore - Switching to recovery did work (just seemed like it wasn't)
I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"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"
}
I desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version
You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.
sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse
merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.
DISCLAIMER: Not my work, Tutorial followed from : http://choimobile.vn/threads/unbrick-lg-lu6200-ghim-cap-qhsusb-khong-thao-may.8448.html
Hi
I have been using LU6200 from last one year, and I loved this phone. I have tested many roms, and was using 4.4.2 CM11 rom. Then I installed an app from Play store, which modified the kernel, and booted my phone.
At this stage, my phone was totally dead, no screen indication, no light, no sound. Only one thing, is that when I connect my USB cable to computer, my computer try to install driver and also make sound of USB connection and disconnection.
So below are he steps which I have performed
MUST: KEEP YOUR PHONE ATTACHED WITH USB CABLE TO PC
Download the following files
http://pan.baidu.com/share/link?shareid=547069&uk=3071575749 <-USB DRIVER
http://pan.baidu.com/share/link?shareid=547084&uk=3071575749 <-Softwares
http://www.mediafire.com/download/ed4zec8itgjh37t/unbricklu6200.rar
Winhex - Forensic or Specialist version full not evaluation and registered. I have found only one version [WinHex 17.SR1.rar] which worked for me, not remember where from I downloaded this
Follow this tutorial http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ to run your OS in Advance mood where we have to disable DRIVER SIGNATURE ENFORCEMENT
When you have booted into windows after disabling driver signature, install the 1st Link file,
Install the Driver, when Installed it will show a COM Port installed, QUALCOMM one
Install the Softwares, default path will be C:\Program Files (x86)\Qualcomm\QPST\bin\
You also have items in your start menu, so run
1, In the "Start Menu" -> "QPST" -> "QPST Configuration" RUN This
2, Select the tab "PORT" and click "Add New Port ..."
3. A new window will open where the COM port which is newlly added to your system will be listed, select that port and add that
{
"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"
}
Keep that running
4 Go to the "Start Menu" -> "QPST" -> eMMC Software Downloadapp " RUN THIS
4.1 Uncheck, Program MMC Device
4.2 Click Browse, it displayed me PHONE ATTACHED with QUALCOM details near the top right of the image, where No ports Active is written
4.3 Check Search Path 2 and Browse to you files, where you have downloaded 3rd file. Which contains one hex, one img and mbn file
4.4 In the Flash Programming File name, enter the name of hex file
4.5 in boot image, enter the mbn file name
4.6 Click DOWNLOAD
at this point, it mounted me a 200kb drive which was not formatted. I have formatted that, and then kept this program running in the background as well
5. Winhex
5.1 Run Winhex, Make sure you have forensic version, and also Full version ,there are evolution version too, but that will not work. FULL VERSION and FORENSIC/SPECIALIST License is must
5.2 In Winhex, go to "File", "Restore Image", Change the file type from "WHX" to "Raw Image container"
5.5 Select lu6200.img from the 3rd file downloaded
5.5 Now it will ask for Target disc
5.6 Carefully select the QUALCOM, or else you will be formating your own HDD
5.7 In this window click OK
Now it will start giving your some strange, nasty warnings, just keep pressing OK, and Yes Continue Ok, etc etc
When that will finish, you phone will auto restart.
Now you may have to reflash that, or wipe it and install the KDZ ICS engineer version again. As right now My phone is in boot loop but I guess that can be fixed.
Tutorial followed from : http://choimobile.vn/threads/unbrick-lg-lu6200-ghim-cap-qhsusb-khong-thao-may.8448.html
我大中华威武啊，哈哈
qqzwc said:
我大中华威武啊，哈哈
Click to expand...
Click to collapse
我是威武大中国区第二部分哈哈哈
help me please
after step one i got 0 byte partition and when i connect the phone by usb it says unknown device and i cant do anything to it
baidu links are not working!. Can this tutorial also be used for SU640 or the .img file is only for LU6200?
not working they stock only on emmc software download, no pocket recieve and while running that i try winhex judt like the tutorial said but i dont detect any usb mmc to use for.
please provide your own screen shot that we can follow yiur step. thanks anyways
aamirrajpoot said:
DISCLAIMER: Not my work, Tutorial followed from : http://choimobile.vn/threads/unbrick-lg-lu6200-ghim-cap-qhsusb-khong-thao-may.8448.html
Hi
I have been using LU6200 from last one year, and I loved this phone. I have tested many roms, and was using 4.4.2 CM11 rom. Then I installed an app from Play store, which modified the kernel, and booted my phone.
At this stage, my phone was totally dead, no screen indication, no light, no sound. Only one thing, is that when I connect my USB cable to computer, my computer try to install driver and also make sound of USB connection and disconnection.
So below are he steps which I have performed
MUST: KEEP YOUR PHONE ATTACHED WITH USB CABLE TO PC
Download the following files
http://pan.baidu.com/share/link?shareid=547069&uk=3071575749 <-USB DRIVER
http://pan.baidu.com/share/link?shareid=547084&uk=3071575749 <-Softwares
http://www.mediafire.com/download/ed4zec8itgjh37t/unbricklu6200.rar
Winhex - Forensic or Specialist version full not evaluation and registered. I have found only one version [WinHex 17.SR1.rar] which worked for me, not remember where from I downloaded this
Follow this tutorial http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/ to run your OS in Advance mood where we have to disable DRIVER SIGNATURE ENFORCEMENT
When you have booted into windows after disabling driver signature, install the 1st Link file,
Install the Driver, when Installed it will show a COM Port installed, QUALCOMM one
Install the Softwares, default path will be C:\Program Files (x86)\Qualcomm\QPST\bin\
You also have items in your start menu, so run
1, In the "Start Menu" -> "QPST" -> "QPST Configuration" RUN This
2, Select the tab "PORT" and click "Add New Port ..."
3. A new window will open where the COM port which is newlly added to your system will be listed, select that port and add that
Keep that running
4 Go to the "Start Menu" -> "QPST" -> eMMC Software Downloadapp " RUN THIS
4.1 Uncheck, Program MMC Device
4.2 Click Browse, it displayed me PHONE ATTACHED with QUALCOM details near the top right of the image, where No ports Active is written
4.3 Check Search Path 2 and Browse to you files, where you have downloaded 3rd file. Which contains one hex, one img and mbn file
4.4 In the Flash Programming File name, enter the name of hex file
4.5 in boot image, enter the mbn file name
4.6 Click DOWNLOAD
at this point, it mounted me a 200kb drive which was not formatted. I have formatted that, and then kept this program running in the background as well
5. Winhex
5.1 Run Winhex, Make sure you have forensic version, and also Full version ,there are evolution version too, but that will not work. FULL VERSION and FORENSIC/SPECIALIST License is must
5.2 In Winhex, go to "File", "Restore Image", Change the file type from "WHX" to "Raw Image container"
5.5 Select lu6200.img from the 3rd file downloaded
5.5 Now it will ask for Target disc
5.6 Carefully select the QUALCOM, or else you will be formating your own HDD
5.7 In this window click OK
Now it will start giving your some strange, nasty warnings, just keep pressing OK, and Yes Continue Ok, etc etc
When that will finish, you phone will auto restart.
Now you may have to reflash that, or wipe it and install the KDZ ICS engineer version again. As right now My phone is in boot loop but I guess that can be fixed.
Tutorial followed from : http://choimobile.vn/threads/unbrick-lg-lu6200-ghim-cap-qhsusb-khong-thao-may.8448.html
Click to expand...
Click to collapse
Confirmed , LU6200 boot img working on su640 ..
and thnx man u saved my phone , Winhex Worked
mrroks said:
Confirmed , LU6200 boot img working on su640 ..
and thnx man u saved my phone , Winhex Worked
Click to expand...
Click to collapse
I'm sorry, but can you upload the fie again?
That baidu link above doesn't work anymore.
Sent from my LG-SU760 using XDA Free mobile app
---------- Post added at 01:10 PM ---------- Previous post was at 01:00 PM ----------
qqzwc said:
我大中华威武啊，哈哈
Click to expand...
Click to collapse
@qqzwc , are you still working on Korea LG Optimus 2X (SU760)?
Sent from my LG-SU760 using XDA Free mobile app
Genie's said:
I'm sorry, but can you upload the fie again?
That baidu link above doesn't work anymore.
Sent from my LG-SU760 using XDA Free mobile app
Click to expand...
Click to collapse
Link just use Google Translate > Russian to English , Everything is here :good:
mrroks said:
Link just use Google Translate > Russian to English , Everything is here :good:
Click to expand...
Click to collapse
I cant find it even though I saw with Chrome Translation.
Can you upload those file in any cloud storage.
If you can, it will be very thankful, because my Korean friends had LU6200 bricked.
Sent from my LG-SU760 using XDA Free mobile app
I am following all the steps. eMMC software showed that it QPST server not running. I ran eMMC download tool with Admin rights and that problem was gone.
Now when I Press download button this error pops up showing Image Download Failed. Cookie(if present) not received.
Is there a solution for that?
saaqirajput said:
I am following all the steps. eMMC software showed that it QPST server not running. I ran eMMC download tool with Admin rights and that problem was gone.
Now when I Press download button this error pops up showing Image Download Failed. Cookie(if present) not received.
Is there a solution for that?
Click to expand...
Click to collapse
i get the same error
saaqirajput said:
I am following all the steps. eMMC software showed that it QPST server not running. I ran eMMC download tool with Admin rights and that problem was gone.
Now when I Press download button this error pops up showing Image Download Failed. Cookie(if present) not received.
Is there a solution for that?
Click to expand...
Click to collapse
I am also getting the same error.
saaqirajput said:
I am following all the steps. eMMC software showed that it QPST server not running. I ran eMMC download tool with Admin rights and that problem was gone.
Now when I Press download button this error pops up showing Image Download Failed. Cookie(if present) not received.
Is there a solution for that?
Click to expand...
Click to collapse
i am also getting the same error
saaqirajput said:
I am following all the steps. eMMC software showed that it QPST server not running. I ran eMMC download tool with Admin rights and that problem was gone.
Now when I Press download button this error pops up showing Image Download Failed. Cookie(if present) not received.
Is there a solution for that?
Click to expand...
Click to collapse
Put the file at drive C: :fingers-crossed:
Q&A for New Storage Layout for HOX Endeavoru
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for New Storage Layout for HOX Endeavoru. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
this is great. so we don't need move to sd card app? ill make review as soon as i getting this done
donkey09 said:
this is great. so we don't need move to sd card app? ill make review as soon as i getting this done
Click to expand...
Click to collapse
Correct. No need to move apps.
Thanks teemo ... works like a charm
So New Layout needs a special rom? right? are there any ways get CM11/12 compatible with this layout? or how/where to get ROMS compatible with New Layout? if /sdcard becomes /data where is /sdcard?
maniel said:
So New Layout needs a special rom? right? are there any ways get CM11/12 compatible with this layout? or how/where to get ROMS compatible with New Layout? if /sdcard becomes /data where is /sdcard?
Click to expand...
Click to collapse
No more sd card
maniel said:
So New Layout needs a special rom? right? are there any ways get CM11/12 compatible with this layout? or how/where to get ROMS compatible with New Layout? if /sdcard becomes /data where is /sdcard?
Click to expand...
Click to collapse
As Thant say, the SD Card as we know it is gone. It has changed from FAT to ext4, which mean that you can not use USB Mass Storage to copy files. It is done only with MTP now.
Yes it need special made ROMs. I list all compatible ROMs on this page.
There will also be some FAQ in post #2 of the same page.
I am currently running CM12 20150208 on the New Layout. No problems till now. Not available yet.
I have a problem, after installing twrp2843-Big phone does not want to boot into recovery. I unplug the phone from the PC, boot into bootloader, push recovery and nothing happens, the phone just restarts again in the bootloader. What could be the problem? Thx.
wramp said:
I have a problem, after installing twrp2843-Big phone does not want to boot into recovery. I unplug the phone from the PC, boot into bootloader, push recovery and nothing happens, the phone just restarts again in the bootloader. What could be the problem? Thx.
Click to expand...
Click to collapse
Flash it again with fastboot and make sure there is no errors after flashing:
Code:
C:\>fastboot flash recovery twrp2843-BiG.img
teemo said:
Flash it again with fastboot and make sure there is no errors after flashing:
Code:
C:\>fastboot flash recovery twrp2843-BiG.img
Click to expand...
Click to collapse
flashing it twice, without errors. always trying twrp2810-HOX - same here.
flashing CWM, CWM loaded but now can not connect as a removable drive
I was able to restore the android through sideload from cwm. Now everything works. But still can not get to go to the new layout.
Everything Everywhere says okay, but the result is zero. And by the way I have not mounted as a USB flash drive from the CWM 6.0.4.7 and 6.0.4.8
Some information:
HTC One X 16Gb
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
RADIO-5.1204.167.31
cid: HTC__A07
UPD: just redownload recovery from another PC, flashed and it WORKS....seems it's probably my fault antivirus, it is not fully allowed to download recovery//
wramp said:
flashing it twice, without errors. always trying twrp2810-HOX - same here.
flashing CWM, CWM loaded but now can not connect as a removable drive
I was able to restore the android through sideload from cwm. Now everything works. But still can not get to go to the new layout.
Everything Everywhere says okay, but the result is zero. And by the way I have not mounted as a USB flash drive from the CWM 6.0.4.7 and 6.0.4.8
Some information:
HTC One X 16Gb
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
RADIO-5.1204.167.31
cid: HTC__A07
UPD: just redownload recovery from another PC, flashed and it WORKS....seems it's probably my fault antivirus, it is not fully allowed to download recovery//
Click to expand...
Click to collapse
What happens now, does it boot to the recovery?
If not, maybe you have a bad download?
teemo said:
What happens now, does it boot to the recovery?
If not, maybe you have a bad download?
Click to expand...
Click to collapse
The problem was my antivirus which blocked the download recovery. Now everything works perfectly, thank you!
I format data, reboot to recovery and connect device to PC. On the PC does not appear any drives, in Device Manager has a unknown device "One", as I understand it on the PC driver is not installed, where to get them? twrp 2.8.1.0 with the old layout worked fine and twrp2811.BiG worked fine too...
{
"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"
}
I am not at my windows PC right now, but you can try this (you may have to pick a different driver though):
Small guide for solving problem with usb not working in Windows.
Aat work, my Windows7 like to change settings as it think is best for me. I guess it just don't know me well enough. Here is what I do when Windows get confused and forget what I want.
First make sure you have the latest drivers from Google and HTC.
Install latest drivers from HTC for your PC. http://www.htc.com
Next, get your adb/fastboot drivers updated.
Locate "android.bat", mine is in C:\Android\android-sdk\tools, but yours will be wherever you initially installed your adb drivers.
Run the file and install any suggested updates.
Windows device manager (run devmgmt.msc from start menu or a command window).
Connect your phone and check where it get attached. For a working connection, it should say "Android USB Devices" -> "My HTC", but since you read this, chances are, that your device is in "Other Devices" -> "Android Phone".
That is what this guide will correct.
1. Wrong driver - double click "Android Phone"
2. Update Driver
3. Browse (for your HTC driver, which is already installed)
4. Pick the driver yourself
5. Select "Android USB Devices" -> Next
6. Select "My HTC" -> Next
7. Choose Yes - You know you want the HTC driver
8. Ahhh, success - test your adb/fastboot/MTP/UMS
9. Here is what happened. We make Windows choose the correct driver and Windows will place it under Android USB Devices.
Let me know if it works or not.
Unable to copy the rom from my pc
Hi!
I installed the rom of the 2nd February and everything worked well for me! no problem and I was very happy of that! but the lack of storage bothered me a lot and I tried the new layout with twrp recovery. I flashed the recovery and then when I want to copy the rom and the gapps on my one x , IMPOSSIBLE!!!
When the phone is connected there is just a repetitive sound of disconnection usb storage! I don't know what to do
Patinho888 said:
Hi!
I installed the rom of the 2nd February and everything worked well for me! no problem and I was very happy of that! but the lack of storage bothered me a lot and I tried the new layout with twrp recovery. I flashed the recovery and then when I want to copy the rom and the gapps on my one x , IMPOSSIBLE!!!
When the phone is connected there is just a repetitive sound of disconnection usb storage! I don't know what to do
Click to expand...
Click to collapse
Hi. Sorry it did not turn out well for you. But hang on, it will.
First, it is not enough to flash the recovery. You also need to prepare the memory for the new layout. This is all described in this guide: http://shares.teemo.dk/s#d676c36c-e...rive.teemo.dk/Switch to SuperSized Layout.pdf
Try to follow it and see if that helps. Just remember that it will delete everything on the sdcard. Copy your data to PC first
teemo said:
I am not at my windows PC right now, but you can try this (you may have to pick a different driver though):
Small guide for solving problem with usb not working in Windows.
Aat work, my Windows7 like to change settings as it think is best for me. I guess it just don't know me well enough. Here is what I do when Windows get confused and forget what I want.
First make sure you have the latest drivers from Google and HTC.
Install latest drivers from HTC for your PC. http://www.htc.com
Next, get your adb/fastboot drivers updated.
Locate "android.bat", mine is in C:\Android\android-sdk\tools, but yours will be wherever you initially installed your adb drivers.
Run the file and install any suggested updates.
Windows device manager (run devmgmt.msc from start menu or a command window).
Connect your phone and check where it get attached. For a working connection, it should say "Android USB Devices" -> "My HTC", but since you read this, chances are, that your device is in "Other Devices" -> "Android Phone".
That is what this guide will correct.
1. Wrong driver - double click "Android Phone"
2. Update Driver
3. Browse (for your HTC driver, which is already installed)
4. Pick the driver yourself
5. Select "Android USB Devices" -> Next
6. Select "My HTC" -> Next
7. Choose Yes - You know you want the HTC driver
8. Ahhh, success - test your adb/fastboot/MTP/UMS
9. Here is what happened. We make Windows choose the correct driver and Windows will place it under Android USB Devices.
Let me know if it works or not.
Click to expand...
Click to collapse
it does not work. in the Device Manager now 2 "My HTC", and in my computer there is nothing
and I am not alone, some of my friends have a same problem
teemo said:
Hi. Sorry it did not turn out well for you. But hang on, it will.
First, it is not enough to flash the recovery. You also need to prepare the memory for the new layout. This is all described in this guide:
Try to follow it and see if that helps. Just remember that it will delete everything on the sdcard. Copy your data to PC first
Click to expand...
Click to collapse
thanks! it was a problem of drivers! everything works fine now! thanks a lot! :good:
---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------
Hi!it's me again ! Thanks again for your help but i want to know if we can't use the 2GB extra data space. i have the 16GB version and the layout shows me 10GB. is that space useless?
Patinho888 said:
thanks! it was a problem of drivers! everything works fine now! thanks a lot! :good:
---------- Post added at 11:42 AM ---------- Previous post was at 11:36 AM ----------
Hi!it's me again ! Thanks again for your help but i want to know if we can't use the 2GB extra data space. i have the 16GB version and the layout shows me 10GB. is that space useless?
Click to expand...
Click to collapse
At the moment, you can use it only if you have given the apps root access. Developer options - Root access:adb+apps. Then you can access it from a root filemanager.
The recovery can use it to store anything you like. I use it for different ROMs. Your PC can (currently) only access it via TWRP.
And as Thömy suggest in his document, you can keep your old data (from old layout) on it. Then, if you want to go back to the old layout, you can use the data directly (xtradata is the old data).
@popcee.p
look in cm12 thread
Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"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"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Valeeeu dms irmao, ajudou dmss
Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).