Related
Ok... So a couple of days ago, I was having bootloop issues on Ineffabilis 1.3 using the Anthrax kernel. After doing a battery pull, I booted into the bootloader and then to recovery and found that my roommate, while playing with my phone, had flashed the ClockworkMod Recovery, I suppose through the Rom Manager app.
I figured it would be ok to do a full wipe and re-flash the rom since flashing the stock kernel didn't stop the bootlooping and I would just flash AmonRa back when I was done to do a backup.
Well, after doing a factory reset from CWM and getting errors thereafter trying to flash the superwipe and Ineffabilis, I rebooted the phone and skipped through the setup to get to the restart menu to get into the bootloader again to flash AmonRa. I was able to flash it, but now every time I try to get into the recovery whether from the restart menu, ADB, or through the fastboot menu, it automatically restarts the phone as soon as the recovery is loaded and goes back to the OS.
Has anyone experienced this and is there any way to fix it to get back into it?
Sounds like you have a ph image on your sd card. Just delete it and you should be fine
sent from ics land
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
ojdidit84 said:
I've long since removed all PH files from my phone, internal and external sdcard included, and even if there were that's never stopped my from booting directly into recovery from the restart menu or through ADB.
I've even gone as far as removing the external sdcard with the same result. It just boots into recovery and as soon as it loads for that split second, it automatically reboots to the HTC screen and back to Android.
I still have root and my phone isn't bricked. I just can't flash any roms or kernels in the future when we get our official ics update. WTB my EVO 3D's hboot 1.4 back...
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
what happens when you try to go to recovery...
i would just reflash a recoveyr in fastboot. cant hurt.
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork using rom manager, scott's tool, adb & fastboot, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow and using these methods to go back to AmonRa produce the same result. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
ojdidit84 said:
What it does is as soon as it boots to recovery, I see it load the recovery and then as soon as it loads, it's as if the phone automatically selects the reboot option and goes back through the normal boot no matter which method I use to boot into recovery.
I've done the fastboot method which flashed successfully, tried to re-flash clockwork, also used scott's flash tool which was also successful and it just seems as if recovery mode is borked somehow. I'm usually good at figuring these things out myself since I've been rooting and flashing since my first Sprint HTC Hero, EVO 4G, 3D, Epic 4G/Touch and I've never had anything like this happen before. Completely stumped .
Have done a search and haven't found anyone with the same issue so I have nothing prior to go off of. The phone works fine for now so I'm in no hurry since I still have root and thankfully Titanium Backup for my apps. Not sure what to try next at this point.
Click to expand...
Click to collapse
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
mjh68 said:
From hboot, choose factory reset and see if it boots you into recovery. I had a similar issue after running the new RUU, once I chose that it booted into custom recovery and i was able to reboot and then afterwards had no trouble accessing recovery.
Click to expand...
Click to collapse
Ok. I'll give that a whirl in the morning and see if it solves the problem.
Bump... I'm stuck with this issue...
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
phaedrus43 said:
Hi,
Spent the last two days trying everything I could think of to get a custom recovery loaded on my rezound with no luck. Have searched everywhere and short of trying to hex edit some code nothing has worked.
I was on a custom ICS rom and applied the 4.03.605.2 RUU (hboot 2.27). Was S-ON with unlocked bootloader. I locked the bootloader, installed RUU successfully, unlocked the bootloader with my token. I tried flashing amon-ra, CWM, TWRP many versions of each by fastboot and hboot (PH98IMG). The custom recovery is successfully written in each case, but i can't successfully boot into the recovery partition either from fastboot or hboot menu option. I can write the recovery.img file from the RUU zip, and all is good. Ultimately, I am just trying to install a custom ROM/root my device.
I tried the above advice about performing a factory reset. No Dice. So for now, I am stuck in Verizon bloatware land, and very unhappy about it.
Suggestions welcome. Thanks everyone.
Click to expand...
Click to collapse
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Thanks. Did try that, but not with phone off. I'll try both for good measure and let you know. Thank you fly...
Sent from my ADR6425LVW using xda app-developers app
Flyhalf205 said:
Hook up to PC. the phone can actually adb when turned off. or make sure ROM is booted with ADB turned on. It should connect to adb. Does it? Then your command would be "adb reboot recovery" after you have flashed a custom recovery. So what does it do when you try to enter recovery?
Click to expand...
Click to collapse
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
phaedrus43 said:
Hi Fly,
I was unable to get adb to see the phone when it was off with either a custom recovery or the stock recovery. When I rebooted to recovery from adb with a custom recovery installed, it attempts to boot to the recovery partition but fails and boots back to the OS (this is true when using adb, fastboot, and hboot to boot to recovery). When i reinstalled the stock recovery, it successfully boots to recovery using all methods.
i have tried other custom recovery versions, TWRP (preferred), AMON-RA, CWM Recovery...
annoyed.
Thanks Fly. Any other ideas?
Click to expand...
Click to collapse
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Flyhalf205 said:
I'm out of ideas. Since your s-on you can't go down to the OTA RUU and try there. Maybe someone else can spread some light.
Well one more idea. Boot your phone into Fastboot. Plug into computer and download a custom recovery to your computer. The command to use is "fastboot boot recovery.img"
If that does work then download http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and flash it inside of recovery. That will give you root inside your stock rom at least.
Click to expand...
Click to collapse
Hi Fly,
Nothing doing. Can't flash the attached in stock recovery, can't boot into any recoveries with stock flashed or with custom recovery flashed. Seems there must be some new security built into the new RUU? I did note one thing. When I first flash the RUU the hboot banner says relocked (as i have to relock to install an RUU). However, as soon as I flash anything to the recovery partition it adds a new white on black banner that says tampered. Now, i have seen that before when I s-off'd my rezound previously (returned to verizon for audio problems). I never did s-off this particular phone. I don't recall my first phone flagging a new recovery or this phone flagging a new recovery on the old firmware (i could be wrong though as i don't spend a lot of time in hboot).
Still hoping to put a custom recovery on this. Any other way to load a custom rom? i really want to run Neo's AOKP, as I had that on here before I RUU'd. In fact, i got into this position because I was going to s-off the phone, but I had a custom rom. I started looking for RUU's to restore to stock because controlbear wouldn't work with custom rom. Instead of installing an early ICS again, i opted to install the latest RUU.
I searched the forums high and low and wasn't really able to find anyone with this problem. I wonder if there is something wrong with the RUU? I checked the MD5sum and it matched. When flashing recovery i checked the mainver too, so it isn't that... I'm stumped.
This phone wasn't real popular and is gettting old now (man, the lifecycle on phones suck, I had my N1 through many roms and AOSP releases! These new phones are gone in 6 months, a year tops). I doubt anyone is going to trouble themselves to crack a new HBOOT on this phone (this is 2.27).
Only other things i can think (and I haven't tried yet) is trying zergRushing it for temp root to at least remove/freeze the bloat like I did with this phone when I first got it. Or if I can just get a rom installed without a custom recovery I don't flash as often as I used to and figure an upgrade isn't long off. Or if i could downgrade the hboot or install jb hboot...
Would love it if someone had something new to try.
Thanks so much again Fly and happy holidays.
Success! (but how?)
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
phaedrus43 said:
Ok Fly,
I don't get it... not at all. I tried, just for the hell of it, a little more tonight and my phone was happy to flashboot boot TWRP 2.2.2.1 SPECIFICALLY. I was unable to get other versions working or other custom recoveries. I have no IDEA why. I can only think that the recovery partition is too small for some recovery.imgs? but 2.2.2.1 is actually bigger than 2.3.3.0 that you compiled for the rezound. Anyway, i have ROOT! now, my first step before I dork with anything is to S-Off this bad boy so i can move around a little more. I will probably still leave the locked bootloader after that, just to keep me from n00bing up. Haven't tried flashing the twrp recovery yet, don't want to goof up my S-off chances or not give you a chance to ask a question.
If you want some forensics to help others out, please let me know. I am gonna leave this phone alone for a day in case you have questions. There HAS to be some lesson in here. Totally random to me. (last thought) i was running 2.2.2.1 before I ran the RUU... wonder if that has something to do with it?
Thanks again Fly.
Click to expand...
Click to collapse
Anytime :fingers-crossed:
Crazy how things work like this. But the recovery partition shouldn't be to small to flash a custom recovery. Good luck. Just sounds like one of those rare things that happens.
I don't want to be giving my friend the wrong information. When his sprint 3d was boot 1.5 I took it and soff it for him downgrading to 1.4. Now recently he upgraded to hboot 1.58 and it says relocked at the top. Of course he still has recovery and still is rooted.
My question is since his phone is soff can't he just still flash whatever with no issues? Does he have to do dev unlock again?
I own a rezound and have had many HTC devices and soff has always been the key to everything for me. Any help would be appreciated
With s-off there's no need to unlock his boot loader again. (For example) If he wants to flash an aosp rom, all he's gotta do is downgrade his hboot via boot loader.
Perfect. Already installed JP bear latest hboot and went to twrp. Making a backup now. That's what I was thinking but I wanted some confirmation. Its been a while since I messed with an Evo 3d
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
stkiswr said:
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
Click to expand...
Click to collapse
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
ramjet73 said:
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
Click to expand...
Click to collapse
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
stkiswr said:
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
Click to expand...
Click to collapse
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
ramjet73 said:
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
Click to expand...
Click to collapse
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
What kernel are you flashing with pa?
Jsparta26 said:
What kernel are you flashing with pa?
Click to expand...
Click to collapse
It doesn't come with a kernel?
stkiswr said:
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
Click to expand...
Click to collapse
Are you doing the "format all partitions except SD card" in 4EXT right before flashing the ROM? Make sure to give it plenty of time to boot since sometimes the first boot can take up to 10 minutes.
ramjet73
stkiswr said:
It doesn't come with a kernel?
Click to expand...
Click to collapse
Well go with ramjets suggestion and try format all partitions minus sdcard along with full factory data wipe and cache/dalvik wipe and see if it boots up all the way.( it couldn't hurt to do all the wipes two or three times before you flash the rom). Just to make sure everything was wiped all the way.
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Ok, try flashing a different kernel. Try the Mac kernel that's located in Mazda's aokp jb thread. I believe buttered toast came with pa that your trying to flash. It could also be a bad download as well. You could always redownload the rom as well to see if that works. You never know about these things sometimes.
stkiswr said:
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Click to expand...
Click to collapse
You've tried all the standard stuff to get AOSP ROM's to boot on the Evo 3D. At this point I can only suggest that you flash the 2.89.651.2 SPrint ICS RUU from here, then reflash a custom bootloader and recovery. That will make sure everything is in sync and has cleared up this problem for other users.
You don't need to relock the bootloader (although I think you said it is already relocked) when flashing the RUU if the phone is S-OFF.
ramjet73
Yes, I will try to download ROM again and also grab that kernel.
I soff this phone for him when it was hboot 1.50. Then I reverted to 1.40 via brick method to get it soff. He has ran some form of an hboot/radios update because he was told to do that. Now we are working together and I am trying to fix all his stuff and get him setup correctly. I have an soff rezound and am sure his phone isn't seeing the boot.IMG.
Now today his phone said locked or relocked am not sure. I went ahead an changed his hboot to a recommended 1.04eng hboot. Installed 4ext recovery via the app that was linked. I am downloading gangam style cm10 to test just to see if something will boot. It successfully flashed a sense based ROM and booted fine thru an aroma installer that came with the ROM. In the installer I stated it was soff and had no issues. I will try the ROM and it doesn't boot I will jump back to recovery and flash a kernel and see. Thanks very much for all the help
Well, I have done it all. Not much more I can do. He may try to run the ICS ruu later but I just can't get any cm10 jb based ROM to boot. Y'all have been more than helpful catching me back up to speed on the 3d and while I agree this should be flashing alas it is not booting. I am positive its just not accepting the boot img for what ever reason because it never makes it far enough after reboot from recovery. Just endless quick splash screen reboots.
No problem. I just wanted to add that a lot of users are having weird issues with paranoid android. ( I'm subscribed to the thread) so it could be that your phone doesn't like pa for some reason. ( Not a diss on Lens Flare at All) but he's been having some issues with the rom and is more than likely trying to work on it. Hopefully you can get gangnam style up and running or even aokp jb. If none of these work, I would go with ramjets suggestion and run a ruu and then back to Asop.
Edit: guess you already tried them. Hopefully you get some better luck after you try the ruu method. Good luck.
My Evo has been completely trashed and I have no clue what to do.
I have hboot 1.19 s-on and I did the HTCdev unlock, and I rooted it and have the latest version TWRP (i think 2.3.something) with SuperSU installed. I tried to flash a ROM that was supposed to be compatible with with I had but i guess not. Everything was going great but I was stuck on the CM boot screen. After about 30 min of it sitting in that screen I figured something was wrong so i reset it and went back into TWRP. Someone told me to download MeanRom and flash that because its kernel and rom would fix everything. Here's where things get weird. I download MeanRom to my computer and mount my phone in TWRP to move the file over to the phone and when i went to factory reset before flashing it it kept saying unable to mount SD card and Internal Storage. I tried to do a restore my phone to an old back up and that wouldnt even work. So I wipe both caches and try to flash MeanRom anyway. i got a failed error and my phone shut off. Now my phone will only go into the Fastboot thing on the white screen and when i try to go into recovery, it just stays on the TWRP loading screen, not even letting me into the recovery program.
Is there anyway to fix this? My best buy insurance has expired because i missed 3 payments since I'm away at school and not working a whole bunch. So my whole smash it to pieces and get a new one solution is no longer an option.
I'm on a mac by the way so is there something I can enter into terminal to fix this? I don't care about losing any files or anything I'll do whatever I have to, to fix this.
Thanks in advance
- Josh
Read om4's guide don't panic...hboot 119 s-on you have to flash kernels separately.
Sent from my EVO using xda premium
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
falconoble said:
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
Click to expand...
Click to collapse
How would i unroot if I cant get into SuperSU since i cant boot up my phone? Do I need to do that first or can i just run the RUU without Going into SuperSU and hitting Unroot?
Also what do I need windows for? Getting S-OFF? Or unrooting?
Also thank you! I really hope this work!
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
I'm sorry if this is a stupid question. But how do i re-lock it from fastboot?
U have to use the cmd window on your windows computer. I did it with mine before I ran dirty racun. It is a simple command but u have to be in the right directory ind the cmd line. Go through and look at the dirty racun guide and it tells u how to re-lock word for word I believe.
Sent from my EVO using xda app-developers app
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
jklatt747 said:
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
Click to expand...
Click to collapse
Turn on USB debug in devopleper options
Sent from a lens flare powered EVO LTE
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
Yeah i couldn't figure out how to do that. I would ask a question on how to do that and i just kept on getting the response of "google it" "look it up on youtube" or look in the forums. and I wasn't ever sure really where to find it because all my searches for it came up useless.
I just did the RUU on my phone and its finally back up and running! What a relief!!!
Now I'm going to try to get DirtyRacun s-off. How do I put a Custom Rom on my phone with S-off?
With s-off you just flash it in twrp..no extra steps
Sent from my EVO using xda premium
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I only have windows 7 64bit. So this means i cannot go the dirtyracun route. Is there any other way to get S-OFF?
if not.. How do i fastboot flash the boot.IMG from the ROM manually?
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
falconoble said:
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
Click to expand...
Click to collapse
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
jklatt747 said:
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
Click to expand...
Click to collapse
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
bigdaddy619 said:
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
Click to expand...
Click to collapse
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
bigdaddy619 said:
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
Click to expand...
Click to collapse
dandan2980 said:
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Okay so here's whats happens for me.
When i go bigdaddy's way: I put the MeanRom zip on my phone from my computer (MeanRom v64 or what ever the latest one is) I factory reset, wipe cache, wipe dalvic chache, and then go to install find the app and swipe to flash.. everything seems fine until i get an error and fail. It also says there is no MD5 file when i do this.
When I go dandan's way: I have the MeanRom zip on my phone (i've tried this with v64 *or whatever the latest one is* and v34) then i go into flash image GUI and go through finding it and everything. Then i get an error right above the Flash Image button saying "zip file must contain only one of the following: recovery.img, zimage, or a type of boot.img!" On my computer I unzipped the file and looked inside and all I see the boot.img and some folders but no recover or zimage so i dont know what it is talking about.
I really dont want to go through the processes of unrooting and relocking my phone again so i want to do this right. Any help from here on out would be greatly appreciated!
If someone could give me a step by step to follow or something for putting the Latest version of MeanRom on my phone that would be great!! I think i read somewhere that you have to put on the old version of MeanRom first. If that is so, could you also include how i would go about updating from the old version to the new one?
(If you're going to help me please make sure your method supports the HTC EVO 4G LTE on hBoot 1.19 Software v. 2.13.651.1 71ORD HTCdev Unlocked and Rooted with SuperSU and TWRP. (GooManager, and Flash Image GUI are installed to)
I dont know if this matters but it also says under Kernel Version:
3.0.8-01680-gb6402b4
[email protected] #1
SMP PREEMPT
Other info:
Baseband v: 1.12.11.0809
Android Version: 4.04
HTC Sense: 4.1
HTC SDK API level: 4.24
I know this post is really long and I probably put waaayyy more information then I actually needed to but I just want to be safe. It seems like everything I try for putting any Roms on my phone goes wrong with an error or failed message and I really want to do this.
I had followed this video ht tp://w ww.youtub e.com /watch?v=hQtUxEL8pd8 and did everything correctly. When I go to boot my phone up it shows the blue android boot animation then the green HTC animation then restarts.
Hboot 1.57
Somehow my recovery got deleted.
Clockworkmod recovery is installed.
I just don't know what to do
Is there a way I can just undo everything and go back to the stock rom?
Edit: Tried ViperROM and it's doing the exact same thing.
Make sure you are wiping everything except sdcard and then flash the rom. Maybe even try changing recoveries to 4ext.
Sent from my PG86100 using Tapatalk 2
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Jsparta26 said:
I assume you are s-off correct? I suggest going with Scotty's idea and switching to 4ext recovery. Cwm has been know to cause issues with the evo 3d. I'm also assuming that you mean hboot 1.58 not 1.57. FYI you can use any hboot with those ROMs. Just can't use the stock 2.89 kernel with any other hboot but 1.58. You also havnt specified whether or not your using the stock kernels that come with the ROM.
The meanrom by default flashes the VM kernel so if your on hboot 1.58. You have to flash the stock 2.89 kernel in the meanrom folder that's generated after you flash meanrom.
As for viperom you shouldnt have any problem flashing it considering that its compatible with any hboot. Which brings me back to my main point. Flash 4ext recovery and make sure you do a full wipe. That includes data factory wipe, cache and dalvik wipe and wipe all partitions except sdcard.
There's no reason give up when you run into a snag. There's usually a solution to every problem and you did the right thing by posting your question here. There's a ton of possibilities on here to do with your phone. Just read, research, ask questions if you are unsure of something.
Click to expand...
Click to collapse
I'm S-on, will it matter? And also I do mean 1.57. And one more thing. Does it matter if I boot up into a recovery using the command prompt? Also I'm not sure what kernel it is. I guess the one that's in the zip folder? Also sorry for slow responses I've been working days. Any chance you'll be on tomorrow around 7pm central?
Update: I reformatted everything and tried reinstalling Viperrom through CWM but no dice still boots up and resets. Got 4ext installed. Working from there.
Update: 4EXT is the best recovery I've ever seen and I'm never using CWM again.
Update: I installed VIperROM through 4ext and it's still restarting itself.
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Jsparta26 said:
Do you have smart flash enabled in 4ext recovery? Its under tools settings.
Click to expand...
Click to collapse
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I? Also i youtubed bootloop to see if it is really what's wrong and I came up with this video. ht tp ://www .y outube.co m/watch?v=OKXTD1-fqbc and my phones doing more than that. It's booting up all the way then once the screen and dock begins to load it restarts.
IAnb3rlin said:
No I do not. Just got off work and I'm doing it now. I don't need to have root for a custom rom do I?
Click to expand...
Click to collapse
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Jsparta26 said:
OK go ahead and turn it on. This will enable you to flash kernels inside recovery having s-on. No you don't have to root to flash a custom ROM. However every ROM has superuser baked into them so flashing one will automatically give you root.
I just want to add that s-on users do not have access to the boot partition which is where your kernel sits. Thats the cause of your bootlooping, before your recovery wasn't flashing any kernel with the ROM. Now with 4ext and smart flash its possible.
Click to expand...
Click to collapse
How do I flash a kernel? I'm not really sure what one is, I just know it's really important.
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Jsparta26 said:
Think of a kernel as a airplane tower that guides the direction of how the android system operates. It controls touch screen, it contains the drivers that make your keyboard work, WiFi, 4g, camera etc.. it is also responsible for taking over android run time after hboot finishes initiating everything to get android up and running. Someone correct me if my information is incorrect please lol. For now, stick with 4ext recovery and enable smart flash under tools settings. Everything should be good after that. I would highly recommend gaining s-off to make everything easier.
If your interested just ask and I'm sure one of us will be glad to help you.
Edit: Its real easy to flash a kernel once smartflash is enabled. A kernel always comes with every ROM or else it wouldn't be able to boot up. As I have stated before in my previous post about s-on users and the limitations.
Click to expand...
Click to collapse
I formatted everything using 4ext and installed a rom i also flashed the boot img just incase and it still restarted.
Here's the steps I took.
1. Format everything.
2. Download the.zip file and copy to SD card.
3. Load the recovery and enable smartflash.
4. Installed the rom.
5. Flashed the boot.img
6. Also tried without flashing the boot img.
And just to clarify. I'm installing ViperROM. And I only need the .zip file, correct?
I ended up using RUU to fix it and go back to the stock rom/ect, Then locked the bootloader unlocked it and flashed superuser and rooted it then got s-off using the wire trick. But after I rebooted it keeps taking me back to the jbear bootup logo and when I try to flash a recovery it doesn't load I just get the htc logo then jbear logo then it restarts. I followed this guide.htt p://w ww.yo utube.co m/ watch?v =tRj47iFQvbE I found here on the xda forums.
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Jsparta26 said:
Do you have the ics ruu correct? Boot back into bootloader and reflash the ruu. Do not unlock your bootloader again. Its not necessary anymore now that you have s-off.
Click to expand...
Click to collapse
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
IAnb3rlin said:
Booted up perfectly . So now I'm ready to flash any cdma rom with no problems? Do you know if there's a cdma rom that comes with, beats, adobe flash, and extras?
When I tried to flash a recovery this happened.
C:\android-sdk\platform-tools>fastboot flash recovery 4ext.img
sending 'recovery' (3738 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.031s
Also my bootloader is saying *** locked ***
Click to expand...
Click to collapse
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Jsparta26 said:
Your s-off. If you have root you can flash your recovery from 4ext updater or use flash GUI image from Google play. If no root, you will need to take your recovery and Rename it to PG86IMG, place it on root of sdcard and boot into bootloader. Let the phone pick up the recovery update and flash it. Power up your phone and take the file off the root of your card. Then power back down into bootloader and click on recovery. Let me know if it works.
Edit: just realized your using virgin mobile correct? I believe the reason your phone kept bootlooping with viper ROM was because of hboot. Try flashing a different hboot with the same method as the ruu and recovery.
Click to expand...
Click to collapse
I downloaded root checker and apparently I'm not root anymore. Yes I'm VM. I'm trying to rename the recovery and update it using the SD card now.
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
IAnb3rlin said:
I tried changing the name and it won't detect it. Do I rename the img file or use a zip file? For the RUU I used the pc program to update it and the recovery I use fastboot in the cmd prompt. How do I flash a different hboot? Would I be able to use fastboot for the recovery if i reunlocked the boot loader?
Click to expand...
Click to collapse
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Jsparta26 said:
My bad. Yes, get the zip file version. As for hboot, same way your trying to flash the recovery.
Click to expand...
Click to collapse
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
IAnb3rlin said:
When I tried to update it said Invalid model ID update failed. For the PG86IMG file.
Click to expand...
Click to collapse
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Jsparta26 said:
OK, get latest twrp recovery zip and do the same thing you tried with 4ext. I know, its a pain in the ass. I had to go through the same thing when I got my phone s-off with wire trick. The reason why I'm having you do this this way is because in case you ever need to have your phone serviced. They will check to see if you unlocked your bootloader or relocked it. Your bootloader is in "locked" state thus, they cannot deny you service regardless of s-on or s-off.
Click to expand...
Click to collapse
I just ended up unlocking the boot loader again and installing the recovery that way. Then saw this.. oh well lol. I really do appreciate the help. . I'm going to try to install viperrom again, and double backup this time! I'll let you know how it goes.
Hey im new to the fourms but i have a HTC evo 3d on the Sprint network. I am unlocked S-On hboot 1.58 with MeanRom ( the latest) i am suffering from a boot loop. The screen boots i see the ring and then black screen back to HTC and restarts process. I am in way to over my head. Can anyone tell me if i can put a stock rom back on and it will fix boot loop or i heard about relock but don't know how to do it. Ive rooted other devices and jail broken devices but never had a problem like this. Help is much appreciated. Thanks
edit: I used a video on youtube but cant post the link :/
ClockWorkMod Recovery was used in it so i think i have it still.
I have tried the factory reset from the boot menu (power + vol down)
Tanker990 said:
Hey im new to the fourms but i have a HTC evo 3d on the Sprint network. I am unlocked S-On hboot 1.58 with MeanRom ( the latest) i am suffering from a boot loop. The screen boots i see the ring and then black screen back to HTC and restarts process. I am in way to over my head. Can anyone tell me if i can put a stock rom back on and it will fix boot loop or i heard about relock but don't know how to do it. Ive rooted other devices and jail broken devices but never had a problem like this. Help is much appreciated. Thanks
edit: I used a video on youtube but cant post the link :/
ClockWorkMod Recovery was used in it so i think i have it still.
I have tried the factory reset from the boot menu (power + vol down)
Click to expand...
Click to collapse
Don't panic tanker, lol I can help you out with this. Here is the reasons behind your boot loop
Your recovery,
Your hboot
Your kernel
Let me elaborate. Cwm has been known to cause lots of problem with evo3d flashing latest twrp or 4ext recovery is recommended. Highly for 4ext. Now before I explain about hboot and kernel, currently you are a s-on user. What that means is that you only have access to certain partitions in the nand memory. System, data, and recovery. That leaves radios and boot partition( that's where your kernel sits) inaccessible through normal recovery means. Anytime you flash a ROM inside of recovery, you phone can't flash the kernel that came with it. So in actuality, your still on stock kernel with mean ROM.
Now for the solution. Your in a endless boot loop with your phone so you will have to download 4ext recovery for your phone and place the recovery image in your fastboot directory. Hook your phone up to the computer and run the command fastboot flash recovery "whatever the name of recovery"img . Boot into recovery and navigate to tools directory. Scroll down and turn on smart flash. This feature will allow you to flash kernels within recovery for s-on users. Wioe everything and flash your ROM again.
Now as for your kernel. Hboot 1.58 is only compatible with ICS stock kernels. That's the main point of your problem. What you will need to do is navigate to the meanrom folder and select the 2.89 kernel and flash it. Your phone should be able to boot up properly after that.
If that doesn't work, you could also try the first step of Ramjet's thread. That will get you back to stock and hopefully not bootlooping. Then if you continue the steps, you'll be s-off which makes flashing easier. See: http://forum.xda-developers.com/showthread.php?t=1889438
Jsparta26 said:
Now for the solution. Your in a endless boot loop with your phone so you will have to download 4ext recovery for your phone and place the recovery image in your fastboot directory. Hook your phone up to the computer and run the command fastboot flash recovery "whatever the name of recovery"img . Boot into recovery and navigate to tools directory. Scroll down and turn on smart flash. This feature will allow you to flash kernels within recovery for s-on users. Wioe everything and flash your ROM again.
Now as for your kernel. Hboot 1.58 is only compatible with ICS stock kernels. That's the main point of your problem. What you will need to do is navigate to the meanrom folder and select the 2.89 kernel and flash it. Your phone should be able to boot up properly after that.
Click to expand...
Click to collapse
okay so i have downloaded 4extrecoveryupdater.apk
Now i would open up CMD and what do i type in for "whatever the name of revoery".img or is that just someting i make up?
sorry im a really noob
Tanker990 said:
okay so i have downloaded 4extrecoveryupdater.apk
Now i would open up CMD and what do i type in for "whatever the name of revoery".img or is that just someting i make up?
sorry im a really noob
Click to expand...
Click to collapse
Funny. No you cannot make up file names, or commands...
First of all you need fastboot application. Save it to c:/fastboot folder.
1. Open CMD, type cd fastboot to enter fastboot folder
2. Type : fastboot flash recovery recovery.img (where recovery.img is the name of your recovery choice weather it is TWRP, 3eXT, or CWM.
I am currently using 4eXT, which I switched to from TWRP
And that's it after its done you should have a flashed recovery on your EVO 3D
Maybe I should add that the "recovery.img" file HAS to be inside c:/fastboot folder.
Good luck. If that doesn't fix it, or if you need any recovery images that worked on my phone, POST
peteypub said:
Funny. No you cannot make up file names, or commands...
First of all you need fastboot application. Save it to c:/fastboot folder.
1. Open CMD, type cd fastboot to enter fastboot folder
2. Type : fastboot flash recovery recovery.img (where recovery.img is the name of your recovery choice weather it is TWRP, 3eXT, or CWM.
I am currently using 4eXT, which I switched to from TWRP
And that's it after its done you should have a flashed recovery on your EVO 3D
Maybe I should add that the "recovery.img" file HAS to be inside c:/fastboot folder.
Good luck. If that doesn't fix it, or if you need any recovery images that worked on my phone, POST
Click to expand...
Click to collapse
petey I am having the same issue as him, 1.58 hboot running ext4 recovery with smart flash on and i cant get out of a boot loop. i have tried using an ruu to return to stock (ruu fails/becomes non responsive). as well as flashing roms using ext4 and then flashing the boot image via fastboot.
if you could help me as well or send me any recovery files you have i would appreciate it
Sure ill send you the images I'm using. I'm at work now, so ill shoot you an email when I get back...
Sent from my PG86100 using Tapatalk 2
pm sent with email address
Youre in a boot loop because you need to downgrade your hboot see link below
Don't forget to hit the thank button!
http://forum.xda-developers.com/showthread.php?t=1906172
sent from my 1920 overclocked note 2 running jedi xp11
---------- Post added at 02:06 AM ---------- Previous post was at 02:05 AM ----------
Btw I use TWRP not 4ext. And forget the ruu.
Just downgrade and it will work
sent from my 1920 overclocked note 2 running jedi xp11
restore rom
When you flashed rom did u make back up cause you could always restore old rom. And you could try flashing the right kernel but most of the time it cause you have to flash boot image that worked for me in trying flash cm 10.1 and I keep get bootloops my self try figure this one out. Same hboot 1.58 2.89 base
harry1471 said:
When you flashed rom did u make back up cause you could always restore old rom. And you could try flashing the right kernel but most of the time it cause you have to flash boot image that worked for me in trying flash cm 10.1 and I keep get bootloops my self try figure this one out. Same hboot 1.58 2.89 base
Click to expand...
Click to collapse
Are you saying youre still getting boot loops and you havent figured this out yet or you did figure it out?
If you havent figured it out I can assist as ive got it 100% working
sent from my 1920 overclocked note 2 running jedi xp11
Same deal
markbencze said:
Are you saying youre still getting boot loops and you havent figured this out yet or you did figure it out?
If you havent figured it out I can assist as ive got it 100% working
sent from my 1920 overclocked note 2 running jedi xp11
Click to expand...
Click to collapse
I'm having the same problem:
Sprint EVO 3D
Unlocked
S-On
Hboot 1.58
eMMC-boot
Won't boot any rom past the OS lock screen. Tried relocking and RUU update, Tried booting recovery from fastboot.
Any help?
Thanks!
jy04 said:
I'm having the same problem:
Sprint EVO 3D
Unlocked
S-On
Hboot 1.58
eMMC-boot
Won't boot any rom past the OS lock screen. Tried relocking and RUU update, Tried booting recovery from fastboot.
Any help?
Thanks!
Click to expand...
Click to collapse
Give me a bit mire info on this. I can help for sure. The evo3d is a pita but we can get it. So basically if I understand, you're stock rooted but have s-on and im assuming all roms are bootlooping?
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
markbencze said:
Give me a bit mire info on this. I can help for sure. The evo3d is a pita but we can get it. So basically if I understand, you're stock rooted but have s-on and im assuming all roms are bootlooping?
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
Click to expand...
Click to collapse
Yes, that's were I am at this point. Right now I've got MeanRom booting to the homescreen seems like it's going to work, but the time is wrong and there's no service, before it can completely boot, bam, shuts down and reboots.
It does the same for the stock Sprint ROM.
Unfortunately I didn't make a backup of the phone when I gor it so I'm using a downloaded one.
I had Meanrom running on another 3D not too long ago, but don't remember it being this troublesome. What did I miss?
jy04 said:
Yes, that's were I am at this point. Right now I've got MeanRom booting to the homescreen seems like it's going to work, but the time is wrong and there's no service, before it can completely boot, bam, shuts down and reboots.
It does the same for the stock Sprint ROM.
Unfortunately I didn't make a backup of the phone when I gor it so I'm using a downloaded one.
I had Meanrom running on another 3D not too long ago, but don't remember it being this troublesome. What did I miss?
Click to expand...
Click to collapse
Ok well the first thing you need to do is downgrade your hboot to v 1.49000. I posted a link on the first page. If you were stock you coukd get s-off via the wire trick
But since you're s-on you need to flash the boot.img in fastboot and then flash the rom or vise versa. I cant remember which one needs to be done first as its been a while since I've used my evo3d. Basically anything thats ics and above cant be flashed unless you downgrade your hboot. Htc sent a hidden hboot ota to you at some point without your knowledge to prevent you from flashing. So downgrading your hboot is your #1 priority and you need to get back to stock to get s-off too
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
Using the wrong ROM!! Got it to boot using MeanRom ICS. Thanks!
Can I get S-OFF with MeanRom flashed? Or do I need to flash a rooted stock ROM?
jy04 said:
Can I get S-OFF with MeanRom flashed? Or do I need to flash a rooted stock ROM?
Click to expand...
Click to collapse
You can try but the instructions say stock. You tube it. Ive done it. It works. Just be patient with the wire trick
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way