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.
Related
Here's what's happenning.
- Device was rooted using HTC unlock method with HB00t 1.5
- Was running Synergy Rom
- Wanted to get latest OTA from Sprint so I followed the steps from another thread :
http://forum.xda-developers.com/showthread.php?t=1447839&page=2- Went through steps and unlocked my device again
Used file from post #16
- Did my updates, unlocked device, booted back into HBoot
- Decided I would try the Infected Eternity Rom this time so I followed those steps as stated in their thread. Did a clean flash. Flashed Superwipe, flashed data ext optimizer tool, flashed eternity rom w/ 3.5 sense
- after message said installation was complete, i got error message when i went back to main menu in recovery:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
- device wouldn't boot once I rebooted from CWM. It would hang a the HTC white screen, then reboot again, keeps repeatedly doing this.
- Then I rebooted back in HBoot by pressing Vol Down and Power buttons. Went to recovery, flashed Synergy rom. Install was fine, still can't boot up device. Having the same issue. Device would hang at HTC white screen and continue to cycle on and off trying to reboot.
- Rebooted back to HBoot by pressing Vol Down and Power buttons. Went into recovery with CWM, restored my back up. Everything went fine except I got message:
sd-ext.img not found. Skipping restore /sd-ext.
As of right now, I can still boot into HBoot. I've tried reflashing Synergy rom again, but still nothing.
From my search, it says that based on my error message:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
It could be a HW or SW issue.
Phone is still under HTC warranty, if I need to return it, what do you say to support department?
Thank you.
Have you tried flashing through fast boot through a usb connection? I know the h boot 1.5 are tough to do when you need to change kernals which is what happens when you got to a 3.5 Rom. I had some trouble too if you open recovery through fast boot and do everything that way all should be good.
Edit: as long as you can get into recovery I think you'll be okay.
I can definitely still get into recovery and HBoot. So I would assume those are good things.
Read another thread suggesting to use TWRP instead of CWM.
Will try both flashing with fastboot from usb and twrp and see if that helps.....
If anyone else have other suggestions,
fastbook using android sdk...
it's never bricked unless it won't turn on.
next time, don't try to fix it if it aint broken.
Unlocking via htc will require you to follow the following. The kernel can't be written unless you follow the directions below which can cause the issue you stated.
http://forum.xda-developers.com/showthread.php?t=1239821
Just let us know what happens it is most likely just a kernal problem. Look up how to do the fast boot to make sure it works right. Fingers crossed.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
That's not a brick a brick is where you can't even get into hboot tho if your slick enough you could still fix a bricked phone lol
cobraboy85 said:
next time, don't try to fix it if it aint broken.
Click to expand...
Click to collapse
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
kyaj9 said:
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
Click to expand...
Click to collapse
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
you should give that set up a shot man. most reliable rom in my opinion.
k2buckley said:
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
The only back ups I have when I first rooted the device.
As long as formatting the SD card doesn't mean I am losing anything vital to the operation of the device, I would have no issues with having to put everything back on manually.
cobraboy85 said:
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
Click to expand...
Click to collapse
No it's the 3.5. I wanted to try the one with Sense 3.5.
For the good news!!! Finally got it to work. Backing up my apps with Ti Back up as I am writing this.
The only difference I did this time around was that after flashing Superwipe, I DID NOT flash the optimizer tool.
In all my other attempts, whether with TWRP or CWM, I was also flashing the optimizer after flashing Superwipe. Don't know if that was the actual cause or not with the install, but that was the ONLY step I did not do this time around.
From what I read, the optimizer is suppose to make the rom run faster because of the ext 4 partition. So my question now that I have up and running is will NOT having it flashed have any significant results?
On another thought, I did flash the optimzer as needed when I re-flashed Synergy. Does this carry over to the new rom or was I suppose to do again also for Eternity?
In any matter, thank you to all who helped. I will run Eternity for a week or so and see how stable it is first before trying anything else.
EDITED NOTE: Perhaps it should also be noted that I did download the latest build of Eternity also beforing getting it flashed and finally getting it running. Build 180. The file I couldn't get running was build 155.
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
kyaj9 said:
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
Click to expand...
Click to collapse
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
cobraboy85 said:
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
Click to expand...
Click to collapse
cobraboy85 said:
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
Click to expand...
Click to collapse
Making sure I wiped out everything was the first priority I took. I did re-download the rom just to be sure it was a good download also.
Can't seem to get 3.5 version working propperly, but I did get 3.0 version up and running. Have had it for a couple days now with no issues so just gonna stick with that. Wanted to try out the sense 3.5 first, but the fact that there's no 4g support for it yet means I am probably better off with just using the 3.0 Sense.
Thanks for your help....
mahmutmuratdemir said:
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
Click to expand...
Click to collapse
Not familar with Black Rose....but if I am not mistaken, isn't that just a HBoot for the Nexus 1?
yes it is made for nexus one to flash higher andrid versions but i think it can be used in some other models for partitioning internal memory
Sent from my Nexus One using XDA App
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.
Hi,
after crashing my phones display (in fact it was my girlfriend :cyclops I sent my HOX+ to HTC repair service to replace the display.
After finally getting it back today, all seemed perfect, my Custom ROM (AOKP 2.2.2) was reset - but I expected that. (cleared /data and /cache I guess) I thought OK directly upgrade to latest version of AOKP from maxwen, flashed new kernel from the zip first then tried to copy the rom to sd card via windows explorer - and there was the problem: it showed an 'SD Card' Link but now size/space and just empty. I first thought about stupid windows drivers etc. but I found out that was not the problem...
So I restored my nandroid backup I made before sending it to repair service via CWM. After the restore process finished I found that google play was crashing because the SD card was missing! I checked storage information and found that my internal storage now shows 56GB? I'm not sure how it behaved before, but I though the /sdcard partition is separated from the other space?
I then checked stock android explorer which just gives an error that storage is not available or so. then I checked es explorer and it just showed a broken link 'sd card' in /mnt/.
I restarted into CWM 6.0.2.7 and chose 'install zip from sdcard' and CWM was able to access my sd card without problems... I tried installing an older AOKP version still on the ROM - same errors as above (sure after cleaning everything).
I also reformatted the /sdcard partition but still it won't show up in Android! :\
I also flashed back the old kernel (which came with the old ROM I restored via nandroid) but no change. The damn sdcard link seems somehow broken. It is accessable in CWM recovery without problems, but none of my ROMs seems to be able to access it...
I really wonder what the repair service did... Is my device somehow repartitioned? :\
Help?!?
[update]: I flashed TWRP recovery and tried sideloading a ROM cause my 'sdcard' (or whetever which internal partition it now is) is empty: adb brings an error 'sdcard not found in /etc/fstab' so I am not even able to upload a rom anymore.... ??
[update]: OK I was able to upload AOKP rom via adb push, flashed it via TWRP - still stock explorer says 'file or folder was not found' :\ also in android settings only internal storage is visible...
Thanks a lot!!
Boernsb
Is there something like this here for HOX+?
http://forums.team-nocturnal.com/in...ountable-internal-storage-on-the-htc-one-xxl/
This guy seems to circumvent the need for RUU with a self-made recovery image he flashes and then do 'factory reset' from boot loader?
bboerny said:
Is there something like this here for HOX+?
http://forums.team-nocturnal.com/in...ountable-internal-storage-on-the-htc-one-xxl/
This guy seems to circumvent the need for RUU with a self-made recovery image he flashes and then do 'factory reset' from boot loader?
Click to expand...
Click to collapse
Alright, with the storage partitions messed up I would really advice you as mentioned to flash the RUU , look around on howto depending on your CID, If you did send it to HTC repair service and It came back broken up then I think you should just call them again and tell them? You wouldn't want your phone damaged and just let it go do you?
In the meantime do an RUU, and do a factory reset.
But just to clarify, can you or can you NOT adb push files to your storage?
Ghand0ur said:
Alright, with the storage partitions messed up I would really advice you as mentioned to flash the RUU , look around on howto depending on your CID, If you did send it to HTC repair service and It came back broken up then I think you should just call them again and tell them? You wouldn't want your phone damaged and just let it go do you?
In the meantime do an RUU, and do a factory reset.
But just to clarify, can you or can you NOT adb push files to your storage?
Click to expand...
Click to collapse
OK I was able to solve the problem by relocking and Re-RUU the device. After that all was back to normal. Unlocked again via HTCDev etc. and now all works fine.
For the next time - and I strongly advice all others - when I send a device to repair service I will put it in original state by myself. And yes I was able to push the rom via adb push... (just still don't understand where the difference between sideload and adb push is...)
btw: flashed newest stable of Cyanogenmod and now I have the first custom ROM on HOX+ where loudness of phone speaker is not only as good as original rom - but much louder
bboerny said:
OK I was able to solve the problem by relocking and Re-RUU the device. After that all was back to normal. Unlocked again via HTCDev etc. and now all works fine.
For the next time - and I strongly advice all others - when I send a device to repair service I will put it in original state by myself. And yes I was able to push the rom via adb push... (just still don't understand where the difference between sideload and adb push is...)
btw: flashed newest stable of Cyanogenmod and now I have the first custom ROM on HOX+ where loudness of phone speaker is not only as good as original rom - but much louder
Click to expand...
Click to collapse
Glad to be of help ^^
I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
rumpus01 said:
I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
Click to expand...
Click to collapse
Okay, first, what machine are you on? Linux,mac,xp,vista,7? You can't unlock on 8.1 drivers aren't compatible. But Yes you unlock via HTC dev, I have a tool to help for that if you want to try it it helps first time root you still have to take the info that it gives you and put it into HTC dev then put the code you get from the email you get into the folder but I don't know if you would want that I need someone to test it But continuing.
Unlock via HTC dev if you want to do it manually with the command first.
1. Open a cmd prompt where your fastboot tool is using shift+right click.
2. Boot into fastboot by pulling the battery, then holding volume down and power, then clicking on the first thing which is fastboot by clicking power.
3. Back to the computer type
Code:
fastboot devices
4. If your device is found your good to get your unlock data, if not you need to reinstall drivers/check your connection/or your on windows 8/8.1
5. Now to get your unlock token.
Code:
fastboot oem get_identifier_token
6. Copy and paste this into HTC dev starting at
Code:
<<<< Identifier Token Start >>>>
And ending with this line:
<<<<< Identifier Token End >>>>>
7. Submit the unlock token it will say if its valid or not and send you a email with it is.
8. When you get the email it will have a item called Unlock_code.bin place this item into the same folder in which your fastboot is in.
9. Initiate the command
Code:
fastboot flash unlocktoken Unlock_code.bin
10. It will then send the Unlock_code.bin to your phone, you will see a prompt saying "Unlock bootloader" Then volume up and click yes. It will wipe ALL of your data back it all up before you do anything...
11. When your phone finally reboots. If you would like a custom recovery boot back into fastboot again, (Pulling battery then volume down+power button and clicking on fastboot
12. Then once into fastboot, back to your computer download either
TWRP: http://techerrata.com/browse/twrp2/vigor
PhilZ: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/vigor <-------you must use this if using a ROM by snuzzo "aka Plain-andy or illusion ROM
CWM: Or go here http://forum.xda-developers.com/showthread.php?t=1914215 Download one of the zips, Extract it with your favorite extractor. You should get a .img in a folder, extract it and put it in your fastboot folder. This is only for CWM.
Take one of the .img's from above that you just downloaded and place it in the folder with your fastboot.
13.Back to your computer to push the recovery. Then while your phone is still in fastboot and connected to the computer make sure your device is still found.
Code:
fastboot devices
then if your device shows up, you are good to then flash the Recovery. Initiate this command.
Code:
fastboot flash recovery <name of recovery>.img
14. It should write the img successfully.
15. If you would like to go into recovery, you can either press "bootloader" In the fastboot option then click recovery and go into it from there. Or do
Code:
fastboot reboot
it will reboot your phone like normal. Then you can put your ROM and correlating GAPPS of choice onto your phone via USB Mass storage, along with SU. Put it on the root of your external SD card. Then you can reboot into recovery. After booting normal and transferring the ROM of choice you can then enable USB debugging and do
Code:
adb reboot recovery
16. It will reboot you to the recovery that you used. You might get a lot of errors on your phone. IGNORE THEM!!
17. Go to install and find SU from your external SD card. Install that. Then after that I would suggest STRONGLY making a backup (NANDroid) By clicking the backup button in any recovery, make sure you back it up to your external SD card.
18. Make sure that you have your ROM of choice on your SD card.
19. Wipe the hell out of everything once your ready to install your ROM.... EXCEPT SD CARD
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
23. Take your original <Name of ROM>.zip and extract it. Open the folder. In the folder will be a item called boot.img
24. Place this boot.img into the folder with your fastboot.
25. Again initiate the command
Code:
fastboot devices
make sure the device is found.
26. Initiate the command, this will flash the kernal aka "boot.img"
Code:
fastboot flash boot boot.img
27. Once you've confirmed that it has flashed the boot.img do
Code:
fastboot reboot
it will reboot your device. WAIT AT LEAST 20 MINUTES!!! FIRST BOOT CAN TAKE A WHILE!!!
28. Once rebooted set up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now talking about s-off, if you like to flash ROM's a lot I would suggest it, if not and your just staying on one ROM then just stay s-on. s-off allows you to write to every partition to the phone. s-off can be dangerous as if say you flash a ROM made for the S3, well your phone will flash it happily and well brick itself going down happily... But with s-on it will abort the flash or anything. That being said theres also the advantage of s-off being you can flash a ROM for your phone, flash and go, no computer. S-off can do some stuff inside the phone such as bootlogo's etc.. BUT its not needed for almost any app in the play store or any ROM... s-off just simply means you can write to every partition freely. No its not required. Now if you were to mess up and something goes corrupt on the phone and you need to return to stock for some reason......Well.... You almost kinda need s-off for that.... unless you do
Code:
fastboot oem lock
relock your bootloader and run a RUU..... But while s-off you can simply run a RUU (ROM upgrade utility I think ) But you can just run it.... This is how your would "return to stock" if anything messes up.... s-off can be EASILY obtained via rumrunner, use the universal 0.5.0 it will s-off your device http://rumrunner.us/downloads-2/
Unlike the old version of s-off which requires linux and a 22ga wire.... Hope this answers any questions!
I will post anything if i missed something, have to go, typed this real quick, please don't do this yet I think its right though....
edit: Just checked over it and made some changes... This should be exactly step by step... Or for what I did and what most others did. If I missed anything, someone else please post...
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
rumpus01 said:
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
Click to expand...
Click to collapse
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Code:
fastboot flash boot boot.img
8. Reboot phone.
If you have any questions with that. I will explain each step more in depth. But steps 1-11 were unlocking help.
Step 12-19 is pushing the recovery, making a back up, rebooting to it.
Step 20-end actually getting the device to boot after flashing ROM. If I need to explain again. I will. In a ever more simplified version. Plus the reason that there were so many steps is because the longest step literally takes like 2 minutes max. The rest is almost like 30 seconds besides actually flashing the ROM and GAPPS. I tried to do as much detail as POSSIBLE!!! Please consider rereading it, if you don't understand a step, ask and I will gladly explain. But it is a COMPLETE STEP-BY-STEP GUIDE. Hope you get your phone rooted, but if you didn't know what fastboot was....you might need some more reading..... I can write up a complete guide of what EVERYTHING means, what EVERYTHING does. But fastboot is just where you flash recovery/boot.img/etc.....any questions, please ask, I will explain or someone can beat me to it
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
rumpus01 said:
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
Click to expand...
Click to collapse
sweet. Just PM me or post here :good:
pball52998 said:
sweet. Just PM me or post here :good:
Click to expand...
Click to collapse
Alright man so after re-reading it, it's starting to make a whole lot more sense now. Initially, I was wondering why the hell there were so many steps in your first post. Now I realize you were just going step by step through the HTC unlock process as well, which I'm guessing HTC walks you through more or less but you clarified it in more detail.
Now in a broader step by step list, you said this:
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Click to expand...
Click to collapse
Now my understanding is that unlocking the bootloader wipes all data, but #4 is a backing up procedure... Is this just creating a backup of the stock ROM on my phone at the moment, without any of my apps or personal data? Then #5 would actually be wiping the stock ROM?
These few steps confuse me a little:
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
Click to expand...
Click to collapse
Are GAPPS included with the ROM download?
#21 - Are you telling me to "cache and dalvik" or is that part of the flash process that I don't have to do in separate steps? For example, are you saying
a) After a confirmed flash, you need to wipe, cache, and dalvik.
or
b) After a confirmed flash, wipe, cache, and dalvik, you need to boot into fastboot.
WTH is dalvik?
Now I think those are my only questions regarding the process for the moment; I'm going to check out some YouTube videos of some of these processes individually to get a better understanding. It sounds to me like most of this makes sense once you actually start going through the process and seeing it instead of reading about it, but I wanted to do as much homework as possible first.
Think I'll go ahead and give this a try tonight... It sounds like with S-on, I can only screw it up so much but we'll see. I did all my chores tonight so I can focus on this tomorrow all night if I wonk it out and just be without my phone during the day.
Oh one last question - Will I be able to get updates / update without flashing again?
Thanks again man!!!
Okay. So my "full" step by step makes more sense now? Good now do you see why I had so many steps? It was each individual part. Step by step. With clear detail or at least I tried
So moving onto the "unlocking wiping data" yes it will wipe every piece of data. But leaves stock. What I would suggest is putting su on your SD card and that being the first thing you flash before wiping or backing up..I've heard you can't back up bare bone stock. It must have root, or so I've heard... So put su on your sd card and flash it first (aka go to install and find it swipe to flash. Su should now flash. You now have root or should). Not very hard, just flashing it won't do any damage.
But backing up. When you back up it pulls every piece of info you have and puts it into a folder on your SD card. Like I have no stock... I accidentally erased it... But besides that. Do you see in my signature how I have 3 roms on my rezound. PAC, CM, And sense 5. See every one of those has been backed up. If I were to restore it, it would automatically restore to the point where I made the backup.
So now let's say. You have your backup of stock. It's on your EXTERNAL SD CARD. It should be about 1-3 gb backup. So now we have that backup made in twrp. Wipee we now have stock saved just incase something happens
So then we go in to the wipe button. Youre going to
factory reset 3 times
Wipe data, cache, dalvik cache, boot and system 3 times each. Don't ask why 3 I really don't know. But one isn't good enough...it's proven... So this leaves you with no OS oooo noooo. But the thing is you have your backup on your external hard SD card. And also your ROM/gapps on there. (gapps is google apps) but you must download the two separately. Both in a .zip format. Not a folder... Can't flash a folder... But there should be a need gapps button on the evervolv page? Click it and it should take you to a download for gapps. Remember all this is on the root of your external SD. So now we have 3 things on your SD card and no OS. O Lordy.... Time to hit up the install button!!! ;D now were going to choose the evervolv ROM. Bam, click add more zips, find gapps, click it. Bam, now you have two zips queed to flash. Just swipe to flash make sure you choose the rom before the gapps. so time passes (less than 5 minutes) and rom and gapps are now flashed. When it gets done flashing you should have some options. One being wipe cache/dalvik. That is where your question of the #21 is... Sooo.... Dalvik is pretty much like our java almost... It runs our apps...soon android will be changing to ART (android run time).
Blah blah blah, doesn't matter!! Lol xD so then after wiping your cache and dalvik after flashing your rom, return to the main menu of TWRP you should see a button on twrp's main menu, at the very bottom right, "reboot" when you click on that you should get 4 options, reboot system, bootloader, recovery, power off. We want to choose bootloader. This will bring us to fastboot (it will say fastboot usb in bug red letters if your in fastboot) where you flash the boot.img that you extracted earlier from the zip and placed it in the same folder as your adb/fastboot you remember? We need to open a cmd prompt and flash this boot.img "aka kernel" so were going to type in that cmd prompt: fastboot flash boot boot.img
This will flash the boot.img to your phone once confirmed, (only about 6 seconds to write it) were going to reboot the phone and hope for the best.. Do: fastboot reboot
It'll reboot your phone, remember first boot can take a while....
Also what do you mean by your last question??????
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
Hey man! I did not read your full post just now because I'm tired of thinking about this stuff, but I went through your step by step instructions and everything seemed to work out. I'm currently waiting for on my first boot; it's at the Evervol screen with the heartbeat animation going on. Everything made perfect sense once following your guide to the actual process; it just seems risky since there's no good way to practice unless you have a spare phone or something.
The only thing that tripped me up was that my SD card had all the data from my previous ROM even after everything was wiped. So I formatted it in Windows prior to copying the SU, ROM, and GAPPS zips on there.
Oh and I noticed after wiping and booting into the "clean" stock ROM, I had no service... Obviously, I didn't try to fiddle around with that since I was about to install a new ROM, but I can see that being a problem if this ROM ever loads (been about 22 mins).
I did find this info on a different thread:
1. Go to the dialer and press *#*#4636#*#*
2. Click on "Phone Information"
3. You should notice almost towards the bottom radio settings, Make sure the radio is on and change the settings from WCDMA to GSM (auto)
4. Exit out of the screen by pressing the back button
5. Reset the phone and you will have service.
Click to expand...
Click to collapse
I'll give that shot if it's no bueno!
Thanks again man, I'll post back tonight if I don't fall asleep before it's done loading, lol. Either way I'll post back tomorrow. Seriously thank you again, can't believe you typed all that out for me, even when the first 11 steps were step by step from HTC too. :good: True internet assistance!
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
I did indeed as it was listed in your steps, of course!
It's been about an hour now, so I'm guessing something went askew and it is not going to power up. What course of action should I take from here? I'm guessing go back to stock ROM via recovery (the backup I made), and then do the whole process over again, aside from unlocking and what not. I definitely installed SU before making a backup, so hopefully that works out.
Thanks again! It's never simple...
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
No, I did not... I did everything before your post about that, so I'm guessing that's the problem. I also only wiped cache, dalvik cahce, system, and internal storage. There's an option for android secure and factory reset under the wipe menu as well, but I wasn't sure about those...
I tried pulling battery and rebooting, I'm guessing it's dunzo. I am now booted into recovery mode and going to recover to the backup I made, and try the whole thing again after reading your post about wiping multiple times.
EDIT: To clarify, I am wiping everything 3 times before restoring. Then I'm going to reboot normally to see if the restore worked, and then go through the process again except wiping multiple times before installing the ROM this time.
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
Crap I already wiped everything and tried a restore, which doesn't appear to be working haha. And don't worry man, I can't believe you gave that many instructions to begin with. It's a lot of steps! Nothing happens when I boot after doing my recover install. My computer gives the sound of a USB device but says nothing, and my phone doesn't even light up in any way. I'm going to go wipe everything and try rebooting it normally again.
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
So after wiping everything, I go to "install" and all the zip files for the GAPPS and SU and ROM are on my Internal storage device... didn't I just clear that 3 times???
I cleared everything including internal storage and selected reboot, and recovery told me SU was not installed and asked if I wanted to. I chose yes and rebooted. Then wiped cache/dalvik cahce 3 times each, and now installing the ROM and GAPPS again... I think I wiped my internal SD card & system in addition to cache and dalvik cache after installing SU but before installing the ROM and GAPPS initially... I wonder if this was the main source of the problem.
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
WELL WELL, IT IS WORKING. IT blew through that Evervolv boot screen in like 2 minutes this time.
I see that my service is not working, and my computer said MTP USB Device drivers failed to install. I now see that has something to do with transferring media files to PC.
Well, whatever. I am cool with this for now, at least it is installed. Very tired, let's all go to sleep! Thanks again for all the help man, feel like I'm paying someone for remote support lol.
Lol gg man. We got it. Cheers!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF