Related
I broke my phone (radio rom) while trying to flash my dear Samsung Omnia i900 using GrandPrix. The full story can be found here: http://forum.xda-developers.com/showthread.php?t=418917
Here is the latest help I receive from chaimd:
The other way, I found strings of "phone.bin" or "SD download Mode" in eboot.bin.
I think you can try below;
1. copy i900DXHG4_phone.bin into a microSD as "phone.bin"
2. set the microSD and power on your OMNIA
you can try with microSD format FAT16 or FAT32.
And perhaps, entering SD download Mode need some key combination with POWER key.
Good Luck
Click to expand...
Click to collapse
I will try this out. Does anyone know how to enter the SD download mode?
10x for this
i try format fat 32 sd card i copy phone.bin and try some key combinations my omnia power buton light blu green and red but noting.How to setup in menu my phone boot whit mmc?
this is help as?
To boot from a program, create a folder entitled "MCSTART" which contain a programme call "AUTORUN.EXE". When you insert card, windows will copy executable and launch it with parameter "install" (and when you remove it, windows relaunch app with "unsinstall parameter")
So maybe you can create an executable that launch ROM update
NO you do not need autorun, bootloader should exevute the flash from SD but i am unaware of the key combination
Bootloader
mr_tormoz said:
i try format fat 32 sd card i copy phone.bin and try some key combinations my omnia power buton light blu green and red but noting.How to setup in menu my phone boot whit mmc?
Click to expand...
Click to collapse
Me too, I tried to press alot of key combinations but no help at all.
I found out the SD Download Mode is actually one of the Bootloader mode. Therefore if you know how to enter Bootloader Mode then please share it here. Thanks.
binh said:
Me too, I tried to press alot of key combinations but no help at all.
I found out the SD Download Mode is actually one of the Bootloader mode. Therefore if you know how to enter Bootloader Mode then please share it here. Thanks.
Click to expand...
Click to collapse
Thats were there is a little problem in the Omnia the boot loader mode is automatic. When your device starts up and you see the Samsung Omnia logo this is bootloader mode. If no request is made to to the system to enter bootloader the normal startup proceeds. This is why when you flash from Grandprix you have to press detect first then restart. The detect sends a command to go into bootloader mode.
bobsbbq said:
Thats were there is a little problem in the Omnia the boot loader mode is automatic. When your device starts up and you see the Samsung Omnia logo this is bootloader mode. If no request is made to to the system to enter bootloader the normal startup proceeds. This is why when you flash from Grandprix you have to press detect first then restart. The detect sends a command to go into bootloader mode.
Click to expand...
Click to collapse
That's why I think the solution to Samsung Omnia i900 SD Download Mode is to find a program that will activate it from Windows.
Anyone have better idea?
hello
My omnia is 5 days in service center but not alive. any progress for repair the phone part ? i have 2 x i900 one is work and one only pda i try metod phone to phone but not work.
I have the same problem. I tried to download HH1 rom, i followed the steps and the procedure went successfuly with any error, screen say job done. then my phone wont power on again.
will the SD download mode work if the phone won't even turn on? how to make it turn on? how to use the SD download mode? can anybody give exactly direction? please help.
My omnia original english rom working if can help with something to ressurect yours tell me.
anybody have more details of i900 SD Download Mode and how to use it?
will it recover the bricked phone? my phone wont power on now.
So, does anyone have idea?
Hmmm. Yesterday I kill 2 pcs I900 Omnia with GrandPrix 1.8.1 trying to flash with HH1 version (only PDA part), but after that I flash them with old version (HG3), and everything looks ok. I think if You do not kill the boot sector, you should bring your phone to live. And one more. NEVER try to flash bootloader in phones like this, because there is no solution to restore it!! It's this same problem like qualcomm phone series. No TestPoint, no solution, at now.
how can you flash it again it the power cant turn on? the main problem now is the power cant turn on. any ideas?
prpetrov said:
My omnia original english rom working if can help with something to ressurect yours tell me.
Click to expand...
Click to collapse
Thanks prpetrov, your kind heart is really appreciated especially when someone like me really need help.
We, the people who has half-bricked phone (no phone function) really need to know how to enter the SD Download Mode with or without using software.
People on this forum make me feel really welcome. Thank you all.
samsung service center
binh said:
Thanks prpetrov, your kind heart is really appreciated especially when someone like me really need help.
We, the people who has half-bricked phone (no phone function) really need to know how to enter the SD Download Mode with or without using software.
People on this forum make me feel really welcome. Thank you all.
Click to expand...
Click to collapse
I think there is no solution to our bricked omnia's but to send them to Samsung Service centers. If warranty covers it, it will cost $150 or so for shipping. Losing $150 is better than $700. Once I get it fixed, I will sell mine and won't get it again. If a firmware update caused this issue, I cannot rely it as the device of my choice. I have not even used any tricky methods, just tried to update with its firmware and now in Monahan's. Sucks big time.
I contacted samsung US. they told me they will only support handsets manufactured in US. I also contacted samsung singapore,they told me that there is no warranty on exported handsets. warranty is only availiable to handsets purchased from local stored in asia countries. all handsets purchased online from europe, US, do not have warranty, so samsung will not support those.
I am so disappointed with samsung. there are people all round the world purchase products from ebay and online stores, samsung do not provide services for them. this is a big problem.
I will say, can we all complain to Samsung? may be see some light? may be i am too silly.... If we don't try... we do not know the answer; Right?
source : http://www.modaco.com/
OK, here is time for report what I've done so far.
Firstly, THERE IS a function to download from SD card, but at this moment, there is only 1 way to activate this function, have to be done through telnet from JTAG.
People have MONAHANS is problem with PDA bootloader (PXA312) , then PHONE problem is related to Qualcomm bootloader.
Secondly, there is some functions that I tried on PXA312
sys.cpu PXA310
sys.JtagClock 10MHz
sys.option WAITRESET On
sys.up
data.set 0x40e10414 %long 0x00001841
after this, it will bring you control of MONAHANS
Something important here:
d.s 0x4A00000C %l 0x00000638 ; MSC1 (Static Memory Control Register - SRAM/Async Flash memory)
d.s 0x4A0000A0 %l 0x00000002 ; CSMSADRCFG(CS Config Register)
d.s 0x4A000088 %l 0x0033C919 ; CSADRCFG2(CS Address Config Register) set SCLK cycles address bits and 16 bit device
Any info?
vivi
The main Samsung Approved Service Center here in Kenya has just given up on my SGS 1900 UK Model Nov 2010, originally 2.1 firmware upgrade via KIES to Froyo 2.21 in March 2011. They have handed it back unfixed after a week. Cant find a problem like this on any forum/google. Can find one that is fixable with the resistor jig, but Samsung dealer says his jigs don't help:
1) Press power, on comes B&W Samsung GT I900 screen, then the mosaic graphic that resolves to the glowing big "S". Then it buzzes feebly. Eventually it goes black but keeps buzzing now and then. Power off works.
If you poke around trying to get it into 3 touch reset, the Menu and Back keys light up and stay lit.
2) 3 Touch reset will not work. Dunno if it ever did as never tried before.
3) Plug into USB charger, it charges fine and shows the charger icon.
4) Plug into KIES and after a lot of attempts, KIES identifies it + firmware and connects. I can see and save my contacts and it displays CONTACTS, INTERNAL SD and CALENDAR folders in KIES. No more
5) ODIN ( which I dunno how 2 use but have) sees the SGS's COM when I plug it to my comp.
6) The dealer claims to have tried to resart/reflash with Samsung jigs. He has handed it back with a "cant fix".
What the heck is going on here? Looks like I have lost a few hundred bucks and have to throw it away.
When did this start? Phone was working perfectly. Suddenly a solid red icon with large white star labelled "Web Page" appeared on home page but no such App was found in SETTINGS>ETC. In any case, "Web Page" just led me to a totally innocuous page I use all the time as a homepage on INTERNET app. A few starts and shutdowns after that ( the battery was getting low so swx'd on and off like 3 times over an hour), it just went into (1) above.
Phone is STOCK, no mods, no reflashes,no rooting etc
Thanks
Peter in Darkest Africa
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. Get your phone into download mode by pressing volume down+menu button+power button until you get the yellow screen showing the android working. then open odin 1.7 and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
flash Darky Rom 10.1 with JVO Modem . Best GPS i´ve ever had, and my GPS was really bad.
frostygenius said:
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. then open odin and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
Click to expand...
Click to collapse
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Ok, I dunno if this is gonna help but I had a very similar issue when I first got my phone, within a week of owning it.
Points 1-3, exactly what happened mine.
Points 4 & 5 I didn't try, (was fairly new to Android)
Left it in to my local Vodafone shop & within 5 days I had it back in perfect working order, the maintenance report stated faulty hardware, the display module had to be replaced. Maybe worth mentioning to the service guy?
R34L2Pac said:
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Click to expand...
Click to collapse
Thanks for the heads-up I forgot to mention those points. I've updated my original post.
Sent from my GT-I9000 using Tapatalk
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Yes you are correct, I can't get download mode. The phone has never been reflashed or messed with. It came with 2.1 and using KIES in March I reflashed to 2.2 and it worked perfectly for 10 weeks until it semi-bricked.
There is the Black Screen of eath...then there is the pulsasing S screen of limbo! That's what I have.
The only harwdare clue I have is the SGS blew the fuse in my car charger shortly before "expiring"...yet if connected to USB or other charger, it charges the battery and displays the logo.
peterg123 said:
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Click to expand...
Click to collapse
..But download mode doesn't display the S logo or even the first Galaxy S 1900 logo...it goes straight in.
Try looking up in the Development section - I'm sure there is a jig method in there and it might be worth trying yourself, you've not got mush to lose now.
If you can get into download mode eventually, search for and flash Ezbase, that will get you onto a rooted firmware and it works EVERY single time for me. Good luck.
@R34L2Pac
Hi, thanks. As posted, the stock UK model SGS 1900 with 2.1 Eclair worked perfect from Nov to March 2011, was firmware upodated by KIES in March 2011 to 2.2.1 Froyo and worked like a dream until it went "semi-bricked" with the "Logo of Limbo" screen ( the pulsating giant S) for no reason.
A week before this, I changed SIMs when I changed countries and for some reason lost all added apps. I had to re-install them and even then, sometimes twice as I got many "android process stopped" errors --- even on some of the Sansung installed ones like Layar. That is the only problem I ever had.
The phone has only had apps from Market and never been modded whatsoever. Many thanks
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
R34L2Pac said:
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
Click to expand...
Click to collapse
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Try en carefully learn hw to use odin coz I gt tha same exact model. I hav flashed mine many tyms en am on 2.3.4 XXJVP. if u do gt into download mode odin will sort u. Regards frm K.poly.
Sent from my GT-I9000 using XDA Premium App
peterg123 said:
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Click to expand...
Click to collapse
how long have you tried holding down the 'volume down+menu+power' keys? a simple quick press of the three buttons does not work. you have to keep holding them all down for a bit (sometimes upto to 15-20 seconds) for it to go into download mode.
Sorry for the fast answer but I'm at work atm... I think he needs to do the 3 combo button fix on his phone first. I know it's on the forum somewhere... Can anyone check it for him? I lost the 3 combo the first time I updated with Keys from 2.1 to 2.2 and I had to fix it using a program that I can't remember to go on download mode and apply that fix.
Then he can use Odin to flash a stock rom as he needs, plus having 3 combo fixed!
Good luck mate!
Sent from my GT-I9000 using XDA App
Possible fix for your problem
Hi peterg,
I was looking through the general forum and found this post, where user beamzuk1 describes method how he fixed his semibricked phone. Symptoms are the same (not booting, glowing soft-keys, vibrating, no recovery and no download mode). So he used 'adb reboot recovery', I would say that proper command is 'adb reboot download', but you can try both. Also go through guide HOWTO use ADB, which I posted here the link in earlier post.
Hope this will help.
PS: Try follow beamzuk1 step-by-step, because if you start phone earlier than you connect it to pc, adb might not recognize the phone. Also be sure that you have correctly installed drivers and android-sdk before you try this.
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
LiverpoolFCfan said:
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
Click to expand...
Click to collapse
+1
Also think that Samsung should repair it or replace it.
The fact your repair center has done nothing to fix your phone, in several occasions, now entitles you to brand new replacement or your money refunded in full, contract terminated and expenses paid for your losses incurred as a result of their negligence.
Why not hit them up for the SGS 2.
I had the same issue with my first Galaxy S...wifi stopped working at first, I turned it off then on again but nothing changed. So I rebooted to see if it would correct itself. Bootloops and no 3 button combo (download or recovery)
Sent it off to Samsung through the Carphone Warehouse in the UK. I'd contact a Samsung Service Centre directly if I were you.
Just thought i would share my findings. I have been trying to get my T-Mobile UK Omnia 7 into download mode for ages!
The Vol UP, Camera Button, Power button trick did not work.
However i discovered that if you
- Hold the Vol UP button and the Camera Button
- THEN connect the device to your PC via USB
it will power it up and enter the device into Download Mode.
Well i hope that helps some others like it helped me
Regards,
Alan
I still can not update my phone to version 7.0.7392.0
I tried and cant go into download mode
I have to hold vol-up+camera for how long?
Basically what i did was hold the phone in one hand pressing the vol up and camera button. Then simply plugged in my Omnia 7 via USB. It went into download mode all by its self.
I had been trying for months, even just ordered a jig thing off ebay lol
Anyway, i managed to flash the phone down to 7004, then upgrade to 7392. Also make sure you have installed the new drivers off the samsung site (v1.3).
Long story short, i am now happily running Mango, and WOW it's a massive improvement! What ever you do dont Waslh your phone, it causes more issues than good as i found out lol.
That's great news influenceuk. I am also a new T-Mobile Omnia 7 user (great deal @ £15pm), and I had to enter 'download Mode' the hard-way, a little bit of patience and a 300K Ohm resistor from Maplin did the trick. So the method you propose bypasses the USB-Jig antics, that would be awesome.
I'm tempted to flash the blocked bootloader back to confirm your findings.
Yeah chemeng, it worked perfectly for me last night after trying for months!!
I only had to do it cause i walshed my phone, and it was causing issues updating to the mango beta. i will see if i can find the page i found the instructions on
Just looked thought my history, but cant find the exact solution i mention. I did find the XDA Dev guide, which i think i may have mis read... then found my work around.
Some one else should try and see if it works too, hopefully it does.
Sorry but I cant get my phone into dowhload mode with your solution
It seems as if Alan's bootloader was semi-blocked
hey folks thıs worked for me
http://pocketnow.com/windows-phone/samsung-outs-omnia-7-patch-fixes-wp7-update-errors
Well, I used to encounter this problem that cannot access to the download mode and getting error code (8XXXXXXXX) when trying to update the phone via Zune Software. But after trying update via zune few times, I successfully updated my OMNIA 7 to 7392 and got download mode works afterwards.
Same here. Tried to get into Download Mode for hours. I was about to build myself a jig.fortunatley i Tried updating my phone via zune... et voila...zune updated my bootloader and the Rom.
Now im able to get into Download Mode without any problems! I got a Samsung omnia 7 from t-mobile Germany.
Hope this helps...
Greetings
Bootloader version
Is there anyone who has successfully updated their Omnia 7 from NoDo to 7392 (latest security update) or Mango, with a bootloader version of 4.10.1.9, without using a USB jig?
Thanks,
Karthik
I have tried almost everything, but nothing works, I also have Omnia 7 with 7390 and bootloade 4.10.1.9, I think with this version of bootloader there isn't any other option than usb jig. I even called samsung helpline (they were much less informed than me, so they just told me to bring the phone to service center), does anyone have experience with service center, or is it better to make USB jig and do it at home?
I have three Omina 7 ,they are all 16G type.
First one ,by pressing vol up ,camera and power button can reach the download mode.
Unfortunately,the other two must use a jig to get the download mode.
@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 had just updated to April update patch. For whatever reason I was going through the options at bootloader and noticed....there is no longer an option for Download Mode? Just Bootloader, Recovery, Barcode (? whatever that is), Power Off, and Restart. I'm not really up-to-date on these kinda things so, for all I know, this was implemented way back when on February or March update patch. In any case, I did search through this (Pixel 2 XL) thread for keyword "Download Mode", and not much came up; certainly no mention, yet, of it being taken off/away.
Doesn't look like the ol' Odin methods gonna be an option for the Pixel 2 and/or Oreo or P...
In the end, was there any use or method that Download Mode was used (at least for the Pixel 2's)? I mean, we update/reflash through adb and fastboot and applying root patches usually go through Magisk modules... But I came from the Galaxy S5, so Odin is still current and very much in use in my head/timeframe...
simplepinoi177 said:
I had just updated to April update patch. For whatever reason I was going through the options at bootloader and noticed....there is no longer an option for Download Mode? Just Bootloader, Recovery, Barcode (? whatever that is), Power Off, and Restart. I'm not really up-to-date on these kinda things so, for all I know, this was implemented way back when on February or March update patch.
Doesn't look like the ol' Odin methods gonna be an option for the Pixel 2 and/or Oreo or P...
In the end, was there any use or method that Download Mode was used (at least for the Pixel 2's)? I mean, we update/reflash through adb and fastboot and applying root patches usually go through Magisk modules... But I came from the Galaxy S5, so Odin is still current and very much in use in my head/timeframe...
Click to expand...
Click to collapse
Couple points of clarification before I answer...
1. Odin is a tool for Samsung Devices.
2. The device has download mode still
3. Download mode is not the same on Samsung devices as it is other devices. Download mode on Samsung is more like bootloader.
So with that said...
I think you may have been mistaken. There is has never been a download mode that is user friendly like Samsung devices.
Scott said:
Couple points of clarification before I answer...
1. Odin is a tool for Samsung Devices.
2. The device has download mode still
3. Download mode is not the same on Samsung devices as it is other devices. Download mode on Samsung is more like bootloader.
So with that said...
I think you may have been mistaken. There is has never been a download mode that is user friendly like Samsung devices.
Click to expand...
Click to collapse
Thank you @Scott ! I wasn't aware of a whole bunch of that...
Okay...some things...
1) I wasn't aware Odin was only for Samsung. I thought it was a whole Android mobile OS thing... And with that assumption, I would've thought that Odin was applicable to a whole lot other phones/manufacturers.
2) When researching if anybody has brought this up (at least in this thread), I did see a thread talking about using Download Mode to update the monthly updates. I'm going to check that right now and see how it goes...
If anything, Download Mode used to be "selectable" in Bootloader mode. It was actually colored green rather than the red for Recovery and Bootloader. It no longer is there; at least for 8.1 April update. Also, I've tried to enter it using the Magisk app -- reboot to download, but it merely rebooted like regular... You might want to check on that.
3) same response as 1). But yes, it does seem that most of the stuff I did in Download Mode with Odin is what I simply do in Bootloader Mode for the Pixel 2.
Its there man. I have been in and out of it for the past couple weeks.
To get to download mode on this phone (and most LG's) simple hold the volume up button and connect the USB cable while the phone is powered down.
This will bring you to download mode.
Scott said:
Its there man. I have been in and out of it for the past couple weeks.
To get to download mode on this phone (and most LG's) simple hold the volume up button and connect the USB cable while the phone is powered down.
This will bring you to download mode.
Click to expand...
Click to collapse
Not meaning to sound like a noob, but doing this allows you to............?????
Badger50 said:
Not meaning to sound like a noob, but doing this allows you to............?????
Click to expand...
Click to collapse
Enter download mode to factory program the device. Its a factory service mode.
Scott said:
Enter download mode to factory program the device. Its a factory service mode.
Click to expand...
Click to collapse
Ah! Much obliged. I'll leave that one to you programmers! I'd just blow it up if I tried anything like that
Badger50 said:
Not meaning to sound like a noob, but doing this allows you to............?????
Click to expand...
Click to collapse
LOL! Thanx for inquiring Badger! I was wondering as well...
Scott said:
Its there man. I have been in and out of it for the past couple weeks.
To get to download mode on this phone (and most LG's) simple hold the volume up button and connect the USB cable while the phone is powered down.
This will bring you to download mode.
Click to expand...
Click to collapse
Hmmm that's interesting! I've never had a Google or LG phone...
Well...I guess I was mistaken as there is that mode -- just a special way to get into it! But, as I said previous, at the very least they took it out of the selections in Bootloader...And I've seen it rather easily accessible and obvious from Motorola Droids and Samsung Galaxies over the years, so I found it interesting that after all this time they [finally] removed the easier way to access it...
simplepinoi177 said:
I had just updated to April update patch. For whatever reason I was going through the options at bootloader and noticed....there is no longer an option for Download Mode? Just Bootloader, Recovery, Barcode (? whatever that is), Power Off, and Restart. I'm not really up-to-date on these kinda things so, for all I know, this was implemented way back when on February or March update patch. In any case, I did search through this (Pixel 2 XL) thread for keyword "Download Mode", and not much came up; certainly no mention, yet, of it being taken off/away.
Doesn't look like the ol' Odin methods gonna be an option for the Pixel 2 and/or Oreo or P...
In the end, was there any use or method that Download Mode was used (at least for the Pixel 2's)? I mean, we update/reflash through adb and fastboot and applying root patches usually go through Magisk modules... But I came from the Galaxy S5, so Odin is still current and very much in use in my head/timeframe...
Click to expand...
Click to collapse
Well actually LG download mode is exactly like Samsung's, it's a holdover going back to the LG transformer that used TouchWiz UI. If it's not in the fastboot setting you can still manually boot to it by powering off the phone. Then press and hold the volume up button while plugging in the USB c