Related
@MikeChannon removed OP. please close
what? lol
Yeeha! You are the magic man....
workdowg said:
Yeeha! You are the magic man....
Click to expand...
Click to collapse
He truly IS the man. Helped me out BIG style.
ionioni said:
READ CAREFULLY AND BE WARNED BEFORE ANYTHING:
THIS CAN HARD-BRICK YOUR DEVICE AND I TAKE NO RESPONSIBILITY FOR THAT!
use it only if you must or not at all
you can read this for some details about what bricks are so you understand what you can get into
this is for all Yoga Tab 2 models 830, 1050, 1380 (regardless of the submodel F,L,LC)
it restores(downgrades) your bios firmware from whatever Lollipop version to the original/genuine one from the latest KitKat stock rom released by Lenovo (and all the latest KitKat stock rom's have 150422 in the rom filename, ie April 15, 2015 and nothing not even minor OTA's were released after this date for KitKat, next ones upgraded KitKat to Lollipop)
useful to:
1. those who want to return back to the KitKat stock rom from Lollipop (if you simply flash back the KitKat stock rom files and you are still on Lollipop bios firmware you will softbrick as the Lollipop bios is a x64 version while the KitKat loader/kernel are ia32 so you will get stuck at efi shells, bios screen etc)
2. those who took the Lollipop OTA, succeded, but had in time problems (bricked their device) and cannot flash a Lollipop stock rom as they don't have one (not being released by Lenovo/available yet and at least some 830 and 1380 models are in this situation), so they must flash back KitKat stock rom and after take the OTA to Lollipop (and the KitKat flashing part put's them in the same situation as those from p1.)
3. those who tried to take the Lollipop OTA and had problems and they tried to flash KitKat stock rom and yet they are failing (this could be due to problems in the updating while OTA was applied, yet could be that their bios firmware was updated to Lollipop version)
4. those who want to test stuff (going down/up between versions) ... you name it...
how to use it:
1. first download and extract the corresponding tool for your device (830 and 1050 models share the same bios firmware so they have a common tool), while at this you can watch the little attached recording i made with the tool restoring the bios for my 1380F tab so you know what to expect when you run it. USE THE TOOL THAT MATCHES/CORRESPONDS TO YOUR MODEL, you can hard-brick if for eg you use the 1380 one on a 1050 model (didn't even tried but nothing good can happen)
2. place your tab in the DnX mode: power off (by force if you have to), press and hold both VolUp and VolDown butons, keep them pressed, now press Pwr to start and release Pwr when it turns on/buzz (but keep holding pressed Vol buttons), in a few seconds your screen will display "Fastboot starting..." and it will hold on that, now you can release the Vols (you are in DnX mode). you must get that message, try again the whole sequence until you succed, don't move on until you have that "Fastboot starting..." on your screen.
3. run the tool (you must have the intel drivers installed, if you flashed to your tab at some point you should have them already), follow the messages i think it's quite easy and straightforward, in a few minutes you will be done and having a brand new kKitKat bios firmware on your tab
(3) if while running it hangs on the "Preparing to push files..." message, and your tab starts to the whatever error message you had before it means that you already have a KitKat bios (the tool works only with the Lollipop bios firmware) so you don't need to restore the bios, you can flash stock KitKat rom directly (in this scenario the tool doesn't modify anything on your tab)
4. when it finishes the tool will automatically reboot your tablet, leave it for a few seconds to start (it will most likely go ninto some efi shell, or bios screen whatever your old files were) afterwards turn it off (long press Pwr) and that's it
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
i must warn you again, while i tested this tool (i think i moved from KitKat to Lollipop and back at least 20 times and never had any issue with it) you are the only responsible if something bad could happen, this is playing with bios (and any mistake will hard-brick your tab so you will have to send it to a service for fixing). make sure you have enough battery (while i used the tool even when i was with 5% on my battery i would not recommend, i say at least a 30-40%, the process runs only for 2-3 minutes so that should not be an issue). and of course once it started the flashing DO NOT EVEN THINK OF INTERRUPTING! (you could close other software on your PC that maybe can hang your computer while flashing.. you got the point)
Good Luck!
edit: i already have messages about successful bios restoring (as expected no? ) but failing on completing the OTA to Lollipop update after flashing anew the KitKat stock rom. to them and to all of you people who are going to Lollipop from your newly flashed stock KitKat: SET YOUR COUNTRY CODE!!! after you flash back stock kitkaton the first boot input ####6020# in your contacts and a dialog will pop from which you MUST choose a country (no matter which one, preferably yours or a close one), then after the tab reboots for updating the region and comes back to Android check that you have a country code set by entering #### 59930# and it should show the code you chosed. if you take the OTA without a country set you will FAIL! if you failed on your OTA to Lollipop flash anew the stock KitKat rom and set the country code
also do not take an OTA if your device is rooted, always UNROOT first then take the update, and you can root back after or just don't root until you finished the whole Android installing and OTA updates
Click to expand...
Click to collapse
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Works perfect! Thanks!
daWyrd1 said:
thank you! i had the boot to bios problem after trying some not-smart things. after spending an hour on the phone with lenovo this morning getting a repair authorization, i printed out the label. i don't need to send in my 1380f now.
your app fixed that and i was able to flash to kitkat and then upgrade to lollipop.
Click to expand...
Click to collapse
yeah... the guys at Lenovo deserve a break, they have such a beautiful daadeedaadoo sound on the boot animation (that one cannot even disable it )
bisti2004 said:
Works perfect! Thanks!
Click to expand...
Click to collapse
Pentru putin
Mersi Dorin!
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
aerofisher said:
My 1050F cannot boot for long time, I posted the problem(http://forum.xda-developers.com/thinkpad-tablet/general/help-1050f-dead-t3188696) but no one answered me. Today I was very excited to find this post and read it carefully, then tried to do it. But just after the sending progress started (the "xx%" progress began)for about 10 seconds, the program "restore-kitkat-bios-830_1050" vanished(Maybe forced teminated by Windows? I ran the "restore-kitkat-bios-830_1050" after a new reboot of Windows). I waited for about 3 minutes, the "restore-kitkat-bios-830_1050" program still didn't appear, and the tab hanging on a normal picture ( I don't remember, probably a recovery stage picture? but I remember the last line is "the result is Okay"). So I had to disconnct the tab from the computer, and powered it off. Then I try to power it on, but sadly find it cannot boot to any screen. In a dark room, I find the backlight of the tab is on when I pressed the power button, but there is no text or picture on it, regardless of whether I press the power button independently, or press the power button together with any volume button(s).
Now the tablet seemingly has changed into a REAL brick (or hardware brick?). How can I rescue it? The only way is to send it to a service?
Click to expand...
Click to collapse
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
ionioni said:
i've seen the post with the problem you had, now the thing is on a "normal" bricked tablet (meaning soft bricked one) your tab never hangs at the screen to which you're referring to (Powered by Android) it will always move on (to some error message, bios etc). the same tool was used by me and others (including for your 1050F model last one I recall is @Einwood) and never had issues (until now) so imo it's very unlikely that the problem was from the tool (it's task is quite simple and don;t see what could go wrong) something interrupted the flashing process. also you said you tried both lollipop and kiktkat rom flashing and failed and at least one of them should have worked (the roms are flashed using bios dnx as start) so the issues are with your tab hardware most likely.
but all that is irrelevant now... if it doesn't boot at all and you cannot get it to show ANY message at all (white Lenovo logo doesn't show up when you power on nor does it buzz when pwr on) then service is the only solution
@ The Others: please post your tab model too when posting
Click to expand...
Click to collapse
aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
aerofisher said:
Thank you so much for such detailed analysis, but I cannot figure out why the hardware has problem. Yes, now it cannot show ANYTHING, white Lenovo logo doesn't show up nor does it buzz when pwr on. Anyway, I think I have no choice except the official repairment now.
I'm trying to find the LENOVO service sites in Canada, but their Canada official site has no such information, on the contrast, its website is full of sale/order/payment information. I think I should re-think about this company.
Thank you again for the reply.
Click to expand...
Click to collapse
http://bfy.tw/2gNc (just having fun) it is the one that says phone support.
ionioni said:
sorry about your issue, yet repairing should not take long, maybe @workdowg can guide you more as it had a similar problem and was solved very fast (6 days if i recall) sending through fedex on lenovo's expenses.
Click to expand...
Click to collapse
Yes, once i talked to them (about 5 minutes) they emailed me all i needed and i just had to find a local fedex dropoff center. They boxed it and i got it back in 6 days.... this seems to be a common thing for them....
Sent from my YOGA Tablet 2-1050F using Tapatalk
Yoga Tab 2 (830, 1050, 1380) - get back to KitKat
You are my lifesaver and I just can not thank you enough @ionioni
how can you make a file like restore-kitkat-bios-1380.zip ??!! you are such a genius !! :good:
We will never be able to flash it back to KitKat Bios without this zip file !! :crying:
But why don't we need to flash it back to Kitkat Bios on my Samsung Note 3, S5, Note 10.1 (2014 version) and Nexus 9 ?!!
thank you very much for your hard work again and keep up the good work pls
this was on my inbox and it should continue publicly maybe others can benefit
KainXSS said:
I'm wondering what your flashing to the tablet with your tool, I have a Lenovo S8-50F and lollipop is pretty abysmal on it, so I'm wondering what your flashing to downgrade the bios so I can try it on the S8, since its very very similar to the 830.
Click to expand...
Click to collapse
you should NOT use the tool unless it is made exactly for your model, or you most likely will hard-brick. moreover Lenovo uses an in-cpu module for digitally checking the authenticity of the firmware you have on your board at pwr on time and even if you have a bios that would work on your model if it is signed with another key it will cause a hard-brick (the measured boot module will refuse to load the IBB in the new bios).
for eg if one writes the 1051 windows variant of bios on the 1050 android one (they are identical in hardware) it hard-bricks (tested).
send me a link to the latest KK stock rom for your device and i will check on it.
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
bombolota1 said:
That is what happend to me. My loved 1380f is hard-bricked. Only the white lamp is blinking and it doesn't turn on anymore.
Is there a possibility to repair it or can i throw it in the garbage? Please give me an advice. Thank you very much.
Click to expand...
Click to collapse
not so much you can do, the hardware is fine, it just got the wrong firmware in it... somehow you must rewrite the bios but you cannot do that from the outside (ie by software means) without being able to boot at least in DnX mode. you can check quickly ... if after you PwrOn (well.. after you long press Pwr button as at this moment Powered On of Off are werid concepts ) you don't get NOTHING on your display (ye not even the Lenovo -> Powered by Android white/black logo) than that's it (try maybe to see if somehow DnX didn't got hooked by entering a fastboot devices and see if by some miraccle you don't see your device there)
your device must be opened by a repairing service tech (especially if he is on warranty), you could do it yourself (i did) but you need the appropiate tools and know/how otherwise from a hard-bricked yet recoverable (the hardware is ok) you will transform it into just a paper holder
updated kitkat bios restore tool to version 2 (foolproof version). read the main thread post at the beginning.
Good morning.
Please let me introduce my situation. I use Lenovo Yoga tablet 2 Pro. On 9-th of november I updated Android to 5.0.1. Unfortunately, one of my commercial aps now can not make a connection with external device (no appropriate information about USB connection is appeared).
I am affraid the problem lies on the Android 5.0.1 system. Before that everything had worked perfect.
That is way I decided to downgrade to the Androix 4.x.
I found above treads, but have some doubts.
Is above tool downgrade my system to Android 4.x or do I need to do some additional operations, to get back to the Android 4.x?
In the section - how to use it (point 5) we can read:
5. you can now start in DnX mode again and flash your stock KitKat rom (this step is quite known by now so i won't detail it, there's a lot of info on that in other threads), take OTA's, eat candies... whatever you like
Click to expand...
Click to collapse
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
pawlikp100 said:
In the section - how to use it (point 5) we can read:
Can you give me some more detalis (links about that?)
Kind regards from Poland
Pietia.
Click to expand...
Click to collapse
you must:
1. Downgrade the bios using the restoring tool (you mention "Yoga Tab 2 Pro" so you must use the 1380 version), and you must do that so you can flash KitKat stock rom on your tablet (if you try to flash directly, without the bios downgrade it will fail and you will soft-brick your tablet)
2. After restoring the bios, download from here your stock KitKat rom and extract
3. Flash using Intel Phone Flash Tool (open with it the "flash.xml" from the target_bin directory of the extracted archive). the Intel Tool can be found in the tools directory of the same extracted archive.
4. After you finished sotck KitKat flashing, remember to set your contry code (####6020# in Contacts), also it's not necessary to make your settings wifi etc before you set your country code as they will anyway going to be deleted (a factory reset is performed on country code setting operation). if you don't set a country code you will fail when upgrading to Lollipop.
5. Update using the Lollipop OTA or stay on KitKat
Thank you for explanation.
I download system, installed Phone Flash Tool, open it and chose flash.xml, but after connecting my YT2Pro I can not see device specific with "Start to flash" button in the Device list area of the program.
see below screen. Is this screen looks as it should? (ups, unfortunately I can not post images, because I am new user).
One more thing, tablet should be turned off during flashing?
Right now my tablet is connected to the laptop by USB. It is not switched off and charging is in progress (laptop does not see my tablet as an additional disc/device).
Is above status correct?
I ve been trying to unbrick my asus zf2, i used xfstk and everything seem to work well untill the download os and everything was completed ( in xfstk ), the problem is that after the xfstk process is done the zenfone always shows the 4 colored screen , but it doenst fastboot it just shows that irritating battery logo with question mark in it.
Tried charging phones for hours, even a full night but nothing , even tried doing everything over and over again..
ALL DRIVERS ARE WELL INSTALLED THO and
FORGIVE MY BAD ENGLISH.
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
easyxx said:
Hello,
i have a problem with my 1 week old yotaphone and hope you guys can help me to solve.
Let me say, this is my first android device. After a long time using iphones i saw this 2-displays concept and wanted to give it a try.
But now my problem and the way to:
The phone was brand new and first of all i charged it for a wohle night.
After that i put in the sim-card and started the phone and walked through the start-procedure with WLAN, Googleaccount etc.
Then the phone told me about an update and i started it over WLAN.
The phone was downloading, rebooting and shows me a white window "updating x of 127(?) Apps".
Somewhere in the middel the phone rebooted again and now its in a bootloop.
What is possible with the phone right now.
I can start the phone wit the bootloop (powerred byAndroid, then restart)
I can use "Power + Vol-" to bring it into downloading mode
When i use "Power + Vol+" nothing happend.
When i use "Vol+ + Vol-" nothing happend.
The akku of the phone is empty now and it only works with usb or power unit connected.
In bootloop or downloading mode it is not charging.
What i tried.
What i try:
I read many topics with bricked / bootlooped yotphones and how to flash or cache whipping.
i connected the phone to my pc and used yotoflasher with many different firmwares.
I used fastboot:
- flashed the system.ing with differnet sizes.
- tried different custom recovery.img from different threads here and from other sites.
Even a complete new image, moddified RU img doesn`t help.
The phone stays in bootloop.
Yes, it`s a warranty case, but before i start to strech my nerves by handling with the dealer and shipping
this phone back to china i will try everything else and hope you can help me out of this situation.
Thanks a lot
Click to expand...
Click to collapse
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
kophyo07 said:
Mine too,stuck in bootloop. I also tried the fastboot and it said waiting device.
Click to expand...
Click to collapse
If your phone displays Downloading... and fastboot keeps saying waiting for device then there is something wrong with the installed ADB driver. Check some of the posts in this forum like this one on how to fix this. http://forum.xda-developers.com/yotaphone-one/help/yotaphone-2-yd-206-china-flash-firmware-t3306797/post69311402#post69311402
Strange that you had an OTA (Over The Air update). You didn't do anything between the SIM/Google registration and OTA ?
Normally there are no OTAs allowed on yd206 phones bought from China/HK , where did you buy it ? Chinese retailers have their own firmware that they put on phones , for me , maybe you had bad firmware installed.
The warranty of your phone is voided if you flash yotaphones bought from China and HK .
When you use yotaflasher do you get error message or "waiting for device" ?
To flash the Yotaphone , it should be in developer mode , but you couldn't put it in this mode because it first did the OTA that started your bootloop. Android apps are updated like that ("installing x of 127") when it gets updated to lollipop. Normally the OTA should have worked OK. Did you allow enough time at the Yotaphone logo after the first reboot ? It stays on this logo for 5 minutes before starting. I made this mistake.
The OTA started just after you set up Google etc ?
If so, normal yotaflashing will never work, but at least you havent broken the warranty . The thing we need to know is what exactly happened when you tried to flash , what errors messages appeared ?
If you did not put the phone in developer mode, then you cannot easily flash the phone, so your best possibility is to return the phone. Normally you can contact the seller by chat or email . Some are very good in exchanging.
It IS possible to flash your phone using fastboot, but I would not personally attempt it and you would lose your warranty . You need rootkits, SDK toolkits, universal drivers and images. Google "bootloop without USB debugging".
When I flashed my yd206 , (after many attempts) I flashed my yd206 to yd201 Russian KitKat ROM first and then did an OTA to lollipop.
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
metobayrak said:
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
Click to expand...
Click to collapse
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
brainvision said:
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
Click to expand...
Click to collapse
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
metobayrak said:
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
Click to expand...
Click to collapse
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
brainvision said:
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
Click to expand...
Click to collapse
I used this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i opened my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
metobayrak said:
I use this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i open my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
Click to expand...
Click to collapse
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
brainvision said:
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
Click to expand...
Click to collapse
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
metobayrak said:
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
Click to expand...
Click to collapse
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
brainvision said:
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
Click to expand...
Click to collapse
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
metobayrak said:
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
Click to expand...
Click to collapse
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
brainvision said:
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
Click to expand...
Click to collapse
Yes, because of the eMMC chip is damaged. But the crux of the problem is processor heats and cause of no proper heat dissipation this damages other chipsets. Thermal pad solution must be done after chip replacement.
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Is there anyone on the platform who knows on this issue?
Or it's just a platform of Ads?
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
found some fix on a russian website, gonna translate it:
im gonna make a warning there off-script of the russian website, this is NOT guaranteed to work. if it doesnt, send it off for repairs.
what do you need to do this:
1 - fully charge the phone
2 - a working usb cable
3 - a computer with wifi on it (i can tell you have it since you likely posted it on the computer)
4 -you should have Mi flash pro
5 - a recovery image on chinese (WARNING: 1.9 GB, BE PATIENT)
6 - actually working braincells and hands ( you guaranteedly have em)
THE STEPS:
1 - Load in mi flash pro and register in it under your name (not always under your name)
2 - press recovery
3 - you should see a lightning bolt icon along with the IMEI of your device
4 - type in the path of the firmware
even if your device shows your system has been destroyed you can still boot into recovery.
5 - in your device boot into recovery
6 - you see connect with mi assistant? choose that option and confirm it
your device should direct you to connect the usb from your computer to your device
7 - After you setup everything you should see your device, if not, press refresh device, then you should see the flash button, press it
8 - and there begins the magic - wait 5-10 mins for the firmware to initialise, DO NOT DISCONNECT THE USB FROM YOUR DEVICE AT THIS POINT, IF YOU DO, YOU WILL SCREW IT UP AND HAVE TO DO IT ALL OVER AGAIN!
if you dont screw up and your device actually boots congratualtions! the power of xi jing ping has restored your phone to normal with a small drawback - its all in chinese
worry not, it doesnt end here:
9 - Unlock the bootloader AKA Unlock OEM (This is important, because otherwise you will brick yourself again and will have to do it all over again)
10 - boot your device into fast boot and flash the global firmware onto your device (the global firmware can be found on the same xiaomiui website you got the chinese firmware from)
i hope this lengthy guide helps
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
crud, i forgot the critical part:
it doesnt boot you to the average xiaomi screen, its the A1 model
at this point you need to use the ADB to flash the chinese firmware and unlock the bootloader on the chinese firmware, then flash the global one
though you can still use the same method i typed above
How's the progress so far?
Lamntox said:
oooooof, sounds like a harsh brick from some sort of malware downloaded into the device or your kids diddled with some kernel settings somehow
is your device running on qualcomm snapdragon? i have the fix for it in this site
but first try the update option on the recovery, might fix something
Click to expand...
Click to collapse
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
arshad4u said:
I tried recovery also try to format the disc with recovery mode(power on + Volume up ) but then it stuck on the formatting disc... line
Click to expand...
Click to collapse
Yup, the device is probs bricked
Have you tried the other methods i described?
arshad4u said:
Hi All,
I'm new to this as I'm not an Android developer but a good Android user. Requesting moderator to update anything required.
I've Xiaomi mi A1 and it was working for the last 3 years. Last Sunday, it just got hanged while kids were playing with it(maybe multiple apps/videos/some ad clicked) and it got hanged.
I restarted and it stuck on "Android One" screen till now even after multiple attempts.
What I tried:
1. I tried to wipe/factory reset from the Android recovery option(power off + volume up) then it stuck there saying "Formatting data" and I've restarted it to come back to Android One screen after hours.
2. I tried using MiFlash tool and it continues throwing the error "remote device is locked. cannot erase".
Then I got to know bootloader must be unlocked. and for that:
1. I tried fast boot oem unlock but it just says OK and device reboots. When I check status back, it's again locked .
2.I tried to unlock it using MiFlashUnlock tool but it says not able to find account details as I may have logged in once but probably I may not have used Xiaomi as cloud instead I prefer Google cloud.
You can assume I'v already searched possibly all threads on the internet and added here all possible information.
Attached getvar-all.txt output
Click to expand...
Click to collapse
Hi i dont have that kind of a problem!
my problem is when i try to do oem unlock it says error 0x1002 and idk what to do (i have same phone btw) i tried anything but nothing works!