Hello my friends!
As my background I already played with S-OFF, TWRP, custom rom,etc...I come from an OneS S4 (lovely one) which unfortunately had display broken. :crying:
So I replaced that with the HOSV branded by italian mobile provider HTC__401 (TIM) and I would like to fully unbrand it with an HTC__001 (or HTC__405) RUU and have it finally without any bloatware or their customization on it.
Probably will be easy, but let's discuss. You are my virtual knowlege :angel:
Going to tell you what I have done to my device until today:
- Updated to Jelly Bean 4.2.2 from OTA with CID HTC__401 (the phone was totally stock). After update I had:
Android 4.2.2 with HTC Sense 5
kernel: 3.4.10-g47d5073 [email protected]#1 SMP PREEMPT
baseband: 1.18.40a.00.05
build: 3.11.901.108 CL274079 realese-keys
- Unlocked from HTCDEV (I still have the unlock_code.bin saved)
- Installed the TWRP Recovery 2.6.3.1
- Backup from custom recovery
- Rooted with SuperSU 1.80
- Run Rumrunner to S-OFF (I confirm it worked on a stock HTC__401 updated 4.2.2)
- Changed CID to HTC__001
This now the getvar of my phone:
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3787mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
and these are my boot info:
*** TAMPERED ***
*** UNLOCKED ***
K2_U PVT SHIP S-OFF RL
CID-HTC__001
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS-
eMMC-boot 1024
Nov 6 2013, 18:23:28.20240
I think I give all details you need
Now, As far as I know to be completely unbranded to run the "RUU_K2_U_ICS_40_HTC_Europe_1.17.401.3_Radio_0.12.4 0.00.14_2_10.49.40.11L_release_302178_signed.exe" I have to downgrade my HBOOT otherwise will fail (following the guide to "Back to Stock ICS for k2u & k2ul with S-Off").
Could you tell me if this is the correct procedure having the above device details? Any issues downgrading from HBOOT 2.21 to 1.xx (don't know the exact version) directly? what about mainversion could differs from the WWW version? Any major risk of brick?
Any suggestion from you all guys are appreciated. I' m here to learn from you.
I thank you in advance all the devs who work on this device!
Obviously after back to ICS and backed up the stock, I'll update and will play again with my phone
In my opinion all sounds good and should go well.
Use k2u hboot from my thread and check md5sum, then the risk is very low.
Also model id (mid) should be fine.
old.splatterhand said:
In my opinion all sounds good and should go well.
Use k2u hboot from my thread and check md5sum, then the risk is very low.
Also model id (mid) should be fine.
Click to expand...
Click to collapse
Thanks old.splatterhand for you reply.
But sounds like to many "should"
What about the mainver specified in your android-info.txt? It differs from mine, it is ok anyway?
In the worst case what would happen to the phone? I would be able to recover it?
Maybe to many question, but I think the best approch is to be careful and evaluate the things before those happened!
basically, If you were me with that phone status do you try it?
thanks a lot
I still can't believe someone just popped up with a question and gave ALL THOSE DETAILS ABOUT THEIR DEVICE!!! If only everyone else could start doing that ha! Very impressed.
If it doesn't accept mainver, it refuses to flash. In this case, change it to the unbranded number.
Your phone status is not much difference to mine, i had supercid and unbranded. But this way worked for many others to unbrand.
Modding.MyMind said:
I still can't believe someone just popped up with a question and gave ALL THOSE DETAILS ABOUT THEIR DEVICE!!! If only everyone else could start doing that ha! Very impressed.
Click to expand...
Click to collapse
Thanks Modding.MyMind!
This is what I learnt from you all guru of XDA (and in general, too. this for me means respect). Read all topic, if I didn't find the answer, collect everything I need prior to post.
I'm quite sure topic wouldn't be so long and you all will be less stressed.
What's your thought about?
thanks mate.
old.splatterhand said:
If it doesn't accept mainver, it refuses to flash. In this case, change it to the unbranded number.
Your phone status is not much difference to mine, i had supercid and unbranded. But this way worked for many others to unbrand.
Click to expand...
Click to collapse
thanks old,
with unbranded number you mean that one I have now on my phone (3.11.901.108)?
Can I try to do now, do you have minutes so you could assist me in case something happen?
I''ll start with the attachment in your post, and then we will see. ok?
thanks
I'll leave this to @old.splatterhand to assist you. You are in good hands with him. Just have patience and follow instructions. If you come across errors then be sure to provide to him the exact steps you took then the error which occurred during those steps. I would help, but I am currently slammed right now with porting 4.2.2 for K2_CL users. Mainly doing this for myself, but of course I will make it available to others as well. Almost done with it. The updater-script is what is killing me right now lol.
Modding.MyMind said:
I'll leave this to @old.splatterhand to assist you. You are in good hands with him. Just have patience and follow instructions. If you come across errors then be sure to provide to him the exact steps you took then the error which occurred during those steps. I would help, but I am currently slammed right now with porting 4.2.2 for K2_CL users. Mainly doing this for myself, but of course I will make it available to others as well. Almost done with it. The updater-script is what is killing me right now lol.
Click to expand...
Click to collapse
ok thanks I heard very well from him (also reading many and many posts ).
Good luck for the porting! :good:
I'm sorry, i'm out for some beers and only on the phone.
But if you follow the guide, i'm sure it will work.
k2u unbranded software number is 3.11.401.106.
Try it, in worst case it refuses to flash (as long as md5sum fits).
old.splatterhand said:
If it doesn't accept mainver, it refuses to flash. In this case, change it to the unbranded number.
Your phone status is not much difference to mine, i had supercid and unbranded. But this way worked for many others to unbrand.
Click to expand...
Click to collapse
oki, hboot has been downgraded to 1.01.0000 succesfully and as you said "the most tricky part is done".:good:
Phone is reebooted ok and I'm now proceeding to execute RUU in you post for K2_U,
RUU_K2_U_ICS_40_HTC_Europe_1.17.401.3_Radio_0.12.40.00.14_2_10.49.40.11L_release_302178_signed.exe
My phone is attached to a laptop, as many time suggested, in case of power loss.
a
old.splatterhand said:
I'm sorry, i'm out for some beers and only on the phone.
But if you follow the guide, i'm sure it will work.
k2u unbranded software number is 3.11.401.106.
Try it, in worst case it refuses to flash (as long as md5sum fits).
Click to expand...
Click to collapse
oops, i'm sorry mate. Don't want to bother you. Have a beer for me, too then!
I'll post the step I'm doing, you'll read then later. btw hboot was succesfully downgraded to 1.01 :good:
Speak later!
hondasat said:
oki, hboot has been downgraded to 1.01.0000 succesfully and as you said "the most tricky part is done".:good:
Phone is reebooted ok and I'm now proceeding to execute RUU in you post for K2_U,
RUU_K2_U_ICS_40_HTC_Europe_1.17.401.3_Radio_0.12.40.00.14_2_10.49.40.11L_release_302178_signed.exe
My phone is attached to a laptop, as many time suggested, in case of power loss.
Click to expand...
Click to collapse
RUU executed succesfully! Now I'm on ICS 4.0.4.
Just one thing, I'm still *** UNLOCKED *** after RUU.
I'm executing this command to have a Stock backup of ICS in case of need (recovery included then):
fastboot boot customrecovery.img
Congrats, you only have to run the updates now.
I will have many beers, as i don't have to pay them, so one is for you
YES!! Script is working!! Few more modifications and 4.2.2 Port for K2_CL will be available! Off topic, but I figured since I brought it up I might as well post this good news. Will be the last one lol. Next time will be a thread
old.splatterhand said:
Congrats, you only have to run the updates now.
I will have many beers, as i don't have to pay them, so one is for you
Click to expand...
Click to collapse
You are great man! Cheers!!!!
Now to receive update should I relock the phone? by executing
fastboot oem lock
As I'm still not receiving update to JB 4.1.2, yet.
Thanks
You usually dont have to relock. Mine worked without.
You did search for update manually?
Modding.MyMind said:
YES!! Script is working!! Few more modifications and 4.2.2 Port for K2_CL will be available! Off topic, but I figured since I brought it up I might as well post this good news. Will be the last one lol. Next time will be a thread
Click to expand...
Click to collapse
What a fantastic day then!!!!:good:
Congrats to you too, then,:laugh: Boost mobile will appreciate!
old.splatterhand said:
You usually dont have to relock. Mine worked without.
You did search for update manually?
Click to expand...
Click to collapse
Yes, I did, without success also manually.
Unfortunately mine could not get OTA, what I have to do now?
Thanks
When I try lock the bootloader in fastboot mode with
fastboot oem lock
I have this error:
C:\>fastboot oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 0.000s
The full getvar all now is:
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0000
(bootloader) version-baseband: 0.12.40.00.14_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
Something goes wrong with RUU (I'm not LOCKED after that, have to re-run again?)?Wrong CID?
Any suggestion?
A big thanks
hondasat said:
Yes, I did, without success also manually.
Unfortunately mine could not get OTA, what I have to do now?
Thanks
When I try lock the bootloader in fastboot mode with
fastboot oem lock
I have this error:
C:\>fastboot oem lock
...
FAILED (status read failed (Too many links))
finished. total time: 0.000s
The full getvar all now is:
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0000
(bootloader) version-baseband: 0.12.40.00.14_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *************
(bootloader) imei: ***************
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
Something goes wrong with RUU (I'm not LOCKED after that, have to re-run again?)?Wrong CID?
Any suggestion?
A big thanks
Click to expand...
Click to collapse
I *** RELOCKED *** the bootloader now (USB debug was not checked...)
Trying again with OTA.
No success, and still Relocked (not Lockeed ad stock)
Related
Hi, I was trying to unroot my desire S, I have been following the desire fanatics guide on youtube (Can't post the link - sorry)
And I got up to the point where I was running the RUU utility. It started and then It got to about 50% in and then said Error, please use the correct RUU utility. (I'm guessing I've downloaded the incorrect RUU file.
So now, when I turn the phone on it goes right into the white menu with all the stuff on HBOOT etc.. fastboot I think it is, and it says security warning.
I'm guessing Its wiped the data but no longer has an OS to boot into. I honestly don't think it is bricked but I have no clue what to do from now!
I got my phone from mobiles.co.uk (A carphone warehouse subsidiary) and it is on contract with T-mobile. The phone had no branding on it from T-mobile so I guess its unlocked.
However I downloaded the T-mobile UK RUU and ran that..
Any advice on what to do from here? I'm currently in the process of downloading The Saga_HTC _Europe_1.28.401.1_Radio20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
I don't even know if this will work because I can't get into any OS. I also read a lifehacker article and it said I can put a file onto the SD card and it will automatically run fixing the phone, making it better.
Please help me!
So far, I've tryed:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
But neither of these have worked, it gives me an error 140 saying I'm using the wrong version!
Can anybody tell me the correct version for an unlocked desire S bought in the UK from mobiles.co.uk?
Something that may of made this slightly more difficult for myself Is that While following the guide I followed, I used android flasher and flashed the bootloader included in the Revert to stock bundle kit thing, It was called engHBOOToverARX
I honestly have no Idea how I can fix this but Hopefully somebody else can!
can you tell me your current hboot version?
is your device detected by ADB?
if you have not set up ADB before read this below link
His device won't be detected by adb, only fastboot.
Run fastboot command "fastboot getvar all" and post the response.
Ok, this is what I get after fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: SH15NTJ00762
(bootloader) imei: 356708049175530
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
And I have the ability to run adb commands but I don't know what command to use to check if its detecting my device, I type adb into cmd and loads of commands come up..
@imattacus
Okay you have a UK unbranded phone, I say this cause your CID is HTC__001 and your main version is 1.47.401.4.
So to fix you can either;
1) You can download this RUU (v1.47.401.4, hboot 0.98.0002) and run it from the PC.
Or
2) Change your main version (by getting shell root) then trying again with the 1.28.401.1 RUU. (but may be impossible since you can't get adb)
Option 1 is the easiest.
Same issue with Virgin Mobile RUU
Anyone got the correct RUU for me as I've got the same issue with a Virgin Mobile RUU. I followed the instructions for unrooting here. I was using the Virgin Mobile RUU listed on the link provided which was this list but I keep on getting error 140 when I run the RUU, telling me to use the correct one.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I just need to find the right RUU version.
Any help would be greatly appreciated and as soon as possible.
Thanks
Just use Goldcard and try 1.47.401.4 again.
I also have a few problems with my Desire-S:
-my android email app keeps crashing when i try to open any email;
-official update aborts instalation (system 7) (even after hard reset).
So i decided to try fixing this via RUU. My phone is unbranded (bought in Slovenia's Vodafone), unrooted:
-android 2.3.3
-Sense 2.1
-Build 1.47.401.4
-Boot says: Saga PVT Ship S-on RL, Hbroot 0.98.0002, radio 3805.06.02.03_M
I tried to install:
-RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed.exe
Every time i get an error 131- customer id error and message, that the ruu is wrong...
So i tried with the older one:
-RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe
And i keep getting error 140.
And i'm stuck here. Any help? I'd like to put on 2.3.5 with sense 3 without that email bug.... and i'm considering taking it to the repair service...
Thank You
i had in a way similar problem with imattacus...
only i can't run adb commands (adb devices returns no value)
i tried folowing ruu-s:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
RUU's installed, but after boot phone was stuck in white screen with green htc.
after i installed this RUU my phone booted:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
update>>
I checked for updates and there were some... After installing phone stuck on white screen...
I just whish to restore my phone to it's factory outofthebox state..
My getvar all result is::
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13HTJ16283
(bootloader) imei: 355067040509788
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Any sugestions?
Goldcard
Sent from my HTC Desire S
I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!
>>>>>update...
Unfortunately, with gold card everything went same as before...
When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...
i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...
my fastboot screen reads:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
One more curious thing..
When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?
>>> FINAL UPDATE
SUCCESS!!!
as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.
have a nice day, everyone!
Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
masev said:
Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
Click to expand...
Click to collapse
Given that this has been covered many times, you would be better off listing EXACTLY what you have tried and the results you get so that people can have a better chance to help you. However, the answers are all out there and you simply need to read and make sure that you understand what you are doing and why.
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
masev said:
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
Click to expand...
Click to collapse
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
SimonTS said:
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
Click to expand...
Click to collapse
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
masev said:
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
Click to expand...
Click to collapse
RUU to a higher version.
Had the same problem with a branded phone. Problem is - you need a higher RUU. In my case there was no higher branded RUU.
I've made a gold card and flashed a unbranded higher RUU (latest ICS), and that makes the phone work again.
But without HTC-dev unlock we now can't get root! So if you can't find a higher RUU with your brand you may can't bring it to service with the new unbranded software on it.
Gesendet von meinem HTC Desire S mit Tapatalk 2
Hi everyone.
I'm trying to get back on stock (S4), but I can't find any RUU that matches my hboot and radio.
this is the result of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4005mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried several S4 RUUs, european ones gave me error 131, Vodafone UK gave error 155 (the cellphone was bought in Italy).
What I did before executing the RUU exe(s) was just locking the bootloader. I think that probably installing ROMs in the time (the cellphone belongs to a friend of mine, so I don't know what was installed before) may have somewhat changed hboot (and/or radio) version, and now I can't find a RUU matching mine. Now i can only access the bootloader (I think the previous custom recovery is gone). I managed to access recovery by unlocking again the bootloader, but I can't mount any partition from the recovery (which is the main problem that lead me to decide to get back to stock.
What are my chances to return to HTC stock?
I have the same problem
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
addsfsds said:
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
Click to expand...
Click to collapse
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
hasanalikhattak said:
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
Click to expand...
Click to collapse
Dude give a quick look around, all the guides are here! or come to androidiani.com to get italian translated guides and support!
HI Guys
So my mate's phone won't boot up and I'd really appreciate some assistance. The last thing I did was unlock the phone via htcdev. But that's all I could do. Now I can't flash a recovery (I've tried a few) because I get an IMAGE UPDATE ERROR. I've also received a "SIGNATURE VERIFY FAIL" error.
Also, adb won't recognise my device but fastboot does.
What I'm trying to do is install a custom rom because my mate was complaining that his phone was slow and a bit laggy. I sold the phone to him in the first place so I've taken it upon myself to fix it.
Thanks guys, let me know if you need any further info.
CJ
First of all, we need some information about your phone.
I need : what kind(k2u, k2ul and so on)
Then what you have already done.
Then the other things (best of all you copy all information from your boot loader)
Edit: okay skript point 2 xD
Kreumadragon
Thanks for getting back to me.
Here's the information you've requested.
UNLOCKED
K2_ul PVT SHIP S-ON RL
HBOOT-2.21.0000
Radio-1.18.40a.00.05
openDSP-v13.2.0268.0620
OS-3.12.980.10
eMMC-boot 1024MB
Jul 2014
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.12.980.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2BWTP01724
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8015000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.100s
Let me know if you need any further information.
With regards to what I have already done, I tried to flash TWRP recovery but I got an image update error.
Mhh do you flash the right TWRP?
And use fastboot flash recovery *recovery name*?
Do you have any data's to loose?
Kreumadragon
yeah I flashed a few different TWRPs and none of them worked.. if there is a specific one and if you have a link, I could try again?
nope i don't need any data to lose. I have removed the sd card. Thanks again.
Anyone? Still having no luck with this phone.
Please test (if you want) the cwm recovery. Link:
http://forum.xda-developers.com/showthread.php?p=37075457
If this doesn't work flash a ruu and try again
Kreumadragon
There is no RUU out which will work and also the cwm is outdated.
How did you flash recovery?
Use the one i recommended in my index thread. This should work on your hboot.
An other option is to get s off and flash it via pl**img.zip isn't it?
Kreumadragon
You need a working OS for S-off. Not sure if that is working here.
@Old
You have s off, haven't you?
And I get s off with hboot 2.21
Kreumadragon
I don't have One SV anymore.
Rumrunner works on hboot 2.21.
He says that he didn't have data's to loose
theoretically you can create an ........IMG.zip file with all files a ruu use, only the recovery is changed? Think I can make one but first want to read what you think(old)
Kreumadragon
As long as he is S-on you don't need to make anything.
Right now he can only flash signed firmware by HTC this way.
Okay, thx I don't know
Actually no ruu for any kind of k2ul?
Kreumadragon
Only one. And you must be S-off or on ICS to use that.
@CJ_
Do you have test old.s method?
If this doesn't work, you probably need SOff.
Kreumadragon
Hi old.splatterhand, to answer your question, I flashed the latest TWRP recovery (2.8. something) but I got the following IMAGE UPDATE ERROR. Will try the ones in your index and report back.
Thanks for your help guys.
Will try it now... If that doesn't work, how do I get S-Off when I can't do anything with the phone?
Hi DEVs,
My phone is stuck ina bootloop and been searching for tow days but no luck.
i will be soo thankfull if someone could provide me with the correct rom
(Bootlouder Locked and S-ON)
C:\ADB>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.401.106
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT39JTP00464
(bootloader) imei: ----------------
(bootloader) meid:
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097s
None gonna help me ?
medpks said:
None gonna help me ?
Click to expand...
Click to collapse
If you can run Android, you should first do S-OFF.
Read and understand >this< post and adapt the appropriate files to your k2_u device (without LTE).
ze7zez said:
If you can run Android, you should first do S-OFF.
Read and understand >this< post and adapt the appropriate files to your k2_u device (without LTE).
Click to expand...
Click to collapse
Thanks for your reply, but as i mentioned above i am stuck ina bootloup so no way i could perform a S-OFF
ze7zez said:
If you can run Android, you should first do S-OFF.
Read and understand >this< post and adapt the appropriate files to your k2_u device (without LTE).
Click to expand...
Click to collapse
Thanks for your reply, but as i mentioned above i am stuck in a bootloup so no way i could perform a S-OFF
medpks said:
Thanks for your reply, but as i mentioned above i am stuck in a bootloup so no way i could perform a S-OFF
Click to expand...
Click to collapse
If the bootloop is on every startup, the eMMC memory may be corrupted.
In this case there is a small chance that the RUU will help.
Anyway, I can see the ROM > here <.
If after logging in you will not be able to access the file, check the remaining links after searching in google.
I wish you luck.
ze7zez said:
If the bootloop is on every startup, the eMMC memory may be corrupted.
In this case there is a small chance that the RUU will help.
Anyway, I can see the ROM > here <.
If after logging in you will not be able to access the file, check the remaining links after searching in google.
I wish you luck.
Click to expand...
Click to collapse
I agree with you about That eMMC could be corrupted :good: , but im having a slight doubt it could be a software issue, and i want to try Flash first then confirn.
Btw thanx for the RUU link, but its a paid file.. wish i could test my phone with a free file
Official OTA
medpks said:
(...cut...) wish i could test my phone with a free file
Click to expand...
Click to collapse
You should be satisfied. Below is the link to the official OTA from HTC.
OTA_K2_U_JB422_SENSE50_MR_HTC_Europe_3.11.401.106-2.14.401.107_release_339145qf6n2sk971fk7x3k.zip
Guide: How To Manually Flash OTA File