Related
Hey!
A friend of mine recently got her S2 bricked due to a faulty OTA update. She was prompted to install ICS, even though the network operator's branded version is not to be released for another week or so (2 weeks after the stock release).
Now the device won't start, and customer support says she needs to hand it over to reset the phone. Although this fixes the phone, she would like to keep her pictures etc. that is saved in the phones internal memory.
Is it possible to mount the /data partition (or /user or whatever) to a Windows PC, and recover the files? I do believe the phone can boot in recovery, and I am moderately experienced with using ADB.
Optionally, is it possible to "abort" the update, and reset the phone to it's previous state? I was thinking to wipe the cache partition, but i'd love your input on this matter!
--excubated
You could try flashing a GB rom via Odin. Or if you can, flash CWM recovery and mount the internal card (its sd_card, I think). Otherwise, I haven't a clue.
Sent from my GT-I9100 using XDA
Try Recuva
jje
JJEgan said:
Try Recuva
jje
Click to expand...
Click to collapse
Recuva is for deleted files (which also doesn't work too well on flash memory).
If she's got a custom recovery like ClockworkMod, skip to step 2.
Step. 1) download and install ClockworkMod recovery onto the device.
Step. 2) boot into CWM.
Step. 3) Go to Mounts and Storage.
Step. 4) Select Mount USB Storage.
Step. 5) Download (the .zip version) and extract the Android SDK.
Step. 6) Open a command prompt (CTRL+R, type cmd, hit enter).
Step. 7) CD to where ever you extracted to the SDK, like say C:\Android_SDK
Step. 8) CD to \platform-tools
Step. 9) In the command prompt, enter:
adb pull /sdcard/DCIM DCIM\
That should pull the camera folder. If there's photos outside that folder, try adb pull /sdcard SDCARD\
If you're looking to delete the photos, go back into Mounts and Storage, and hit format /sdcard.
But, if you can, as stated above, try flashing to a Gingerbread ROM and copying over like normal. A lot less hassle than the above.
screamworks.
Try It
excubated said:
Hey!
A friend of mine recently got her S2 bricked due to a faulty OTA update. She was prompted to install ICS, even though the network operator's branded version is not to be released for another week or so (2 weeks after the stock release).
Now the device won't start, and customer support says she needs to hand it over to reset the phone. Although this fixes the phone, she would like to keep her pictures etc. that is saved in the phones internal memory.
Is it possible to mount the /data partition (or /user or whatever) to a Windows PC, and recover the files? I do believe the phone can boot in recovery, and I am moderately experienced with using ADB.
Optionally, is it possible to "abort" the update, and reset the phone to it's previous state? I was thinking to wipe the cache partition, but i'd love your input on this matter!
--excubated
Click to expand...
Click to collapse
try using different ROM of any other country but of same Model no. (e.g. GT-I9100) in the downloading mode throug ODIN3. And formatting Cache partition will not change anything, but speed up the phone. firmware up gradation will not wipe your phone internal memory.
Hope it works for you....
Thanks for your answers so far, but I do believe flashing over any recovery or firmware will void the warranty on the device? She's not very eager to venture into the realm of warrantylessness, unfortunately ..
If whe was, she'd have had the MIUI ICS experience from the day it was launched Need to keep everything stock, and if there is no way to retrieve the files without voiding the warranty, she'd rather send it in and lose all her data..
screamworks said:
adb pull /sdcard/DCIM DCIM\
Click to expand...
Click to collapse
Can't I enter the normal recovery's terminal with adb shell? From there I mean to remember it is possible to mount and pull whatever I want..
Even without installing a custom recovery (CMW), the SGSII will allow you to go in to either Download Mode or Recovery mode. And I believe you should be able enter either mode even if the phone isn't booting up successfully (from a failed upgrade).
To enter recovery mode, you press and hold the Up Volume, Home Key and Power buttons.
To enter Download mode, you press and hold the Down Volume, Home Key and Power buttons.
You should be able to find the latest official/stock Gingerbread ROM in the forums here, and then you use Odin to install the GB ROM (from Download mode). This won't increase the count of "unofficial" Roms on the phone and shouldn't void the warranty.
While Odin is often referred to as a means to flash a custom ROM, it's not limited to only that. And the same for recovery mode. Most posts reference the CMW recovery that allows you to change to custom kernels and update "unofficial" packages on a rooted phone.
But you should still be able to revert back to a GB-based ROM and not void any warranty.
[if you boot the phone in to the official Samsung Download mode, it will display a message on the screen about the number of non-Samsung ROMs have been installed on the phone, and you should not see any number, or maybe "Zero"... I can't check to be sure because I forgot my phone in the office when leaving work today After you downgrade to GB, you can verify that the number is still blank or "Zero" by going back in to Download mode after you're sure the GB install was successful (it's not destructive to go in to Download mode just to view the counter. just power it off (as long as you're in the middle of pushing code to the phone ) and then reboot]
I'm not as experienced as a lot of the folks on the site, but everything I've outlined above I've done at least a few times on my phone (to custom ROMs, back to official, even resetting/clearing the "counter", and I've always been able to recovery from a "bad install").
I hope that helps,
Hey,
I am currently trying to help my best friends dad out. He dropped his GS2 during his holiday. Now the lcd is dead. The digitizer is not broken and seems to be working, as I get a feedback from the lockscreen when I tap on it, but I am having a small suspicion, that one half of the digitizer doesn't work anymore. The phone has a pin lock screen, it is not rooted and developer options are not turned on.
Is there any way to get access to the internal storage, and recover files from there? (He wants the pictures back he made on holiday )
Btw: I haven't owned any Samsung smartphone yet and I don't know how the recovery stuff works there so if there is a solution for this problem I would really appreciate a step by step tutorial. I have knowledge about rooting, flashing and stuff, so if it would be a solution to root the phone, I could do that, as my best friends dad doesn't want to repair the device anyways.
Greetings
Bl4ckX
Nobody any idea? :/
Sent from my HTC One X using XDA Premium 4 mobile app
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
GoogleFap said:
I read the wonderful "Don't Panic" sticky, but I think I need a more drastic fix.
SHORT VERSION:
TWRP keeps saying, "Unable to mount /sdcard", and "unable to mount internal storage". I can't boot past the HTC screen, and my attempts to flash a ROM have failed due to those errors.
LONG VERSION:
I tried using TWRP 2.2.1 and Cyanogenmod 10 today, my first time flashing a custom ROM.
My phone (HTC EVO 4G LTE) was already rooted using the plain ol' HTC bootloader unlocking method.
I booted into recovery and performed a backup first. That appeared to go okay, and verified a backup existed on my external SD card.
I booted back into the OS and used ROM Toolbox to download the ROM and gapps thingy, wiped the cache and dalvik's cache. The phone rebooted and started wiping the cache and stuff. I went away for a bit.
When I came back thirty or so minutes later, the phone was all black. No lights at all despite being plugged into the AC adapter.
I came back about thirty minutes after that, and the same thing. I rebooted. The phone went to the HTC screen and then blacked out again. I rebooted into recovery. I figured the ROM didn't get flashed right, so I went to flash it again. I used the file manager in TWRP and saw that the directories /sdcard /sdcard2 and /sd-ext were completely empty, except /sdcard had a TWRP directory, which was empty. I didn't see any of my storage!
I set up ADB on my Mac and tried mounting my sdcard. No dice. I tried using fastboot to flash a ROM. Everytime I tried to do that, I got an error in TWRP, "unable to mount /sdcard", "unable to mount internal storage". I tried using fastboot to flash the .zip on my Mac, and tried using "adb put" to move the .zip to the phone and install from there. Same result.
Any ideas?
Click to expand...
Click to collapse
this seem to becoming a more frequent problem maybe something TWRP is responsible for i came to this same obstacle when trying to flash a new rom like a week ago. i tried all the nifty moves i could but no luck even went to sprint looking for answers ultimately i was forced to format (with windows) both internal and external SD. end result. yep u got it i lost everything almost 26gigs of music and files i had backed up no where else. so i formatted (heart broken) got over it now i back up files daily on my laptop thats the only way ive come to see out of this one. but check around forums a solution might work for i saw a couple didnt work for me tho.
JB ROMs rewrites the addresses of your SD cards, good chance the internal is corrupted. Boot to recovery and go to mount/mount USB storage, if you have windows then as soon as you plug it in windows will tell you to reformat, if you have Mac or Linux manually reformat the card
Thanks for the replies, guys.
Tried reformatting, but that didn't seem to help. On #twrp on freenode, they said it looked from my recovery.log that the internal and sdcard storage is hosed, and the maintainer of TWRP said to RUU back to stock. SIGH. . . .
So, since I don't have Windows at work, going to try these at home tonight:
(Great. Was trying to post links, but wasn't allowed. Suffice it to say, I was going to post my recovery.log link and the links to the instructions I am going to follow to RUU back to stock.)
Well that sucks, I'm lucky that I haven't hosed my emmc yet. I can't decide whether to stay on aosp or not, must have flashed back and forth a million times by now
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
GoogleFap said:
Argh!
I have tried every RUU scenario I can find, and remain unable to mount my sdcard or my internal storage, have no ROM, am contemplating getting drunk. Anyone have any other ideas?
Anyone know if Sprint will fix this, or should I just cash in on my phone replacement plan?
I'd like to know what happened to mess this up so I can avoid it next time. What must have happened for my internal storage to not only be wiped -- I think I get that part -- but why can't it be mounted???? I don't get it.
Click to expand...
Click to collapse
Did you ever find a solution to this? I'm in the same boat...
llaen said:
Did you ever find a solution to this? I'm in the same boat...
Click to expand...
Click to collapse
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I had backed up my sdcard so I didn't really care about not losing it. I think the problem was at least partially caused by having it encrypted.
I ended up flashing to stock and it let me format the sdcard from within the phone - that did it.
Thanks for the suggestion.
onefasttreopro said:
If you're able to access bootloader, you can recover from this issue(been there myself). You'll end up losing all your ad card stuff but you'll be back up and running. Download the newly released 3.15.651.16 RUU, get into bootloader on phone, set it to fastboot, connect to computer, relock your bootloader (it can be unlocked after ruu app), run the RUU, and you should be back and can reunlock and install custom Roms etc.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
This just advice just saved my life. I thought for sure I bricked my phone, and right before memorial day weekend toooo! I did run into issue with the latest Lollipop RUU. I had to resort to using the old Kit Kat RUU I had saved to my computer from before. It worked like a charm.
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
theskyisoutthere said:
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
Click to expand...
Click to collapse
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
attempted to unroot
aicjofs said:
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
Click to expand...
Click to collapse
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
theskyisoutthere said:
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
Click to expand...
Click to collapse
If you have touch in Android install this https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager push your backup and use the program to make the open recovery script for you.
no touch anywhere. and no wifi!
Like I said no wifi and no touch at all anywhere So going online Iis a no go. I can use a mouse on the android system. Also I beleve my backup firmware is what caused the issue with the touch. Again this is a nabi 2 so now its been reset no file manager either access a apk from the sdcard if I could get the apk for that.
update
browser loaded the twrpmanager apk with that installed stock image now wifi works but no touch still what am I missing with the touch? Trying the stock update to see if that corrects anything I doubt it though
over post sorry
I know I am over posting on my own thread... sorry about that.
Had a thought. Since I am not great at describing what I need to accomplish here, try to work with me on this.
I need to just complete start over GO FOR BROKE format and push out the rom with adb How can I get started to do this and what do I need?
I feel that something in the touch input is not working based on some part of the rom is hosed. even tried the original recovery gives that android error icon thingy and I see nothing till she restarts nothing changes.
OK if you want to go for broke... You have to have an external SD card for this. TWRP must be installed
Hook Nabi up via USB can be in Android or TWRP
1) Download this: Nabi 2 stock
2) Unzip the NABI2STOCK.zip
3) Go here: http://forum.xda-developers.com/wiki/Fuhu_nabi_2
4) Grab either the 2.0.5 or 2.1.27 stock rom
5) Put the downloaded ROM zip in the "install" folder that was made in #2. Dont unzip, just download it straight to the install folder
6) Run 205.bat or 2127.bat depending on which ROM you chose.
The script will extract the ROM from the zip, copy the stock ROM to your external SD card, create an openrecoveryscript that will format system, format data, and restore Boot and System partition. Data will be left blank. This erases everything, except hidden partitions and recovery partition.
downloading will update when its done
downloading now will update when I run it. I hope things fixes it. as I have hosed it so far.
I get an error
I get an error
mkdir: can't create directory /external_sd card/twrp/backups/015d2a50211c1a19/abcdstock or something like says directory does not exist odd error it went thought its cycle and exited after that.
I do have an external sd card in it and it is working. did not know if that was an sd card error or what
no touch still
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
theskyisoutthere said:
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
Click to expand...
Click to collapse
It seems hardware now, but it is odd that touch went out when you were doing things to it. Still under warranty? Have you taken it apart and seen if anything is wrong?
I explained in the help thread that I can't boot up anymore into the stock image. So, I followed some instructions and managed to unlock the device. Here are some questions I have:
1) How do I tell what the current image/build is of the phone (like 4.05 etc)? This is all it shows me in bootloader:
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20, 2012, 17:40:22
2) I noticed that some of the images are called RUU's that come as a .exe file. In order to update using these, do I just need to have the phone in fastboot mode in the bootloader? Or does it need to be booted all the way into an existing OS?
3) Is there a stock version of KitKat or Jelly Bean that I can get for the Rezound? I see so many different custom ones but for now I'd just like to try the stock if it's possible.
Thanks!
SuperAwesome78 said:
I explained in the help thread that I can't boot up anymore into the stock image. So, I followed some instructions and managed to unlock the device. Here are some questions I have:
1) How do I tell what the current image/build is of the phone (like 4.05 etc)? This is all it shows me in bootloader:
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20, 2012, 17:40:22
2) I noticed that some of the images are called RUU's that come as a .exe file. In order to update using these, do I just need to have the phone in fastboot mode in the bootloader? Or does it need to be booted all the way into an existing OS?
3) Is there a stock version of KitKat or Jelly Bean that I can get for the Rezound? I see so many different custom ones but for now I'd just like to try the stock if it's possible.
Thanks!
Click to expand...
Click to collapse
You are welcome to continue this discussion here, or you can continue in the help thread...
1) They key here, without booting up, is in the HBOOT and RADIO version. 2.28 and 123r/124r are indicative of the most current OTA, 4.5.605.14... http://forum.xda-developers.com/wiki/HTC_Rezound
2) "RUU" is kind of a misnomer and carry over from older HTC products... basically there are two flavors of stock ROM, once is an EXE file, it is run from your PC and the phone is placed in download mode and the entire phone is re-imaged (these are 'real' RUU's), the ZIP files that are typically renamed to PH98img.zip and placed on the SD card are often called RUU's, but are really just signed ROM images that the stock bootloader and recovery will process, similar to just flashing a ROM but may also include radios and hboot, this can also be simply updates to previous official ROMs as well. These are all done from the HBOOT or download mode, the phone does not need to be booted.
3) This one is very tricky... the final version of the stock ROM was 4.5.605.14 and was ICS, the problem is it was never released (or even leaked) as a full ZIP or RUU from HTC or Verizon, only in an OTA update. The tricky part is that you are already on the current firmware, so you can't use an older stock ROM and downgrade, the phone won't allow it, and you can't restore it to pure stock at it's current level.
I am assuming you cannot boot the device? Then you are in a precarious position, you will need to unlock the device via htcdev.com to troubleshoot further.
acejavelin said:
3) This one is very tricky... the final version of the stock ROM was 4.5.605.14 and was ICS, the problem is it was never released (or even leaked) as a full ZIP or RUU from HTC or Verizon, only in an OTA update. The tricky part is that you are already on the current firmware, so you can't use an older stock ROM and downgrade, the phone won't allow it, and you can't restore it to pure stock at it's current level.
I am assuming you cannot boot the device? Then you are in a precarious position, you will need to unlock the device via htcdev.com to troubleshoot further.
Click to expand...
Click to collapse
Right, I cannot boot it, but I have unlocked it using the instructions from htcdev.com. It is still set to S-ON though. Is there a unmodified Jelly Bean or KitKat ROM that will work with the Rezound?
SuperAwesome78 said:
Right, I cannot boot it, but I have unlocked it using the instructions from htcdev.com. It is still set to S-ON though. Is there a unmodified Jelly Bean or KitKat ROM that will work with the Rezound?
Click to expand...
Click to collapse
JellyBean was never a "stock" operating system for this device, nor was KitKat. Ice Cream Sandwich is the latest stock ROM available.
If you wish to try to restore this device to "almost" stock, it is possible... Download this ROM, it is essentially the latest stock ROM with root added and nothing taken away, and TWRP 2.8.0.1F recovery and the CleanWipe script from this thread.
Once you get this, copy the ROM and CleanWipe script to your SD card and put it back into the device, and copy the openrecovery-twrp-2.8.0.1F-vigor.img to the same directory as fastboot/adb. Remove the battery and disconnect the USB cable, reinsert the battery and power up into Hboot, then start Fastboot and connect the USB cable, then enter the command:
fastboot boot openrecovery-twrp-2.8.0.1F-vigor.img
After a few seconds the device should boot into TWRP, go to Wipes menu and select everything except the external SD card (external storage, micro SD, or whatever it is labeled), and wipe it, do it once more time (note that the entry names may have changed or switched order). Now go back Home and select Install and navigate to the CleanWipe ZIP and install it, then go back Home, then press Install and select the ROM ZIP and Install. Do NOT wipe cache/dalvik or factor reset, just reboot and remove the USB cable, it should boot up. You will be on a completely stock ROM, except it is rooted.
If this doesn't work, we have one more option, going to a ROM that doesn't use the internal storage... some early JellyBean ROMs have the internal and external storage swapped, we can sometimes use this to our advantage to get the phone booted to perform S-OFF and RUU the device if needed.
acejavelin said:
JellyBean was never a "stock" operating system for this device, nor was KitKat. Ice Cream Sandwich is the latest stock ROM available.
If you wish to try to restore this device to "almost" stock, it is possible... Download this ROM, it is essentially the latest stock ROM with root added and nothing taken away, and TWRP 2.8.0.1F recovery and the CleanWipe script from this thread.
Once you get this, copy the ROM and CleanWipe script to your SD card and put it back into the device, and copy the openrecovery-twrp-2.8.0.1F-vigor.img to the same directory as fastboot/adb. Remove the battery and disconnect the USB cable, reinsert the battery and power up into Hboot, then start Fastboot and connect the USB cable, then enter the command:
fastboot boot openrecovery-twrp-2.8.0.1F-vigor.img
After a few seconds the device should boot into TWRP, go to Wipes menu and select everything except the external SD card (external storage, micro SD, or whatever it is labeled), and wipe it, do it once more time (note that the entry names may have changed or switched order). Now go back Home and select Install and navigate to the CleanWipe ZIP and install it, then go back Home, then press Install and select the ROM ZIP and Install. Do NOT wipe cache/dalvik or factor reset, just reboot and remove the USB cable, it should boot up. You will be on a completely stock ROM, except it is rooted.
If this doesn't work, we have one more option, going to a ROM that doesn't use the internal storage... some early JellyBean ROMs have the internal and external storage swapped, we can sometimes use this to our advantage to get the phone booted to perform S-OFF and RUU the device if needed.
Click to expand...
Click to collapse
Thanks Ace for the great info! I will try that. I realize that ICS is the latest ROM from HTC, but I guess what I meant was the closest to what Jelly Bean or Kitkat would look like straight from Google, like on a Nexus device. I see other developers here have made their own custom versions of Kitkat and Jelly Bean that work on the Rezound, but those are all modified from what came from Google.
SuperAwesome78 said:
Thanks Ace for the great info! I will try that. I realize that ICS is the latest ROM from HTC, but I guess what I meant was the closest to what Jelly Bean or Kitkat would look like straight from Google, like on a Nexus device. I see other developers here have made their own custom versions of Kitkat and Jelly Bean that work on the Rezound, but those are all modified from what came from Google.
Click to expand...
Click to collapse
Gotcha... The closest you would find then are Evervolv or Plain-Andy.. You will also need a Gapps package, I recommend PA Gapps mini modular in most cases. You flash ROM then Gapps package.
acejavelin said:
JellyBean was never a "stock" operating system for this device, nor was KitKat. Ice Cream Sandwich is the latest stock ROM available.
If you wish to try to restore this device to "almost" stock, it is possible... Download this ROM, it is essentially the latest stock ROM with root added and nothing taken away, and TWRP 2.8.0.1F recovery and the CleanWipe script from this thread.
Once you get this, copy the ROM and CleanWipe script to your SD card and put it back into the device, and copy the openrecovery-twrp-2.8.0.1F-vigor.img to the same directory as fastboot/adb. Remove the battery and disconnect the USB cable, reinsert the battery and power up into Hboot, then start Fastboot and connect the USB cable, then enter the command:
fastboot boot openrecovery-twrp-2.8.0.1F-vigor.img
After a few seconds the device should boot into TWRP, go to Wipes menu and select everything except the external SD card (external storage, micro SD, or whatever it is labeled), and wipe it, do it once more time (note that the entry names may have changed or switched order). Now go back Home and select Install and navigate to the CleanWipe ZIP and install it, then go back Home, then press Install and select the ROM ZIP and Install. Do NOT wipe cache/dalvik or factor reset, just reboot and remove the USB cable, it should boot up. You will be on a completely stock ROM, except it is rooted.
If this doesn't work, we have one more option, going to a ROM that doesn't use the internal storage... some early JellyBean ROMs have the internal and external storage swapped, we can sometimes use this to our advantage to get the phone booted to perform S-OFF and RUU the device if needed.
Click to expand...
Click to collapse
I just did send the twrp image to the phone and booted to it. I ran the wipes and they failed, it has a bunch of lines that say it's unable to mount /cache /data /cache /system /emmc /system. Also says failed to wipe delvik and on the second line in yellow it says Kernel does not have support for reading SELinux contexts. Did I do something wrong?
SuperAwesome78 said:
I just did send the twrp image to the phone and booted to it. I ran the wipes and they failed, it has a bunch of lines that say it's unable to mount /cache /data /cache /system /emmc /system. Also says failed to wipe delvik and on the second line in yellow it says Kernel does not have support for reading SELinux contexts. Did I do something wrong?
Click to expand...
Click to collapse
No, you did nothing wrong... The SELinux message is not relevant in this case, it's just reporting a status, not an error.
Unfortunately it appears that no partition can be mounted at all, so the partition information table or the internal storage chip is bad.
You can try booting up TWRP, going to Wipes, Advanced, and tick each partition, one at a time, and then click "Repair or Change File System" and select "Repair" and if that fails try "Change File System"... most of the partitions should be Ext4 except internal and external storage, they are FAT32. To be honest though, I have not seen this work for anyone who has this problem yet on the Rezound, but it has worked wonders on other devices so it is worth a try.
Being S-ON there is no other remedy for this that you can do. If you were S-OFF we could try a full RUU which writes a new PIT file, but the paradox is we cannot achieve S-OFF without being able to boot the device fully.
I have seen several Rezound's in the past few months have this happen... not sure if they storage chip is just getting old and it's seen it's limit of reads/writes or some situation is happening, but you are not alone.
It is 9 days from it's third birthday, it is getting old, that's like 90 in human years.
acejavelin said:
No, you did nothing wrong... The SELinux message is not relevant in this case, it's just reporting a status, not an error.
Unfortunately it appears that no partition can be mounted at all, so the partition information table or the internal storage chip is bad.
You can try booting up TWRP, going to Wipes, Advanced, and tick each partition, one at a time, and then click "Repair or Change File System" and select "Repair" and if that fails try "Change File System"... most of the partitions should be Ext4 except internal and external storage, they are FAT32. To be honest though, I have not seen this work for anyone who has this problem yet on the Rezound, it has worked wonders on other devices.
Being S-ON there is no other remedy for this that you can do. If you were S-OFF we could try a full RUU which writes a new PIT file, but the paradox is we cannot achieve S-OFF without being able to boot the device fully.
I have seen several Rezound's in the past few months have this happen... not sure if they storage chip is just getting old and it's seen it's limit of reads/writes or some situation is happening, but you are not alone.
It is 9 days from it's third birthday, it is getting old, that's like 90 in human years.
Click to expand...
Click to collapse
Tried the repairs and change file system, and it still gave the mount errors. Is the internal storage on the main board via a connector or is it hardwired in? I was thinking maybe I could take it apart and re-seat the storage it if it uses a connector.
SuperAwesome78 said:
Tried the repairs and change file system, and it still gave the mount errors. Is the internal storage on the main board via a connector or is it hardwired in? I was thinking maybe I could take it apart and re-seat the storage it if it uses a connector.
Click to expand...
Click to collapse
It's soldered, part of an AIO chip... JTAG is the only real possibility at this point, and that's still a 50/50 gamble.
Dang... Rezounds are starting to drop like flies :/
pball52998 said:
Dang... Rezounds are starting to drop like flies :/
Click to expand...
Click to collapse
Yeah... I think this is the 4th, maybe 5th, in last 2 months that I've seen in the forums, exact same issue with every one. [emoji24]
acejavelin said:
Yeah... I think this is the 4th, maybe 5th, in last 2 months that I've seen in the forums, exact same issue with every one. [emoji24]
Click to expand...
Click to collapse
Yeah over the past few months they've just been dying. I had to retire mine because the charging port and battery prongs broke.. It just sits on my counter in my room.