I am trying to install Fresh ROM 4.2 on my Evo 3D.
The instructions at geekfor.me (sorry, can't post direct link since I'm too new--search Google for fresh rom 4.2) have a terse warning about people like me with HBOOT 1.5. (Yes, I used the HTC unlocker.) I am supposed to download boot.img first, install it with Flash Image GUI, then install the ROM via recovery mode.
OK, so I got the boot.img installed OK, but when I go back into the bootloader, highlight RECOVERY, then press the power button, all that happens is I boot right back into the main OS.
I am supposed to use RECOVERY to install new ROMs, right?
I'm at a loss for what to do with the next step. I've tried searching forums, but each search comes up with a new, novel theory, unfortunately, and so far none seem to apply to my case.
novasource said:
I am trying to install Fresh ROM 4.2 on my Evo 3D.
The instructions at geekfor.me (sorry, can't post direct link since I'm too new--search Google for fresh rom 4.2) have a terse warning about people like me with HBOOT 1.5. (Yes, I used the HTC unlocker.) I am supposed to download boot.img first, install it with Flash Image GUI, then install the ROM via recovery mode.
OK, so I got the boot.img installed OK, but when I go back into the bootloader, highlight RECOVERY, then press the power button, all that happens is I boot right back into the main OS.
I am supposed to use RECOVERY to install new ROMs, right?
I'm at a loss for what to do with the next step. I've tried searching forums, but each search comes up with a new, novel theory, unfortunately, and so far none seem to apply to my case.
Click to expand...
Click to collapse
Sounds like you got into the HBoot menu OK, but might have either not installed the recovery properly, or not at all.
eXplicit815 said:
Sounds like you got into the HBoot menu OK, but might have either not installed the recovery properly, or not at all.
Click to expand...
Click to collapse
Thank you. That could be true.
What recovery do you recommend for Evo 3D?
Seems like TWRP is popular, but it appears their recovery-twrp-shooter-1.1.1.img is broken as all I get is (remote: image error! (BootMagic check fail)) when installing it over fastboot.
CORRECTION: *I* had a bad copy of their .img file.
novasource said:
Thank you. That could be true.
What recovery do you recommend for Evo 3D?
Seems like TWRP is popular, but it appears their recovery-twrp-shooter-1.1.1.img is broken as all I get is (remote: image error! (BootMagic check fail)) when installing it over fastboot.
Click to expand...
Click to collapse
I've only ever run one since I rooted my phone. And that was back when it was first rooted. It's never given me problems, and has always worked great.
Revolutionary CWM v4.0.1.4 - Can be found HERE
eXplicit815 said:
I've only ever run one since I rooted my phone. And that was back when it was first rooted. It's never given me problems, and has always worked great.
Revolutionary CWM v4.0.1.4 - Can be found HERE
Click to expand...
Click to collapse
I agree
eXplicit815 said:
I've only ever run one since I rooted my phone. And that was back when it was first rooted. It's never given me problems, and has always worked great.
Revolutionary CWM v4.0.1.4 - Can be found HERE
Click to expand...
Click to collapse
Hmm, looks like that ROM is from Oct. 2011. Wouldn't it be missing important updates?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
See the recovery issues thread in my signature & the detailed scenarios. I think it Will help u out. I had the same problem. Basically posts 1,2, & 10.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
novasource said:
I am trying to install Fresh ROM 4.2 on my Evo 3D.
The instructions at geekfor.me (sorry, can't post direct link since I'm too new--search Google for fresh rom 4.2) have a terse warning about people like me with HBOOT 1.5. (Yes, I used the HTC unlocker.) I am supposed to download boot.img first, install it with Flash Image GUI, then install the ROM via recovery mode.
OK, so I got the boot.img installed OK, but when I go back into the bootloader, highlight RECOVERY, then press the power button, all that happens is I boot right back into the main OS.
I am supposed to use RECOVERY to install new ROMs, right?
I'm at a loss for what to do with the next step. I've tried searching forums, but each search comes up with a new, novel theory, unfortunately, and so far none seem to apply to my case.
Click to expand...
Click to collapse
Try the app Flash Image GUI...
PMGRANDS said:
Try the app Flash Image GUI...
Click to expand...
Click to collapse
Per #3 above, I had a bad download of the .img file. But I do have that utility, and it's nice.
Related
Ok so here's the thing I obviously have a Motorola Atrix 4g and I am from the United States. I have rooted my device via Pete's Motorola root tools, I have accessed my webtop hack and tether. I've been research for about a week straight on how to install CM7, but the CM7 that I really want is EVOGP's whch has facial recognition capabilities (http://forum.xda-developers.com/showthread.php?t=1382934&highlight=facial+recognition). I am currently running stock Gingerbread. I have previously tried t0dbld's way of installing for the latest version of CM7 (Ba2TF) based on his installation instructions (http://forum.xda-developers.com/showthread.php?t=1257574&highlight=facial+recognition). Unfortunately I failed and ended up wiping all my contacts and starting brand new. The portion that I do not see is the second step :
1.)Reboot phone into CWM recovery (Power Button + Vol Down), press Vol Down until you see "Android Recovery" then press Vol Up to enter.
2.) Go to Backup & Restore and create a backup (this may take some time)
I dont see where to go for Backup and restore to create a back. It too me a while to figure out that had to press the both volume buttons just to toggle. But this was the first area, that was blurry. If someone could explain step by step how to get to "Backup &Restore and create a backup" would be great.
Next while apparently not backing up my rom, I decided since I already had a rom and I wanted CM7 that wouldnt be important. So I try to install the Ba2tf.zip via the bootloader screen which located on my sd card. So I go "apply blah blah to Sd card" I see the Ba2tf.zip and I press the power button to unzip the file or install. The process I see starts unloading the zip file then starts to installing the file, everything is great. Then it says "installation failed".
If someone can tell me what I did wrong and give me a step by step process of what I should and be seeing, I would greatly appreciate this help. As you cant tell I really want CM7 especially EVOGP's. Please help!!! Step by step please!!!!
Have you unlocked your phone using fruitcake? Which CWM are you running?
It's Pudding, not fruitcake.
http://forum.xda-developers.com/showthread.php?t=1136261
Fruitcakes are stock system files that can flashed through CWM.
jiggytom said:
Have you unlocked your phone using fruitcake? Which CWM are you running?
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, then unlock it. Search for pudding in the Dev Forum.
After that, you need the right recovery (CWM)
Which recovery are you using? You should flash romracer's latest CWM. Most of all the ROMs are using the latest Romracer's recovery so you won't go wrong with using that.
Then from there --- you should be good to go.......
I had no idea you had to unlock, I thought unlocking and rooting was the same thing. And I a bit new with lingo does CWM refer to Clockwork Mod? If so I downloaded the standard free Rom Manager on the market. I assume judging by your message I should probably unlock my phone using fruitcake? If I do can you post simplified link on how to install fruit cake?
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1302423
The instructions provide links for Pudding and romracer's recovery, which are both needed to flash any custom Rom.
Here's the link for CM7:
http://forum.xda-developers.com/showthread.php?t=1257574
baller24hr said:
I had no idea you had to unlock, I thought unlocking and rooting was the same thing. And I a bit new with lingo does CWM refer to Clockwork Mod? If so I downloaded the standard free Rom Manager on the market. I assume judging by your message I should probably unlock my phone using fruitcake? If I do can you post simplified link on how to install fruit cake?
Click to expand...
Click to collapse
I guess I have to use pudding right? I see the link i'll flash it. I'll go searching for Romracer's latest recovery... please point me towards it if possible.
Re-read what I wrote.
live4nyy said:
Follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1302423
The instructions provide links for Pudding and romracer's recovery, which are both needed to flash any custom Rom.
Here's the link for CM7:
http://forum.xda-developers.com/showthread.php?t=1257574
Click to expand...
Click to collapse
baller24hr said:
I guess I have to use pudding right? I see the link i'll flash it. I'll go searching for Romracer's latest recovery... please point me towards it if possible.
Click to expand...
Click to collapse
@live4nyy Thank you so much you are a huge help.... I greatly appreciate it
No problem, just make sure to read the instructions thoroughly and make sure you have the appropriate "pudding" file.
baller24hr said:
@live4nyy Thank you so much you are a huge help.... I greatly appreciate it
Click to expand...
Click to collapse
I have installed rsdlite. Where can I find the drivers that I'm supposed to install? Or does it come bundled already?
Here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Also, after you install the drivers it helps to plug it in and then go through all the USB options in the drop down and allow each one to install as well. (eg. Windows Sync, USB Mass Storage, Portal)
baller24hr said:
I have installed rsdlite. Where can I find the drivers that I'm supposed to install? Or does it come bundled already?
Click to expand...
Click to collapse
Yeah i remember downloading this a while back.... I'm currently at Proper Recovery 5B and my command prompt says <waiting for device> and it wont allow me to type 5C.... Do I choose either A,B or C then pick D? And I'm currently on my bootload screen and it says Unlocked in the top left corner
Does anybody know anything of this nature?
Someone help I'm getting worried now
Now my phone shut off and the charging light is on....
I typed in 5c and it says it's not found... i tried 5d and that didnt work <waiting for devices> .... my phone was unresponsive even to the power button so i pulled the battery and turned it on it brought me back to the bootload screen that said unlock in the top left. my phone is now charging on the normal house charger and i turned it back on it's responsive I dont have any of my cards in so it's showing motoblur
Does this mean my phones unlocked and I should just go ahead and install the CM7?
baller24hr said:
Does this mean my phones unlocked and I should just go ahead and install the CM7?
Click to expand...
Click to collapse
Yup.
Sent from my Xoom using xda premium
thanks I appreciate it
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
ten6 said:
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
Click to expand...
Click to collapse
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Dark Nightmare said:
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Click to expand...
Click to collapse
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
ten6 said:
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
Click to expand...
Click to collapse
Don't download that one, it has issues, hold up, I'll give you a link to the most recent file.
Here, get this: http://d-h.st/3VD
Download speed should be faster as well. rename it PH85IMG and place it on your sd card after you relock your bootloader, then boot into bootloader, it's gonna detect the file and ask you if you wanna update, follow the on screen instructions to update, voila! Follow the basics to install the new energy rom.
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It is useful, I fully agree with you, it's like we come here to answer the same questions over and over, but I'm just trying to be nice, cause I usually just say, read the amaze bible, but then they go and do something even more noobish, so to avoid the tear jerks I just give the basic info, though I'm fading away slowly.
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
I came across this issue. As earlier posts said, install the new ICS update. The partitions were messed up and the ruu will clean it up.
ten6 said:
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
Click to expand...
Click to collapse
Lol, never pointed fingers buddy, so calm down.
Maybe I should create a new topic but my issue is similar to this one except for the fact that I read quite a lot and tried quite a few things.
My situation is that I made a backup with cwm only booted not flashed so I have the 100% stock backed up, after this I flashed cwm and tried to install the Energy rom based on ics and that was my mistake as I used to be on a Nexus device I didn't have to worry about this.
So I got stuck on a bootloop and tried factory reset/wiping everything, tried to reinstall a stock ROM (t-mobile one as I only found a .exe for the videotron one and I did not feel like exploring the exe as I am a Linux user) by relocking bootloader and using the HTC method, tried to install manually the stock Kernel with Energy ROM using adb and fastboot commands, tried to restore my backup but nothing seems to work, I'm still bootlooping.
Is-it possible to s-off without a regular adb access (only the cwm adb access)? And would s-off allow me to flash anything as I wish? Is there a way to have any ROM working on my device? (i know the answer is yes to the last one, at least )
Thanks!
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
johnride said:
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
Click to expand...
Click to collapse
Okay okay, calm down, there's currently only one method of going about restoring your device since you're s-on and no you cannot s-off with just cwm adb, I think JB s-off method is only an exe file, never saw linux files anywhere on his site. Anyways, you have to use the GB exe for videotron and restore to stock via it then update to ics to use the most recent energy rom, BUT if you just want a working device, this is just an idea, though it should work fine, you can flash a custom recovery and flash the GB version of energy rom, you should be able to restore your backup as well, but you said you can't, which is odd, it may be because of the kernel not being flashable as since CWM cannot flash kernels while s-on, in which case I'd advise you to get 4EXT recovery and then try restoring your back once again, it should work fine since 4EXT can flash kernels while S-ON.
My two cents.
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
johnride said:
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
Click to expand...
Click to collapse
I got lost halfway through that post, after flashing a rom, if the kernel isn't flashed (reboots and does it automatically), then flash the kernel manually, should boot fine, does anyone ever really read anymore? This very issue both s-on and s-off has been answered more times today than I can count. If you read the details on JB's site, you'd see and know all you need to.
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
johnride said:
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
Click to expand...
Click to collapse
How did you go about flashing the kernel?
Sent from my SGH-T679 using xda app-developers app
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
johnride said:
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
Click to expand...
Click to collapse
Okay here's a few tips, cwm cannot flash kernels with son devices, get 4ext recovery for that. Second thing, reflash the from after doing a super wipe, if 4ext doesnt reboot and flash the kernel, do it manually, ill assume you know how to use ad, if not check my Bible tutorial on it, use the boot command for flashing boot images, take the boot file from the zip file, place it in the folder where your adb files are and flash it to your device while its in fastboot mode.
Sent from my SGH-T679 using xda app-developers app
Well, I think I have done all you mention above, the only thing i'm not sure to understand is what you mean by "super wipe" I found some executables about it but I guess it can't do much more than the flash all partitions (except external sdcard) in 4ext recovery wich I finally managed to install properly.
So, I made that global formatting thing, I tried to install an ICS based ROM and 4ext rebooted to install kernel, same bootloop. Tried to install manually the kernel that came with this rom via the classic fastboot flash boot boot.img. Same bootloop. Tried to put the modules manually via the recovery adb access (performing a mount -a in adb shell to have everything present in fstab mounted) and flashing this stock kernel with no more success.
Achieved the same operations with a GB based ROM (this one: http://forum.xda-developers.com/showthread.php?t=1535173) with both the faux and the stock kernel without any more success.
Did I miss something? Am I so dumb? Do you have any other rom to suggest that have higher chances to succeed?
Do you think trying to restore my sotck nandroid with 4ext has more chances to succeed?
Thanks, again and always!
I'm a complete noob, and I probably should have done more research before doing this - Sorry for annoying post if this has occurred already, I couldn't find a post with a solution.
What I did:
Installed adb tools, unlocked bootloader, then rooted it. Then I tried installing cm10.1 following this guy's method(I don't have s-off) :
wwjoshdew - How To Install CyanogenMod 10.1 Android 4.2.1 Jelly Bean on the HTC Evo 4g LTE (Sorry, since I'm a noob, i can't post external links)
Everything seemed as if it was going according to plan but when I got to lock screen on first boot, I couldn't touch anything on the screen. Only volume control and power buttons on the outside functioned.
Also, I'm on twrp v2.4.1.0 and I flashed the rom using a app called flash gui on the phone. I made a backup as well, but after restore to backup, the phone just keeps restarting incessantly.
Can anyone help me, explaining in depth what I can do? I'm a complete noob, and I'm sorry if this post is annoying! I've seen that noob video.
Flash gui is only for flashing the kernel, the rom still needs to be flashed separately. If you're running the latest firmware update then you can't use roms that require older binaries (basically all aosp). Either wait for the source to drop, flash an updated sense rom, or go to the mean bean thread and look for the instructions for downgrading the touch panel update.
om4 said:
Flash gui is only for flashing the kernel, the rom still needs to be flashed separately. If you're running the latest firmware update then you can't use roms that require older binaries (basically all aosp). Either wait for the source to drop, flash an updated sense rom, or go to the mean bean thread and look for the instructions for downgrading the touch panel update.
Click to expand...
Click to collapse
Do you know how I can just revert back to regular android. I mean I can not do anything except boot into bootloader and recovery, I can't reset or restore. cheers and thanks
No first hand experience and I haven't looked into the issue too much. Better to check the mean bean thread in android development forum
Download and flash a 3.16 based sense rom and you should be fine. I ran into the same problem since i downloaded the lastest twrp. Also don't forget to wipe before installing.
mito8485 said:
Download and flash a 3.16 based sense rom and you should be fine. I ran into the same problem since i downloaded the lastest twrp.
Click to expand...
Click to collapse
How do I flash, like through fastboot devices then fastboot flash boot... in cmd on my pc?
Also, how do i know if the rom is 3.16 based?
Cheers and thanks mate.
SvetKrasivaya said:
How do I flash, like through fastboot devices then fastboot flash boot... in cmd on my pc?
Also, how do i know if the rom is 3.16 based?
Cheers and thanks mate.
Click to expand...
Click to collapse
You can download the lastest meanbean v3.06 rom, or any rom that is 3.16 software based. Usually it says it right by the name of the rom on the header. Place the rom zip on your sd card. I usually put all my files in the downloads folder. Then boot into recovery and do a factory reset, then wipe cache, wipe dalvik cache, and wipe system. Then go to install and flash the meanbean rom you have in your downloads folder. Then reboot. You should be good to go. Since your S-on try staying with roms that contain the s-on installer. Most 3.16 based roms have the S-ON installer but in the event that one does not you will have to flashboot the boot.img of the rom prior to flashing the rom through recovery. Note: You can only run roms that are based on the latest 3.16 software.
mito8485 said:
You can download the lastest meanbean v3.06 rom, or any rom that is 3.16 software based. Usually it says it right by the name of the rom on the header. Place the rom zip on your sd card. I usually put all my files in the downloads folder. Then boot into recovery and do a factory reset, then wipe cache, wipe dalvik cache, and wipe system. Then go to install and flash the meanbean rom you have in your downloads folder. Then reboot. You should be good to go. Since your S-on try staying with roms that contain the s-on installer. Most 3.16 based roms have the S-ON installer but in the event that one does not you will have to flashboot the boot.img of the rom prior to flashing the rom through recovery. Note: You can only run roms that are based on the latest 3.16 software.
Click to expand...
Click to collapse
How can I put the rom on the sdcard if I can't excess anything on the phone except for the bootloader...? I can't even access the recovery, because it has become relocked. pretty much all i can access is the bootloader and fastboot, nothing eles, I can't even restore to normal htc sense firmware.
Cheers and thanks
SvetKrasivaya said:
How can I put the rom on the sdcard if I can't excess anything on the phone except for the bootloader...? I can't even access the recovery, because it has become relocked. pretty much all i can access is the bootloader and fastboot, nothing eles, I can't even restore to normal htc sense firmware.
Cheers and thanks
Click to expand...
Click to collapse
Take the card out and put it in your computer, dl it to the card and then put back on your phone.
tonyevo52 said:
Take the card out and put it in your computer, dl it to the card and then put back on your phone.
Click to expand...
Click to collapse
Thanks mate, I'll give that a try. I didn't think about taking the sd out jaja Do what exactly should i do once i put the rom on the sd?
Check out this thread. I believe you can flash the rom through fastboot. I have not done this though. So proceed with caution. Remember it has to be 3.16 based.
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
adb reboot bootloader (requires USB debugging to be turned on).
power off the device then back on with 'vol up' + power button.
Wipe your device.
fastboot -w
Update your ROM.
fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM.
SvetKrasivaya said:
Thanks mate, I'll give that a try. I didn't think about taking the sd out jaja Do what exactly should i do once i put the rom on the sd?
Click to expand...
Click to collapse
Follow the steps that Milo put above and hopefully it works. Whenever I screwed mine up and wouldn't recover, I would run the 3.15ruu to put it back to stock.. However if you are on 3.16 I don't believe there is an ruu for it yet, I know captain throwback had something in works though, search for him and check his threads as a last ditch effort.. Best of luck.
Mito that is...
tonyevo52 said:
Take the card out and put it in your computer, dl it to the card and then put back on your phone.
Click to expand...
Click to collapse
Nevermind, got it all fixed, thanks so mate! You are my hero!:laugh:
SvetKrasivaya said:
Nevermind, got it all fixed, thanks so mate! You are my hero!:laugh:
Click to expand...
Click to collapse
Awesome... Now did you get it back to stock or did the cm10.1 work for you finally, curious what you did. Still learning stuff myself.
tonyevo52 said:
Awesome... Now did you get it back to stock or did the cm10.1 work for you finally, curious what you did. Still learning stuff myself.
Click to expand...
Click to collapse
I'm actually on meanbean latest version.
I couldn't do anything else except this
What I did:
- Put the micro sd card in pc
- copied meanbean rom to sd
- put sd card back in phone
- put phone into fastboot
-on pc, I extracted the boot.img from meanbean rom and placed it into android-sdk folder,
- simultaneously pressed shift and right clicked in folder to open command prompt
- in command prompt, type fast boot devices
- then fastboot flash boot boot.img
- on phone, put phone into recovery(twrp) then I installed the rom.
then the phone booted as normal. I'm working to see if I can install the cm10.1 on meanbean, I'm gonna test it to see what happens. I hoped I was able to help.
SvetKrasivaya said:
I'm actually on meanbean latest version.
That's cool, so you flashed the boot.img first after you extracted it and then you went right into Twr precovery and just flashed the rom zip file. And I agree, I don't know if the cm10.1 is for 3.16 or not, and if you flash a kernel and is not right, you're toast, that's why I'm hesitant to flash the cm10.1 zip....
Click to expand...
Click to collapse
tonyevo52 said:
SvetKrasivaya said:
I'm actually on meanbean latest version.
That's cool, so you flashed the boot.img first after you extracted it and then you went right into Twr precovery and just flashed the rom zip file. And I agree, I don't know if the cm10.1 is for 3.16 or not, and if you flash a kernel and is not right, you're toast, that's why I'm hesitant to flash the cm10.1 zip....
Click to expand...
Click to collapse
Yes, thats exactly what I did. Once I flashed the boot.img, I booted into recovery and installed the meanrom.
Yeah I feel you mate. I'm going to give it try again, see what happens and i'll let you know how it goes.
Hey, I tried it, and its still doing the same thing...touch screen is not working.
Click to expand...
Click to collapse
CM will not work with the latest touch panel update. See Captain Throwback's thread in Android Development to downgrade your touch panel software to run non-3.16 roms.
garfilo said:
CM will not work with the latest touch panel update. See Captain Throwback's thread in Android Development to downgrade your touch panel software to run non-3.16 roms.
Click to expand...
Click to collapse
Thanks for the answer, but where specifically is that thread mate?
Cheers and thanks.:good:
It's in the Android Development section. Here is a link and the title header
http://forum.xda-developers.com/showthread.php?t=1704612
[FIRMWARE][S-OFF] Jewel Firmware Collection - Latest: 3.16.651.3 OTA
Read the first post carefully. You already did all the hard stuff. Just downgrade the touch panel firmware to the previous version.
I just rooted my phone, installed 2 different kernels, my phone's wifi now only 'Error's I factory restored (flash recovery with stock Evo info.)
Honestly I feel really stupid. I can't even flash my TWRP back on. Any advice or help would be greatly appreciated. I am fairly new to Rooting and its customizations. Thank you.
xFatex said:
I just rooted my phone, installed 2 different kernels, my phone's wifi now only 'Error's I factory restored (flash recovery with stock Evo info.)
Honestly I feel really stupid. I can't even flash my TWRP back on. Any advice or help would be greatly appreciated. I am fairly new to Rooting and its customizations. Thank you.
Click to expand...
Click to collapse
Can you access your recovery
Sent from my EVO using XDA Premium 4 mobile app
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
lreyes said:
Can you access your recovery
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had no access to my TWRP Recovery, I actually fixed that though.
The Kernel is changed and now I have no Data access? I think my ROM is not compatible like suggested. (Sense ROM)
FinZ28 said:
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
The current situations has changed sadly.
I have no custom ROM just Sense.
The Kernel: Bulletproof-EVO-v1.4.
ROM: Default Sense?
This is my first attempt at really rooting/adding kernels just messing around and doing damage.
Now instead of WiFi I have no Data Service with this Kernel and ROM combo. I will check out your links thank you very much.
FinZ28 said:
It might also help to post what ROM you were running, along with what two kernels you flashed. Certain kernels only work with certain ROM's (AOSP kernels don't work on Sense ROM's, and vice-versa). Take a look at the top link in my sig. At the bottom is a few helpful links. om4 has an excellent "Don't Panic" guide that contains some excellent info and really should be required reading for new users.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Now my phone is stuck in bootloop I even tried to remove TWRP recovery to to StockRecovery...
Just let it die?
Or is there anyway to flash a Kernel via command prompt?
Anyway to fix this?
xFatex said:
Now my phone is stuck in bootloop I even tried to remove TWRP recovery to to StockRecovery...
Just let it die?
Or is there anyway to flash a Kernel via command prompt?
Anyway to fix this?
Click to expand...
Click to collapse
Hit the top link in my sig. I think you'll find what you're looking for there. Sounds like you may need to reflash your recovery from the bootloader via fastboot. Assuming that works, you need to due a full system wipe from recovery, then flash a ROM.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hit the top link in my sig. I think you'll find what you're looking for there. Sounds like you may need to reflash your recovery from the bootloader via fastboot. Assuming that works, you need to due a full system wipe from recovery, then flash a ROM.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Do forgive me, I am reading your thread and advice.
I am just running on zero sleep in the past 4 days and trying to fix this all day.
The bootloop is gone now that I have flashed the TWRP recovery Stock recovery and Twrp again.
The stock recovery was still giving me the twrp startup screen (disclaimer at the HTC screen)
I also don't quite get what to do via Hboot 2.09 (what I have)
All the ROM's with the kernels are in a zip that needs to be opened via TWRP well the ones I download...
I have wiped the ceche/delvik etc... fear I wiped the whole thing by accident rendering the device empty.
My android's exe file doesn't seem to be about either.
Android version: 4.1.1
Software: 3.17.650? (The most recent for Evo commercially)
When I do attempt a Stock restore via fastboot flash not exe file I end up getting the red ! next to my phone and the phone doesn't reboot naturally.
Do I need to hunt down ROM's and Kernels that I can flash into the cmd?
I understand with my version I must flash in the using the prompt and have them separate but I am totally new at this I feel really dumb I'm sorry if I am bothering you with redundant questions I am attempting to follow and get the information but I think I am reading so many different threads on it I am suffering from information overload (artist not a programmer lol.)
EDIT:
NOTE:
I AM currently reading your bottom link about Fixing system wipe.
xFatex said:
Do forgive me, I am reading your thread and advice.
I am just running on zero sleep in the past 4 days and trying to fix this all day.
The bootloop is gone now that I have flashed the TWRP recovery Stock recovery and Twrp again.
The stock recovery was still giving me the twrp startup screen (disclaimer at the HTC screen)
I also don't quite get what to do via Hboot 2.09 (what I have)
All the ROM's with the kernels are in a zip that needs to be opened via TWRP well the ones I download...
I have wiped the ceche/delvik etc... fear I wiped the whole thing by accident rendering the device empty.
My android's exe file doesn't seem to be about either.
Android version: 4.1.1
Software: 3.17.650? (The most recent for Evo commercially)
When I do attempt a Stock restore via fastboot flash not exe file I end up getting the red ! next to my phone and the phone doesn't reboot naturally.
Do I need to hunt down ROM's and Kernels that I can flash into the cmd?
I understand with my version I must flash in the using the prompt and have them separate but I am totally new at this I feel really dumb I'm sorry if I am bothering you with redundant questions I am attempting to follow and get the information but I think I am reading so many different threads on it I am suffering from information overload (artist not a programmer lol.)
Click to expand...
Click to collapse
if youre S-OFF then you can just use ViperRUU and then reunlock your device.
lreyes said:
if youre S-OFF then you can just use ViperRUU and then reunlock your device.
Click to expand...
Click to collapse
S-ON.
I am attempting to download MeanBean after reading Fin's Fix.
Though I don't know if FlashImage GUI will work.
I also have to figure out how to flash .apk files too...
Sorry about the bother... I really am far below Novice at this I should have had someone holding my hand step by step lol.
Okay, so the problem with the Kernel originally was it wasn't compatible?
Then the next one with the service error was I suppose the same thing?
Then when I tried to restore apparently I wiped my phone of all Data resulting in a bootloop and being no one has the exe file for the factory RUU of the latest version for the Evo 4g LTE I had no way of restoring any of the files?
So then I stalked Fin's suggestions eventually lead me to MeanBean. at least it got me up and running... I attempted to back up with TWRP.
Which apparently doesn't work (I have to learn how to backup else where... Lets add it to my list.)
But after I attempted the back up I also attempted the instillation of "Operation Jelly Bean" I love the ROM I love the theme I love the sleekness
Apparently I am missing something with my touch panel software. I wish I could have kept the ROM but couldn't sadly (If you know what I am doing wrong I would love to keep that ROM in the future)
So with another failed ROM I tried to restore... which there was no restore when I went to do so... I was a little frustrated from my constant bricking as is...
I attempted factory restore apparently also wiped everything (Internal sd, external, everything.) I don't know what is up with that do you have any clue if its a glitch or am I just wiping it?
I also do Stock restore that does absolutely nothing for my phone anymore...
I will flash it... and it does nothing... it still runs like TWRP (disclaimer etc) but won't go to the twrp boot screen... this is a bit frustrating.
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.