Related
Most of the roms seem to lack any real info about installation. I successfully rooted my phone but I dont want to brick it trying to install a rom that requires a certain radio version or something. Is this even a concern? Or should I be able to just flash to any rom without any real worries?
all ROMs install the same way, from Rom Manager or Clockwork from Recovery.
as far as radio goes, just about any are compatible with the MR 2.5 and if thats not the case it will tell you. even then, just from having the wrong radio/rom combo cant brick your phone. its when you try to flash a corrupt radio that that can happen.
Look in stickies under
Development
Sent from my ADR6400L using XDA Premium App
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.
I recently tried flashing several different ICS roms and got the same result with each. The phone turns on, but after sitting on the initial Motorola boot screen for a few seconds, the screen goes black. From what I can tell, it is not the roms themselves that are causing it.
I follow all of the wipe instructions to the letter.
I am able to boot into safestrap recovery and do a restore.
One of the roms I tried (I can't remember the other)
Gummy Resurrection rom
Current stock version: 6.12.173 (latest update)
Does anyone have an idea as to what the problem may be?
Are you GSM or cdma?
Sent from my Droid Razr using Tapatalk
Based on the stock version I would assume Cdma. What version of Safe strap? I also assume since you can go into Safe strap you can access the internal memory and external sd card. What cwm are you using? So what other Roms did you try? Were you not ever able to get anything other than stock running?
I am using the latest version of safestrap (1.07)
I can access internal memory and SD card, as I am able to restore my backup of the stock rom.
I'm not using CWM, I'm using safestrap recovery.
I think the other rom was |Aokp| |Icsrazr| |Kang| |4.0.3| Ab (it can be found on droidrzr.com)(I can't post links yet).
I haven't tried anything other than those two roms, but since I got the same result for both, I would assume that the issue affects any rom I try to flash. I can try to flash a different rom and see if that works.
Umm oh that takes alot of thought. No idea at this point. Only think I could say is ditch Safe Strap re install and start again. Im sure smarter people will give a say.
Maybe the update fixed something?
http://forum.xda-developers.com/showthread.php?t=1391900
I got a Gingerbread rom to boot correctly. Maybe both of those ICS roms have the same issue. I dunno lol.
Yeah lol ive flashed both kinds of Roms and always getting them to work. Currently on AOKP M4 | AXI0M | KANG | RAZR and loving it.
ICS roms requairs you to have CWM on boot recovery if I'm not wro ng.
The first thing I see is safe strap maybe he needs to re install or update for some reason.
I wasn't aware that there was a later version of safestrap out. That seems to have done the trick. ICS roms are now booting properly.
Sweet now enjoy some Roms.
So I have bootstrap installed now. Can i just load safestrap overtop of it? or do I need to remove bootstrap first?
IdowhatIwant said:
So I have bootstrap installed now. Can i just load safestrap overtop of it? or do I need to remove bootstrap first?
Click to expand...
Click to collapse
Remove the strap you don't want first
Ask us any Android Related Question @FeraLabsDevs on Twitter
I have had a Bad ESN Fascinate for a while that I was playing around with, trying to get it to work on Sprint... No go. Anyway, it was rooted with a stock GB ROM and I decided I wanted to try out some of the ICS or Jellybean offerings that XDA has in its forums.
To be honest, I am no noob, but I didn't do enough research to begin with. First I installed GeeWiz 2.9 Kernel, System, and 2.8 Recovery. I didn't like the 2.8 Recovery, so I tried to flash something else, but nothing would replace it. Then I tried to install Baked CM10 from the GeeWiz recovery, and it went downhill from there.
Long story short, I have ODIN'd back to stock EH03 and tried to update to a couple of CM10 ROMs using the guides I have found here and on a few other forums. I have a working install of Hacksungs CM9 build 5 as of right now, but I can't get any further.
After using ODIN to get to Stock EH03, I ODIN the CWM4 for CM7. 3-fingering brings me to CWM4 where I begin the install of CM9. When it examines the partition BML/MTD it reboots the recovery (took me a while to figure that out) in to CWM 5.5.0.4 where it finishes the CM9 install. When I soft reboot into recovery, I get CWM 5.5.0.4. According to the guides, this is where I would flash CM10. It runs the update, but when I go to reboot the system, it reboots into a recovery of CWM 6.0.1.4. Also, if I reboot the system from CWM5 without installing anything, it boots back into CM9 just fine.
I am pretty sure I installed CWM 6.0.1.4 sometime in the past, but to be honest I have no recollection of when.
My question is multi-part: How do I get rid of CWM6; why is it still there after all the repartitioning with ODIN (with and without PIT file), MTD partition formatting, etc; why can't I get CM10 to install?
While this is a fairly wordy post, I have to say, I do have a working Fascinate with CM9 that I am enjoying playing with. I just thought if nothing else, people might get a laugh out of my struggles with this phone, that is basically a web browser and toy.
FWIW I have seriously ODIN'd back to stock about 5 or 6 times today alone.
Thanks for any help or suggestions in advance.
Unlike Gingerbread and earlier, with ICS and JB kernels they include whatever version of recovery the developer wants to include.
Is there a reason you don't want the latest CWM?
Sent from my SCH-I500 using xda app-developers app
Its been awhile for me since I had to go back to stock, but unless something has changed the three finger reboot into cwm caused some problems when flashing. Try rebooting to recovery through power menu.
Some ROMs are requiring to be installed a second time to "stick" due to partition layout changes.
Sent from my SCH-I500 using xda app-developers app
Thanks for the info on the ICS and JB attached recoveries. I was unaware of that. Maybe that's where the CWM6 came from.
And it isn't that I don't want to most current, it just didn't seem to want to play nice with the ICS and JB Roms I was trying to installed.
Now my problem is that the phone won't boot when powered down from ICS. Glad this isn't my main phone.
Sent from my EVO using xda app-developers app
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
From my limited knowledge,,,
I know the fixed cwm is what you need to get out of a 3 finger boot loop,,, I've had to do that...
Cwm 6 is what runs and works with cm10/jb roms,,,
Causes no errors that I'm aware of...
No more 3 finger,, always use power button/reboot
Once you have started an install of say cm10 ... Let it run its course , so to speak,,, if it comes up with cwm5 or cwm6 then that is the one the developer designed it to work with,,,
Let it come all the way up,, and then reboot through the power button method always,,,, you'll get used to that quick enough , as i remember the old gb froyo stuff didn't offer this method
I keep a copy of the fixed cwm just in case i happen to accidentally 3 finger ever again...
Sent from my swagger
spikeekips said:
That's what I had read everywhere... NEVER 3-Finger into Recovery from ICS or JB. I still managed to do it a few l times when I wasn't thinking.
It definitely screws up the install. I can attest to that.
I just don't get why there are all three CWM versions present during the install, and if I am installing CWM4 fixed for CM7, and one of the other two is included with the ICS Rom, where did the 3rd one come from? Just a big, confusing mess
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Not sure if you are still looking for advice but here is a little guide that has not failed me at all. If you follow this then you should come to the latest JB rom that you want.
Click here
So I had some problems resulting in losing my OTA, and had to reinstall Stock ICS from the download link. Since then, I've been having lots of minor problems, needed to do a Nandroid restore once or twice. Just wondering if there is a conflict somewhere with my ROM/Kernel/Hboot/Radio etc. Most things are fixed with the restore, but the most annoying thing is my bluetooth headphone buttons have stopped working. (tested the actual buttons using another phone, they're fine).
Hboot - Juopunutbear 1.53.7777
Kernel - Coolexe's 4.4
ROM - RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe
Thanks
I've seen a lot of issues come from using cwm on the evo 3d. My suggestion and recommendation is to flash 4ext recovery.
You can get this recovery by downloading this called 4ext updater from Google play for free and flash 4ext with it. After that, reflash your stock ROM from it. It should eliminate your problem.
Jsparta26 said:
I've seen a lot of issues come from using cwm on the evo 3d. My suggestion and recommendation is to flash 4ext recovery.
You can get this recovery by downloading this called 4ext updater from Google play for free and flash 4ext with it. After that, reflash your stock ROM from it. It should eliminate your problem.
Click to expand...
Click to collapse
Thanks mate. It was more trouble than I wanted really, but it seems to have worked. I now get better benchmarks as well.
Cheers