Fastboot wont work, sees device but I get:
FAILED (remote: not allowed)
when I try to flash a kernel or just boot.
my boot screen shows:
ace pvt ship s-off
hboot-0.85.0007
microp-0438
radio-26.06.04.06_M
eMMC-boot
oct 11 2010 12:47:02
Regular S-Off will not allow you to flash via fastboot, you need ENG S-Off
http://forum.xda-developers.com/showthread.php?t=855403
You can use that tool. Put a check in the box where it says "I'm already S-Off" then click "S-Off It"
Note: Some users are recommending against ENG S-Off and here's the reasoning:
Originally posted by ClearD:
With a corrupted or incomplete bootloader, meaning if your flash of engineer HBOOT fails, which is what I've been discussing this whole time, you will NOT, I repeat NOT be able to flash ANYTHING, including the stock RUU. It will not even boot. To flash the stock RUU, you need your phone to be able to boot into HBOOT mode. If that doesn't exist in a working format, that is impossible without using JTAG, which force-flashes using the phone's hardware pins and is very expensive. Make sense?
I don't look for the bad either, I just want to make sure there aren't a bunch of people with failed flashes that brick their phones beyond repair. I am simply trying to warn of the dangers, because unlike the method that Bubby uses, the ENG HBOOT method is a little riskier.
Click to expand...
Click to collapse
I haven't researched it myself, and have used ENG S-Off to flash multiple radios without any trouble. Another option, I believe, would be to rename the .zip to PD98IMG.zip, put it on the root of your SD, then let HBoot automatically install it. I've never done it this way, but I think it should work - anyone can feel free to correct me
Related
Well, title says it most, i have been trying all day to get a working root.
ut i cant get the damn bootlock (or is it called hboot?) lock away, and htcdev doesnt have a verson for desire s? or just me that cant find it, i dont know. im sort of new to working with android devices.
When i boot with volume down + power, the screen says
***LOCKED***
SAGA PUT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
HBOOT
<VOL UP> blah blah, you knowtheese lines
*****
*****
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Pola3F0x said:
Well, title says it most, i have been trying all day to get a working root.
ut i cant get the damn bootlock (or is it called hboot?) lock away, and htcdev doesnt have a verson for desire s? or just me that cant find it, i dont know. im sort of new to working with android devices.
When i boot with volume down + power, the screen says
***LOCKED***
SAGA PUT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
HBOOT
<VOL UP> blah blah, you knowtheese lines
*****
*****
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
Sounds like you need to read and do some more research before attempting this.
Just because the HTCDEV.com site doesn't list your specific DesireS version doesn't mean you can't use it.
Part of the unlocking process will involves generating a key on your phone and this is what drives the unlock process, not the selection you made on the HTCDEV.com screen.
Read and search the sticky posts on this forum.
Well, i got some steps forward in this prosses.
I got the bootlock, unlocked, and rooted with super one click, as in this >>http://forum.xda-developers.com/showthread.php?p=20701305#post20701305<< guide. but when it comes to the: adb shell chmod 777 /data/local/tmp/misc_version commend, i get the error: Unable to chmod /data/local/tmp/misc_version: No such file or directory
Whats have i done wrong now?
Pola3F0x said:
Well, i got some steps forward in this prosses.
I got the bootlock, unlocked, and rooted with super one click, as in this >>http://forum.xda-developers.com/showthread.php?p=20701305#post20701305<< guide. but when it comes to the: adb shell chmod 777 /data/local/tmp/misc_version commend, i get the error: Unable to chmod /data/local/tmp/misc_version: No such file or directory
Whats have i done wrong now?
Click to expand...
Click to collapse
Did the previous adb push command work? More than likely you received an error and the misc_version file did not get copied to the phone.
no, forst time i got that message was ther, and i tried again, and the same.
Hmm, maybe you can restore a backup from before you tried to root it. Then use this guide to root it again. Look at the discription!
That one worked perfectly for me
http://forum.xda-developers.com/showthread.php?t=1399331&page=3
This is the guide I used, I had to add a bit to 2 of the commands for mine to work but it done the trick.
When typing.
adb push zergRush /data/local/tmp
I added /zergRush
adb push misc_version /data/local/tmp I added /misc_version
Also there are 2 misc file choices in the link, use the second 1 misc_version02 zip, unzip all files into the folder on c:
Swyped from my Desire s using XDA App
Pola3F0x said:
Well, title says it most, i have been trying all day to get a working root.
ut i cant get the damn bootlock (or is it called hboot?) lock away, and htcdev doesnt have a verson for desire s? or just me that cant find it, i dont know. im sort of new to working with android devices.
When i boot with volume down + power, the screen says
***LOCKED***
SAGA PUT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
HBOOT
<VOL UP> blah blah, you knowtheese lines
*****
*****
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
So it is possible to S-OFF ***LOCKED*** hboot?I have bought this phone two days ago, but I can't understand what does ***LOCKED*** mean. There's no guide or howto specific for ***LOCKED*** phone and I'm afraid to brick my brand new phone!
thank you
Pola3F0x..........
i had unlocked my phone thru htcdev......select desire model
try step by step.....i can help you.....
Mine is S-ON unlocked and rooted
please try to other methods of downgrade/S-OFF. Using the htcdev method has two big disadvantages:
1. You may void your guarantee
2. You will have to flash the boot image after every rom change/backup restore
of course......
uqadwe said:
please try to other methods of downgrade/S-OFF. Using the htcdev method has two big disadvantages:
1. You may void your guarantee
2. You will have to flash the boot image after every rom change/backup restore
Click to expand...
Click to collapse
if hboot is ***LOCKED*** must I use htcdev ?
no, it means your bootloader is ok, and using alternatives methodes you can easily find in the INDEX you can keep it
that way.
uqadwe said:
no, it means your bootloader is ok, and using alternatives methodes you can easily find in the INDEX you can keep it
that way.
Click to expand...
Click to collapse
apologize me but I've read all the thread in the index and I havent found any answer to this question.
Thanks,
here you go
UNLOCK your Bootloader by HTCDev (S-ON - Security On) (HBOOT>2.0)
[GUIDE][01 MAR 12] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002 using HTCDEV unlock method
[GUIDE] Stuck at HTC logo/boot loop? Just flashed custom ROM after using HTCDEV unlock?
[GUIDE][13 JAN 12] How to Downgrade Latest Hboot 2.00.0002>> without using HTC Dev V2
[GUIDE][05 JAN 12] downgrade HBOOT 2.00.0002 to 0.98.00000 without using HTCDEV unlock
[GUIDE][18 NOV 11] Official HBOOT 2.00.0002 Downgrade to OLD HBOOT
Guys..i didnt want to create one more thread with a question so i am asking it here.The only reason I am talking about myself that i want to root my device is because i want to delete all the crap that it had pre-installed.Is it possible by using this method http://forum.xda-developers.com/showthread.php?t=1399331&highlight=zergrush to gain temproot then go delete the crap and go back to the original state without them or i MUST flash a new official rom without the crap? Phone info:HBOOT 2.00.0002 and software version 2.10.163.5
Guys is this possible? http://forum.xda-developers.com/showthread.php?t=1245334 ?? I just found it and it might be helpful to others as well!
If you do this, you have to use a old RUU. That means you are going to install al old version of HBOOT. Revolution can only work with a old HBOOT. But when you install that RUU. You also get a old version of the software and also a old Sense version. You may choose to use that. But i think you do not want that. So after you have done that all, you have to install a new ROM. And you may choose which rom that will be.
Auke11 said:
If you do this, you have to use a old RUU. That means you are going to install al old version of HBOOT. Revolution can only work with a old HBOOT. But when you install that RUU. You also get a old version of the software and also a old Sense version. You may choose to use that. But i think you do not want that. So after you have done that all, you have to install a new ROM. And you may choose which rom that will be.
Click to expand...
Click to collapse
Well lets make it clear..Right now i have 2.10.163.5 software version..If i download a newer software version (newer RUU) and instal it will it debrand the phone?(Without using rooting tools and stuff).Because that's what the second link i posted says...
So all you want is debrand the phone. I dont know how to do that. I have seen a few topics about that. I also do not know if you loose your warranty when you do that.
hmm i see mate..Well at least someone who knows should tell us if what i posted is valid and we can do it without bricking the phone..
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
edit: Issue solved, see page 2.
Also, in case this information helps - I do have a goldcard.img but it doesn't appear to work. My CID is T-Mob005
this guy seems to have been in the same boat as me but he did everything correctly - http://forum.xda-developers.com/showthread.php?t=1378921
if he still has his goldcard.img is there a chance it would work in my phone? I've PM'd him asking if he still has it
FrakEarth said:
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
Click to expand...
Click to collapse
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
tpbklake said:
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
Click to expand...
Click to collapse
Thanks, that's one problem down!
At present I have this RUU Europe Rom that won't load, and the T-MO UK ones still won't install either. I've installed ClockwordMod Recovery 5.0.2.0, so that's good, but I take it I still need a goldcard if I'm going to install a ROM that doesn't match my phone's carrier ID?
Is the reason these older T-Mobile ROMS won't install because of S-ON and the higher radio version number?
edit: by the way, cyanogenmod and similar ROMs appear to install with no errors in clockworkmod recovery but I don't think they are. If I load one of the RUU exes it shows the same 2.10.4 version number with no changes evident whatsoever.
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
gefilus said:
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I realise that now... I'm less concerned about rooting / getting full S-Off again and more concerned with just getting any working ROM at all onto the phone... as it seems the only ones that are probably going to work are T-Mobile ones, and the only available ROMs I can find are older - I may have to send this off to someone
So you cab get into fastboot?? If you can then use downgrading without HTC Dec unlocked bootloader, there is a post about this, try it should work and use misc_version to let phone thinks he is on older hboot and then use latest T-Mobile ruu. I hope and it should work.
Sent from my HTC Desire S using xda premium
i would do this:
unlock with htcdev.com
downgrade hboot to 0.98.0000
use revolutionary for s-off
change cid to supercid
relock bootloader again
and flash the ruu of youre dreams.
think this should do it
This worked for me in the same situation
http://forum.xda-developers.com/showthread.php?t=1443636
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
FrakEarth said:
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
Click to expand...
Click to collapse
Only if you left on USB dedebuging if it's off then sorry can't. Bet if its o n you can easy make him to boot into fastboot. Take a try, and you need to be installed sdk and adb tools on, PC. Try switch on phone put into USB and open terminal, write adb devices if it works there will show a list and HTXXXXXXXXXX something. If it so then adb reboot - bootloader or if you have custom recovery boot there. If don't anderstand look commands in Wikipedia about adb. Good luck
Sent from my HTC Desire S using xda premium
Okay guys, managed to get this sorted.
Firstly, I read that if you mounted /system from Clockwork mod that ADB commands work... well I didn't get to try that out, because something else worked.
One of the reason RUU updates were failing was because the bootloader was unlocked, when I relocked (fastboot oem lock) they started working again, but I was getting Carrier ID errors on the European RUUs and the T-Mobile ones were too old.
I decided to visit a friend who also has a Desire S and from his phone I was able to get the CID (card identification register) code from a smaller microSD card I have -- this was one I hadn't tried as a goldcard before, and I was unable to try without being able to get at the GoldCard Helper app on my phone... so after using his phone and writing down BOTH CIDs, I tried both and it worked -- I now have the phone updated fully using the European RUU.
I think my mistake the first time may have been copying the wrong CID from Goldcard Helper: if you press Menu > Copy Code it seems to copy the code from MMC1, whereas my SD card was clearly MMC2 -- so my goldcard.img was completely incorrect the first time I tried it. I don't know why the phone let me partially install the European RUU without a goldcard and almost brick the phone, but I suspect it was because I had the Revolutionary bootloader with S-OFF.
So in summary if you have this problem I would suggest borrowing an Android phone (any should work) to get the right goldcard CID needed and then try installing an RUU.
Many thanks to everyone who replied and tried to help me, you guys helped me exhaust every other possibility - and I appreciate it a lot! Thanks!
I was attempting to unroot the device, it was rooted, bootloader unlocked and s-on, had cwd recovery and was running on 4.0.3 hboot 1.27 and firmware was 3.32.66.53 (according to the ruu i was trying) it's locked to bell, cid is BM___001
i used this guide and it didn't work out very well in the end
http://forum.xda-developers.com/showthread.php?p=26541181
right now it's stuck in hboot, stating
******* RELOCKED ******
PYRAMID PUT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24.3504.10_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I'm in fastboot
but not connecting with adb anymore, it was working before a failed installation of a RUU
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_266171_signed
and i when try to go to recover in hboot, it automatically restarts and goes back to hboot
I've tried extracting a RUU into zip and putting it in my sdcard, it'll read it, check it up and in the end it says wrong model id, error, power off
I just need to find the correct RUU for Bell Sensation 4g ICS firmware 3.32.666.53 or higher since I have S on right now
i went through a few threads to get s off but it didn't work with the controlbear s off method, it can just never detect the phone when executed
but when i type in fastboot devices i do get a serial number and it's connect.
obviously right now I'm getting nothing, just waiting for device.
Just want to get back to stock first, then s off and root afterwards again
Also I flashed the stock kernel hoping it would fix the wifi problem on a custom with the all in one tool, but after that i tried the RUU and this happened
Any comments will help, sorry for being a nub, I did try my best to go through all the forums before posting here
unlock your bootloader again
flash a recovery(suggest you 4ext because you are S-ON)
see here how http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
format all partitions except sdcard
enable smartflash from recovery
immediately flash the rom
for stock rom see here
http://forum.xda-developers.com/showthread.php?t=1529941
then S-OFF with this guide
http://forum.xda-developers.com/showthread.php?t=1614617
I have successfully Rooted the device and obtained superCID, S-Off, and Network Unlock using a manual instruction thread elsewhere, however I have a few questions i am unable to find, the first one is reguarding the mmcblk's and which blocks are pointed to the different mount points for this phone, for example which block does the hboot reside on, or the boot image or recovery, ive searched google and forums and can't seem to find the info for this phone specifically, and help would be greatly appreciated. The second question is reguarding the ENG S-Off Hboot, as i understand it the later phones got shipped with gingerbread and using the known hboot was for froyo, and ends up making the phone boot very slowly, is their any tool that can be used to create an engineering hboot for GB or should I just leave it be?
Wildcat2083 said:
I have successfully Rooted the device and obtained superCID, S-Off, and Network Unlock using a manual instruction thread elsewhere, however I have a few questions i am unable to find, the first one is reguarding the mmcblk's and which blocks are pointed to the different mount points for this phone, for example which block does the hboot reside on, or the boot image or recovery, ive searched google and forums and can't seem to find the info for this phone specifically, and help would be greatly appreciated. The second question is reguarding the ENG S-Off Hboot, as i understand it the later phones got shipped with gingerbread and using the known hboot was for froyo, and ends up making the phone boot very slowly, is their any tool that can be used to create an engineering hboot for GB or should I just leave it be?
Click to expand...
Click to collapse
To find the partition table you can use this command:
Code:
fastboot oem list_partition_emmc
Regarding the ENG S-OFF you don't need ENG S-OFF to flash anything at all. Having S-OFF is more than enough and safer. You can flash the modified ENG S-OFF included in the AAHK2, using the original ENG S-OFF will mess the bootloader as you said.
glevitan said:
To find the partition table you can use this command:
Code:
fastboot oem list_partition_emmc
Regarding the ENG S-OFF you don't need ENG S-OFF to flash anything at all. Having S-OFF is more than enough and safer. You can flash the modified ENG S-OFF included in the AAHK2, using the original ENG S-OFF will mess the bootloader as you said.
Click to expand...
Click to collapse
Thank you, I got the nodded eng hboot without a hitch, now to figure out all these fastboot commands
SAGA PVT SHIP S-ON
HBPOT - 0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
I tried to revert to stock but now the os won't load, can't get the htcdev unlock to work either so can unlock the boot loader and the ruu I'm using is throwing a 140 error. Tried to htc unlock but when asking for the code for it it shows an error in the command.
I feel like I need an older ruu or a way to upgrade the hboot but I'm not sure.
Any help would be appreciated!
chapmana81 said:
SAGA PVT SHIP S-ON
HBPOT - 0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
I tried to revert to stock but now the os won't load, can't get the htcdev unlock to work either so can unlock the boot loader and the ruu I'm using is throwing a 140 error. Tried to htc unlock but when asking for the code for it it shows an error in the command.
I feel like I need an older ruu or a way to upgrade the hboot but I'm not sure.
Any help would be appreciated!
Click to expand...
Click to collapse
Error 140 may ussualy reffer to wrong bootloader version,
the numbers however, are not always the same for similar
issues they reffer to,or perhaps the numbers differ according to
different circumstances they describe- i`m not able to tell you beyond doubt,
but in your case (0.98.xxx) it could be something more like
CID, or region version error,
http://forum.xda-developers.com/showthread.php?t=2143855
posts: #2 and #3- `issues with flashing RUUs`
will sheed some light on that matter for you,
providing that other steps like:
- locking bootloader before flashing a RUU
-always choosing higher RUU version
than the one running on the device
(in a normal circumstances, one is not able to ovewrite higher
bootloader version by the lower one- not without
support of < misc_version >)
you where aware of and complied with.
As for the command, they could sometimes be
little tricky to execute,and must therefore be issued
precise to the letter,
so, always try to find that error in the command first,
before assuming it`s been caused by something like:
- no/broken comunication: PC <--> Phone via ADB,etc..
(but you may also try to look it to that corner
and assure- the obstacle is
not comming from that side)
..To tell you the truth, while flashing RUU- with
all requirements for that procedure fulfilled,
there is very little that might go wrong,
in the end, this is an official conduct that is supported
by device`s manufacturer,...
Another method of loading the stock rom on the NAND,
would be to use PG88IMG method:
-extract the rom.zip from the RUU, (google how to)
-rename it to PG88IMG
-load it on your device`s sdcard
-reboot to bootloader,
let it find an update (this very file)
and flash it...
As for unlocking procedure, it is probably
required to be on a stock rom to proceed-but i might
need a correction here,
or having kept the code obtained in the past-and use that binary,
you've said,you were attempting to come back to stock,
May i ask:
-from what?
-has your device been S-off'ed
in the past-by any chance?
- is 0.98.xxx the hboot that use to be in the device,
or, was that changed after unsuccessful RUU flash,
-what was the original system and sense version
your phone was shipped with,
-and most obvious-most overlooked:
is your phone sim /or firmware branded
to any carrier?
well i tried to use this one:
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
i got the 140 error and when i tried this one:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i also tried erasing the boot image and the recovery image using the fastboot commands but im getting some sort of access denied error.
there also seems to be no recovery image so my options are limited, any further thoughts?
I really appreciate your help, hopefully my wife wont kill me!
chapmana81 said:
well i tried to use this one:
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
i got the 140 error and when i tried this one:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i also tried erasing the boot image and the recovery image using the fastboot commands but im getting some sort of access denied error.
there also seems to be no recovery image so my options are limited, any further thoughts?
I really appreciate your help, hopefully my wife wont kill me!
Click to expand...
Click to collapse
Try to use <gold card>as my next blind thought,
With a stock recovery, one is limited anyway...
I'd say:
In your case, bootloader is your only recovery