Database Users

One more brick to the Cathedral

This is my first Thread and unfortunately for the worst reason, that’s right … my WISA200 (Qtek 9100) is officially a brick.
For one week now that I’m surfing this forum looking for a solution. No success.
Long story short….
I’ve “see the light” with XDA and got so addict that I’ve started to make all the ROM’s I could get my hands on…last I got RUU_Molski.Biz_226102_22610105_022511_WWE-30MB (G3 Device. IPL/SPL like: 2.xx) and I was a very happy person, thanks to Molski.
The problem was that my enthusiasm did not stop and I made the big mistake …my own ROM.
My idea was quite simple, use the 3.0 Molski Rom thaking out the extended and that’s it, clean OS … I’ve tried sereval times and versions without any problem until one week ago...
I got the boot screen and never got read of it. The strange thing is that when previously the IPL and SPL were 2.26, now is IPL 2.26 and the SPL 2.18.0001.
I’ve already tried everything, without success …..
Downgrade:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Old Molski great job (how I miss it):
and even MiniSD image:
Nothing works …..
I’ve Google search (it always goes back here) and nothing……
Has any one got this boot screen before?
Thanks in advance even for those who just will read my post and … why not …laugh on me ….brick nerd….
Obrigado,
The Nerd

If it's getting as far as the boot screen, you should still be able to get into the bootloader (see wiki) and try a flash that way.

Looking for help .....
Alan, thank you for your care and time reading my post.
Unfortunatelly I've spent my day using the different bootloaders tools and solutions and nothing works .... or I'm making the wrong procedure. I've even created (I think) a MiniSD SPL upgrade, but it did not work.
It seams the phone stops responding when I try to make any think.
MTTY without error, seams not to do anything although it connects to the phone ...
If anyone else has any ideas I would apriciate a lot.
Once more thanks Alan.

HAPPY
I did not stop trying even though the bootloader did not work properlly, so still I insisted on inserting a rom, and I've tryed this one:
Qtek_9100_Telia_Danish_2.18.7.9245
Now it is on 98% I am really happy.
I'll keep you guys posted.
Nerd!

now that u got that far.... go as alan points out to this thread with unlock advice and follow the procedure to get a good bootloader unlocked and all

the process went all the way to the end but it came back again to the bootscreen rgb screen without any change still the IPL is 2.26 and the SPL 2.18.0001, does this mean my wizard is G4 and all the problems come from there? .....
I've made the format procedure, but still gives me FAT error.
Also I made a huge digging in the wiki and all posts to get in to the bootloader to change it or correct the SPL nothing has worked for me. Does any one has a SD image (any langue dont care!) which might solve me the problem?
Thanks a million.
Nerd ....
I promisse if I solve this I will never make a rom again!!!!

Problem solved!!!!
The issue was a new motherboard ... yes... hardware failure.
As anyone expirenced similar issues?
Thanks to all support.

When you tried to flash to molski's rom it gave you an error 300 message. This message is usually displayed on a G4 device (you're SPL is a G4 SPL now). I think it could be flashed to you're device if you replace the "ROMUpdateUtility_Wizard_NoID.exe" with the one that works on G3 and G4 devices from this thread:
http://forum.xda-developers.com/showthread.php?t=291215
If this doesn't work, try flashing the wizard_love rom. It seems to flash to almost every device out there.
Good luck!

I need the original Vodafone splash image

Hello,
In order to take it to repair (again) for the G sensor problem I need to put back the original Vodafone splash screen.
Can someone upload it somewhere?
Also I have an engineered spl (had the perfect one). Should I change it too? Or the guys from the repair won't notice that?
Thanks

you should change the spl to a standard one really as they will tell straight away. Do you know what your orignal one was?
Cant find the original splash screen but heres a similar one i have made
The image looks pants in preview but is perfect once splashed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for the image.
I had the 1.33.0010 one. Now it's the same but engineered with S-OFF.
Where can I find the original one?
I had a nandroid backup of my original rom after changing the SPL. Now i'm running the original software, but with wrong spl. It will be enough just to apply the the perfect SPL before going to repairs?

I woudnt like to say really, i have had mine repaired it had the spl for g1/dream n it (bricked) i didnt get charged for the repair
This thread has shipment spl Thanks to AMON_RA

I had mine repaired too, ut it was bricked...so it was impossible to say that i had another rom/spl. But now the scenario is different...the phone is up and running. Only the G sensor isn't working

you tried doing a factory reset?

And not just once...
In Teeter game the ball is going in the upper right corner and is staying there no matter what.

Have you tried amon ra recovery 1.2.3?has a fix rotate option in the recovery,you don't have to flash it only boot.
Could you tell me all The about phone info like kernel etc for the original voda rom? Would be a great help to me.

Just tried the repair from the recovery...no luck with it.
Also i jst figured that I don't have the original ROM anymore....I will try to take it from someone else. And after that....repairing center
Another thing....how can I put back the original perfect SPL (1.33.0010)?

I made a nandroid backup of the South African Magic ROM when I first got the phone. If someone can tell me how to upload it, I will.
In return, if someone can help me root the phone, that would be greatly appreciated. I've got the recovery flasher loaded, and it seems to work, but any attempt to load a custom ROM just ends up in a hang and I need to revert.
I don't think most ROMs are compatible with whatever customised software we use here. It may have something to do with the radio version. DON'T FLASH A RADIO UPGRADE! I learnt that the hard way.
Regard,
H

I've managed to change the eng SPL 1.33.2010 S-OFF to 1.33.0009 S-ON and now I cannot change the splash screen anymore...
How can I keep it on the original SPL side but with the Vodafone splash image?
Thanks

flash the image BEFORE you flash the perfect spl

I couldn't find the perfect SPL...so now it's in the repair center wit 1.33.0009 S-ON spl and the original rom image in it...maybe they won't find that as it's a hardware issue for sure.

strange 32B

Hi there
I got a white 32B from German Vodafone.
Code:
SAPPHIRE PVT32B SHIP S-ON G
HBOOT-1.330007 (SAPP10000)
CPLD-10
RADIO 2.22.19.26I
Jul 31 2009.15.49:25
It has 1.2.1 recovery, which is nice, as I can change the ROMs, but...
I have no idea how the guy flashed this recovery. I'm trying with the second phone (exactly the same)
The method with original RUU and downgraiding, fails (wrong RUU for this model).
I can't fastboot boot or fastboot flash on both phones. I get FAILED (remote: not allow) and the SPL is NOT perfect!
The guys here:
http://forum.xda-developers.com/showpost.php?p=4649780&postcount=43
have the same problem.
How can i use fastboot? Guess the perfect method is not for me.
How can I root the second phone? It has 1.6 now and refuses to go back to 1.5...
Ok the method with flashing ENG SPL via update.zip via recovery worked for the 1st phone (http://forum.xda-developers.com/showthread.php?t=529019)
Now it's only how to root the other...
BTW What does RADIO mean (on the fastboot 3-boards white screen) ? I can't find it...

It seems that we have the exact same model
As you saw on my thread, I used the 1 method click to flash the recovery rom, and from that install the ROMS.
As for the flashscreen, I did not find an answer, I guess that the only solution will be to flash a new SPL that allows to flash through fastboot.
On some threads that I created and were blocked since they were in the wrong section(I was stupid, twice...), they have sugested to update to the Engineering SPL 1.33.2005 using the recovery method tool.
I have never tried it since I haven't seen anyone with HBOOT-1.330007 that have changed its SPL... I don't want to risk bricking it... I have been told that there are some risk, but not too big... any way, I still have not tried to flash the SPL.
You said that you have flashed a first phone with a ENG SPL, what was its original SPL and how did you flashed if?
Here are the threads that were closed:
http://forum.xda-developers.com/showthread.php?t=567517
http://forum.xda-developers.com/showthread.php?t=567497
Here is a message that may be important:
http://forum.xda-developers.com/showpost.php?p=4643066&postcount=164

I had this spl inside my Magiic from Voda Germany
HBOOT-1.33.0007 (SAPP10000)
I used "RecoverFlasher" to get another recovery inside.
Then I Booted into recovery mode and flashed
HBOOT-1.33.2004 into the phone.
It is now running perfectly well with AmonRA s rom
and AmonRa 1.23 recovery inside

Eurocrypt said:
I had this spl inside my Magiic from Voda Germany
HBOOT-1.33.0007 (SAPP10000)
I used "RecoverFlasher" to get another recovery inside.
Then I Booted into recovery mode and flashed
HBOOT-1.33.2004 into the phone.
It is now running perfectly well with AmonRA s rom
and AmonRa 1.23 recovery inside
Click to expand...
Click to collapse
Humm, thats excellent news, finally someone with an HBOOT-1.33.0007 that had changed its SPL
Thanx
Did you use the "Engineering SPL 1.33.2004 - MD5 : 1B49F0A53E147171E7C51F08510CF95F" from http://forum.xda-developers.com/showthread.php?t=529019?

Well for now I've got
1. white 32B with an eng SPL (Engineering SPL 1.33.2010 - MD5 : 865020FBDFBD9C08950076A701A8A003) changed from 0007 (http://forum.xda-developers.com/showthread.php?t=529019). recovery 1.2.1 -> select zip file -> reboot and it worked. then i flashed my boot screen with fastboot, as in the tutorials.
i'm doing everything using the recovery and the 'update.zip' position in the menu. right now having cyanogenmod 4.2.2 with my native Polish keyboard installed as an app from the market. Works great.
2. black 32b with Donut 1.6 which refuses to do fastboot and adb flash. What's more HTC Sync doesn't recognize the phone and the RUU (from the 1 click method) says there's an error with the files (and shows strange ROM version installed on my phone)

skhell:
Thats the one I used

Altembas said:
Well for now I've got
1. white 32B with an eng SPL (Engineering SPL 1.33.2010 - MD5 : 865020FBDFBD9C08950076A701A8A003) changed from 0007 (http://forum.xda-developers.com/showthread.php?t=529019). recovery 1.2.1 -> select zip file -> reboot and it worked. then i flashed my boot screen with fastboot, as in the tutorials.
i'm doing everything using the recovery and the 'update.zip' position in the menu. right now having cyanogenmod 4.2.2 with my native Polish keyboard installed as an app from the market. Works great.
Click to expand...
Click to collapse
I am starting to like this thread, I see that I can flash two SPLs on my phone with no problem
2. black 32b with Donut 1.6 which refuses to do fastboot and adb flash. What's more HTC Sync doesn't recognize the phone and the RUU (from the 1 click method) says there's an error with the files (and shows strange ROM version installed on my phone)
Click to expand...
Click to collapse
I guess that your only option will be to use the "Gold card" method, but I really don't know how that works, there are quite a posts over the forum with info on that, a quick search will tell you how.

I keep getting this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and later err 155...
seriously wt*?

Have you tried the "Gold card" thing?

nope, i don't feel like buying and then destroying an SD card I'm not that desperate... yet!
I'm concerned about that RUU which shows vfpioneer-user instead of the ROM version...

Altembas said:
nope, i don't feel like buying and then destroying an SD card I'm not that desperate... yet!
I'm concerned about that RUU which shows vfpioneer-user instead of the ROM version...
Click to expand...
Click to collapse
I don't know how the goldcard method works, but how will it destroy your SD card?

I've found in some tutorials that when you write bytes to the card it stops working as a normal card. Probably because you write from sector 0, and i guess there is some important data stored.
If personally find it VERY odd. If you can use (under linux) dd to write to the card, then you can use it to read from it it's original bytes and restore them later. That is ofcourse if the card (after turning to goldcard) will be recognized as a SD card...

Altembas said:
I've found in some tutorials that when you write bytes to the card it stops working as a normal card. Probably because you write from sector 0, and i guess there is some important data stored.
If personally find it VERY odd. If you can use (under linux) dd to write to the card, then you can use it to read from it it's original bytes and restore them later. That is ofcourse if the card (after turning to goldcard) will be recognized as a SD card...
Click to expand...
Click to collapse
I do believe if that happens, if you make a copy with dd, you can safely restore it. Just to be sure, you can also make a backup of the partition table of the sdcard.
Oh, the dd tool is also available to windows, but I guess this kind of things should be done on linux

I don't mind using linux. Actually I use both everyday. And it seems easier to use dd than some fancy hex editor under windows.
Anyway, my only concern is that, I may overwrite the bytes which identificate the card as a SD card (and not as a MMC for instance) and then the usb reader and linux woun't be able to use it... So there will be no way to use dd to restore backup...
On the other hand, I'm pretty sure I'm exaggerating and the only problem some ppl had was with the Windows Hex editor editing to much. I see no reason why the 'dd method' shouldn't work...

Ahhhhhhhh!
Finally some progress, little but still. RUU finds my phone (and version number) only if my magic is in fastboot mode! Then it actually works, until it starts to check the CID number...
rom.zip contains android-info.txt which has a different cid number (i'm talking about the 1click method).
The question which arises is why can't i edit rom.zip and put there recovery flash, eng SPL, modified ROM and force an update by changing CID in .txt?

And an answer:
because CID check is done between the phone and the .img files, the txt is only supplementary. So preparing another .zip file doesn't work
Back, to where I was 3 days ago

Am I good to flash radios?

There's a thread over in the development section with a could of radios, and I was gonna try flashing the third one.
This is the thread:
http://forum.xda-developers.com/showthread.php?t=1059347
My question was whether or not I was clear to flash them. I used the visionary method to root, but does that mean I have radio S-OFF? I've rooted the phone, i have the engineering bootloader, and I've flashed roms before. I'm nervous to try a radio because I've heard flashing radios is one of the more dangerous things one can do with an android phone. Also, will all of the mytouch 4g roms still work, including stock?

No you need real root perm S-Off plus engineer bootloader. Visionary is just temp root every time you reboot you'll lost root.
Sent from my Desire HD using XDA Premium App

I did the permroot using visionary method. I have the eng hboot and S-OFF. I know what you're talking about, but there is a way to permroot using visionary.

kimbernator said:
I did the permroot using visionary method. I have the eng hboot and S-OFF. I know what you're talking about, but there is a way to permroot using visionary.
Click to expand...
Click to collapse
what version of visionary? Last time i check visionary is just temp root. Then Good luck to you bro.

Visionary has been perm root for months now, but he would still need to Gfree to S-off.

I used visionary for perm root s-off on stock rom, and just updated the radio thru hboot, so you should be able to do the same thing.
[via XDA premium]

Wait, he's talking about using the root.sh file to gain S-OFF. He didn't use the Gfree method like most of us. I'm still rooted using the root.sh file. Will it work, he's raido is still S-ON but his bootloader is S-OFF. I remember reading somewhere when I had the G2 that, the radio is still locked.
Wait, just to be safe, root using the gfree method and then flash the radio.

sleepyfu said:
I used visionary for perm root s-off on stock rom, and just updated the radio thru hboot, so you should be able to do the same thing.
[via XDA premium]
Click to expand...
Click to collapse
That's just what I needed to hear.

And by the way here's proof that there is a perm root visionary has a permroot method - this is my phone.
I think this is enough to be able to flash a radio, right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

That is correct... You need the g-free method (ultimate s-off/radio off) to unlock your radio, so the new one can be flashed.
You also should install the eng. bootloader.

vabeach454 said:
That is correct... You need the g-free method to unlock your radio, so the new one can be flashed.
You also should install the eng. bootloader.
Click to expand...
Click to collapse
See above pic

kimbernator said:
And by the way here's proof that there is a perm root visionary has a permroot method - this is my phone.
I think this is enough to be able to flash a radio, right?
<image snipped>
Click to expand...
Click to collapse
Here's the thing: VISIONary is ALWAYS used to temproot and to permroot, but somewhere in between you need to run an exploit script. You used root.sh to root your phone. Other people have used gfree to do it. That's where methods differ, so saying "I used the VISIONary method" is unclear and doesn't tell us exactly what you did.

jdkoren said:
Here's the thing: VISIONary is ALWAYS used to temproot and to permroot, but somewhere in between you need to run an exploit script. You used root.sh to root your phone. Other people have used gfree to do it. That's where methods differ, so saying "I used the VISIONary method" is unclear and doesn't tell us exactly what you did.
Click to expand...
Click to collapse
Ohhhh, fair enough. I'll remember that next time. But this still doesn't really answer my question. Is it safe to flash a new radio after using that method?

According to your photo you can flash the radio.
Here is a good post about radio s-off mean.
http://forum.xda-developers.com/showpost.php?p=9540801&postcount=29
[via XDA premium]

sleepyfu said:
According to your photo you can flash the radio.
Here is a good post about radio s-off mean.
http://forum.xda-developers.com/showpost.php?p=9540801&postcount=29
[via XDA premium]
Click to expand...
Click to collapse
I read it, but it doesn't provide a way to tell if you have a REAL radio s-off or not.

kimbernator said:
I read it, but it doesn't provide a way to tell if you have a REAL radio s-off or not.
Click to expand...
Click to collapse
You don't have radio s-off because you only used visionary method to perm root and I wouldn't flash other radios if I were you, just to play it safe. You need to use gfree method here to get radio s-off (turn off radio's security completely). You need to restore back to stock ROM for gfree to work because it didn't work for me when I was on another ROM and I had to restore back to stock and do gfree method. If the gfree method from the previous link that I gave, doesn't work, try this newer one from here. You can find instructions and download links to HTC Glacier's radios from there also and other files.

Oooh for the love of god people you made me post. I don't normally post but in this case ill make an exception. Now listen carefully as ill say this only once.
You do NOT need to have "Radio S-OFF" via gfree for it to flash the RadioROM. All you need is S-OFF and yes using VISIONary+ permROOT you can flash the new radio. All you have to do is download it and place as /mnt/sdcard/PD15IMG.zip and restart in to the bootloader. Once its detected just follow the instructions and press down to accept or up to deny.
You do NOT need gfree meth to flash the radio has it can be done using VISIONary+ permROOT. I hope this clears that about the OP.

what does flashing the radio accomplish?

Looks like I have to post again. The RadioROM controls the device's power control along with other radio interfaces for example wireless, data, wifi, bluetooth, gps, ect. Since resection capability is also handled in Radio each can have different impact on cell/battery which depends on the location thus not giving same results for all users. On serious note RadioROM bricks the phone if image is corrupted due to the radio bootloader which is always device specific thus controlling the firmwares that is directly interfacing with the OS.
PS: When you mess with the RadioROM's you get Hard-Brick not Soft-Brick.

TmpUsr said:
Looks like I have to post again. The RadioROM controls the device's power control along with other radio interfaces for example wireless, data, wifi, bluetooth, gps, ect. Since resection capability is also handled in Radio each can have different impact on cell/battery which depends on the location thus not giving same results for all users. On serious note RadioROM bricks the phone if image is corrupted due to the radio bootloader which is always device specific thus controlling the firmwares that is directly interfacing with the OS.
PS: When you mess with the RadioROM's you get Hard-Brick not Soft-Brick.
Click to expand...
Click to collapse
Thanks for the help, but quit acting like it's such a hassle to post on a forum...

Help with Rooting Mytouch 3g 32A

I have been trying for the last 18 hrs to root my Mytouch 3g 32A and having no success...
The specifications are:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.28.25 (62.50SJ.20.17U_2.22.28.25)
Oct 21 2009
I tried several methods; Androot, SuperOneClick 2.1.1 and this other method called HTC(Cant remember the rest of the name)
None works and it is incredibly frustrating because I want to flash a new OS since the wifi and camera arent working and I think it is a software error.
Searching around I saw something saying that the phone may be a 1.2 variant(it lacks a 3.5mm jack though)..
How do I get this to root? My last android was a g1 phone 3 years ago and I rooted and flashed without any problems whatsoever.
Thanks in advance.
P.S.
For SuperOneClick the process runs but when it comes to the point of testing it says "testing failed"

herrhorace said:
I have been trying for the last 18 hrs to root my Mytouch 3g 32A and having no success...
The specifications are:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.28.25 (62.50SJ.20.17U_2.22.28.25)
Oct 21 2009
I tried several methods; Androot, SuperOneClick 2.1.1 and this other method called HTC(Cant remember the rest of the name)
None works and it is incredibly frustrating because I want to flash a new OS since the wifi and camera arent working and I think it is a software error.
Searching around I saw something saying that the phone may be a 1.2 variant(it lacks a 3.5mm jack though)..
How do I get this to root? My last android was a g1 phone 3 years ago and I rooted and flashed without any problems whatsoever.
Thanks in advance.
P.S.
For SuperOneClick the process runs but when it comes to the point of testing it says "testing failed"
Click to expand...
Click to collapse
Guten tag, Herr Horace
Before anything else, make sure USB Debugging is enabled in the phone's Settings menu. Also, if you have HTC Sync installed on your system, make sure it is disabled before you try rooting.
According to this SuperOneClick thread:
THe HTC Legend and My Touch 3G 32A also have a NAND lock and need more specific methods to unlock.
Click to expand...
Click to collapse
Rather than trying for Full Root (Level 3) right away, see if you can get Shell Root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see the Shell Root button is right next to the Root button. If you can get Shell Root, you'll be able to move on to the next step.
If it still gives you problems, try this suggestion: DISABLE USB debugging on the phone, click the Root button in SuperOneClick, wait for SuperOneClick to say "Starting ADB Server", ENABLE USB debugging, then DISABLE USB debugging.
If you cannot get Shell Root, try to give us the exact error messages or output that SuperOneClick gives.

You can try also with flashrec and a custom recovery image,then you can change the spl and radio as you wish and flash any ROM you want.(this is the metode regarding gettin root an my device) L.E: http://forum.xda-developers.com/showthread.php?t=547133
Sent from my HTC Magic using xda app-developers app