Related
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
I bet you got a refurb that someone previously rooted. If they used revolutionary then you retain S-off even on hboot 1.50 when the refurb facility repaired the device. Why don't you check if you're S-off?
It was S-On. That was the first thing I checked while walking out of the store. S-On 1.50.000
How strange. Hopefully people will keep coming to the thread and ask the right question. With the right question, the right answer will come to shed some light on what is special about your scenario.
Unfortunately that will not be me, because I have hboot 1.4, thus have less knowledge on the HTC unlock method.
Hopefully this has happened to someone else. I'm not sure why it happened. :O
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
umm i have hboot 1.50 unlocked htc method and i can flash any rom or kernal i want by just booting into recovery through fastboot its an extra step that takes about 10 seconds with a copy and paste of 2 commands from dos prompt
Yeah, I'm not sure why there's this myth that you can't flash kernels with 1.5, just need to load recovery in fastboot. Only limit I know of for 1.5 is that I can't use boot manager (if I'm wrong, let me know because I would love to use it). Either way, doesn't sound like OP was flashing through fastboot, which is odd.
Sent from my HTC Evo 3D using XDA App
saboture said:
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
Sounds like after unlocking with htc method you never disconnected your phone from PC and directly booted recovery from fastboot when you flashed TWRP .
So there's nothing new, i guess.
Every hboot1.50 user can flash kernels whether it is sense kernel or AOSP......
You can also use Flash image GUI to flash custom kernels from within the running android environment too.
So far JUST using HTC's unlock method I'm able to do the following
Flash custom roms through recovery like normal
Flash custom kernels through recovery like normal
Perform Nandroid backups/restores of EVERYTHING
UNABLE TO FLASH A CUSTOM SPLASH SCREEN
I thought this was going to be horrible going from a 1.40.000 device to 1.50.000 but honestly it's exactly like when I used Revolutionary to unlock my 1.40.000 device. And yes - I did leave my USB cable hooked up from start to finish. Hopefully other people will see this thread.
I tried Flash GUI and I couldn't get it to work for me so I guess I'm grateful. I'll check if I can install a splash screen once I post this and edit with the update.
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
You can flash kernels through fastboot. But you stated that you booted into recovery using power button, so it doesn't sound like you used fastboot....
You didn't use the flashimage GUI app, did you?
Sounds strange to me. Did you check the kernel In settings after you flashed? Don't think Its possible for stock kernel to support miui, but I suppose its possible.
Either way, you had something happen that shouldn't have. Either got a kernel to flash in a way that it shouldn't have, or got a rom to run on a kernel that shouldn't be compatible.
Another possible thing....I wonder if the 2.08.651.3 update did something that allows for you to flash kernels now. We know it wasn't possible on the .2 software, has anyone tried it with. 3. Doubt it made a difference as it was supposed to be a security update only.
Who knows. Ill give it a shot tomorrow to see if I can flash kernels without fastboot or flashimage GUI.
Sent from my PG86100 using XDA App
If you can flash a splash or radio then you should seek out a dev and let them know. They would probably have you do some tests. Might help achieve s off on 1.50
Sent from my PG86100 using XDA App
thos25 said:
You didn't use the flashimage GUI app, did you?
Click to expand...
Click to collapse
I tried it but when I booted into miui I got stuck at the boot screen. Miui boots in about 30 seconds or so on a fresh install but I was there for over 10 minutes.
Right now my phone is flashing Eternity 3.0 - R39 followed by Anthrax kernel. I'll let you guys know in a sec.
Edit: Well, the kernel flashed successfully but I'm freezing in the middle of the boot screen. Gonna try another kernel
Okay while booting Eternity 3.0 R39 I froze up mid boot screen. I remembered seeing a post about it freezing and I found it here and did what he said to do and it all works fine now. This is after I flashed rom+kernel in recovery then rebooted.
saboture said:
I tried it but when I booted into miui I got stuck at the boot screen. Miui boots in about 30 seconds or so on a fresh install but I was there for over 10 minutes.
Right now my phone is flashing Eternity 3.0 - R39 followed by Anthrax kernel. I'll let you guys know in a sec.
Edit: Well, the kernel flashed successfully but I'm freezing in the middle of the boot screen. Gonna try another kernel
Click to expand...
Click to collapse
Yeah. I have trouble with flashinage GUI as well. Funny thing is my issues with it were with miui as well.
Sent from my PG86100 using XDA App
saboture said:
Okay while booting Eternity 3.0 R39 I froze up mid boot screen. I remembered seeing a post about it freezing and I found it here and did what he said to do and it all works fine now. This is after I flashed rom+kernel in recovery then rebooted.
Click to expand...
Click to collapse
Good stuff. Did you check to see if you can flash radio or splash?
Sent from my PG86100 using XDA App
thos25 said:
Good stuff. Did you check to see if you can flash radio or splash?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm unable to flash a splash, and I've never flashed a radio before.
But as of right now I can flash kernels/recoveries/roms from TWRP. I'll try flashing a bootscreen with Rom Toolbox real quick just for extra measure.
Edit: can flash custom boot screens. One thing I cant seem to do though is take screenshots with screenshot it. When it saves it's always corrupted and wont let me transfer the screenshot to anything.
From what I gather, the questions you have answered still haven't shed any light as to whether your phone is behaving in a matter that is the same anyone else in your situation would experience? If it is still in fact behaving different than what we would expect it to I think the suggestion given to you to contact a Dev would be best. You may end up and be able to help the community achieve a more comprehensive solution to the root process.
Sad Panda said:
From what I gather, the questions you have answered still haven't shed any light as to whether your phone is behaving in a matter that is the same anyone else in your situation would experience? If it is still in fact behaving different than what we would expect it to I think the suggestion given to you to contact a Dev would be best. You may end up and be able to help the community achieve a more comprehensive solution to the root process.
Click to expand...
Click to collapse
Yeah, I was thinking the same thing.
Sent from my HTC Evo 3D using XDA App
could it be possible htc updated their unlock process to allow access to the boot.img without using fastboot?
ok. so I finally got around to trying to flash a kernel without using fastboot to see if it would work.
It did not. Like others have reported, it will say that the flash is successful, but when I go into the "about phone" menu, it did not change.
I have CM7 (secretpartymeow) on it now with stock (as in whatever kernel came with the ROM) kernel. Tried flashing infected Anthrax (aosp). No luck.
It is indeed looking more and more like your phone is a bit of an anomoly. I would suggest contacting one of the devs over at TeamWin to let them know what you are able to do.
This is my first time trying to ask help on the forums, considering i've never run across a issue of this magnitude with my HTC Evo 4g before. So please do try to help me out if its in the wrong thread, etc..
Anywho onto the problem
im not sure how to classify my problem
I have a htc evo 4g rooted, Via revolutionary method, im not sure if this plays a part in causing my htc evo 4g to reboot randomly every 1-5minutes.
This problem only comes up when i flash any other rom on my device. I first tried flashing Fresh Evo 4.3.3and after 1-5 minutes of use my phone goes into a reboot mode (when i attempt to download anything through market place, or heck i leave the phone idle).
I had also tried flashing the MikGinger - Re-Eng GB Sense (3/9/2012)
I did wipe data/factory reset
wipe cache partition
and also wipe dalvik cache 3x before each rom install.
This definitely didnt help what so ever. What my issue is, is that the stock rom (root enabled) android 2.3.3 functions perfectly fine but every other rom i attempt to flash works to the extent of 1-5 minutes idle or not. It forces a reboot. Oh and the kernel used on the android 2.3.3 rom is freedom-v0.8.5-UNIVERSAL-signed.zip Its the only kernel that runs stably on my htc evo 4g, enabling tethering, and full scale rooting, with semi stable functionality
Heres the current stock recovery menu version when i hold down Power and +volume
-Revolutionary-
SUPERSONIC EV2T2-3 Ship S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANE-ATMEL224_16ab
RADIO-2.15.00.05.02
Mar 8 2011, 17:02:15
i also have clockworkmod Recovery v5.0.2.2 installed.
*Notes*
I always make nandroid backups, and i keep multiple ones backed up on the pc and phone for just incase measures like this one.
Im unable to diagnose what exactly my phones malfunction is so anyone who can provide useful info on how to diagnose the problem please do give me some advice, as everything else i've tried so far has failed (flashing, unrooting, re-rooting revolutionary method).
I'd also appreciate any advice that doesn't point me towards unrooting again and returning my device (as this is the 2nd htc evo 4g i have gone through, and the sprint repair center techs are idiots as far as im concerned. Their replacement htc evo's come shipped out refurbed and updated hboot which is harder to root and the stories go on and on.)
Try switching to Amon Ra recovery. You can use the original version - latest version is 2.3, or use the Amon Ra style recovery, I believe that the latest version is 3.11. Flash one of those as PC36IMG.zip via hboot.
From there, wipe everything except the SD card and battery stats, then flash whichever rom you want. Don't flash a kernel, just let it boot up and sit for at least five minutes. Then flash whatever mods you want to flash.
Hopefully it's just that things aren't being wiped properly - CWM is known for this on the Evo. Wiping system and boot via Amon Ra will hopefully get you on the right track.
If not, Evos can have a reboot issue that requires a replacement. Unfortunately if it doesn't do it on the stock rom then reproducible the problem for Sprint may be difficult. Hopefully it won't come to that.
alright ill give it a go, i did a system restore, and rolled back my phone to android 2.3.3 I'll try doing amon recovery later on tomorrow or come sunday. I need my phone to be in a operable stat to function for work. I'll be sure to post my results though. In the mean time if you can post a link (i dont mean to be lazy) just im heading to bed now.
And yes it is hard to reproduce errors for sprint techs. They think all it requires is a simple factory reset, and then install the most up to date RUU and it fixes the problem. If anything it makes the problem worse, as this is what happened with my first htc evo 4g (from launch). Except it caused the phone into a hard core brick like state. it literally locked you out of every function but dialing 911.
Add in:
Forgot to mention i updated my
-Revolutionary-
SUPERSONIC EV2T2-3 Ship S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANE-ATMEL224_16ab
RADIO-2.15.00.05.02
Mar 8 2011, 17:02:15
to
-Revolutionary-
SUPERSONIC EV2T2-3 Ship S-OFF
HBOOT-6.16.1002
MICROP-041f
TOUCH PANE-ATMEL224_16ab
RADIO-2.15.00.12.19
Mar 8 2011, 17:02:15
(Just the radio was updated, updating radio did more than enhance signal quality it also broke some system functions, and alleviated other issues like glitchy rebooting bugs).
Its notable that after re-installing a backup of my android 2.3.3 alot of things restored broken (Broken links, that a fix permissions wouldnt fix), so i did another
wipe data/factory reset
wipe cache partition
wipe dalvik cache
from within CWM. (Im still surprised i havent borked my RSA keys yet, from the 39 times i have attempted reflashing both fresh & mikginger{Regardless a new rsa key backup was made})
{Question, since i have 2 RSA key backups, one from my original HTC EVO 4g, can i use them on the new device, or flash it to another 3g/4g enabled hotspot considering it is a active and available key? Or will it only function on the htc Evo 4g it was binded with (MAC address wise?) I havent tested it yet, and i dont know if ill set off red-flags. Hence the question.}
Then restored the phone, i noticed alot of things changed, like suddenly a vast majority of quirky reboots disappeared (Overclocking cpu suddenly doesnt cause a forced reboot if overclock is left to long due to overheat, it instead stalls and then crashes sense, and functions again instead of rebooting) a very nice improvement.
I've almost reinstalled everything through titanium backup, but only certain programs, im trying the one by one install, method, and seeing if this will beable to be upgraded to fresh 4.3.3 because if it can, then ill be a happy camper. Till then, ill explore your option, and if it backfires ill continue testing out my new fresh install of android 2.3.3 (rooted), with ICQ removed, and 98% of the stock apps removed. See how far i can get on getting my phone to run like android 2.3.2 the most stable android os i have ever run
(I dont want to restore my android 2.3.2 backup though to buggy, the only qirk was the texting bug and dialer bug, if its possible to port over the 2.3.3 updates to the text bug, and dialer bug, please do tell me as attempting to install from 2.3.3 into 2.3.2 tends to make the system run into a endless boot on 2.3.2)
I'm getting ready to head to work, but I just wanted to let you know to NOT restore a wimax backup from one phone to another. Toss it, it has no use now.
Amon Ra is in the Evo Development section. If I have time later tonight at work I'll post the link, but for now I gotta run. I will check back in with you though.
plainjane said:
I'm getting ready to head to work, but I just wanted to let you know to NOT restore a wimax backup from one phone to another. Toss it, it has no use now.
Amon Ra is in the Evo Development section. If I have time later tonight at work I'll post the link, but for now I gotta run. I will check back in with you though.
Click to expand...
Click to collapse
Do you mean install this version of Amon Ra? Just to clarify Amon Ra and CWM have their own ways of making a full backup, and i cannot just restore a backup made with CWM via Amon Ra, or can i? Im new to using Amon Ra, as i never trusted it much (to worried it may cause more harm than good, as im more use to using CWM)
Edited:
Yep i tried Amon Ra, it didnt work. I tried reflashing Fresh 4.3.3 2x and it ended it the same 1-5minute idle or not before reboot failure, same with MikGinger - Re-Eng GB Sense (3/9/2012). Nothing works but the stock roms with SU added in. I tried with my android 2.3.3 backup, and android 2.3.2. It seems my phone is incapable of working on android 4.3.3 but it works on all previous builds. It makes no sense to me though why it is like this, anyone think they can explain as to whats going on exactly with my phone?
supernet2ec2 said:
Do you mean install this version of Amon Ra? Just to clarify Amon Ra and CWM have their own ways of making a full backup, and i cannot just restore a backup made with CWM via Amon Ra, or can i? Im new to using Amon Ra, as i never trusted it much (to worried it may cause more harm than good, as im more use to using CWM)
Edited:
Yep i tried Amon Ra, it didnt work. I tried reflashing Fresh 4.3.3 2x and it ended it the same 1-5minute idle or not before reboot failure, same with MikGinger - Re-Eng GB Sense (3/9/2012). Nothing works but the stock roms with SU added in. I tried with my android 2.3.3 backup, and android 2.3.2. It seems my phone is incapable of working on android 4.3.3 but it works on all previous builds. It makes no sense to me though why it is like this, anyone think they can explain as to whats going on exactly with my phone?
Click to expand...
Click to collapse
I think it might be that you needed to update your radio and that fixed some things, but also I notice that your HBOOT version is not the right version. that version is only used to downgrade so you can gain s-off. use the hboots in this thread http://forum.xda-developers.com/showthread.php?t=715485
try that and see if it works
I cannot for the life of me coax my Rezound into creating a nandroid backup. I kind of a n00b, so I'll give you my info and how I rooted.
ROOT
I rooted by following Scotty's noob friendly root guide: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
I followed his instructions for "temporary recovery" which installed Amon RA 3.14
MY CURRENT SOFTWARE
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
FIRST ATTEMPT
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were.
I selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection.
It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
SECOND ATTEMPT
I installed ROM Manager.
I selected "Flash ClockworkMod Recovery" ... not realizing exactly what I was doing. None the less ...
I booted into CWM.
CWM freezes while making a nandroid backup. Every time. Battery pull. Every time.
THIRD ATTEMPT
I followed Scotty's "temporary recovery" instructions to install Anon RA 3.15 (different version this time)
The md5 in the command window did not match the md5 at download site (http://forum.xda-developers.com/showthread.php?p=23781936)
Seeing no alternatives, I flashed it anyway ... Nothing catastrophic happened.
Did same thing I did in the first attempt, and it gave me the same message.
Anyone have any other ideas?
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
You realize that after the OTA your backup won't work right? If you're just trying to cover yourself between now and then, maybe just copy your whole system and data partitions manually??
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
I don't understad why I can't enjoy these things and create a nandroid backup of my current ROM in case I decide to try other ROMs.
Are you saying that a permanent recovery is the difference between it working and not working?
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
bloodymurderlive said:
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
Click to expand...
Click to collapse
I can't say for certain because I've never gone through that situation before, but if you want to be stock...Why not just let the OTA update you to ICS stock and keep it as it is? Do you really like Gingerbread Stock that much? I guess I just don't understand your reasoning behind all of this. If you were flashing a new ROM after wiping everything in a recovery I would understand your need to nandroid...
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
bloodymurderlive said:
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
Click to expand...
Click to collapse
The firmware that is updated with an OTA update will most likely break Gingerbread compatibility if you try to restore a temporary nandroid backup.
With S-Off none of this would be a problem because we would just flash old radios and kernels right from recovery. HTC makes it difficult to downgrade
uToTMeH8
I want to have the option to return to whatever ROM I want.
If I OTA-update to ICS, I want the option to return to GB (especially given how notoriously buggy OTAs are).
If I install a custom ROM, I want the option to return to stock if I don't like it.
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
bloodymurderlive said:
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
Click to expand...
Click to collapse
This is why everyone is going mental about s-off in this thread:
http://forum.xda-developers.com/showthread.php?t=1578449
Honestly unlocking your bootloader, flashing Amon-Ra and backing up your stock is the way to go. I've had my phone unlocked for 3 months with no problems and the devs on this site are amazing! You're going to want to try every gingerbread ROM once you get really good at backups and flashing. I was getting around 6-8 hours on the stock ROM for battery life. I flashed NilsP's Business Ginger Sense and I hit 30 hours. It's ridiculous how much better battery life is after stripping the ROM down and adding tweaks.
This Toolkit really makes it very easy...Good Luck!
http://forum.xda-developers.com/showthread.php?t=1504824
The error is commonly not enuff space on the SD,or insufficient battery charge.
It has nothing to do with leaving the stock recovery in place.
The only reason you won't be able to restore your gb backup after ics is the fact that it takes a different hboot and.radio,and until the s off method is released,there is no way to revert those. With htcdev,you can only go fwd,not back.
MrSmith317 said:
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Click to expand...
Click to collapse
uToTMeH8 said:
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
Click to expand...
Click to collapse
the reason for leaving the stock recovery is simple: a custom recovery will not install an OTA.
if you leave the stock recovery in place,the OTA will happen,quite naturally,and without isrupting your personal data. sure,it will break root,and anything youve frozen will pop back up,so you do have the minor inconvenience of re-freezing some bloat,and re-launching the temp recovery to flash root files. not a big deal,IMO. remember,htcdev is more like s-off in that you will always be able to root,or re-root. its not an exploit that will disapear.
even if a person wishes to permanently install a recovery,i strongly recomend to get into the habit of launching recovery from fastboot when messing with your phone. as we know,htcdev only unlocks boot,recovery,and system,and we cannot write 'boot' from 'recovery'.
however,launching recovery from fastboot(what ive been calling a 'temporary' recovery) does allow recovery to write to boot. it doesnt do much good(yet) for flashing,as rom devs are still not including the neccessary scripts to install the kernel,but it does allow you to restore nandroids without a seperate kernel flash,making them quicker and easier.
until you switch to ICS firmware(i.e.,install the leaked ruu,or take an OTA) you can flash,backup,and restore any gingerbread roms,and GB firmware based ICS roms,as you desire.
again,what the guys were trying to say when the said you cant restore the GB backups after ICS is simply because the hboot and radio are different. sure,you can physically power up your recovery and restore a GB backup with ICS hboot and radio(firmware),and it will restore,and even boot. you will just have issues due to the incompatible firmware,such as the disapearance of your SD card
hope that helps clear a few things up for you. sorry the above reply was short,i was trying to reply on my phone at work
edit:
one last thing: since youve downlooaded rom manager and used it to flash clockwork recovery,you now have a permanently installed clockwork recovery. you can still temp launch amon with cw in place,but you now are missing the stock recovery,and as such will not be recieving OTAs. if this is important to you,you need to download the stock recovery,and permanently install it(fastboot flash recovery recoveryname.img)
http://www.mediafire.com/?wb21d2gdurui2c6
Thanks Scotty!
First, I'm a complete moron and assumed that my 32GB microSD had enough space. I deleted a movie and made my backup.
One question though about the CWM recovery ... I was concerned that it was permanently installed. However, I attempted to boot into recovery from my phone (power + volume down), and it booted into what looked like the stock recovery ... No dark Amon or CWM recoveries ... Is it possible that CWM didn't permanently flash after all? I know that I have been in both Amon and CWM, and CWM was installed from within the ROM Manager app ...
Are you sure you were in recovery, because power and volume down boots to the bootloader, called boot, which is entirely different.
Sent from my ADR6425LVW using xda premium
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
bloodymurderlive said:
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
Click to expand...
Click to collapse
Yes, Once and OTA is released it should not be long till someone posts here the zip install of the same OTA. Give it another day and I say you will see a cleaned up debloated, rooted etc... zip of the same OTA. These days there is really no need to rush for the OTA downloads, let the Dev's do their magic and offer you something better than Big Red will offer.
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
I've grown tired of my ARHD ROM mainly because it lacks the Update functions and not being able to at least update my profile means I often don't have signal or just 1x data. That makes my apps sloooow when using the internet. Plus I'm ready for something new.
I finally got s-off, so I'm good there. I was thinking about going with CyanogenMod 10.1 - WILD FOR THE NIGHT, but it seems like MMS isn't working well and that's something I use all the time. It seems like most ROMs want HBOOT 1.5 and I'm on 1.58. What's the easiest rollback method? I used the JuopunutBear method to get s-off, but it's really tedious to boot a live CD, plus their instructions for their older HBOOT aren't quite clear enough for me.
Secondly, about the ROM, the features I care about most are:
- Making calls
- Web surfing
- SMS/MMS
- Camera (3D not needed)
- wimax
I also would like something that's a bit more snappy. Going to JB would be nice, but if it's more sluggish on my hardware then I'll stick with ICS.
I found some previously recommended ROMs but they don't seem to be maintained anymore.
Thanks much.
Changing hboot is easy. Just copy the hboot PG86IMG.zip to the root of sdcard and reboot into bootloader. It will flash the hboot. Now at this point I pull the battery cause it will only let you reboot. Remove pg86img from sdcard and boot into recovery. Always wipe all partitions on the phone cause the hboots can have different partition sizes. Now flash your ROM of choice. If you need hboots I have them on my goo. Goo.im/devs/jlmancuso.
You can go up and down without losing root. So flash away.
Sent from my PC36100 using xda app-developers app
Thanks. That's a big help!
snokarver said:
Thanks. That's a big help!
Click to expand...
Click to collapse
As always if you need any help I can be found on Talk/hangouts [email protected]. Feel free to hit me up.
The more we share the more we learn.
I might recommend the MiUi v5 Rom. I have had a lot of success with it and it seems to be flawless. I currently don't have the ability to post links, but it is in the development tab.