Have been trying my best to figure this out, but so many steps. Lame I know but...
I've got a Rogers 32A SPL 1.33.0010 SAPP50000 3.22.20.17. After buying it used with a Hero ROM almost a year ago, I managed to flash CM6-FroyoRedux-1.6-32a which worked (great!) for almost a year. Lately it has been getting really flakey with lots of FC and problems connecting to wifi.
So I thought a re-flash of ROM should fix things up. No luck, same problems. Super flakey, lots of FC (even with base install). Does that mean I have a hw problem?
So thought I would try another more up to date ROM. Tried CyanogenCARZ-7.1.0... and Ginger Yosi 1.2.1 and a few other but none would flash properly (Recovery on the phone is ClockworkMod Recovery v2.5.0.1 - is that the problem? If so can anyone direct me to easy steps to change this? Found some others but me to dumb, or they to hard to follow b/c no luck. I have done ROM messing about for years, more recently with Dell Streak, but it seemed to be much easier.)
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Where should I go from here?
Thanks for your help, and sorry for being so dumb.
Don't worry, it's natural to have questions whwn confronted with such a confusing phone. I would recommend going to the RUU sticky in the development section, and flashing back to stock. If you still gets fcs and the like on stock, it is likely a hardware issue. Otherwise, we can just reroot and flash another custom rom. Let me know how it goes!
Sent from my Sapphire/dream using XDA App
What you need is a simple (full)wipe.
The problem when applying new roms or re-flashing the same rom is that the userdata and cache partitions are not cleaned.
Userdata = all the app and settings you have accumulated through the years.
Cache = as the name says.
When the partitions are not wiped, then complication can and most likely will occur when (re)flashing roms.
So, inside the recovery, chose to wipe all the partition you can find. Then you flash the rom you want. Wait 5-15 min for it to load and you should be good to go.
paulheth said:
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Click to expand...
Click to collapse
Rooted = have SU binaries... my guess = YES you are rooted.
Perfect SPL does not influence rom flashing since you are working from recovery.
If you are flashing from fastboot, then SPL will have a dominant position.
Looking more like hardware.
Seems it may be a hardware issue? Even with the stock RUU rom from HTC there are still sim recognition and wifi flakiness issues.
Any chance a radio re-flash/update would help?
Related
Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer
Hi,
Already posted part of the situation in Amon_RA's recovery thread but neither of the answers there seem to solve my problems. Decided to post it here since the problem seems to involve aspects other than the recovery itself.
Here's the complete situation:
Had problems with RA recovery freezes since the start and with different versions. I could (and can) enter recovery mode (v1.6.2), scroll down the options but after 15 seconds the recovery just freezes and reboots every single time. Checked the version (H) and the MD5, they where all correct. Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Tried booting the latest RA recovery trough fast-boot and it worked fine the first two times I did it (scrolled down the options for like 10 minutes and it didn't freeze). After that it did not work and got the freezes+rebooting problem back again. Tried ADB, Flash-rec and flashed the recovery but got the freeze+reboot problem once again. Re-checked the version and MD5 and they where all correct.
Why does this happen? Any clues?
Thanks for your help!
I'm kind of lost here...Could it be a radio or SPL problem? Should I re-flash/update it? I never had problems with the stock ROM so this situation is really odd...
Can anyone help?
Thanks in advance!
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
But anyways, I'm a bit confused. What rom are u using?
noroses said:
Hi,
Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Click to expand...
Click to collapse
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
I have no idea dude but what I would do if I was in your situation:
1) Flash ENG SPL, something like 1.33.0010 (double check everything, i dont like advising people to play with their spl/radio so dont just take my word)
2) load up recovery and give it a try! if all that fails...
3) I'd backup your phone via nandroid in recovery (i pray that it doesn't freeze lol)
4) Wipe wipe wipe
5) Go into fastboot, fastboot erase system -w and then try another rom! And if the rom is good, then go back to your old one. Try to find out what the prob is.
It appears that you're able to flash roms still even with your recovery freezing (so weird) so I dunno. Just give it a try I guess lol
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Hi,
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
Click to expand...
Click to collapse
Will try this. Can I flash the SPL trough the recovery?
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
Click to expand...
Click to collapse
Will have to check and recheck this complex process.
But anyways, I'm a bit confused. What rom are u using?
Click to expand...
Click to collapse
Now I'm using stock 1.5. I tried cyanogen, superD and other 1.6 Roms and they all freezed at the android setup process. Used myhero for a week with no problems whatsoever. Since I have a nandroid backup done with CM's recovery I restore everything back as it was.
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
Click to expand...
Click to collapse
The Amon_Ra recovery freezes every time. It doesn't give me enough time to do anything...Now I'm using CM's recovery and I have no freezing problems while in recovery mode. The problem is after I flash a Rom and reboot. The ROM experiences freezing problems (just like the Amon_Ra's recovery).
Thank you for your answer and suggestions!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi,
Thanks for your answer.
I have never tried with the phone plugged into a socket but did it with the phone running on battery and connected via usb to the computer. Should it make a difference?
Could it be a hardware problem? I never had problems with the stock ROM or with the myhero ROM...
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
digitaljeff said:
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
Click to expand...
Click to collapse
Checked that guide but I'm unsure about this part:
If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
Click to expand...
Click to collapse
This part I can do within the recovery to enable flashing via fast-boot right?
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
digitaljeff said:
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
Click to expand...
Click to collapse
Will try that tomorrow.
Thanks for your help!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi again,
Still didn't mess with SPL and Radio. I'm still afraid I'll brick the phone..However yesterday tried a few simple things like using another sd card or entering recovery while plugged in. These two things seem to influence the behavior of the latest Amon_RA recovery but don't solve my problem completely. Example: When I enter recovery using the original SD card (2gb) the recovery would freeze within 20 secs max. Using another SD card (128mb) most of the times it would take longer to freeze (4 or 5 minutes). Sometimes it would not freeze at all. Although this seemed to influence what happened it wasn't constant and could not find a pattern. The same with the phone plugged into computer. Sometimes it helped. One thing is certain: with the original SD card and unplugged from the computer the recovery freezes within 20 secs every single time.
With the CM 1.4 recovery never had any freeze problems. It seems to work great while in recovery mode. The problem is after a flash a ROM I have freeze problems with the ROM itself (tried different ROM's, CM, SuperD, etc and got the same freeze problem). The only Rom that worked fine was myhero 2.0.5.
This is a very strange situation and I'm starting to think that this could be hardware..
Would that be a SD card problem?
try using another SD card and see if the problem still occurs
I am having exactly the same problem, did you ever find a solution?
Went from a fully updated magic 32A (1.76.0009H) now i'm at 1.76.0008
UPDATE: I just found that the hero recovery works (I would post link but xda doesn't allow new users to do that) however it may still be necessary to downgrade radio and spl
I had also same problem. My device is Magic 32A radio 6.35. Solution was to reflash recovery-RA-hero-v1.6.2.img.
Hello all,
Here's what happened - I DL'd the app 'ROM Manager' from the Android Market, installed and allowed this app to be the recovery for my MT3g (non-Fender and non-headphone jack version).
Suffice it to say that the ROM Manager app jacked up my phone... none of their items worked for me. I uninstalled the ROM Manager and now when I tried to go to recovery mode (power + Home) I get nothing but stuck on the MT splash screen
My phone is rooted, originally ran the recovery-RA-dream-v1.6.2 recovery and am currently running a 2.1 ROM.
I have tried to redo the flashrec-1.1.3x and this does not work.
Where do I go from here? I'd like to be able to partition my new 8GB SD card and I can't even do that...
Thanks in advance.
If your phone is rooted, can't you just flash the previous working recovery via fastboot again?
-------------------------------------
Sent via the XDA Tapatalk App
You should be able to put the recovery image on your sd card and use the flash_image command from the terminal right? thats what i did
Mod. edit: not dev related, moved to general
twigster said:
If your phone is rooted, can't you just flash the previous working recovery via fastboot again?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Just to let you know, it is possible to root a mytouch without ever having installed an SPL that allows flashing though fastboot. I know from personal experience that the one-click flashrec method does this
adavis159 said:
Just to let you know, it is possible to root a mytouch without ever having installed an SPL that allows flashing though fastboot. I know from personal experience that the one-click flashrec method does this
Click to expand...
Click to collapse
I know, thats what I did as well.
But since then, till the date I changed to an engineering SPL, im pretty sure I have always done the subsequent changes to my recovery and spl using fastboot, even after starting with the 0010 SPL (which was at the time a problem SPL) and using flashrec to change the recovery before installing my first non stock rom, being cyanogen 4.x.x, still with the 0010 SPL.
I do know that it only became necessary for me to change my SPL when I wanted to try new radio ROMs (subsequently moved back, and took the chance to move to the 2010 engineering SPL) Before that I was actually too scared to change the SPL because of the brick threats.
I used the cursorsense rom thread instructions on how to change the radio and spl, and it worked great.
Maybe, so far, I have been lucky not to brick my phone. But I have always followed well documented threads on the dev section and so far so good, not excluding one or two times when I thought I had made a nice brick, but just persevered.
Fastboot is your friend, and so is XDA if you are nice to it and the good people who frequent it.
If you look through the threads, and in the development section, there are alot of areas where they give the commands necessary for a variety of actions, and peoples responses on whether it works.
I don't yet believe in the programs created to do everything for you, nothing against the devs, who are all great, just not quite happy enough with comments posted to try them out yet.
(I think my response was little longer than needed) ;-)
Thanks for the info guys...
Problem was I could not boot into fast boot - the recovery was not there.
What I ended up doing was unrooting then rerooting my phone, reloaded my ROM and went on from there...
That might have been the long way of doing things but it all worked out well.
Hi all, thanks in advance for any help and my apologies if this exact problem has already been resolved. I searched through this forum and found issues *similar* to my problem but nothing exact enough for me to find a solution.
My experience with Android is limited but have quite a bit of terminal UNIX experience...so I'm not a total noob and I can follow directions pretty well.
I purchased a MT3G from someone and everything seemed to be in order when I checked it out (and the price was good, so I figured I didn't have much to lose). He was running Cyanogen Mod on there but of course I wanted to restore to factory settings and build it up from scratch on my own. Thinking that I knew what I was doing, I booted into Recovery (Home/End key simultaneously) with no issues and ran the factory reset utility, thinking that this would just drop the phone back to factory settings and I could re-root it from there. When I turn the phone back on, it just hangs at the "splash" screen and runs the animation over and over again.
I can still boot into Recovery and I can get into Fast Boot so I hope I am not bricked.
Here is the output I get from Fast Boot (attached file).
I tried to restore with a SAPPIMG.zip that I found but it said wrong device...
Any help would be GREATLY appreciated. Thanks!
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
If you get an error, you need to download an engineering spl, and then try. (Engineering 2010 SPL)
The link and instructions are around somewhere on XDA.
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Vontropnats said:
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Click to expand...
Click to collapse
Yes sir, that is the easy way!
there are plenty of 1.6, and 2.2 roms out there.
Just download to sdcard, boot into recovery, wipe and flash
Don't flash any SPLs. Your fine as long as you've got a custom recovery. Just flash another ROM from there and make sure you wipe data, dalvik-cache, and cache before flashing. I've been running CyanogenMod 5.0.8 since the summer (CM6 ran like crap) and I've been happy with it so far.
Sent from my HTC Magic using Tapatalk
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Vontropnats said:
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Click to expand...
Click to collapse
Not true you can root using the this app then use rom manager to install clockwork mod recovery. This is how I helped my friend root his device.
attached is the app
Goodmorning,
I did a good few searches and could not find an answer to my delima. I am pretty informed about rooting and flashing ROMs. What happened was I already had a phone rooted and mikroms 4.61 but needed to exchange it due to a bad camera. I recieved my new evo 4g (hardware v4...hboot 2.10) and rooted it with unrevoked. Everything went will and was rooted within minutes. I then went to downgrade the hboot (this is where the problem began). I followed the same instructions I did with my previous evo (I believe it was hardware v3) and did the update, did not reboot, installed the .zip file. I then went and wiped everything (Full Wipe). Dalvik and Cahche as well. I then went to install mikfroyo and everything seemed ok. I them went and rebooted and now I am stuck on the bootloader. The hboot is still 2.10 but it has s-off. I tried a RUU, the RUU finds the evo and reboots the phone. Then the RUU cannot get to the bootloader. It stays waiting for a good minute but can't seem to find the bootloader even though the phone is on the bootloader. All drivers are installed properly as I checked the Device Manager and no question marks come up. Any ideas would be fully appreciated. Thank you.
By the way...I cannot get into Recovery either. When I choose that option it just heads right back to the Bootloader screen.
Why would you downgrade the hboot?
I know people have dome this to try and solve issues with their phone not booting at all, but to just do it?? Why?
HipKat said:
Why would you downgrade the hboot?
I know people have dome this to try and solve issues with their phone not booting at all, but to just do it?? Why?
Click to expand...
Click to collapse
For some reason I thought the evo would just function better with the previous hboot, doing nandroids and flashing ROMs. If I didn't need to do it I would not have even looked that way. Guess I am not as experienced as I thought. I just did that because it worked well with my previous evo. I hope I don't have to go to sprint and replace it again for my ignorance. There's other phones that have true issues that deserve to be exchanged next to mine.
Your phone is bricked. Try fastboot devices, if you get 123456789012....your screwed. You now have bad blocks and partition info is mixed up. Sorry.
Your new phone has newer block sizes
snandlal said:
Your phone is bricked. Try fastboot devices, if you get 123456789012....your screwed. You now have bad blocks and partition info is mixed up. Sorry.
Your new phone has newer block sizes
Click to expand...
Click to collapse
That stinks. Well, I will go in ahead and have it sent in through Best Buy. Thanks a bunch, friend. Godbless