Hello,
I made a terrible misstake while trying to figure out how to flash a custom rom to this device, I followed a video online where a guy flashed some sprint firmware to his device and it allowed him to write to the protected partitions on the device.
Now obviously once I realised I had flashed the wrong firmware I knew I had screwed up my phone, (I was unable to take a backup because it wouldn't let me write to the SD card or any partition at all)
I flashed the firmware from a USB OTG cable but did not have a big enough USB for the backup.
Now at this stage the device was stuck inside a bootloop on the HTC screen, I attempted to flash Cyanogenmod 11 but because of the protected partitions I can't do this.
I've tried to find RUU for this English HTC one mini but when I try and flash the RUU I'm getting errors that are not documented.
I was able to flash Cyanogenmod via ADB but I just get stuck on the Cyanogenmod boot screen due to the corrupt firmware I guess.
Is anyone able to provide me with a way that I can reflash the firmware and Rom back to stock? Obviously I cannot do this via recovery because of the protected partitions, I wish I could make these writable!! I love this phone so much and now it's just a brick.
Kind regards
Kyle.
Related
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Dissentire77 said:
So tonight I began the process of unlocking my phone and installing a custom ROM. I unlocked my phone successfully with the toolkit and was able to get into recovery and begin flashing my first ROM (Cyangogen 10 most recent nightly along with the Gapps). However on my first reboot after flashing the room, I started to realize something was awry when after 20-30 minutes it was still on a boot screen. I proceeded to try and reflash the ROM 2 more times with no real change in outcome. Whenever I tried booting out of recovery I would get a warning stopping me saying that no OS was installed, despite having clearly flashed a new ROM. Okay, so as a last ditch effort I went into the bootloader mode and enabled fastboot so that I could try the RUU - which of course failed despite 2-3 attempts at using the utility. After the RUU failures I also noticed that my SD card would no longer mount unless I manually formatted it - which I finally gave in to and was able to load another custom rom (Jellybam this time) which also would get stuck on the boot screen despite successfully flashing. So now I'm basically stuck in a limbo land where no custom ROM will boot into the OS and the RUU to take me back to stock has failed. Any suggestions on how to get out of this? (I've read in other places that you can use fastboot to flash files in the bootloader but my attempts at doings this have also been unsuccessful - if this is the route to go can anyone give me some specific instructions on how to do it?)
Thanks in advance guys.
Phone Specifics - AT&T HTC One X, 16gb running the 2.2 firmware on Android 4.04 before I got into all this nonsense.
Click to expand...
Click to collapse
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
WhatTheAndroid? said:
You know you also have to relock the bootloader before you RUU Right?
and if your on hboot 1.14 you have to flash the boot img separately from the zip(in the folder you put fastboot,adb,etc.)
Click to expand...
Click to collapse
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Dissentire77 said:
I was forgetting to relock the bootloader, thanks man. Was able to go back to stock, restart the process and am now rocking CM10. This is why I love XDA.
Click to expand...
Click to collapse
Sounds like a thanks button click is on order for WhatTheAndroids post to you
ViperXL 2.4.0 w/ElementalX 3.1 kernel
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img
Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.
Hello,
I don't know if this is the correct place to write this, but if not please advise me as I'm new in this fields.
Some time ago I decided to root my Jelly bean HTC One S (S4). To do that I used the HTCDEV method and follow this post step-by-step witch I thank to all developers involved: http://forum.xda-developers.com/showthread.php?t=1583427
It worked well and the only thing I done different was installing TWRP 2.6.3 recovery instead CWM.
Lately I decide to install a custom kernel (Bulletproof 1.4), essentially because I wanted to fix refresh rate/crash of HDMI output among other good things that this kernel provide. Here started my problems. I download the zip file, file copy it to phone memory through usb and then restart the phone to bootloader, enter in recovery and flash it with TWRP. After that my phone don't boot and was stuck in bootloop.
As I previous made a backup of my system through TWRP I thought it would be enough to restore it, but then my sdcard was unreachable and I found no way to access it. At this point I had also the copy of the backup I done with recovery in my laptop. With the phone in bootloader screen (witch I'm still able to reach) I can see the phone in devices although not accessible. So the only way I found to fix my phone was format the sdcard though windows copy the backup to sdcard via and then make make a restore via TWRP. It somehow worked and I was able to back to system.
I checked the kernel and it changed to bulletproof 1.4+. Nevertheless the performance of the phone decreased at the point that he almost freezes sometimes (no restarts) and also can't acess phone storage via usb in windows. When I plug it to computer it beeps as a normal device inserted and htc one s device appears but I can't see any of the contents inside it.
After some days, I decided to install Busybox app and somehow that app makes some miracle and the phone got something better in terms of performance, but never as it was before the installation of the kernell. Even know the phone has some freezes, but Can someone help me recovering the normal phone performance?
more info:
I'm factory unlocked
HTC ONE S (S4)
HBoot 2.15
S-ON
RADIO 1.11.50.05.28
TWRP 2.6.3
Thanks a lot in advance and sorry my bad English.
You have you're stock rom?
http://forum.xda-developers.com/showthread.php?t=2082451
Download rom. Open it.
Copy "boot.img" to computer. (Because you're S-ON)
1.save you're data from phone to PC.
2.put the rom from above link in SD CARD
2.reboot bootloader
3.factory reset
4.wipe all except SD CARD.
5.flash rom from recovery
6.reboot bootloader
7.Fasboot USB will apear when you conect to PC
8."Fastboot flash boot boot.img" with command promt. (without this you're phone wont start)
First of all thanks for your quick reply and sorry the later answer...
I have some backups of all the system done with TWRP made immediately after rooting the phone and before flash the custom kernel. One of those backups I used to help me bring phone again to life however in the end with performance and usb problems I mention before. Can I use this? If yes should I take some specific step? (I watched the files of the TWRP backup and they are all .win and .md5, is this normal? can I use it as you mention?)
If I use some of the rom you point me (or eventually my backup) in the end flash boot.img I will be replacing the custom kernel I installed right? If so and if everything goes right I will still be rooted but with stock kernel right? I watched the roms available from the link you gave me how do I choose from them, I suppose will be some of the Europe, probably Ville_Europe_3.16.401.8_OTA_UPDATE_Stock_Rooted_ODEX, however how do I know if those match with my radio/Hboot version version which are 1.11.50.05.28 /HBoot 2.15.
I know I probably did some stupid questions, but as you may noticed I'm a lot "green" here.
First use backup.
OTA is an update. Find the one before that. Must be the one compatible with the region that you live.
http://www.androidfilehost.com/?w=files&flid=2484
I choose LITE. Then OTA:
http://www.androidfilehost.com/?w=files&flid=2489
Don't forget!
comand promt : fastboot flash boot boot.img
Thanks a lot man for the help, it worked...
Had some issues with the OTA installation as in the first try phone stuck on HTC boot screen, but on second try it worked, thanks a lot!!
Have on more question, if possible, now I'm again on stock kernel which as mhl hdmi problems (phone outputs 1080p 24hz which makes it slow and some times freezes)... so would you recommend me some custom kernel? just want to fix that. The buletproof 1.4 was ok in that point but last time I flashed it phone enters in bootloop and the rest you already know.
Can you tell the correct steeps to install a custom kernel, should I flash it through recovery, clear all cache in recovery and then flash the boot.img file of the kernel via fastboot? or should I use some market app like "kernel manager" or "flash image gui"
Hi, is there any ROM's like the ones you point me already with Heartbleed vulnerability fix from HTC? I mean a stock, odex, rooted rom's made after the update release from HTC? With those ones how can I apply the fix?
thanks in advance.
HD or full HD ask's alot from a phone. I guess that is the problem...
Hi,
About my last post (the heartbleed issue), I don't know If it was the best solution but still on 4.1.1 and used the patch from http://forum.xda-developers.com/showthread.php?p=51830870, tested it with the heartbleed detector and look like it's ok now.
After that I flashed again the bulletproof 1.4 now with Flash Image Gui, not via recovery (my previous try I used twrp, but as I'm s-on probably boot.img wasn't flashed well or flashed at all, and probably from there started my problems). After this try phone runs good and fluid most of the time. However I noticed that when use a browser (chrome/dolphin or even the stock browser) or turn on gps and mobile data after been some time without connection he becomes very slow (not all times but somehow frequent).
After that I flash the last bulletproof 2.1 (again with Flash Image Gui), thinking it might be due to the fact that version 1.4 still have some problems.
After installation and in the beginning the system was fluid, but then again even with this version sometimes lags a lot when browsing. Do you know what may cause that?
About hdmi with this kernel, if the phone isn't passing for a period o lag I mention before it runs very fluid in 720p 60hz.
thanks advance for for your time!
I've had an LG E970 running the stock ROM for about a year and decided to try out CM. I'm new to this, but I did some research and went ahead and rooted the phone, and then installed ClockworkMod. That went smoothly, so I tried to install CM through CWM and it appeared to work until it finished booting up and led me to the encryption PIN screen. My PIN from the stock ROM won't open it. CWM can't mount the encrypted data partition to wipe it.
I can boot to CWM or the CM encryption screen. I tried doing a restore on CWM but keeping getting MD5 errors. I haven't had any luck finding the stock ROM anywhere online, I tried an LG tool to get the kdz but it kept giving me error messages when I entered the serial number. I used Titanium to backup everything beforehand, but I can't figure out how to use the files to restore the old ROM. I can put files onto the SD card with my computer, but don't know if that'll be any help. I tried using the ADK to connect to the phone in fastboot, but the phone doesn't show up when I enter the fastboot devices command. Will an older version of CM thats based on the same version of Android the phone was encrypted with be able to open the data? I've tried researching this but everything I've found suggests going about it in different ways and nothing I've tried has worked.
If anybody could give me any help I'd appreciate it.
You may wish to refer to [GUIDE][E970]Using LG Flash Tool To Flash .tot Files {Alternate To LGNPST}[WIP]
Of note to you is Post #8 If you still have issues, you can post on that thread as well.
I followed that guide, but got stuck because the LG Flashtool is identifying my phone as a Nexus 4 and not allowing me to install the E970 files. I think the phone ID changed because the CM version I downloaded was converted from the Nexus ROM. I was able to flash an earlier version, but it had the same problem. Do you have any suggestings for a ROM with the correct phone ID? Is there any other ROM that might be able to decrypt the stock Android encrypted data?
Thanks!
I fixed it!
By plugging my SD card into the computer, I was able to add new ROMs to it and flash them in CWM. I was trying out different ROMs, hoping one would show up as the right phone model in LG Flashtool, and I found one for LG Official Kitkat 4.4.2 Stock. It was able to decrypt the data and now my phone is usable again. I'll revert to the stock recovery, wipe the phone (including encryption) and then start over with CM.
Here's a link to the ROM in case anybody else has this problem later:
http://forum.xda-developers.com/showthread.php?t=2771440 - Thread
http://level99.nighthorsemedia.com/geeb/LG-KK-4.4.2-Fixed.zip - Download Link
Thanks!
After literally two weeks of reading thread after thread attempting to understand this , I tried to go from a sense ROM to a GPE ROM and I tried to flash the GPE firmware following Digital high's instructions here..
Things did not work out as instructed I'm afraid and that is probably due to my not understanding enough....nevertheless following DH instructions left me with repeated flash failures. Finally the following flashes got me from firmware 5.0.1- the firmware I was already on- to this:
fastboot flash zip VZWm8LfirmwareTWRP.zip - success; followed by the same ' flush" flash - again, success:
then:
fastboot flash zip 5.1_6_firmware+hboot.zip - and again another "flush" flash with success
From the way I read it we are then to reboot to bootloader and proceed further with recovery flashing the rom, blah, blah.... , however, my little android guy is overlaid with a black screen (instead of white) and he is dead. I rebooted to recovery to see if I could flash the sinless GPE ROM which is my goal in the first place (yes I realize it is a 4.4.4 but NOTHING flashes in recovery now) but now I m out of ideas. I have no workable phone and I have to get my ass to a new job in the afternoon. Can anyone help with either finishing my goal to install the sinless ROM or restore back to the adrenaline ROM I was running? I don't want to restore as I am afraid I may have altered the firmware and thus brick if I do restore...PLEASE HELP!!!! PLEASE!
right now my phone is sitting on the charger on the dead android screen. i don' dare touch it. What should i do?
Update: I am flashing digital highs GPE_5.1-multi_dh_051215.zip and I am getting a bootloader remote 24 "parsing android info fail". Does anyone know what that means or how to fix?
Update again: Figured out this needs to be flashed in recovery and not fastboot. Now I have been booting for about five minutes now. Hope I'm not bootlooped. ....
Figured it out
Got it figured out.
Mods, could you please close the thread. thanks!
kerryh said:
Got it figured out.
Mods, could you please close the thread. thanks!
Click to expand...
Click to collapse
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
cntryby429 said:
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
Click to expand...
Click to collapse
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
kerryh said:
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
Click to expand...
Click to collapse
When compared to the steps I took to flash the 6/15 build as cleanly as I could manage, here's what jumps out to me as strange or unnecessary:
-I don't know what the '5.0.1 firmware' is but I suspect it's the same as the 'VZWm8Lfirmware.zip' you flashed next. I chose to run the 5.0.1 RUU and considered that as complete of verizon 5.0.1 firmware as there is.
-I don't think that superCID has been necessary for DHs GPE for some time. I don't know that it would necessarily cause a problem but I've never gone to superCID and have had no problems
-flashing DH's carrier-agnostic 5.1 firmware is stated as optional in his OP and I think DH himself admitted a little while back that it may actually be the cause of some folks' wi-fi issues
Regarding restoring old nandroids to a system with updated firmware, I can say that each time a new official software has been released, I've flashed tigerstown's firmware-only zips alongside whatever custom rom I was running at the time with no issues. This points to a trend of successfully running roms on top of newer firmwares without issues. I know of many 5.x roms saying that you must update firmware but I've never read about a 4.x rom having issues with 5.x firmware. I don't think there's much risk of flashing a custom rom (or restoring a nandroid) from recovery that doesn't match the firmware beyond a possible bootloop.