@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?
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.
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
What error show miflash when you try to flash in edl mode?
balannaer said:
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
Click to expand...
Click to collapse
take your sd card off your phone i had similar issues and fixed them that way
ccalixtro said:
What error show miflash when you try to flash in edl mode?
Click to expand...
Click to collapse
it depends on which version of the flash tool is used. the beta version of the flash tool claims that it is successful, but the phone will not load to the Android OS after that is completed and it still will not load into the recovery mode to attempt to factory reset or anything else.
other versions have given errors:
miflash 2017.7.20.0 gives the response after attempting for about 10 seconds of "ACK count don't match!"
miflash 2018.11.15.0 gives the error response of "cannot receive hello packet"
and as stated before the miflash beta goes through the complete flash process with the result stating a "success" response, but the phone will not load to OS, just remains stuck on the MI logo screen when the phone is booting up
i have some screen grabs of all this but i am not yet worthy through XDA to be permitted to share them
thanks for the reply
kuartito said:
take your sd card off your phone i had similar issues and fixed them that way
Click to expand...
Click to collapse
i dismantled the phone manually bro, when you use EDL mode this way the SIM/SD tray is removed you then remove the entire backplate and then disconnect the battery cable from the circuit board and you use the test point method to short two pins that force the system to start in EDL mode when you connect the usb-C cable, so unfortunately that is not the issue :crying:
it never seems to be the simple solutions
Thanks for the reply!
Still dead in the water on this one.
Going to look into getting a replacement, that is a disappointing end to the Xiaomi experience
Facing similar issue. Am able to flash however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Hi.
To start off, I'd like to say im no expert with phones, I had phones mostly to call, watch videos and listen to music, and this is my first attempt at doing all the stuff I will be describing now.
From the beginning:
I bought a seller refurbished LG G2, which worked fine when I received it, I had to do some updates which my phone found automatically, and it ended at OS version 4.4.2.
I wanted to finally have a decent but cheap phone, however it couldn't play some games I wanted to play and thought "Maybe if I update OS to something new, it will work, and it looks better"
Here my journey to update the phone to Android 11 started.
I was looking at many different videos and guide and everything, how to root, first time I rooted was by accident, only later a better video instructed me how to do it properly, then I installed the trww or whatever its called. then it didnt work properly after using that recovery to install android 11, so I had to flash it to some old version I found for my device (My version is LG D802 btw). For some reason it now had only 11gb of space, instead of 32gb. Anyway, I tried installing root and twrw thing again. After getting root and the recovery program I clicked reboot in its options and now my phone is having an issue.
First off, I left it to charge over 9 hours. If its NOT connected via usb it does nothing, power button, volume buttons do nothing.
I tried connecting it to my phone to flash it, but nope, after few seconds it says my phone disconnected from the usb and try again, even tho it is connected and I can see in device manager that it's seen by my PC. Now, I tried to enter the download mode manually, and it worked.
It says that it's rooted and B0 above it (this number was going down over different roots, twrw installs and flashes and such, no idea what it is.
I tried to flash it again since Im in download mod, however now the main issue appeared. It goes well for 40% of the flash using the LG flash tool 2014, I can see the progress in the download mode on the phone's screen, however once it reaches that certain point it just resets and the program treats it as disconnected.
Now when I have the phone connected via usb it just flashes red between 1 and 3 times, LG logo shows up for several seconds, then it turns off, and repeats the whole process.
During the flashing, software instructed me to remove the batter and try again, so I looked up how to remove it, did it, put everything back together, and its still the same.
Please tell me what to do, I've already spent over 10 hours trying to fix it and I just bought this phone...
hi... if your phone flashes LG logo - i'd recommend a full TOT flash of the original Lollipop image as a starting point...
just make sure you download a proper TOT file for your d802 device (32gb model)...
you'll end up with a working stock Lollipop rom which you can later root and flash a custom rom (i.e. Lineage 18)
Stock TOT file is usually about 2.6-2.7GB in size (at least for my 16gb model)
this youtube video shows how to do it and what is required for the process...
i think there is also an older thread here on XDA on how to TOT flash a G2 device (try to search it)
Hello!
I recently got my hands on a Nokia Lumia 520 for tinkering with. Its running on really old firmware, and I figured before I try anything weird, I'd mess around with it in its stock state. Thus, I tried updating the firmware.
The internal updater returned an error, stating that it could not contact the server for whatever reason. I figured this is most likely due to the Windows phone being discontinued, so I scoured the internet for firmware files. I eventually stumbled upon a YouTube guide that linked to a guide on Microsoft's Own guides page. It explained how to reinstall the firmware to a stock state. Desperate for progression. I gave it a shot.
The guide provided the "windows Device recovery tool", Which I would install on my windows 11 machine. I then proceeded to run the software and plug in the phone. HURRAY! It was able to tell me exactly what type of phone it was. Clicking the option to proceed, I was shown a screen explaining just how dated my firmware was. Suggesting It would fetch newer if not the latest firmware for me. I clicked on install and it started downloading.
I waited patiently for the software to download the firmware. After which it went to the installation screen. It then attempted to put the phone in flashing mode. Explaining that in this mode, the phone would restart, then have a blank screen. Instead what happened was that the system restarted normally, asking me to unlock the device. I wondered if maybe I had been impatient, so I waited for another while. The phone restarted again, still on the normal lock-screen. This happened another two times before the Recovery tool gave up and told me it had failed.
My question: Is there any reason why it would do this? Are there any methods to get it into flash mode?
I would hate to discard the potential of this device simply due to the inability to flash it. And I really hope it can be helped. Please let me know if there's anything else I should share about this. I'll happily take any help I can get!
Thanks in advance!
Edit, after a lot of trial and error, I managed to force it into flashing mode. Turns out the guides I followed missed a step. Pressing the Power and Camera buttons did the trick