Database Users

Recovery permission denied

Hi all,
I hope somenone can help me with the following:
My phone (as it was when it came out of the box):
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
After many months of reading about rooting etc. I took the plunge and did the following:
- installed the sdk and made sure adb was working
- fastboot recovery-RA-sapphire-v1.6.2G
- made a nandroid backup
- adb push recover to sd card
- adb shell to flash recovery permanently
- flashed Defanged base and flashed cyanogen rom
All the above worked like a dream. Tried stable rom first:
update-cm-4.2.15.1-signed and then got really exited and tried update-cm-5.0.7-DS-test5-signed. (after a wipe)
Again all this worked like a dream.
I then wanted to see how well the nandroid restore would work. So i booted into recovery and performed a wipe before the restore.
Wow this was going so well. I now had my phone back in its original state.
Clearly i was ready for more so wanted to go back to cyanogen rom.
As i booted into recovery (home button+power button) it stopped booting into recovery but instead displays a white triangle with a yellow exclamation mark and a little phone.
What have i done wrong? I can still fastboot into recovery.
I also tried reflashing the recovery but now get permission denied.
hope someone can help
Kind regards,
PS. I am now back on update-cm-5.0.7-DS-test5-signed
I used fastboot to get to recovery, wiped and reflashed. So that all works.
I just don't understand why i cant get into the recovery i flashed in the first place without using fastboot

What details say on fastboot? What SPL Radio type of phone etc . Thanks

Mod edit: not dev related, moved to general

Broken recovery image, need help fixing

Hi,
First off these forums have been a huge help since I first rooted my Magic back in August. So, a big thank you to everyone to begin with.
I tried scanning the forums to solve this new problem I'm having, but I've lost my Amon RA recovery installation and want to get some explicit help since I know if I do this wrong I'll be bricking my phone.
Here's my setup:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
May 27 2009 19:06:41
CyanogenMod 5.0.7 final
I had Amon RA installed up until today - an old version (around 1.3 I think) and since CM 5.0.8 was available via ROM Manager I thought I'd give that a try. But ROM Manager made me install Clockwork Recovery, overwriting Amon RA, and the installation of Clockwork failed or something. When I try to boot up into recovery, it just hangs at the green MyTouch screen.
I read the installation notes for Amon RA 1.7, but I could use some advice on how to do this without winding up with a brick. I can still boot into CM 5.0.7, but without a recovery image I don't think I'll ever update anything again since I can't do backups/restores.
The three installation options for Amon RA are:
- via fastboot: Can't use this, I don't think I have an engineering SPL.
- via adb: Can't use this, I can't boot into recovery at all
- via terminal: The BIG BOLD WARNING about not using this on CM 5.0.7 is pretty scary.
Can anyone help a brother out here? I'm stuck.
Thanks very much in advance for any suggestions or hints.

raybez said:
Hi,
First off these forums have been a huge help since I first rooted my Magic back in August. So, a big thank you to everyone to begin with.
I tried scanning the forums to solve this new problem I'm having, but I've lost my Amon RA recovery installation and want to get some explicit help since I know if I do this wrong I'll be bricking my phone.
Here's my setup:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
May 27 2009 19:06:41
CyanogenMod 5.0.7 final
I had Amon RA installed up until today - an old version (around 1.3 I think) and since CM 5.0.8 was available via ROM Manager I thought I'd give that a try. But ROM Manager made me install Clockwork Recovery, overwriting Amon RA, and the installation of Clockwork failed or something. When I try to boot up into recovery, it just hangs at the green MyTouch screen.
I read the installation notes for Amon RA 1.7, but I could use some advice on how to do this without winding up with a brick. I can still boot into CM 5.0.7, but without a recovery image I don't think I'll ever update anything again since I can't do backups/restores.
The three installation options for Amon RA are:
- via fastboot: Can't use this, I don't think I have an engineering SPL.
- via adb: Can't use this, I can't boot into recovery at all
- via terminal: The BIG BOLD WARNING about not using this on CM 5.0.7 is pretty scary.
Can anyone help a brother out here? I'm stuck.
Thanks very much in advance for any suggestions or hints.
Click to expand...
Click to collapse
Try holding down the menu button while booting your phone up.
Keep holding until it starts to boot or for at least 30 seconds or so.
Make sure you flash the appropriate recovery. Did you have Amon_Ra G or H version prior to clockwork?

Binary100100 said:
Try holding down the menu button while booting your phone up.
Keep holding until it starts to boot or for at least 30 seconds or so.
Make sure you flash the appropriate recovery. Did you have Amon_Ra G or H version prior to clockwork?
Click to expand...
Click to collapse
What is Menu+Power supposed to do when booting? I tried and the phone just booted up normally.
If I hold Home+Power which used to boot me into Amon RA (it was ~1.3G btw) the phone just sits at the green MyTouch bootimage screen.
Booting into fastboot via Back+Power works normally. If I had the right SPL I'd be set.
I guess the big question is, is installing Amon RA via terminal on CM5.0.7 possible yet, or are the memory problems kernel related and unavoidable without an upgrade?

raybez said:
What is Menu+Power supposed to do when booting? I tried and the phone just booted up normally.
If I hold Home+Power which used to boot me into Amon RA (it was ~1.3G btw) the phone just sits at the green MyTouch bootimage screen.
Booting into fastboot via Back+Power works normally. If I had the right SPL I'd be set.
I guess the big question is, is installing Amon RA via terminal on CM5.0.7 possible yet, or are the memory problems kernel related and unavoidable without an upgrade?
Click to expand...
Click to collapse
The problem is supposedly fixed in 5.0.8. I've personally had a couple of issues flashing the Clockwork Recovery where the recovery would seem to flash alright but it would just hang at the splash screen. I found that if you held the Menu button while pressing the power button will allow the device to boot. Afterwards, if you flash the SAME recovery a second time it will work 99% of the time.
An alternative solution would be to use the goldcard method.
Create a nandroid backup before starting
Create your goldcard (if you don't already have it from your previous rooting process)
You should now have SHIP-S OFF. This will allow you to use fastboot.
Fastboot flash the latest radio again just in case (don't want to risk bricking).
Fastboot flash your recovery (1.7.0G)
Fastboot flash your stock hboot (spl)
Reboot while holding the home button and you should be looking at your new recovery.

help

Sorry my english is very bad. I tried to root my phone image by replacing''Recovery''to step flash recovery fastboot boot.img boot.img''is the new image can not load MSDOS reported "boot.img''boot file. dc img has put in SKD / tools, and do not know the new Image download file decompression is necessary or is not simply rename a DC? I leave it renamed unsuccessfully boot.img
uphinh.vn/image/stream/143628.jpg ==> link image

I have no idea about your error, but you can't flash recovery.img unless you have an engineering SPL (which you'd have to root to acquire).
Please boot your phone holding home and vol- and post what's displayed on the screen.

SAPPHIRE PVT 32A Ship S-On H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009,21:02:32

possible solution
my phone is:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-10
RADIO-2.22.19.261
i had a similiar problem with yours. stuck in the recovery img and spl issue. my actual statu is a rooted phone with a cutom recovery img but with the original spl and radio(about to change those too).
this is how i did:
as far as i've learned, u dont need to flash your spl in order to flash your recovery.
i intalled FlashRec.apk and then installed RA recovery img from it. there a video on youtube called how to root your magic in one click. try that!
goodluck!

Looks like you have a Rogers Magic, correct?
You have S-ON (security on) so you can't flash anything useful from fastboot.
I use a 32B device, so hopefully a fellow Rogers user can help you :-/
i intalled FlashRec.apk and then installed RA recovery img from it. there a video on youtube called how to root your magic in one click. try that!
goodluck!
Click to expand...
Click to collapse
That will work on some 1.5 builds, 4zroot and universal androot are newer alternatives.

AdrianK said:
Looks like you have a Rogers Magic, correct?
You have S-ON (security on) so you can't flash anything useful from fastboot.
I use a 32B device, so hopefully a fellow Rogers user can help you :-/
That will work on some 1.5 builds, 4zroot and universal androot are newer alternatives.
Click to expand...
Click to collapse
I tried to use that way, but that backup device''error flaied image invalid"I think I deleted the original recovery of the phone and now my phone is not in recovery mode again, no way to recover it?
if you follow the way of''recovery''Amon_RA img instead only image recovery platforms, the need of the SDK is not it? I think I have not installed successfully because when you type the command ADB ADB device only shows up on MSDOS''attached''List of devices without the S / N of my phone

nhieptieuminh said:
I tried to use that way, but that backup device''error flaied image invalid"I think I deleted the original recovery of the machine and now my phone is not in recovery mode again, no way to recover it?
if you follow the way of''recovery''Amon_RA img instead only image recovery platforms, the need of the SDK is not it? I think I have not installed successfully because when you type the command ADB ADB device only shows up on MSDOS''attached''List of devices without the S / N of my phone
Click to expand...
Click to collapse
Just because the backup failed, doesn't mean your recovery is gone. Use home+power and tell us if it's still there.
"adb devices" will show the serial number of all attatched devices, you have it set up correctly. However you can not use adb or fastboot to root your device.

AdrianK said:
Just because the backup failed, doesn't mean your recovery is gone. Use home+power and tell us if it's still there.
"adb devices" will show the serial number of all attatched devices, you have it set up correctly. However you can not use adb or fastboot to root your device.
Click to expand...
Click to collapse
because I used the command "erase fastboot recovery" so I think I deleted the original recovery of the phone away and then, when I press home and power it boots up the words "HTC Magic" and stop there

nhieptieuminh said:
because I used the command "erase fastboot recovery" so I think I deleted the original recovery of the phone away and then, when I press home and power it boots up the words "HTC Magic" and stop there
Click to expand...
Click to collapse
Oh, and flashrec did that? As in, it removed recovery but couldn't flash a new one?
That's a *****, you could try another root method like universal androot to get to flash the custom recovery image.

AdrianK said:
Oh, and flashrec did that? As in, it removed recovery but couldn't flash a new one?
That's a *****, you could try another root method like universal androot to get to flash the custom recovery image.
Click to expand...
Click to collapse
can you give me the link?? thanks for helping

uphinh.vn/image/stream/143628.jp ==> please help me fix this error ? can not load new recovery.img with fastboot

[Q] Is my MT3G 3.5mm bricked?

Hello all,
I've been trying to find a solution to this problem for the last 3 days, and get nowhere. About a year ago, I rooted my Mt3g LE using the unlockr's goldcard method.
Everything worked fine until 5 days ago, when some programs stopped working. So I try to get into my recovery, and it's no longer there.
Now, I boot back into the ROM, and go to ROM manager to fix permissions. I reboot again, and try to get to my recovery. Still no, so then I got into my ROM, and clicked "Fix recovery".
Big mistake.
Now, my phone is stuck at the ROM loading splash screen. I found my goldcard, tried to flash the same SPL that it was rooted with [the top one on this page](http://forum.xda-developers.com/showthread.php?t=548218)
and it tells me "Model ID Incorrect".
Then, I tried both of the other SPL's on that page, and it tells me the same thing. I checked my goldcard on my friend's phone, and it seemed to work okay.
summary= Can't boot into ROM, can't get into recovery, can't flash SAPPIMG's.
I can get into HBOOT and FASTBOOT / FASTBOOT USB on my phone.
The lastest thing I've tried is to [unroot](http://forum.xda-developers.com/showthread.php?t=665814) but it tells me "Main Version is older! Update fail!"

Try the stock recovery (power off the phone, press and hold HOME+POWER, until you see the phone with exclamation sign, then let go and press HOME+POWER again, until you see the stock recovery, might take a few presses to get to it), with this rom "6db5d4965a64.OTA_Sapphire_TMOUS_3.56.531.1-2.10.531.4_P2_release", just do a search here. Rename the file to update.zip and put it on the root of your sd. When you're in stock recovery do a wipe and then flash the update.zip. See if that works for you.
I'm in the same situation though and nothing I've tried has worked.

I did discover that I can get into ADB when it's trying to boot.
Is there anything I can do via ADB?
I've attached a logcat for any ideas.
thanks dark0,
the screen just stays at the HTC MAGIC splash, though. I left home and power pressed for 6 minutes.

If you still have root access and your fastboot is working, try flashing the amon ra's recovery through fastboot (http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ , skip to step 4 if you've already set up the adb on your pc), and see if that works, if you still have root, you won't be getting the "not allow" message when flashing.
From there you'll be able to flash the new rom to get out of the bootloop.

Go into fastboot mode and post here ALL info.

SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27
HBOOT
then I try to run a SAPPIMG.nbh or sappimg.zip and both of them say Model ID incorrect! Update Fail!
dark0: all fastboot commands say "remote:not allow"

[Q] ADB - HBOOT or FASTBOOT (USB) / HBOOT Version .85

I know this may be hopeless, but I thought I would exhaust all efforts before accepting defeat. I have the MT4G and I have rooted it as well as S-Off. I loaded a ROM on it was working great (Beast V 4) and then it just froze while watching a movie. I had to pull the battery to get it to reboot. It rebooted to the loading screen (Animated Green Droid) and just sat there for 15 min or so. Pulled the batter and it would just stop at the MT4G splash screen. So I booted into HBoot and have:
Glacier PVT ENG S-OFF
HBOOT 0.85.2007 (PD1510000)
MI CROP-0429
RADIO-26.03.02.26_M
eMMc-boot
When loading Recovery I get:
Clockworkmod Recovery v3.0.2.4
E: Cant Mount /cache/recovery/command
E: Cant Mount /cache/recovery/log
E: Cant Open /cache/recovery/log
E: Cant Mount cache/recovery/last_log
E: Cant Open cache/recovery/last_log
I am able to:
Wipe data/factory reset
Resulting in Date wipe complete and then comes back with same errors seen above
Wipe Cache Partition
Resulting in Cache Wipe Complete and then comes back with same error.
Wipe Dalvik Cache
Resulting in nothing. and then comes back with same error
I then tried the PD15IMG.Zip on the root of the SD Card
Result:
[1] BOOTLOADER - Fail-PU
Leaving the rest blank
Update Fail!
So it seems bricked I know. I have bee reading for hours it seems and here are the questions I pose.
1. I read somewhere if the HBOOT is .86 there is nothing I can do, but it mentioned in the thread if I had .85 there was hope, but the person had .86 so the person involved was done. Plus it was different phone. I am wondering since I have .85 is there something else I can do?
2. Another thread I read the person has used ADB and -w to wipe everything off the device. However everything I can find tells me you cant use ADB in FASTBOOT or HBOOT. Is this true? Or can I? I have loaded different drivers to where device manager will see the device as ADB Device but when I run "ADB Devices" It sees nothing. Therefore cannot run -w on it. However this person somehow did then ran the PD15IMG.Zip and it fixed it. Any ideas on how this could be accomplished?
Any help would be appreciated. I am a novice at this, but I do have SDK loaded. I downloaded the HTC Drivers for the device, but it doesnt recognize my device (assuming since I cant get a full boot) and also drivers that will load the phone as an ADB device just cant see it (I know getting repetitive)
One other thing everything I have seen for screen shots is it shows the Fail-PU for each item. Mine however just stops at BOOTLOADER and then tells me update fail and to just press power to reboot.
Couple things I failed to mention
Phone is Rooted and Obviously S-Off (seen above) - Using the Visionary 11 and Gfree process (Not through SDK, but Terminal Emulator and Astro File)

1. You can try to manually flash recovery and ROM using "fastboot flash recovery recovery.img" and "fastboot flash system system.img" commands. The recovery image can be downloaded from Development forum, the stock ROM system image needs to be extracted from PD15IMG. The flash will fail, though - so don't get your hopes high.
2. You can't use ADB in bootloader, you need the phone to boot the kernel and run the ADBD (ADB daemon) to be able to access ADB.
I'm sorry to disappoint you, but Fail-PU means dead eMMC chip, and there's no way around it, no matter which bootloader you have. The only hope is when you have cache failures in recovery, but don't have Fail-PU (and in this case, engineering bootloader helps). Fail-PU is one-way ticket.