Develop Bugs

[Q]4 Day Search,Need ENG SPL for fresh rom

I have searched for about 4 days just for instructions on this eng-spl,and im probably going to get told to read more for posting this question.Basically when i try to install a splash screen i get this error.
sending 'splash1' (750 KB)... OKAY [ 0.355s]
writing 'splash1'... FAILED (remote: not allowed)
finished. total time: 0.356s
And when i did some research it seems you have to have a ENG-SPL or something to have advanced fastboot access.
I followed the tut guide on how to root 2.2
and afterwards i flashed the latest fresh rom.i didnt follow any other instructions because my second evo came with 2.2
i just need to know how to install this ENG spl on the fresh rom , or if some one can tell me how i can change the splash image from the rom so i can just re flash the rom when i want a new splash screen,or if i can sign a splash screen so i can flash it thanks.Thanks alot.

You need to flash the negineering bootloader, this thread is the one you need.

Ok so do i have to flash another rom before i do that update,right now i have the latest fresh rom....do i have to download that pc36img and flash from recovery or flash on hboot,i read that link and tried those steps before and i semi bricked my phone,i would just like to know if i flash that pc36img what do i do next? thanks.

[Q] I'm stuck with Clockworkmod 2.5.0.7 recovery !!

I cannot upgrade to a newer version of Clockworkmod recovery !
I have tried everything, fastboot flash returns failed signature verification, rom manger also cannot update to a newer version.
Also tried Unrevoked but it fails.
the phone is rooted and I have flashed several ROMs in the past without any problem.
Any idea?

Fastboot flash doesn't return verification failed error.
You need to be s-off to change recover using fastboot. Before you do anything, read some tutorials, you need to differentiate among most basic terms.
Sent from my HTC Desire using Tapatalk

erklat said:
Fastboot flash doesn't return verification failed error.
Click to expand...
Click to collapse
It can do if you try to fastboot flash connected in hboot or are s-on

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

I get this error from fastboot
< waiting for device >
sending 'recovery' (3256 KB)... OKAY [ 0.468s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.952s
I have tried to flash clockworkmod 5 and also tried the touch version, but with no luck.
Maybe the S-OFF is messed up, but only if rom manager did something wrong, because last time when I have upgraded the recovery it was from ROM Manager.

Fail on my part...
That seems like there is no device tho. My money is on broken drivers. There is a guide how to do in development so search for it as it works 100%.

unrevoked connects to phone, sends the file to phone then at the end it fails.
I have tried revolutionary for S-OFF the program connects to phone then displays the phone serial number, asks for the key then after I enter the key, the connection is lost.
So I really don't know what to do anymore, and I need a newer recovery since the one which I have does not have options to partition the SD Card and ICS is eating a lot of memory without SDExt.
The phone is ok, it's not broken, I flash every 2-3 days a newer ICS ROM and it works.

why dont you try a different recovery.i have been using ext4 recovery for a while and imo it is way better than cwm....

I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7

evolution_x said:
I use clockworkmod because I have purchased the ROM manager tool and it works with their recovery.
I finally managed to flash a newer clockworkmod recovery and very strange after reboot it has reverted back to the old 2.5.0.7 version !!! At least I was able to partition my sd-ext...
I have tried the boot CD with alpha-rev it freezes in the final stage, but after that I was able to flash the new recovery using the recovery itself, but as I said after reboot the new recovery has gone !
Now I have tried to flash again a newer recovery from ROM manager it says it finished successful, but the recovery still remains 2.5.0.7
Click to expand...
Click to collapse
Because all you are doing is a fake flash. You need to flash it from fastboot in order to stick.
Ditch the Rom manager. That pos app is guilty of more usb bricks than most of us can count.

And how can I flash it from HBOOT ?

evolution_x said:
And how can I flash it from HBOOT ?
Click to expand...
Click to collapse
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.

erklat said:
You need to read ADB for dummies guide to gain knowledge how to set ADB up.
Then you go into hboot by pressing vol- and power button.
Select fastboot.
Download your recovery.img and place it in the same folder your fastboot.exe is, then type in cmd:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache.
Return to hboot and boot in the recovery.
Click to expand...
Click to collapse
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?

KitkatKlub said:
Erklat, thanks for this - I have the same problem.
i have finally got round to get adb, etc, working..and it kinda works, except that when flash a newer version of CWM (v5.0.2) on fastboot it still doesn't work. I tried using the Rom manager, which failed straight away, and I followed your steps above. But still didn't work.
So my story's background:
I rooted my Desire with Unrevoked so I could install ICS (sandvold) - and it has been working beautifully. But now I want to create an ext3 partition and the GParted method is far too complex for me to follow through.
CWM i have installed doens't partition, and so I though I'd update the recovery tool so I could use it to partition.
Any suggestions on what I could do?
Click to expand...
Click to collapse
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.

stankyou said:
Do you get an error when you flash a new recovery via fastboot or does it say it successfully flashed the recovery.img file? If you didn't get an error, do you always go to Rom Manager to access recovery? If yes, I say ditch rom manager. Try vol down + power like on erklat's instruction, this time select Recovery. See if the recovery you flashed is booted.
If you are s-off it's better you flash 4ext recovery. It's by far the best recovery you can use for Desire.
Click to expand...
Click to collapse
Hey thanks sthankyou.
This is what i get on fastboot:
sending recovery...
OKAY
writing recovery
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.054s
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
I have also tried this flashing using the terminal, Which I found in the Q&A's but i get several error messages, and then finally:
"error writing recovery: No space left on device"
So I uninstalled a couple of apps (freeing some 10mb+) but still the same issue.

As you are not s-off you can't flash recovery, get s-off and flash any you like
Sent from my HTC Sensation XE with Beats Audio using XDA Premium App

KitkatKlub said:
I also tried flashing RA, just to see if it would work (and also heard its better). But nothing. It's quite bizarre.
Click to expand...
Click to collapse
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
KitkatKlub said:
My phone is not S-OFF - I used the HTC official software and I dont' think it does it - I have no problems in doing it if it will resolve this problem.
Click to expand...
Click to collapse
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk

erklat said:
RA has not been maintained for quite some time. 4EXT is probably the best and it's developer is very devoted to his project.
You made your life a whole lot complicated by using that official tool.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!

KitkatKlub said:
Ah that really sucks. Will I be able to gain S-Off by using AlphaRev? Revolution doesn't work because my HBoot is 1.0.3... and thus not supported.
Once I get it to be S-Off I'll switch to 4EXT.
Thanks, for the help so far!
Click to expand...
Click to collapse
theresa way to downgrade. check resources on my guide.

i had the same problem. s-off solved everything.
i had problems with s-off. i had ISC 4.0.3. and i couldn't get it to s-off and i installed some stable rom. cant remember which one, but i'm sure it was on of stable ones. and then tried to s-off again and it was over in few minutes.
and then i flashed recovery with adb

iconia tab a101 : recovery verified failed

Hi guys,
I got an issue since I tried to downgrade from leak ICS for A101 (the russian) to HC.
Since that day, each time I try to use recovery with a stock rom, I always got the same message while booting recovery kernel image : Recovery verified failed.
I downgraded because ICS had a very annoying draining battery issue but even after downgraded, it seemed something went wrong as I cant use any stock recovery rom at all.
Would you any idea so that I could go back to an official A101 stock rom o that I could get OTA future upgrades ?
I searched all over the forum and googled as well billions of pages with no success.
Thanks for your help. :good:

Infomediasvc said:
Hi guys,
I got an issue since I tried to downgrade from leak ICS for A101 (the russian) to HC.
Since that day, each time I try to use recovery with a stock rom, I always got the same message while booting recovery kernel image : Recovery verified failed.
I downgraded because ICS had a very annoying draining battery issue but even after downgraded, it seemed something went wrong as I cant use any stock recovery rom at all.
Would you any idea so that I could go back to an official A101 stock rom o that I could get OTA future upgrades ?
I searched all over the forum and googled as well billions of pages with no success.
Thanks for your help. :good:
Click to expand...
Click to collapse
That means your recovery isn't stock with a stock boot loader. Does android boot at all?
Sent from my Nexus 7 using Tapatalk 2

It does but I'm stuck in 3.2.1 now !
Baseband : Cust R3C01 Config : R4B01 Protocol : R3B01 App : R3C01
Core version : 2.6.36.3+
Build : Acer_A101-2_005.01_COM_GEN1
pio_masaki said:
That means your recovery isn't stock with a stock boot loader. Does android boot at all?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse

Take a look here
http://forum.xda-developers.com/showthread.php?p=33574648
You can use this to update to ICS for a100 but instead of the 101, you'll lose 3g. If you can find the 101 ICS update then use that instead.
You may end up needing to go to stock ICS then root to get recovery back as the honeycomb boot loader won't do fast boot.
In the end you'll need to replace recovery to do anything else, have you hard reset with the volume key + lock switch toggle?
Sent from my Galaxy Nexus using Tapatalk 2

What procedures did you use to go to ICS and then back to HC? What boot loader is displayed when booting?
My guess is that somehow you are on the ICS recovery while on HC. Causing the recovery fail, or the recovery is not there. I would flash the Honeycomb recovery, then reboot a few times, and then boot to the recovery to confirm it is working. Then you should be good to go to flash an official HC or ICS a101 ROM. http://vache-android.com/?dir=Tablets. Has most of the ROMs. Some a101 ROMs are located in the a100 folder. Look for the prefix of 'a101' in the ROM name. You will have to do your own research on the ROM versions, as I'm not versed in a101 ROMs.
I have attached a copy of the HC recovery.

Romman0 said:
What procedures did you use to go to ICS and then back to HC? What boot loader is displayed when booting?
My guess is that somehow you are on the ICS recovery while on HC.
I think the same'as my boot loader is 3.0.1 from what Acer recovey tells me.
The procedure is the normal one for the custom leak version of ics (four files renamed one after the other as update zip flashed through recovery (power + rock volume buton at the Left).
However when I tried to recover Hc stock rom things went wrong. I haven t been able to boot back until I flash another time one of the hc stock rom.
From this day, I have been able to boot ans use hc but for each update or each time I tried to flash a custom or stoc rom I alway got tis eror message.
Regards
Click to expand...
Click to collapse

Infomediasvc said:
Romman0 said:
What procedures did you use to go to ICS and then back to HC? What boot loader is displayed when booting?
My guess is that somehow you are on the ICS recovery while on HC.
I think the same'as my boot loader is 3.0.1 from what Acer recovey tells me.
The procedure is the normal one for the custom leak version of ics (four files renamed one after the other as update zip flashed through recovery (power + rock volume buton at the Left).
However when I tried to recover Hc stock rom things went wrong. I haven t been able to boot back until I flash another time one of the hc stock rom.
From this day, I have been able to boot ans use hc but for each update or each time I tried to flash a custom or stoc rom I alway got tis eror message.
Regards
Click to expand...
Click to collapse
You can't run a custom ROM on the honeycomb bootloader. You must be on ICS then root then unlocked then custom recovery THEN you can use custom ROMs.
The last sentence I take to mean you can't run a custom ROM, in which case update to ICS again then follow the directions.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse

I cant't anything at all in fact !! That's the point... Whatever is the file I try to flash, I got the same message from scratch : "recovery verified failed". I doesn't even boot on the file itself.
How can I do to repair the recovery process ? Do I have to rename HC-Recovery.IMG or do I have to flash it from the pc itself within the Terminal ?

I have moved a little forward :
I used adb reboot-bootloader to use fastboot from the pc and tried to erase or reflash and I got this : Bootloader v0.03.14-ICS Satrting Fastboot Usb download protocol
Fast Boot: Not suported the command in Lock mode
Failed to process command erase recovery or download 0034c100 error (0x2)
That confirms the fact that I'm on a ICS bootloader with HC !!
I tried to unlock the bootloader :
it seemed to work :
O:\ACER A101\ICS UPDATES\ICS_rooting>fastboot oem unlock
...
OKAY [ 0.093s]
finished. total time: 0.093s
BUT I got the same result:
erasing 'recovery'...
FAILED (remote: (00000002))
finished. total time: 0.101s
and
sending 'recovery' (3376 KB)...
FAILED (remote: (00000002))
finished. total time: 0.117s

Infomediasvc said:
I have moved a little forward :
I used adb reboot-bootloader to use fastboot from the pc and tried to erase or reflash and I got this : Bootloader v0.03.14-ICS Satrting Fastboot Usb download protocol
Fast Boot: Not suported the command in Lock mode
Failed to process command erase recovery or download 0034c100 error (0x2)
That confirms the fact that I'm on a ICS bootloader with HC !!
I tried to unlock the bootloader :
it seemed to work :
O:\ACER A101\ICS UPDATES\ICS_rooting>fastboot oem unlock
...
OKAY [ 0.093s]
finished. total time: 0.093s
BUT I got the same result:
erasing 'recovery'...
FAILED (remote: (00000002))
finished. total time: 0.101s
and
sending 'recovery' (3376 KB)...
FAILED (remote: (00000002))
finished. total time: 0.117s
Click to expand...
Click to collapse
Unlock doesn't work on the a100 bootloader, only the a200 ics boot loader, have you done a hard reset? You have to or the hc boot loader won't fire up.
Power off the tab, hold the volume furthest from the lock switch, press and hold power, once the screen comes on let go of power and flip the lock switch a couple times while still holding the volume key.
Sent from my Nexus 7 using Tapatalk 2

I did and it's exactly the same messages...

You can push a new recovery img to the recovery partition with terminal or adb.

Fastboot can only been used from the pc. I tried to push the recovery from the pc and I got the same same error messages...
Su hasn't been installed on the tablet. Even after the hard reset, the issue is the same.

[Q] error: cannot load 'recovery-clockwork-touch-5.8.4.0-endeavoru'

Hi, I am having a problem with the recovery on my One X (UK - HTC_001). I am still running the stock ICS ROM, was planning on flashing JB ROM, but noticed that the OTA update became available for my device yesterday. I flashed stock recovery (endeavoru_recovery_signed) & proceeded with the OTA update, it got about 1/3 of the way through & switched to the red ! triangle. It rebooted & still works perfectly, so I figured back to plan A & flash a JB ROM. This is where my problems have began...
1. When booted into recovery, it loads a small image (a handset with green circular arrows above it) in the centre of the screen for a few seconds then goes back to the red ! triangle & eventually (after couple of minutes) reboots the handset.
2.When I try to flash CWM Recovery or any other Recovery I get this error....
C:\Users\Danny\Downloads\OneXRoot>fastboot flash recovery recovery-clockwork-tou
ch-5.8.4.0-endeavoru
error: cannot load 'recovery-clockwork-touch-5.8.4.0-endeavoru'
'fastboot erase recovery' comes up with a similar error.
I have also tried flashing CWM Recovery from ROM Manager several times, it appears to download & says flash complete, but when I reboot into recovery it still loads the useless stock recovery.
3. When i flashed the unlock code again i got this error (although the handset is now showing as unlocked)....
C:\Users\Danny\Downloads\OneXRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
FAILED (status read failed (Too many links))
finished. total time: 16.391s
Other than this the handset works as normal. I am unsure about attempting to flash a JB ROM without having CWM Recovery. Any help / advice would be much appreciated.

try using JBFWTOOL. just do a quick search and you should find it

jinogungon said:
try using JBFWTOOL. just do a quick search and you should find it
Click to expand...
Click to collapse
Awesome, worked first time. Any tips on best custom JB ROM to flash?
Thanks

The error with flashing the unlocktoken is normal, I usually get it. Tried redownloading the clockworkmod img file?

DH0586 said:
Awesome, worked first time. Any tips on best custom JB ROM to flash?
Thanks
Click to expand...
Click to collapse
depends on what you want. for stock android i'd still go for cm10 official and i used it for three months and didn't have any problems. now i'm trying jb sense roms. i tried arhd for a few hours but got irritated of the stock sense look so i flashed renovate (renovate is a jb sense rom that looks a bit like vanilla jb, of course with the help of launchers)

[Q] Locked or Unlocked

Hey Guys,
Hope that someone can help me, I have rooted, installed recovery and custom firmware on a few HTC's.
But this has frickin stumped me !!
The desire I have gotten my hands on does not show locked or unlocked in the boot menu, but It has got S-off I didn't think it was possible??
Tried to unlock the bootloader through HTC dev and that failed, so i thought it was already unlocked
Tried flashing recovery through fast boot, but that failed!!
I'm a bit lost, anyone got any ideas as to where I'm going wrong??

Step one: Stop trying to unlock it...there is no need
Since the phone is already s-off you dont need to worry about unlocking the bootloader.
S-off is the highest level of "openness" you can have on the desire. You have the ability to write to all of the partition that you can with an unlocked bootloader, plus more.
The fact that flashing a recovery failed is indeed a problem though. What was the exact error?

Chromium_ said:
Step one: Stop trying to unlock it...there is no need
Since the phone is already s-off you dont need to worry about unlocking the bootloader.
S-off is the highest level of "openness" you can have on the desire. You have the ability to write to all of the partition that you can with an unlocked bootloader, plus more.
The fact that flashing a recovery failed is indeed a problem though. What was the exact error?
Click to expand...
Click to collapse
Dude,
Thanks for that, I'm now clearer on the bootloader issue.
This is what was returned from the fastboot command.
C:\>fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.829s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.830s
C:\>
Now the phone is just bootlooping at the HTC splash screen, any ideas whats gone wrong??

sudd1976 said:
Dude,
Thanks for that, I'm now clearer on the bootloader issue.
This is what was returned from the fastboot command.
C:\>fastboot boot TWRP.img
downloading 'boot.img'...
OKAY [ 0.829s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.830s
C:\>
Now the phone is just bootlooping at the HTC splash screen, any ideas whats gone wrong??
Click to expand...
Click to collapse
in my sig (click to show content) theres 4ext recovery as PB99IMG, click the link and follow instructions to flash recovery.
Or
Use the twrp recovery img that u have and flash it using fastboot command
fastboot flash recovery TWRP.img
Then u should be able to boot into recovery

It's ALIVE !!!!
jmcclue said:
in my sig (click to show content) theres 4ext recovery as PB99IMG, click the link and follow instructions to flash recovery.
Or
Use the twrp recovery img that u have and flash it using fastboot command
fastboot flash recovery TWRP.img
Then u should be able to boot into recovery
Click to expand...
Click to collapse
Guys,
Ok, so i realised that I was being a major dumbass and using the wrong fastboot command to try and flash my recovery.
Even when I used the command - fastboot flash recovery TWRP.img, the result was the same, no recovery for me and a bootloop
But the 4ext recovery as PB99IMG zip file on the root of my S/d card has worked, I now have a working recovery and no more bootloop.
Thanks for all your help guys

sudd1976 said:
Guys,
Ok, so i realised that I was being a major dumbass and using the wrong fastboot command to try and flash my recovery.
Even when I used the command - fastboot flash recovery TWRP.img, the result was the same, no recovery for me and a bootloop
But the 4ext recovery as PB99IMG zip file on the root of my S/d card has worked, I now have a working recovery and no more bootloop.
Thanks for all your help guys
Click to expand...
Click to collapse
Glad it worked :cyclops: ps: 4ext recovery is by far the best recovery so keep using it
Out of interest, what version of twrp were u trying to flash??
This is the official device listing TWRP Recovery
But i found this version for desire
By island3r
Im guessing u tried to flash wrong version, hense the fail.

jmcclue said:
Glad it worked :cyclops:
Out of interest, what version of twrp were u trying to flash??
Click to expand...
Click to collapse
I tried flashing both of these recoveries
CWM - Touch 5.8.2.0 - Bravo
TWRP - 2.6.0.0 - 2013.07.16
Had the same result on both neither would flash in fastboot.
Taking a look through the files on the phone i can see leftover data from both CWM and also Titanium backup, so its totally been flashed and rooted before I got my hands on it.