Okay... So I have a bit of an issue here that I hope I can get resolved really quickly. I got an HTC Evo 4G LTE and decided I wanted to root it in a fairly short amount of time. I previously had a Samsung Galaxy S3 which I rooted and I have a Nexus 7 tablet which is rooted, so I'm not necessarily new to the process. I followed all the normal steps.
However, whenever it came to installing twrp I thought it would be better to install cwm, so I switched the recovery image files. This worked for the time being and I was able to boot into recovery without a problem. I booted into recovery successfully and was able to wipe everything that needed wiping, but since this is a new phone I didn't think it would be necessary to back up anything, so I skipped that step. After wiping the dalvik cache, sys cache and did a data/factory reset I went to install CyanogenMod 11 (since I wanted android 4.4 on my Evo). When it went to install the mod the phone gave me a "status 7" error message. I tried again to no avail. So I thought it was because I had installed cwm instead of twrp. So I went ahead and flashed twrp onto the phone. No dice, twrp didn't even work. So I flashed a stock rom, didn't work either. So I re-flashed cwm onto the device and now it won't go past the recovery stage. i.e. when I try to power on the phone it goes directly into recovery, I boot into the "power+volume down" mode and it doesn't help at all. So I'm kind of stuck at this point and not sure what to do. I cannot access the internal files of the phone and I would really like to get it working by tomorrow or the next day.
Thanks for your time.
Look HERE
In addition to what Bigdaddy posted, you need to use TWRP recovery, not CWM. CWM doesn't play well with the misc partition on the EVO LTE. I also suggest reading the Hboot guide in my sig for some useful information. Once you get your phone up & running, you will need to fix your misc partition.
Sent from my HTC EVO 4G LTE
Related
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
I've been running AOKP Milestone 6 for about 2 months now. It always had a problem unlocking the lockscreen at full battery as it didn't receive touch input so I just restarted the tablet. Then it would just reboot as the tablet would not turn off if the power button was held. I dont care. Dont turn it off enough for that to make a difference.
Well one day I woke up turned on the tablet and like normal there was no touch recognition. Oh well reboot like normal. Then my tablet stuck in the AOKP animation. It just froze. About halfway through the animation. I used the hard reboot (vol- and power) and it froze again at about the same place. I WTF and go to CWM and reflash the ROM and it froze at applying data. Hard reboot. Flash Galaxy Task. Freeze at applying data. Flash a backup I made on AOKP milestone 6. Froze at applying data. Plug into computer and flash stock root package. SUCCESS!! Then the AOKP boot animation comes up and freezes at the same place as before. I have no idea what to do as I decided I would flash 1 ROM and leave it on my tab because I've hard bricked my infuse before and didn't want to send this in have it come back broken and buy a new one.
Galaxy tab 10.1 wifi running http://forum.xda-developers.com/showthread.php?t=1459287
What version/mod of CWM are you running?
Grab CWM 5.5.0.4 at this address.works pretty well:
https://sites.google.com/site/arashtarafar/
Remember to wipe data/cache after flashing processes...
arashtarafar said:
What version/mod of CWM are you running?
Grab CWM 5.5.0.4 at this address.works pretty well:
https://sites.google.com/site/arashtarafar/
Remember to wipe data/cache after flashing processes...
Click to expand...
Click to collapse
I'm Running 4.0.0.4. Wasnt planning on flashing a lot of ROM so flashing that would be not so important to me. Checking that site out now.
I noticed I forgot to mention it's a wifi model. will update OP.
This currently happen to me too.
Will try to find 3g stock Rom and try to upgrade CWM
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
I am currently having this problem too.
It all started when my wifi started not working so I rebooted my tablet. Suddenly im stuck in a bootloop with no way to get out of it.
I'm able to access CWM and have tried wiping cache, but that didnt work. Now i've tried wiping /data but it freezes.
I'm unable to access my USB as it repeatedly says "E:unable to open ums lunfile (No such file or directory).
I've tried using ADB to push a new flash image which worked but im still stuck in a brand new bootloop (presumably because i cant wipe /data).
Can anyone help? I have NO idea how this happened.
Flash a stock ROM using Odin in download mode...now that you are in such trouble flashing a 3G ROM doesn't make much difference...
Today I decided to root my phone, and after successfully doing that, decided I wanted to try out installing a custom ROM. Obviously by the title that didn't work out too well.
I'm using ClockworkMod as recovery, and I attempted to flash CyanogenMod using ROMManager. I created backups before I tried flashing, but that didn't help. Once I hit Install ROM from SD Card I made sure to back up again, but I did not check clear the cache which I probably should have done. My phone then rebooted into ClockworkMod and I then went to install zip from sdcard and chose the .zip that contained the latest CyanogenMod, it ran through the process alright then rebooted.
At that point I got stuck in a boot loop, I think it might've been either that I didn't clear the cache before or if it was that I had the .zip on an external SD card or not. I then looked up ways to fix the loop such as clearing the Dalvik cache, wiping the cache partition, then eventually I tried to wipe the data/factory reset on the recovery option but that all did nothing. During all this I also tried my backup hoping that would end my problem, but I got an error with the MD5 mismatching so I can't use that backup, I do have other backups on my computer, but I can't get them onto the SD card, and ADB isn't detecting my phone so I can't try a way to fix the backup that way either.
Anyone have any idea how to fix this? I can provide more information if needed. Any help would be great.
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig for more info. Also, TWRP recovery is recommended on the EVO LTE, not CWM, which is no longer supported, at least on this device.
Sent from my HTC EVO 4G LTE
FinZ28 said:
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig for more info. Also, TWRP recovery is recommended on the EVO LTE, not CWM, which is no longer supported, at least on this device.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Ok, thank you so much for your response this actually got me back on track after switching to TWRP and flashing the kernel first with CWM being the big issue for me. Now I'm just waiting for CyanogenMod to load, which I assume just takes a few minutes at the loading screen.
Got it fully working, thanks again
Not a problem.
Sent from my HTC EVO 4G LTE
First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.
Hi all,
New to this whole rooting and flashing thing. I'm not as good with computers that one can hold in their hand.
Anyways, I'll try to explain this stew of issues that I have
I'm running CW Recovery (6.0.2.3) in conjunction with SlimBean (dtt 4.2.2). One day, in a far away land, my phone prompted me to update Slim. That was all and dandy because I've flashed roms from zip files before. When I tried to do that, the process was aborted and I was given a slew of error numbers that made my brain hurt.
So, I tried to start fresh and clean, like the cilantro that chipotle puts in our burrito bowls. I tried a factory reset using the CW Recovery mode so I can re-root now that jellybean is 4.3. After I wiped the cache and data/factory reset, I rebooted the phone. My phone still boots into Slim and uses clockwork for recovery mode.
Essentially, how do I de-root my phone or factory reset it to the settings that I had from day 1?
UPDATE: I just tried flashing CW Recovery from 6.0.2.3 --> 6.0.4.7. After flashing it, I rebooted my phone into recovery. Now I'm getting a never-ending boot cycle. The samsung logo pops up along with the little blue text "recovery" at the top, then shuts off and repeats that every 3 seconds or so. Methinks I broke it
Thanks
Flash stock ROM via Odin. Download [URL="http://www.sammobile.com l" ] Sammobile [/URL]
Edit: better url
Why download a flight simulator?