Related
will any of this work with the myTouch? im in the US and have one, but havend done anything to it yet. I have a rooted G1, would i be able to use the same JF software? if these are all dumb questions, dont tell me. lol
I was just going to post about this. I cannot seem to get any of the rooting methods to work with this phone. Here is the info:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
May 27 2009, 19:06:41
Any help would be appreciated.
You can't root the MyTouch 3G due to what haykuro described as a "perfect" SPL.
That's true. Haykuro is saying that it is the perfected SPL on his blog. Don't fret everyone as this just makes dedicated hackers like Haykuro more interested in being the ones to root it.
Go Haykuro Go!!!! I know you've put in hours upon hours of hard work rooting our beloved devices and moving us forward in the field.
Thanks.
That doesn't mean I forgot others who have put hard work in. I just wanted to let Haykuro know as he has been missing from our scene because of the poor treatment or lack of credit when due.
I'm not sure you comprehend what the SPL is since its not as clear for Android as it is for WinMo. The SPL allows you to overwrite the entire system and the modified SPL's allow you to flash unsigned. Now the SPL resides in a part of the device that stores other vital low level software like the radio and such.
In order to flash the SPL, the new SPL has to take the same exact place as the old one using the same exact memory addresses or else it will overwrite the other vital low level like the radio and one incorrect byte in the wrong place could cause you to be unable to make calls, etc.
This is where it gets to be a pain in the ass because the SPL is what allows you to write to low level parts of the phone and more importanly use the USB port as a serial port. If the SPL is flashed badly and you can't communicate via USB anymore you now have brick unless you know JTAG. Another problem is if the radio or anything else overwrites part of the SPL causing a brick.
In other words you will probably be able to achieve root via a software exploit but if the SPL cannot be replaced then you will never be able to flash a new ROM.
Hope that helps. sry for being so long winded
how about after achieving root (via software exploit), we replace the recovery.img with a modified one via adb shell? Is that possible?
(n00b here)
The SPL will not allow it to be written although there may be a solution like fakesigning ROMs using some sort of security hole.
like previously mentioned the SPL will not allow it. So until a great mind like Haykuro finds away of replacing the SPL with a modified one not in an update.zip or a fastboot flash it will not be posible till then. Maybe a nbh file might be possible but currently there is not one that is available for this device yet.
nope cuz .nbh = updates.zip for winmo and works almost the same way
mytouch
rogers started a fund raiser i think we need to start another one?
Has anyone tried using a Goldcard to flash Dreaimg.nbh or another system image? It's been done on the Dream, I don't see why it would be any different on the MyTouch.
Someone needs to figure this out. This is the only thing keeping me from buying a MyTouch. Someone help free me from my loose hinges and inexcusable lack of system memory on my dream...
I realize that there may be no easy solution (or none at all) for this predicament at this time. However, I thought it might be helpful to start a thread that is solely devoted to trying to get root access back on devices that unfortunately have already applied the mandatory Rogers update.
I have absolutely no answers, but I am more than willing to donate to someone who puts time into solving this issue. The other thread(s) are filled with pages upon pages of people just whining and complaining about Rogers and their ill-fated attempts to work with tech support. This is not my intention for this thread. There are a few posts within the sea of complaints that are directed towards a solution, but they are not the easiest to pick out.
Anyone with any ideas, PLEASE post here!
Hack the nbh?
Hi,
As I said in an earlier post, we all now know that the flashrec method is broken, and the goldcard method seems to be broken.
Trying to downgrade the rom fails with an error that basically says you can't install an older firmware over a newer version.
Question: How does the firmware perform this validation? Is it via the build number or timestamps on the files?
Question: Are we able to make our own NBH files? Is the structure known?
If someone can figure out the first question, then we will be half-way there, assuming someone can package nbh files.
gNoob
I'm in school right now (taking college courses now )
But, when I get home, i'll play around with it.
Question: How does the firmware perform this validation? Is it via the build number or timestamps on the files?
Click to expand...
Click to collapse
There is a "version" on the NBH that is checked. (when i get home today, i'll show you guys the down-and-dirty of each NBH [the latest and the old one])
Question: Are we able to make our own NBH files? Is the structure known?
Click to expand...
Click to collapse
Yes, and no. The structure is known. We *CAN* create NBH files, but they won't be signed. The stock SPL runs a check on the NBH files for a signature. If the signature is off, it won't flash. Therefore, no we can't.
Has anyone tried this method?
Could this method work. Treating the phone as a brick and bringing it to a pristine state?
Sorry, I'm a "new" user so I can't post urls correctly until the admins let me
code dot google dot com/p/android-roms/wiki/Unbrick
JakeArmitage79 said:
Could this method work. Treating the phone as a brick and bringing it to a pristine state?
Sorry, I'm a "new" user so I can't post urls correctly until the admins let me
code dot google dot com/p/android-roms/wiki/Unbrick
Click to expand...
Click to collapse
http://code.google.com/p/android-roms/wiki/Unbrick
Yeah they did that cause new users would spam Ads or other things.
Nope, this unbricking procedure doesn't work. It returns the following message:
Model ID incorrect!
Update Fail
Not too surprising, actually. If only we could get someone who works for HTC to sneak their signing key to Haykuro. Then an .nbh file with a version number greater than the version inside the SPL could be created and maybe the SPL would allow itself to be replaced.
Interesting challenge, this.
Okay, so I decided to try and see what was inside this RUU from Rogers. When it is initially run, it extracts its contents into my temp directory, and there you can find the rom.nbh file. I thought, maybe, it might allow me to switch out the rom.nbh with Haykuro's older image. So I started the installer, while it was sitting on the start page of the wizard, I replaced rom.nbh with Haykuro's, and it allowed me to get to the part of the updater where it uploads the image to the phone and tries to verify the update.
Unfortunately this fails because it reports the BootLoader version is 'incorrect'. I wonder if this means the wizard can be 'patched' to allow the downgrade?
I also noticed that there's a version fastboot.exe and adb.exe inside the installer's temporary files. I wonder if there's anything different about these versions of the files that might allow them to sidestep the new bootloader checks? Though I suspect without a correct signature this would also fail.
Just fiddling with this, trying to understand the details.
Old Rom:
Version: 1.85.631.5
Model ID: DREA21000
Target CID: ROGER001
New Rom:
Version: 1.89.631.1
Model ID: DREA21000
Target CID: ROGER001
I'll have more time to play with this later, i had some other stuff come up right now. Hopefully in a few days i'll have a bit more to put up.
Thanks Haykuro,
Just a little more information about my fiddling today. I verified that the fastboot.exe is pretty much stock. Trying to 'flash' the firmware with this returns a 'Remote not allowed' error. I also tried taking a look at ARUWizard.exe and ARUGlobal.dll. I thought these might be .NET code, but as far as I can tell, they are not, so maybe a standard decompiler would give some idea of what it's doing inside there? I might try to understand this a little more later.
120 volts to the battery terminals...
That should wipe the Rogers crap off the eff'ing memory and clean things up real good
With that wipe thought in mind is there a way to wipe the device and basically take it back to how it would have been before any rom image was installed at the factory? jtag'ing perhaps...
The problem I think is that the bootloader won't allow a version below version 1.89.631.1..
Man they locked this thing up tight...
Since my dream is pretty much now a useless crashing and freezing POS I was tinkering with the erase/flash <partition> commands of fastboot from the command line and all I get is the FAILED <remote: not allow> Same message when trying to flash a recovery image.
Tried to write an spl too and nadda...signature errors
Wonder if jtagging it would do the trick...hehehe
Too bad we can't JTAG. If we could then there wouldn't be all these DeathSPL bricks laying around :\
Yea eh...seems nobody has found a solution that would allow us to do that. I was reading the HTC service manual last night and it's not mentioned in it so I think if a brick needs fix they install a new motherboard.
t3mp3st said:
I realize that there may be no easy solution (or none at all) for this predicament at this time. However, I thought it might be helpful to start a thread that is solely devoted to trying to get root access back on devices that unfortunately have already applied the mandatory Rogers update.
I have absolutely no answers, but I am more than willing to donate to someone who puts time into solving this issue. The other thread(s) are filled with pages upon pages of people just whining and complaining about Rogers and their ill-fated attempts to work with tech support. This is not my intention for this thread. There are a few posts within the sea of complaints that are directed towards a solution, but they are not the easiest to pick out.
Anyone with any ideas, PLEASE post here!
Click to expand...
Click to collapse
Thank you for starting this, I agree with it all. Most willing to donate to whoever figures it out.
I also stupidly updated and am kicking myself for it. So hopefully we can get something done soon.
I'm definitely up for sending a donation to the winner too. Jeez am I looking forward to that day!
Hopefully Haykuro will soon have some time to share his expertise with us!
Anyone have any thoughts on what you see in the first pic attach to my post in this thread ??
Never mind...figured out where I got the file and like the others mine fails to complete because of a version error.
Ok I fixed the version error fail part...
With a hex editor I changed the version info in the ROGERSDREAM.nbh file haykuro posted here from 1.85.631.5 to 1.89.631.1 but now I get a "Signature incorrect" error. I need the 1.89.631.1 nbh so I can compare but trouble is HTC Sync since the update no longer see my device so the RUU won't run which screws me from digging the nbh out of a temp folder.
Hi all
I feel like i am going round in circles trying to get my 32b magic rooted. Ive tried all sorts of methods even buying relentless rooter magic, but after lots of helpful emails i was told i have a perfected spl1.33.0007.
I was then told my problem would be solved by creating a gold card. I did this following the unlockr guide. Then went back to trying to use relentless rooter but I still cannot get the phone rooted.
I would appreciace any guidance at this point as I really dont know what else to do. Some of the help people give is great but it assumes a certain level of android knowledge that I have not got and will not ever have.
Thanks in advance fellas. I hope you can help as I love my phone
Regards
Del
have you tried follow these instructions?
http://forum.xda-developers.com/showthread.php?t=548218
to make sure your not on perfect spl.
for rooting check this thread
http://forum.xda-developers.com/showthread.php?t=547133
then you should be able to fix it
Sorry to be stupid but where do i get the following from?
* an non-perfected SPL (preferably an engineerings SPL).
* a ROM with a version that is HIGHER than your current ROM version.
Im sure this is all straighforward stuff to all you guys who do this all the time but it just seems like one obstacle after another for me
Thanks again for the help
i don't know much about the 32b version, but the second thread i posted to you is the one to use, try read very good the first post in it, cause the first thread i posted he tells 32b user to go to the second thread, so try study the second thread thats what i can do to help, hope you find something in it.
Again please excuse my stupidity but i have not a clue what ROM is appropriate for my phone. This is the problem that I always encounter, that others assume that your level of knowledge is comparable to theirs. I know im not a total moron but this is a whole new language to me and the last thing i wanna do is ruin my phone. It seems the more i read on forums etc the more i get confused as there are a seemingly infinite array of different methods to get your phone rooted.
well can you provide info on which spl radio you have now first?
He mentioned in the original post he had perfected spl1.33.0007.
How about telling us what you did with the goldcard process, what happened and what went wrong? Any errors received that you can tell us etc will help us to help you.
just wondering cause he messed with the phone after getting the info of perfected spl so just wanted to be clear what there is to work with so he can get a working good phone
I followed the gold card process on the unlockr webby and all went fine. No issues there at all.
Im now stuck as to what to do next. I bought relentless rooter software and the guy on support has been helpful. Just wondering what my next port of call should be. Like I said im no Mr Android but Im not totally clueless either. I would just like it if someone could tell me what should be the correct/best/simplest procedure for getting my phone rooted and getting the best/closest ROM to 2.0/2.1
Sorry to be a pain but there is so much info out there its really difficult to determine whats right and whats wrong.
BTW Ive got 2 magics so if a totally brick one, Ill know to definitely stop. Unfortunately they both have the same spl
Thanks again in advance
Just tried another method from the relentless support. Ive put SAPP.nbh on my goldcard and restarted with vol down and power. Tried to apply the image and got an error of
model id incorrect!
Update fail
Do you want to reboot device?
any more advice please?
first off im not trying to be a **** here... but..if your having this much trouble rooting, and you admit you dont know much, then why are you bothering rooting??
if you root and get a custom rom on your phone, you will NEED to know how to update said rom, as you will not get support from your carrier.
rooting is not hard, there are MANY guides out there that hold your hand and walk you threw rooting, installing rom ect ect...
for you i would recommend cyanogen mod (www.cyanogenmod.com) JUST because it is stable and works great.. i dont think you want a rom like super d , cdsi , fasttest or something like that where you will probably have to update your rom somewhat often.
please see this guide and READ it fully, its not hard to understand or to follow....just make sure you are on a 32B, if you are not then this guide will not work..
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
also you are looking for a rom that is 2.0/2.1, first off they are not fully functional, there are issues with all 2.0/2.1 roms out there (some are great dont get me wrong, but in my mind not fully functional) so again i would recommend cyanogenmod its based on 1.6 but has bits and pieces of eclair(2.0) in it. before you try a 2.0/2.1 rom i would say get root first, run cyanogenmod and go from there..
again.. im not trying to be a ****.. but it really isnt hard rooting.. and hearing you say you dont know anything is kind of rediculous.. i came into the android scene not knowing anything, its easy to learn if you want to, if you want the easy way out without learning then dont root...
edit: Im sorry i sound harsh, but i still stand behind what i said.. please please please try the cyanogenmod wiki guide, and also please post EXACTLY what sys ver your running, which carrier your on, and confirm please the SPL..
i started out knowing nothing too, but reading and do what guys say in their guides gets you far, and when keep wanting to tell in every post (i know nothing) is kinda saying, don't use custom roms cause if something goes wrong, you will be more fustrated and angry on the android system (also not trying to be rude, but think about it, do you really want to root?)
In the normal course of events I am capable of following the simple instructions found on forums like this to do whatever I need. In the past I have chipped my xbox and flashed my 360, but I am really struggling with my phone. The reason I went for the relentless piece of software was because it was supposed to be simple.
As far as I was concerned I was having a problem following the instructions until I was told I had a perfected SPL. Thats why I had so much difficulty in the past getting it rooted. I thought using relentless might help me out in that respect. It didnt.
So I then find out that I need to create a gold card. Got that sorted ok, then proceeded with the root process. All systems stopped again as I get model id incorrect error. I posted on here to see if anyone else was having the same problems and would be willing to help.
I am really thankful for the suggestions so far and if anyone has any more I will endevour to use them. But my main problem is that there is so much info out there its difficult to work out whats right and wrong especially if you are encountering problems like I am. Ive seen many videos and read many tutorials on how to root so I know it should be straightforward but that has not been my experience thus far
have you tried the wiki link i posted??
start over.. forget everything you have done.. and try that wiki link..
again we need to know your phone model, carrier, spl and sys version(android 1.5, 1.6, ect ect) to move forward if you still are stuck..
Thanks again for your help
My phone is a UK Vodafone Magic 32B
1.33.0007
CPLD-10
Radio- 2.22.19.261
Its running on cupcake and wouldnt update OTA when it was sent out last year
Just reading through that wiki now. Thanks again for all your help. I really appreciate it
also see this
http://forum.xda-developers.com/showthread.php?t=640229&page=2
delboypb said:
Thanks again for your help
My phone is a UK Vodafone Magic 32B
1.33.0007
CPLD-10
Radio- 2.22.19.261
Its running on cupcake and wouldnt update OTA when it was sent out last year
Just reading through that wiki now. Thanks again for all your help. I really appreciate it
Click to expand...
Click to collapse
You need to make certain that your gold card was made properly. My first attempt at making a goldcard failed for no reason what so ever. The second attempt went fine on the same micro sd card. I would follow the directions of using Flashrec. That process has been flawless due to the fact that it takes advantage of a bug in Android 1.5. It's easy as long as your goldcard was made properly. Good Luck
p.s. once your able to flash an engineering/non-perfected spl, Leave It Alone.
I had the same problem with mine, couldnt find a guide that works on a uk Voda Magic
I used this and it worked great:
http://wiki.cyanogenmod.com/index.p...o_CyanogenMod#Spanish_Vodafone_1.6_NOT_rooted
Use the guide for Non-TMobile 32B Magics
sapphire pvt 32b ship s-on g
hboot-1.33.0007 (sapp30000)
cpld-10
radio-2.22.23.02
jul 31 2009, 15:49:25
main version is older!
update fail!
do you want to reboot device?
action yes
power no
tmobile mytouch 1.6 just a regular mytouch not 1.2 ( fender)
i had rooted about 12 mytouch ( tmobile usa) and never had any problem till now,
i did the gold card using theunlockr how to.
and i still get the same error.
not know what to do to get this done.
i just can't downgrade to 1.5.
thanks.......................................
I finally pulled my head out of my ass last night/early this morning and got a handle on what i needed to do. And now I have a rooted magic with a shiny new hero rom on it. Very pleased with myself. Now off to try to get the second one done. Fingers crossed
Thanks everyone for all your help and patience. Its really appreciated
Back to square 1 again. After the excitement of havig a working root and displaying a rather lovely hero rom, I though all was well. So I decided to have a crack at rooting my other magic. During the process which was unsuccessful this time my original rooted decided to shut itself down for no apparent reason. Whe i tried to reboot it would get to the splash screen and no further even though it had been working perfectly happily just hours before.
Any help please?
The details are:
32b ENG S-OFF h
HBOOT-1.33.2005 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
I rooted using the gold card method and flashed with a hero rom. All the instructins taken from theunlockr.com as I couldnt get the cyanogen wiki instructions to work.
I did try the cyanogen wiki method having already rooted using gold card, but that phone also stops at the splash screen after flashing bot images. I waited several times for 15mins+ but nothing
I would really appreciate some help mainly on my first issue
Thanks in advance
I am deciding to take the plunge and root my phone. what I am curious about is whether or not I can create a goldcard on a 1 gb sc card. I have scoured google and searched the forums and cannot find an explicit answer to this question. If anyone has some insight I would greatly appreciate it
youngalumni said:
I am deciding to take the plunge and root my phone. what I am curious about is whether or not I can create a goldcard on a 1 gb sc card. I have scoured google and searched the forums and cannot find an explicit answer to this question. If anyone has some insight I would greatly appreciate it
Click to expand...
Click to collapse
I believe that you can do it on anything upto 4gb? either way I used the 2gb card which came with my phone without a problem
i've created on 512mb
it doesn't matter the size, it must be fat32 formatted...and you have to follow instructions which you can find here
http://forum.xda-developers.com/showthread.php?t=572683
What I don't understand is - what's a goldcard?
Sorry for my stupid question, but I allways see "goldcard here, goldcard there"... but what's it??
Is it an SDCard which is able to self run flashing a particular radio/SPL? Can you use it with a perfected SPL? If yes, why don't all just use this method? And also, in case of brick, can it be used to unbrick it? (Dis)advantages?
Thanks
Excellent!!! I'm doing this today. the only other question I have is whether it would be easier for me to do this on windows 7 or my ubuntu partition?
elegos said:
What I don't understand is - what's a goldcard?
Sorry for my stupid question, but I allways see "goldcard here, goldcard there"... but what's it??
Is it an SDCard which is able to self run flashing a particular radio/SPL? Can you use it with a perfected SPL? If yes, why don't all just use this method? And also, in case of brick, can it be used to unbrick it? (Dis)advantages?
Thanks
Click to expand...
Click to collapse
Yep, it is. It doesn't work with every single perfected SPL though
People always use brick incorrectly. If you brick it, your phone is dead, gone, not usable. You effed it up completely and the only way to restore it is to like mess with hardware.
In the case though, where you soft brick it (for example: no ENG spl and you need to flash an RUU or w/e to get it working again) then you'll need a goldcard. Just do what you do and get an ENG SPL in and you won't need a goldcard. With ENG SPL, You can do fastboot commands, which does wonders =)
If it helps, you guys can only really brick your phone if you play with radio and SPL. So while your rooting it, I'll just let you know (This gave me peace of mind..) Don't be nervous, I was the first time! Then I found out you can only brick it if you don't follow instructions and put on the wrong spl/radio.
youngalumni said:
Excellent!!! I'm doing this today. the only other question I have is whether it would be easier for me to do this on windows 7 or my ubuntu partition?
Click to expand...
Click to collapse
Hmm.. I remember reading somewhere that windows 7 causes problems. But that may be for RUU stuff, so give it a try! If it doesn't work, move on over to ubuntu. It should work fine in windows 7 though!
yeah I figured out the windows 7 issue with hot sync and the adb...
im past that. the only isue i am having right now is with the goldcard. from the looks of it i am golden i have a serial but when i type the next command in the instructions
Code:
cat sys\class\mmc_host\mmc1\mmc1:*\cid
im getting a file not found error...
do i need to put my formatted sd card in my phone? or is the info i need physically on the phone?
ok sorry about wasting space and time by asking questions that I was able to figure out. but the only issue i have now is that i flashed the fender rom from theunlockr.com it gets to the android boot screen and now its blank. should i try another rom?
done. thank you
First of all thanks for this great forum !!!!
This will be my first post. I have to thank all developers to get the sensation s-off.
I made a stupid mistake with the eng hboot. I played a little round and typed
"fastboot oem fdisk erase_emmc.
Now Phone is completly dead and bricked. Can not power on and no charging.
But it must be possible to bring the sensation back to life. I downloades QPST an drivers and see, that the device is in download mode.
I tried cdma workshop and DFS CDMA Tool too.
Can somebody make a dump with QPST and backuo the nv file and firmware image to unbrick the sensation.
Please no commands why I have done this. I said it before. I have no second sensation to try it by myself.
Has anyone an idea ??? (without to send it back or jtag flash)
Thank you for any help.
Kindly regards Woody01
Sorry for bad English
Send me the commands and i do it for you!
No comment on what you have done
I'm sorry man, but we can't help you. Once you erase something like that, it's over for that device. If i'm reading correctly, the internal sd card is completely wiped, no recovery, no HBOOT, no / (original mount point). The thing that bothers me, if you didn't know what it did, why would you run that command? That is idiocy at it's finest. The only thing you could do is send it back for a warranty replacement, since it's bricked like that, they won't able to tell you ever rooted or flashed anything. If you do send it back, play dumb, say you woke up one day after charging it all night and it just wouldn't turn on any longer. Once you get your replacement, do not install the ENG HBOOT, it isn't for noobs for this exact reason.
Download mode could be a mode where it wait for flash ... keep it off until someone comes with ideas....
Thank you for your answers but I expectet such replies.
It must be possible to bring it back. In QPST you have the ability to flash back the Multi-Image file. But i am missing the the phon image hex and boot hex. I think if someone make a backup from the Multi-Backup and NV file we could unbrick it.
For the Galaxy S someone wrote at tool (One click unbrick). There will be everything restored. (partition, boot, etc).
Is someone interestet to help me trying this ????
Kindly regard Woody01
I say again tell me how i do it .... backing up should be no problem for a device
@xtcislove
First of all you must dwonload QPST (I found it by google). I have version 2.7 buil 355.
You need the QHSUSB Drivers. I found the drivers on google. I think the phone must be in diag mode. Use QPST Software download. There is an option backup. There you can backup the firmware. It will be restored as an qcn file.
To restore the NV File you can try DFS CDMA Tool. There is an option to read the NV file. At that point I could write the file from Wildfire. I could delete it too. I used the free version 3.2.0.0
For Diag mode you need the HTC Diag driver.
It is possible for me to upload these files here in forum and is it allowed ???.
Thank you
Be careful with the NV file. There is your imei and serial number. It would be nice if someone send the file with edited imei and serial.
I need the hex files for QPST. Some wrote in the www something about CDMA-Workshop to get the hex dump.
Kindly regards Woody01
Sry i cant edit my imei etc out ...
and with 3 posts i dont trust you really ... sry i think u should ifnd someone
@ xtcislove
I understand you and is absolutly O.K . I would not send the NV file with my emei and serial too. (only the file with editet imei and serial)
I hope someone is interestet and crazy to unbrick the device and help me.
Kindly regards Woody01
Get a warranty replacement and don't even S-Off your phone. You obviously can't handle it.
In curious, why were you doing what you were doing?
Sent from my HTC Sensation Z710e using XDA Premium App
WorldWide60 said:
In curious, why were you doing what you were doing?
Click to expand...
Click to collapse
Haha i was wondering the exact same thing
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
massasshadows said:
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
Click to expand...
Click to collapse
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Bricked mine too (Yes, very stupid indeed)
aramis73 said:
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Click to expand...
Click to collapse
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
choas2009 said:
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
Click to expand...
Click to collapse
I'm actually doing the whole return process. Since mine is so badly inoperable, I'm hoping that after they inspect it they will be able to give me a new one. I was able to S-On the phone (as far as i know) during the process so if they are able to read it, it should be cool. If anything i'll either be turned down or have to pay for a new one.
Planning on blaming it on the over night charging + the 2.3.4 update they released the day i bricked it haha. It's all just a game of chance.
i did it too my friend , some mistake S-off ---> s=on transition , do you have any solutions
Hello everyone, I'm a noob and this my first post. I had been reading blogs for years now on all sort of advice and solutions, so yes this is my first reply or post on any blogs. I usually find the answer I'm looking for so posting anything was unnecessary. Now I really need help. I screwed up some how. I was attempting to turn S back to ON because my device was not taking the new update, and by doing so bricked my phone (wont power on. I'm guessing I had restored a rom and not original back up which xl VipeR lx had warned about in his instructions. I have SD with su-2.3.6.3-efgh-signed.zip on it. Can someone please help I really should had not rooted my phone because I dont have the knowledge. I can take instructions very well (was Soldier in the U.S Army for 8 years (2 years in Iraq). So if some one would please give me instruction on how to fix this, I would really appreciate it.
Is there any solution ?
Thanks !
Would this tool allow me to make a backup of my phone that can be restored if ever it is bricked? In other words, would it make my phone nearly unbrickable? I mean, there is very little chance of my phone being bricked, I make sure I know exactly what command does before I execute it. I realised I have spent most of my days in the last couple of weeks reading XDA and thinking about my soon to be gf in Hong Kong XD. I just worry that when flashing a firmware file I may be left with a brick, or even get one of those bricks people speak of that just happens randomly. I really don't want to lose my phone, it means so much to me lol. I just get so worried with these things....
What I'm trying to ask is, a partition backup created with this tool can be flashed to the phone with what functioning partitions? ie do you need a working radio partition or not? working hboot? Cause what I'm scared most about is flashing a bad radio and creating a phone that can not get into hboot... i'm also scared about getting a random brick which at the moment seems to be unfixable.
Mind you, it would make a pretty impressive paperweight....
EDIT: found this guide... can someone explain what NV items are? A small understanding of this may allow me to make a backup using this tool that could then be used to unbrick sensations... I couldn't find what NV items are... I also found this....