Database Info

[q] bricked? Arhd bootloop

Hey guys, I been away from the sensation for a few months now and I think I bricked it on my first flash back! I was flashing ARHD & I followed the noob guide, I downloaded firmware & updated, deleted the firmware file, performed super wipe, flashed the rom, and I checked my md5 sums. Now I'm bootlooping the white HTC splash screen, and sometimes I see the beats audio symbol but right back to the slash screen! Ahhh.... I use this line for work. I used the 3.30 firmware as it said to & I'm on boot 1.27? I know one of you guys can help, so please ANYONE,I've got a get this fixed tonight.....

well if its booting then fortunately you're not bricked lol
have you tried re flashing the new firmware?

I flashed the 3.30 that the installation guide I was following told me to. I have ext 2.2, so is that an issue or is it the correct recovery.

Anyone who can walk me through this I'd really appreciate it guys. Just like most, I rely on my phone for work. I'm a little worried here, I've flashed quite a few times and I've never had an issue like this that I couldn't restore out of.....

Try this??
what I did was everything you did.. except I used this firmware update...
Firmware from 3.30.401.1 & 3.30.401.101 RUU
--- MD5 checksum: 824295C6ACDC8D55BED9E0B913192DBE *PG58IMG.zip ---
--- Only for 3.30.401.1 & 3.30.401.101 based ROMs
Then I installed the ICS Energy rom, and everything works great.. I've also flashed a few other roms without issues.. I haven't tried the arhd yet.. I'm currently running the virtuous AOSP rom.. and still, everything works great.. I hope this helps
Just a side note.. have you tried formatting the sdcard then trying that setup? I did have issues with my sdcard in the beginning, but after formatting, I've had no issues..Also make sure the ROM you're using is made for the correct firmware, otherwise you'll have bootloops! hope this helped!

That's the same firmware I used, and I've ran the firmware upgrade twice now. Now right after I updated the firmware the first time I did it, I rebooted on accident & it wouldn't boot even before I flashed arhd.... is this normal?

It wouldn't boot into hboot? What I did was put all the needed files on my sdcard, flashed the firmware, removed the sdcard(while the phone is powered on).. booted into the rom, then put the scdard back in and removed the firmware update..then rebooted the phone, then wiped and loaded an ICS rom..that was really about all I did.. and so far all works well.. I'm really at a loss as to what the problem on your end is.. it sounds like you've done everything you're suppose to do..

You could try to run the relevant ruu (assume you have s-off?) and start again?
http://forum.xda-developers.com/showthread.php?t=1074559

Update::II flashed Virtuous and had no issues and everything is running perfect. Looks just like my transformer prime now. I doing know why at this point that my system would not play nice with ARHD, I followed the guide to the letter and I flashed the firmware 3.30 several timed just as directed. None the less, I am satisfied with this from, and my device is much smoother and more productive than the ****ty GS2 by T-Mobile that I had been using the last few months! I just can't retire my Sensation. Thank you to all who chimed in, you're a great community!

Bricked
That happened to me too when I tried to install ICS without updating the firmware
first.
I just re-booted to recovery and did a restore. I'm assuming you backed up your
ROM right?
Then at least your phone will go back to normal and you can start over...and use it for work haha

I'm good now on virtuous, but I just couldn't get ARHD to work for me. Yes I had upgraded to the proper firmware first, and I always compare md5 sums. I'm by no means an expert, but I always research, read and ask all the nessecary questions before I flash anything I'm not familiar with. I think there may just be rare occasions when some of the devices just won't play nice with certain software. Virtuous took on the first flash & I'm actually very pleased with it, so all's well that ends well. ICS is just so much more intuitive & functional for me
.

Very Weird Issue with my Sensation is there a self test service mode?

Im currently in the middle of uploading a video to youtube to try and show the issue but its like my phone is possessed, i actually bought the phone from a recycle place so I have a 60 days warranty with the phone but I was wondering is there a diagnostic or service mode I can get into on the handset to see if any faults are found
One thing is I thought I was getting an Orange handset which I would have thought would have had some branding on but it didnt and it also didnt have any orange bloatware on but not sure if they do or not on Orange UK handsets? even though i've supercid would it matter if it wasnt an Orange one that I used the orange firmware for 3.32?
It seemed fine when it arrived yesterday on 2.3.4 GB rom but since changing to ICS nothing but bother
Link isnt live yet showing about 12 mins to go at 21:49 UK Time
http://youtu.be/Z2Bvf0FfTlU

My phone is currently
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
Hboot-1.27.1100
Radio-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012.17:33:34
Had this problem with Darkforest 6.0.0 and also ARHD 6.5.1 and currently virtuous s4x b3 which has been the worst of the lot and the one in the video

Ok so I flashed back 1.17 firmware and restored a back up of my GB 2.3.4 rom and its working perfectly so my guess is my phone for some reason doesnt like firmware 3.32? which means im going to be pretty much stuck on GB?

Hey, it looks like a sense 4 rom that is running in the video? All those roms are ported from another device.. I'd recommend to try stock ICS with the new firmware, see if that works any better than the ported roms

Ive tried 2 3.6 roms too and they did the same, used the newest firmware

http://www.htcsensationforum.com/htc-sensation-4g-how-to/secret-menu's-in-sensation/

The Radius Kid said:
http://www.htcsensationforum.com/htc-sensation-4g-how-to/secret-menu's-in-sensation/
Click to expand...
Click to collapse
thanks, not quite sure what im look at but thanks all the same will take a peek

bradmax57 said:
thanks, not quite sure what im look at but thanks all the same will take a peek
Click to expand...
Click to collapse
In your first post you were looking for a diagnostic mode?

The Radius Kid said:
In your first post you were looking for a diagnostic mode?
Click to expand...
Click to collapse
Sorry yeah i am and thanks, just not sure which tests i should be looking at, anyway im now on virtuous_inquisition v4.0.0 but using firmware 3.24 its had one little hissy fit which seems to have gone away when i restarted, also when it starts acting usual screen of and on seems to sort it, its just odd it works perfectly in GB which makes me think its software and not hardware issues?
Just to confirm im doing everything right, was it ok to jump from firmware 1.17 on GB straight to 3.32 for ICS with 3.6?
Method im doing
flash firmware in hboot, pull battery delete the PG58IMG file, put battery back in boot into recovery, full wipe in ext4, then run the superwipe script and then install rom, everything seems to go ok until I begin having the issues as shown above in the video clip, I know that was a sense 4 rom but its done the same in 3 sense 3.6 roms now

Did you tried to flash a stock kernel? Not OC'ed? My bet if every ROM does the same, that there is an issue with the hardware.

davebugyi said:
Did you tried to flash a stock kernel? Not OC'ed? My bet if every ROM does the same, that there is an issue with the hardware.
Click to expand...
Click to collapse
Hi
I havent as yet, however when I first had problems on darkforest I did try with the 1.2ghz option during flash.
Any recommendations on which to try? So far it seems on on v inquisition v4

Seems to have been ok then this morning I put the phone on charge as it was about 20% remaining, left it charging went back 30mins later or so to check it and it wouldnt wake, not sure if this is a common issue or if its related to the previous problems ive been having?
Ive requested a return from the place I bought it so will see, ill have to make sure I can get it back to how it was, fortunately I have a backup, but ill have to read up on the s-on procedure aswell as getting rid of 4ext

gawd this is doing my nut in, just flashed Android Revolution 6.5.1 using the stock 1.2ghz kernal doing the same so I just have no idea now, going to put firmware 1.7 back on and do a nandroid recovery and see how that goes for the next few days, just wondering if anywhere in the rooting + S-off, unlocking or supercid somethings gone wrong that I didnt see, but afaik it all went fine

format sd card, place only the files you will need.. i.e. firmware and your choice of rom.. reboot phone, flash this firmware "Firmware from 3.24.401.1 & 3.25.401.101 RUU" from http://forum.xda-developers.com/showthread.php?t=1412618.. after you flash the firmware, remove the sdcard while the phone is still on, reboot into recovery. Once in recovery, put the sdcard back in, then flash whatever rom you wish to use, just make sure that it supports the firmware, after flashing the rom, remove the sdcard again and reboot phone.. once the phone is booted, turn on usb drive and remove the firmware that's on the sdcard and see how things go.. if things are still messed up, then go for an exchange as at that point, it may be hardware related...
I don't think it has anything to do with superCID or s-off as I can see that you're able to flash any rom to the device.. same with s-off...

Quakeworld said:
format sd card, place only the files you will need.. i.e. firmware and your choice of rom.. reboot phone, flash this firmware "Firmware from 3.24.401.1 & 3.25.401.101 RUU" from http://forum.xda-developers.com/showthread.php?t=1412618.. after you flash the firmware, remove the sdcard while the phone is still on, reboot into recovery. Once in recovery, put the sdcard back in, then flash whatever rom you wish to use, just make sure that it supports the firmware, after flashing the rom, remove the sdcard again and reboot phone.. once the phone is booted, turn on usb drive and remove the firmware that's on the sdcard and see how things go.. if things are still messed up, then go for an exchange as at that point, it may be hardware related...
I don't think it has anything to do with superCID or s-off as I can see that you're able to flash any rom to the device.. same with s-off...
Click to expand...
Click to collapse
Thanks, ill give it ago! the only bit is where yousay after flashing firmware remove sdcard whilst on, then reboot into recovery. The only option I get is to reboot no option to reboot into recovery?
anyway
flashed insertcoin 5.1.4 so will see

in order to boot into recovery after flashing the firmware, power off the phone, yank the battery and sdcard, then put the battery back in and power on with the usual power down + power button with the sdcard still out. once in recovery, you will notice that recovery counts down until the sdcard is back in so slip the sdcard back in, give it a sec, then choose the zip file you're going to flash.. flash the rom, remove sdcard and boot into rom.. slip the sdcard back in one final time.. once booted, go into the sdcard and remove the firmware so that it doesn't keep wanting to update everytime you reboot...reboot once more to make sure all is setup and see how it goes.. I'm sure there are easier ways of doing this, but this is one method I've tried and all worked fine... hope this helped..

Quakeworld said:
in order to boot into recovery after flashing the firmware, power off the phone, yank the battery and sdcard, then put the battery back in and power on with the usual power down + power button with the sdcard still out. once in recovery, you will notice that recovery counts down until the sdcard is back in so slip the sdcard back in, give it a sec, then choose the zip file you're going to flash.. flash the rom, remove sdcard and boot into rom.. slip the sdcard back in one final time.. once booted, go into the sdcard and remove the firmware so that it doesn't keep wanting to update everytime you reboot...reboot once more to make sure all is setup and see how it goes.. I'm sure there are easier ways of doing this, but this is one method I've tried and all worked fine... hope this helped..
Click to expand...
Click to collapse
Still the same, flashed back to 1.17 and did nandroid recovery and it works perfectly in GB oh well, the closest Ive had it working on ics was with Virtuous Inquisition v4.0.0. The problem im going to have returning the handset is that it works perfectly as it was sold to me and if I start going on about installing ics roms etc they are likely to refuse a return.

yay!!! think ive cracked it, well not me but at least I think what ive found what the problem was
Spotted this rom http://forum.xda-developers.com/showthread.php?t=1542192
Thought what the hell, and long story short its worked, not a single issue like before, which leaves me to believe that for whatever reason 4ext recovery wasnt working correctly when flashing firmwares on my phone as when I used it to restore my original backup it worked fine. Installed the rom above that was packaged as a PG58IMG.zip file and it worked great, might try and reinstall clockworkmod and see if that helps as I never actually used it
Fingers crossed its now sorted but so far so good, not a single issue after installing all my apps again

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.

I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk

I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA

Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.

Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.

I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though

I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).

I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.

Flashed ROM won't take even with S-Off

After a tragedy with my S3, I'm having to limp along with my old One SV. Unfortunately I am having trouble getting this thing to keep a newer ROM. And before anyone says "turn s-off" I have S-Off already.
Booting to the boot menu it says:
moonshine S-OFF
K2_CL PVT SHIP S-OFF RL
CID-SPCS_003
HBOOT-1.01.4444
RADIO-1.1250.0516
OpenDSP-v9.2.0268.1214
eMMC-boot
Jan 16 2013, 01:26:39:-1
I've tried jellybean flashing
I tried the viper ROM (which gets stuck flashing unless I don't install all the google apps)
Post every flash, I turn the phone off and then power it back up. For a little while it'll say something "correctly" like that it's android 4.4.... buuuuut it is still the default wallpaper and goes back to saying android 4.0 and of course the bugging to update to a new stock android is still present as is the "out of storage space" error message....
I've tried updating the recovery (currently a somewhat buggy cwm where the screen is 1/8th offset half the time... v6.0.2.8) and that hasn't worked... Typing this out I decided to try flashing the recovery once more since when I first was doing it I apparently had S-ON... So I flashed the latest TWRP (3.0.1-0-k2_cl) and..... now it's bricked.... it won't boot normally nor will it boot into recovery mode, but I can get to the hboot menu.... HALP! lol
The final kicker to my scenario is that I'm on linux and don't have access to any Windows machines, but I do have heimdall and adb installed.

Okay... So because I was still able to get into the HBoot menu and then put it into the Fastboot menu with the USB cable connected I was able to flash a new recovery.
I got the TWRP 2.8.5.0 recovery from http://techerrata.com/browse/twrp2/k2_cl
I was able to install fastboot and adb thanks to http://forum.xda-developers.com/showthread.php?t=2638673
I re-tried flashing the Jelly Bean rom I had with the same result as before the bad recovery problem occurred... It boots up, but it's still Android 4.1, even though it is S-OFF-ed.... And that shouldn't be happening... I'm pulling the battery and rebooting after flashing so nothing should be overwritten... What gives?

Your best way to go:
http://dl3.htc.com/application/RUU_...V_NV_Boost_2.20_150_release_389346_signed.exe
As far as i remeber, there was no custom rom that was made for k2cl.

correct.. there is no custom rom for the boost variant.. there is a partition swapper changing the 4gb media with the 1gb internal storages.. romcleaner works to get rid of all the boost garbage.. twrp will fit your screen.. havent used cwm since my hero

The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
I tried to get the RUU to work, but couldn't. I borrowed a friend's Windows laptop, installed adb and fastboot and it just would not connect or see my phone in the RUU. I even tried forcing the driver to be installed correctly, which never worked for some reason.
I ended up installing Link2SD and setting up a 16gb partition for apps. So at least it's not complaining about being out of space anymore. It is still wanting me to download the OTA update. Not the end of the world.
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?

Hathalud said:
The Viper rom claims it covers all variants. And somewhere along the way I downloaded two Boost based roms aside from that.
Click to expand...
Click to collapse
Hm,
From the Viper Rom thread:
Modding.MyMind said:
THE VIPERSV ROM IS NOT FOR BOOST MOBILE (K2_CL) USERS!!!!!!!!
This is what could happen to you if you fail to follow instructions!
Click to expand...
Click to collapse
xpirt said:
This Rom is not compatible with Boost/Cricket variants, which model have you flashed it on?
xpirt
Click to expand...
Click to collapse
Hathalud said:
I do have a new issue though. For some reason the "wiper" app keeps crashing. Not sure what it is or where to find it. I suspect it's named differently and I either need to flush it or install an uncorrupted copy. Any suggestions?
Click to expand...
Click to collapse
This was a permission bug from updater script, when i remember.
Wiper is some wifi or network location service. If you don't need it, rename it or delete it.

Phone acting really weird (HTC m7)

Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%

universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it

Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.