Hi all,
I've been trying to install the amon RA recovery rom on mg gf's magic, but I'm stuck in a loop.
I've got a non perfect SPL loaded which boots into cupcake
Sapphire PVT 32B Ship S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-10
RADIO-3.22.20.17
However when I try to run fastboot boot recovery.img it restarts and gets stuck on the splash screen.
I've re-made the sd card to be a gold card and I've still got the issue.
I've also tried running fastboot flash recovery recovery.img
and I get Infosignature checking... FAILED )remote : signature verify fail).
Can anyone help me sort this?
Many thanks
will
You're using a non-engineering SPL, so all fastboot commands will fail. 1.33.2005 has fastboot enabled and you should be able to flash it from your currect state, however I was on .26i radio when I flashed it so I don't know for certain.
EDIT: Since you're on cupcake you should be able to use flashrec to flash the recovery image, so not engineering SPL required!
Hi Adrian,
thanks so much for replying.
In the meantime I've tried another sappimg and this has taken me to 1.33.2010 which has let me fastboot flash recovery... but when I try to boot into recovery (hold home and restart) all i get is the htc magic spash screen
The other issue is that the rom ive now got is lacking the google tools and therefore market, so i cant get flashrec
Any thoughts?
thx
No problem about missing the market, do "adb install *Drag FlashRec APK here*", that will get it installed.
How long did you hold down home+power to get to recovery? The first time I did it after loading up Amon Ra's 1.7.0 it took me holding them for around 1.5-2 minutes before it finally booted in.
Hiya,
I waited about 5 mins or so
I've now got flashrec installed... looking for what to do next?
Here. Start at step 12 assuming you've already got a recovery image.
Hmm, just tried that and it flashes in an instant (too quick tbh!), so im wondering if this is because its already got the recovery on it from when i did it via fastboot
After restarting and holding home im still getting just the splash screen
Is there a way to view what is on the /recovery/ partition, or is there a reason its not wanting to boot into it?
thx
Which recovery image are you using?
billytkid said:
Hmm, just tried that and it flashes in an instant (too quick tbh!), so im wondering if this is because its already got the recovery on it from when i did it via fastboot
After restarting and holding home im still getting just the splash screen
Is there a way to view what is on the /recovery/ partition, or is there a reason its not wanting to boot into it?
thx
Click to expand...
Click to collapse
try
fastboot erase recovery, then reflash recovery
AdrianK said:
try
fastboot erase recovery, then reflash recovery
Click to expand...
Click to collapse
He can't complete any fastboot commands since he doesn't have an engineering SPL.
DonJuan692006 said:
He can't complete any fastboot commands since he doesn't have an engineering SPL.
Click to expand...
Click to collapse
I did tell him how to get one ;-P
Hopefully it won't come to that. I think he's loading the wrong recovery image.
recovery-RA-sapphire-v1.7.0G.img
Try re-downloading the recovery image from here and try flashing again. If it doesn't work I think your going to have to try going Adrian's route.
Better yet, you can get it from step 5 here for a quicker download.
Also, when you were in FlashRec running the "/sdcard/recovery-RA-dream-v1.2.3.img" command did you change recovery-RA-dream-v1.2.3.img to match the filename of your recovery image?
I've just managed to update the recovery, but strangely this is using the 32A recovery.. and not 32B.. but I've got a vodafone Magic
So I can now get into recovery and have followed the steps or dangerSPL, followed by cyanogen mod + gapps, but not i cant get it to fully start up and im stuck on splash screen
V confused now.. just checked in hboot and its still showing sapphire pvt 32b eng s-off H
Hboot 1.76.2007
radio 3.22.20.17
looks like the gf's not having a mobile tomorow.. oh dear im in trouble!
any ideas again much appreciated!
thx
Can you run any fastboot commands?
Yes I can now run fastboot commands and use the recovery tool
thx
Hi all,
hope to get some more help, sorry!!
After looking more into this it seems that one of the previous images i put on the 32b phone was a 32a radio... hence the issue with putting on the recovery image for the 32b not working.
So... i downloaded myTouch-radio-2_22_23_02.zip and using the recovery did an update from zip.. now however the phone boots and all i get is a picture of a box with an arrow pointing to an android robot (see attached!)
At this rate its looking like i need to buy a new phone!
cheers all
Hi.
i need some advice to see what can i do to get the phone working again.
case:
htc magic 32A.
ENG S-OFF H.
hboot-1.33.2005
radio.3.22.20.17.
i had cyangoenmod 6. working just fine! for several months. a couple a days ago (without installing anything new) it crashed, and now it gets stuck in the splash screen.
symptoms:
i can enter fastboot. fastboot devices lists the phone.
i can't enter recovery. fastboot boot recovery.img doesnt work, still stuck in splash screen. fastboot flash recovery.img doesnt work either.
i thought the next step would be a factory reset so i got a friend to copy the sappimg.zip on my sdcard and tried to run hboot mode, but it says NO IMAGE! when checking SAPPIMG.zip
should i use RUU? whats the procedure there?. from where i run it?. also i don't know whats the right one for my phone. i see this list: http://forum.xda-developers.com/showthread.php?t=659403.
and fastboot getvar version-main gives me: 3.05.529.9. while CID gives BSTAR301
i dont see that exact version in the list, and the only one with that cid is 2.20.515.5 HTC Chile BrightStar/Entel. im a little confused here...
thanks for any help!.
the problem seems to be bigger. I decided to go with the RUU directly from Htc site. For my device, i gave my serial no. and downloaded the .exe for magic_brightstar. It did successfully updated everything (?), radio, hboot, recovery, system, splash....
But i start the phone and it is still stuck in the freaking init screen.
I don't understand, what else can i do?.
Can you enter the recovery now?
No. the recovery doesn't enter. still frozen.
I'm trying to have a working goldcard, but it has been a little tricky without another phone to convert the sd. I'm following what amon_ra suggested here http://forum.xda-developers.com/showthread.php?t=548218. Because right now my hboot is locked (after running the factory RUU) and i can't run any of the flashing fastboot commands.
will post what happens...
ok the goldcard did its job, i have again eng spl with all fastboot flashing enabled. but i cant get into recovery yet, no matter what.
at this point i'm thinking on flashing the original hboot, radio and go claim the guaranty...
Any ideas before throwing the towel???
i was thinking that if it is a hardware/firmware problem, it should be possible to test via fastboot oem commands, isn't?
Download my fastboot commander from my signature (the magic version).
It has a special 32A tab.
Using the tool, flash the old combo and see if you can enter recovery afterwards.
You can also flash the new combo and give it try...
Tried to install a new radio so I could get radio 2.2 instead of 3.2 rogers htc dream..
Just stuck at boot screen won't load os, fastboot or recovery should I try install adb and doing some commands there or should I just said it is bricked and dead ?
Thanks for answers, Also if you know it is bricked recommend a new phone please
I take it you ignored the advise to flash radios via fastboot rather than recovery.
If you had a 3.22.* radio and flashed a 2.22.* radio from recovery you are likely bricked (as this is one of the two easiest actions you can take to brick your phone).. Jtag can fix this.. but the jtag operation is worth more than the phone at this point)
Regardless: see if you can get into fastboot [power on holding camera] if you can get the fastboot info so we can help (if its 1.33.2005 just follow fastboot instructions to install 2.22.28.25 and 1.33.0013d including flashing recovery)
Cannot get into fastboot, I had danger sql on it also I did flash it via recovery
thanks for post please post back.
Dear all,
My magic've used
Hboot 1.33.2010
Radio 3.22.2017
Rom cook 2.2
But on bad day, i try to use official by install RUU ROM Roger 2.1 on my Magic. Now it stop at hboot screen.
I install RUU roger 2.1 on Old radio but not success. the process stop at 45%. then i reboot the phone and it donot work
Then screen show
Hboot 1.76.2010
Radio 3.22.2017
I try to reinstall the RUU "Roger.exe" but not success
fastboot flash zip rom.zip but not success
fastboot flash recovery recovery.img but not success
fastboot flash radio radio.img but not success
fastboot oem boot. The phone boot but stop and loop at the "Change Language" screen.
I try to use Adb but not success.
Please help me unbrick my Magic 32A
Thanks in advanced
Phuong
Havent played with my rogers g1 much yet (havent even got a chance to root it) but im pretty sure you can just download the orange.nbh and all is well. You may have to reroot and flash some new roms but i think you are fine if you still have hboot
Sent from my NXM726HN using XDA App
Hi I was on viper rom I relocked my bootloader and went s-on. So now my phone won't let me boot because the software has been tampered and all my efforts to flash a new ruu has failed.
I'm trying to follow method 3 from here
https://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
If i use htc_fastboot command it is not recognized, so i remove HTC_ and just use fastboot and it'll boot to ruu mode but when I use "fastboot flash zip" it tries to flash and fails I've tried the newest ruu I've tried
2.41.605.20 Full Stock Firmware with stock boot.img and stock recovery included(will replace/remove Twrp/will wipe/encrypt)
from
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
as well as (2.41.605.20_FULL_Stock_firmware.zip) and the hboot for 1.65.605.8
I'm currently downloading the ruu exe for 1.82.605.6 since that is the version I am on, hoping that works does anyone have any good news for me?