Related
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
On another note - I had purchased a working 2110 with a good mobo to replace this one if the flash is not repairable - is that a difficult procedure? Unfortunately, the 2110 I purchased was not working, but this may still be in the books at a later time, so some info would help.
Thanks!
Rustmonkey said:
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
Click to expand...
Click to collapse
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
reggaepoo said:
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
Click to expand...
Click to collapse
You, my good sir, are a genius - worked great! Fixed BOTH 2110s
tangwd898 said:
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
Click to expand...
Click to collapse
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Rustmonkey said:
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Click to expand...
Click to collapse
really amazing !!!!!!
I just saved my hx2110 as per your step by step instruction now.
Thank you very much.
ok, well, I thought they were fixed... now one of them freezes at the bootup screen, even when I do a clean reset... I've tried reflashing multiple times to no avail... any ideas whats going on?
ok, got everything working - reflashed the non-working one back to an original 2003 rom - which made if freeze at boot - then upgraded it via pre-bl to 1.00.00.L - from here, it wouldn't do anything after filling the bar at the boot screen, but it didn't CRASH (as in lights out) - so I ran the pre-bl again and ran the flash program for 1.00.00.L again WITHOUT swapping between the 2495 and the 2110 - just put the 2110 in pre-bl and away we went - flashed, formatted, and booted - then proceed to upgrade to WM6 via 1.00.00.H --> 1.02.00.H --> WM6 - works GREAT!!!
Thanks for the help everyone!
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Hello,
I have run into some problems with a bricked hx2110.
I was flashing the IPAQ to a new ROM WM5 (Battery was full and I read all the instructions 10 times prior to flashing). While flashing, the progress bar went to 100% then faded out immediately and it wouldn't reset (clean reset). I put the battery in my friends hx3000 series and the battery I used was completely dead. It did flash to 100% though, but not matter how many times I try 1 + 3 + reset, it doesn't reboot. If I can figure out how to get it to boot, that would be great, but I can't get anything to come up with any key combinations.
To this point all I can do is get into Pre-BL mode 1.00.04. I have tried the below scenarios on two machines, both running windows XP SP2 (USB 2.0) with the firewall and virus software disabled.
http://forum.xda-developers.com/showthread.php?t=330382&page=4
1) I have tried the above links directions and used the the Universal Bootloader (Bootloader.exe). It gets to the point where it says "The PDA should be updating now" or something similar but nothing happens. I don't get any errors regarding communications (it sees the device when I hold the "Calendar" button until it says USB; windows then recognizes the device as "HP USB ..." so I know it's communicating).
2) I tried to use the Bootloader_GUI.exe beta so that I can watch the progress indicator but it just sits at 0%. There are no error messages so it is communicating but for some reason, the device won't let it flash (and the flash utility thinks it's doing something).
3) I tried the original ROM flash from HP (SP29856.EXE) and it recognizes the device, but because the current ROM on the PDA is hosed, when it does it's "verifying" process, it comes up with "?" marks as the model number and when it goes to flash it starts at .1% then says "FINISHED" immediately. The ROM utility thinks it flashed it correctly but it didn't flash anything. I'm guessing that the verification of the PDA failed and forced the utility to not flash.
Does anyone have ANY ideas of what to try? I wish I had another HX2000 series PDA and try the "swap" thing prior to hitting the update button but I don't. All I have to work off of it my sad bricked PDA and a full battery (friend keeps charging it). His PDA is an HX3000 series.
Any ideas would be appreciated,
Thanks!
Are you using a the HP flash program that is specified for your device?
2nd - you might be able to use your buddies device in a swap as well - not sure but its worth a shot - use HPs upgrade program, let it verify, then swap your device onto the same cable - overwrite the firmware in the update program for HIS device with firmware compatible with yours and then hit update - let us know if this works...
I am using the "official" HP flash program specific for the HX2110 (from their website - SP29856), bootloader.exe, and bootloader_gui.exe
I wanted to try my friends, but he won't let me touch his because I bricked mine lol (I swore nothing would happen to his but he still won't let me try it).
Anyway, I just copied over the ROM image (from HP) and stripped out the header (now showing 64 bytes before the ECEC). The ROM is for WM2003. I copied the ROM in binary using psdwrite.exe to an 256 MB SD card. As soon as I can get the battery back, I'm going to try to flash it from the SD card. If this fails, I am going to try to play around with MTTY / USB and manually call the ROM flash and see what happens.
Having another HX2000 series would make this easy (maybe a little TO easy )!
Bootloader never worked for me - but if you can get it to manually call the flash, more power to you good luck!
Well it was worth a shot. After spending the better part of the day with the PDA, I have made no more progress (can't get Pre-Bl to update). The only option I have now is to find someone with another hx2000 series that is willing to resurrect it from the dead for me (PM me if you can help - I will pay two way fare). Until that happens, it's going in the "broken" drawer with all my old comp stuff .
Thanks to all the tips and tricks that is posted on these forums and brighthand! There is a wealth of information on this topic and without them, I would have gotten nowhere in trying to repair the device (granted, I wouldn't have been intrigued to upgrade the ROM in the first place and would still have a working PDA, but that's besides the point ).
Best of luck to you all.
1).download original ROM from HP (sp29799) -extract files
2) download http://upload.dvhk.pl/content.php?id=88892 - replace files
3) flesh device.
bay!
link crash http://upload.dvhk.pl/content.php?id=88892 - replace files
Please it can raise it again, thanks
Absolut3k said:
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Click to expand...
Click to collapse
Same here.. is there another way to un-brick hx2110 on this problem ? thx ...
Solved, my hx2100 returns to be in this world
thank you i saved my ipaq
I wasn't expecting to do this, but I had a 2 hour delay at my college due to snowy weather, so I decided to take the time to upload my 1st official WM6.5 rom for the Asus A6x6 early. Keep in mind that this rom is far from perfect and the fancy new WM6.5 today screen is not working (looks like the today screen from WM6/6.1).
Thanks to Makuu (for helping to get me started), Lenny, AstainHellbring (thank you for all the nightly help sessions), the creators of the tools I used to make this rom, and anyone else that I failed to mention in name who gave me the knowledge to complete this rom.
Asus Mypal A6x6 WM6.5 version 1a
Windows CE version 5.2.21234 (Build 21234.5.0.1)
This was tested on an Asus Mypal A626 (and works). It should work with the A686/A696, but the other models were not tested. Any other models not metioned above WILL NOT WORK.
Updates
1. os build
2. bug fixes
Additions
1. Windows Marketplace
2. File Dialogue Changer
3. PsShutXP
Removals (you can reinstall these via windows marketplace)
1. Windows Live
2. MS Office Mobile (get the beta from marketplace)
Removals (non-Windows Marketplace)
1. Remote Desktop Mobile
download: http://www.easy-share.com/1909744620/Asus_A6x6_WM65_1a.rar
At this time, this will be the only download link. Mirrors will be created in the future (after I give permission).
Instructions (I have included a txt file with same instructions for offline convenience)
Before you do anything, make sure you have at least a 256mb SD card and a card reader (you can get one at a place like Radio Shack or Office Depot). You also need to install winrar (found at http://www.win-rar.com/download.html). Your SD card must be formatted with the FAT16 file system.
To format your SD Card with the FAT16 file system
Step 1: To do this insert the SD Card into the reader and go to "My Computer".
Step 1a: BACKUP YOUR FILES before you start!!
Step 2: Right-click the drive letter of the SD Card reader (differs for each computer, probably either E:\ or F:\ or G:\) and click "Format".
Step 2a: Don't worry about any of the options except for file system, choose "FAT"
Step 3: Click "Start" and wait until it is done
Step 1: Get (OS) rom image
Step 2: Extract files to any folder on hard drive using Winrar
Step 3: Go to the folder where you extracted the files in the RAR archive
Step 4: Make sure that the filename is "CANNES_A_WM6.img"
Step 4a: if the img file it's not exactly "CANNES_A_WM6.img", rename it to that
Step 5: Format the SD card if you haven't already done so using the instructions above
Step 6: Copy the img file to the SD card, see step 6a
Step 6a: Make sure that the img file is the ONLY file on the SD card after formatting
Step 7: Take SD Card out of SD Card reader and put it in the a6x6
Step 8: Make sure that the a6x6 is plugged in via ac adapter before doing the next few steps
Step 9: activate SD Loader using the following instructions {
Step 9a: Hold down the power button and enter button (that's the button in the center of the d-pad)
Step 9b: Double tap the soft reset button while holding the other 2 buttons
Step 9c: After double tapping the soft reset button, keep the other 2 buttons held until a blue screen comes up that says something like Asus Cannes flashing utility
Step 9d: Wait until the process is finished (it's near the end when it says "writing private")
}
Step 10: At this point, your a6x6 should reboot on its own
Step 11: enjoy your updated rom
If you have any questions, feel free to just post or PM me.
As I release new roms, if you have a support question, please give me the rom version so I know what rom you are working with. You can get the rom version from the filename of the rom pack.
Example: Asus_A626_WM614_1
A626 = device (most often it will be A626, will rarely be different), WM614 = os version, 1 = release #
Update: Ok, I put out a bug fix rom with a fix for the today screen. I am still trying to find a fix for the sound and notifications control panel applet. The old rom (version 1) is deprecated and is not available for download any more. Use version 1a instead.
ASUS A696 User
Hi, Thanks for the release and good work. Since this is only the beginning (I hope), I begin to inform the performance firmware on my PDA (ASUS A696).
1 - Bluetooth - does not work (does not receive or send files)
- In the settings instead of the icon is a black square.
2 - Today - of all the elements shown only date and time, and only in the old form (as in the previous OS). I wish that Today was like other communicators.
3 - Start - which happened to all the sounds from the "Sounds and Notifications"?
4 - Software & others - as the 696 series have more memory, you can not throw out the program and plug-ins.
Waiting for a new version
Sorry for my English? i'm from Ukraine).
Skromnjaga said:
Hi, Thanks for the release and good work. Since this is only the beginning (I hope), I begin to inform the performance firmware on my PDA (ASUS A696).
1 - Bluetooth - does not work (does not receive or send files)
- In the settings instead of the icon is a black square.
2 - Today - of all the elements shown only date and time, and only in the old form (as in the previous OS). I wish that Today was like other communicators.
3 - Start - which happened to all the sounds from the "Sounds and Notifications"?
4 - Software & others - as the 696 series have more memory, you can not throw out the program and plug-ins.
Waiting for a new version
Sorry for my English? i'm from Ukraine).
Click to expand...
Click to collapse
A few comments on your post:
1. I will check on the bluetooth situation. When I tested bluetooth, I didn't quite test file exchange enough.
2. I am working on a remedy/fix for the today screeen. However, I have no idea how long it will take for me to get it working.
3. This is just a matter of updating a few files. I used an older (and verifiably working) package to give non-phone support.
4. I am aware that the A696 and the later version of the A626 carry more flash rom space than the older version of the A626 and the A686. However, no matter what device I make roms for, there is a finite amount of space to fit everything into. As operating systems and programs progress, they get bigger and bigger. If everything keeps growing in file size, there is less space to fit more items, so I must remove some files/programs to keep within that finite limit of storage space. Where do all the files that I put into the rom go? Well, if you take a look at your storage memory, you will see that the total storage memory available is less than the standard 256 rom size.
I've downloaded and successfully flashed. Working good so far. I'm just installing some programs that I normally use and haven't run into an issue yet. It will be nice to have a working home screen but for now it isn't that big of a deal. I don't use bluetooth often so I can't comment on that yet. Wifi working, my music plays with S2P, I used windows market place to install netflix and office.
Keep up the good work!
Good job, but there are many failures to complete.
1) Today
2) Pictograms from former versions
3) "Sounds and Notifications"
4) Black pictogram Bluetooth in menu
5) When I close program - PDA show me Today(but must show menu)
6) Where is Oficce?
7) The pictograms not move in Start menu(only "Move to top")
Can you change your previous OS(WM6.1 rom version 2) context menu, pop-up menu and other for new from this OS?
P.S.: Sorry if you don't understand me I used translator...
Do you have french rom...?
Thank you.
just tested this build together with your WM6.1 release.
first impression - looks nice
even though seems slower on A696 - but this could be just because it's not tailored fully.
1) didn't test bluetooth much but seems to work fine with sending/recieving. I'd even say it's faster than on WM6.1 v2 release;
2) "Sounds and Notifications" problem with Events from previous v2 WM6.1 build;
3) under "System - Bluetooth" sometimes on BT icon there's black square - didn't notice when it happens though;
4) closing program throws you into Today screen insted of previous step;
5) same problem with Task Manager as I've said in previous thread for WM6.1
good luck
Hello, Steven!
I'm very thankfull to you for WM 6.5.
I have trouble, while installing, to say correctly, on the beginning of installing on my a626. I did everything as in instructions, even for few times. When i press power and enter button, make double tip on the soft reset, I see blue screen, where said sth about Cannes and its version.
it write my FAT type(FAT16), i see very little blink of "Reading file", if not take off fingers from power and enter button, it resets to blue screen again, if take fingers off the buttons, PDA loads...I just don't know what to do.. please, help me!
ps: sorry for my english.
I think I've found an issue. This morning when I turned on the device I had a missed appointment, the notification dialog at the bottom of the screen showed up but it was blank and had the wrong time on it. Not sure if this is a 6.5 issue or an Outlook 2010 issue.
bmasephol said:
I think I've found an issue. This morning when I turned on the device I had a missed appointment, the notification dialog at the bottom of the screen showed up but it was blank and had the wrong time on it. Not sure if this is a 6.5 issue or an Outlook 2010 issue.
Click to expand...
Click to collapse
Oh dear..I will be sure to check on that. As far as Outlook, do you mean Outlook on desktop Windows or Pocket Outlook on Windows Mobile? The only thing is that office (outlook) 2010 is still in beta and hasn't been released officially to the general public yet, so I can't find any definite fixes. I still believe you, but the fact remains that Outlook 2010 is still in beta and the code for the finished product could always change.
Steven, why have you ignored my message?
Hello, Steven!
I'm very thankfull to you for WM 6.5.
I have trouble, while installing, to say correctly, on the beginning of installing on my a626. I did everything as in instructions, even for few times. When i press power and enter button, make double tip on the soft reset, I see blue screen, where said sth about Cannes and its version.
it write my FAT type(FAT16), i see very little blink of "Reading file", if not take off fingers from power and enter button, it resets to blue screen again, if take fingers off the buttons, PDA loads...I just don't know what to do.. please, help me!
ps: sorry for my english.
Click to expand...
Click to collapse
I had the same issue. With a slightly modified .img ("replace:0xC 09 04 => 36 D6" by _barmaley; because I'm a new user I couldn't link the original post...) the update completed successfully.
PS: Steven thank you for the ROM!
Steven855 said:
Oh dear..I will be sure to check on that. As far as Outlook, do you mean Outlook on desktop Windows or Pocket Outlook on Windows Mobile? The only thing is that office (outlook) 2010 is still in beta and hasn't been released officially to the general public yet, so I can't find any definite fixes. I still believe you, but the fact remains that Outlook 2010 is still in beta and the code for the finished product could always change.
Click to expand...
Click to collapse
I am using Pocket Outlook, the new 2010 beta. But it doesn't seem to be related to that, if I make a Notification Dialog popup from something like turning off the A626 it gives me a blank white box. Now I've soft reset the device and it seems to have gone away. I'll keep trying to figure out how to recreate it.
First of all, thank you Steven855 for your job
Skromnjaga said:
1 - Bluetooth - does not work (does not receive or send files)
Click to expand...
Click to collapse
i have no problems with a bluetooth (i can send and get files from my nokia e60)
Skromnjaga said:
2 - Today - of all the elements shown only date and time, and only in the old form (as in the previous OS). I wish that Today was like other communicators.
Click to expand...
Click to collapse
Try to change values in System Registry:
HKLM\SOFTWARE\MICROSOFT\TODAY\ITEMS\Windows Live\Enabled (from 1 to 0)
HKLM\SOFTWARE\MICROSOFT\TODAY\ITEMS\Windows Live Search\Enabled (from 1 to 0)
make a soft reset, check(ON) your plugin in today's settings, make a soft reset
now i have a problem with a today's size (you can see a scrollbar at the right side of the today's area) but its a better as nothing
_barmaley said:
First of all, thank you Steven855 for your job
i have no problems with a bluetooth (i can send and get files from my nokia e60)
Try to change values in System Registry:
HKLM\SOFTWARE\MICROSOFT\TODAY\ITEMS\Windows Live\Enabled (from 1 to 0)
HKLM\SOFTWARE\MICROSOFT\TODAY\ITEMS\Windows Live Search\Enabled (from 1 to 0)
make a soft reset, check(ON) your plugin in today's settings, make a soft reset
now i have a problem with a today's size (you can see a scrollbar at the right side of the today's area) but its a better as nothing
Click to expand...
Click to collapse
Are you telling me this is how to fix the today screen issue? If it is (I still have to test it), I commend you for finding a fix that actually works.
Steven855 said:
Are you telling me this is how to fix the today screen issue? If it is (I still have to test it), I commend you for finding a fix that actually works.
Click to expand...
Click to collapse
yes, this is a tricks to fix the today screen...
i've tested it on my ASUS mypal a696 (but due to the fact that wm6.5 is not stable, I was forced to return to the WM6)
Is this all? Is there a step you're not telling me (I can't seem to replicate it)? What registry editor did you use? Did you use the (soft) reset button or did you use a program to soft reset the device?
Steven855 said:
Is this all? Is there a step you're not telling me (I can't seem to replicate it)? What registry editor did you use? Did you use the (soft) reset button or did you use a program to soft reset the device?
Click to expand...
Click to collapse
I edited the registry, because I was not able to check (ON/OFF) plugins in today's settings
i use resco explorer & reset button.
!!!!!!!!!Try to set ENABLE to 1 for your Plugin (HKLM\SOFTWARE\MICROSOFT\TODAY\ITEMS\"YOUR TODAY'S PLUGIN"\Enabled (from 0 to 1)!!!!!!!!!!!
what program can record video from screen PDA, I could write all steps
ASUS 696 owners please check and confirm the efficiency of the method.
what's the soft reset button on the asus a626? Not quite sure, the device reboots into OS D:
EDIT:NVM I got it, for ASUS A626 DEVICES, POWER OFF YOUR PHONE BUT DO NOT PRESS THE REBOOT KEYS. ONLY PRESS THE MIDDLE D-PAD BUTTON AND YOUR POWER BUTTON
Hello!
I am hapy to share this link that I just found!!!
http://www.attdroids.com/forum/motorola-flipside-forum/3230-froyo-2-2-2-a.html
So, seems that the dream of having some custom rom could be more possible...
Personally I would like to thank the Moto people that take care to make approval for make this beta possible and for sure to the original poster in the ATTDroids forum, marvin and the others that are already testing it.
I will also copy a instructions resume of him (marvin) in order to get an idea of the process:
"For the best result from this upgrade I suggest:
Backup all your data from your various apps
use an app to backup your text messages if you want to restore them
make sure that you calendar and contacts are up to date on google so that they can be resynced
Make sure that you have all of your usernames/passwords handy
Factory reset your phone to clear everything out
install update
Do another factory reset (probably not needed, but it will not hurt)
set your phone up from scratch (setting up your WiFi connection first will speed up the initial setup)
Doing a reset first makes sure that you have enough space and that you don't run into issues with misbehaving apps after the upgrade. When the backflip was updated many users ended up doing a reset to clear various issues after they upgraded and you should at least be prepared with backups before you start the process.
The first thing that Moto support will advise you if you have issues after the upgrade is to do a reset.
Be prepared for some of your apps to not show up in the market after the upgrade. This is not just a Moto issue, but an issue for any phone that undergoes an upgrade because the market signature changes.
Waiting at least a week after the general release and reading the questions/problems that show up in the forums (especially the Moto support forum) is a good idea to prevent any gotchas.
MotoBlur will try to restore some of your settings when you enter your username/PW. If you want a true fresh start set up a new MotoBlur account."
I downloading by now and for sure will be try it asap. I use linux, so I will also check the SBFFLASH utility that I already used in my XT720 before and will test if would work fine in recognizes the FlipSide (I almost sure that it will do, but I will report if this may helps since I found more easy to use SBFFLASH since I didnt requires any installation of ABD or other stuff, only the litlle binary excutable and run also from a Live CD).
sbfflash download:
http://blog.opticaldelusion.org/2010/05/sbfflash.html
sbfflash instructions:
http://blog.opticaldelusion.org/2010/07/new-sbfflash-features.html
the main advantage of sbfflash is that it could be used with the original Moto Bootloader mode that loads sbf so it will help with flash with original Moto 2.1 ROM and then with flash of Froyo 2.2 ROM beta
Best regards!
Ok, some feedback...
Well did my test, and the phone works fine and found some quirks so I worte them at the en of this post.Also, I had to use the instructions at this link in order to get the update.zip menu option (because Moto page with instructions on update are down by now, so I may suspect that is something goes wrong with moto providing us with the final update at least we already have this beta working for possible future custom roms...), so I will try to post a collected list of steps for easy on another friends around...
Detailed Step list for update (copy and collected of other posts):
A) Backup Existing Data:
A-1) Backup all your data from your various apps
use an app to backup your text messages if you want to restore them
make sure that you calendar and contacts are up to date on google so that they can be resynced
A-2) Make sure that you have all of your usernames/passwords handy
A-3) Factory reset your phone to clear everything out
by using Menu->Settings->Privacy->Factory Data
A-4) Reboot, enter nomal and set the phone in USB debug mode.
by using Menu->Settings->Applications->Development
A-5) Turn Phone Off
A-6) B) Get Original 2.1 Eclair SBF file:
SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0 R_PDS001_SAGEATT_P033_HWp4_1FF.sbf
form this link:
http://www.mediafire.com/?l7i266ugb3pklxk
C) Install Original SBF file for get Full Stock Android 2.1 base
with Flipside Bootloader Mode - Restore with SBF File
C-1) Power Down Phone
C-2) Open the keyboard
C-3) Press and hold the up arrow key (to the left of the OK key)
C-4) Hold the power button down
and Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using SBF_Flash in LINUX or RSDLite in window$.RSD Lite version 4.9 works with the Flipside
C-5) Let phone finish and reboot without disturb (flash process may take around 8-10min and reboot may take 4-5min first time)
C-6) Reboot, enter proper data keywords for gain acces to normal menu.
D) Get Froyo zip with name:Blur_Version.2.159.17.MB508.ATT.en.US.zip
D-1) Download from this link:
http://www.filesonic.com/file/1597204534/Blur_Version.2.159.17.MB508.ATT.en.US.zip
D-2) rename the zip file to update.zip and put in the sd card.
E) Install update.zip for Froyo 2.2.2
E-1) Power off your phone
E-2) Open the hardware keyboard
E-3) Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
E-4) Press the key labeled Fn (lower left corner of the keyboard in landscape, upper left in portrait) and the T key at the same time
E-5) You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
E-6) Repeat previous steps for clean cache if You want (I did)
E-7) Repeat E-5 steps for option update.zip, and it will look for the file update.zip in the sd card and then start the upgrade. Let this to finish without disturb around 10-12min.
E-8) When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone, the phone will take around 12-15min first time after upgrade the update.zip
F-9) Reboot and start with registering process normal
DETAILS FOUND! PLEASE READ!
1) It could not by now to get access again to Fn+T recovery menu after update.zip install!!!!, please help if somebody could find if there another key combination after froyo update or if may be something else.
2) The update DETECTS Non-Original batteries!!! I have 2 batteries for my FlipSide and I just found that one of then that I bought by Ebay is NON-original and now the phone do not recognizes none charges it also (the battery was labled as original ,and in fcat WORKS AND LOADS FINE in 2.1 previously the update.zip).
Hope may helps, so please share your info & details about.
Best regards!
I found this info on Motorola sight for froyo recovery for flipside. Hope this helps.
Froyo
Power off your phone
Open the hardware keyboard
Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
Press the Up and Down Volume keys at the same time
You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone.
How does this open up the possibilities for custom roms? Does this unlock the kernel or something?
pre4speed said:
I found this info on Motorola sight for froyo recovery for flipside. Hope this helps.
Froyo
Power off your phone
Open the hardware keyboard
Hold the X key and then hold the power button
When you see the Moto symbol you can release the power key
Hold the X key until you see a triangle with an exclamation point
Press the Up and Down Volume keys at the same time
You will now see a menu on the screen
Use the hardware keyboard cursor keys (lower left in portrait mode) to move the blue highlight to the various selections. You want to highlight "wipe data/factory reset"
Press the return key (to the right of the OK key with the phone in portrait mode) on the hardware keyboard to select the option that is highlighted.
Use the cursor keys to highlight YES from the next menu.
Press the return key to complete the selection
The phone will begin to reset. WAIT until it says it is complete
When it is complete you will see the the menu again, select "Reboot system now" with the cursor keys
Press the return key to reboot the phone.
Click to expand...
Click to collapse
Hi!
Thanks for the info, tested and IT WORKS so, return back to 2.1 SBF is possible in case (I found previously the info about Fn+T keys combination and it works on 2.1 but no in 2.2, so glad that this VolumeUP+VolumeDOWN keys is working)
About custom roms from this, I previously was using an XT720 (but really need the hardware Keyboard and 850Mhz 3g Band in my country) so I goot my FlipSide for a solution, but, as far I remenber, one of the big troubles previously to tht XT720 got 2.2 was the fact that were no release, so the process that the Dexter dev had to use was a long Hack&Test Roms and codes from other model until got one working.
IMHO the fact of have a beta ROM that have tthe native harware support for the FlipSide may could make more easy to get a custom or at least "Enhanced" ROM (aka... crapware free, and with some useful touches like removing crapware & locking things as battery detection, overcloking, swap, more memory swap utils compatibilty, EXT filesystem supports, etc), but I am not a dev, so this is IMHO. And also I am happy that this beat at least reach the comunity, since is suspecting for me why Moto shut down the page about offcial FlipSide update and no more annoucements...
Thanks to all and best regards!
I have received info from a reliable source that downgrading the Flipside from the not-yet-released (or after it's release) Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Here is part of the communication I received:
Just so you know AT&T devices cannot be flashed back(downgraded). It will likely brick them. I would urge strong caution when flashing SBF files
Click to expand...
Click to collapse
marvin02 said:
I have received info from a reliable source that downgrading the Flipside from the not-yet-released (or after it's release) Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Here is part of the communication I received:
Click to expand...
Click to collapse
If your talking about essentially following this guide twice, it will not brick your phone. I followed this guide, flashing to fresh 2.1 then upgrading to 2.2. Then did my cousins phone for him. Without thinking it would cause problems I used my motoblur login on his phone on the 2.1 step to make things faster (not having to ask his info) and afterwards my phone as flagged unassociated with motoblur that i needed to contact tech help. To save myself the time on the phone I simply followed this guide again... flashing 2.1 on top of my 2.2, then upgrading to 2.2 again. All works fine. That was 2 or 3 days ago.
boazjuggalo said:
If your talking about essentially following this guide twice, it will not brick your phone. I followed this guide, flashing to fresh 2.1 then upgrading to 2.2. Then did my cousins phone for him. Without thinking it would cause problems I used my motoblur login on his phone on the 2.1 step to make things faster (not having to ask his info) and afterwards my phone as flagged unassociated with motoblur that i needed to contact tech help. To save myself the time on the phone I simply followed this guide again... flashing 2.1 on top of my 2.2, then upgrading to 2.2 again. All works fine. That was 2 or 3 days ago.
Click to expand...
Click to collapse
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
boazjuggalo said:
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
Click to expand...
Click to collapse
Yea I just did this and now my phone is doing the same thing...we are indeed BRICKED!! I'm working to try to solve this problem too. Let me know if you find anything as I can't figure it out! I really want this unbricked...I can't do ANYTHING!!
Well, finally I was able to return here after several very busy and hurry days.... too bad the issue of the bricked phones... really bad also that the info about the bricking risk was leaked several days after the beta sbf was leaked and that some of us use it on our phones.
However, I wonder about, if somebody may knows what could be the instructions of Moto Devs to the official beta Testers, that were on the beta testing process, for update their beta phones to the official Froyo after Moto ends their beta testing process... I suppose that tehir could be the official instructions to this beta testers so make their phones to normal froyos.
Anyway, I will ask the moderator of this forum to please change add the word OBSOLETE to the title of this thread in order to avoid more bricking issues, since is all that I could do by know since I am not a programmer that could help more about how to revert bricked phone.
Good Luck and best regards!
boazjuggalo said:
Ok, so I just tried the official upgrade to the full (nonbeta) 2.2 on moto site.
Running the beta it shows that I did not have an available upgrade. So I went to flash back to 2.1 using the RSD method. I think my phone is bricked... RSD finishes like it normally does with no errors, but when it finishes and reboots the phone, instead of opening into the android OS it opens into a black screen that says
Bootloader
91.7B
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
As I said before, I did successfully do this one time, so it is possible but for me it was a 50/50 chance. Good luck and wish me luck finding a way to unbrick it.
Click to expand...
Click to collapse
Ok Bud just discovered someone got the bootloader and sbf for us to unbrick! Here you go!
Froyo SBF and Bootloader for Flipside MB508 AT&T USA
Bootloader: BL_917B_4G_sageemu_Consumer_replacer.zip
Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com
SBF Flash :
Android 2.2.2 ------ Blur_Version.2.159.17.MB508.ATT.en.US
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
Download SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz for free on Filesonic.com
WARNING: ONCE YOU FLASH THE FROYO SBF ANY ATTEMPT TO DOWNGRADE TO ECLAIR MIGHT RESULT IN A HARD BRICK !!!!!
These files are made available as a general courtesy and I assume no responsibilty for your own actions.
Thanks for share, very usefull, and in fact, I could use it with success. Best regards
Hi XDA geeks , pros and fans !
I'd like to start this new threadline concerning the freshly-appeared TCT MOVE handheld device marketed for the budget segment.As i understand it appeared in march or later this year and has quite good specs for the approx. 100 euro category.
Some details can be found on
http://alcatelonetouch.com/products/smartphones/move
Contrarily to some beliefs IT IS NOT a branded OT-908 ,rather a cosmetized one .It comes in black or silver / white , a bit heavy for it's size , and higher specs than the OT-908.
Concerning the hardware specs, i'll be coming back later with some accurate chipset and sensor details.For now
OS is Android Froyo v2.2.2.Looks like there will be official ROM updates,at the time being there is the OneTouch Upgrade v1.2 ,which downloads about 540 Mb chunked firmware files, and exits with error.
Memory is 512 Mb RAM , for user space is available about 300 Mb
512 Mb ROM flash, available to user about 160Mb.
SD card slot supports up to 32Gb MicroSD, the phone comes with a 2Gb one.
Camera is a 2.1Mpixel one.There is no secondary one,but the main camera is available for video calls,with Yahoo! Messenger i tested it myself.How to use it this way i will explain later.
GPS is amazing , if assistance software is used , the lock-on takes only seconds.
Sensors - linear acceleration sensor
- 3 axis orientation sensor
- 3 channel magnetic field sensor (digital compass)
- light sensor for illuminance detection
- optical proximity sensor , it seems not in use by operating system(or rather poorly)
Processor - 600 MHz Qualcomm ARMv6 compatible, min frequency is 122 Mhz, and deep sleep capability.Qualcomm MSM 7627 chipset
rooting ?
hi djada80.i should like to ask if you managed to root your phone ?
Yeah , it's quite simple.There are in the Android Market some free apps , i think the best which i also use is the one named Ginger Break.Just download and install it.Detailed usage info can be found here
http://forum.xda-developers.com/showthread.php?t=1044765
firmware upgrade
it seems that the branded ones somehow cannot be upgraded ! at this point i need assistance , so PLEASE , if there is anybody experienced in debranding Acatel smartphones, then YOU ARE MOST WELCOME !.I saw guys having problem with debranding T-Mobile Move , so let's DO IT !
cannot sync with windows
i cannot sync my tmobile move with windows.have a toshiba satellite c665 with win 7 .pls help !
connect phone to computer,enable usb tethering.install alcatel android manager on computer. Can be found here
alcatelonetouch.com/contents/download/T-Mobile_AndroidManager_2.2.1108.1645.rar
This should work,instead of Android Sync Manager WiFi ,the last has some issues with this phone ,do not use it.
Yahoo! messenger front camera
Contrarily to some beliefs THERE IS POSSIBLE TO MAKE VIDEO CALLS with front camera only on Froyo 2.2.It is quite simple:
1.) if you have any version of yahoo apps , remove them all
2.) install Y!Messenger v1.3.2 , the afferent audio and video plugin and
optionally Y!Mail v1.3.2
Nothing fancy with it , just works.Remember, DO NOT UPDATE from Market.
Might also check this,if it doesn't work
http://forum.xda-developers.com/showthread.php?t=1087769
remove bundled apps ?
Hi !
Is there a way to remove some of the unnecessary factory shipped apps ?
RE
Yes , there is. So the smart method vould be to remove them from phone memory , and eventually install it on SD Card , if they are (and they are) UNMOVABLE.
Or just leave them ,anyway a factory reset will restore all the shipped applications.
1.) [optional] install Android SDK with platform 2.2 , sdk tools and eventually drivers.Enable USB debugging on device.On PC launch command prompt and change directory to \Android\android-sdk\platform-tools\.Run command
adb shell pm setInstallLocation 2
This enables SDCARD installation by default.Prerequisits to have ROOT ACCESS.
2.) with RootExplorer simply delete unwanted applications from \custpack\apps\ on device.Optionally you can make backups.
3.) if you made backups , the backed-up apk can be used to be reinstalled , NOW ON SD CARD
Good luck.
RE again
A reboot of the device is required to cleanup the junk after a forced delete.Or it can be done manually , BUT USE CAUTION.
i have an alcatel move branded Cosmote Move, i like this phone very much but i`ve managed to brick it the second time, first time i bricked and took it to waranty, they reinstall the software free of charge, now it has the same simptoms (pass the carrier logo and get stuck to carrier animation) and i need to send it to waranty again. i dont manage to get it unbricked. i`ve root it with gingerbreak but this phone doesnt go to recovery mode. i`ve searched the internet and google it for hours, but nothing.
if anyone knows how to do it please tell me, in the user manual says hard reset vol - and power, get stuck whit touch buttons light up and screen black!!
thanks in advance
re Themaster
it's not a brick yet i suppose , though you didn't specify how you managed to "brick" your phone.a nice clean reflash would solve the problem , probably you deleted some system files while in root mode.again did you use root explorer or something similar ?
try a factory reset as it follows:
1.) turn off the phone
2.) press vol up and the power on and hold the buttons pressed for about 1 minute
3.) the phone boots up , android logo appears and then an animation with some sort of thrashcan or whatever
4.)wait until it finishes , then the phone shuts down automatically.power on the phone and it will be restored
Beware ,battery must be at least 70 % charged or kept in charger , NOT USB connected to PC.
This restores phone to factory state , but not all the applications from /custpack/apps
Best regards !
Useful Key Combinations
These keypress modes apply on a shut down phone
Hard Reset - reinstalls android core system from ROM , deletes user data and misconfig
key combo : vol up + power on long pressed until trashcan animation appears
Flash Mode - used for ROM update , useless momentarily
key combo: vol down + power on long pressed , black screen appears and touch buttons lit up
Root access , mount filesystem with root access ,DANGEROUS !
key combo : home + power on long pressed until boot
build environment under Ubuntu
Lately, there has been some problems setting up an Android build environment under Lucid Lynx, as i've seen many have been complained for the missing java5 jdk.
For Romanian users: seems to be a problem with the Romtelecom DNS servers , when adding Jaunty or Dapper repositories to Lucid.
Use Google DNS as alternatives 8.8.8.8 and 8.8.4.4.This works.
From what I've been able to determine. The move and 908(s) are the same hardware with with only cosmetic differences. Something is different in software, I've been unable to root my 908s with ANY tools I've found.
I was also unable to use ADB under windows. The handset apparently requires four drivers, I was only able to find three of them. I got the Alcatel tools to work, as well as tethering, but no ADB. i didn't have any such issues under Ubuntu, but without root it isn't helpful.
I could not locate a stock rom or source anywhere on the Alcatel sites, so I sent a GPL request, i'm waiting to hear back.
UPDATE
After a long night I managed to root my 908s. I'll write out the jist of it, but I was flying by the seat of my pants, fueled by caffeine and sleep depervation. DON'T consider this a HOWTO.
First off, to the best of my knowlage there is no one click solution as of yet. As I said before still missing the driver that makes ADB work in windows, and handset based solutions didn't pan out. A little reasearch showed that the OT-990 has the same chip/ram and ROM space as ours. The screen is bigger, and I don't know what board is in it, but on a hunch I figured it was close enough. So I went here: http://forum.xda-developers.com/showthread.php?t=1164391 in the hopes that some sort of combined effort in future ROM development would be possible.
Yes that's right folks its a guide to MANUALLY root you handset with ADB. So not for the faint of heart. I didn't have high hopes, as issuing ls -l on either the sqlite folder or data threw a permission denied. So blindly I tried to push psneuter, busybox and su to /data/local. I almost fell off my chair when it worked! from there I used psneuter to get ADB into root, and managed to get the su binary to /system/xbin, and Superuser into /system/app. Superuser was installed, but still no root. So I checked out Root Checker to see what was going on. There are three places that su typically lives; /system/xbin, /system/bin, and /sbin. So I tried to put su in those folders. I got it into /system/bin but sbin is mounted read-only. I did not remount any directories, as the instructions are lacking syntax (I'm a little rusty with advanced mounting commands). I think things are mapped a little differently anyway. I still did not have root on the handset, so I then fired up Superuser to see what it could see. It saw the su binary, even though it wasn't working right. Then I thought well if it can see it, then maybe it can update and fix it. Sure enough after running the update to su in Superuser, (drumroll please...) I had working root.
So that's my story so far, I'm gonna give Alcatel a week or so to reply to my request. Then we'll take it from there. (Hey it worked on Huewei right?)
If a real dev should come across this, feel free to jump in. Its a solid little phone and has the potential to work on a range of handsets.
Gratitude
Thanks snkiz for your attention ! I am pleased that someone 'heavy' noticed my efforts of dedicating this threadline to the newcomer ! Indeed a small little phone with potential , maybe in time we get it gingerbread , cupcake ( or whatever ),even wm6.5 or 7 ...
As of ADB drivers , i had ADB from the first by these steps:
1.) http://www.alcatelonetouch.com/contents/download/move upgrade 1.2 Setup.rar , package contains the drivers
Now i noticed that when i try firmware upgrade , the utility downloads about half a giga of *.bin files and then exits with 'download failed error'.
2.) installed Android SDK , platform tools and Google drivers (i am not sure if necessary), the 2.2 platform (api 8)
Under Win7 cmd in platform tools , adb shell , su and on device pops up 'unknown has been granted superuser rights' and voila! in cmd shell i have '#'.Previously installed Gingerbreak.
My device is a Cosmote Move.
Ya, no I got that file too. I think they are "consumer drivers" because like I said I got all the Alcatel tools running but on my win 7 one driver was still missing, and I have pretty good googlefu. effin hate windows, this is why. I'm by no means a "heavy" but I am comfortable in a Linux environment, that helps alot. As to you being able to get gingerbreak to work, i'd bet that comes down to carrier firmware.
---------- Post added at 06:53 PM ---------- Previous post was at 06:39 PM ----------
djada, seeing as your the op could you please re-tag the thread with the model numbers to make it easier to find? cosmote, 908, 908s, and qualcom should do.
perhaps a mod could move this thread to the android hacking forum where it can get the proper attention please?
ADB driver
Driver files are from WHATEVER.\android-sdk\extras\google\usb_driver\ , if does not install automatically , can be forced.Anyway Win$ux 7 detects ADB interface , installs some sh.t from windows update server , and you'll have an ADB interface in Device Manager (working or not).Try to force the google drivers.
On the other hand ,i'm sorry but dunno how to move the thread , maybe i should start a new one in
http://forum.xda-developers.com/forumdisplay.php?f=565&order=desc&page=552
Just looked at it and they don't have Alcatel
Mod
Just started workin on a Cyanogen build , if i manage to build at least a kernal img , maybe i can lure in the Koush guy from github.We are in need of flash , backup , recovery tools.Not as lucky as the Samsung or HTC guys ...
While the Nokia Lumia 530 isn’t officially supported, it’s still possible to get Windows 10 mobile running on it. At the time of writing, it has become a bit tricky to get it to work, since most official Microsoft tools are discontinued and will therefore not work. I will be linking the files which I’ve used. The credits to the people who made or shared the tools and guides I used will be at the bottom of this guide.
Note that I am not responsible for any damage made. Proceed at your own risk!
Prerequisites:
- A Nokia Lumia 530 running the Windows 8.1 Denim Update (will be referred to as "device")
- A stable Windows 7 system or VM, with .NET Framework 4.5.x or 4.6.x (on Windows 10, the IUTool will fail to synchronize, hence this requirement)
- An internet connection that can handle a download of approximately 2GB data on the computer and about the same on the phone
- A good USB cable (a flimsy one with a loose fit could brick the device while it’s updating)
- The programs linked below
First part of the installation:
1. Make sure the device is fully charged. If it’s not fully charged the device could get (soft-)bricked.
2. Factory reset the device, so you have as much storage as possible available on the device. After the reset is done, leave it at the language selection screen, because it doesn’t do anything there.
3. Extract HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z with 7zip or whatever you prefer.
4. Download the Visual C++ libraries from here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ and run the install script.
5. The next thing you are going to do is download the updates, push them to the device and install them. This will take some time, but it depends on your internet connection for the most part. The files will be downloaded from the official Microsoft servers. Now here’s what to do: open run_en.cmd and follow the steps. These are pretty clear, so I don’t think I need to point all of them out here. It will open a webpage where you can download WDRT, you will need to install that for the tool to work.
6. Now you can move on to the second part.
Second part of the installation:
In this part of the installation, you will be updating the device from version 1511 to the latest available build, which should have a working Microsoft store.
1. The setup of the device. The version that just got installed doesn’t have a lot of options yet, including language packs. If you have a device that’s not English United States, the keyboard will bug out on setup, because it’s trying to access a language pack that doesn’t exist. Therefore, the first step, setting the language should be English (United States), so the OS itself won’t bug out. Once you’ve set the language (it will prompt to reboot, do that), you can go through the rest of the setup. Don’t log it into your Wi-Fi, don’t log it into your Microsoft account and don’t turn on automatic app updates. It’ll say it needs to set up apps, that takes some time but eventually you’ll get to the home screen. Now is when you need a few tools, which brings us to step 2.
Now is a good moment for me to point out that, if you have a non-English-US device, the keyboard for another language is still "installed". It can be removed by holding it in settings -> time and language -> keyboard and choosing “Delete”.
2. Installing Interop Tools. In order to get updates, you’ll need to modify your device a bit. This won’t be very hard, but it involves some registry modifications so you’ll have to pay close attention.
Go to settings -> update and security -> for developers and enable developer mode, so you can sideload the Interop Tools (Linked below). Copy the contents of the Interop Tools zip to the device first. Then, go to the file manager on the phone and go to the directory where you put the files. INSTALL THE DEPENDENCIES IN THE \ARM FOLDER FIRST, THEN THE INTEROP TOOLS FILE ITSELF! Check if the Interop Tools installed on the “all apps screen” and get ready to open it.
3. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
3.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Then, put PhoneManufacturerModelName in the “Registry Value Name” box and tap the “Read” button at the bottom. You’ll see some text appear in a box. This will need to be edited to the following value: RM-1089_1048. After you did that, tap the “Write” button.
3.2. Now put PhoneModelName in the the “Registry Value Name” box and tap “Read” again. Now change the value to Lumia 535 and tap “Write”.
3.3. Exit out of Interop Tools and go to the next step.
4. Logging in to the Wi-Fi and checking for updates.
4.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
4.2. Checking for updates. This is the part that always went wrong with me, because of storage limits (gotta love that 4GB eMMC). But if I’ve explained this well enough, you might not have to do a lot of weird stuff. Oh well, to the instruction we go. Go to settings -> update and security -> windows update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got two updates: from 1511 to early 1607 and from that to late 1607. Maybe you can get a newer version with WDRT or OTC but I doubt that to be honest.
Hooray! Now you should have a fully functional Nokia Lumia 530 with Windows 10 mobile!
Credits:
nemesis from Realmtech (for the registry changes) (https://www.realmtech.net/user/1)
@hikari_calyx (for the semi-offline update tool)
@STALKER18 (for the tips on how to clear storage)
@gus33000 (for the Interop Tools)
My dad (for the device)
Everyone who encouraged me to do this mod
Files:
Interop Tools: https://forum.xda-developers.com/attachments/interoptools_rc2_1-9-400-0_arm-zip.3995811/
And it's dependencies: https://forum.xda-developers.com/attachments/dependencies_arm-zip.3995814/
Windows 10 mobile semi-offline updater: https://forum.xda-developers.com/attachments/hctsw_wxmsoup_v5-3beta6-update-lzma2-7z.4955261/
PS: If you brick the device, the WDRT can restore it. If it just puts it in flashing mode, you can use Windows Phone Internals to download and flash a ROM. That tool can be found here: https://www.wpinternals.net/index.php/downloads/doc_download/46-wpinternals-2-8-zip
[ADDITION] Updating from build 1607 to 1709.
I said it wouldn’t be possible and it would break stuff, but I tried it and it doesn’t break anything some people say it might break. Yeah, it might impact on battery life a bit, but nothing has broken for me (yet), it has only improved.
I’ve learned that the update from 1607 to 1703 is the hardest one yet, but you should be able to get it going. This is because the preinstalled Store in 1607 can connect to the app update servers, but it can’t view the app. This is a difficult situation because many apps will become very large when they get updated. You need to figure out for yourself what gets you the space you need, but I found that uninstalling all the apps that can be uninstalled and deleting system apps through MTP (which can be done by bootloader unlocking, rooting and booting into mass storage mode with Windows Phone Internals (I recommend that you only delete OneNote, SkyDrive (as it’s being referred to in /data/program files/windowsapps) and the Xbox app).
Step 0: you might want to factory reset first
Let’s get to the updating though…
1. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
1.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Now do the exact same as you did before, except use these “registry value names” and put the corresponding information into the box below that. Don’t forget to tap write!
Values you should use:
PhoneHardwareVariantRM-1104PhoneManufacturerMicrosoftMDGPhoneManufacturerModelNameRM-1104_11210PhoneModelNameLumia 950
1.2. Exit out of Interop Tools and go to the next step.
2. Logging in to the Wi-Fi and checking for updates.
2.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
2.2. Checking for updates. Go to settings -> update and security -> Windows Update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got 3 updates, one from 1607 to 1703, one from 1703 to 1709 and another one from old 1709 to last 1709.
Credit to @demon2112 for the registry values
Can you backup your efiesp.bin partition and share?
augustinionut said:
Can you backup your efiesp.bin partition and share?
Click to expand...
Click to collapse
Did you break it?
Edit: WPInternals refuses to put the phone in mass storage mode so uh... Yeah...
I managed to get them off with Interop Tools
How?
augustinionut said:
How?
Click to expand...
Click to collapse
In the Interop Unlock menu, there's a mount entire storage option. Copied the EFIESP from there and compiled it into a bin. For WPI the Windows on the phone is too new :/
Thats why didnt worked
I wanted dumped partition with, WPInternals.
augustinionut said:
Thats why didnt worked
I wanted dumped partition with, WPInternals.
Click to expand...
Click to collapse
Yeah that doesn't work. Rename the .bin to .zip, extract, mount the phone in mass storage mode and copy the files to the EFIESP folder/symlink. If you can't do that, WDRT can probably unbreak it
Please anounce me when you can upload the dumped partition.
Is resulting that efiesp.bin , data.bin and mainos.bin are related, so i cant upgrade my phone to windows 10 mobile without them.
augustinionut said:
Is resulting that efiesp.bin , data.bin and mainos.bin are related, so i cant upgrade my phone to windows 10 mobile without them.
Click to expand...
Click to collapse
Just flash the original FFU. Literally all I did is in the guide and I never had to flash something from another device
Thanks, but: my phone was reflashed with reset protection active. Guess what?
augustinionut said:
Thanks, but: my phone was reflashed with reset protection active. Guess what?
Click to expand...
Click to collapse
Something that might work (according to a friend. Again, I am not responsible for a phone that gets rendered useless)
Mount as mass storage, diskpart clean the thing, hold power button for ~10 seconds, flash a bootloader with WDRT (may fail 2-3 times), flash FFU
_Yep, erase clean DPP partition )) buhahahaha
How do you get to the Denim update? I'm getting the error that I am running a build older than 8.10.14219.341 and need to update first.
EirikrHinnRauthi said:
How do you get to the Denim update? I'm getting the error that I am running a build older than 8.10.14219.341 and need to update first.
Click to expand...
Click to collapse
You can download and flash it in WPInternals (will delete all data so back that up first) or WDRT (not sure if that erases userdata)
BennoMP said:
You can download and flash it in WPInternals (will delete all data so back that up first) or WDRT (not sure if that erases userdata)
Click to expand...
Click to collapse
WDRT already says I'm at the latest version of Windows for my device, so that sucks. I shall try WPInternals! Thanks!
Would you please transfer a video of the process?
BennoMP said:
While the Nokia Lumia 530 isn’t officially supported, it’s still possible to get Windows 10 mobile running on it. At the time of writing, it has become a bit tricky to get it to work, since most official Microsoft tools are discontinued and will therefore not work. I will be linking the files which I’ve used. The credits to the people who made or shared the tools and guides I used will be at the bottom of this guide.
Note that I am not responsible for any damage made. Proceed at your own risk!
Prerequisites:
- A Nokia Lumia 530 running the Windows 8.1 Denim Update (will be referred to as "device")
- A stable Windows 7 system or VM, with .NET Framework 4.5.x or 4.6.x (on Windows 10, the IUTool will fail to synchronize, hence this requirement)
- An internet connection that can handle a download of approximately 2GB data on the computer and about the same on the phone
- A good USB cable (a flimsy one with a loose fit could brick the device while it’s updating)
- The programs linked below
First part of the installation:
1. Make sure the device is fully charged. If it’s not fully charged the device could get (soft-)bricked.
2. Factory reset the device, so you have as much storage as possible available on the device. After the reset is done, leave it at the language selection screen, because it doesn’t do anything there.
3. Extract HCTSW_WXMSOUP_V5.3beta6.update.lzma2.7z with 7zip or whatever you prefer.
4. Download the Visual C++ libraries from here: https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ and run the install script.
5. The next thing you are going to do is download the updates, push them to the device and install them. This will take some time, but it depends on your internet connection for the most part. The files will be downloaded from the official Microsoft servers. Now here’s what to do: open run_en.cmd and follow the steps. These are pretty clear, so I don’t think I need to point all of them out here. It will open a webpage where you can download WDRT, you will need to install that for the tool to work.
6. Now you can move on to the second part.
Second part of the installation:
In this part of the installation, you will be updating the device from version 1511 to the latest available build, which should have a working Microsoft store.
1. The setup of the device. The version that just got installed doesn’t have a lot of options yet, including language packs. If you have a device that’s not English United States, the keyboard will bug out on setup, because it’s trying to access a language pack that doesn’t exist. Therefore, the first step, setting the language should be English (United States), so the OS itself won’t bug out. Once you’ve set the language (it will prompt to reboot, do that), you can go through the rest of the setup. Don’t log it into your Wi-Fi, don’t log it into your Microsoft account and don’t turn on automatic app updates. It’ll say it needs to set up apps, that takes some time but eventually you’ll get to the home screen. Now is when you need a few tools, which brings us to step 2.
Now is a good moment for me to point out that, if you have a non-English-US device, the keyboard for another language is still "installed". It can be removed by holding it in settings -> time and language -> keyboard and choosing “Delete”.
2. Installing Interop Tools. In order to get updates, you’ll need to modify your device a bit. This won’t be very hard, but it involves some registry modifications so you’ll have to pay close attention.
Go to settings -> update and security -> for developers and enable developer mode, so you can sideload the Interop Tools (Linked below). Copy the contents of the Interop Tools zip to the device first. Then, go to the file manager on the phone and go to the directory where you put the files. INSTALL THE DEPENDENCIES IN THE \ARM FOLDER FIRST, THEN THE INTEROP TOOLS FILE ITSELF! Check if the Interop Tools installed on the “all apps screen” and get ready to open it.
3. Modifying the registry. Open Interop Tools and tap the “This Device” button. This will bring up a menu.
3.1. Tap the menu button on the top left corner, then select “Modify Registry”. In the “Registry Key Path”, put SYSTEM\Platform\DeviceTargetingInfo. Then, put PhoneManufacturerModelName in the “Registry Value Name” box and tap the “Read” button at the bottom. You’ll see some text appear in a box. This will need to be edited to the following value: RM-1089_1048. After you did that, tap the “Write” button.
3.2. Now put PhoneModelName in the the “Registry Value Name” box and tap “Read” again. Now change the value to Lumia 535 and tap “Write”.
3.3. Exit out of Interop Tools and go to the next step.
4. Logging in to the Wi-Fi and checking for updates.
4.1. Logging it in to the Wi-Fi. Go to settings -> network & wireless -> Wi-Fi and choose your network. Easy peasy probably.
4.2. Checking for updates. This is the part that always went wrong with me, because of storage limits (gotta love that 4GB eMMC). But if I’ve explained this well enough, you might not have to do a lot of weird stuff. Oh well, to the instruction we go. Go to settings -> update and security -> windows update and check for updates. This will take a while! Keep it on wall power because updating can only be done at 40% or more at this point. I got two updates: from 1511 to early 1607 and from that to late 1607. Maybe you can get a newer version with WDRT or OTC but I doubt that to be honest.
Hooray! Now you should have a fully functional Nokia Lumia 530 with Windows 10 mobile!
Credits:
nemesis from Realmtech (for the registry changes) (https://www.realmtech.net/user/1)
@hikari_calyx (for the semi-offline update tool)
@STALKER18 (for the tips on how to clear storage)
@gus33000 (for the Interop Tools)
My dad (for the device)
Everyone who encouraged me to do this mod
Files:
Interop Tools: https://forum.xda-developers.com/attachments/interoptools_rc2_1-9-400-0_arm-zip.3995811/
And it's dependencies: https://forum.xda-developers.com/attachments/dependencies_arm-zip.3995814/
Windows 10 mobile semi-offline updater: https://forum.xda-developers.com/attachments/hctsw_wxmsoup_v5-3beta6-update-lzma2-7z.4955261/
PS: If you brick the device, the WDRT can restore it. If it just puts it in flashing mode, you can use Windows Phone Internals to download and flash a ROM. That tool can be found here: https://www.wpinternals.net/index.php/downloads/doc_download/46-wpinternals-2-8-zip
Click to expand...
Click to collapse
Hello! I followed your step with editing values and after checking updates, there was an update which is Windows 10 Mobile (10.0.14393.1066) as of now, May 2022.
my question is what is the size of this update? and will I able to install this with my Lumia 530?
any other way to install this offline? i really need this update because I need working Microsoft Store.
Thanks...