Hello there, I have just bought a Mi A1 for my father and get notified on system update (October patch that is over 1 GB of size). However, download seems to never progress even though I have an internet connection. Is it possible to download the update using PC, put it somewhere on the phone directory and use the System Update to flash it? My father doesn't want to get his phone bootloader unlocked and rooted.
He also already experienced SIM card not being detected twice over two days which require phone reboot to make it detect it again (SIM card is at slot 1, SD card is at slot 2). Is there any known problems and workaround with this device regarding that issue?
Thank you in advance.
Hey you can try flashing the latest rom through mi flash tool. This is will not make any change to your bootloader status. You just need to download and extract the rom somewhere on the C: folder and the rest of the tutorial you can find on this page (its for a different phone but works the same way on A1)
http://en.miui.com/thread-142056-1-1.html
Also you can find all the downloads for A1 on this page:
https://forum.xda-developers.com/mi-a1/how-to/rom-mirrors-mi-a1-stock-androidone-rom-t3696821
And you can grab minimal adb and fastboot here (extract them in the same folder that you extract the rom)
https://forum.xda-developers.com/showthread.php?t=2317790
All the best
Related
Hi, I'm hoping to get some help with cooking and burning ROMs to my o2 XDA.
My original product specs are:
ROM Version: 3.20.06 ENG
Radio version: 4.21.01
I cooked and then downloaded 4.01.00 ENG from Lumpi Stefan's site, then ran the rom.exe file that it produced for me. Everything worked fine, and then I rebooted my XDA. Upon first boot the phone appeared to work, but after performing a soft-reset because the XDA froze, all of the phone functionality appears to be not working.
When I do a hard-reset I get: Wallaby Bootloader v6.22 - GSM OK which I think looks good as far as the phone functionality is concerned. Looks like it's the OS that's on the XDA which is causing the phone difficulties.
I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started!
I don't have an SD card, and am in dire straits about getting my phone to work. Is it possible at all to get this to work, or perhaps to go back to my original ROM (I backed it up to orig.nb1) using XDAtools. Anytime I try to burn the .nb1 file back to my XDA it fails. Or is the ONLY way to get an SD card and use the Bootloader technique? I even tried downloading the 3.17.03 ROM upgrade directly from the o2 sitebut it fails.
Any help will be GREATLY appreciated.
Thank you.
[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![/qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.
[qoute]I read somewhere that if you burn any T-Mobile ROMs an SD card is *required* to reverse it and put a different ROM on the XDA. Well, the cooked ROM I downloaded is from T-Mobile - I didn't know this before I started![\qoute]
this is true with 4.00.10 and 4.00.16 but not anymore with 4.01.00.
if your xda still can be connected to activesync, try to reflash the ROM.
Otherwise, you have to use the SD flashing method.
Thanks, I will try. ActiveSync still works...
I notice you are running the same ROM version as me - sis your radio still work?
Can you verify that I am trying to Flash the ROM correctly?
1. Confirm that I have orig.nb1 - yes, it's there - backup of original ROM before I started this whole dilemma.
2. Ensure that XDA is Activesync'd - yes, as "Pocket_PC" - all working okay.
3. Right click on orig.nb1 and select "burn"
4. OSImageTool.exe then pops up and copies orig.nb1 to Programme A.
5. A DOS box then appears saying "ERROR: GetConnectionType - A
ote host. error getting connectiontype".
6. Programme A then runs and after pressing "next" a couple of times, I get an error - "Error 011: Cannot execute the remote communication program. Pleace make sure that the USB cable is properly connected."
And that's basically it.
I have tried different variances of this, but all without success.
Help!
BTW, I'm logged in to MSN Messenger now, could you let me know when you're online - or anyone else, for that matter. My address is [email protected]
This message means that the current ROM in your XDA can't be flashed through Program A ... not a big issue, for unknown reason it happened with me few times ... but now you have to use SD card to flash your ROM.
Here is an update...
I have played around some more with the XDA with no success. I have now bought a 64MB SD card and am unsure as to how the ROM image on my PC gets onto the SD card. This is how I have been doing it:
1) Insert SD card into XDA
2) Place XDA into cradle
3) XDA then ActiveSync’s to the PC
4) Run OSImageTool.exe and select the following –
a. Source: “C:\Documents and Settings\Paul\Desktop\orig.nb1”
b. Destination: “XDA SD card slot – unknown size”
5) Then I press “copy” and I see the progress bar go across to 100%. After this appears to finish, the program just sits there not telling me it’s finished. I assume that it’s all okay and I then close the program
6) Take XDA off cradle and hold power button down whilst doing a warm-reset
7) The following appears: “Wallaby Bootloader v6.22 – GSM OK” – nothing else happens, and from what I have read it is supposed to ask if I want to perform a ROM upgrade. However, I can get into the diagnostic and flash tools by pressing the action button etc, but nothing is in there to upgrade the ROM.
Does the fact the OSImageTool destination says “XDA SD card slot – unknown size” matter? I’m assuming not because when I have transferred the ROM using the above steps, the XDA asks if I want to format the card; meaning that the transfer worked okay. Do I have to have an SD card reader/writer on my PC to get the ROM onto the SD card?
I have read a little about a Bootloader patch – do I need to run this, and how do I get it onto the XDA – using the same method?
I would be very appreciative of any help that can fix this, as all I want to do is get my three-day old XDA working again!
Any other comments and help in relation to solving this hair-challenging issue would be great!
Thanks,
Paul…
Ok ... from what you wrote it seems your doing it correctly. However, I have doubts on the file orig.nb1 you are using ... maybe it wasn't copied properly.
Try to cook any ROM (TMO 4.01.00 is good) at Stefan kitchen and you can cook it as .nbf or EXE then extract the .nbf file using winzip or winrar.
Follow the same steps and let me know.
Good luck ...
Is bootloader v6.222 okay - will it allow me to overwrite my current ROM with this new ROM that you are suggesting? I have read that I may have to downgrade my bootloader to do the SD ROM writing thing.
I can't confirm that my self ... I used SD with 5.17 and 6.22 without problems but maybe it's my luck
Cook the 4.01.00 as EXE and try it as is or extract the .nbf file and use the SD method.
Okay I'll give that a go now... Will let you know how I go...
Nope - didn't work. I'm not getting a screen in the bootloader to update the ROM via SD - if I press the action button I get into dignostics...
Is this a bootloader issue, and if so, how do I downgrade?
Also just tried the following:
C:\Program Files\XDAtools\binaries>pnewbootloader bootloader_v5_15.nb0
And got the following error message:
Unable to find flash info offset, cannot disable bootloader writeprotect
Any ideas?
I don't get it ... you cooked and downloaded and tried a new nbf file for TMO 4.01.00 in less than 15 minutes ??!!!!
what is the nbf file size ??
Yes, I used Winzip to extract NK.nbf. It is 31,745kb.
I am now cooking on Lumpi's site a zipped NK.nbf file and will try that too...
Hi,
I have a T-Mobile Pocket PC Phone 2003.
Rom version: 4.01.16 ENG
Rom date: 02/04/04
Radio version: 6.25.02
Protocol version: 324e4
Wallaby Bootloader: V5.22
I am in a GSM 1800Mhz region while the phone has only 900/1900Mhz. I have read various reports that with a Firmware upgrade I can make the phone Tri-Band capable meaning 900/1800/1900Mhz. There have also been reports that this is a hardware feature which will not be effected by software upgradation. But I wanna still try. Firstly the phone was Simlocked by T-Mobile which I managed to unlock with a code given by their SimUnlock dept. believe it or not.
The problems / issues I am facing with this phone are:
1. Downloaded the XDAROM.exe with adaptROM.exe Program A.exe etc in it but it always stops at the dreaded -
ERROR: GetDeviceData - An existing connection was forcibly closed by the remote host.
error getting devicedata
For the above I have tried all the suggestions on this forum like hard booting (battery off/on), Select GSM900 in Wallaby Mode then reset, Remove Sim Card then Reset, Switch off Radio (which I presume is GSM) in Wallaby then reset. All options lead to the same error.
2. Tried backing up the current ROM in Bootloader Mode which it does and asks me to press the Action key. But when I reboot the device or remove the SD Card and plug it into a PC it says Card not formatted. The SD card
works under normal conditions transferring data to and fro and storing data.
3. Read that I can copy the .NB1 (update file) onto a SD card and on rebooting it should ask if I want to Flash the device with this new data but it never asks and reboots completely.
4. Wallaby mode is also supposed to Flash the device via USB if I press the record key I tried but the computer and device never connect.
5. Device does not ActiveSync always on docking very often I may need to reboot the PC and or the Device for them to talk.
6. Tried XDAUnlock. exe which gave me 'error getting unlock code'.
Any ideas people? Any help would be greatly appreciated.
Andrew with no clever lines
In no particular order:
(1) 1800 MHz is a hardware feature. At best, playing with the firmware will make the phone think it can operate at 1800MHz, but it really can't without hardware changes. But hey, you already know that.
(2) When you dump the ROM to an SD card, it is dumped as an image, which overwrites any FAT formatting on the card. This is why you're getting the "Card not formatted" message on the PC. You need special PC software (XDATools -- available on this website, or XDArit) to access the ROM image on the card with the PC.
(3) In order to upgrade the XDA with an SD card, the firmware needs to be placed on the SD card as an image (the same format as #2 above). If you just did a PC file copy you used the wrong method. XDATools also does this function.
(4) Why are you trying to use XDAUnlock.exe when you've already unlocked your phone with the code from T-Mobile?
Hi,
Thanks I did finally realise what every one took for granted in this site that the ROM dumps on the SD were written in a proprietory image format not FAT format.
Am trying the entire exercise coz have read at enough places on the site that the phone can be cracked to be tri-band which is what I need for it to roam India. We have only 900Mhz at select locations and the rest is 1800Mhz. Can only but be hopeful.
The chronology for the unlock bit was off on my mail.
Basically I cant perform any updates to the phone via the adaptROM method because I feel Wallaby 5.22 has protection built into it and shuts down the connection. If I try to Downgrade the Wallaby to V5.15 using the bootloaderfix included XDATools I get the error listed below.
'C:\bootload\pput.exe' is not recognized as an internal or external command,
operable program or batch file.
ERROR: ITReadProcessMemory - Unspecified error
Unable to find flash info offset, cannot disable bootloader writeprotect
If I use XDArit V1.02 route to write via SD I get Failed to open Device \\.\PhysicalDrive7
Anyone got the older version of XDArit ??
Help people.
Thanks,
Andrew
I'm not as familiar with Bootloader version issues. My (old) unit was Version 5.15. I just got a replacement for it after I busted the screen, and the new one is Version 5.22. Maybe I'll learn more about bootloaders...
But LumpiStefan says he hasn't had problems using the SD card method with 5.22. I haven't played with the new phone yet, since it came with WM03.
Wouldn't it be easier for you to spend $100 (or so) on an unlocked 900/1800 phone?
I have a HTC ELF 0300 it is stucking in the tri colour screen with the following
IPL: 2.26.0002
SPL:2.28.0000
i have followed the advice i found on this forum of flashing the ROM but when i try the rom update utility it comes up with error 270 about the image also i tried the mtty process but it wont open the usb port
i tried flashing the SD Card but it then says "Invalid Certificate"
i'm a total loss and totally stuck..
any help appricated
Have you really read this sticky thread http://forum.xda-developers.com/showthread.php?t=406721 before flashing ?
Have you used "search" function with f.e. "stuck in bootloader" before posting ?
If not, please do and you'll find very useful solutions
i have read the theads over and over again and finally worked out mtty and worked out my phone is
elf0300
tmob050
it's still in tri colour mode yet i cant find a rom for it...
i tried the nbh file flashing to the memory card
but no luck....
heelllp
Do you know if you have Elf or Elfin?
It is essential for flashing original Rom Elf: http://forum.xda-developers.com/showpost.php?p=2045325&postcount=2
Elfin: http://forum.xda-developers.com/showpost.php?p=2045051&postcount=1
i haave an elf (p3450) well thats what it says on my box
i cant find the orginal rom for this and i'm totally stuck
any help is greatrully recived
also i have tried CID unlocking it so i can put custom roms on it but my computer wont active sync when the phone is connected through the USB port...
Also, what did you do to get your phone stuck in bootloader in the first place?
my brother did it to my phone before i'd even had chance to use it , and i don't know what he did.....sorry x
Try this and follow the instructions exactly http://forum.xda-developers.com/showthread.php?t=347700 and report pls
i tried this yesterday at first when i pressed enter i didnt get >cmd (which is what happening now)
then when i do get it eventually after many tries it sasys
cmd55 or something failed
and stays on 0% on a gray screen
sorry if i sound stupiud.
Ok
First you connect your device, then right click on active sync icon on your computer, chose connection settings and change according to the instructions then continue with mtty.exe
i have done this
when i press enter i dont get anything come up....
yesterday i managed to get it up though and just stayed gray screen at 0%
Try again a few times making sure you didn't overlook any detail.
I just found this http://forum.xda-developers.com/showpost.php?p=3395787&postcount=155 possibly mtty version doesn't work
2- Another possibility is unbricker rom http://forum.xda-developers.com/showthread.php?t=446242
3- gold card method (the links are dead so you should pm Dsixda)
Flash from the SD card:
ELF0IMG.nbh on a FAT32 filesystem, complete flash takes about 30 minutes, so check your battery or connect to charger before the flashing process starts.
1. Format microSD card from your computer.
2. Extract the .NBH file from your prefered ROM upgrade: In windows use winrar (right click) to extract the contents of the exe file. In Linux / MacOS use cabextract.
3. Rename the .NBH file to ELF0IMG.nbh and copy it to the root folder of your microSD card.
4. With microSD card inserted in the phone, start the bootloader (the bootloader is invoked by hold down the camera button and reset device with the stylus).
5. Confirm flashing on screen by pressing the power button (or the volume slider down).
6. Flashing might hang after some time but this is normal. Just wait.
Will try now and keep u updated
manny thanks x
Follow the instructions until you get cmd only, then return to the tutorial to continue
Good luck
Just an update
i downloaded the nbh file you sugested and tried both
1) flashing from the SD card by renaming file - when i do this is says checking sd contents then goes back to my bootlooder screen
2) running the romupdateutility.exe with the nbh file in the same folder it goes through then i get error 294 incorrect vender
i am unable to pm Dsixda about the gold card
i have no idea what else to try
ps: when running mtty i still get a gray screen then the bootloader screen.
Sorry to hear this, I'm out of ideas. Just some details not to miss:
try a hard reset
writing "ELF0IMG.nbh" (elf zero img and not elf o img)
google for mtty and download a few versions
Wait for an answer from Dsixda for gold card if you can't find your original rom
Creating your GoldCard
I don't remember well the procedure but you can try the following:
If you have access to a working pda or a working GPS device - PNA which is powered by WM (even modified) then you have to follow these steps:
Download this package and save it in your C:\ drive.
Run it.
(it will extract all the necessary files in C:\itsutilsbin (folder) and it will start the setup of Perl)
When the Perl - installation is finished run Perl Package Manager from Windows Start Menu.
Add repositories.
Name: itsme
Location: http://www.xs4all.nl/~itsme/projects/perl/ppm
Name: theoryx
Location: http://theoryx5.uwinnipeg.ca/ppms/package.xml
(HowTo: run Preferences from the Perl Package Manager menu and switch to the repository tab)
After database synchronization install these packages:
Crypt-DES
XdaDevelopers-NbfUtils
(HowTo: at the main window of Perl Package manager find those packages, mark them for install (the icon with green plus, next to the search bar) and run marked action(green arrow icon))
Format the sd card(FAT32) and insert it in a working pda.
Connect the working pda to the pc , wait to sync and run psdread.bat from C:\itsutilsbin.
Find an official rom from here with a ModelID which matches your device's one
Example: If your pda is an Elfin and you have ModelID ELF030000 then get the below rom from that thread.
RUU_Elfin_TMO_NL_2.26.114.52_4.1.13.52_03.08.90_BL UE_Ship.exe (T-MOBILE)
Device: ELF030000
CID: T-MOB003
Version: 2.26.114.3
Language: NLD
Click to expand...
Click to collapse
Extract the RUU_Signed.nbh, rename it to ELF0IMG.nbh and copy it to the sd card.
Fully charge your battery, insert the sd card to your pda, enter bootloader and flash from memory card
(Confirm flashing on screen by pressing the power button (or the volume down button)).
If everything went ok then you can use a HardSPL or a USPL to CID Unlock your phone and update the rom with one of your choice.
If you don't have a working pda use a card reader - Ubuntu (even from a LiveCD) and QMAT are required
Regards!
i don't have a working pda to use :-( the only pda i have is my bricked one :-(
buncie2010 said:
i don't have a working pda to use :-( the only pda i have is my bricked one :-(
Click to expand...
Click to collapse
There is a way to use a card reader instead.
Using Ubuntu LiveCD and QMAT
ps:I wonder how did the wiki entry got erased?
Dsixda and all the members who worked on this had done a great job and it's really annoying that all their work was lost.
Hi there i am hoping somebody can help i have found alot of threads explaining the issue with htc hd2 white screen error but have not found a solution to help i have tried for days to load stock roms original telstra roms tried hspl3 i can not connect through windows mobile with usb and have tried flashing original roms via 4g sd card with no luck am i missing something i have tried RUU_Leo_Telstra_WWE_1.49.841.1_Radio_Signed_15.28.50.07U_2.05.51.11_Ship RUU_Leo_Telstra_WWE_1.72.841.0_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship i have tried to run through adminstrator i can not access the phone settings to turn on active sync so as far as i am aware i can not do anything through usb. i get an error msg when flashing via card and it terminates the update. Can anyone help with this issue i know there are many threads none have helped me.
Thankyou in advance
There are several possible reasons that the flashing process fails. Or, as it seems, the connection from your device to the PC - which might be a driver issue.
Normally, HD2 turns on ActiveSync if you want (you can select when a popup screen offers this) as soon as the device is connected to a PC through USB.
If the flashing process doesn´t run via SD card, there are also various possible reasons: Sometimes, cards bigger than 2GB don´t work, or your card is not formatted FAT32, or the naming of the ROM file is incorrect (should be leoimg.nbh). Or, your device is not a Telstra device after all?
Anyway, in order to help, there is more information from your side needed, otherwise, it´s a bit like searching a needle in a haystack.
Like tictac0566 said
Try 2gb sdcard - make sure its fat32 formated.
Make sure battery its not under 50%.
Most important Make sure the rom your are trying to flash its for your hd2 ( best way its to download from htc - web support with serial number ).
sd installation
i down loaded the rom. the oiginal rom is in exe extention. how do i used it to install from sd card. i gotthe rom from tmobile with serial number? where can i downlead the seperate rom file.. any link for .nbh file
The exe is actually an executable zip file. Rename it to. .zip from .exe and you can then open it with winzip or winrar or whatever,and inside you will find several files,one of which is ruu_signed.nbh which you extract and rename leoimg.nbh and flash with.
steps to flash through sd card.
i tried 3 stock roms even from tmobile web site. it gave me a radio error and terminate. what can i do it just wont install radio..???
Hi, I’m the owner of an Acer Neotouch S200. Yesterday while I was updating from Acer v2.003 to Acer v3.003c (Italian version) a black out occurred and the process stopped. Since that moment my smartphone turn on but it stucks on the Acer Logo, first screen, with the red led flashing (installation mode active?). It’s not recognized when I link it to the PC (usb cable). I read something around the web and I find this two possible solutions:
1) Flashing the ROM using the acer download tools.
2) Flashing from microSD.
1_I’ve downloaded the prog, but I don’t know where to find the .bin file that I have to use. In the v2.003 I’ve founded Extrom e Flash files but I don’t know which one should I install. The prog also says that the image files aren’t correct. I tried this metod but my pc still didn’t recognize the phone. Probably I have to push some combination of buttons that I don’t know. Can you help me?
2_Flashing from microSD requires: microSD <=2 GB (no SDHC), sd must be FAT or FAT32 (first one is better), you have to copy the .bin files and then push a group of buttons with the device turned off, then it will start the process of upgrading and after a reboot it will works. Same problem: which file should I copy over the sd? Which combination should I press?
Are there some other methods to recover my phone?
Thanks for helping me, sorry for my bad eng.
Those method were used on an Acer Liquid (1) and Acer F900 (2).
Solved. I used the Hacked ACER_EUU and I have installed the 2.003 version. Then update the device to the 3.003c. You can close, thanks.