How to unbrick Lenovo A3000 - A3000 General

A couple of weeks ago, I bricked my A3000-F. I finally found a way to unbrick it.
Note: I also put the link for the A3000-H.
Requirements: A Windows computer, a program like WinZip to decompress files, a cable to connect your tablet to your computer, and (duh) your tablet.
Warning: If anything goes wrong, I am not responsible for it. In addition, all data on your tablet is already lost, or will be lost after this tutorial.
Download at the bottom of the post the required rar file for either your A3000-F or A3000-H.
Step 1: Decompress A3000 fix package.rar. Inside you should ind 3 comppressed files called R1 DRV, R1 Flash_Tool, and R1 target_bin. Decompress these files.
Step 2: Navigate to Control Panel and click on Device Manager. In device manager, go to Other Devices, expand it, and make sure MT65xx Preloader is 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"
}
Step 3: Right click on it, and select Update Drivers.
Step 4: Click on the second option in the window that pops up.
Step 5: In the next window, click again on the second option, and select the driver that has the words multiple and serial. I don't know how it's called in English because I'm Spanish.
*
Step 6: Click on Have Disk
Step 7: Browse to the decompressed A3000 fix package, and select the decompressed R1 DRV.
Step 8: Select USB_Driver.
Step 9: Select your OS. In my case Windows 7. For Windows 8, too bad so sad.
Step 10: Now select 32 bits or 64. In my case 32.
Step 11: If prompted, click accept.
Step 12: Click next, then wait a little,you will get a success message, then close. After this, close all open windows.
Step 13: Navigate do the decompressed A3000 fix package, and go to the decompressed R1 Flash_Tool folder.
Step 14: Open up the Flash Tool program (The blue icon).
Step 15: Click on the Scatter Loading on the right.
Step 16: Navigate to your decompressed A3000 fix package, and open the decompressed R1 target_bin.
Step 17: There you will find 3 files. Select the MT6589_Android_scatter_emmc
Step 18: Now tick the check-box next to FAC, and then click those 3 letters (FAC)
Step 19: In the same target_bin folder as before, now select fac. (It may be called fac.img)
Step 20: Now tick the check-box next to DA DL All With Check Sum Then Click Download.
Step 21: Wait. A pinkish bar will appear at the bottom, then a yellow one, then a green circle will appear.
Step 22: Unplug your tablet from your computer and plug it in to a normal charger. Turn it on. When you first turn it on, it will be in chinese. Just tap on the first option and change to the desired language.
Step 23: Sit back and enjoy your reborn tablet.
A3000-F Download: http://www.mediafire.com/download/xdcvhn0c2gbx2lm/A3000-F_fix_package.rar
A3000-H Download: http://www.mediafire.com/download/tk9hip7z753y5wh/A3000-H_fix_package.rar
I hope I helped! The thanks button is waiting for you.

PJMOR said:
I'm new to XDA, and I just bricked my a3000 tablet. I'm hoping someone could post the stock ROM or post a guide to unbrick to help me and other people in the future.
Click to expand...
Click to collapse
you can see stock firmware in developer section.

hey man i have the same problem but i can't download the file of the lenovo a3000-f when i'm about to finish it says network error i'v done it 5 times and the same thing happens isn't there another link you can pass me google docs is bad

Added a new download link.

Did I help? Did you unbrick your tablet?

thanks
PJMOR said:
Did I help? Did you unbrick your tablet?
Devices:
-LG Optimus L3 II
-Lenovo IdeaTab A3000-F
-Hyundai Dual SP 4S
Before you criticize a man, walk a mile in his shoes. That way, when he gets mad, he is a mile away and barefoot.
Click to expand...
Click to collapse
Thanks, dude! This thing helped me and my tab A3000-F!!! :good::highfive:

GanibalSerg said:
Thanks, dude! This thing helped me and my tab A3000-F!!! :good::highfive:
Click to expand...
Click to collapse
That's why I posted this tutorial.

where can I find the "A3000 fix package" please? do you have a link for it?

follow up: I searched the A3000-H archive for a "fix package.rar" but it's not there, no I searched the whole internet for a A3000 fix package.rar but it's only mentioned in this very post!
I gonna need my tablet soon, and no other drivers are working! please upload your copy of "a3000 fix package.rar" or mention the link here.. thanks.

Sorry for being offline for so long, I've been studying for exams. Anyways I saw your reply. So, for the model F, here's two download links for the fix package:
https://docs.google.com/uc?export=download&confirm=6K2G&id=0B2u6Nx1AQ_66Tzhrek05Q0lPWms and https://www.dropbox.com/l/0qB1QGrDHKDKZJed6U9Z5s
And for the model H there's this download link for the fix package:
https://mega.co.nz/#!3M1U3CCA!Jo5LDEKYeFLfjdCZNX1JVhkrbFcJJLgf7LL-f1r152g
If you find that the guide is complicated, I'm happy to remake one, now that I have a newer English pc. Hope this helps!

PJMOR said:
Sorry for being offline for so long, I've been studying for exams. Anyways I saw your reply. So, for the model F, here's two download links for the fix package:
https://docs.google.com/uc?export=download&confirm=6K2G&id=0B2u6Nx1AQ_66Tzhrek05Q0lPWms and https://www.dropbox.com/l/0qB1QGrDHKDKZJed6U9Z5s
And for the model H there's this download link for the fix package:
https://mega.co.nz/#!3M1U3CCA!Jo5LDEKYeFLfjdCZNX1JVhkrbFcJJLgf7LL-f1r152g
If you find that the guide is complicated, I'm happy to remake one, now that I have a newer English pc. Hope this helps!
Click to expand...
Click to collapse
I can't understand! this is the same link of the rom from above! it contains none of the three folders mentioned above!
still no link for the fix package I'm afraid.

faissl said:
I can't understand! this is the same link of the rom from above! it contains none of the three folders mentioned above!
still no link for the fix package I'm afraid.
Click to expand...
Click to collapse
The files are there, it just may be a little hard to find them. Anyways, I'm repackaging the files, and it should be up and running in about an hour!

I just un-bricked my A3000F, but it took a while. First you have to open up your tablet. And that is tricky.
Because of some reason my tablet lost contact with "SP flash tool" and as reckless as I'am, I decided to open it. And some how unplug the battery. Totally forgetting that there is a thing called Google these days, I started tearing and ripping, like monkey's do when they want to open an nut. Although I skipped the part where they use a rock.
And I opened it..........:victory:
I disconnected the battery and I started to run the "sp flash tool" from this post. And to every bit of my surprise, it found the tablet. Now I wasn't there yet, because now it gave me error code 8038.
Wondering what this code meant, I now remembered my ones good friend Google, and I started praying on my keyboard. Oh dear Google, holy is thy name. Please would you show me would you give me the answer to error code 8038. But like god has forsaken mankind a long long time ago, Google din't answer. Instead now he showed me how to open a Lenovo A3000. Thinking by my self, why Google why. And remembering the good old day's when Google showed me how to flash the ROM of my X-box 360, with just some bits and peaces. I started to feel some anger boiling inside of me, and I threw down my mouse. Accidentally pushing the format switch, and some how OK. And because my usb wiggled a bit, it started the format. And I was greeted by a green circle. So I thought to myself, what if I do the same with update. And again, a green circle. And after that i did the download, and it worked. My A3000F is up and running again. So this is what you have to do
-open your Lenovo A3000F after you removed the (15) screws.
-Start at the bottom on the side of the volume button and work your way around it.
-When opened it, there's a little white square on the left under your lence. Rip that out.
- And start sp flash tool. First format it, then update it and then you can download your stock firmware.
Good luck.......

I just un-bricked my A3000F, but it took a while. First you have to open up your tablet. And that is tricky.
Because of some reason my tablet lost contact with "SP flash tool" and as reckless as I'am, I decided to open it. And some how unplug the battery. Totally forgetting that there is a thing called Google these days, I started tearing and ripping, like monkey's do when they want to open an nut. Although I skipped the part where they use a rock.
And I opened it..........
I disconnected the battery and I started to run the "sp flash tool" from this post. And to every bit of my surprise, it found the tablet. Now I wasn't there yet, because now it gave me error code 8038.
Wondering what this code meant, I now remembered my ones good friend Google, and I started praying on my keyboard. Oh dear Google, holy is thy name. Please would you show me would you give me the answer to error code 8038. But like god has forsaken mankind a long long time ago, Google din't answer. Instead now he showed me how to open a Lenovo A3000. Thinking by my self, why Google why. And remembering the good old day's when Google showed me how to flash the ROM of my X-box 360, with just some bits and peaces. I started to feel some anger boiling inside of me, and I threw down my mouse. Accidentally pushing the format switch, and some how OK. And because my usb wiggled a bit, it started the format. And I was greeted by a green circle. So I thought to myself, what if I do the same with update. And again, a green circle. And after that i did the download, and it worked. My A3000F is up and running again. So this is what you have to do
-open your Lenovo A3000F after you removed the (15) screws.
-Start at the bottom on the side of the volume button and work your way around it.
-When opened it, there's a little white square on the left under your lence. Rip that out.
- And start sp flash tool. First format it, then update it and then you can download your stock firmware.
Good luck.......
Click to expand...
Click to collapse
Happy to see I helped!
I can't understand! this is the same link of the rom from above! it contains none of the three folders mentioned above!
still no link for the fix package I'm afraid.
Click to expand...
Click to collapse
My bad. I realized I hadn't included all the files in the A3000-H version of the fix package. Well, I fixed it. Here it is:
https://drive.google.com/drive/u/0/#folders/0BybeKUqhknfDdDRvZnoxc05JLVk

PJMOR said:
Happy to see I helped!
My bad. I realized I hadn't included all the files in the A3000-H version of the fix package. Well, I fixed it. Here it is:
https://drive.google.com/drive/u/0/#folders/0BybeKUqhknfDdDRvZnoxc05JLVk
Click to expand...
Click to collapse
Hi, the A3000-H fix package dloaded frm mega, the content within it is different from the step you shown. Furthermore, the package which you upload to google drive no longer there. Is there any way to dload the A300-H full package and unbrick my tablet following your step? Hope to get reply from you asap. Thanks and have a nice day. :good:

Fixed the file. New download link at the bottom of the initial post.

PJMOR said:
Fixed the file. New download link at the bottom of the initial post.
Click to expand...
Click to collapse
Thanks for the dload link.
I was able to follow until step 21. From here on, instead of yellow bar after pinkish bar, red bar appear with error. ]
1st picture is when I clicked "Firmware Upgrade"; 2nd pic is "Download" ; 3rd pic is the error before my tab won't turned on.
Any helpful inputs will be appreciated. Thanks

The A3000 gives you that error message after unsuccessfully flashing the rom? If so, hit the "I'm feeling lucky" button, follow my guide on installing CWM (http://forum.xda-developers.com/lenovo-a3000/general/custom-recovery-img-t2893011), and then just reboot into recovery and wipe your data partition.

PJMOR said:
The A3000 gives you that error message after unsuccessfully flashing the rom? If so, hit the "I'm feeling lucky" button, follow my guide on installing CWM (http://forum.xda-developers.com/lenovo-a3000/general/custom-recovery-img-t2893011), and then just reboot into recovery and wipe your data partition.
Click to expand...
Click to collapse
I couldn't press the "I'm feeling lucky' buttom because it seems t be stucked on that page. After restart my tab, it stucked at lenovo logo. Than I pressing volume and power button, it stucked in "meta mode".
After flashing , it fails and my tab couldn't turn on anymore = no display at all. Than I follow this guide till step 21 and flash tool pop up pic 1 and pic 2

Unfortunately, I'm stumped. I don't know how to fix that. Sorry

Related

[REF] If odin gives error - unbricking

Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - 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"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution
try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.
dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.
dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.
Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)
Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.
Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).
I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App
Maybe we should pin this or any other topic for people to post if they have bricked their device?
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.
Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.
ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps
m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.
was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.
Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash
Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App

So I bricked my GNEX...Then brought it back to life!

So, this morning at 5am (yes, stupid time to be playing) I flashed a zip. I have stored on my phone zips for both this and my tablet, and guess what genius did? flashed the wrong friggin one! Very surprised it went through without fault, but hey, **** happens.
So, basically what happened, is my phone became a brick. Black screen, could not boot it up, couldn't et to bootloader or download mode or recovery, tried several things like pulling battery for 30 secs then putting back in, plugging into PC without battery and putting battery in, leaving without battery or SIM for 30 minutes and putting back in, NA friggin DA. Still a brick. Not even the vibration when it first kicks in. Nothing
Starting to think time to call tech support, but as I was trying to plug into PC, I noticed something trying to install, then disappearing real fast. That was my first clue. I opened device manager, plugged phone in, and watched what was happening. A device called OMAP4460 was trying to install for half a second before disappearing, failing, but still, it was something. Even though screen was still blank, and not even bootloader would come up, this was happening. So I googled.
I found this site/thread: http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/. Legija, is a friggin genius Downloaded and unzipped the package, ran the bat, and plugged in the phone. But alas, still no joy
Reread his post - install drivers first...So, putting on my tech hat, how to install drivers if device is not listed, I went into the Actions menu in Task Manager (Win 7), and selected to add legacy hardware. I then chose to install manually, then selected have disk, and browsed to the drivers in the zip package from Legija (all this without device plugged in BTW). I installed the OMAP flash driver successfully, and now showing in task manager with the nice yellow triangle/exclamation mark.
Ran the bat file again, plugged phone in **WITHOUT** battery in phone, and off it went scrolling through it's processes, ninja'n away my f'up. When it completed, put battery back in, held down power, and up she came! Woot! Got back into OS no issues, and I'm one very happy camper.
So I thought i'd share, not thinking anyone else may do the same bloody stupid thing, but maybe a variance, or just have the same symptom (black screen, attempt to install OMAP when plugged into USB), this may just help you! AS for me...deleted all files not for GNEX, i'll continue to stuff around before work, so this is safe
EDIT:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Thanks for sharing this find, I'm sure others will find this to be useful
No problem, true believer in sharing my stupid mistakes so other may not follow, or if they do, know how to fix
Oh, in my write up - one change now edited - run the bat with the phone connected to USB **WITHOUT** battery in, once it's finished insert and boot up
Next time I'll be more safe while flashing roms to my phone.
Great find.
wow, this is possible? i thought cwm will prevent you from flashing wrong zips and even if not, why would it kill the bootloader? i was under the impression gnex is close to unbrickable but this topic you linked opened a whole can of worms for me, whats with all these hundreds of people who hard(!)bricked their nexus ... did i miss something?
This was a custom zip I had created myself to do some things on my tab, it ran from install script an install.sh that then went and installed a recovery img. Pretty sure i've never seen this before from any install zip, it was the behaviour I put in mine that allowed it to go through, and I hadn't put into the script to stop if not correct device - lesson learned
BUT - that said, you can do things like this to your phone running scripts, very easy to actually if it's running from su... So never run scripts unless you trust he person whose created it (or have written it yourself and certain of it), know it's definitely for your device, and, most importantly - never miss this step - have had 3 cups of coffee first :good:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
rekrapg said:
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
Click to expand...
Click to collapse
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If it's not permanent, it's not, and never was, a brick.
Click to expand...
Click to collapse
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
Well it happens my dude.....at least he took the time out to give a guide and explained how he fixed it just in case someone else does something similar
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
efrant said:
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
True....but most people would not know what to do in this situation and call it a day....at least he searched Google and fixed his problem. Wish more people were like him ya know
---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------
rekrapg said:
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Click to expand...
Click to collapse
Exactly I said most people would have called it a day.....ZOMGZ MA FONEZ NO LITE UPZ IT HARDSOFT BRICKED!! .....lol all joking aside man your like me I wouldn't have stopped until I was absolutely sure I needed them JTAG boys
Persistence pays off...remember that
Yup. In most cases, there's a way around a problem, you just have to dig until you find it
Congratulations
Saludos desde Ecuador
Though I don't want to have chance to perform your provided method, it's really good to know, in case....
Congratulation and thanks!
rekrapg said:
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Chad_Petree said:
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Click to expand...
Click to collapse
Choose the one closest to what displays on the device manager. I started with the OMAP Flash Drive one and it worked for me, but you can always choose the 'update driver' option and install another if required. Turn off User Account Control in Control Panel/Users and make sure you're on an admin account, as it may by default block the ability to install unsigned drivers, to be honest not sure on that one as it's always been first port of call for me on Win 7 (and Vista).
I also found this that might help: http://www.techspot.com/community/t...signed-drivers-in-windows-vista-7-x64.127187/
Wish I would have found this a week ago! The exact same thing happened to me, except I had been running a working JB ROM for a day or so.
Went jogging, was listening to music, came home, music stopped, screen wouldn't turn on with power button or USB cable with a charger or a computer, but there was a notification LED flashing. No amount of pressing and holding the power button would bring it back to life, so I pulled the battery. After that it was in the exact state your GNEX was in. Not even the vibrate when trying to power it up. After a few hours of charging and trying all sorts of things to breathe life into it (including a battery swap) I ended up returning it to the brick and mortar VZW store and they replaced it because I was under 2 weeks with the phone.
Thanks for posting!
I ran the OMAPFLASH_tuna on my GNex and now, I seem to be stuck at "Sending Data"(SEE last line in the image attached)
The values of 131072 has been like that for over 20 minutes and have not changed. What data is it sending and to who or where?
to those who've used this too, What should happen after this?
thanks...
{
"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 would be lying if I said I knew exactly what this wonderful tool is doing mate With mine, it ran through in like 30 seconds to completion. I ran it 3 times to be sure! I have 2 suggestions,
1. Sign up to those forums and ask the expert
2. If your device is already 'bricked', it may be worth just disconnecting, closing the CMD window, reconnect and re-run it.
I'm no expert on this application though, I simply found it, it worked for me, so I shared. So option 1 may be your best shot. It's quite likely the bloke who created the tool will be able to let you know the proper path to go down.
EDIT: I am at work atm, so I can't 're-run' it on my device to show you the screen - but I recall it comes up with a 'press any key to continue' prompt after completion (pressing any key just re-runs it).
Funny because another person on GSMHosting is experiencing the same problem and says that his just stops downloading... Just like mines and at the same stop too... hummm...

[GUIDE] Flashing KDZ Files

(THIS TUTORIAL IS ONLY FOR FLASHING KDZ FILES, I WON’T PROVIDE ANY KDZ FILES HERE, BEFORE YOU FLASH ANY KDZ FILES MAKE SURE IT IS INTEDED FOR YOUR DEVICE, FLASHING THE WRONG KDZ FILE WILL BRICK YOUR DEVICE, USE THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF YOU’RE DEVICE GETS BRICK)
(Update) sorry guys, dont have time to update the tutorial. You can used abuulala's method http://forum.xda-developers.com/showthread.php?p=53776835
Or this method http://forum.xda-developers.com/showthread.php?p=44983841
This tool is tested and working using XP, 7, and 8.
Use this tool if you experience errors on other KDZ Flasher
Tools:
LG Updater
Flashtool
LG Driver
Windows Enabler
MSXML Parser
(All the files above is in the archive)
Click here for link
Steps to do before flashing:
1. Backup your data, I am not responsible if you lose your important data.
2. Makes sure your device have 50% remaining battery or more. Full charge is recommended as putting your phone into “Download Mode” doesn’t charge the device.
----------------------------------------------------------------------------
Flashing the KDZ:
1. Unzip the files in your preffered location.
2. Install B2CAppSetUp,wait for the installation to finish then quit the application after the installation.
3. Install LGUnitedMobileDriver and MSXML 4.0 SP3 Parser
4. Open the properties of the UpTestEX.exe and Windows Enabler.exe then enable compatibility mode and admin rights (Right click> Properties> Compatibility tab> Check the box “Run this program in compatibility mode for: Windows XP SP3”> also check the box that says “Run this program as an administrator.” Don’t forget to hit “OK.” (Don't forget to do Windows Enabler.exe 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"
}
5. Double click Windows Enabler, it will go on your taskbar, left-click to enable. If it is enabled, it should look like this:
6. Open UpTestEX
7. Select “3GQCT” and “CS_EMERGENCY”
8. Locate your .KDZ file.
9. Now put your phone in “Download Mode” (To do this: Turn your phone off completely, press and hold Vol Up button together with power button, don’t release until you see “Download Mode” on-screen.
10. Connect phone to the computer and wait for the drivers to install.
11. If you’re ready, click the “Normal web upgrade test.” Note: Don’t click the “Start Upgrade” option.
12. A popup window will show, just click “Upgrade Start.”
13. Choose “Different Country” and “(Your preffered language, mine is ENGLISH)” After you click OK, LG Updater will now open.
14. The update will now start.
15. Your phone will reboot after some time, don’t unplug the cable yet, the upgrade is not yet done.
16. When the upgrade is finished, just close the updater. Your phone is now Upgraded/Downgraded or Unbricked!
-----------------------------------------------------
If you encounter bootloop after the process:
Turn the phone off completely, press and hold Vol Down and Power Button at the same time, don't release until you see "Factory Reset," Press Power button twice to confirm.
expressions104 said:
(THIS TUTORIAL IS ONLY FOR FLASHING KDZ FILES, I WON’T PROVIDE ANY KDZ FILES HERE, BEFORE YOU FLASH ANY KDZ FILES MAKE SURE IT IS INTEDED FOR YOUR DEVICE, FLASHING THE WRONG KDZ FILE WILL BRICK YOUR DEVICE, USE THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF YOU’RE DEVICE GETS BRICK)
This tool is tested and working using XP, 7, and 8.
Use this tool if you experience errors on other KDZ Flasher
Tools:
LG Updater
Flashtool
LG Driver
Windows Enabler
MSXML Parser
(I created an archive with all the tools required for flashing)
link for tools
Steps to do before flashing:
1. Backup your data, I am not responsible if you lose your important data.
2. Makes sure your device have 50% remaining battery or more. Full charge is recommended as putting your phone into “Download Mode” doesn’t charge the device.
----------------------------------------------------------------------------
Flashing the KDZ:
1. Unzip the files in your preffered location.
2. Install B2CAppSetUp, quit the application after the installation.
3. Install LGUnitedMobileDriver and MSXML 4.0 SP3 Parser (Skip if you already installed this)
4. Open the properties of the UpTestEX.exe and Windows Enabler.exe to enable compatibility mode and admin rights (Right click> Properties> Compatibility tab> Check the box “Run this program in compatibility mode for: Windows XP SP3”> also check the box that says “Run this program as an administrator.” Don’t forget to hit “OK.”
5. Double click Windows Enabler, it will go on your taskbar, left-click to enable. If it is enabled, it should look like this:
6. Open UpTestEX
7. Select “3GQCT” and “CS_EMERGENCY”
8. Locate your .KDZ file.
9. Now putyou phone in “Download Mode” (To do this: Turn your phone off completely, press and hold Vol Up button together with power button, don’t release until you see “Download Mode” on-screen.
10. Connect phone to the computer and wait for the drivers to install.
11. If you’re ready, click the “Normal web upgrade test.” Note: Don’t click the “Start Upgrade” option.
12. A popup window will show, just click “Upgrade Start.” After you click it the LG Updater will open.
13. Choose “Different Country” and “(Your preffered language, mine is ENGLISH)”
14. The update will now start.
15. Your phone will reboot after some time, don’t unplug the cable yet, the upgrade is not yet done.
16. When the upgrade is finished, just close the updater. Your phone is now Upgraded/Upgraded or Unbricked!
-----------------------------------------------------
If you encounter bootloop after the process:
Turn the phone off completely, press and hold Vol Down and Power Button at the same time, don't release until you see "Factory Reset," Press Power button twice to confirm.
Click to expand...
Click to collapse
This is the error I get after clicking on upgrade start button. Pls help on what I can do. I used windows 7 pro 32 bit system.
Im getting that error too!!!
Somebody help!!!
trojan ledge said:
This is the error I get after clicking on upgrade start button. Pls help on what I can do. I used windows 7 pro 32 bit system.
Click to expand...
Click to collapse
You are using an installer from another guide make sure you download the software at the link in the first post.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
You are using an installer from another guide make sure you download the software at the link in the first post.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
It's the tool from this post. If I'm not getting this error, it'll be "Windows Explorer not working" error, there by crashing the tool itself. May be I try another system.
trojan ledge said:
It's the tool from this post. If I'm not getting this error, it'll be "Windows Explorer not working" error, there by crashing the tool itself. May be I try another system.
Click to expand...
Click to collapse
Make sure the LG updater is running and all drivers installed and try again.
Sent from my LG-P930 using xda app-developers app
Now this is the error i am getting. :crying: I'm not progressing in this stuff. Pls help, this is my first android and i'm new to flashing and stuffs
http://forum.xda-developers.com/attachment.php?attachmentid=1914653&stc=1&thumb=1&d=1367013492
I was getting that same error too!
But then I tried the whole procedure again on Windows 7 32BIT, and it worked!!!
So try on a 32bit OS.
Hope that helped. :good:
---------- Post added at 08:50 PM ---------- Previous post was at 08:45 PM ----------
Try this method. Its really easy. This is how I got it done. (BTW, not my guide).
http://wiredsoup.blogspot.com/2013/02/lg-optimus-su640-comfirmed-working.html
:good:
Hi,
I'm having the exact same issue. I tried it with win8pro and xpPro(both x86) and got the same behaviour at every try:
After the update starts it took some havy load on CPU and HDD transfer for a few seconds while a cab file appears in the working directory. After that the CPU/HDD load reduces to 0 and the cab file disappears again. About half a minute later the "application not responding" error pops out.
I'm pretty frustrated right now. Can anyony help?
Thor368
Make sure you followed step 4. Its very important. Set the uptestex and windowsenabler properties to "windows xp compatibility" and "run as administrator". Install lg drivers and msxml parser. I think reboot would be nice.
I didnt get any errors trying this guide on windows xp home, 7, and windows 8 pro (all 32bit). Try disabling your antivirus for a while.
expressions104 said:
Make sure you followed step 4. Its very important. Set the uptestex and windowsenabler properties to "windows xp compatibility" and "run as administrator". Install lg drivers and msxml parser. I think reboot would be nice.
I didnt get any errors trying this guide on windows xp home, 7, and windows 8 pro (all 32bit). Try disabling your antivirus for a while.
Click to expand...
Click to collapse
Also works with 64 bit
Sent from my LG-P930 using xda app-developers app
nothing happen after point 12... I don t get a pop up asking me to choose a country...what to do???
help please
EDIT : it worked.. I just had to completely close B2CAppSetup completely even from the system tray...
cheers for your help
life saver!
Working almost well for me, but the phone is in Korean / Chinese even if I selected Other country/English
how change that ?
Edit: ok solved it was the red icon with the letter A on it :highfive:
win8
has anyone successfully flashed kdz file using windows 8?
Yeah. Tested it with windows 8. As you seen in the pictures its windows 8. Just remember to enable compatibility mode and run as admin.
expressions104 said:
(THIS TUTORIAL IS ONLY FOR FLASHING KDZ FILES, I WON’T PROVIDE ANY KDZ FILES HERE, BEFORE YOU FLASH ANY KDZ FILES MAKE SURE IT IS INTEDED FOR YOUR DEVICE, FLASHING THE WRONG KDZ FILE WILL BRICK YOUR DEVICE, USE THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IF YOU’RE DEVICE GETS BRICK)
This tool is tested and working using XP, 7, and 8.
Use this tool if you experience errors on other KDZ Flasher
Tools:
LG Updater
Flashtool
LG Driver
Windows Enabler
MSXML Parser
(I created an archive with all the tools required for flashing)
link for tools
Steps to do before flashing:
1. Backup your data, I am not responsible if you lose your important data.
2. Makes sure your device have 50% remaining battery or more. Full charge is recommended as putting your phone into “Download Mode” doesn’t charge the device.
----------------------------------------------------------------------------
Flashing the KDZ:
1. Unzip the files in your preffered location.
2. Install B2CAppSetUp, quit the application after the installation.
3. Install LGUnitedMobileDriver and MSXML 4.0 SP3 Parser (Skip if you already installed this)
4. Open the properties of the UpTestEX.exe and Windows Enabler.exe to enable compatibility mode and admin rights (Right click> Properties> Compatibility tab> Check the box “Run this program in compatibility mode for: Windows XP SP3”> also check the box that says “Run this program as an administrator.” Don’t forget to hit “OK.”
5. Double click Windows Enabler, it will go on your taskbar, left-click to enable. If it is enabled, it should look like this:
6. Open UpTestEX
7. Select “3GQCT” and “CS_EMERGENCY”
8. Locate your .KDZ file.
9. Now put your phone in “Download Mode” (To do this: Turn your phone off completely, press and hold Vol Up button together with power button, don’t release until you see “Download Mode” on-screen.
10. Connect phone to the computer and wait for the drivers to install.
11. If you’re ready, click the “Normal web upgrade test.” Note: Don’t click the “Start Upgrade” option.
12. A popup window will show, just click “Upgrade Start.” After you click it the LG Updater will open.
13. Choose “Different Country” and “(Your preffered language, mine is ENGLISH)”
14. The update will now start.
15. Your phone will reboot after some time, don’t unplug the cable yet, the upgrade is not yet done.
16. When the upgrade is finished, just close the updater. Your phone is now Upgraded/Downgraded or Unbricked!
-----------------------------------------------------
If you encounter bootloop after the process:
Turn the phone off completely, press and hold Vol Down and Power Button at the same time, don't release until you see "Factory Reset," Press Power button twice to confirm.
Click to expand...
Click to collapse
HI , i have a boubt does it work on my LG Optimus 3d?
SU760 Upgrade ICS to JB
Boss I am using SU760 which has ICS 4.0.4. now i want to upgrade to JB. Can anyone post step by step procedure on how to upgrade to JB, so that I won't brick my device. It was rooted by the previous owner.
Would appreciate if anyone can post detailed instructions as I am a novice in installation of Android OS.
Thanks.
Thanks
It really helped me to flash KDZ on my LU6200 without any issue.
ladiesman6 said:
HI , i have a boubt does it work on my LG Optimus 3d?
Click to expand...
Click to collapse
Yes, i think it would work on any lg android devices. Just make sure you download the correct kdz for your device. Sorry for late reply.
hello there i have a problem with B2CAppSetUp, when i install it, it going nothing, only show the pop-up you need internet connection to upgrade software, i already click continue but it nothing happened, then i skip this, then continue the next point, but when i click upgrade it needs B2C, anyone can help me?:crying:

How to guide (9.0 Android) LVM Chinese Unification Storage Method

In this guide, I will show how to how to change from LVM to Chinese unification storage method. Windows OS Only.
This guide is specifically for Oppo Find 7(A/S).
The idea of changing to chinese unification storage method is to have access to 8.1 Android operating system and future Android OS builds.
Please follow these following steps in order be able to run 8.1 Android on your OPPO Find 7.
1) Back up only your internal storage because after you flash the following tools, the internal storage will be wiped completely.
2) Download this file (for OPPO Find 7s) and this file (for OPPO Find 7a) then run the following steps:
Extract the files, and locate the QcomMtk_Driver_Setup.exe (*install this driver*) and reboot your computer system.
After rebooting, take off the battery off the Oppo find 7 and press the volume up button and connect to the PC using a micro USB cable. Go to the device manager, open the ports tab and there should be something like qualcomm etc. If there is no warning sign then you are fine and you should proceed along the steps. If there is a warning sign, just right click on the driver and update by letting windows finding the appropriate 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"
}
Then go back to the folder where you extract the zip file and locate (X9077_Android5.0_32G_20150520.exe) or X9007 respectively and run as administrator. rights only.
Agree with the licence. As shown in the image.
Now, again, make sure your battery is removed, hold volume up button and connect to the pc.
Click the first top left button as indicated in the image below.
Now, the software should do the rest so please be patient and wait until the green line has finished and the timeclock down on the bottom right as come to a halt.
After the green line has finished, please remove your device and plug back your battery. Let the device fully boot up before moving on the following steps.
After you get to the setup screen. Press and hold the power off button and shutdown fully before going back to the fast boot mode by pressing volume up and power button at the same time, the battery needs to be installed this time.
-
Now, flash the twrp modded image using fast boot flash and download the two files fastboot and twrp-modded img :
1) Have your phone in bootloader mode. (Turn off your phone, press volume up button and power button together and connect usb).
2) Navigate to the folder and click on the top left of the folder and copy that. e.g C:\Users\samgi\Desktop\platform-tools
3) Open cmd and type in: cd C:\Users\samgi\Desktop\platform-tools
4) In cmd type in: fastboot flash recovery image-modded.img
4) Remove USB and press power button and volume down button simultaneously.
-After you have flashed the recovery, boot into recovery and store the ROM, GAPPS and cm13 unified patch in the external sd card using your USB.
Download your favourite 9.0 ROM:
crDroid for example: https://androidfilehost.com/?w=files&flid=262369
Install GAPPS (only pico):
http://opengapps.org/
After you have downloaded all the files rom gapps cm13 patch etc. Make sure to flash each of the zip files one by one:
1) Flash ROM
2)Flash Pico Gapps
3)Flash CM13 Patch here
So basically, just head over to https://download.lineageos.org/find7 and download the latest Lineage OS 16 ROM. Then download the MindTheGapps (since pico OpenGapps can't work) from https://androidfilehost.com/?w=files&flid=170282 make sure to get 9.0.0arm.
Reboot to recovery, wipe the dalvik, system and cache. Then proceed with installing the the LOS 16 ROM. After that, you can flash the CM 13 patch and the gapps (MindTheGapps). It's ok to do gapps first before the CM 13 patch. I noticed that it makes no difference. Works the same every time.
Well, that's about it, reboot and enjoy. OTA should work after this. I think.
Good luck.
Then, simply clear cache and boot to your 9.0 OS. P.S don't forget to restore your data that you deleted in step one.
Optional: If you want to go back to Color OS or you have hard-bricked your OPPO Find 7(A/S) this tool will help you get back to stock firmware.
STOCK FIRMWARE (LVM)
Here are the instructions to unbrick your phone:
This is going to be a step by step guide on how to unbrick your OPPO FIND 7 (A/S)
Before attempting this guide, Windows is needed to be in "Test Mode".
To do this:
1) Open CMD with admin rights, and type "bcdedit /set testsigning on" without the colons.
2) Restart your computer.
End result:
This will check if this guide is applicable.
Note: Make sure your device has at least 70% battery. Charge it for an hour or so if you are not sure about the amount of battery left.
Note 2: I'll assume you are an admin of the computer you are using.
1) Disconnect your device from your charger/computer, etc.
2) Take out the battery and wait for 5 seconds.
3) Put the battery back in, hold the Power+Volume Up buttons and plug it into the computer.
4) Release your hands, and go to Device Manager. (How to go to device manager below)
1. Click the start menu
2. Right click Computer (Right hand side)
3. Click Properties
4. On the left hand side, click on Device Manager
5) Under Ports, you'll see either QHSUSB_BULK or Qualcomm *blah blah blah* 9006/9008
If you don't see any of the three, you're doing it wrong (Probably).
If you're not seeing it, try connecting your device without the battery.
Next, we uninstall the drivers. Simple enough.
WARNING: This part is only for people seeing Qualcomm 9006/9008 in Device Manager.
1) Uninstall the driver. (Right click your device, then click Uninstall. If prompted, delete driver software too)
2) Unplug your device.
3) Take out the battery and wait for 5 seconds.
4) Put the battery back in, hold the Power+Volume Up buttons and plug it into the computer.
5) Release your hands, and go to Device Manager.
You should see QHSUSB_BULK, if not, you might be doing it wrong.
Now we install the proper drivers.
NOTE: You should be seeing QHSUSB_BULK in your Device Manager, if not you're doing it wrong.
1) Download the Find 5 Drivers and unzip the file anywhere.
2) Right click on your device showing QHSUSB_BULK and click on Update Driver Software.
3) Click on "Browse my computer for driver software", and select the folder in which you extracted the drivers to.
4) It will install automagically. If prompted, click on Install the driver anyway.
After installing, your device should say Qualcomm *blah blah blah* 9006/9008.
The moment all of you have been waiting for. Unbrick!
NOTE: Your device should be connected at all times.
1) Download the tool that will save you below.
2) Extract the contents from the zip file.
3) Open the .exe file with admin rights.
4) There should be a line that is visibly different from others.
5) If there is, click start and wait till that line turns green. (It takes a few minutes. Generally nothing should go wrong at this stage.) If there isn't, you're doing it wrong.
6) After the line turns green, unplug your device and hold the power button until you see the Oppo logo.
7) If all goes well, you should be booted to ColourOS v1.2.5i.
If everything went through smoothly, you should be unbricked and ready to brick your device again.
Special thanks to:
@tashimotor https://forum.xda-developers.com/showpost.php?p=64149659&postcount=3
@Manas1796 thread: https://forum.xda-developers.com/find-7/general/7-dead-development-oppo-7-terminated-t3764649
@crdroid
@ akmlfhm https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802
@play8oy
A very helpful thread, my friend! Thanks for keeping us up to date that this is possible!
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
5ufy9n said:
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
Click to expand...
Click to collapse
Sure, I will let you know once I upload the file to Google Drive. :fingers-crossed:
Nice... looking this step... because last i try switch lvm to chns unified.. got bricked
So my question is ....
1. Support for find7 with this model X9076? Because the file download is X9077
2. What windows u running when u doing this?
3. Is possible support for windows 10.1 64 bit?
4. any suggest what custom rom ?
Cant wait u reply.....
Tq....
itmdn said:
Nice... looking this step... because last i try switch lvm to chns unified.. got bricked
So my question is ....
1. Support for find7 with this model X9076? Because the file download is X9077
2. What windows u running when u doing this?
3. Is possible support for windows 10.1 64 bit?
4. any suggest what custom rom ?
Cant wait u reply.....
Tq....
Click to expand...
Click to collapse
Sorry for the late reply,
Don't worry, I will upload the tool also that I managed to download when oppo forums was running and luckily saved that on my hard drive :') so if you do brick your phone, the software will put you back to default X9076 color OS software mode so you're safe.
1. This guide is for Oppo Find 7s. The 8.1 android OS does not recognise X9076 (LVM) and shows "encryption unsuccessful" whenever you boot into the OS. However, when your phone shows X9077 (Chinese unified method) the 8.1 recognises and lets you boot successfully. I'm not quite sure why OPPO had to make this sooooo confusing. Lol.
2. I am running the latest Windows 10 Anniversary Update.
3. I'm not sure what you're asking ? It does not matter 32-bit or 64 bit
4. I'm literally running CrDroid and its amazing, the latest update just got out online check it out.
Let me know if you need further help.
brownboy1289 said:
Sorry for the late reply,
Don't worry, I will upload the tool also that I managed to download when oppo forums was running and luckily saved that on my hard drive :') so if you do brick your phone, the software will put you back to default X9076 color OS software mode so you're safe.
sorry, is this your mean u will upload the X9076_Android5.0_32G_20150520 version?
or you are saying that files at OP is working for X9076 and X9077 ?
sorry .... cant wait anymore ... really need switch from lvm to chns unified and taste the Android 8.1
tq
Click to expand...
Click to collapse
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
---------- Post added at 08:33 AM ---------- Previous post was at 07:56 AM ----------
itmdn said:
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
Click to expand...
Click to collapse
already solved.
first try ... got problem sdcard0 corrupt.
so i do this step, boot to twrp, flash removesetuplvm.zip - done
repeat again the guide at OP and now sdcard0 corrupted problem is gone.
now ... time for me taste android 8.1 and restore all my data
tq for this guide
itmdn said:
i success do it, but now i got new problem, at my storage sdcard0 corrupted, tried format still no luck.
any help or suggestion ?
tq
---------- Post added at 08:33 AM ---------- Previous post was at 07:56 AM ----------
already solved.
first try ... got problem sdcard0 corrupt.
so i do this step, boot to twrp, flash removesetuplvm.zip - done
repeat again the guide at OP and now sdcard0 corrupted problem is gone.
now ... time for me taste android 8.1 and restore all my data
tq for this guide
Click to expand...
Click to collapse
I'm glad that it is working for you. :fingers-crossed::good:
Let me know if you have any problems
Sorry for those waiting on the OPPO FIND 7a files, I have really slow upload speed.
5ufy9n said:
Glad to see a detailed method of Unification! Can't wait till you post one for the Find 7a
Click to expand...
Click to collapse
Up and running: https://drive.google.com/file/d/1h74LKVucM4RoBJ-Bsgkmzdavzn_MbtPY/view?usp=sharing
Can some post thread in this xda where is crdroid oreo discussion? Because i have strange problem with crdroid...
Tq
itmdn said:
Can some post thread in this xda where is crdroid oreo discussion? Because i have strange problem with crdroid...
Tq
Click to expand...
Click to collapse
What's the problem? I think they had a 7.1 forum but I'm not sure if it's closed
If 7.1 i think no connection on this 8.1 version, right? But if u dont mind i wanna ask if u have this issues.
My problem is weird ....
1. Press long at recent button will appear some apps that we have opened.. at the top have lock button, right? I already press that button become lock. But that make it permanent... in no time will be unlock.
2. Last night when i sleep i leave my phone idle with battery 100%, at morning i woke up and see my phone low batt with 13%. Weird draining battery so fast. Nothing running only some email and chat that i haven' t read. Maybe the notification light?
Tq.
itmdn said:
If 7.1 i think no connection on this 8.1 version, right? But if u dont mind i wanna ask if u have this issues.
My problem is weird ....
1. Press long at recent button will appear some apps that we have opened.. at the top have lock button, right? I already press that button become lock. But that make it permanent... in no time will be unlock.
2. Last night when i sleep i leave my phone idle with battery 100%, at morning i woke up and see my phone low batt with 13%. Weird draining battery so fast. Nothing running only some email and chat that i haven' t read. Maybe the notification light?
Tq.
Click to expand...
Click to collapse
The first problem I'm not sure lol ?
The second problem is maybe most likely of background apps turn off any background apps that might be running i.e apps that run constantly Facebook Instagram others. One recommendation to turn off Wifi and mobile data so there is no data incoming/outgoing when you go bed.
brownboy1289 said:
The first problem I'm not sure lol ?
The second problem is maybe most likely of background apps turn off any background apps that might be running i.e apps that run constantly Facebook Instagram others. One recommendation to turn off Wifi and mobile data so there is no data incoming/outgoing when you go bed.
Click to expand...
Click to collapse
Maybe my english bad hehehehhe
I already attach the pic for first problem....
I cant make it stick locked ... in some how it will unlock itself... weird...
Also i cant play Mobile Legends anymore always force-close lol
Tq
That,s weird battery usage. When I leave a 100% battery at night, next morning ( about 8 hours) I have about 90+% left, and I leave WiFi and mobile data on all night. Though I use Servicely and Project Skynet Raising.
itmdn said:
Maybe my english bad hehehehhe
I already attach the pic for first problem....
I cant make it stick locked ... in some how it will unlock itself... weird...
Also i cant play Mobile Legends anymore always force-close lol
Tq
Click to expand...
Click to collapse
This is a strange problem I'm not quite sure how to help... sorry
Omg so frustrating ..... battery really draining... lol. In 1 day i can charge 3x .... any suggest official custom rom with android 8.1 for find 7s?
Tq
itmdn said:
Omg so frustrating ..... battery really draining... lol. In 1 day i can charge 3x .... any suggest official custom rom with android 8.1 for find 7s?
Tq
Click to expand...
Click to collapse
Best advice would be to reflash the ROM with pico gapps or at last change to another 8.1 ROM i.e lineage rom or omni 8.0

Zenwatch (WI500Q) firmware needed...

Hey all.
It seems like this section of the forum hasn't seen any visitors for some time, not surprising given the age of the original Zenwatch. However, I am posting this on the slim chance that someone with one of these watches might see it and help a brother out.
My Zenwatch was bricked years ago following a corrupted OTA update, and hasn't seen the light of day since. Recently though I found the watch, charged it up, and gave it another go. The stock firmware was still crashing constantly leaving the watch unusable, but I managed to install the Asteroid OS on the watch and now it works, albeit in a very limited fashion compared to the official software.
Now that I know that the watch itself is OK, and it just needs the stock firmware to be installed, I turn to you. Asus were unable to help me, as they no longer have access to the original firmware (or more likely, they're unwilling to share them with an end user), I am hoping that someone on this forum still possesses one of these watches and can create and share a backup of the OS, as it now appears that this is pretty much my last chance of getting my watch working properly again.
So, any retro watch owners left in this corner of the t'interweb?
Hi! I have this watch with stock firmware. Tell how to do the backup or send manual and I'll do it.
{
"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"
}
helloworld1337 you might be about to make a lot of people very happy!
I'm not sure how to extract the firmware from the watch, I'll have to do a little research in to that, but I don't think it's a particularly complicated procedure. Give me a little time and I'll get back to you as soon as I can.
Thanks again!
OK, I think I understand how to do this now, but as with any image copying / rooting process, only proceed if you are happy to do so, there is always the slim chance that rooting a watch can have undesired effects, but mine rooted without any issues. So, here we go...
Files that you will need...
KingRoot - https://kingroot-pc.en.uptodown.com/windows/download
ADB & Fastboot - https://developer.android.com/studio/releases/platform-tools
ADB Explorer - Can be found in the Microsoft Store. It only gets a 1* rating but we only need it to look for files and delete created images once we're done with them.
Next, connect your watch to your PC via the charging dock and a suitable USB cable. Now comes the technical stuff which I hope I have understood correctly...
1) Enable developer mode on your Zen watch. You do this by going to settings/about and tapping on the version number 7 times. This should enable the developer options, one of which should be to enable USB debugging (I can't tell exactly where this option is as my watch is running Asteroid OS, but it should be in there somewhere).
2) Extract the ADB tools to a known folder. Open a command prompt in that folder. Type the command "Fastboot oem unlock". This should unlock the bootloader on your watch.
3) Install and run KingRoot, this will root your watch granting you access to all the files on it. Again, this step is done at your own risk, I did it with mine and it worked perfectly, but it would be remiss of me to not give a warning at least. It takes a little while to complete so be patient.
4) Open ADB Explorer and hopefully your watch will be listed in the left-hand panel in the devices list. If it is, click on it and then click the browse button, this should display all of the accessible directories. In my case I see "Internal storage" and "Root", open "Root".
5) At this point we are looking for a folder that contains all of the partitions listed by name. On my watch it is in /dev/disk/by-partlabel, but again, I'm running Asteroid OS. Another possibility is /dev/block/platform/dw_mmc/by-name, but have a browse around the dev folder and subfolders, somewhere in there should be folder with lots of files, some named "boot" "recovery" and "system". Make a note of the path to these files.
6) In the command prompt type "ADB shell", the cursor should change to a # symbol (the first time you do this, type "mkdir images", this will create an images folder on your watch that'll just make things a little easier to navigate in the next steps, you only have to run this command once).
7) Type "dd if=/dev/disk/by-partlabel/boot of=/images/boot.img" but change the "/dev/disk/by-partlabel/boot" to match the path that you found on your watch earlier. If successful this will create a "boot.img" file in the /images/ directory. This can take a while depending on the size of the partition, just give it some time and it will eventually go back to the # prompt (boot and recovery are about 16mb, system is about 500mb so takes longer).
8) Type "Exit" which should return you to a normal command prompt. Now type "ADB pull /images/boot.img", this will copy the boot.img file to your PC (into the same folder as the ADB command file).
9) Use the ADB Explorer program to go to the /images/ folder on your watch and delete the boot.img file, it'll just free up space for more images.
10) Repeat steps 6-9 for the "recovery" and "system" partitions, naming the created image files recovery.img and system.img respectively. Don't forget to delete them off your watch after you have copied them to your PC as the system one takes up quite a bit of space.
11) Take the three image files (boot.img, recovery.img and system.img) and upload them to a sharing site of your choice, then let me know the links to them.
I have tested the above steps with my Zenwatch and have successfully extracted and then re-flashed the images. With luck, and the images you produce, this will allow me to re-flash my watch back to factory standard, then I'll see if there's somewhere where I can host them permanently for anyone else that may need them, as I suspect that I am not the only one looking for them.
Fingers crossed!
Hi!
I got problems with ROOTing.
Tried Kingroot, kingoroot - failed at exploiting. Also looked for TWRP, but all links dead.
ED: Failed means that process went to the end without results.
Yeah I've not been able to find TWRP anywhere either. It's gone midnight now and I'm turning in but I'll see what I can find tomorrow. Bear with me, we're almost there.
Just to check, have you done these steps?
On your watch, head to Menu->Settings->About and tap on Build number for 7-8 times until it says you are a developer. When it does, the developer menu should be unlocked on your watch.
Head to Menu->Settings->Developer options and enable ADB debugging. Without this, your computer will not be able to communicate with your watch.
Yeah sure. I also went to the fastboot mode by swiping from right top corner to left bottom at boot, or sth like that and enabled bootloader by oem unlock. Kingroot has problem with rooting because device is unsupported. It tries many root strategies but all of them are unsuccessfull. It's Marshmallow 6.0.1 - m1d65s build.
We could try Kingo Root, an ironically close name to the other app, but beggars can't be choosers at the moment.
Kingo Root, the king root android app for free.
Kingo Root is #1 one click root solution so easy to use. Take your android phone by your control! You will love this feeling - the freedom.
www.kingoapp.com
I tried it on my watch and phone but they're already rooted so the process didn't succeed (obviously), but it could be worth a try.
As I mentioned before I tried both with no success.
Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.
As I mentioned before I tried both with no success.
Click to expand...
Click to collapse
Ah, that's my bad, I misread your reply, I didn't realise that you had already tried that one.
Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.
Click to expand...
Click to collapse
Damn man, that is exceedingly generous of you! If you're sure that you're happy to do that then I am more than willing to cover the cost of postage. I'll PM you my details and we can get something arranged, you are an absolute legend sir.
Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.
helloworld1337 said:
Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.
Click to expand...
Click to collapse
I absolutely will do that, and thank you again, in these days of doom and gloom you have absolutely rekindled my faith in humanity .
For anyone following this thread, the stock firmware files are now available HERE.
Howdy! Nice to see you done the work
BR
helloworld1337 said:
Howdy! Nice to see you done the work
BR
Click to expand...
Click to collapse
Hi BR.
Yup, I eventually managed to work out a somewhat unconventional way to access the storage on the watch, something which I would not have been able to do without your generous donation. I also apologise for not letting you know that it arrived safely, that was an oversight on my part I think caused in part by the dejection that set in from repeatedly failing to root the damn thing .
However, between us we have succeeded in creating the firmware files, and are now able to offer them up to anyone that needs them. I'd call that a job well done .

Categories

Resources