Related
Hello, I have a T-Mobile HTC Sensation 4G, and I've ran into some problems recently. I'm a basic-intermediate user when it comes to Android, but I can't find a solution specifically for this. It started with a small problem but got worse and worse until I couldn't even boot correctly.
I started out installing a small custom battery mod, but that led to a few problems with the notification bar (not a big deal).
Then I tried to revert to the stock battery to fix the problem, format cache and dalvik cache in recovery, and reset. Then I was put into an infinite boot loop with the HTC splash, but going into cwm recovery was still possible.
Then, in recovery, I could not access my sd card for some reason, so I shut off, reinserted the sd card, and remounted it, then I reset again.
Now, it's impossible to boot to android at all, and I am completely stuck at HBOOT/FASTBOOT, and cannot access recovery OR perform a hard reset.
If I try to reinstall cwm recovery, I get a partition update fail as well...
I have full root, s-off, etc.
ROM- InsertCoin 3.3.1
Kernel- Stock
Hboot- 1.17.1011
Clockwork version- 5.0.0.8
Any suggestions? Am I bricked? I can give more details if needed.
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
neoissuperman said:
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Alright, thanks, I'll try that soon and see if it works.
Update: Unfortunately, I don't think I can flash anything, it just comes up with a partition update fail...
Anyone else know what I could try? I also tried to flash the 1.45 RUU, but it can't continue past the search for the bootloader.
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
joshndroid said:
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
Click to expand...
Click to collapse
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
joshndroid said:
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
Click to expand...
Click to collapse
Nope, still nothing, I even tried different sd cards and usb cables, with no difference...
So has my phone been reduced to a paperweight?
APmoss13 said:
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
Click to expand...
Click to collapse
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Divine flaw said:
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Click to expand...
Click to collapse
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
APmoss13 said:
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
Click to expand...
Click to collapse
ok.... i was just askin cause did the exact same thing (well almost, i tried to change the notification icons which resulted in my notification bar completely gone) you did and got into that infinite boot loop. and couldnt boot into android. and couldnt figure it out. the only thing i did was just install the ruu while i was in the fastboot screen and it worked. i wasnt aware that there was a 1.45 ruu for tmous but i dont think that should matter since you are scid anyways. now im just wonderin if you tried any other ruu's besides that one. for me i flashed the 1.29 ruu for tmous and that got me up and running...... sorry i couldnt help
Hey guys I have somewhat of a problem. I'm experienced when it comes to rooting phones (by no means an expert), but this problem has me stumped. You see, I was helping my friend to root his phone Photon XT897 and showing him how to do it. We got the device unlocked, installed CWM and rooted the device, all without issue. Anyways, I had to leave to go to work and he decided that he knew enough that he wanted to install TWRP recovery. According to him he did that by flashing an image of TWRP via fastboot, and everything was fine... except his wifi would no longer turn on. He then proceeded (and God alone knows why he thought this would help) but he formatted the modem in recovery and now, obviously he gets NO data connections whatsoever. I've scoured this site and everything I've been able to find online to fix this with no result; can somebody please help me? So what I need to know is this:
1. Has anyone else experienced wifi issues (i.e. the wifi no longer turning on) when flashing TWRP?
2. Is there any way to restore the modem?
3. Can I trade my friend in for a smarter version or at least store credit?
Thank you!!
No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here: http://sbf.droid-developers.org/asanti_c/list.php
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin
hfase said:
No problems with WIFI here.
You can get your modem back by either doing a full flash with RSD and the appropriate file found here:
Or if you want to flash only the Modem fish out this file from the above ZIP NON-HLOS.bin
The command used would be similar to the following.
Code:
fastboot flash modem ./NON-HLOS.bin
Click to expand...
Click to collapse
Thank you for the suggestion, but I tried both of those and neither one produced any results. I can't flash the NON-HLOS.bin in fastboot becuase it says:
F:\Scottys Droid ****\Devices\Motorola\Photon XT897\android-sdk-windows\platform
-tools>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load 'NON-HLOS.bin': No error
I can't flash the entire file with RSD because at first it throws the error:
getvar not found or something to that effect which I understand; getvar isn't a fastboot command. I then googled that problem and somebody with a similar issue with another phone said merely removing the line of code in the xml that calls for "getvar" fixed their problem. I tried that and now I get the error:
Flashing process failed flash sbl1 "sbl1.bin" -> phone returned fail.
Any other suggestions?
Are are the files extracted to folder you are running that command in?...
If not you will need to call the file with its absolute location. In ubuntu that looks like the following:
fastboot flash modem /home/hfase/Desktop/modem.bin
Hence the ". /" shown in my earlier example. Meaning "same dir" in linux. these will of course be different on Winblows.
If you cant get fastboot to flash just that try backing your system/data up with TWRP and just flash it with RSD. (using the edited XML found around here...) Basically for RSD to work you need to delete the getvar's in the XML.
If you look at my posts I posted a thread showing the XML file you need with the getvars edited so it works,, and even added the steps to relock the bootloader if you are interested lol
Sent from my XT897 using Tapatalk 2
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
I'd love to... how?
arrrghhh said:
Hmmmm never mind it seems you edited those lines already....
Can you post the full output of your error ?
Click to expand...
Click to collapse
Actually, RSD Lite is suddenly working now... but I didn't do anything different so I don't understand why its cooperating. Well, there is one thing different that I did: I restored a TWRP backup that my friend made before the phone went down. You see, after he wiped the modem partition he installed a ROM (the Evervolve ROM), which didn't boot. He did this in an attempt to fix his mistake, thinking that the ROM carried a modem file in it. When I learned of this backup, I restored it and got into the phone; obviously the modem still wasn't working, but then I figured I would try the RSD flash again. So I removed the "getvar" lines of code from the "asanti_c-user-4.0.4-7.7.1Q-6_SPR-125_ASA-10-11-release-keys-Sprint-US.xml" and it worked.
So the modem issue is now fixed, but wifi issue is not. I'm unclear as to whether I should close this thread because it's main issue has been solved, or if we can now take a look at the wifi issue. Basically, after flashing the TWRP recovery through Goo Manager that I downloaded from the market (I did this in the app by choosing the "install script" option, as I was instructed to by another of XDA''s threads) I then rebooted the phone only to find that the wifi didn't work. Whenever I go to turn the wifi on, the switch immediately goes back to the off position, but in the window below the switch it still says "turning on wifi." Please advise if I need to open a new thread, or if not, how we can perhaps solve this wifi problem. Thank you.
OK, glad you got the phone booting again.
Have you tried just doing a 'factory reset' in TWRP since you got the phone back to a functional state?
What kernel is flashed?
Hey again, so, trying to fix the problem described here: http://forum.xda-developers.com/showthread.php?t=2523194, I decided to go back to stock rom (JellyBean 4.1.2 from LiquidSmooth 2.1). I did it trough fastboot (with a batch file) because I'm on windows 8.1 and can't get RSD to work.
So, fasboot gives me the error several times:
"(bootloader) variable not supported
target reported max download size of 3147280 bytes"
Now a have a phone that won't go past motorola logo. I can get to fastboot mode (but can't use rsd, doesn't recognice my phone) and my have my bootloader unlocked.
How should I proceed to bring it back to life? I've been trying everything I could.
Edit: Well, my phone is working again. I installed TWRP again and CM10.1
But I still not able to install a stock rom. So, I also was going to try with a virtual machine with different os but decided to not take (more?) risks.
If could be of use, I could install windows 7 on my machine.
daro.brussa said:
Hey again, so, trying to fix the problem described here: http://forum.xda-developers.com/showthread.php?t=2523194, I decided to go back to stock rom (JellyBean 4.1.2 from LiquidSmooth 2.1). I did it trough fastboot (with a batch file) because I'm on windows 8.1 and can't get RSD to work.
So, fasboot gives me the error several times:
"(bootloader) variable not supported
target reported max download size of 3147280 bytes"
Now a have a phone that won't go past motorola logo. I can get to fastboot mode (but can't use rsd, doesn't recognice my phone) and my have my bootloader unlocked.
How should I proceed to bring it back to life? I've been trying everything I could.
Edit: Well, my phone is working again. I installed TWRP again and CM10.1
But I still not able to install a stock rom. So, I also was going to try with a virtual machine with different os but decided to not take (more?) risks.
If could be of use, I could install windows 7 on my machine.
Click to expand...
Click to collapse
by "batch script" do you mean you tried this? http://forum.xda-developers.com/showthread.php?t=2474393
shouldn't give errors unless something in your partition table is messed up.
********Edit, i just read the other post and see you are on a 925, do not flash the script i suggested above.
bweN diorD said:
by "batch script" do you mean you tried this? http://forum.xda-developers.com/showthread.php?t=2474393
shouldn't give errors unless something in your partition table is messed up.
********Edit, i just read the other post and see you are on a 925, do not flash the script i suggested above.
Click to expand...
Click to collapse
Hey, I fixed it using this tool http://forum.xda-developers.com/showthread.php?p=38190729.
It installed stock rom by sending big files "in parts", I believe. So I dind't have problems with size. Thanks for your answer though.
Hey guys,
So this morning I stupidly tried to update to 4.4.4 since the phone said it has an update available. I was rooted running a few xposed modules, so I did the update, everything was fine, then upon getting back into the OS system.ui kept crashing every 3 seconds.
"Okay, just go use your Nandroid back up and flash via TWRP like always" I thought. So I did exactly that - rebooted to recovery, and went to flash my backup and it just sat there at "writing system" and did nothing. Next I rebooted to recovery again and did a full wipe of the OS - userdata and all, then tried two different toolkits (Mac and PC) and THEY got stuck at the 'writing system' as well.
Now I'm trying to flash stock to get my damn phone working via fastboot, but when i use the command fastboot flash userdata userdata_64g.img I get my cmd window saying "target reported max download size of 536870912 bytes erasing 'userdata'..."
This has been displaying for about 25 minutes now and I don't know what to do... Do I just leave it? Clearly something's not working. If this is an issue, what do I do to get around it and get back to android? How can I make the phone work again? I've flashed and reflashed stuff before but why is it seemingly busted now?
Help....anyone?
(FYI Since I have no phone, replies might be very sparse throughout the day because I can't actually check this thread and have to now go to work.)
Talnoy said:
Hey guys,
So this morning I stupidly tried to update to 4.4.4 since the phone said it has an update available. I was rooted running a few xposed modules, so I did the update, everything was fine, then upon getting back into the OS system.ui kept crashing every 3 seconds.
"Okay, just go use your Nandroid back up and flash via TWRP like always" I thought. So I did exactly that - rebooted to recovery, and went to flash my backup and it just sat there at "writing system" and did nothing. Next I rebooted to recovery again and did a full wipe of the OS - userdata and all, then tried two different toolkits (Mac and PC) and THEY got stuck at the 'writing system' as well.
Now I'm trying to flash stock to get my damn phone working via fastboot, but when i use the command fastboot flash userdata userdata_64g.img I get my cmd window saying "target reported max download size of 536870912 bytes erasing 'userdata'..."
This has been displaying for about 25 minutes now and I don't know what to do... Do I just leave it? Clearly something's not working. If this is an issue, what do I do to get around it and get back to android? How can I make the phone work again? I've flashed and reflashed stuff before but why is it seemingly busted now?
Help....anyone?
(FYI Since I have no phone, replies might be very sparse throughout the day because I can't actually check this thread and have to now go to work.)
Click to expand...
Click to collapse
I would try to download another ROM like Cm m9 and see if that will boot.
Sent from my A0001 using Tapatalk
I'm not sure how these posts work, but I am currently trying to figure out how to return my phone to a stock rom using the fastboot method. I was rooted and my intention is to unroot it. I was on 10.3.3 or something similar when I did this process and I uninstalled all magisk modules. Magisk itself for some reason, did nothing when I tapped on complete uninstall, so I thought nothing of it, as I'm wiping my entire phone and replacing it with a new rom through the fastboot method. After getting my phone into fastboot and being recognized by my computer, I double clicked the flash all file and after a few minutes, it read finished. But after unplugging my phone the phone went into the unlocked bootloader warning screen and rebooted to the oneplus logo and repeated. I am now back on fastboot mode and trying to figure out what to do. Anyone, please let me know what I can do to fix this!
Edit: I've tried reflashing another version of the ROM and it gave me a getvar variable not found error and I tried again this time with target didn't report max download size error: failed to identify current slot
Edit: I was able to wipe using recovery mode and retry but it seems that the fastboot method runs fine on the computer but leads to a bootloop on my phone... what should I do! I'm panicking!
Edit: I watched this video:
and I'm wondering if this MSM Tool would be viable. I really hope to have a response soon, if anyone could tell me anything I would greatly appreciate it.
LAST EDIT: I FIXED IT WITH THE VIDEO
Thanks