Database Users

Bricked/Blind/Barely alive magic, no recovery screen (SPL ****up) any suggestions?

Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe

*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe

Try downloading the ruu from your phone's official reseller.

T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.

Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?

Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe

Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.

For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.

abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe

Restoring to stock

I know there is all kinds of information out there on returning a phone to stock, but I cannot seem to get anything to work. I flashed my Magic with the engineering spl, set up a custom recovery image and rom, but now I need to return it back to stock to exchange it... I've tried the old rogers wiped rom, and I've tried a rooted version and a signed version... I can't seem to get anything to properly flash on to this phone now... I can flash any of the fun cool roms, but no boring old stock. The closest success I had was the signed rom installed, but hung on the rogers boot screen. the other ones all complain that they are unsigned. Any advice? I need to get this thing restored ASAP, and I would normally muck with it myself, but I don't have the time to play around anymore. I need to ship this thing back in 10 days or less now... Please?

Before you flashed anything, you should have fastboot-ed a recovery image & did a nandroid backup of your stock ROM.
Did you do it?

Before you flashed anything, you should have fastboot-ed a recovery image & did a nandroid backup of your stock ROM.
Did you do it?

Use the search button. This has been asked before. And this is not question and answer. Post in right forum.
Reported

This is not development related. Please post in the correct forum next time.

Can't Flash Fresh ROM

I have run into a strange problem. I have spent the last 2 days trying to flash the Fresh Rom back onto my phone. I had some problems while trying to do Apps to SD. Flashed back to stock, Updated and rerooted. I can restore all backups of the original sprint ROM. Every time I flash Fresh 1.0 or restore one of my nandroid backups for Fresh it will get stuck in a boot loop. I have searched everywhere and tried every possible option and can not get this Rom back on the phone. Anyone have any ideas?

first off, do you have a modded Recovery Menu? Because you need one, it is in the forums, i believe it is stickyed, but if its not search for it.
second, did you download the right ROM for YOUR phone?
Third, is the download a good download? it is possible it is corrupt.
put ALL these into consideration.

That what I was gonna ask gotta make sure you're rooted for flashing first! Good luck and let us know if you have any questions...if the directions for rooting viat the Android SDK are too confusing for you like they were for me search the forum for the "flashrec" way of rooting your phone so easy a caveman can do it!
Also be sure to get the base 1.29 RUU just to have if you need to default to stock and I found with my Sprint Hero model that recovey image 1.5.2 works best for back up and restoring 1.2.3 didn't work at all for me hence the need to run the base RUU anytime I tried to restore lol.

Yes I did all of that. I had it flashed with the fresh Rom before. Used the same files that where on my card even redownloaded. No go.

eris 2.1 to 1.5 downgrade

my girlfriend hates the OTA 2.1 cause there is so much not working now
so i was wondering if there is way/tutorial to downgrade from the crappy 2.1 OTA back to original 1.5 without rooting
if not what is there a tutorial for rooting then downgrading
Edit:
since i have a moto droid and my girlfriend didnt care much about rooting till now what type of things are diffrent when rooting the eris compared to droid (OCing, roms, themes, nandroid backups, ect.)??

Check out this link to root the eris: http://forum.xda-developers.com/showthread.php?t=647707
I'll post again once I find the 1.5 rom, although I think it may have been removed.

After searching it appears that jcase took the download down at the request of a few users.
So, what I would do is root then flash some of the new roms that have come out. Personally, I'd give either CyanogenEris or Senseless a try because they are AOSP based (like your droid is).
If you are into the Sense scene, I would check out the plethora of roms listed here: http://forum.xda-developers.com/showthread.php?t=649705

so your not able to just downgrade?? cause thats all my girlfriend really wants
and are the 2.1 roms(with sense ui cause for some reason my girlfriend likes it) based off the leaks or the official 2.1 and do they run better then the official 2.1
Edit: that tutorial is for stock 1.5 not 2.1

Downgrade instructions are here http://androidforums.com/all-things...ot-thread-apps-roms-updated-05-06-2010-a.html
Full Downgrade from 2.1root (any) to 1.5 stock - FULLY WORKING
THIS IS NOT FOR LEAK USERS SO DON'T ASK
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
http://www.multiupload.com/6UE7AUN810
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this commanhttp://www.multiupload.com/6UE7AUN810d
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Click to expand...
Click to collapse
Personally I'd stop after step 2 in case you ever want to flash a rom in the future.
Woops, I missed that she's not rooted. You could root it and go back down to 1.5.

tiggerxplur said:
so your not able to just downgrade?? cause thats all my girlfriend really wants
Click to expand...
Click to collapse
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
tiggerxplur said:
Edit: that tutorial is for stock 1.5 not 2.1
Click to expand...
Click to collapse
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.

nindoja said:
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.
Click to expand...
Click to collapse
yea she doesnt care for the advanced things i have tried to get her to use another home replacement app like helix cause i know sense ui is a resource hog but she likes it too much and doesnt wanna try and get used to something new but i will talk her into rooting and choosing a rom she might like thanks for the help
i had a rom before 2.1 for the droid that didnt block the ota and it was very annoying it varied between 2 minutes to ten minutes

is there an app like rom manager to switch between roms like the droid

I went from 2.1 OTA back down to 1.5 using the RUU MR2 on the computer. Worked like a charm!

downgrade leak 2.1 to 1.5 stock
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.

damon428 said:
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.
Click to expand...
Click to collapse
No...... x10

Please Delete. Duplicate.

If its been said once, it's been said a thousand times here,
"can I root the 2.1 LEAK?"
As always the answer is HELL NO!!!!
"can I root 2.1 OTA?"
Yes.
"can I downgrade 2.1 OTA to 1.5"
Yes.

God, I just KNEW I shouldn't have even tried to root... Please help =(

I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help

ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem? The radio update was probably included in the ROM you flashed, if you're experiencing problems, search the forum for the Radio you want and instructions on how to flash
Be careful though, you can brick your phone when flashing a radio.. so make sure you read the instructions..
Good Luck

S_Dot said:
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem?
Click to expand...
Click to collapse
2 things I am worried about:
1. Before I rooted and changed the radio, I could check for system updates and it would say I could to update to 2.2.1 ota... Now, after I unrooted and got it back to stock 2.2, I would check system updates and it no longer gave me the option to update to 2.2.1 (I had to manually do this)
This worries me since I don't want to miss out on all future ota updates if my radio has been screwed up when I flashed one earlier.
2. Radio has been slower since upgrading manually to 2.2.1 but still having the old radio in place.
Isn't the each radio optomized for the particular android build?
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?

What country is yor phone? And with what build did it came after warranty?
My guess the radio is just part of the update (if you flashed a stock rom)
I recently bought my nexus in holland it came with FRF91
And 5.08.00.04 radio so

Radio isn't per build.
There was a major change to adjust to Froyo in 4.06 radio, all the above are compatible with it, all the 4.04 and below are compatible with Eclair and not suitable for Froyo.
2.2.1 includes 5.08 anyway. Your not getting OTA doesn't have anything to do with radio.
You can flash any radio you want when you're rooted, using the guide found in Wiki.

Yeah I've benefited from newer radios. Dont sweat it your rooted, this is good.
Sent from my Nexus One using XDA App

ap3604 said:
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
Click to expand...
Click to collapse
It's the rom and recovery.
I really would not get stressed out about this. Worst case scenario is that you have to come on xda every so often and flash the update manually.

LOL, if ur on CM6 u already have 2.2.1 and worrying about future otas, root user update to latest version normally before unrooted people and u should have to problem updating, if u want to revert back to the old boring stock version just flash one of the shipping roms in bootloader by renaming them to PASSIMG.zip

ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
1) From where did you upgrade to 2.2.1?
if you upgraded from rom manager or any ROM given by developer, they remove the radio and provide it as a separate update file.
http://www.tap3w0rm.com/hosted/android/radios/nexus-1/FRF50-radio-4_06_00_12_7.zip is the update for radio you want.
2) However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
3) In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus

hmmm interesting...what makes you wanna unroot besides OTA? From what I see that's virtually no advantage to go back to stock rom
If you really want official OTAs, just make sure you check xda often when those are pushing out. There will be stock OTA updates hanging around.

Try this:
http://djmcnz.batteryboss.org/Kang-o-rama/froyo/radio/froyo-radio-update-signed.zip
Flash it from custom recovery. It will reboot, unpack the radio, reboot again in a few minutes, and you should end up back on the 4.06 radio. For what it's worth.
If you want to go back to totally stock unrooted, the most complete way to do so is using a PASSIMG file.

arkavat said:
However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
Click to expand...
Click to collapse
I installed Clockwork recovery when I first did the Cyanogen flash so how do I know if I still have it on my phone blocking OTA updates?
I had an old 2.2.1 update.zip on my SDcard from an old Nexus One that I sent in through a warranty swap.
Then I powered off and did the whole Volume Down + Power button.
I get the screen with the 3 androids on skateboards and clicked on Recovery
I press on recovery
When I see the triangle with exclamation mark I press power button + volume up and the only options I see are reboot system now, install update.zip from sd card, factory reset, wipe cache
I click on install update.zip (2.2.1) and reboot system now so the phone reboots but I still am stuck with the old radio. How do I know if I have stock recovery and will get OTA updates from now on?
arkavat said:
In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.

Can't you download a unrooted 2.2 rom from rom manager and then ota once its installed? Dont quote me though I've never actually tried to unroot
Sent from my Nexus One using XDA App

ap3604 said:
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Click to expand...
Click to collapse
On my phone this is what I get in bootloader mode...
I start up the phone holding down the trackball, and I get the Fastboot with the skateboards. The first menu option, BOOTLOADER, is highlighted. I press Power and I get to the HBOOT screen (also with skateboarding androids). I wait 5-10 seconds and it checks for a PASSIMG on SD. Since I don't have one, it finds nothing and returns me to HBOOT.
Or alternately I boot while holding volume down and I get HBOOT directly. In 5-10 seconds it checks for PASSIMG. The only time it won't do that is if my SD is not installed.
You're saying that on yours it doesn't check for PASSIMG at all?

I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan

Read the Wiki, it has specific reference to FRG83 stock ROM now, which refuses to work in PASSIMG mode.

dan1431 said:
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Click to expand...
Click to collapse
Try as update.zip through custom recovery? Then clear the custom recovery by flashing stock one...then delete superuser.apk + unroot?

liam.lah said:
It's the rom and recovery.
[snip]
Click to expand...
Click to collapse
Actually, it's just the ROM. Even if you have a custom recovery: a rooted, stock ROM will still receive OTA updates...

Yes but on quite a few custom recoveries, it will fail to install due to the signature.

Rusty! said:
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Click to expand...
Click to collapse
True. If you are using anything earlier than Amon_RA 1.8 or the latest ClockworkMod, it won't install.