Related
I've managed to get myself stuck up a dead end.
My device: Orange UK spv c500.
SPL: 2.00.0013
OS: None!
I upgraded to wm2005 but despite updating the reg keys posted by subliminal I couldn't install the certificate I use to ActiveSync with my Exchange Server; so I decided to downgrade.
I immediately realized my first mistake - I didn't have a backup of the old ROM on SD. Instead I downloaded one from a link in one of the forums and used psdwrite to put it on my SD card. I ran the update, but it failed and the device wouldn't start.
My next mistake was to try and re-flash the 'phone with the latest Orange UK ROM (v4.2.1.1). What I'd forgotten was that this updates the bootloader at the same time.
The flash appeared to go fine, but on restart I'm stuck in the bootloader. When I attempt to re-flash again the summary in the RUU says "Image Version:" ie no image version present.
If I was still on a v1 bootloader I'd be able to run IU_SPL+PatchedRUU again to give me an IU mode bootloader. With a v2 bootloader I can run this as many times as I want, but it won't put a lower version on.
Without an IU mode bootloader I can't "r2sd spl" to use itsme's dowload tools. Without a working OS I cant use TyphoonNBFTools to flash the SPL.
Can you think of any other solution?
If there was someway to "con" the rom update process into installing an older version of the SPL I'd be OK. Alternatively if it was possible to change the version of the SPL in SPVDEVS-SPL.nbf I could get it on.
Thanks for your help.
robhughadams said:
I've managed to get myself stuck up a dead end.
I immediately realized my first mistake - I didn't have a backup of the old ROM on SD. Instead I downloaded one from a link in one of the forums and used psdwrite to put it on my SD card. I ran the update, but it failed and the device wouldn't start.
.
Click to expand...
Click to collapse
did you tried this rom backup with your card writer i used this one with psd write and it worked download this one and try it ;-)
greets { ps let me know if this time you sucseeded ;-) }
http://rapidshare.de/files/2633600/backup.rar.rename.html
Ok, i just want to say hello to all members, and i hope you'll be abe to help me.
I have HTC Magic with these specifications:
SAPHHIRE PVT 32A SHIP S ON H
HBOOT 1 76 2009 (SAPP10000)
CPLD 12
RADIO 6 35 08 29
Dec 8 2009 17 38 48
Firmware ver 1 5
Kernel Version 2 6 27 5b476e83 htc kernel and18 2 989
Build Number 3 05 401 3 CL 98222 release keys (coulndt put dots between number again, because I'm new user)
I have downloaded and installed the HTC Sense update on this phone few months ago. (I couldn't download the Sense update from the HTC site with my phone's serial number that i entered, instead I found and downloaded the update here on the forum, that someone posted.)
Before the update, my phone SPL was 1 33 something and radio was 2 22 something if I remember correctly.
I have tried this:
How to root the HTC magic in one click guide on unlockr site (cannot provide you the link cause i'm a noob user and cand post links
I wanted to do the rooting the easy way but it was a "no go" i guess
With the FlashRec.apk application couldn't get past the "backup failed" message, because of the SPL i guess??
Then i tried this, because the first article said at the and that i need to unroot the phone with this guide "how to unroot your mytouch 3g" guide also from unlockr site.
I downloaded the sappimg NBH file from the provided link and put it in the root of the SD card, tried the fastboot (volume down + power button) but i could flash the phone, got the "wrong main version" message.
At the end of the article it says that the known issue is
"Issue: Phone says that the wrong Main Version is Older or Wrong Model ID"
and that the solution is:
"Solution: Use our Goldcard Method instead."
I am going to buy a gold card tomorrow, and i would be very thankful if you could point me into the right direction and give me some explanations and hints what should i do next, considering that i have a very "root unfriendly" versions of SPL and Radio. All help is appreciated.
You don't buy a gold card, you make one with an ordinary microsd card and some software you download. Here are instrucitons to get you started:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
And since the Wiki is down, go to this thread and follow those instructions.
Ok, guys, i made the Goldcard, according to the instructions on the unlockr site, and everything seems ok. I get the problem when i try to load SAPPIMG file from HBOOT, it picks up the sappimg file and start loading it but does not ask me to flash or anything similar, just finishes the process of checking and stays in the HBOOT screen, like nothing happened. Could this be because of a 1.76.0009 perfected SPL that my Magic has? Can my magic be even rooted?
I have done the Goldcard rooting method on the unlockr site, just for the info.
It should tell you to push "action" to continue after it checks the sappimg, with the "action" being to push the trackball.
Sent from my HTC Magic using XDA App
I've made it. It's rooted now.
Used instructions for rooting 1.76.0009, from Orange_24 (whom i thank soooo much)
I have installed Amon_RA's recovery image RA-sapphire-v1.6.2H.
I am still having problems.
I can't install [32a][3.22][6.35] CM6 - FroyoRedux Mod v1.5 (08/01/2010) Froyo Supreme ROM. I start recovery mode (home + power) button, and start Flash Zip form sdcard (i previously copied the CM6-FroyoRedux-v1.5-32a-blk.zip file to the sdcard root) and I always get the "verification failed" message" and that some file is corrupted (it's not the same file always).
My SPL and Radio now are:
SAPHHIRE PVT 32A ENG S OFF H
HBOOT 1.76.2007 (SAPP10000)
6.35.xxx
Check that the ZIP file was downloaded correctly and that your SD card isn't broken. Best way to check would be to copy a file on your card and check if it has the same MD5 sum as on the computer.
God da*n it!
Why do I have problems every step of the way!!??
I have checked the MD5 and managed to install the ROM. Now i'm stuck at the infinite boot screen. Please help, i'm really running out of patience. (I have made Nand backup and stored it on my PC if all else fails).
Don't get me wrong, but from this little experience that i have until now i got the feeling that the rooting concept is just too cumbersome and that all this problems and inconsitencies are the reason why many people never let them selves into the rooting thing. I just hope the reward will be proportional to the amount of problems that an average ROOT beginner user comes in contact for the first time.
PLEASE HELP THIS IS URGENT!!!
I might have bricked my phone. After succesfull install of CM6, my phone went to boot loop, so i tried to NAND restrore my phone. I got the error message to do the NAND restore. I got the error message, saying that to do it from the adb. I didnt know how to do it, so i tried to put some other ROM, just to get the phone working. I tried with the Amon RA's clean donut ROM. Also got the infinite boot. So i tried other recovery, the recovery-RA-sapphire-v1.7.0H, flashed it through recovery adb and got the sporadic restarts after flashing when i go into the recovery mode.
After that i flashed the recovery-RAv1.2.0H.img from fastboot because this recovery is mentioned on the unlockr site instructions on how to install custom ROM. Now i cant get into recovery mode, and cant flash none of the above mentioned recoveries from fastboot.
I really need help and information is my phone bricked. Please, i have been on my computer for the whole weekend, messing around with my android phone.
ill look into wut u can do..
Flash this recovery: http://www.theandroidkitchen.com/fi...download=recovery-RA-Magic32A-6.35-v1.6.2.img and use only ROMs made for NEW RADIO/NR/6.35. Either that, or flash the old radio/spl using eyegor's Radio Switcher (see dev thread).
^ Thank you in advance
The current state of the phone is, just to give you info:
Engineering SPL, S-OFF, HBOOT is 1.76.2007, Radio 6.35.08.29, recovery (flashed from Fast Boot) recovery-RAv1.2.0H which is stuck at boot loop, and Amon RA's clean donut ROM which is also stuck at boot loop.
I suppose the only way to fix this problem is to use adb from Fastboot USB or using gold card?
What are the symptoms of a definitively bricked phone?
keinengel said:
Flash this recovery: http://www.theandroidkitchen.com/fi...download=recovery-RA-Magic32A-6.35-v1.6.2.img and use only ROMs made for NEW RADIO/NR/6.35. Either that, or flash the old radio/spl using eyegor's Radio Switcher (see dev thread).
Click to expand...
Click to collapse
Can you give me the console command to flash it from fastboot? Is that the only way to flash recovery? I have tried flash recovery <recovery_name.ext>, but with no success, i get the :
C:\android-sdk-windows\tools>fastboot flash recovery recovery-RA-Magic32A-6.35-v1.6.2.img
error: cannot load 'recovery-RA-Magic32A-6.35-v1.6.2.img'
EDIT:
Me stupid, forgot to place the recovery in tools folder
I'll try now to load some ROM for 6.35 radio, or maybe downgrade the SPL/Radio
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
JW 301 said:
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
Click to expand...
Click to collapse
You'll need to use this guide (http://villainrom.co.uk/viewtopic.php?f=46&t=375) to make a goldcard, and downgrade using the HEROIMG.zip method (google it)
it doesn't work... I took the rom.zip, renamed it HEROIMG.zip and put it on my sdcard.
hboot finds it, loads it and then says "Main Version is older! Update Fail! Do you want to reboot device?"
what can I do now?
Have you checked to see if your goldcard has definitely worked?
it definitively is a goldcard, as I used it to install generic ROM on T-Mob device... still doesn't work now... but the problem is not that I try to install a ROM that's not meant for my device (thats what I understood goldcard does), but the problem seems to bee the bootloader-version the 2.1 RUU brought.
what can I do now?
Same thing happened t me a while back, I just re-tried every step from scratch and it worked the third time...!
what exactly did you do then? I tried so many things, at least I want to know, which steps to repeat over and over again
Just going to have a look at it for you, I am going through the processes as we speak so if I find a solution I will post back.
@JW 301 post the info in settings > About Phone
- Model number
- Firmware version
- Baseband version
- Kernel version
- Build numbr
- Software version
- Model number: HTC Hero
- Firmware version: 2.1-update1
- Baseband version 63.18.55.06PU_6.35.15.11
- Kernel version: 2.6.29-063c4d24 [email protected] #1
- Build number: 3.32.405.1 CL191507 release-keys
- Software version: 3.32.405.1
I want to get back to 2.73.111.26 (that is a T-Mobile ROM) so I can apply official T-Mobile OTA updates (by the way, I managed to get to VillainROM 12.0 yesterday, but went back. I want to use official ROMs...)
See new post here;
http://forum.xda-developers.com/showthread.php?p=7600524#post7600524
Had the same problem, I mean, EXACTLY the same.
This is what sorted it for me:
http://forum.xda-developers.com/showthread.php?t=726118
Hi
I have the following problem:
I've tested FroyoRedux Mod v1.9.5 with the requested radio and hboot. After that I've tried to install the original stock ROGERS 2.1 ROM. Now, the problems appeared. somehow I'm stack with the
1.76.0010 hboot, with security ON
Radio 3.22.20.17 (which should be 6.35.xx.xx) after flashing (don't ask why the update didn't take place because there was no error)
and the phone hangs at the ROGERS screen (just before start loading android).
I've tried reflash SAPPIMG from flashboot but it detects is already there and won't flash. I can not use fastboot from computer because security is ON, i don't have recovery installed because ROGERS rom took it away.
Any ideas on how I can fix this mess?
UPDATE: After reading tons of forum pots, seems I have found the source of the problem and seems that became a common issue: I've installed Rogers 2.1 manually over CM custom ROM with froyo (SPL 1.33.xxxx and RADIO 3.22.xx.xx) without knowing that Rogers will not update both RADIO and SPL.
Now all of us who did this need a solution. Anyone has an ideea?
Thanks
how did u install the rogers 2.1?
from the RUU?
u have a rogers magic+ phone?
blizard80 said:
how did u install the rogers 2.1?
from the RUU?
u have a rogers magic+ phone?
Click to expand...
Click to collapse
Hi, Yes, I've instaled Rogers 2.1 but not from RUU but from fastboot with SAPPIMG.zip
and u installed hboot from the ruu?
i think u must make a gold card... but wait for the experts
When I've installed the SAPPIMG using a goldcard, it automatically overwiten hboot, recovery and radio.
BTW: if I've formatted the goldcard, how can I create a new one now that i don't have a linux pc and i can only enter fastboot.
Thanks
Why did you post this in Development?
I'll move it to General... but I fail to see how this is development related.
Binary100100 said:
Why did you post this in Development?
I'll move it to General... but I fail to see how this is development related.
Click to expand...
Click to collapse
sorry, i was reading in development and post the thread here from mistake
any solution please?
Now I can access teh memoy card again. Please give me a solution using RUU. Maybe a valid RUU which works on all devices because when I've tried to flash a RUU it sais whong RUU version and I must get another one.
No one can help?
http://rapidshare.com/files/421772202/SAPPIMG.nbh
Try flashing the above.... using a goldcard and from fastboot/hboot.
Thank you for answering
I will try now
I've tried it but it say "Main Version is older". Can you tell me how can I fix that or how to make a SAPPIMG.nbh file with Rogers update or even android 2.2. Or do you have such thing?
Thanks a lot.
Anyone with a solution please !?!?
Got your PM... normally i don't respond help request over pm, but i'll make an exception.
You need to redo your goldcard... all the errors you get points to a faulty goldcard.
You can post/pm the cid nr you get from the htc device + the reverse nr. you used to make the goldcard... then i can verify that you have done it correctly.
You should have made it work with the sappimg.img i have provided earlier....
All points to a bad made goldcard!
Thanks so much for your reply.
So, Let's get started . My SD CID is
035344535530324780109ac8ee0093aa
After using http://hexrev.soaa.me/
My reversed CID is
009300eec89a10804732305553445303
(first two zeros already present)
Now, I've used this code here http://psas.revskills.de/?q=goldcard
and get the goldcard in the attachment.
Can you check please?
Thanks a lot
Well all ok from here.
The only thing left is how you made the hex-changes to the goldcard...
Which guide did you follow?
Read your pm!
i have exactely the same problem so when you get the solution can post it please !!!
Sure I will
Try this...
http://rapidshare.com/files/424005789/sappimg.zip
Put it on the goldcard and reboot by holding volume_down + power.
Then let it work...
Make sure there is nothing else on the goldcard!
Do not rename or anything.
This sappimg.zip is the new rogers 2.1 update... it should work :0)
Please report back :0)
I feel like I have looked everywhere but forgive me if I missed a thread that may answer this.
I don't know if this is a hardware or software issue.
I installed HSPL 2.08 successfully
I then installed MAGLDR 1.13 successfully
Flashed my phone with HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS successfully
Android booted fine and worked for about a day and a half. My phone froze up and had to remove battery. Now it only boots to white screen.
I have attempted to reinstalled MAGLDR without success
I have attempted to change my HSPL back to SPL to install OEM Rom without success HSPL says it was successful but bootloader screen says different.
I read in a thread that it could be a radio conflict (though I don't know why it would work for a day and then stop) but I can't install a radio ROM. I get Error 207 Image file corrupted.
I have read threads about flashing from the SD card by extracting the signed_RUU.nbh file from the stock ROM, but I have no idea how to do that. I do not have the extract option on the exe file of the stock ROM I download...and I have downloaded several versions.
Please help.
Hookwitz said:
I feel like I have looked everywhere but forgive me if I missed a thread that may answer this.
I don't know if this is a hardware or software issue.
I installed HSPL 2.08 successfully
I then installed MAGLDR 1.13 successfully
Flashed my phone with HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS successfully
Android booted fine and worked for about a day and a half. My phone froze up and had to remove battery. Now it only boots to white screen.
I have attempted to reinstalled MAGLDR without success
I have attempted to change my HSPL back to SPL to install OEM Rom without success HSPL says it was successful but bootloader screen says different.
I read in a thread that it could be a radio conflict (though I don't know why it would work for a day and then stop) but I can't install a radio ROM. I get Error 207 Image file corrupted.
I have read threads about flashing from the SD card by extracting the signed_RUU.nbh file from the stock ROM, but I have no idea how to do that. I do not have the extract option on the exe file of the stock ROM I download...and I have downloaded several versions.
Please help.
Click to expand...
Click to collapse
I have no idea what is happening with your phone and why is it happening... But I can tell yoy one thing. Whenever I had any problems when phone would not go further one step, I would do TASK29 and follow all the steps all over again. TASK29 is sth like wiping everything off your NAND. Hope it helps.
I kind of think this is a hardware issue... My boys did the same thing... Never got it back up and running.
Sent from my HTC HD2 using XDA App
what about the radio ?
do task 29 and flash radio if you haven't (ignore if you did it earlier) then install MAGLDR and flash the rom from within MAGLDR or follow whatever instructions the developer has posted in his thread.
I too have tried everything and although magldr and wm6.5 both flash from sd, still wsod. My advice is take it to tmobile, and talk them into admitting its a hardware problem ;-)
Sent from my HTC HD2 using XDA App
I forgot to mention I did try the Task29 and it too failed. So I am thinking it is a hardware issue.
UPDATE: I figured out where to find the .nbh files in my temp folder and was able to copy and paste them to the SD card. I have also gotten to the image load screen to flash the leoimg.nbh file. However all of them fail at RADIO and subsequently fail the update. I have tried new and old stock ROM and the Radio ROM by itself. I also used the Task29 nbh file and was successful in flashing that from my SD card ... but the HSPL is still there at the boot loader screen.
I can't seem to figure out what is causing the fail.
Thoughts anyone?
Sorry
HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TM OUS successfully
Did you check is this version quiet similar to your phone's hardware configuration
Ram 1024
My version is compatible. Again, it was running fine. In fact, I have a phone previous that I installed it and it worked beautifully but I dropped and shattered the screen. When I got this new one (same model) I performed the installation the exact same way. It worked a day and a half and then froze.
Based on other searches, it looks like I may have bricked my radio.
UPDATE:
I think I was able to solve this and hopefully I won't be as cryptic as someone else who had a similar problem. Don't Give Up is good advice however attempting the same time over and over is probably not the best.
This is what I did ... after banging my head at the redundancy.
I used NBHExtract from the NBHExtract forum on the Stock ROM T-Mobile_HD2_MR_Software_2.13.531.1 that I downloaded from T-Mobile. This extracted all the .nb files and thankfully they were well labeled.
I then used the NBH Creator from the NBH Creator forum (yes you will have to register to download this application.)
In the NBH Creator I used the settings provided to me in the NBHExtract window and used the SPL, Splash, and OS only ... leaving the Radio blank.
I created the leoimg.nbh file and put that on a blank 2Gig FAT32 formated SD card.
Booted the phone in Bootloader.
The update failed however it uninstalled the HSPL
From here I did a Hard Reset to clear the ROM Update failure message on the tri-color screen.
I attempted to update the ROM via USB to the 3.14 version (again downloaded from T-Mobile's site). This got to 4% and failed. I now had the warning triangle symbol on my screen indicating the Software Update failed and to try again.
I tried again however this time with the 2.13 version (the ROM I extracted at the beginning) via USB. This time is successfully installed.
This is probably not a fool-proof nor verified option, however it worked for my phone model PB8112000. It might work for you.
I am tempted to try Android again, however, I don't know if the radio issue was hardware or software.