I have been playing around with this for the past 24 hours almost non-stop. The device information:
M7 T-Mobile (converted to GE 4.3)
No OS installed at this point
HBOOT 1.54
S-ON (Unfortunately big mistake not to take care of this during conversion)
Unlocked Bootloader
Can do adb and fastboot commands, but anything that I try to write to system (from a ZIP file either RUU or custom ROM, they error out)
fastboot oem rebootRUU then trying to flash would give me: FAILED (remote: 99 unknown fail)
trying to update the bootloader from the same package I get: FAILED (remote: 12 signature verify fail)
I can flash boot and recovery images and that's about it, tried both CWM and TWRP to install CynogenMod, they both fail.
Here is the history of what happened:
Day one, I wanted to convert to GE so I did and everything worked, the device wasn't rooted or anything so it was fully GE. (S-ON though). Yesterday, when 4.4 OTA came, I went aehead and installed, everything installed fine OS booted to lock screen, but as soon as launcher was initiated, the phone would restart within 3 seconds (first mistake was to update through OTA, but I thought I was converted completely so trusted it). Second mistake was I said, well I will just reinstall all the apps since nothing worked after trying for hours so I did a wipe and reset factory and now, it would boot to the setup screen and after 3 seconds like before, it would restart, so I decided to get rid of whatever on there from fastboot and that's where I stand today. I played with it for hours yesterday and today and I have tried the toolkit, revnov (which doesn't work with 1.54 and rumrunner requires the device to boot to OS, which I don't have).
I feel like I have managed to brick it even with being able to send and execute commands.
Any help would be immensely appreciated.
EDIT 1:
TWRP comes up with a password prompt right at the beginning as if the data on the phone is encrypted. I never encrypted the phone in any way, I did have corporate email that had the right to wipe the device.
Try sideloading a Rom from recovery from your pc to phone
Sent from my HTC One using xda app-developers app
---------- Post added at 07:14 AM ---------- Previous post was at 07:12 AM ----------
I know one thing never hit reboot if you ever see No Os installed while In recovery
That means the bootloaderr will be wiped
...I did this with my s3 had to jtag repair.
Best of luck
Sent from my HTC One using xda app-developers app
Sideload won't work, it immediately fails on TWRP (last log is updating partitions), in fact, when on CWM, adb wouldn't load the device at all (no devices listed), but when TWRP, it works just fine.
lojak29 said:
Try sideloading a Rom from recovery from your pc to phone
Sent from my HTC One using xda app-developers app
---------- Post added at 07:14 AM ---------- Previous post was at 07:12 AM ----------
I know one thing never hit reboot if you ever see No Os installed while In recovery
That means the bootloaderr will be wiped
...I did this with my s3 had to jtag repair.
Best of luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try uninstalling and re-installing your drivers on your PC and try again.
I actually got it back. I gave myself a clue on here, apparently, the phone when factory resetting encrypted the device and I went through fast because the device would restart if I didn't so couldn't read all pop-ups. I went ahead and encrypted which is why TWRP and CWRM didn't work, tried many methods to remove the encryption and just wipe everything off. Nothing worked, the data couldn't even mount to be wiped therefore no ROM would successfully install. So I reinstalled recovery of GE build that I used for factory reset, went into that recovery and wiped cach and data completely and this time it worked (no other version worked before). After that it was easy to TWRP or any other custom recovery to get the stock ROM on the phone and now it's all back. Now I am back to completely stock with tampered flag and unlocek bootloader. Eventually, I will do a proper conversion to GE because I am starting to dislike the SENSE (which I knew I would) because of all the stuff I don't use and worse battery management and mobile data unnecessarily updating things I don't use. This was such a experience, as much as I wanted to keep the Nexus 5, had to return it.
Thanks all for the suggestions.
Is there any way I can get rid of tempered flag, I know I ran across something well hidden, ant link would be helpful, thanks.
what is meant with "GE build"? I am stuck in the same situation you have been, but have no clue what you did to get it back to life. THanks for a hint.
I meant version by build. You can find an RUU for the version you were on (4.2.2 or 4.3 or 4.4) and take out the recovery.img and in fastboot, flash recovery with that image and go in recovery and wipe data. I hope this helps.
MrWhat said:
what is meant with "GE build"? I am stuck in the same situation you have been, but have no clue what you did to get it back to life. THanks for a hint.
Click to expand...
Click to collapse
Related
To summarize:
Rogers EVO 3D GSM
No SIM Card currently in the phone
Had Stock ICS Update
Rooted the phone, causing it to become stuck in an irreversible restarting pattern
Phone (if left alone for a while) will turn itself off within 4-6 minutes, and restart. It will repeat. If it is plugged-in and charging, it (occasionally) does not turn off. If the music player is playing in the background, it will not turn off.
Problem will persist even if the SD Card is not present.
Have tried multiple solutions (see page 2) which haven't worked.
Could really use some help!
Hi there, I was hoping that the more experienced phone users here could help me with my problem.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
I'm really at my wits' end here, and I hope that someone can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
ReversaI said:
Hi there, I'm relatively new in terms of anything phone-related, so I was hoping that the more experienced people here could try to help me with my issue.
My phone is an EVO 3D (Rogers GSM). A while back, I decided to try and root my phone (I had the ICS update at the time). I managed to S-OFF it and later unlock it, but I had a lot of trouble rooting the phone through conventional guides.
In trying to root my phone, it became stuck in a boot loop that would cause it to turn on, flash the HTC logo, but then turn off and repeat the process. This was a really annoying issue for me, that I couldn't resolve until as a last-ditch effort, I managed to install a stock RUU and fix the problem.
Finally, I was able to root the phone last week. But as soon as I did so, it began performing erratically again. This time, the phone would turn itself off and turn back on (and repeat the process infinitely) if I left it alone for 5-7 minutes.
I tried everything I could think of to fix the problem, even wiping the partition caches/dalvik drives and factory resetting it multiple times. But even with all that, it wouldn't resolve the issue. I heard that the SD card could've been the root of the problem, but even after taking it out the problem still occurs. I've also tried factory resetting it without the SD card, but to no avail.
So I decided to install my first ROM; Viper3D (1.0.0-Multi-8_14).
I was successful in installing it, and the new software was great, but unfortunately, the issue still carried over. Unless I was constantly doing something on my phone, the phone would shut reboot after 5-7 minutes. And it would keep repeating without end. More factory resets would not do anything, and I find myself unable to install Stock ROMs now.
A sort of "temporary" fix (when I want to keep the phone on for a bit) is to keep the music player playing. As long as a song is playing (even if the volume's off), the phone won't reboot.
Nothing else works.
To summarize:
Rogers EVO 3D GSM
Had ICS installed before root
Rooted, now phone is stuck in irreversible restarting pattern
Problem persists even without SD Card
Now using Viper3D ROM, but the problem remains
Could really use some help
I'm really at my wits' end here, and I hope that some of you can help me with my problem. If you have any further questions you need answered before you can help me, by all means ask.
(Also, I'm not sure if this has any bearing on the issue, but my HBOOT downgraded after the root from 1.58 to 1.49. Could that be related to my problem at all?)
Thank you very much for your time.
Click to expand...
Click to collapse
Sounds like a possible bad flash, you are obviously using the stock kernel, did you flash the new firmware, check setting about phone and will see baseband etc, that will tell if you have flashed the correct firmware, I too am with rogers. also using viper rom multi, hboot is the same and I have no such problem, here a screeny baseband, never mind the kernel
Please don't quote an op of that size next time but I'm on the correct firmware on my CDMA device and reboots happen occasionally it is most likely the ics update in general or just the kernel try a different one
Sent from my PG86100 using xda premium
No, mistake using tapatalk on my phone, anyways as I am a gsm phone and you already have a thread opened, wait for an answer from someone as I have no experience with cdma evo's, I would advice you to put more info as what rom you are using, hboot, firmware and service provider
sent on my Evil Evo running the special sauce kernel
It says:
UNLOCKED
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.0008
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
Jul 15 2011, 14:39:25
Kernal Version
3.0.16-ge733189
[email protected] #1
SMP PREEMPT
(everything else is identical to yours, I think)
Baseband Version
11.77.3504.00U_11.25.3504.06_M
Build Number
1.11.401.110 CL68035 release-keys
Browser Version
WebKit/534.30
Yes, new firmware, what I would try is in recovery wipe all partitions except sdcard, wioe dalvik and cashe and factory wipe, then reflash the rom, I do have a custom kernel which might interest you, I do know that some people have had issue's with the viper rom, pm me if you want more info
sent on my Evil Evo running the special sauce kernel
Could you please help provide some step-by-step instructions, assuming you can remember them? Sorry. D:
Ok, 4ext recovery is hopefully what you have installed on your rooted phone? Have you made a nandroid back up of your existing rom?Boot into recovery you will see wipe and format, press that and you should see down near the bottom format all partitions except sdcard, press that also on that screen you will also see wipe dalvik & cashe and factory wipe. Then install zip from sd card and find the rom zip and flash, and wait, now just to let you know all your data will be erased, so contacts should be back up with gmail
sent on my Evil Evo running the special sauce kernel
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
ReversaI said:
I have ClockworkMod, actually. o-o
Should I get 4ext instead?
Click to expand...
Click to collapse
yes that could be why you have an issue, 4ext is much better and prefered
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Since your phone is rooted, you can just use the 4ext app to install the recovery. See my Web signature for a link to the free version.
Read, Search, Read again, ... Then Ask with Tapatalk 2
ReversaI said:
Is there a way to get rid of one and add the other? Like, flash a new recovery or something?
Click to expand...
Click to collapse
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
flashallthetime said:
I believe if you install 4ext it over rides cwm but it was months ago since i did the upgrade, viper rom has an aroma installer which works much better with 4ext recovery, who rooted your phone?
Click to expand...
Click to collapse
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Still working on it...
ReversaI said:
Still working on it...
Click to expand...
Click to collapse
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
---------- Post added at 11:57 PM ---------- Previous post was at 11:50 PM ----------
coal686 said:
It will overwrite, so no need to erase first.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
flashallthetime said:
yap it;s so easy just read the recovery b4 you make any selection and take your time
---------- Post added at 11:50 PM ---------- Previous post was at 11:47 PM ----------
us old folks forget things:laugh: first sign of dementia :laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
i'll give you the apn's for rogers as I remember them by heart
Name rogers
apn rogers-core-appl1.apn
mmsc http://mms.gprs.rogers.com
mms proxy 10.128.1.69
mms port 80
apn types default,supl,mms
those are the settings for mobile and mms
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
spirithandler said:
Ok here is the deal you flashed Vipers ics rom unless you flash the latest kernel from that other guy you are going to experience random reboots.
So my suggestion is go download that other guy's kernel and install it.
Click to expand...
Click to collapse
gave him it already:good:
List of attempted solutions that have not worked:
Wiping everything (and formatting it) except for SD Card.
Wiping (and formatting) the SD Card
Installing a new ROM
Flashing a different kernel
Factory Resets
Wiping Dalvik & Cache
Wiping Dalvik/Cache BEFORE & AFTER installing a ROM
Stuff I haven't tried:
Re-locking the Phone
Reinstalling a stock RUU (not ROM)
Unrooting
Welcome to the world of the EVO 3D. Hate to be the one to say this but it's just one of those 3ds. Mine had random reboot problems and lockups no matter what ROM, kernel, firmware, root access, anything. Just happens to a lot of them. Some people report success with relocking and unlocking the bootloader and making sure you're S-Off but I've tried it all.
Maybe that's not the case for you but it seems to be for a lot of people.
You can follow me on Twitter - @NotSo1nter3stin
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
So im fairly new to unlocking, flashing, etc. I have a HTC One M8 for AT&T that im trying to unlock to use with different carriers. After reading a bit I realized that I had to unlock my bootloader, root, install s-off before I could achieve my goal. I used htc-one.wonderhowto. com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444 to root and unlock my bootloader. Followed the guide to a T and all was fine. Then I was going for S-Off and here's where I encounters my problems. I used htc-one.wonderhowto. com/how-to/get-s-off-your-htc-one-m8-install-custom-firmware-mods-0154461 guide and this is where I believe I fudged up bad. Step one says to download InsertCoin from insertcoin-roms. org/category/devices/onem8 this link. I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM and that's why im having this problem but im not sure. I followed each step with the exception to Step 3 which is also where I fudged up. I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything. At step 5 my life changed forever..lol.. but when I flashed it , it said failure. I tried to follow the steps again but it kept failing to flash. So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. Which says ***unnlocked*** and ***tampered*** at the top and im stuck. Please someone help me and tell me what to do.
I recently deleted my OS by my stupidity. I fixed the issue by side loading a stock Rom via adb/twrp sideload. Saved me. There are tutorials on how to do this. Just Google search. You could also put a stock Rom on an external sd and flash that way. Don't have a link to the stock Rom I used, but it's in the resources thread in general section. Hope this works for ya
Sent from my HTC One_M8 using XDA Free mobile app
vansslamcityjam said:
I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM
Click to expand...
Click to collapse
The file you downloaded is if you were already on InsertCoin 4.0.6, and updating to version 4.0.7, which was not the case for you. You should have downloaded the full ROM, and that is likely why the flash failed.
If you ever have any doubt about what you are flashing, this should be a red flag to STOP and either read and research some more, or come on here and ask.
vansslamcityjam said:
I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything.
Click to expand...
Click to collapse
That is why you make a TWRP backup before wiping anything.
vansslamcityjam said:
So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. .
Click to expand...
Click to collapse
Did you specifically wipe system in TWRP? If so, that is where the OS is stored, so of course wiping it means you have no OS.
I do not advocate wiping system when flashing ROM, especially if you are new to this. Reason being, it already gets wiped when you flash a ROM anyway (so its redundant). Also, if the ROM fails to flash, you will still have a working OS if you did not wipe system manually. As stated on the wipe screen in TWRP, the default wipe (data, cache, and Dalvik) is all that is usually needed. It says this for good reason.
All you need to do is download a ROM to your computer, and either adb push to the phone, sideload flash, or copy it to a removeable MicroSD card using a USB card reader. Then flash in TWRP.
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....
Hi a month ago i flashed twrp 2.8.7 on my M8 to make backups and use helium for app backup (with supersu). today an OTA update came out, so i flashed back the stock recovery and started the OTA update. it went through but it hang at the white HTC One startscreen. after 15 mins i shut it down and rebooted it.
it showed the white screen with the small htc logo and then immediately wents black.
the power button does not respond so i did a "soft reset" (powerbutton and vol+) but that just brings it back in the unusable state.
what can i do now?
can be closed, after the battery drained i was able to restore it. (damn phones without removable batteries)
I'm having the same problem, I received a message last night that an update was downloaded to my phone. Sometime in the middle of the night my phone restarted and it's now frozen at the htc one splash screen.
My bootloader is unlocked and the phone was rooted, but have stock recovery. Also, my phone was encrypted.
I was able to get into Fastboot by holding vol-up+pwr, then when the screen goes blank immediately switch from vol-up to vol-down. I tried factory reset from Fastboot menu and also from the Recovery menu, but problem remains. I also loaded TWRP through Fastboot and tried Data Wipe, but still doesn't work.
Any suggestions?
dwestall said:
I'm having the same problem, I received a message last night that an update was downloaded to my phone. Sometime in the middle of the night my phone restarted and it's now frozen at the htc one splash screen.
My bootloader is unlocked and the phone was rooted, but have stock recovery. Also, my phone was encrypted.
I was able to get into Fastboot by holding vol-up+pwr, then when the screen goes blank immediately switch from vol-up to vol-down. I tried factory reset from Fastboot menu and also from the Recovery menu, but problem remains. I also loaded TWRP through Fastboot and tried Data Wipe, but still doesn't work.
Any suggestions?
Click to expand...
Click to collapse
I'm in the same boat. My rooted, s-off but otherwise OEM phone updated itself and now hangs at boot. (I haven't tried anything yet that would wipe my data.) Other weird issue I've seen (posted elsewhere) is that my external card won't keep writes made within TWRP (backup show up one minute in TWRP's file manager, then the new ones disappears a few minutes later).
I was able to restore an old nandroid backup I made and stored on my PC, so now I'm at least back up and running though with an order version of Android (4.4.4). When I checked for updates it says I have the latest. Hopefully, it will eventually update.
I wonder if my device encryption caused problems with the update. Does anyone else use device encryption? Did you have problems with the update?
generalprobe said:
Hi a month ago i flashed twrp 2.8.7 on my M8 to make backups and use helium for app backup (with supersu). today an OTA update came out, so i flashed back the stock recovery and started the OTA update. it went through but it hang at the white HTC One startscreen. after 15 mins i shut it down and rebooted it.
Click to expand...
Click to collapse
Where did you find the stock recovery? Thanks.
sorry i did not see your post @indiana99
first do the following please: fastboot getvar version-main
and then proceed to the site here: http://www.handy-faq.de/forum/htc-one-m8-firmwaresammlung-ruus-otas-backups-t301918/#comment-2710920 and find a matching version.
when you found one, for me it was 4.16.401.10 but i have an unbranded m8 you proceed with these commands:
fastboot flash recovery name_of_the_recovery.img
and then afterwards
fastboot erase cache
Thanks.
generalprobe said:
sorry i did not see your post @indiana99
first do the following please: fastboot getvar version-main
and then proceed to the site here: http://www.handy-faq.de/forum/htc-one-m8-firmwaresammlung-ruus-otas-backups-t301918/#comment-2710920 and find a matching version.
when you found one, for me it was 4.16.401.10 but i have an unbranded m8 you proceed with these commands:
fastboot flash recovery name_of_the_recovery.img
and then afterwards
fastboot erase cache
Click to expand...
Click to collapse
Thanks.
generalprobe said:
first do the following please: fastboot getvar version-main
and then proceed to the site here: http://www.handy-faq.de/forum/htc-one-m8-firmwaresammlung-ruus-otas-backups-t301918/#comment-2710920 and find a matching version.
Click to expand...
Click to collapse
He won't find the matching version on that page. AT&T is 502, which is not listed.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
generalprobe said:
when you found one, for me it was 4.16.401.10 but i have an unbranded m8
Click to expand...
Click to collapse
Then you're posting to the wrong forum section, this one is specifically for the AT&T version.