yashsingh1/xdaforums huggingface dataset:
[MDA II, XDA II, 2060 ROM Development] cairo31male:
@hcnsoft:

The 2 solutions described above are for XDA 2's which have been screwed up by installing / uninstalling the latest beta version tmob 1.72. If this is your situation, and you have a working bootloader, both solutions should work for you.

@SEB152030:

The beta we have is 1.72, which caused all these problems. If you have another working device, as described in solution 1, you can revert back to the latest working official ROM (1.66), just follow the steps decribed above and use the official 1.66 upgrade program.

@applecom:

If your XDA 2 is dead, there is no harm in trying. But basically, this SD file will only work on devices that have already been upgraded to 1.72 and then died. If it is dead because of any other reason, I suggest you stick with older stable versions and don't try to mess up with 1.72 for now, until the developers come up with a simple tool to go back and forth between different roms. You can flash SD images that were made from other working devices that have your same model/language. You wouldn't get any errors that way.

@Panja:

Since your device is working, I suggest you wait a couple of days, before trying anything. The developers might come up with a simpler solution. If you absolutely have to downgrade, you can follow the solution 1 described above, but you will need another working device for a few minutes. Use the other working device which has the old ROM installed and start the OLD ROM installation software, then plug in your device with the 1.72 ROM AFTER you get the different versions dialog with the button "UPGRADE".

@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.

OLD version means any version before 1.72
[MDA II, XDA II, 2060 ROM Development] Ivan_R:
I already try BOTH solution!! Solution 1, i try with ROM 1.03.11, which is thats the basic ROM. Solution 2, the RESULT is Not Allowed UpDate!!

So i guess this is the matter of BOOTLOADER!! Yours is 1.06 and me 1.03. THATS THE PROBLEMO NOW!! Now... How about upgrade the BOOTLOADER?? :cry:

F@#$!%G FREAK ROM!! :evil:
[MDA II, XDA II, 2060 ROM Development] vwonges:
Mas Ivan,

Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72
[MDA II, XDA II, 2060 ROM Development] applecom:
thanks cairo for the info, my xda is working with the standard rom, Our only problem is me and the guy that got the rom in the first place would like to use it but we cant

anyway thanks for youe info

John
[MDA II, XDA II, 2060 ROM Development] SEB152030:
Solution 1

Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....

I found a solution : Here
[MDA II, XDA II, 2060 ROM Development] watchdogsdg:
Radio Stack Downgrade

I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.

Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?

Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
[MDA II, XDA II, 2060 ROM Development] Ivan_R:
Re: Radio Stack Downgrade

Go go go... Just downgrade it!! 8) Then you will join me in HERE!! Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!
[MDA II, XDA II, 2060 ROM Development] mkriemersma:
Didn't have any trouble downgrading

I just upgraded to 1.72 last week...hated it...gprs was WAY too slow. Today I downgraded and crossed my fingers back to Xda_II_Upgrade_v16050.exe (filename..not sure where i got it).

IT WORKS!! everything went fine and is fine.

I think my bootloader said it was something like version 1.01 (very hard to read that screen without the backlight) So I'm guessing this downgrade problem may be specific to bootloader versions.

No expert, just letting you know what i did.

This site is amazing. Thanks for everything.
[MDA II, XDA II, 2060 ROM Development] Ivan_R:
Re: Didn't have any trouble downgrading

I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!! :oops:
[MDA II, XDA II, 2060 ROM Development] nilron:
Hi,

Thanks for all help!

I have a dead unit due to 1.72 ROm.

Itried to fool the himalya upgrade program with a soft reset as suggested in another thread, it works It gets trough the device id but stops when erasing rom, any suggestion?

Is there anyone out ther that can disassamble the himalyprogram and

make a small program without error checking?

I also have bootloader 1.06 and tried also "ntrw write ROM.nb1 H:"

It works writing the image but my bootloader don´t loads any rom.

Tried with 2 differnet SD cards, and soft reset, hardreset, and only pushing camera button, without succes, what is the right command?

Any more suggestions?
[MDA II, XDA II, 2060 ROM Development] cairo31male:
@nilron:

Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together, then wait a little. You should get instructions to press POWER to start flashing.
[MDA II, XDA II, 2060 ROM Development] :
bootloader v 1.06 is locked. you will not be able to flash in the manner you are attempting, I believe.

there are or will be found ways around this, I am sure, but the cat and mouse game the OEMs play with the persons/forums(like this one) trying to keep up have lead to these types of situations.

Another example of this game is the new EXT ROM procedures for loading. The programs write a file to the windows directory and this is read back during the loading process.

When someone finds a fool proof method of replacing the bootloader ROM (fool proof in the sense that non-developers can do it), this may make most of these problems go away.

I think you are stuck, like a few others on the forum with that bootloader (just search for the very angry posts...)
[MDA II, XDA II, 2060 ROM Development] :
Maybe the 1.06 people can get their problem solved in this manner

http://www.qtek.nu/default.asp?nc=4596&id=68&element=0

but I doubt it. Country ID error can be gotten around, but model ID error cannot (easily)
[MDA II, XDA II, 2060 ROM Development] nilron:
Hi

Well qtek 1.66 from www.qtek.nu does not work for me.

Model id error, can be bypassed by resetting when the screen becomes black, then the upgrade goes to upgrade rom ... with the rom 1.72 . radio etc.. klick next, goes to erasing rom and after a while a time out occurs.

I guess resetting also kills the process that should start and erase the rom.

But it also not for sure because if you can fool the program by switching devices, it can´t be depended on a program in a certain state waiting for the next command.

Any other suggestions?

And yes I cold not upgrade with SD cards, bootloader ver 1.06 ............
[MDA II, XDA II, 2060 ROM Development] watchdogsdg:
Bootloader Version?

How can we determine which bootloader version our XDA II has without doing a cold reset?

Steve
[MDA II, XDA II, 2060 ROM Development] nilron:
Hi

This is from himalya upgrade program ver1.1, error text extracted from the exe file when loaded in memory, (of course this is only the order of the text apparing in the program not the logical order it may be executed in)

I guess this is the part when it goes wrong before erasing the ROM

If it is works by switching devices (that uses bootloader 1.06) it looks like it could be something with the crypt... and password..

Can someone with bootloader ver 1.06 confirm that the device could be upgraded by switching PDA.

If its not works to switch devices it could be something similar thats happen when you reset the device to fool model iD, losing the thread, have a look at "ContinueFlashEvent "

Any more suggestions?

+++++++++++++++++++++++++++++++++++++++++

5 F800

set 2 1

set 6 ffff

set 1 0

password wrong!

Connection with Serial

Connection with USB \\.\WCEUSBSH

PortTestEvent

COM1PortTest

COM2PortTest

\\.\WCEUSBSH009 \\.\WCEUSBSH008 \\.\WCEUSBSH007 \\.\WCEUSBSH006 \\.\WCEUSBSH005 \\.\WCEUSBSH004 \\.\WCEUSBSH003 \\.\WCEUSBSH002 USBPortTest

\\.\WCEUSBSH001 COM1

Failed to create hPasswordEvent event !

PasswordEvent

%s\RUULog.log

%s\NK.nbf

Exit USBReadThread!

Read thread exit

Line 572: USBSerialReadThread close !

Invalid password.

:A=A0040000 :A=A1FC0000

Failed to create hReadJumpCodeAreaOKEvent event for thread!

ReadJumpCodeAreaOKEvent ParserEvent

Line 2275:

WriteFAT0Fail==TRUE

WriteBinaryFail==TRUE

Error during CryptReleaseContext

Error during CryptDestroyKey

Error writing plaintext!

Error during CryptDecrypt!

Error reading ciphertext!

Out of memory!

Error during CryptDestroyHash

Error during CryptDeriveKey!

Error during CryptHashData! Error during CryptCreateHash!

Error during CryptImportKey!

Error reading file header!

Memory allocation error.

Error reading file header!

Error during CryptAcquireContext!

Microsoft Enhanced Cryptographic Provider v1.0

Error opening plaintext file!

Error opening ciphertext file!

Program terminating.

Error number %x.

%s

An error occurred in running the program.

download

:A=70010000 info 2

WriteFAT0 is fail

WriteBinary is fail

Line 509: Recive bootloader return false

Line 505: Recive bootloader return TRUE

Line 546: Erase complete!

:L=

port.c line 512: bLength!=TRUE

Port.c Failed to create hGetBootloaderVersionEvent event !

Port.c Failed to create hBootloaderGetPlatformNameEvent event !

Failed to create hReadA0040000Event event for thread!

ReadA0040000Event

Failed to create hBeginWriteEvent event for thread!

BeginWriteEvent

Failed to create hContinueFlashEvent event for thread!

ContinueFlashEvent

Failed to create Erase event for thread!

EraseEvent

Line 1490: Read file fial!

Line 1506: SendString

TXQUEUE,TXQUEUE

fial!

Port.c Line 1505: Request record 90 seconds time out

Line 1473: SendString

TXQUEUE,TXQUEUE

fial!

Upgrade Radio success

Stage 5 complete

Port.c Line 1110: Request record 90 seconds time out

line 1606:Send HTCE

rwdata 0 10000
[MDA II, XDA II, 2060 ROM Development] hbahaie:
dear cairo31

i just upgraded to tmobile yesterday, just for fun and trial, i want to downgrade to o2 or carrier devices, i didn't try any thing yet, my device working normally. Thank to Allah, i just read ur thread before trying to downgrade, is there any advice?, what will happened if i tried to downgrade as we do usually?

thank u very much
[MDA II, XDA II, 2060 ROM Development] watchdogsdg:
What happened to this thread?

Hey guys what am i missing. I thought some of you were working on how to downgrade this Rom safely, not just a fix for when it f***s up. Then silence. Many of us are dependantly waiting for instructions on how to get rid of this T-Mobile ROM. XDA DEVELOPERS PLEASE HELP!
[MDA II, XDA II, 2060 ROM Development] cairo31male:
@hbahaie:

My advice to you is to wait and NOT try to downgrade for now, untill the Developers come up with a simple solution. If you absolutely have to downgrade, Solution 1 described at the begining of this post should work for you.

@nilron:

Yes, I can confirm both solutions described here were used with Bootloader 1.06 successfully.
[MDA II, XDA II, 2060 ROM Development] hbahaie:
dear cairoman

thanks for ur prompt reply, in fact, i tried allready to downgrade with many different roms, only till the confirmation screen with the upgrade icon ready to click on, but i regretted. Is this a positive sign, or it is normal, and problems usually occur afterwards?

another question please how to know the version of my bootloader and regarding solution 1, how to put my phone in bootloader mode prior to put it in cradle.

thanks alot
[MDA II, XDA II, 2060 ROM Development] nilron:
Hi, Thanks for the information.

Maybe its depends on the SD card I have tested SANdIsk 128, Dane-ELEC 256 with HAMA 8 in1 USB reader writer.

I have also Dane-Elec 512Mb and Panasonic 16Mb(not tested )

All of the above cards works fine when the XDAII is working

Which cards works for flashing ROM?

I am more than happy to buy a working SD card.

Regards,
[MDA II, XDA II, 2060 ROM Development] cairo31male:
@hbahaie:

If you get to the screen with different versions and the "Upgrade" button, all is going OK so far and I do not expect problems. To enter Bootloader, Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together. You should get the bootloader screen with the word "Serial" at the top and the version of your bootloader at the bottom e.x. "1.06". The screen will not be backlit, so it will be difficult to read, but you can still read it.

@nilron:

I do not think it depends on the card, since your cards work with other versions. I am using Sandisk 64MB.
[MDA II, XDA II, 2060 ROM Development] evolvd.:
SD ROM Upgrade Failed

Hey. Tried the SD ROM solution meantioned at the beginning of the thread.

Downloaded the 1.72 sd rom from post and copied to SD ok.

When in bootloader, says:

{

SD Download

=========

Sections=1

Not allow update!

}

I'm using the O2 XDA II. Is this SD ROM designed for the TMOBILE or O2 operator? If not O2, can we get an O2 version.

I originally upgraded to v1.72 using the instructions from the v1.72 thread, using er2003edit to change the operator of the upgrade [posted here: http://xdaforums.com/viewtopic.php?t=8515&postdays=0&postorder=asc&start=100]

Anyone got an XDAII working using the SD ROM flash?
[MDA II, XDA II, 2060 ROM Development] Panja:
Just downgraded succesfully to Qtek 1.66WWE!!

No problems at all using solution one provided in this thread!

For anyone that want to know, I have bootloader version 1.01
[MDA II, XDA II, 2060 ROM Development] cairo31male:
Glad I could help.

For those who do not have a second device, you may want to try this:

http://xdaforums.com/viewtopic.php?t=8903

It did not work for me, but it may for you ....
[MDA II, XDA II, 2060 ROM Development] dr_kaan:
Hi people,

I have the 1.60.00 wwe rom (12.3.2003) with radio 1.06.01 protocol 1337.16

ext.rom 1.60.06 (i think it's the dutch rom)

The original rom was t-mobile german, the device is t-mobile mda 2.

Should i upgrade to a new version? I've been reading the forums for some time and i saw people who are "very happy" with the new rom 1.72 and some people say "their device is DEAD!".

Any comments?

Thanks

K.G.
[MDA II, XDA II, 2060 ROM Development] noone:
Downgrade procedure WORKING & SAFE

Hi folks

though i'm not sure if this is still of interest i'm posting my solution to the downgrade problem.

I had my unit repaired for a broken screen and while they needed >1 month (!) to replace the LCD they also installed 1.72.01_ger_o2. My backup which was based on 1.60.52_ger_o2 was incompatible then.

Trying to downgrade I ran into the same problems described here and this is what i figured out:

- himaupgradeut v0.9.1.0 (from 1.60.52) crashes when 1.72 is installed

- himaupgradeut v0.9.1.0 errors about "model id" when nothing is installed after this crash

- himaupgradeut v1.2.0.0 (from 1.72.01) errors about "checksum error" with 1.60.52 nbfs

you have to decrypt 1.60.52 nbfs to nbas with xda2nbftool, 0.9.1.0 procedure (cf. xda2nbftool wiki page) and to reencrypt these nbas with 1.x.0.0 procedure. then you can use himaupgradeut v1.2.0.0 to flash the recoded 1.60.52 nbfs.

Thanks for all the precious advice in this thread

Matthias
[MDA II, XDA II, 2060 ROM Development] Jimate:
Obtaining Files for downgrading

Hey guys, I had the same problem after upgrading my i-mate (XDAII) from the original 1.72 to WM2003SE, it crashed a lot so i wanted to go back badly, I discovered a very simple solution:

1. Obtain the new .exe files for the new (original) version you want to downgrade to.

2. Run the file, it will unpack, then give you the welcome screen, do NOT press any button, rather, go to the temp folder, usually located in C:\Documents and Setting\your_name\Local Settings\Temp

andd....guess what? you'll find there all the needed .nsf files..

3. Obain the files, modify them with ER tool, and flash as usual.

Chheeeeers:)
[MDA II, XDA II, 2060 ROM Development] Danniel:
Re: Problem Solved: Dead devices due to tmob 1.72 + Downgrad

[thkx for the info.

but i got stock while upgrading so i got a V 1.02 in my screen

can someone help me??
[HTC One S] Phil3759:
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Main thread + features + install instructions + dev support

http://xdaforums.com/showthread.php?t=2201860

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

I would appreciate a screen shot from your device, mainly under GUI options or custom backup menu where you select partitions

To take a screen shot, just slide left

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:
[HTC One S] Phil3759:
reserved
[HTC One S] RockR172:
Downloading, Flashing, Testing..

---------- Post added at 05:05 PM ---------- Previous post was at 04:48 PM ----------

Installed and tried, it boots and works! :)

BUT.

Touch is buggy for me, it just keeps on scrolling and never selects anything.. so i used buttons to navigate around..

Looks pretty neat!

This will be my regular recovery after touch gets fixed.. :) :) :)
[HTC One S] Phil3759:
I need a bit more info:

1 - when you touch menus, do they highlight on touch + validate? Do they highlight only? Or when you touch a menu, another is selected?

2- when you swipe up/down on menus: do they scroll?

3 - bottom recovery virtual buttons (the ones you can hide in GUI settings): highlight on touch and do scroll/validate? If not, what happens?

4- device built in capacitive keys: does the back key work?

After that, I can narrow the issue and maybe release another version
[HTC One S] RockR172:
1. After you touch the menus, it highlights and most of the times it scrolls down to the next option if you try to tap on it again. Can't explain exactly..

2. Yes they scroll.

3. The bottom virtual buttons don't work either. They might get highlighted at times but all that happens is the menus highlight scroll up/down.

4. The built in back key works, so do the power and volume buttons..

That's the best I could explain. :)

EDIT: On first boot to recovery, screen went black and the phone shutdown.. next boot was normal with the above mentioned issues.

EDIT 2:

https://www.youtube.com/watch?v=svY8931n340&feature=youtube_gdata_player

Uploaded a video.

Sorry for the bad quality, its recorded using my old LG P500. :D
[HTC One S] Phil3759:
Great, thank you a lot for the video

Seems wired unless device has flipped axis. Will release a debug version to see what's going wrong. Many thanks
[HTC One S] Phil3759:
Here's a debug version so that I can see what is happening:

http://www.mediafire.com/download.php?7lgtd3qrc8jdl1e

Follow exactly these steps:

1- boot into recovery, do not touch screen

2- touch once the menu "

Advanced

"

3- touch once the bottom left

Down Arrow

virtual button (those that come with recovery)

4- touch your device built in bottom left virtual key (phone "Back" key)

5- Now, do not touch screen anymore

6- Use hardware buttons to go to Advanced / Report Error

7- Post a link to the /sdcard/clockworkmod/philz_recovery.log file
[HTC One S] meke4ek:
www.pastebin.com/4W0WBRPP
[HTC One S] Phil3759:
Thank you for the prompt support :good: (out of my 8/day thumbs up)

It seems a type A touch device which I do not support for now

Will be working on it and let you know soon

Thank you
[HTC One S] Phil3759:
Very sad to see some trolls voting "1" without even reporting something

And if it is for just a broken touch, then it is even more sad as this have some functions you won't find in any third party recovery

All this takes a lot of time, and like most of the devs in xda, it is free, and done on behalf of my personal time.

So, try to show some gratitude rather, or at least give a test report before *****ing, or just shut up

Anyway, moving private debugging through PM:

I just built a new version with completely revised touch handling source. It should correctly detect your type of touch device

If some one is interested to test it, send a PM
[HTC One S] Lacuna666:
Sorry, but i get Öwner has not added any files"?
[HTC One S] AKToronto:
Pls keep up the good work on this! Im curious to see how far along things have gotten. Pls dont worry about the trolls. Theres lots of us here that appreciate any kind of development! Thanks in advance for your hard work!
[HTC One S] Phil3759:
I answered all PM

Many thanks. Still waiting for a feedback if it works + description of any issue if there is one

Understand that i have no way to test this as my GT-I9100 device drivers are fully type B compliant. That's why it takes time + i need logs and description of issues
[HTC One S] Phil3759:
Sorry, I removed the link as I got enough feedback from testers and also it was fixed on HTC Pico which had same issue

Good news, it is done

I will release a final version when I am done with last tweakings

Thanks to all who helped :angel:
[HTC One S] essentialmindz:
deleted my bad, didn't read all posts.
[HTC One S] ipit:
I'm actually looking forward to this. I love TWRP but as already mentioned, it doesn't seem to work that well on this device any more. Your efforts are appreciated.
[HTC One S] Evil-Monkey:
I'm still on CWM 6.0.2.9 touch and it works flawlessly. I tried official 6.0.3.1 and touch is buggy. I'm really curious to see what you do wig this. I love CWM and thanks for giving us options to play with!

echó en Android
[HTC One S] Phil3759:
You'll get a nice one soon.

Got completely revised the scroll interface, now really scrolling, not inverted + faking key up/down
[HTC One S] Evil-Monkey:
Cool! if theres anything i can do to help, just PM me!

Looking forward to it.
[HTC One S] LibertyMonger:
This sounds great man thanks a bunch
[HTC One S] Phil3759:
Advanced / report error

Will copy log from other place

Else, from PC, phone connected with USB, in cmd console:

adb pull /tmp/recovery.log

Or even, use Aroma File Manager to save /tmp/recovery.log to sdcard
[HTC One S] qazsxdcfv:
Roger that , sir ... :D

Sent from my hTC One S powered Trickdroid by Torxx™
[HTC One S] cicciocant:
News of this beautyful Kennedy?
[HTC One S] Phil3759:
What is missing?
[HTC One S] Phil3759:
Released v5.08.5

Change list 5.07.1 ---> 5.08.5

Please Note: Device specific threads will no longer be updated. I monitor them for support and feedback though

To check if you have a new version, subscribe to main thread:

http://xdaforums.com/showthread.php?t=2201860

Thank you for your understanding
[HTC One S] FlyinGrub:
Any news for an update with the sdcard mount issue ?

with new Jb 4.2.2 partition update sdcard has been repartitioned ..
[HTC One S] Phil3759:
you have to provide the last stock recovery.img
[HTC One S] FlyinGrub:
we didn't have it ...

but we have a modified TWRP who can make backup but not mount the usb ..
[HTC One S] Phil3759:
can you post the modified TWRP?

Maybe it is just the partitions addresses that changed, so matter of a repack
[HTC One S] g4ret:
dropbox
[HTC One S] Phil3759:
I unpacked and checked the twrp file

I see no changes in fstab file, same partition blocks

I need to know what changed or provide a device tree with the needed commit

Is it only kernel (partitions sizes) or some other device tree files?

Sorry, I am not going to read all HTC forum to get the point of this

So, please, any advanced user jump in, explain technically the issue, provide a link to commit change on github, and I will update you