II'm getting Emmc errors with twrp when I try to backup or flash new roms. Kinda weird since I used Twrp to flash a 4.3 rom in the first place but now I want to upgrade to 4.4.
Is it just a Twrp error and I should be using another recovery?
Manbot27 said:
II'm getting Emmc errors with twrp when I try to backup or flash new roms. Kinda weird since I used Twrp to flash a 4.3 rom in the first place but now I want to upgrade to 4.4.
Is it just a Twrp error and I should be using another recovery?
Click to expand...
Click to collapse
What version of TWRP? Only version 2.6.3.0 is supported for KitKat based ROMs... That being said, it sounds like your internal storage is corrupted (emmc=internal storage), which usually requires running an RUU to correct, unfortunately this requires S-OFF, assuming you were on the current OTA update.
I'm pretty sure it's the latest version of Twrp. The phone functions fine and it was okay when flashing the 4.3 rom.. Is running an RUU and S-OFF difficult?
emmc
I had the same problem last nite with S-0n and EMMC errors and TWRP.
Cured it by flashing the AmonRa recovery, wiping the hell out of what could be wiped (many errors)
then reinstalled TWRP 2.6.3.0 (only) and miraculously, it did finally format the internal, cache, and data
that were giving EMMC errors.
Yes, you should HTC unlock, install a modded Rom, and carefully follow the new S-0ff (no wire trick) RumRunner
S-0ff for Rezound. S-0ff will prevent you from borking your phone and allow faster ROM installs.
Easy to do if you do "just and only what it wants" for advance preparation.
After S-0ff, you relock it, flash Scotty's Relocked to Locked zip, and run RUU of your choice, or if at this point
it's all good, load up your next daily user.
Running the RUU gets rid of the Tampered hboot status.
Before you do anything, try wiping your Internal SD (back it up if you can get to it via your rom) via TWRP, sometimes it's just simple as that. If that doesn't do the trick, follow the advice already given.
mjones73 said:
Before you do anything, try wiping your Internal SD (back it up if you can get to it via your rom) via TWRP, sometimes it's just simple as that. If that doesn't do the trick, follow the advice already given.
Click to expand...
Click to collapse
How do I backup through the rom? I tried to backup in Twrp and it doesn't let me.
Manbot27 said:
How do I backup through the rom? I tried to backup in Twrp and it doesn't let me.
Click to expand...
Click to collapse
Attach your phone to your PC, copy the contents of Internal SD...
Related
I've already completed all of the steps from hansoon2000's guide here including installing T-Mobile's ICS and \4ext recovery: http://forum.xda-developers.com/showthread.php?t=1619491
Now the next step I wanted to do is install CapromCE. What I did was install the "required" firmware (the link in CapromCE's thread was down but I was able to find the file uploaded by NRGZ28 with identical MD5). I then installed CapromCE through Recovery. Should I have renamed it to PH85IMG and installed through Bootloader?
Installation went fine but I was stuck at the second HTC logo (green logo on black background). I was still able to access Recovery but it couldn't load the internal SD. This was fixed by formatting the SD and I was able to successful re-install the T-Mobile ICS by renaming it to PH85IMG and loading it through Bootloader.
Anyone can figure out where I've messed up?
Thanks!
Install zip from sd after wiping should be all you need to do. Make sure you backup stock ROM in case you have to go back
Sent from my HTC_Amaze_4G using XDA
ok for some reason I'm no longer able to get into Recovery. I'm getting the same screen as when I was running controlbear for s-off
zerolife said:
ok for some reason I'm no longer able to get into Recovery. I'm getting the same screen as when I was running controlbear for s-off
Click to expand...
Click to collapse
You restore everything to complete stock when you flashes the ics ruu via bootloader, now start the entire process all over again, this time wipe your partitions before installing the zip file and make a note as previously stated to backup before doing so.
Sent from an Amaaaaaazing place :-D
Hello! I'm new-ish here... As in I just opened an account to post after watching from the sidelines for a few months now.
Anyway,
I'm having problems with my phone. I was running ViperLTE 2.1.1 and recently switched to CyanogenMod. My sdcard wouldn't work correctly, so I tried to go back to stock, and my phone never made it past the "HTC" boot screen. I've tried reflashing and whatnot almost a dozen times, including restoring my nandroid backup, with no luck. Now I can't even access it via adb. What do I do?
Fastboot the stock boot image. The instructions are in the development section. Are you s off?
Sent from my Incredible 4G LTE using Tapatalk 2
MJL99 said:
Fastboot the stock boot image. The instructions are in the development section. Are you s off?
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I'm not s-off, and I have tried that multiple times, and at this point I can't get to adb or fastboot. I'm having trouble even accessing the bootloader.
EDIT: I got to the bootloader and adb/fastboot, but still flashing any boot image does nothing to fix the problem, and I'm still stuck at the htc screen.
19wolf said:
I'm not s-off, and I have tried that multiple times, and at this point I can't get to adb or fastboot. I'm having trouble even accessing the bootloader.
EDIT: I got to the bootloader and adb/fastboot, but still flashing any boot image does nothing to fix the problem, and I'm still stuck at the htc screen.
Click to expand...
Click to collapse
You are flashing the stock boot image right? From here for example.
Code:
fastboot flash boot boot.img
Are you installing a stock(-based) ROM or restoring a nandroid?
mdmower said:
You are flashing the stock boot image right? From [[Link removed because of new-user limits]] for example.
Code:
fastboot flash boot boot.img
Are you installing a stock(-based) ROM or restoring a nandroid?
Click to expand...
Click to collapse
Yeah. I'm repeatedly flashing the stock boot image and restarting, to no avail. According to the CyanogenMod forum, I need to install a stock-based ROM and then format my sdcard (to fix my initial problem)... and then restore my nandroid afterwards. At this point, it would be nice to just be able to restore the nandroid and have a phone that makes calls for a day-trip I'm going on tomorrow.
19wolf said:
Yeah. I'm repeatedly flashing the stock boot image and restarting, to no avail. According to the CyanogenMod forum, I need to install a stock-based ROM and then format my sdcard (to fix my initial problem)... and then restore my nandroid afterwards. At this point, it would be nice to just be able to restore the nandroid and have a phone that makes calls for a day-trip I'm going on tomorrow.
Click to expand...
Click to collapse
Just to check, after flashing the stock boot.img, you have installed a stock ROM or restored a stock-based ROM from a nandroid right (i.e. you're sure the backup is not from CyanogenMod)? The boot image alone isn't going to do anything. Also, depending on whether you were running Viper 1.x or 2.x, you need a different boot.img. The boot.img for Viper 1.x can be found here.
If restoring your nandroid backup doesn't work, freshly install Stock (or Viper).
mdmower said:
Just to check, after flashing the stock boot.img, you have installed a stock ROM or restored a stock-based ROM from a nandroid right (i.e. you're sure the backup is not from CyanogenMod)? The boot image alone isn't going to do anything. Also, depending on whether you were running Viper 1.x or 2.x, you need a different boot.img. The boot.img for Viper 1.x can be found here.
If restoring your nandroid backup doesn't work, freshly install Stock (or Viper).
Click to expand...
Click to collapse
I'll try that when I get to the computer, but do I need to use twrp or can I continue to use cwm? Also I can't access the sd card via my computer to put the rom onto it because it doesn't mount when I'm booted into recovery
19wolf said:
I'll try that when I get to the computer, but do I need to use twrp or can I continue to use cwm? Also I can't access the sd card via my computer to put the rom onto it because it doesn't mount when I'm booted into recovery
Click to expand...
Click to collapse
Either TWRP or CWM will work. There is a test version of CWM that enables USB mass storage support... but I haven't yet tested the feature under Windows.
I got it to work, via side-loading the zip and then flashing the boot.img. I don't know why I was having so many problems before... But they're better now. Thanks for your help
I have had TACHYON-1.1.5 install for awhile. I rebooted my phone and I cant get into the ROM anymore. The screen is just black. I can get into recovery and reflash, but nothing happens... I cant seem to mount SD card in recovery either. Using CWM recovery.
If its easier can I just bring my phone back to bone stock? I am S-ON rooted, unlocked.
aceofskies05 said:
I have had TACHYON-1.1.5 install for awhile. I rebooted my phone and I cant get into the ROM anymore. The screen is just black. I can get into recovery and reflash, but nothing happens... I cant seem to mount SD card in recovery either. Using CWM recovery.
If its easier can I just bring my phone back to bone stock? I am S-ON rooted, unlocked.
Click to expand...
Click to collapse
are you s-on did you fastboot flash the boot.img
Edit: And your mount issues are caused by the fact that you never reapartitioned and formatted internal sd and emmc using TWRP only
REV3NT3CH said:
are you s-on did you fastboot flash the boot.img
Edit: And your mount issues are caused by the fact that you never reapartitioned and formatted internal sd and emmc using TWRP only
Click to expand...
Click to collapse
Reventech, I have a similar problem which suddenly arose on Vanir yesterday evening. I am bootloader unlocked, using vinylfreak's 2.27 hboot, and I am S-OFF. I can reflash TWRP 2.6.3.0, I can even run and get a nandroid to restore and boot, and the system works completely normally. I can make calls, connect, BT, etc. etc., but when I reboot, the phone runs the splash, then the boot animation, then sits at the black screen. I have run this now twice, completely restoring my ROM and still get hung after boot.
Utterly bizarre.
Any suggestions? Switch to Amon Ra 3.16 and try to re-wipe boot image (I know TWRP can't wipe boot) then reflash TWRP and restore prior nandroid of boot? I'm positively flummoxed.
hgoldner said:
Reventech, I have a similar problem which suddenly arose on Vanir yesterday evening. I am bootloader unlocked, using vinylfreak's 2.27 hboot, and I am S-OFF. I can reflash TWRP 2.6.3.0, I can even run and get a nandroid to restore and boot, and the system works completely normally. I can make calls, connect, BT, etc. etc., but when I reboot, the phone runs the splash, then the boot animation, then sits at the black screen. I have run this now twice, completely restoring my ROM and still get hung after boot.
Utterly bizarre.
Any suggestions? Switch to Amon Ra 3.16 and try to re-wipe boot image (I know TWRP can't wipe boot) then reflash TWRP and restore prior nandroid of boot? I'm positively flummoxed.
Click to expand...
Click to collapse
i noticed that custom edited hboots have been an issue in this trend the last few days...try updating to 2.28 as thats mor compatible with jb roms
REV3NT3CH said:
i noticed that custom edited hboots have been an issue in this trend the last few days...try updating to 2.28 as thats mor compatible with jb roms
Click to expand...
Click to collapse
That worked for a bit, but darn if I didn't do a Nandroid and then the unit failed to boot again. This is so frustrating.
UPDATE: Flashed new nightly and we're back in business.
My name's Harold and I'm a flashaholic....
Ok so I've been struggling with this for MONTHS. I flashed Hatka 2.x (Android 4.2) a while back, and ever since then I have not been able to install any other rom besides Hatka 2.x.:crying:
Android: 4.2
Rom: Hatka 2.x
Kernel: 3.4.10-g4d47dce [email protected] #1 SMP PREEMPT
HTC Sense: 4+
I have tried flashing several roms from just about anything 4.2.2 - 4.3 and now 4.4.x. I'm not sure If maybe I need a new kernel, boot image or what but I feel like I have tried everything. When I flash a rom I wipe data/cache/dalvik cache (of course), Flash the rom, flash gApps, flash cache/dalvik and more times than not my phone will never get past the HTC logo. Sometimes more lately with 4.4 roms my phone will boot loop only showing the HTC logo for a minute or two then restart. I root and flash several different types of phones for my friends all the time, and never have any of these issues that I've faced with my own phone.
I recently thought about trying to un-root, re-lock, and flash back to stock, then re-root and un-lock again but I'm not sure if that will even help.
Things I've tried:
Several roms
Moded kernel
Stock kernel
Multiple CWM versions
Multiple TWRP versions
Fastboot flash
Adb flash
Adb Sideload
Roms I am currently trying to flash:
AOKP unofficial (4.4.2)
BeanStalk (4.4.2)
CM-11 Nightly (4.4.2)
OSE Official (4.4.2)
My secondary HDD with all of the kernels, roms, and anything else I have tried recently failed so I don't have the specific version numbers for any of the attempts listed above.
If someone could give me any advice on this I would be eternally greatful. The Android/xda community has always been so helpful with many others in times of need, so now after spending months of research and trial & error I am reaching out to anyone here at xda that may be able to give me some advice/assistance.
Links to other threads/tools are greatly appreciated also! :good:
Thank you in advance.
-EDIT-
SOLVED
I took thay10's advice and flashed RUU. Since I got an error flashing RUU 3.04 I found RUU 1.15 here and flashed that successfully.
After that I verified my cid using this method.
When that turned out ok I continued to the HTCDev page to unlock my bootloader.
Once the bootloader was unlocked I used Facepalm S-Off method to achieve S-Off. (Using only the modified boot.img and DNA-rescue.img [links in thread]).
After all that was finished and I now had my bootloader unlocked and S-Off, I chose the recovery of my choice and flashed it using fastboot.
FINALLY, I was able to load the recovery and wipe everything (system,data,cache,sdcard) and flash a 4.4.2 rom of my choice!
Everything works perfectly now, I'm so relieved! Thank you again thay10 for your help. Hopefully this can help someone else out as well.
anyone?
Okay first thing. Looks like your doing a dirty flash and going from rom to rom may cause problems and clutter.
What I would advise is you to do a clean flash which involves you wiping. cache,data,system,sdcard.
But ONLY do this after you backup files you need, and make sure you have fastboot and adb installed and is working properly on your computer.
Edit: Are you still soff and bootloader unlocked?
thayl0 said:
Okay first thing. Looks like your doing a dirty flash and going from rom to rom may cause problems and clutter.
What I would advise is you to do a clean flash which involves you wiping. cache,data,system,sdcard.
But ONLY do this after you backup files you need, and make sure you have fastboot and adb installed and is working properly on your computer.
Edit: Are you still soff and bootloader unlocked?
Click to expand...
Click to collapse
Thank you for the advice. Yes I am S-off and my bootloader is unlocked. I noticed that the version of cwm I had installed was not wiping the system folder so I flashed 'Philz Touch 6' cwm and used that to do a full wipe including system,data,cache,sdcard and then used adb sideload to flash a couple roms. Each rom I flashed after a full wipe still won't boot. I continue to loop through the htc logo.
ADB and fastboot are both working properly, and htc drivers are fully up to date.
Roms I am currently trying to flash are:
AOKP unofficial (4.4.2)
BeanStalk (4.4.2)
CM-11 Nightly (4.4.2)
OSE Official (4.4.2)
stevenschemers said:
Thank you for the advice. Yes I am S-off and my bootloader is unlocked. I noticed that the version of cwm I had installed was not wiping the system folder so I flashed 'Philz Touch 6' cwm and used that to do a full wipe including system,data,cache,sdcard and then used adb sideload to flash a couple roms. Each rom I flashed after a full wipe still won't boot. I continue to loop through the htc logo.
ADB and fastboot are both working properly, and htc drivers are fully up to date.
Click to expand...
Click to collapse
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
No problem. I was using TWRP for the longest time but I read a few different places that people were having issues flashing cm-11 on some versions of TWRP and to explorer versions of CWM that worked.
I have RUU downloaded but I have not ran it yet. What exactly will RUU do?
-EDIT- Also when would I run RUU? Would I have to restore my nandroid backup first or can it read my phone while in recovery through adb?
-EDIT- I went ahead and flashed RUU 3.04 while in the bootloader. It says it's sending to my phone right now so I will update shortly with a result.
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
I flashed the latest TWRP and when I sideload the rom I get the error saying "Error executing updater binary in zip '/data/'
This is the issue I was reading about when people were saying they couldn't flash cm-11 with TWRP. I've even tried installing cm-10.2 roms and had the same issue.
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
The RUU 3.04 flash finished and I got "ERROR 158; Image error. The rom update utility cannot update your android phone. Please get the correct rom update utility and try again."
Any idea what would cause that?
RUU was downloaded from HERE.
stevenschemers said:
No problem. I was using TWRP for the longest time but I read a few different places that people were having issues flashing cm-11 on some versions of TWRP and to explorer versions of CWM that worked.
I have RUU downloaded but I have not ran it yet. What exactly will RUU do?
-EDIT- Also when would I run RUU? Would I have to restore my nandroid backup first or can it read my phone while in recovery through adb?
-EDIT- I went ahead and flashed RUU 3.04 while in the bootloader. It says it's sending to my phone right now so I will update shortly with a result.
Click to expand...
Click to collapse
TWRP last time I checked didn't support CM thats why people switched to CWM
What are you trying to do to your phone? Most people only run RUU to get to stock.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
stevenschemers said:
The RUU 3.04 flash finished and I got "ERROR 158; Image error. The rom update utility cannot update your android phone. Please get the correct rom update utility and try again."
Any idea what would cause that?
RUU was downloaded from HERE.
Click to expand...
Click to collapse
I'm guessing you ran the exe. I was refering to the one thats a zip file and you flash it
I have a Wind AWS Amaze 4G. I unlocked the bootloader and rooted it. I then tried out various custom roms and the few that actually loaded didn't support wi-fi. Now trying to go back to the stock rom, every time I try to flash it in TWRP 2.6.3.0, I get install failed: File_getprop: failed to stat, error executing updater binary in zip, error flashing zip. This is getting very frustrating. It's like TWRP is only letting me flash unstable roms.
Stock.
fdiddy said:
TWRP is only letting me flash unstable roms.
Click to expand...
Click to collapse
You can try newer version of TWRP or another recovery, perhaps 4EXT?
Might also be necessary to do factory reset and format all partitions except sdcard--both internal and external if given the choice.
Going back to stock will put you back to s-on, I believe. There are stock-based rom's that will not put you back to s-on. Maybe you never got s-off. In which case, 4EXT will most likely let you successfully flash those other rom's by enabling TOOLS->ENABLE SMART FLASH.
Good luck finding what you want.
I tried with CWM, and the same happened. I was able to flash the Mobilicity (Dave) rom, and then got stuck at the HTC splash screen. When I rebooted, wiped, and tried to flash the same rom, it aborted and threw the same error codes!
I've completely wiped all partitions on the phone. I never had S-OFF. I thought that it wasn't necessary since I was able to unlock the bootloader.
I will try with 4EXT and report back. Thanks.