OBSOLOTE! Official Release available!...FlipSide MB508 FROYO MOTO beta ROM!!! :-) - Flipside Android Development

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

Related

Need desperate help with possibly bricked Diamond

Hi all,
Just received my Vodafone-branded Diamond, and I'm afraid I already managed to brick it!
It was equipped with version "1.37.172.3 NLD" so I decided to upgrade it to the latest version.
The installation of OliNex Hard-SPL 1.93 went flawless, but the installation of ROM "RUU_Diamond_HTC_WWE-ME_1.93.456.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe" stopped at about 25% with error code 302. The recovery method that came with the package didn't help, every time the upgrade stopped at the same moment.
Since the device is stuck in the bootloader, and I'm left with a non-chargeable battery, I tried the official Vodafone-branded "RUU_Diamond_Vodafone_NL_1.97.172.4_Radio_Signed_Diamond_52.44.25.24_1.08.25.08_Ship.exe" ROM. Unfortunately, this upgrade stops at 48% and throws the same 302 error.
Anyone who can tell me what I'm doing wrong, and what I can do to solve all this?
I hope I don't have a brand new, but bricked device on Christmas!
TIA and have a nice day.
Try a hard reset first. If this doesn't help google or search at XDA for MTTY.
This tool can fix your device
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Stuck_at_bootloader
Try this, maybe will work
Try a Vodafone branded stock rom before mtty.
Regards,
Carty..
He already tried a stock rom....
Potential Solution
Have you looked at the thread titled,
[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)
It may just be a model ID glitch that can me fixed.
Take a look. It's in this forum in a sticky by cptsunshine.
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Besides, the bootloaders says upgrade ROM code error please try again.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Install Rom via Internal Memory Method
Steps from Suiller:
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
Let me know how it goes.
Make sure you have Net framework 3.5 installed on devices.
Nakkie27 said:
Thanks all for the help, I'll have a look at your suggestions.
The problem isn't that it stops at 0% or 5%, it stops at random percentages (depending on the ROM I use).
I also see the bootloader (red / green / blue), so it's not dead. I guess it's just that it doesn't pick up a ROM.
Edit:
A hard reset doesn't seem to work. In the bootloader, when I press "volume down" and "enter" together, and press the "reset button" the screen goes black, but then goes back to the bootloader screen after a sec or 2.
Edit 2:
MTTY doesn't do much either, after executing "boot" the phone is showing me the Vodafone logo and that's it.
For the rest, MTTY shows me the following:
Cmd>boot
InitDisplay: Display_Chip=1
dwDirectNum: 0, dwMatrixNum: 0, dwMicroPNum: 0
Fixed new dwPSImageSize = 0x53E0000
Click to expand...
Click to collapse
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
band27 said:
Steps from Suiller:
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!
Click to expand...
Click to collapse
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
janielsen said:
u can do one thing then press woluem down and reset bottom at the same time then u go to rescue mode then u wait and put in the usb stick and there stand seriel when u put in the cable it will change to usb thenu can load the firmware again
Click to expand...
Click to collapse
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Nakkie27 said:
I wish I could mate, but I cannot put files on it anymore, since ActiveSync doesn't recognize my device when it's in the bootloader.
Can you please be more specific? Are you telling me how to do a hard reset? I tried as to do a hard reset, but it goes back to the bootloader instead of resetting. USB stick?
Thanks all, much appreciated. A pain this can happen, looking at the fact that I did everything exactly as described in all these flashing manuals.
Click to expand...
Click to collapse
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
janielsen said:
first push the volum down buttom at the same time press the reset buttom then the 3 color display will appear and in the buttom will stand seriel then u putt in the usb cable to ur phone whit u have attact to ur pc then it will say usb now u can load new firmware
Click to expand...
Click to collapse
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on, and I can't get a USB-connection.
Edit:
Volume down + reset brought me in the bootloader again, although it's saying SPL-1.93.OliNex.
Nakkie27 said:
No mate, I never had problems getting into the 3 color screen. The problem was updating afterwards, which never completed without error code 302.
Anyway, I guess I just fully bricked my device after putting SPL-1.40.OliNex (according to the guide at http://forum.xda-developers.com/showthread.php?t=416211) on it. The SPL install was succesful, but when booting I'm now not even getting to see the 3 color bootloader. All I see is the Vodafone logo with some version numbers at the bottom, but that's it. It doesn't boot further on.
Click to expand...
Click to collapse
that i know but as i say in the post that when u do it that way i say u can load new firmware whitout it needs to boot try my friend i have done it 3 times because wrong loading of firmware
u have to only push thoose 2 buttom then it will work because u go to rescue mode
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Nakkie27 said:
But what will that give me extra? I can access the Hard-SPL 1.93 bootloader (3 color screen), and I can get into USB mode. It's just that the upgrade of both firmwares stop at a certain percentage.
I'm constantly trying to hard reset the device, but after pushing the reset button (with both volumn down + enter pressed down), the device just reboots back into the bootloader and doesn't give me the hard reset warning.
Click to expand...
Click to collapse
u need to hold them down until it leave the 3 color display an turns into grey
Ok, finally managed to do a hard reset. Afterwards I tried upgrading to the official Vodafone NL 1.97 ROM once more, but it failed at 48% again.
Any ideas what to do? I know have Diamond with Hard-SPL 1.93 (which says upgrade ROM code error) with no working OS.
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Hi all,
I have a quit similar problem. I've read a lot, but couldn't find an answer to my problem - may bye someone can help me.
I updated my Dimond (OliNex Hard-SPL 1.93, radio 1.09.25.23 and rom dutty V4). When I start my phone most of the time (95% plus) I end up in the color screen - however some time it's starts perfect (without changing anything).
When I get stock in the color screen, I can start the phone with mtty and the command "boot".
What can I do to make my phone always start in the normal way?
Thanks!
Nakkie27 said:
Ok all, got it finally working again!
Don't ask me why, but flashing the newest Dutty ROM (and the included radio) did work.
Thanks for all your help, and a wonderful evening!
Click to expand...
Click to collapse
i smell a radio issue - last time i was trying to upgrade my radio - ended up with something similar, managed it out like you did - but now you're up - so that's good!!
try some other rom (this time without radio) - i don't think you should have any issues going forward... good luck and have fun!

Official Diamond ROM 2.03 update - HELP

Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Same Thing happened to me :S wtf??
xevier69 said:
Hey guys,
I have no idea what's going on. I appreciate your suggestions. I flashed my Diamond many times (and other phones as well) with most of the ROM available. Unit a month ago or so I've been using the official 1.93 ROM with previously installed hard SPL 1.40. When I attempted to install a new 2.03 ROM I went through the whole procedure same way as always with a little exception. Right after completion - 100% the unit reboots, shows the rainbow screen with a message "Upgrade ROM code error" - try again. What is the world is this? I also have a message on my desktop "Error 270-update error" - The image file is corrupted. My unit is european and I downloaded the ROM from both US and Euro sites. From this point I managed to downgrade again to version 1.93. Then I ran again the hard SPL 1.40 and reattempted to upgrade to 2.03 - SAME THING!
I don't know what to do next. Why I cannot flush it with the latest ROM? Any ideas or similar situations? Please see picture.
Thanks
Click to expand...
Click to collapse
Hi have you tried to flash from the internal storage?
Have you tried flashing with internal storage method?
Exactly the same problem here, so I tried to flash to a really old original HTC ROM after the failure and it flashed fine
So I thought I would try upgrading over the top of an original ROM, had the same error , bloody HTC
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Though I bricked my phone when it happened, never seen that error before despite many ROM flashes
I have now tried tommytaos ROM which is supposed to be very close to the original but some with some tweaks.
http://forum.xda-developers.com/showthread.php?t=479049
It installed just fine on my phone. Seems HTC have broken their ROM
xevier69 said:
So, any ideas how to resolve this issue? Are we stuck with the old ROM? I'm glad that I'm not the only one experiencing the same problem.
No, I have never tried to flash from internal storage. How can this be done? do I copy the whole .exe file to storage and run from there? Any pre-cautions?
Thanks
Click to expand...
Click to collapse
it's the best way to flash the rom and the safest...
From Suiller thread:
the standard procedure to cook a ROM is made trough activesync program, I mean that the .nbh file is pushed into the phone trough activesync, across the usb cable, but this procedure can give some troubles:
1. it takes long time, about 10 minutes
2. it's a bit unsafe (even if the procedure can be always restored safely)
3. it's possible only with Windows OS (NO Linux nor *BSD, et cetera...)
I don't know why this is not well known but ALL producers (like HTC) give the possibility to upgrade the rom/firmware without having MS windows (thanks GOD someone knows that there aren't only windows users).
This faster procedure can be done also with *nix variants (or whatever you use) because the ROM update is made directly by the phone.
The procedure is very simple, it will take just 2 minutes, can be done everywhere & is good for cooking radios too (very fast in this case)
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
notes:
* be sure to have at least 10/20% of charge, anyway the whole procedure will take about 2 minutes, so you must be ensure that your mobile will stay turned on for at least those 2 dirty minutes (just in case you can attach the power AC/DC too), don't panic if something goes wrong... read few lines below
* like told you above the same procedure is good for cooking Radio too, of course Radio are smaller and it will be really fast (about one minute!)
* you don't need windows anymore or activesync, is enough just to copy the file into the storage card (transfers WITHOUT activesync are faster)
* it's possible to make a reset simply by getting off the stylus and pressing the small red button under the stylus carrier
* don't worry if something goes wrong... any cook failure can be always restored, the important thing is that you don't fail hardspl flash... but you have to do it just one time in your life
special note about hard-spl:
if you have signed-only hard-spl I strongly suggest to upgrade to an un-signed one, personally I tested many & I can confirm that the "good ones", at least in my experience, are the Olinex 1.37 or 1.93, you can find a copy here
remember also that you can NOT brick your device if you have a good hard-spl (like the ones I mentioned above) & flashing directly from phone is really faster (also good for flashing radio)
so the only one thing you should take care is when you change/upgrade the hard-spl, but you have to do this step just once, I'm using this hard-spl from about 6 months & I was able to flash everything (plus dozen recovers for failed flash)
for rom/radio upgrades you can safely also reboot/remove cable/turn off your phone while flashing ...every lost flash can be always restored safely, it's enough to restart your device in boot mode & restart flashing, also with cable trough the classic RUU (to put device in boot mode simply reset & keep pressed Vol_Down button)
In the hope this procedure can be useful at least to save time
if you have the official rom which is a exe file you can extract the rom file using winrar.
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Flashing using the Internal Method is the safest and most convenient way to flash. Spread the word.......
xevier69, Thanks for your thread
Having just purchased Oli's security unlocker... I was annoyed about this problem with a HTC official rom!
But your method has solved this issue!
Thanks again
Thanks guys it works perfect!
This just happened to me too and the only roms i have ever flashed:
1.37 official spanish: came with the phone
1.37 official WWE
1.93 official WWE
and now 2.03 official WWE fails.
WTF... One would expect the upgrade not to fail, right?
I wonder if they are checking for HardSPL to be original too!?
Anyway thanks for the workaround
This worked for me to
Cheers
xevier69 said:
EUREKA!!! Done Deal!!!
Flashed from Internal Storage as per following directions:
-= COOKING ROMs & Radios from phone =-
1. open from your PC the rar or zip archive and extract only the BIG .nbh file
2. rename as DIAMIMG.NBH
3. copy the renamed file into the root dir of your "Storage Card" or "Internal Storage" (the one of 4Gb... NOT to the internal phone memory!)
4. reset your device and within 3 seconds push together the Vol_Down + Back button (the one on the right above the hangup button) and keep pressed until the boot loader appears (the one with the color stripes)
5. soon as you see the bootloader stop to press those poor buttons
6. a very simple gray menu will appear asking you what to do, simple press the power button to perform the ROM/Radio upgrade
7. while the upgrade runs be patient and don't press again the power button, reset the device or play with it until it finishes, when finished a message "UPDATE SUCCESS" will appear, now you can safely reset your device
8. who prefer can perform a hard reset after the fresh cook (soon after reset simply press Vol_Down + Circle button, then when you see another simple gray menu choose Vol_Up to confirm format), even if this has no-sense because internal memory is pre-formatted during flash, but... there is always a but... for some unknown "scientific" reason sometimes an hard-reset can save time & headache
THANKS! THANKS! THANKS!
Click to expand...
Click to collapse
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Cheers
Hi!
The same thing happend to me too... I think it's because of the serial number we have entered when we have downloaded that 100 MB ROM Update file from the HTC support site... well i think it doesn't match with the serial and IMEI of the phone that the upgraded rom checks at the end of the update process... so i think it's kind of a protection against piracy developed by htc... taiwanese idiots!
Hi!
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
miriamscorob said:
pls anyone send any information about an rom update file that works and doesn't report errors after it installed 100%. pls specify it's rom version too! 2.03 would be great
thanks in advance
Click to expand...
Click to collapse
read all posts please
works like a charm folks! thank you!
g0x said:
Thers some other option
Install twice from activesync 1st time = error, run for the second time the same version and OK it updates.
At least with my Diamond had worked
Click to expand...
Click to collapse
I made this too for testing First flash: Error, Second time: Ok

[Q - fixed] Defy 2.2 OTA release 4-21-11, installation Error (Status 7) Message?

Defy 2.2 upgrade not installing.
When I first got my phone from best buy it was delivered by UPS late at night on a Friday
so of course I wanted to play with it right away and did not wait to go to a T-Mobile store
to have it set up. I used the sim card that came with the phone and set up motoblur over wifi.
Then on Monday I went a T-Mobile store to get a phone plan (pre-paid) and they put in a
new sim card. The rep had trouble activating it and had to do it more than once
but he did get it activated on maybe the third try. Since then I have been using it daily
and I have not had any problems other than the visual voice mail activation error every time
I reboot the phone. And when I called T-Mobile in whatever country they are in, I was told that is because I am a pre-paid customer I can not use it and that I should "turn it off or delete it".
I have installed programs from lots of different websites to try them out and see if they
are something I might want to continue using, so I have installed and uninstalled at least
100 apps or more from multiple web sites.
I was able to install the prior 2.1 "update" and my firmware version is 2.1-update1 and
I have been checking system update about once a week since then and today I find the
2.2 upgrade.
So I try to do the 2.2 upgrade and it will not install. I just keep getting the
android with a triangle and exclamation point every time I try to install it.
1) So I decided to start from scratch so I did a factory reset to get it back
to factory settings. I Downloaded the upgrade then tried to install and it only gets about
a quarter of the way then I get an android with a triangle and exclamation point. Tried
to install several times with same results. Of course every time I do the factory reset I
have to set up motoblur, activate my google account in the market, have to re-enter wifi info, etc.
I read through the forums and found the discussion "Android 2.2?", I read through it
and tried all the suggestions I found.
2) Did a reboot with "power + volume up";
bootloader 09.10
battery ok
ok to program
connect usb
data cable
3) Did a reboot with "power + volume down";
it starts up with the motorola "M" then it
goes staight to the android with the triangle and exclamation point.
I tap the bottom right of the screen and get the android system recovery screen.
I selected "wipe cache partition" wipe partition and it wiped the cache and formatted the cache.
Then I rebooted normally and downloaded the 2.2 upgrade again and again I get the android
with a triangle and exclamation point.
4) Next I did a reboot with "power + up & down volume together" to try safe mode.
it starts up, I continue holding up & down volume until it boots up and
it says safe mode in the bottom left of the screen.
I go to settings > privacy > factory data reset. I do a factory reset.
And I still get the screen with the android and the triangle with an exclamation point.
I tap on the bottom right corner and get "assert failed": apply_patch_check(" /system/appVending.apk".
(then two long series of numbers)
E:Error in /cache/blur_version.3.6.360.MB525.T-Mobile.en.US.zip
(Status 7)
Installation aborted.
morr22066 said:
Defy 2.2 upgrade not installing.
When I first got my phone from best buy it was delivered by UPS late at night on a Friday
so of course I wanted to play with it right away and did not wait to go to a T-Mobile store
to have it set up. I used the sim card that came with the phone and set up motoblur over wifi.
Then on Monday I went a T-Mobile store to get a phone plan (pre-paid) and they put in a
new sim card. The rep had trouble activating it and had to do it more than once
but he did get it activated on maybe the third try. Since then I have been using it daily
and I have not had any problems other than the visual voice mail activation error every time
I reboot the phone. And when I called T-Mobile in whatever country they are in, I was told that is because I am a pre-paid customer I can not use it and that I should "turn it off or delete it".
I have installed programs from lots of different websites to try them out and see if they
are something I might want to continue using, so I have installed and uninstalled at least
100 apps or more from multiple web sites.
I was able to install the prior 2.1 "update" and my firmware version is 2.1-update1 and
I have been checking system update about once a week since then and today I find the
2.2 upgrade.
So I try to do the 2.2 upgrade and it will not install. I just keep getting the
android with a triangle and exclamation point every time I try to install it.
1) So I decided to start from scratch so I did a factory reset to get it back
to factory settings. I Downloaded the upgrade then tried to install and it only gets about
a quarter of the way then I get an android with a triangle and exclamation point. Tried
to install several times with same results. Of course every time I do the factory reset I
have to set up motoblur, activate my google account in the market, have to re-enter wifi info, etc.
I read through the forums and found the discussion "Android 2.2?", I read through it
and tried all the suggestions I found.
2) Did a reboot with "power + volume up";
bootloader 09.10
battery ok
ok to program
connect usb
data cable
3) Did a reboot with "power + volume down";
it starts up with the motorola "M" then it
goes staight to the android with the triangle and exclamation point.
I tap the bottom right of the screen and get the android system recovery screen.
I selected "wipe cache partition" wipe partition and it wiped the cache and formatted the cache.
Then I rebooted normally and downloaded the 2.2 upgrade again and again I get the android
with a triangle and exclamation point.
4) Next I did a reboot with "power + up & down volume together" to try safe mode.
it starts up, I continue holding up & down volume until it boots up and
it says safe mode in the bottom left of the screen.
I go to settings > privacy > factory data reset. I do a factory reset.
And I still get the screen with the android and the triangle with an exclamation point.
I tap on the bottom right corner and get "assert failed": apply_patch_check(" /system/appVending.apk".
(then two long series of numbers)
E:Error in /cache/blur_version.3.6.360.MB525.T-Mobile.en.US.zip
(Status 7)
Installation aborted.
So, did I not set up my phone correctly? Do I need to go back to the original sim card that
was in the phone when I set it up over wifi? Should I not have wiped the cache when I did the factory reset? Did I miss something?
Click to expand...
Click to collapse
are you trying to update to 2.2??
If so, you have to download RSD Lite (latest version) and go to bootloader, the one with power + vol. up
Then download a fixed sbf of 2.2 (search on xda itself)
Open RSD Lite and it will detect your phoen.
Then choose the downloaded sbf and let it complete
VOILA! You're updated!
Defy 2.2 upgrade not installing
Yes, I'm trying to install the official T-Mobile USA 2.2 upgrade that was released over the air. I've never used RSD lite, I will take a look at the link. Is RSD lite difficult to use?
* Update, I had an error 7 message when trying to install the over the air update and I was missing several stock apps so I wanted to start fresh. The last time I flashed a device was my old Nokia Tablet so it's been a while but RSD lite was pretty simple once I found the correct SBF.
I found several sets of instructions here in the forums but they are scattered across multiple threads so I've been trying to gather them together in one spot to make it easier for the next person who has this same issue. Thank you to everyone who post instructions for an easy to walk through fix.
1) Download RSD lite 4.9
http://www.mediafire.com/?7xjs2d6nubeatc6
2) Locate correct SBF and Download (JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf) for T-mobile USA 2.1 stock, unzip file
http://and-developers.com/sbf:defy
3) Wipe Device
4) Start DEFY in Bootloader (PWR + Vol Up) if necessary download and install the T-mobile froyo bootonly.sbf
http://bluedg.npage.de/get_file.php?id=15782585&vnr=589384
5) Start RSD Lite, Select SBF and flash
6) Sign into phone and download update
7) After installing the update, I did a factory reset and I rooted with SuperOneClick and restored from Titanium backup
Re-Rooting with Superoneclick
http://forum.xda-developers.com/attachment.php?attachmentid=489694&d=1295035181
Plug in in Portal mode. Activate Usb Debugging. Execute Superoneclick with Adminrights and then click on root, restart your phone.
Or try this:
Step 1; Turn your android phones USB Debugging OFF.
Step 2: Download and launch Superoneclick with Admin rights on your PC. Then Click Root.
Step 3: When it says: Waiting for Device, Turn USB Debugging ON
Step 4: It’ll now run RATC
Step 5: When it says: Starting ADB Server…
Step 6: Turn your android phones USB Debugging OFF
Step 7: Turn your android phones USB Debugging ON
Step 8: Turn your android phones USB Debugging OFF
Step 9: All BEFORE it says “Waiting for device…” again
Other tweeks:
Next I downloaded the Defy SD Recovery App from the market and it also an smoothly without any problems.
Then I downloaded SetVsel from the Market for the Defy to overclock it, it comes with 3 preset Vsel settings for 300, 600 and 800. I kept the first two at 33 / 300 and 48 / 600 then increased the 3rd preset to a 52 / 1000 and the CPU now hits 1000MHz, I have also had it set at 58 / 1100 and it works well. There is a noticeable boost plus battery life is at least as good as it was before. I also ran the stability test just to see if there were any issues and it went well.
Then I downloaded Uninstaller for Root from the market and began freezing some of the preinstalled bloatware from T-Mobile one at a time and so far I'm not having any problems.
And then installed Titanium Backup from the market and scheduled regular backups.
So far everything seems to be working well.
Extras:
Motorola website release files for JORDN_U3_6.19.0:
https://opensource.motorola.com/sf/..._defy/frs.defy_tmo.jordn_u3_6_19_0?_pagenum=1
Motorola Defy 2.2 (34.4.9) System Update Release Notes:
http://www.motorola.com/staticfiles..._Blur_Version.34.4.9.MB525.T-Mobile.en.US.pdf
Motodev Defy Page:
http://developer.motorola.com/products/me525/
morr22066 said:
Yes, I'm trying to install the official T-Mobile USA 2.2 upgrade that was released over the air. I've never used RSD lite, I will take a look at the link. Is RSD lite difficult to use?
Click to expand...
Click to collapse
RSD Lite is not difficult at all!
But btw, you can update directly from your phone!
Seetings-> About Phone-> System Updates.
Well, That's some trouble after the long wait.
I think prior to froyo update you will have to update the software to version 34.4.9 first, as a prerequisite for Froyo.
Please visit TMobile official link for detailed steps:
In short:
Software Upgrade for Motorola DEFY™ (34.4.9)
Introduction
This is a software upgrade for T-Mobile USA Motorola DEFY users who are currently using Android™ 2.1 (Eclair) software versions. The 34.4.9 upgrade for Motorola DEFY provides new features from Android 2.2 (Froyo) plus additional improvements.
Instructions for Installing Software
For a successful installation, we recommend installing these updates while the battery in your phone is at least 50% charged. Make sure you have an active SIM card installed in your phone.
Important: The file size of the DEFY Froyo software update is approximately 120MB. To avoid potential data overage charges, please use a Wi-Fi connection to fully download the software update.
If you have received a notification message for this update:
1. Select "Download"
2. After the software is downloaded, select "Install now"
3. After the software is installed, your phone will re-start automatically.
4. Your phone is now updated with 34.4.9 software
If you have not received a notification message for this update:
1. Select the Settings icon in the main menu
2. Select "About phone"
3. Select "System updates"
4. Select "Download"
5. After the software is downloaded, select "Install"
6. After the software is installed, your phone will re-start automatically
7. Your phone is now updated with 34.4.9 software
If you have difficulty with this update, visit site
If any issues call TMobile Customer Care
MazaMoto said:
Well, That's some trouble after the long wait.
I think prior to froyo update you will have to update the software to version 34.4.9 first, as a prerequisite for Froyo.
Click to expand...
Click to collapse
34.4.9 IS the Froyo update. You have to have the 2.1-update1 update installed, though, and you need to make sure you still have all the Blur apps/bloatware intact.
Thanks for the help
My problem is solved, hopefully this thread will help anyone else that had a similar problem.
morr22066 said:
Yes, I'm trying to install the official T-Mobile USA 2.2 upgrade that was released over the air. I've never used RSD lite, I will take a look at the link. Is RSD lite difficult to use?
* Update, I had an error 7 message when trying to install the over the air update and I was missing several stock apps so I wanted to start fresh. The last time I flashed a device was my old Nokia Tablet so it's been a while but RSD lite was pretty simple once I found the correct SBF.
I found several sets of instructions here in the forums but they are scattered across multiple threads so I've been trying to gather them together in one spot to make it easier for the next person who has this same issue. Thank you to everyone who post instructions for an easy to walk through fix.
1) Download RSD lite 4.9
http://www.mediafire.com/?7xjs2d6nubeatc6
2) Locate correct SBF and Download (JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf) for T-mobile USA 2.1 stock, unzip file
http://and-developers.com/sbf:defy
3) Wipe Device
4) Start DEFY in Bootloader (PWR + Vol Up) if necessary download and install the T-mobile froyo bootonly.sbf
http://bluedg.npage.de/get_file.php?id=15782585&vnr=589384
5) Start RSD Lite, Select SBF and flash
6) Sign into phone and download update
7) After installing the update, I did a factory reset and I rooted with SuperOneClick (Do another Reset after Rooting)
8) Restore apps and settings from Titanium backup (or your preferred backup method)
Re-Rooting with Superoneclick
http://forum.xda-developers.com/attachment.php?attachmentid=489694&d=1295035181
Plug in in Portal mode. Activate Usb Debugging. Execute Superoneclick with Adminrights and then click on root, restart your phone.
Or try this:
Step 1; Turn your android phones USB Debugging OFF.
Step 2: Download and launch Superoneclick with Admin rights on your PC. Then Click Root.
Step 3: When it says: Waiting for Device, Turn USB Debugging ON
Step 4: It’ll now run RATC
Step 5: When it says: Starting ADB Server…
Step 6: Turn your android phones USB Debugging OFF
Step 7: Turn your android phones USB Debugging ON
Step 8: Turn your android phones USB Debugging OFF
Step 9: All BEFORE it says “Waiting for device…” again
Other tweeks:
Next I downloaded the Defy SD Recovery App from the market and it also an smoothly without any problems.
Then I downloaded SetVsel from the Market for the Defy to overclock it, it comes with 3 preset Vsel settings for 300, 600 and 800. I kept the first two at 33 / 300 and 48 / 600 then increased the 3rd preset to a 52 / 1000 and the CPU now hits 1000MHz, I have also had it set at 58 / 1100 and it works well. There is a noticeable boost plus battery life is at least as good as it was before. I also ran the stability test just to see if there were any issues and it went well.
Then I downloaded Uninstaller for Root from the market and began freezing some of the preinstalled bloatware from T-Mobile one at a time and so far I'm not having any problems.
And then installed Titanium Backup from the market and scheduled regular backups.
So far everything seems to be working well.
Extras:
Motorola website release files for JORDN_U3_6.19.0:
https://opensource.motorola.com/sf/..._defy/frs.defy_tmo.jordn_u3_6_19_0?_pagenum=1
Motorola Defy 2.2 (34.4.9) System Update Release Notes:
http://www.motorola.com/staticfiles..._Blur_Version.34.4.9.MB525.T-Mobile.en.US.pdf
Motodev Defy Page:
http://developer.motorola.com/products/me525/
Click to expand...
Click to collapse
morr22066 said:
Yes, I'm trying to install the official T-Mobile USA 2.2 upgrade that was released over the air. I've never used RSD lite, I will take a look at the link. Is RSD lite difficult to use?
* Update, I had an error 7 message when trying to install the over the air update and I was missing several stock apps so I wanted to start fresh. The last time I flashed a device was my old Nokia Tablet so it's been a while but RSD lite was pretty simple once I found the correct SBF.
I found several sets of instructions here in the forums but they are scattered across multiple threads so I've been trying to gather them together in one spot to make it easier for the next person who has this same issue. Thank you to everyone who post instructions for an easy to walk through fix.
1) Download RSD lite 4.9
http://www.mediafire.com/?7xjs2d6nubeatc6
2) Locate correct SBF and Download (JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf) for T-mobile USA 2.1 stock, unzip file
http://and-developers.com/sbf:defy
3) Wipe Device
4) Start DEFY in Bootloader (PWR + Vol Up) if necessary download and install the T-mobile froyo bootonly.sbf
http://bluedg.npage.de/get_file.php?id=15782585&vnr=589384
5) Start RSD Lite, Select SBF and flash
6) Sign into phone and download update
7) After installing the update, I did a factory reset and I rooted with SuperOneClick and restored from Titanium backup
Re-Rooting with Superoneclick
http://forum.xda-developers.com/attachment.php?attachmentid=489694&d=1295035181
Plug in in Portal mode. Activate Usb Debugging. Execute Superoneclick with Adminrights and then click on root, restart your phone.
Or try this:
Step 1; Turn your android phones USB Debugging OFF.
Step 2: Download and launch Superoneclick with Admin rights on your PC. Then Click Root.
Step 3: When it says: Waiting for Device, Turn USB Debugging ON
Step 4: It’ll now run RATC
Step 5: When it says: Starting ADB Server…
Step 6: Turn your android phones USB Debugging OFF
Step 7: Turn your android phones USB Debugging ON
Step 8: Turn your android phones USB Debugging OFF
Step 9: All BEFORE it says “Waiting for device…” again
Other tweeks:
Next I downloaded the Defy SD Recovery App from the market and it also an smoothly without any problems.
Then I downloaded SetVsel from the Market for the Defy to overclock it, it comes with 3 preset Vsel settings for 300, 600 and 800. I kept the first two at 33 / 300 and 48 / 600 then increased the 3rd preset to a 52 / 1000 and the CPU now hits 1000MHz, I have also had it set at 58 / 1100 and it works well. There is a noticeable boost plus battery life is at least as good as it was before. I also ran the stability test just to see if there were any issues and it went well.
Then I downloaded Uninstaller for Root from the market and began freezing some of the preinstalled bloatware from T-Mobile one at a time and so far I'm not having any problems.
And then installed Titanium Backup from the market and scheduled regular backups.
So far everything seems to be working well.
Extras:
Motorola website release files for JORDN_U3_6.19.0:
https://opensource.motorola.com/sf/..._defy/frs.defy_tmo.jordn_u3_6_19_0?_pagenum=1
Motorola Defy 2.2 (34.4.9) System Update Release Notes:
http://www.motorola.com/staticfiles..._Blur_Version.34.4.9.MB525.T-Mobile.en.US.pdf
Motodev Defy Page:
http://developer.motorola.com/products/me525/
Click to expand...
Click to collapse
THANK YOU!!!! you my friend are a life saver! thanks a million!
No problem, glad I could help.
It works!
Thank you very much for taking your time in putting the puzzle pieces together. I removed the blockbuster app because it seemed to always run and when this time came I forgot where I put the backup and even then it kept giving me Status 7.
So this way is quite smooth, direct instructions with working links.
Only 2 things...
More detail on how/where to wipe on step 3 I assumed it was under privacy>Factory Data Reset is what you mean... I hope. (works for me)
Emphasize on "RESET AFTER ROOT" lmao I always forget to do that.
Perfect, thanks again.
You're right, I should have said clearly to do another reset after rooting. I have updated it. Thanks.
And thank you again to all those who contribute to the forum and provide clear easy to understand walk through instructions for those of us who do not do this often.
It's rare that I do something like this so after spending most of my weekend looking for all of the instructions and links I wanted to try and spell it out for anyone else who was having the same problem.
Good luck to everyone and of course "any modifications could void your warranty and brick your phone, you do so at your own risk".
"7) After installing the update, I did a factory reset and I rooted with SuperOneClick and restored from Titanium backup"
Does this mean that after wiping the phone (with 2.1), then upgrading to 2.2, then factory reset, then Titanium backup will restore programs from when 2.1 was installed?
I thought you can't restore backups from Titanium Backup on different Android versions (e.g. backups taken while on Android 2.1 cannot be restored once 2.2 is installed).
I ask because I am hesistent to upgrade to 2.2 (where mine requires a phone reset due to rooting, etc) until I can extract some items from the phone (e.g. Yahoo Instant Messenger chats) because I thought I would lose all of those things.
Thank you.
morr22066,
I also had rooted the 2.1-update1 OS and removed the Blockbuster app and the music marketing apps which subsequently caused my 2.2 install to fail. Your guide saved my bacon and helped me get the Froyo upgrade installed without further incident. What an upgrade too! Responsiveness is definitely better, especially voice dialing. It used to take up to 30 seconds for it to load and respond to the click of my BT headset now it's 1-3 seconds max. Lots of small UI refinements and improvements too.
Thank you very much for making it easy to do at 4am and half-awake.
-felipe
Oh by the way after doing this you might want to look into my last post "google maps freeze the phone" after getting updated for those of you following this fyi.
Sent from my MB525 using XDA App
morr22066 said:
Yes, I'm trying to install the official T-Mobile USA 2.2 upgrade that was released over the air. I've never used RSD lite, I will take a look at the link. Is RSD lite difficult to use?
* Update, I had an error 7 message when trying to install the over the air update and I was missing several stock apps so I wanted to start fresh. The last time I flashed a device was my old Nokia Tablet so it's been a while but RSD lite was pretty simple once I found the correct SBF.
I found several sets of instructions here in the forums but they are scattered across multiple threads so I've been trying to gather them together in one spot to make it easier for the next person who has this same issue. Thank you to everyone who post instructions for an easy to walk through fix.
1) Download RSD lite 4.9
http://www.mediafire.com/?7xjs2d6nubeatc6
2) Locate correct SBF and Download (JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf) for T-mobile USA 2.1 stock, unzip file
http://and-developers.com/sbf:defy
3) Wipe Device
4) Start DEFY in Bootloader (PWR + Vol Up) if necessary download and install the T-mobile froyo bootonly.sbf
http://bluedg.npage.de/get_file.php?id=15782585&vnr=589384
5) Start RSD Lite, Select SBF and flash
6) Sign into phone and download update
7) After installing the update, I did a factory reset and I rooted with SuperOneClick and restored from Titanium backup
Re-Rooting with Superoneclick
http://forum.xda-developers.com/attachment.php?attachmentid=489694&d=1295035181
Plug in in Portal mode. Activate Usb Debugging. Execute Superoneclick with Adminrights and then click on root, restart your phone.
Or try this:
Step 1; Turn your android phones USB Debugging OFF.
Step 2: Download and launch Superoneclick with Admin rights on your PC. Then Click Root.
Step 3: When it says: Waiting for Device, Turn USB Debugging ON
Step 4: It’ll now run RATC
Step 5: When it says: Starting ADB Server…
Step 6: Turn your android phones USB Debugging OFF
Step 7: Turn your android phones USB Debugging ON
Step 8: Turn your android phones USB Debugging OFF
Step 9: All BEFORE it says “Waiting for device…” again
Other tweeks:
Next I downloaded the Defy SD Recovery App from the market and it also an smoothly without any problems.
Then I downloaded SetVsel from the Market for the Defy to overclock it, it comes with 3 preset Vsel settings for 300, 600 and 800. I kept the first two at 33 / 300 and 48 / 600 then increased the 3rd preset to a 52 / 1000 and the CPU now hits 1000MHz, I have also had it set at 58 / 1100 and it works well. There is a noticeable boost plus battery life is at least as good as it was before. I also ran the stability test just to see if there were any issues and it went well.
Then I downloaded Uninstaller for Root from the market and began freezing some of the preinstalled bloatware from T-Mobile one at a time and so far I'm not having any problems.
And then installed Titanium Backup from the market and scheduled regular backups.
So far everything seems to be working well.
Extras:
Motorola website release files for JORDN_U3_6.19.0:
https://opensource.motorola.com/sf/..._defy/frs.defy_tmo.jordn_u3_6_19_0?_pagenum=1
Motorola Defy 2.2 (34.4.9) System Update Release Notes:
http://www.motorola.com/staticfiles..._Blur_Version.34.4.9.MB525.T-Mobile.en.US.pdf
Motodev Defy Page:
http://developer.motorola.com/products/me525/
Click to expand...
Click to collapse
So when do I flash this? JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_ JORDANTMO_P022_HWp3_Service1FF.sbf
You say to download this and unzip it. Latter you said to download T-Mobile Foroy bootonly and install it via RSD Lite I'm guessing. Should I flash
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_ JORDANTMO_P022_HWp3_Service1FF.sbf
first then wipe my device then flash froyo bootonly?

[Q] Tried to update, now unuseable

So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.
Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)
Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.

FINALLY: Install Windows 10.0.10586.1176 on the 4GB/512MB Lumia 530 from Stock 8.1

Hi guys,
I've finally managed to get Windows 10 back to my Lumia 530.. from "bare metal" (really, it looked death at some try-and-fail steps
It will be done in two steps.
First, we need to push it to the 10586.107
The second update we will deploy the "final" version of v1511 - 10586.1176 (the fixed issues betwenn 107 and 1176 are a list of 8pages paper )
WHAT YOU NEED:
- Windows Device Recovery Tool (can ressurect dead phones, when nothing else can connect to it.... )
- The included thor2.exe cmdline tool (find it in the install path of the Recovery Tool).
- The Stock Windows 8.1 (can be downloaded by the tool or by yourself at lumiafirmware com
- IUTOOL.exe (included in the Windows Driver Kit (WDK) or from here, the big Windows 10 Mobile Offline Thread) as well as the perfect prepared first packages:
- the "win10_mobile_offline_updater_v41.wim" provided on this page. YOU need only the files in THIS SUBFOLDER: "3rd Generation\43X-532"
- If you want to prepare further updates or a different phone, you'll need also (comes with IUTOOL.exe) GetDuLogs.exe (I HIGHLY RECOMMEND to run it with your fresh updated device connected to USB), It will rip the update log wich are nice but it also includes a package list, that were updated on your Phone. THIS IS IMPORTANT because these package names are the packages you will need for every device upgrade rollup..
HOW TO:
1st: I believe i took the GUI Recovery tool the first time i succeeded but at my second try it didn't work.. The whole success depends on a few megabytes of free space. So whatever caused this, MY LAST and sucessful try worked after i flashed the Stock FFU with the command line tool thor2.exe using the whole bunch of options:
thor2 -mode uefiflash -ffufile "your_Phones_Stock_Build_imageFile.ffu" -do_full_nvi_update -do_factory_reset -reboot
After the reboot, and you will only succeed by following: Leave the phone at the first Screen (The Welcome, languange selection), connect to USB, let windows install the driver and once connected (when using Windows 10) Remove the device from Devices And Printers otherwise IUTOOL.exe will put out an error and won't work.
now start the update by launching: iutool -V -p e:\folderName (Where All The CABs Are Inside).. You won't get any message on your phone, but IF it fails, IUTOOL will put out an Error - in all my tries within 5 minutes.. YOU NEED TO WAIT for reboot. The Lumia 530 will take around 30minutes until it reboots itself. It boots in the known maintenance mode, takes some time and will come up with Windows 10.0.586.107. Because we didn't went through the OOBE before, either only the Start Screen will be empty or in addition the App list will not show every app - as expected - Easy Fix: If you have the settings app, go to SYSTEM-INFO and launch a factory reset.. If not take the hardware forced way: Hold Volume down AND the power button until it vibrates, release ONLY the button, hold volume down a bit longer to get the phone recognized what you want. When it shows the "!" launch the factory reset by pushing in this row: Vol Up - Vol Down - Power - Volume down..
the keyboard wont work so if you want your backup to be forced while OOBE, you need to make your Wifi Open without password... There is a fix for this issue on the Main Thread for the Offline Update, but i just removed my (in my case) German Keyboard and the englich keyboard worked fine immediately after removing..
The Swiss keyboard was also good for me - but i didn't care a lot - will be fixed with the final Update...
THE OOBE WAY doesn't work any more, seems like Microsoft wasn't amused by this and closed this nice door i just found as my very last idea with this phone. The genius idea.. i felt so cool after that really worked.... Now the last step: don't forget to call "getdulogs -o e:\outputfile.cab" in the cab are the logs as well as the important package list..
The second update is easier, because there is not much you can do... You can find it with normal Update search but - trust me - in the best case it fails with 50 MB too less space... really hard So the difficult part this time is to identify and get your packages. I've searched my 6 disks and finally i'found my phone updates but unfortunately i must have overwritten my get.cmd for 1176 which was a download batch for the files.. ****.. but it's also hard to identify the correct package at Microsoft, i'm tired but here's the little gift, definetely the correct package, you'll find here (i cannot post links, too new ) catalog-update-microsoft-com and seach for "14003.1176". The 2500 MB folder is yours, look for " Windows Mobile 10 Production Bundle - OS 10.0.14003.1176 update for all mobile phone devices", Click "Download to see all package links and download the ones in the log files package list...
I got 168 files, should be more - even if more are not a problem - we don't have any space for maybe resolution packages for other devices. NO
If you have some scripting or programming knowlegde, there are some hints for it below.. Or Contact me if you need help.
Update is easy:
- Factory Reset AND DON'T CONNECT your phone to the Wifi - at no point
- After OOBE - Uninstall absolutely every thing that is able to, delete temp files - these little two things worked fine for me, key point here is NO CONNECTION TO NOWHERE BEFORE.. again, we are fighting for 50 MB, so if it was connected -> do the factory reset before... but do it also if it never was on, because there are few files from the previous update, that will lock us these 50 MB...
Update itself like before, IUTOOL.exe -V -p u:\cabFolder
WHAT YOU NEED TO KNOW... If you like ****, this time you can watch the update progress - IUTOOL.exe forces the normal windows update so it will show progress..
reboot to maintenance mode - will all work fine BUT THE FIRST REBOOT - keep cool, and enjoy the blue flashing Disco Screen you will get - you can try to reboot, but it didn't help on all my 2 deployments. what it needs (was a surprise for me, and it helped twice) is a simple factory reset.. like i wrote in the previous update. This time you will have to use the hardware way i mentioned.. Thats all.. One little issue, i couldn't fix yet, but i don't care.. MSN News App, And the Weather App are only links to the store and for whatever reason the store thinks it is already installed, Take Foreca Weather... Everything else works fine.. Keyboard as well with native german on my side
Hopefully i mentioned it detailed enough... worked TWO times for me now.. 14393 update needs too much space, don't even think about it
I'm currently slowly reading into Deploying and developing customized windows mobile images, not that i wan't to run it on my 530 but maybe i'll find somehing...
Greetings, Stephan.. Below some hints for the downloads, if you want to script it...
THE SECOND UPDATE is based on the package list i've ripped. With this and the version number (this is tricky, because the internal Build will not stay at 10586, so you will find the update by searching for "Windows Mobile 1176" or sth near.. look for a Folder size of ~2500 and the update rollup .1176 - i'm not really sure - it was some near 14003.1176 (The Build number MUST BE LOWER than 14393. You'll either some creative knowledge like programming or a lot of patience and motivation to find all your 127 packages and download it manually.. i copied the the whole filename's list and the prefix to have a download link and then i wrote a little C# to compare my needed package List with the whole build list from microsoft.. i added also a "wget -c ". It's even more complicated... 2 different "base" links (i just took both links - only the correct one will work. And finally - the last complication is - there are downloads "tagged" with a "cbs" as well as with "cbsu" in the filename FOR MOST PACKAGES, i've not tried to find what it means - but however i decided to take the CBS because their filesize was realisic, cbsu are way too small, may be these are one fixes from last update, and not the whole rollup - what we need....
..the keyboard wont work so if you want your backup to be forced while OOBE, you need to make your Wifi Open without password...
Click to expand...
Click to collapse
Forget that... you cannot apply your backup at this time, even with internet connected... The hard point would be to login with Microsoft
can you post screenshots?
I followed that whole guide but I didn't succeed. It was then that I deleted the .cab files from languages that I'm not going to use and I remade the whole process, being transferred 31 files. I crossed my fingers and received the full storage message but the update followed and to my surprise the phone restarted and updated.
Someone to helpme with efiesp.bin partition?
Hello,
im trying to understand ur method but im not that into microsoft stuffs so, what do u mean with:
" now start the update by launching: iutool -V -p e:\folderName (Where All The CABs Are Inside) ? "
I get it done with more than 1Gb of free storage !
so I start with your steps u provided above and I got lost honestly.
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340/ of this glorious man @hikari_calyx
-I tired to intall W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
STALKER18 said:
I get it done with more than 1Gb of free storage !
so I start with your steps u provided above and I got lost honestly.
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340/ of this glorious man @hikari_calyx
-I tired to intall W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
Click to expand...
Click to collapse
@STALKER18 did you manage to get 1703 or 1709 on the Lumia 530?
Someone can help me with efiesp.bin file dumped with WPInternals?

Categories

Resources