Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
Good evening/morning all
Just grabbed this new OTA from my One S so i thought i would make an appearance... And before anyone asks, yes - I am working on a ROM
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2
Please note: This OTA takes you from 1.53.401.2 to 1.78.401.2
Change log from the updater service (rather vague):
System enhancment
Enjoy
P.S > Had no time to analyse the actual content but the OTA contains full firmware updates including HBoot & Radio.
Edit: Just noticed paul has done a repack of the base already.. may still come in handy for you devs out there
I knew you would come just like I asked for and others.
Thanks Lee.
If you can work on a T-Mobile ROM/EU ROM.
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Can't wait for some goodness from you!
Sent from my US HTC One S using Tapatalk 2
Dimson75 said:
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Click to expand...
Click to collapse
Certainly will be
Sent from my LeeDrOiD One Xtreme loaded HTC One X
woohoo !! about time you made an appearance !! I knew you was hanging around here somewhere
missed you since i left the sensation forums
I know this is probably a really stupid question but I'm going to ask anyway...
Can you actually install an OTA package on the phone somehow or is it just useful to take files out of it?
And the other question, my phone doesn't find any OTA updates anymore since I've 'tampered' with it so is there a way to make it find and install the OTA updates again?
Thanks
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
LeeDroid said:
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
Click to expand...
Click to collapse
The other thing is that when I try installing the stock RUU it's telling me it's for the wrong device or something like that, although it's definitelly the correct RUU.
Also, my phone is HTCDev unlocked but is still S-ON so if I install the OTA package usign CWM is it going to update the radio and the hboot (I thought it can't do that if you're S-ON)?
Thanks
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Did'nt work for me, wrong CID...
edit the info.txt to match your CID
azzledazzle said:
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Click to expand...
Click to collapse
Ok, maybe I'm not getting this right but I'm talking about two separate things:
Issue 1. My understanding is that I can install the OTA zip package using ClockworkMod, is that correct?
Issue 2. The RUU package won't install on my phone:
i) I have restored via ClockworkMod the nandroid image of the stock ROM (image that I've taken straight after I unlocked the boot loader and flashed a custom recovery, but before I rooted the phone). Then, I flashed the stock recovery image using fastboot. So now my phone should be back to stock.
ii) I then tried to install RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
When I do this, the RUU goes through right up to the step where it says 'Updating signatures' and then it stops saying 'unknown error' and it leaves my phone on that screen with black background and white HTC logo. Then, I have to hard boot and the phone starts up fine but in the state it was before the RUU - not even the user data is missing. To me this means that for some reason it doesn't even try to flash the RUU onto the phone but it stops when checking the signatures - I just can't understand why this is happening...
Can you help?
Thanks
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
azzledazzle said:
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
Click to expand...
Click to collapse
Sorry for my ignorance, but how do I initiate the installation of the OTA zip package using the stock recovery? As I said, I can't actually get it 'over the air' but I've just downloaded the zip package from this thread...
ok put the package on your sd card.
boot into fastboot, flash the stock recovery using the command ''fastboot flash recovery recovery.img'' (or recovery_signed.img) (also no quotes)
when thats done, select recovery from fastboot using volume button..
When you get a red ! press volume UP and power button, That will take you into stock recovery
Then look for the option, install from sd card or something like that
select your OTA package and BOOM !!! job done
Reflash CWM and away you go
Damn... I had no idea that you can actually get into the menu of the stock recovery... It all makes sense now...
me neither till about 3 days ago
I might not seem like a noob,,,,,but deep down i am
azzledazzle said:
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
Click to expand...
Click to collapse
I've tried that again and it actually breaks down when it gets to 'Checking Header...' and it exits with 'ERROR [155]: UNKNOWN ERROR". Maybe this is a bit more specific...
this is what i found for error 155
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator".
Or use the rom.zip -> PGXXIMG.zip flashing method.
Click to expand...
Click to collapse
I dont know if it will fail when flashing the rom.zip in CWM - usually you have to rename it to the model number and flash in fastboot, however you cant do this with S-ON
So I (foolishly) tried to root and flash the Android Revolution ROM onto my phone but as I should have expected, I failed.I have a plethora of problems, and I am not sure what my best course of action is:
so
1) I factory reset, so I have no recovery or ROM on my phone currently
2)My phone is in a bootloop (loads the HTC screen with a disclaimer saying "this build is for development... yadda yadda yadda" and then reboots
3)My phone will NOT powerdown, I have tried to power down my phone through bootloader, and it re"boots" and returns to bootloader once again.
4)I cannot flash any files from my PC to my phone, for example: When I try to flash boot_signed.img from the Rogers Evita Stock ROM, using
fastboot flash boot boot_signed.img, I get an error message saying "FAILED <remote: signature verify fail>" and this occurs for all files I have tried to flash
5)I have tried using ARUWizard to try and get the stock ROM onto my phone with no avail. From reading the forums I believe it is because my phone is using version 1.94.631.3 but the ARUWizard can only update to previous versions which is not allowed? (I am still very confused about this) one alternative I found on the forums was to create something called a goldcard but that required a microSD card which my phone does not have capabilities for.
So this is my dilemma, I think I am thoroughly screwed... any help or advice would be appreciated
You should still have twrp recovery even if you factory reset. Reboot into twrp, mount sd, transfer over a Rom that will work, wipe all and flash
Sent from my One X using xda premium
The_Zodiac said:
You should still have twrp recovery even if you factory reset. Reboot into twrp, mount sd, transfer over a Rom that will work, wipe all and flash
Sent from my One X using xda premium
Click to expand...
Click to collapse
I go to recovery, and it just goes immediately back to bootloader :s
I suggest starting with this thread and see what results you get.
You flashed a ROM for a different device that has a different partition layout, and that ROM installer may have possibly wiped out your partitions and left the device unrecoverable except through a JTAG brick repair
Have you tried flashing twrp again?
Sent from my One X using Xparent Green Tapatalk 2
If you're getting to the splash screen, you're not bricked. Don't start the unbricking stuff yet.
You need to get to bootloader and push a new recovery image. You probably screwed up your recovery partition when you flashed that Tegra 3 rom.
Once you've got recovery back, you just need to flash a correct rom.
If that doesn't work, try running a ruu from bootloader.
iElvis said:
If you're getting to the splash screen, you're not bricked. Don't start the unbricking stuff yet.
You need to get to bootloader and push a new recovery image. You probably screwed up your recovery partition when you flashed that Tegra 3 rom.
Once you've got recovery back, you just need to flash a correct rom.
If that doesn't work, try running a ruu from bootloader.
Click to expand...
Click to collapse
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
paoul.sukii said:
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
Click to expand...
Click to collapse
If you have recovery again why not try the method I listed?
Sent from my One X using xda premium
paoul.sukii said:
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
Click to expand...
Click to collapse
Just go into your custom recovery, mount sdcard, move the rom over, and flash in recovery.
The_Zodiac said:
If you have recovery again why not try the method I listed?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Alright, well i tried installing the ZIP I had, and it said it failed...
Maybe I should try a different zip? could someone suggest a good ROM for me that is compatible with my phone? (dont want to make the same mistake again)
I just want a ROM that has Sense, and is running at least ICS. Stability and speed are my main concerns, thanks!
paoul.sukii said:
Alright, well i tried installing the ZIP I had, and it said it failed...
Maybe I should try a different zip? could someone suggest a good ROM for me that is compatible with my phone? (dont want to make the same mistake again)
I just want a ROM that has Sense, and is running at least ICS. Stability and speed are my main concerns, thanks!
Click to expand...
Click to collapse
Before you do anything else, you should probably double check what phone you have.
Android Revolution HD (http://forum.xda-developers.com/showthread.php?t=1562603) is NOT for the AT&T/Rogers One X or the Telstra One XL.
If you have an international One X, then you're in the wrong place. If you do have one of the phones listed above, then you need to go here and download one of those roms. Then flash using what The_Zodiac suggested.
jeffwyeh said:
Before you do anything else, you should probably double check what phone you have.
Android Revolution HD (http://forum.xda-developers.com/showthread.php?t=1562603) is NOT for the AT&T/Rogers One X or the Telstra One XL.
If you have an international One X, then you're in the wrong place. If you do have one of the phones listed above, then you need to go here and download one of those roms. Then flash using what The_Zodiac suggested.
Click to expand...
Click to collapse
If I have the HTC One X Evita with Rogers, will http://forum.xda-developers.com/showthread.php?t=1868236&highlight=rogers work?
paoul.sukii said:
If I have the HTC One X Evita with Rogers, will http://forum.xda-developers.com/showthread.php?t=1868236&highlight=rogers work?
Click to expand...
Click to collapse
Yessir, that'll work. (I've heard good things about that ROM, though I haven't tried it myself).
Just FYI, the One X on AT&T and Rogers is known internationally as the One XL, and as far as codenames go, is known as the Evita, as you pointed out. The international One X is the Endeavor, and ROMs are not cross-compatible. If you stay in the "AT&T, Rogers HTC One X, Telstra One XL" sub-forums here, you should be alright.
What version of twrp are you using? Try rolling back to a 2.3.x version. 2.4.x seems to have some issues.
iElvis said:
What version of twrp are you using? Try rolling back to a 2.3.x version. 2.4.x seems to have some issues.
Click to expand...
Click to collapse
Okay, I think I am going to go to bed, and try to approach this problem tomorrow.
I am running TWRP 2.4.x so I may try and downgrade that tomorrow. I used adb to push the ROM to my phone and it is on my sdcard
However, when I try to install the ROM, it tells me that it failed... I tried clearing all caches etc but i keep getting the same errors. The weirdest part is that when I reboot my phone, the ROM disappears...
The error that I am getting is:
E:Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard'
E:unable to mount '/sdcard'
Updating partition details...
E:Unable to mount storage.
E:Unable to mount /sdcard during GUI startup.
Running boot script...
Finished running boot script.
E:Unable to mount /sdcard when trying to read settings file.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Click to expand...
Click to collapse
This is the message that is displayed in recovery, to the letter, I'm not sure if this helps...
Obviously something to do with my sdcard is wrong, preventing connection between the sdcard and something else, but maybe you guys could dig deeper, past the elementary
Thank you guys for the help you've given me so far, the outlook for my phone is much brighter now, I will check back tomorrow and continue to try and fix my phone!
Your sdcard is indeed corrupted.
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Walk through that guide using the files for the Evita on that page, it should fix your sdcard. After that you can go ahead and push the rom to the sdcard again and then reflash and see if that does the trick!
jeffwyeh said:
Your sdcard is indeed corrupted.
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Walk through that guide using the files for the Evita on that page, it should fix your sdcard. After that you can go ahead and push the rom to the sdcard again and then reflash and see if that does the trick!
Click to expand...
Click to collapse
Thank all of you so much! my problem is resolved! Phone is working great!
paoul.sukii said:
Thank all of you so much! my problem is resolved! Phone is working great!
Click to expand...
Click to collapse
Awesome! Glad to hear it!
Hello,
I'm new here but today I tried to root my phone and put CM10 on it. Rooting was not that hard but with flashing the rom I had some problems. I used a tutorial from youtube "Htc One s jellybean 4.2.2 Nightly Cm10.1 Rom" and did everything as he said but when I tried to boot CM it came in a boot loop so I restored my backup and everything was back normal again. But I thought i'll give it another try so I did that and it still didn't work so I restored (via recovery) and at the end it said: It appears your phone isn't rooted do you wanna do it now...(or something like that)? I found that a bit strange but I clicked yes but now if I boot up my phone first you just see "HTC - quietly brilliant" and then the red letters come beneath it saying its a developers version. I Couldn't do anything so I jumped into my bootloader and did factory reset but now everything is gone and I still have that booting problem,
I can acces bootloader and recovery mode but that's it
I really need my phone soon and don't have much time to look on the internet for solutions so could you please help me?
Thanks in advance!!
Lennard
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
808phone said:
Do you have the RUU for your phone? Maybe that would be the quick fix to take it back to stock. You can use an RUU that's equal or newer than what you have currently.
BTW: I went through this as well.
Click to expand...
Click to collapse
I don't even know what that it >.< (sorry for being noob )
Did you flash boot.img with cm10
Sent from my One S
ka_55 said:
Did you flash boot.img with cm10
Sent from my One S
Click to expand...
Click to collapse
Jep, as instructed in the youtube video
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
ka_55 said:
Which hboot version and radio?
Cm10 uses 3.4.x kernel, it won't boot with old firmware
Sent from my One S
Click to expand...
Click to collapse
Hboot : 2.15.000
Radio : 1.15.50.05.29
Then it can be a bad download. If not I I'm out of ideas
Sent from my One S
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
808phone said:
Do you remember doing any of the following?
-wipe data/factory reset
-wipe dalvik cache
I think that was my problem that I didn't wipe the cache completely. Possibly a bad download too. Do a search on md5. It's basically a check to see if your download is ok before flashing.
As far the RUU is concerned, it will take you back to stock. You will need the info that appears when you start the phone up by holding down VOL DOWN and POWER. Hold down volume down, then press the power for a second or 2. Then it will boot up into HBOOT.
Write down the info that appears and search for a matching RUU equal or newer.
What is the carrier???
Click to expand...
Click to collapse
I did the factory reset, dalvik cache and cache wipe. When I tried to install CM it indeed said unable to find md5 or something like that.
I think I have a europe version and looked for fitting RUU but the numbers are completely different maybe you could find a good RUU? (See attachement) Btw I have S4/Ville/Z520e
CID
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
LS.xD said:
Could you please read out your CID? Then we can get right RUU.
You can do this by booting your One S into fastboot mode and use the toolkit from the link:
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
I don't know if this is it but it says CID: HTC__E11
Lennardude said:
I don't know if this is it but it says CID: HTC__E11
Click to expand...
Click to collapse
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
LS.xD said:
yes thats it
This should be the right RUU http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
MAY anyone who reads this confirm it? Just to be safe at all.
btw. "HTC_E11" = unbranded Netherlands
Due to you're S-ON you will have to relock your bootloader to perform a RUU update.
Here you can find a step by step RUU guide by "Flashalot" http://forum.xda-developers.com/showthread.php?p=51016251
Click to expand...
Click to collapse
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Lennardude said:
Should I first relock my bootloader and follow the tutorial to flash that RUU of vice versa?
Click to expand...
Click to collapse
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you. May be your storage got corrupted and thats why your phone crashed and you can't install the rom.zip stored on the sd-card. You could connect the phone to your pc as mass storage via recovery, format it and put a new customrom.zip on it. By the way, why you installed such an old rom? You can use CM11 for sure
LS.xD said:
For RUU you need stock recovery and "locked" BL. Please read the guide again and only proceed, if you're sure you got it.
Another question:
You said you got a working recovery? Which version do you use? And have you tried install another custom rom.zip? That would be more easy and safe to you.
Click to expand...
Click to collapse
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Lennardude said:
In that guide it doesn't say anything about a relocked bootloader.
I do have a working recovery but how can I get a zip file on it? I can't acces the files of my phone in windows explorer or something like that. Also I don't know if I have a stock recovery but if I don't I have to install that via a zip but how can I get that on my phone...?
Click to expand...
Click to collapse
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it.
Click to expand...
Click to collapse
v2.6.0.0
Lennardude said:
v2.6.0.0
Click to expand...
Click to collapse
that is TWRP. My suggestion ist installing the latest Recovery and try install CM11. I just get the links for you.
LS.xD said:
PLS boot in recovery mode and tell me what "version" it is You should find it. If you're not sure about it, you can flash a new recovery before installing a rom. Whe you have a working custom recovery you can mount your sd-card to your computer via recovery.
Found the RUU guide i had in mind http://forum.xda-developers.com/showthread.php?t=2501542
Click to expand...
Click to collapse
The problem is, we're talking about an HTC One S which DOESN"T have a SD Card slot...
I could really use either one of these files to fix my phone, anybody out there able to help me out? I'm more than willing to pay you for your time/effort!
d34thbl00m said:
I could really use either one of these files to fix my phone, anybody out there able to help me out? I'm more than willing to pay you for your time/effort!
Click to expand...
Click to collapse
Have a look there. You can fin a complete RUU from AT&T
http://www.htc.com/us/support/rom-downloads.html
ouioui01 said:
Have a look there. You can fin a complete RUU from AT&T
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
I know where to find the RUU files, however that is NOT what I need. Hence the thread title.
d34thbl00m said:
I know where to find the RUU files, however that is NOT what I need. Hence the thread title.
Click to expand...
Click to collapse
I
You can extract from RUU the system.img with RUU decrypt tool from there: http://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562
cheers
ouioui01 said:
I
You can extract from RUU the system.img with RUU decrypt tool from there: http://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562
cheers
Click to expand...
Click to collapse
That thread said you need linux, I have a Surface Pro and can't dual boot, so not sure how to run a linux distro? I have made some progress, I was able to pull rom.zip from an RUU and rename that to 2PQ9IMG.zip and put it on the root of my sdcard. When I rebooted into download mode much to my surprise the RUU ran and was successful. So I reinstalled twrp, but it STILL will not let me wipe data to remove encryption. My /data is unmountable, and every time I try to do a wipe in twrp it returns the error "unable to mount storage". Twrp is also still giving me the "No OS Installed" message when I go to reboot. Is there another way to remove encryption without using linux? Or a way I can setup linux on my Surface? I just need to get root so I can s-off...
d34thbl00m said:
That thread said you need linux, I have a Surface Pro and can't dual boot, so not sure how to run a linux distro? I have made some progress, I was able to pull rom.zip from an RUU and rename that to 2PQ9IMG.zip and put it on the root of my sdcard. When I rebooted into download mode much to my surprise the RUU ran and was successful. So I reinstalled twrp, but it STILL will not let me wipe data to remove encryption. My /data is unmountable, and every time I try to do a wipe in twrp it returns the error "unable to mount storage". Twrp is also still giving me the "No OS Installed" message when I go to reboot. Is there another way to remove encryption without using linux? Or a way I can setup linux on my Surface? I just need to get root so I can s-off...
Click to expand...
Click to collapse
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
ouioui01 said:
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
Click to expand...
Click to collapse
No I haven't, I'll check it out. I'm using TWRP 3.0.0.
ouioui01 said:
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
Click to expand...
Click to collapse
Boot patcher failed, like just about everything I try, and returned with an "unable to mount storage" error. I'm stumped. I think it's weird that an official RUU fails with "os-version in Android-file is missing or invalid" error but rom.zip pulled from an official RUU goes through just fine.
If want get root , device boot into twrp "Wipe/Format Data" then back to "Reboot/recovery" install root.zip.
Sorry my bad english!!
d34thbl00m said:
No I haven't, I'll check it out. I'm using TWRP 3.0.0.
Click to expand...
Click to collapse
There was a bug in twrp 3.0.0. The last release is: Current Stable Version: 3.0.0-1
Install the last release and then try in twrp :Wipe/Format Data. Hope it will work for you...
Cheers