Related
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Did you use WM6.1 or WM6.0 to unlock the phone? Put in boot loader and flash orginal WM6.0 ROM as the other user suggested. You should be able to flash it if it is not a brick.
If it doesn't work you can use mtty to recover your phone, the needed information you'll find in the Kaiser Wiki.
Hope it helps
I just had this exact problem.
Use the EXE included in the tutorial to flash any windows 6.1 ROM from the bootloader via USB, and you will boot again.
HTCOmega said:
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Click to expand...
Click to collapse
I know. The crazy thing is that I've successfully flashed a G3 and a G4 Wizard and I still find this confusing.
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
When I reset the device normally I get:
R 1.27.12.11
G 22.45.88.07H
D 1.62.00.00
I didn't try to flash any other ROMS to unlock it. I just went with the hard SPL and then tried the Unlock tool. The phone is stock.
Thanx for the replys. I reflashed the original ROM and now it's working again. This is what I have now:
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
Now when I reset the device normally I get:
ROM version 1.62.502.0
Radio version 1.27.14.09
Protocal version is 22.45.88.07H
Device info:
Windows Mobil 6
CE OS 5.2.1622 (Build 18128.0.4.4)
Can I go strait to a SIM unlocker and then flash a new ROM?
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
A couple of things:
1) The Kaiser-Unlocker only works on 1.xx hardspl's, so you'll have to put one of those on first.
2) You do need to install the patched radio before you run it.
3) You'll need to flash a compatible radio afterward too, or else your device might not boot all the way.
4) Next time please post these questions in the thread for the unlocker you are using. It makes it much simpler for everyone.
stuff said:
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
Click to expand...
Click to collapse
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
So I guess I went wrong with flashing 3.56 first and not 1.1
Then I need to patch the radio
Run the unlocker
rinstall the radio
Then flash the ROM
Problem I have now is that I can't seem to go back down to a lower SPL version.
shawndh said:
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
Click to expand...
Click to collapse
You need to read the instructions carefully, and ask questions in that thread. All the experts in unlocking will be there to help you.
I did a search, and dont see anything to answer this specific question.
Ive got my new Dev 1, and have the latest JF update. I want to install some cool themes, however, I know its a possibility to brick my phone.
Exactly how easy is it to brick your phone while installing a theme? I plan on following the directions step by step, but I will be very upset if something happens.
Any advice would be much appreciated. I suppose I just need some reassurance...
Thanks in advance.
Not too easy but if you Flash a corrupted SPL your toast
not very easy, just remember, if it boots to the SPL or recovery mode you are fine, it's not a true brick. if it doesn't boot at all then you may have an issue. i have had many times where the phone decided it didn't want to boot past the boot screen, or the flashing android and yet i am able to post this now using my phone as a tether. if you get stuck on one of those screens then you need to either flash the dreaimg.nbh or a new update.zip including the full JF build
Dredge said:
I did a search, and dont see anything to answer this specific question.
Ive got my new Dev 1, and have the latest JF update. I want to install some cool themes, however, I know its a possibility to brick my phone.
Exactly how easy is it to brick your phone while installing a theme? I plan on following the directions step by step, but I will be very upset if something happens.
Any advice would be much appreciated. I suppose I just need some reassurance...
Thanks in advance.
Click to expand...
Click to collapse
Why are you so worry about brink your phone? If you want to brink your phone pour some concrete on the phone and make a customize brink G1.
tubaking182 said:
not very easy, just remember, if it boots to the SPL or recovery mode you are fine, it's not a true brick. if it doesn't boot at all then you may have an issue. i have had many times where the phone decided it didn't want to boot past the boot screen, or the flashing android and yet i am able to post this now using my phone as a tether. if you get stuck on one of those screens then you need to either flash the dreaimg.nbh or a new update.zip including the full JF build
Click to expand...
Click to collapse
whatever he said....^^
I've flashed themes that were designed for RC3xx on my ADP1.1 and managed to "bricked" it. All i did was go to bootstrap and reload the SPL with RC29 and re-flash ADP1.1 to the phone.
As long the hard-SPL on the bootstrap remain untouched, there's always a way to recover your phone...it may be long, boring, and redundant...but it will safe your G1 from truly becoming a brick...or paper weight...or both
This makes me feel a bit better. I will just back up the latest JF update and keep it in case something happens. I will probably just hold off at tleast for a little while before I try doing much. I need to get a feel for the phone before I try to mod it. I found some cool wallpapers that should tide me over for at least a little while. But the clock is u-g-l-y. Im use to having TouchFlo, with HHC, and all the neat custom clocks.
Well, thats why I am probably not going to update my SPL...
I own an ADP1 and so already got the engineering SPL... and as the SPL update seems for me to be the only way to brick my phone... well, I am a coward...
It may be a little offtopic, but i am planning to update to JF1.43, or perhaps even messing around with Ubuntu MID (if ever possible).
Is there a really good reason I should update to HardSPL?
HELP I CAN'T GET DREAIMG.NBH Installed!
I just tried to downgrade my G1 from RC33 v1.42 + Radio Update 1.22.14.11!!!
I think I made the mistake and downgraded my bootloader from SPL_Hard to Original RC29_ SPL, because I was having trouble getting the file Dreaimg.nbh, recognized after booting holding camera + power buttons.
After downgrading from SPL_Hard to Orig RC29, I was able to boot holding the camera + power buttons, and the process started, but just before completing I got an error, FAILED TO UPDATE TERMINATING, and now my phone only reboots to the SPL screen with this showing:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
SEP 2 2008
I believe it's has to due with the Radio Update 1.22.14.11...
I'm going to try using QMAT and follow the Inst from that same thread. If that doesn't help can some offer some help???
Follow UP!
QMAT WORKED:
http://forum.xda-developers.com/showthread.php?t=490960
Sorry about the double posts!
Ok here goes. Be nice, I'm new...
I have a Stellar in front of me (or Kaiser, TyTynII etc) which has managed to get itself into Boot Loader. I'm usually pretty good at getting these out of it but this one has me stumped, and I'm hoping someone may be able to give me some suggestions, or confirm my suspicions that it is kaput.
It's in Serial mode at the moment, showing
KAIS130
SPL-1.82.0000
CPLD-8
on the top of the screen.
So I plugged it into the computer and it nicely popped into USB mode which then let me flash it, using the file: RUU_Kaiser_O2_UK_1.82.206.1_radio_sign_22.45.88.07_1.27.12.32_Ship
This appeared to take, started the process, splash screen loaded, windows mobile loaded OK and for all intents and purposes was back at the factory reset (which is what I wanted). HOWEVER.....when I performed a soft reset it went back into Boot Loader and I'm now back at square one.
Any ideas? I can't install any homebrew ROMs on this, it HAS to be the standard ROM for reasons I'm not at liberty to post here (don't worry nothing illegal is going on, suffice to say, I shouldn't really be here!)
I have at least 2 others that are doing similar as well and would like to get these fixed also. All help/comments gratefully received and I apologise again if this is covered somewhere else.
It seems you have not done any SPL hard flashing yet.
Did you really read the Flashing for Noob sticky ? It's there .. first you need to do hard SPL, SIM/CID Unlock, then only you can change your ROM to anything.
Please go back and re-read.
Sorry. Will this do anything bad to the device, only I've never done anything like that before, I've just run the ROM flash file. I've never had to do anything like you suggested before. It needs to be put back to factory as it is going to get allocated to someone - which means I then have to install a clone over the top of this.....sorry if I'm being thick. I did read the document you suggested but that resulted in me getting more confused.
If this is not the right place for me to be, please feel free to close this thread and I'll keep looking elsewhere. Cheers.
Hi,
First of all: what do you want to do? Read this to clarify your intention
Take your time, read through the WIKI first.
After that, if you still want to flash, go to the Noob sticky.
If you don't have the passion, I'd suggest just use the phone as from factory. Reading the Wiki still will give you insight and many good tips/tricks without flashing.
Edit to addI apologize.
After re-reading again, it seems that what you're trying to do is reviving the dead Kaiser. From the SPL version, it's not yet 6.1. You can check out here to see any other official ROM matches, which what you currently use seemed to be correct.
Mod, please merge this with Kaiser stuck at Bootloader thread ..
Good luck.
Edit 2
It seems that when you did a soft reset (by pushing at the small hole using stylus?), the other two buttons (camera + power) are still pressed (or due to hardware, kept being pressed), thus resulting in boot loader displayed again?
Well that's why I couldn't work out why I couldn't get the ROM to stay.....this has never happened before! So yes, I am trying to revive a seemingly busted Kaiser. The customer handed it to me in Boot Loader mode. Usually running the RUU fixes this and we can then go about rebuilding it. However in this case it really doesn't want the factory ROM but I need it to! I can quite easily get it into USB mode and flash it by running the .exe file on my desktop - but then that's about all I can do. I can't give it back to the customer as the next time he performs a soft reset or switches it off, it'll be back in Boot Loader...ARGH!
Oh, and apology accepted!
And another thing, I just tried running the exe file again and got as far as the screen alignment and the poxy thing just locked....cue soft reset and back to Boot Loader. Me not happy.
Edit: A quick check of the Hardware and all the buttons appear to be OK - nothing looks like it's stuck down
If you want to take the looooong road, perhaps you can do flashing Hard SPL, unlock SIM/CID and then flashing any other ROM/Radio. Once you get a stable working device, you can flash back the OEM using this method
I'm not sure if this custom RUU can help: http://forum.xda-developers.com/showthread.php?t=334890
I haven't tried that, so it's just an idea for now.
Thread closed.
If you are still having problems with the bootloader check out my sticky.
If you need help with the flashing process check out mskip's sticky.
Only create a new thread for new issues that have not been discussed before.
Good luck
Thanks
Dave
OK, I too skim read (I read a lotta threads ).
PDA-Princess
I've sent you a PM.
Dave
Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
As far as I know, it's not possible until T-Mobile releases an OTA update for either the Fender or MyTouch 3.5mm. That was explained in the rooting instructions here on XDA...
merlino211 said:
Hello...
I've been frantically googling and checking the forums, I have a mt3g 1.2 (3.5mm) that needs to be exchanged to t-mobile, I rooted following the stock fender w/ root method, and need to revert it back to the stock settings as shipped. So far, my search has turned up no resolve. I was hoping someone here could provide me with the proper sappimg.nbh to restore. I've got the one for the original MT3G, but it (as expected) damages touch-screen capabilities. Can someone please help?
Click to expand...
Click to collapse
If you use the stock rom http://www.theandroidkitchen.com/fileshare/MyTouch3g32A/?download=MT3G32AFender-1.0-fixed-signed.zip and then you should have touchscreen. It's only with custom roms that touchscreen does not work.
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
shawn1224 said:
Couldn't you just flash the Mytouch splash image and turn in in like that?
It looks pretty stock after that.
Click to expand...
Click to collapse
... you got the splash image handy?
kbeezie said:
... you got the splash image handy?
Click to expand...
Click to collapse
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
ceas909 said:
you can find the stock mt3g splash screen if u search on here but not the fender one... i got the stock myt3g splash on my 1.2...
Click to expand...
Click to collapse
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
kbeezie said:
That's what I'm saying though, no one seems to have the fender one. Far as the op's situation, might have tried flashing one of those "32A" roms, which obviously won't work at this point, probabbly best to just try the rom from my signature (the one linked as Rooted), which is basically the stock rom and touchscreen and all that should work.
Click to expand...
Click to collapse
yea he has a 1.2, so yea i think his best bet is to get the stock mt3g splash screen and the stock fender rom... the only problem is that between the fender and the 1.2 the build number is different..the 1.2 is 2.10.531.4 CL119339 release-keys where the fender is 2.10.531.3 CL111099 release-keys .... but a simple edit of the build prop could make it display the correct buid numbers in the about phone menu..
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
UPDATE!!
Click to expand...
Click to collapse
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Update 2.0
Click to expand...
Click to collapse
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
merlino211 said:
I've actually attempted to just replace the splash with the original mytouch splash. This can be achieved by applying a proper SPL that will allow it to be replaced... PROBLEM being that after repacing the SPL with the ones linked: theunlockr[.]com/2010/03/10/how-to-change-your-splash-screen/
Once this process is taken, the radio functions and all seems well, EXCEPT that now when I place calls, my speaker does nothing. Phones can receive the calls and hear me, but I hear nothing. the end result is to reflash the phone with the rooted rom, minus the mt3g splash... This part is where my frustration is kicking in as their guide claims this is specific for the fender/mt3g 1.2, but yet bricks the speaker somehow.
It appears that the guide on unlockr is wrong for this phone. I was successfully able to get the splash back on the phone by implementing the steps of adding the splash DURING the initial radio and recovery image restores, at which point the sappimg used is the engineering 2010. Once the splash was loaded at this point, I was able to continue with the install, install the rom, but a fresh install would *not* boot into the OS, just hung on a black screen after the animated "android" splash. Upon restoring a nandroid back-up, the phone booted to the OS in its formerly operational state, mt3g splash included.... I'm going to attempt a factory reset from the phones main options purely to see if it'll boot or hang on the black screen again.
Methods were all successful, factory reset worked to bring the phone back to the android setup wizard WHILE retaining the splash screen with no blank screen as described earlier... Process was as followed:
Performing the unlockr guide; during the following steps:
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
the phone is currently running the SPL for the Engineering SPL 1.33.2010... I modified the above process to reflect
fastboot flash splash1 splash.nb
fastboot flash radio radio.img
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Recovered from the rooted fender stock image, which then took me to a blank screen. Recovered from a nandroid back-up, which restored the phone to my state just prior to (re)flashing. After nandroid backup is restored and successfully making calls, factory reset was done and test calls were successfully made from the freshly reset version of fender/wroot stock.... A bit hackish and unorthodox, but it answered the question I was so valiantly struggling to find resolve to.
It appears the stock fender /w root reverts the hboot version to the non-engineering, which functions fine with the speaker.... Hope this helps someone else who was in the same boat as me.
Click to expand...
Click to collapse
Or you can just goto the thread in the link of my sig ("rooted"), you want to make sure when you're reading guides that they are for your specific phone, some people have bricked their fenders or 1.2 cuz they got the wrong radio/spl intended for the older MyTouch3G
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
merlino211 said:
I made sure to use the right guide on the unlockr, the problem came specifically from where they had the SLP change guide... Either way, problem is fixed now and it'll be in the hands of the t-mobile store tomorrow. If I ever doubtfully get a question about the root from them after it ships back, I'll play dumb and inquire if maybe someone else did it while it was waiting to ship
Click to expand...
Click to collapse
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
ceas909 said:
i hope they dont catch the build number being different.. as i stated in eairler post the build nmbers in the about phone menu are different from the fender and the 1.2
Click to expand...
Click to collapse
In my experience most sales reps are completely ignorant of that kind of thing, changing the boot screen may be enough to make em go along with it. IF you're dealing directly with the company on the other hand that may be a different story.
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
merlino211 said:
It's being shipped back via the store under the 14 day buyers resource. I have had two of these so far, both have suffered from the screen oddly self-scrolling... Figure maybe a bad lot produced, as t-mobile tech support has not even heard of such a problem before. I finally settled on buying a nexus one, which arrives tomorrow. The store doesn't even check the phones out except to make sure all parts and accessories are contained in the box, there it will sit for (they said, roughly a week) before it's shipped back to T-mobile. By then, I figure liability of the phone is officially out of my hands.
Click to expand...
Click to collapse
I think you mean buyer's remorse, also I was under the impression that Limited Editions could not be 'returned' , merely exchanged or serviced.
If you don't have a contract, you could sell the phone once you put the working stock rooted rom onto it.
jesus... some of you really hurt my head over this phone.
So flashing the stock mytouch splash screen doesnt work if youre on a 1.2 or are most of you guys worrying because you have fenders?? Also can someone give me the mytouch splash screen???
You can find it here
http://theunlockr.com/2010/03/10/how-to-change-your-splash-screen/