Hello everyone,
recently the ics update for the sensation came out, and just like the most ppl i wanted to update
Unfortunately i had s-off but were on stock rom, so i only wanted to go back to s-on without flashing a RUU (stupid me...)
Now i have a brick and i cant access my phone.
I never had worked with linux before, but i just installed a working ubuntu distribution and everything worked great till now.
I Already have a backup of my image (emmc_recover backup), the partition was sdd12
The Hex-Dump was okay too.
However for the next step (emmc_recover flash) i always get the message "cannot read image file hboot.nb0"
I tried 3 different hboots but get the same message everytime i try it.
I already am the root-user but just to be sure use sudo su in every terminal window.
I tried to have the emmc tool on "desktop" in home-directory and in download directory (the hboot, always in the same folder)
I even tried to use the full path to the hboot file
(example: "/home/knoppix/unbrick_32bit/emmc_recover --flash /home/knoppix/unbrick_32bit/emmc_recover/hboot.nb0 --device /dev/sdb12" , this time i tried it within knoppix because i thpougt, maybe its an error within the latest ubuntu distribution)
I tried 64 bit and 32 bit version of emmc_recover
I hope anyone can help me.
Many thanks in advance, and sorry for my bad english
EDIT:
And sorry for ANOTHER "pls unbrick my phone"-thread, but unfortunately i cant seem to find a solution to this problem and cant find any other ppl having this problem right now, and if...their problem is solved by either downloading hboot.nb0 again or using another distribution or using another directorie or sth like that.
johnlahm21 said:
Hello everyone,
recently the ics update for the sensation came out, and just like the most ppl i wanted to update
Unfortunately i had s-off but were on stock rom, so i only wanted to go back to s-on without flashing a RUU (stupid me...)
Now i have a brick and i cant access my phone.
I never had worked with linux before, but i just installed a working ubuntu distribution and everything worked great till now.
I Already have a backup of my image (emmc_recover backup), the partition was sdd12
The Hex-Dump was okay too.
However for the next step (emmc_recover flash) i always get the message "cannot read image file hboot.nb0"
I tried 3 different hboots but get the same message everytime i try it.
I already am the root-user but just to be sure use sudo su in every terminal window.
I tried to have the emmc tool on "desktop" in home-directory and in download directory (the hboot, always in the same folder)
I even tried to use the full path to the hboot file
(example: "/home/knoppix/unbrick_32bit/emmc_recover --flash /home/knoppix/unbrick_32bit/emmc_recover/hboot.nb0 --device /dev/sdb12" , this time i tried it within knoppix because i thpougt, maybe its an error within the latest ubuntu distribution)
I tried 64 bit and 32 bit version of emmc_recover
I hope anyone can help me.
Many thanks in advance, and sorry for my bad english
EDIT:
And sorry for ANOTHER "pls unbrick my phone"-thread, but unfortunately i cant seem to find a solution to this problem and cant find any other ppl having this problem right now, and if...their problem is solved by either downloading hboot.nb0 again or using another distribution or using another directorie or sth like that.
Click to expand...
Click to collapse
Thats sounds bad.. Ill see if i can find any help on this..
Thank you very much, i really appreciate it
EDIT:
It Worked, thanks for the help
I just had to put emmc_rescue and the hboot.nb0 into the "root" folder of the datasystem in ubuntu and it worked like a charm.
Now i just have to fglash a new ruu
thx very much for the try
Why not just flash the stock ics instead of OTA? Well what is done is done :screwy:
Sensational sent from my Sensation.
Related
Hello all, I apologize if this or similar has been posted ahead of time. I've have been searching the forums and Google for the past 4 days trying to figure this out. I'm lost...
Just to be known, I am not a "complete" noob on rooting/hacking phones. I am however a noob on this Sensation..
So a few days ago I got this phone. I had all intentions of running rooted custom roms. I've followed every turtorial I could find on it. I see there were two ways: Through SDK and the All-in-one kit v1.0
I tried using the SDK first... the problem I had with it was I would get a "failed to fetch URL"
So I would have to close down. Then after that I couldn't get "revision 5" to load up to tick on it.
Obviously it wasn't working correctly or somthing was wrong with drivers? I did install HTC Sync AND latest Java.
I dunno?
Next I went to use the All-In-One toolkit
Seemed better and easier. I went through the steps of unlocking the Bootloader - DONE!
Next I went to flash recovery.. Well I got stuck. It wouldn't load.
Well this next step is probably where I went wrong...
I was trying to move clutter off my desktop and was clicking on things... I happen to hit the "Stock kernel" button. Wouldn't be a problem except the tool kit is used for the HTC One X (although it is said to also be used for the Sensation). I'm thinking maybe I loaded thr One X kernel?
Basically, after that I am stuck on the HTC wite screen. I can get into bootloader, Fastboot, and now CWMrecovery (although recovery is giving me issues too. Can't mount USB and half the time wont run SuperWipe, will say aborted status 1 and sometimes 7)
There is current rom in the phone so I cannot boot into anything and I wasn't able to do "perm root" because of my accident.
I'm stuck and I've run out of options. Is it bricked? What can I do to get back to stock to atleast start over and get S-OFF?
I do have the OTA ICS update 1.27 if that helps.
Please, any help is greatly appreciated!!!!
http://forum.xda-developers.com/showthread.php?t=1631861
look here
first flash 4ext recovery then is easy
Thanks for replying back so quickly! That is the actual thread I've been trying to follow. My problem with it is I can't get command prompt to work right? I follow the directions but every time I keep getting "not found" in the directories. Is it something on my comp I'm not doing right?
BlastDrumBeater said:
Thanks for replying back so quickly! That is the actual thread I've been trying to follow. My problem with it is I can't get command prompt to work right? I follow the directions but every time I keep getting "not found" in the directories. Is it something on my comp I'm not doing right?
Click to expand...
Click to collapse
if you are trying to flash 4ext recovery then did you open the command prompt in the folder where adb and fastboot files are located?
if yes then did you have installed htc drivers?
best wishes
big mistake that you used kernel from that tool
i used the same tool to root my device but never flashed that kernel because it is for one x
never do steps that are not mentioning
Hi.
Your phone is not bricked..
Please look HERE
Sent from my HTC Sensation Z710e using xda premium
Hello everybody,
I've got a friend and his HTC One S is stuck in a bootloop (happened like two weeks ago and it isn't fixed since), now I've got a little bit in the HTC Android scene and downloaded an RUU file already.
I'm using this tutorial to fix it, but I can't open the RUU file, since it's an .img, I think the RUU file meant in the tut is an .exe
Now, does somebody know if I even have the right RUU file (radio-1.06es.50.02.31_10.09a.50.04L)? And if so, does anybody know how to use it?
Thanks in advance,
Sanderth.
go to htcruu.com download once download make sure have stock recovery relocked and in fastboot usb go to folder with the ruu you downloaded and run it as administrator
Thank you for the response, the problem is solved already. I left the phone at my home for the night, tried to start it this morning and found out it worked again. I guess it has something to do with automatic backup. The phone reboots like it should and works like a charm again, anyways thanks for the response
So here is the story.
I'm more of a linux user than anything else. I use Ubuntu Studio and Linux Mint on my home computer, and when I heard about the developers preview of Ubuntu Touch, I got excited.
Following the instructions in one thread here, I found it fairly simple to install Ubuntu Touch, and it looked perfect. However, it was much too early in development for use. Everything was kind of a placeholder, there was no network connectivity, phone capabilities, etc. So I went back and installed the rom I had used previously.
Here's where the problem happened. After successfully flashing the Rom to my phone and booting up into the GUI, if I clicked on anything it would reboot. Seems kinda funny, so I had tried about 5 other working roms, and they all did the same thing.
So I assume that when I installed ubuntu touch, it had actually removed a lot of the drivers for my Sensation.
HTC has been NO help at all in obtaining the correct software so I can fix my phone. Additionally, they don't even answer back my emails with comprehensible responses. I've explained this problem to them in great detail, and the extent of their responses are "if u can not find the softwares on htcdevs.com you will have to send your device in for repairs. If the damage is not covered under warranty we will let you know how much repair will cost, if you dont want repair you pay for shipping of unrepair device back to you."
Like, really?
I would like to do a fresh installation of the kernel, drivers, OS, etc so that I can use my phone again.
If you need more information don't hesitate to ask.
I hope someone has had a similar scenario, or at least know what I'm talking about and might be able to help me a bit.
What you probably need to do is flash (is it flash?) a RUU (Rom Update Utility). You can find them here.
EDIT:
Hmm.. You probably can't run .exes on Linux, can you? Maybe with Wine?
ridder215215 said:
What you probably need to do is flash (is it flash?) a RUU (Rom Update Utility). You can find them here.
EDIT:
Hmm.. You probably can't run .exes on Linux, can you? Maybe with Wine?
Click to expand...
Click to collapse
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
rzr86 said:
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
Click to expand...
Click to collapse
Oh thank you, I will check that, because I had just downloaded a RUU and booted into my windows partition, and attempted to run it. Since I can really only boot into recovery, it was only mounting my SD card, not my internal storage (i seem to recall it used to mount the device itself). So, the RUU for pyramid wouldn't run. If I can flash it, that would be best, I will have a look at that thread, thank you.
I think what happened is Ubuntu Touch stripped down android on my phone... I'm not sure if roms run as a replacement for that, or on top of it, I'm really still a beginner when it comes to phones, but usually I can manage to find the information I need to fix a problem... This is the most difficult problem I've had. Thanks again for the link.
rzr86 said:
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
Click to expand...
Click to collapse
Thank you again. You pointed me in the right direction and I got my phone working once again. Re-rooted and s-offd and now installed CM9. Thanks again for your help.
Hi,
First of all, I'm new to this Forum, but i've been following it for quite a while now since almost everything Android related you can find here. And People around here seem really knowledgeable.
I've trying to update my One SV K2_UL, and i seem to got it messed up.
I was able to flash the update, and everything went smoothely, until i got to the firmware files, a cannot get them to flash.
I guess the problem is my phone is S-ON, and i cannot change it's CID, although a tried several ways of doing it.
And i cannot guet my phone to be S-OFF, i tried Moonshine but it gets stuck on second test. - "Waiting for ADB".
My phone is exactly the same as leegreenaway refers in this post:
http://forum.xda-developers.com/showthread.php?t=2512742&page=9
so i guess, it's not an equipment problem, it was really my order of doing things that screwed this.
Can someone please help me? What can I do?
I tried to revert to old version but with no luck.
Thank you in advance.
Rui
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
I have tried rumrunner also, it behaved a little different from moonshine since it passed the second test, and found the device, but than nothing, it didn't go further it just said - "Press Enter to Exit.".
Thanks for the fast reply btw.
Then maybe this post, can give you a helping hand.
If you have Norton Antivirus, disable it. Make sure, you have a sdcard in the phone.
I did had Norton in the beginning of my day, but i already uninstalled it, just to make sure,.
I do have a sdcard on my phone.
So i tried running rumrunners once again, and took a ps of what is happening.
View attachment 2398349
When i see it right, you are on windows 8?
Windows 8 is known as not "driver-friendly" related to android/adb.
Maybe you have a chance to use a Windows 7 PC or even Linux.
Maybe @beaups knows whats the problem is...
Yes you're right,
i'm on windows 8.
unfortunately i do not own any PC with win7, althought ADB looks to be working right since i was able to use the shell and other adb stuff, i might as well give it a try tomorrow at work. I just hope i can turn this around, the phone is working great appart from that fantastic noise the speaker makes.
Thank you.
Well, today I tried to use both moonshine and rumrunner at work, but with no luck. The pc at work is running win7, althought the problem persisted exactly the same in rumrunner, in moonshine it was a bit different because it only stopped the second time it was waiting for adb. I was wondering if someone with the orange phone from UK could provide the firmware from that update, and if this souls male a difference.
Thanks again,
Sent from my HTC One SV using xda app-developers app
Last idea on my side:
You wrote in first post, you flashed everything except firmware. That means, you have the Sense 5 software already installed?
I think you should try then with the stock software, moonshine is made for.
Maybe its checking the version (HTC One SV (k2_ul) 2.14.401.6) and fails, because it is wrong.
Well, actually I got that same conclusion in my mind yesterday, just when I arrived at home from work. So I used the 2.14 odexed stock you provided in a thread, and from there I was able to run moonshine, it completed successfully, and after I just had to re-flash the 3.22 odexed, change the cid and flash the firmware. Voila, problems solved everything is in order now.
So the problem was only, the boot img moonshine was trying to flash would never work on my sys version.
Thank you very much for your help, this was a great learning experience.
Cheers,
Rui
Sent from my HTC One SV using xda app-developers app
Glad you got it sorted out.
old.splatterhand said:
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
Click to expand...
Click to collapse
Thankyou thiese s-off utility helped me to take s-off
hello,
i am trying to get my htc one mini to S-OFF and to do that, after reading most of the forums in XDA for htc one mini, i was told to use the "revone" file, unfortunately the website revolutionary.io/revone is broke and i cannot find the revone file anywhere on the net. Can any body please upload the file which will be much appreciated and one more question, i have bought my HTC ONE MINI @dubai, which stock rom or RUU or Firmware should i try if in case i have wiped my storage and lost my original OS.
Hi I have it somewhere but it doesn't work anymore. Which ROM do you have and which HBOOT? Are you rooted ?
If you have HBOOT 2.22 and 4.4.2 Android simply flash xXminiWHOOPERxX kernel V6 , then try rumrunner. It worked yesterday for me after whole day of trying with all sorts of methods. Hope that helps.
Thank you , my bad, i managed to work on RUMRUNNER, everything went fine but it seems RUMRUNNER does not work on 4.4.2. My HBOOT is 2.22 and yes i am rooted.
I really appreciate your reply, i stopped looking at XDA because none bothered replying me. I would try xXminiWHOOPERxX Kernel V6 and will update you. Thank you so much. :good:
Also i am not a geek in android, but can you please, if you don't mind, tell me how to flash the kernel? Sorry if i am being Dumb Here
EjđiSixo said:
Hi I have it somewhere but it doesn't work anymore. Which ROM do you have and which HBOOT? Are you rooted ?
If you have HBOOT 2.22 and 4.4.2 Android simply flash xXminiWHOOPERxX kernel V6 , then try rumrunner. It worked yesterday for me after whole day of trying with all sorts of methods. Hope that helps.
Click to expand...
Click to collapse
Sorry, typing response for 10 minutes with instructions, then stupid forum decides to sabotage me, really don't want to type all again. You have to flash it through fastboot (adb binaries).
Or rename it to boot.img, put in archive of rom you will flash and replace with current boot.img in archive. If you need any help , i'll try.
Hi, Thank you. I tried downloading all the 3 versions of the kernel and it pissed me off. It was a zip file and when extracted the file was an .exe which led me to viruses in my laptop. i had to format:crying: i tried searching the the whooper kernel v6 but all in vain. i don't want to risk it all again.
EjđiSixo said:
Sorry, typing response for 10 minutes with instructions, then stupid forum decides to sabotage me, really don't want to type all again. You have to flash it through fastboot (adb binaries).
Or rename it to boot.img, put in archive of rom you will flash and replace with current boot.img in archive. If you need any help , i'll try.
Click to expand...
Click to collapse
Oh man,you never ever open exe file except when you expect it to be exe file. Blue button is to download real kernel. I wish people used more friendly hosting sites tho.. Anyway here you go in the attachment.
I really really really appreciate your effort for helping me. Thanks a lot. Let me Flash it and update you. Thanks a Tons my Friend.:good:
EjđiSixo said:
Oh man,you never ever open exe file except when you expect it to be exe file. Blue button is to download real kernel. I wish people used more friendly hosting sites tho.. Anyway here you go in the attachment.
Click to expand...
Click to collapse
No problem, just make sure to post reply if everything went good, so if somebody searchs for it in the future can find this useful.
I can confirm it works however the rumrunner froze on a few occasions but it seemed to pick up from when It stopped.
I can confirm that rumrunner with the "BootV6.img" supplied above worked like a charm on KK 4.4.2, HBoot 2.22. The only downside to revone is that you can't remove the "TAMPERED" on the bootloader, but I can live with that!
EjđiSixo said:
Oh man,you never ever open exe file except when you expect it to be exe file. Blue button is to download real kernel. I wish people used more friendly hosting sites tho.. Anyway here you go in the attachment.
Click to expand...
Click to collapse
I was almost ready to give up on this site. In the dev section it looks like there might not be a single link left that's functional.
Just flashed the kernel and used rumrunner to S-OFF my mini with 2.22 HBOOT.
I almost had a mini heart attack when i started realizing that people might really be buying into newer devices and abandoning older ones at an ever increasing rate. My old HTC Desire made in 2010 lasted me until now and still mostly works with a custom ROM... I hope this mini will last me just as long although that might require opening it up to change the "non removable" battery at some point.
Bottom line, this previously used thing cost me 65eur (+10 for shipping) and it only had very minor scratches. Please don't forget those who recycle that which gets discarded by walking bags of money.