Warning to Universal Users !!! Do not upgrade to AKU2 if.... - JASJAR, XDA Exec, MDA Pro Software Upgrading

Read here:-
http://www.msmobilenews.com/page/1223/

Re: Warning to Universal Users !!! Do not upgrade to AKU2 if
"Warning to Universal Users !!! Do not upgrade to AKU2 if you have bootloader v0.56 on your device, DO NOT upgrade to an AKU2 or you will turn it into a paperweight!
To check your bootloader, hold the light key, power key and press the reset button. If it says v1.00 then you don't need to worry. If it says v0.56, you must not upgrade to AKU2. If you do, the only way to fix it is to flash back to a pre-AKU2 rom or upgrade your bootloader to v1.00 (which is currenty not possible publically).
How do I know this? Personal experience and a good friend with a lot of technical know-how."

just to let you know, i've edited the article to expand on what actually happened and how i came to find that out

I have a 0.6 boot loader
Will 0.6 boot loader upgrade to the new rom or not?

I have 0.6 Bootloader and newest Qtek rom works fine.

Me too....3 Unis, all of them hv 0.6 and are running latest O2 ROM...
Once again I reapt..while flashing I hv always put them in Bootloader mode manually first and then flashed...always

sh!t
Great... just ran the update on my XDA Exec (not sure about my bootloader version), after the phone rebooted during the first mins, I got an error msg on the PC.
Now the phone won't power up, not even show any light indications when charger plugged!
Damn!

I have the problem because i have this rom and spent a lot of time to try to flash the new AKU2 rom.
I sent a post HERE
but nobody answer :evil:
And HERE
Have some responses
And now what can I do to uprade my bootloader to 1.00 ?

if you stack on Bootloader, possiblity of recover it by this post.
http://forum.xda-developers.com/viewtopic.php?p=254595#254595
if stack on the SPlash Screen, seems to be no solution now.
My Exec also stucked Splash. Bootloader Ver.1.0
My Jasjar Bootloader Ver0.60 is still alive, sometimes stucked on Bootloader after flash ROM, but can escape with the tool on that link

Thank but I don't enderstand, my Universal is working well on old rom but not with AKU2 rom.
Now I have to change the bootloader version ton 1.00
Do you know how ?
Thanks

SEB152030 said:
Thank but I don't enderstand, my Universal is working well on old rom but not with AKU2 rom.
Now I have to change the bootloader version ton 1.00
Do you know how ?
Thanks
Click to expand...
Click to collapse
so, i think,, just think and guess, V0.60 is better than Ver1.0.
Many guys had troubles in V1.0.
How to get 1.0 bootloader, i can not find the way yet.
my exec was got it when flash some ROM, but can not find wich.
also Buzz reported MTTY.exe Task 32 command can back up Bootloader and Flash, i tried it but it was said "no permission task" and can not.
http://buzzdev.net/content/view/64/115/
[Universal] How to 'd2s' dump the ROM
Written by buzz_lightyear
Wednesday, 07 December 2005
Dump Bootloader:
USB>task 32
USB>d2s 70000000 80000
OS ROM + splash:
USB>d2s 70100000 3FA0000
XtendedROM:
USB>d2s 74100000 A00000
Radio ROM:
USB>d2s 60000000 a24200

Bootloader 1.0 Update
Look for this:
http://forum.xda-developers.com/viewtopic.php?t=48590

Bootloader 1.0 Update
Look for this:
http://forum.xda-developers.com/viewtopic.php?t=48590

what is "light key" ??
I'm a newb, i saw the update for AKU2 ROM...but i dont know how to find out what version I have on my phone...
what is a "light key"

Re: what is "light key" ??
here is another link to 1.01 bootloader
ftp://ftp.clubimate.com/JASJAR_BL1.01_RUU_V1.2.zip
I have not tried it.
HTC sais that you need to upgrade to it from 1.0 if you don't see text "Serial V1.0" on screen after entering bootloader. Though bootloader works fine even without this message.

I can confirm the freezing on bootscren is still there evern after ugradation to 1.01..don't know why...I guess a bad DOC...but if it is a bad DOC then why it accepts the flash?

Related

Universal Bootloader Version ?

when I put my spv in bootloader mode, I can see on the screen :
on the top : USB
Botom of the screen V.0.56
I see in the forum that a lot of you have 1.0 or 0.60
do you think that the version of the bootloader has an importance on the good process to update the firmware.
Because all rom before 1.30 work fine
and new rom after 1.30 doesn't work on my spv.
thanks
jean sebastien
I am having the same problem. Does anybody know a way to update the boot loader to 1.00? I am at v.56.
BL v1.00
See this:
http://forum.xda-developers.com/viewtopic.php?p=275993#275993

WARNING: HTC Universal with Bootloader v.056

Re-posted from msmobilenews.com
WARNING TO HTC UNIVERSAL USERS!
Author: nedge2k on 22/04/2006
If you have bootloader v0.56 on your device, DO NOT upgrade to an AKU2 or you will turn it into a paperweight!
To check your bootloader, hold the light key, power key and press the reset button. If it says v1.00 then you don't need to worry. If it says v0.56, you must not upgrade to AKU2. If you do, the only way to fix it is to flash back to a pre-AKU2 rom or upgrade your bootloader to v1.00 (which is currenty not possible publically).
How do I know this? Personal experience and a good friend with a lot of technical know-how.
Just to expand on that, here's what happened...
I upgraded my Exec to the latest O2 AKU2 ROM, after which it would not switch on, only allow bootloader access. I then tried to flash the same ROM again. Still wouldn't switch on. I tried the Qtek AKU2 ROM using MaUpgrade-ut.exe. Still wouldn't switch on. I then connected to the device via mtty and issued the following commands:
set 14 0
task 0
...didn't work
taks 28 (then reflash)
...didn't work
taks 32
...nope
I this point I was under the impression my Exec was now a paperweight. In a last ditch attempt to make it work I flashed an old O2 ROM and hey presto, it booted up!
I was then told by a friend that it was because my bootloader was v0.56 and that AKU2 was not compatible with that bootloader. I upgraded my bootloader to v1.00 (don't ask how as I can't tell you) and sure enough, the new O2 AKU2 ROM booted first time!
Orange, O2, Qtek, HTC...all of you...sort it out!!
UPDATE: There are reports HERE that bootloader v0.6 works fine with AKU2 ROMs. So the advice is: Pre v0.6, don't upgrade! Post v0.6, go for it!
It's already been shown here: http://forum.xda-developers.com/viewtopic.php?t=48309

Stuck at Splash screen. Help!

Hello.
After upgrading, my Universal dont boot. It's locked at operator start screen.
Hard reset dont unlock it from splash screen.
If I press (ligth + soft reset), select Clean Registry Hive and Format Storage to YES, then reboots and the screen goes to WHITE.
I dont know what is happening...
SOme help please.¡
Try putting it on Boot Loader Mode and flash it back with the old ROM.
Im sorry but the problem it's that i dont have OLD rom :x
see that: http://forum.xda-developers.com/viewtopic.php?t=43592
:wink:
see that: http://forum.xda-developers.com/viewtopic.php?t=43592
:wink:
Any of this post has worked...
Readed from beginning to end.
The Universal upgrade goes well, reboot well, but frezee at logo screen...
Any idea?
jjgarcia said:
Any of this post has worked...
Readed from beginning to end.
The Universal upgrade goes well, reboot well, but frezee at logo screen...
Any idea?
Click to expand...
Click to collapse
Have you tried flashing it back to the OLD ROM or the PREVIOUS ROM you have used and worked on your unit? Try finding another link to download your NEW ROM, sometimes files get corrupted.
I tested with a lot of roms, imate, qtek, t-mob... but nothing works,... i will try to get an original rom and flash from SD card...
get connected :?
bad bad bad, not working...
:evil:
i have the same problem i also, stuck at the splash screen. i have bootloader v1.01 i first unlocked my mda pro with the buzz programm after that i flashed wit the tmobile rom. and it got stuck i reflashed it wit my old qtek rom and it still freezes at the qtek screen.
I think the problem lies on your Boot Loader version. Most of the LATER released ROM is using Boot Loader version 1.00. So anyone who flashed their device with the latest T-Mobile ROM without removing the bl.nbf file got updated to version 1.01. Thus any ROM you try to use won't work.
Try flashing your devices back with Boot Loader version 1.0, then use the old ROMs.
Yes, i have the 1.01 bootloader...
How Can I downgrade to 1.00?
Thanks in advance¡ :wink:
Some idea in downgrade bootloader?
. .. .. .. ... .. .. :roll:
jjgarcia said:
Some idea in downgrade bootloader?
. .. .. .. ... .. .. :roll:
Click to expand...
Click to collapse
Here you go my friend. Just follow the instructions from this thread: http://forum.xda-developers.com/viewtopic.php?t=48590&highlight=boot+loader+1+00
Good Luck Mate!
The solution dindnt worked, because the COUNTRY ID¡¡¡
In the post anybody solved this problem. How can i upgrade? The MaUpgrade_NoID do NOT work.
i downgraded the bootloader tot v1.00 but it still doesnt work wit the old Qtek WWE rom is used before. what to do now...
how do you downgrade? no country-id error?
shing said:
i downgraded the bootloader tot v1.00 but it still doesnt work wit the old Qtek WWE rom is used before. what to do now...
Click to expand...
Click to collapse
You have to use the Ma_Upgrade_No_ID Tool and I made a short instructions on how to use it in this thread: http://forum.xda-developers.com/viewtopic.php?t=42784&start=50
AND REMEMBER to put your device on Boot Loader Mode before double clicking the Ma_Upgrade_No_ID Tool.
cktlcmd said:
shing said:
i downgraded the bootloader tot v1.00 but it still doesnt work wit the old Qtek WWE rom is used before. what to do now...
Click to expand...
Click to collapse
You have to use the Ma_Upgrade_No_ID Tool and I made a short instructions on how to use it in this thread: http://forum.xda-developers.com/viewtopic.php?t=42784&start=50
AND REMEMBER to put your device on Boot Loader Mode before double clicking the Ma_Upgrade_No_ID Tool.
Click to expand...
Click to collapse
yeah, i already did that, but what i wanted to say. it succefully downgraded the bootloader from v1.01 to v1.00. and it also succesully upgraded the Qtek WWE rom. but it is still stuck at the splash screen (the screen shows QTEK wit a sky background and it shows the R 1.09.00 G 42.42.P8 D1.30.77 WWE)
jjgarcia said:
how do you downgrade? no country-id error?
Click to expand...
Click to collapse
i had no country error, i put my mda in bootloader mode and i used the v1.00 bootloader upgrade from the link that the guy posted in this thread.

Stuck In BootLoader After Trying To Install D810 Official ROM

Hi All,
My P3600 is stuck in bootloader after trying to install the official D810 ROM. I used the CID unlock install first, which seemed to work fine, I then tried to install the D810 ROM and it looked like it was working, but stopped at 28% with some kind of communications problem. Recovery does not work... it displays the progress bar, but then goes straight back to the rainbow bootloader screen.
Any help or suggestions appreciated.
Thanks
Rael
Phew... got it working. I removed the battery and replaced, boot loader was still displayed, and then ran the old official WM5 update which seemed to progress from 0 to 100% sucessfully.
Thanks
Rael
Your phone was relocked by the update, and I'm guessing you don't have an actual D810 that's supposed to get this update. The best method to flash this is to follow my post here:
http://forum.xda-developers.com/showthread.php?t=316410
oops, you can use hard SPL in this link:
http://forum.xda-developers.com/showthread.php?t=299659
i got the problem like you when i upgrade my device to wm6 officiel.
After you flash hard SPL Olipro, you can use PC to flash again another rom you like.
(sorry for my worth english)...
People just do NOT know how to read...sigh.

HELP: Cooked ROMS won't flash

I have Orange branded spv m700 and have unlocked and supercid'd the device using pof's tool. I then added HardSpl (Olipro 1.20). All appear to have loaded fine - phone is unlocked and Olipro shows up when put into bootloader.
So, the problem - every time I flash a cooked ROM (Ausdim, NiAx, FiNixNover...?) it won't boot past the first screen. I can rescue the situation by putting device into bootloader and flashing the official WM6 ROM (no radio, no ipl....) and it boots up just fine.
Can anybody help or at least point me in the direction of some good advice?
hmm... odd... can you list step by step what your procedure is for flashing the ROMs
I've done lots of devices - old XDA2i, SPVM600, wifes SPV M700 (unlocked, hard spl etc and flashed away!
This particular device shows IPL 0.50 & SPL 1.20 Olipro. It is unlocked (have o2 sim working in it), and should be SuperCid (I checked the box and radio shows as 1.16.00.00 - pof's patch I believe?). I also re-run HardSpl and Pof's unlock/supercid patch just in case it hadn't flashed properly.
I generally just download ROM and flash via RUU. Occasionally I get the device not responding error so I just re-run RUU from the bootloader screen.
Have tried WM 6.1 and 6.0 cooked roms but all show initial boot screen (numbers along bottom) next screen and then frozen, have waited and waited and nothing. Also, it would not flash back to Mozzers WM5 Orange UK ROM - same symptoms. I thought it was bricked, but the Dopod WM6 flashed perfectly.
Hope that helps - thanks for looking into my problem.
anybody please? por favor........
hmm.. i remember someone having a similar problem but it was some time ago..
two things to try just in case...
1) i'd manually go to bootloader (hard-spl) before flashing
2) Have you tried to flash from SD card? this method seems to provide less problems..
let me know how it goes..
A degree of success - managed to flash WM6 AX3L. All seems to be working. As I recall this is very similar to the official ROM and I used to use it last year because it is very stable. Think I moved on because of the missing email accounts problem. Will happily keep it if I can sort the email problem out. Never really had much fun with the hard reset after loading method - is there another/better way? Just wondering.
Also, now I have a "cooked" rom loaded perhaps it will stop being so sensitive.....!!
How strange! Have just flashed Akeo's new Diamond port ROM and no problems. Not only that, the ROM is FAB!!!

Categories

Resources