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.
Related
I am not new to any of this, but I am having a problem. VZW is sending me an Incredible, so I need to unroot. I used 2 different methods, both of which failed. Can someone please give me a hand or link me to some other options?
These are the methods I have tried:
http://forum.xda-developers.com/showthread.php?p=8315870
and
http://www.droid-eris.com/tutorials-corner/%28tutorial%29-how-to-unroot-your-droid-eris/
Perhaps you could state what problem you experienced when you tried using the Flashback21 ROM; the only thing that it requires is the Amon_RA recovery (Clockwork is not supported). Other than that, it should flash like any other ROM.
You might also want to mention what the exact bootloader version you have on your phone, whether or not you can use your trackball (for up/down/press actions) without too much trouble.
bftb0
bftb0 said:
Perhaps you could state what problem you experienced when you tried using the Flashback21 ROM; the only thing that it requires is the Amon_RA recovery (Clockwork is not supported). Other than that, it should flash like any other ROM.
You might also want to mention what the exact bootloader version you have on your phone, whether or not you can use your trackball (for up/down/press actions) without too much trouble.
bftb0
Click to expand...
Click to collapse
I was thinking the same thing, how can one help with that little info
btw bftb0, thank you for all the help with the uber technical issues around here. Your knowledge is very much appreciated, yeah I'll say it, thank you bftb0
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
escalavee said:
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
Click to expand...
Click to collapse
Did you try re-downloading the file at all?
E: corrupt file: system/framework/com.htc.resources.apk
E: verification failed.
I am redownloading now. I thought of that a few minutes ago.
Yes, I have full use of the track ball. I don't know what bootloader version I have, and it is rebooting again, so I can't check right now...
Thank you for trying to help!
ETA: HBOOT v 1.49
recovery v 1.6.2
radio 2.42.01.04.27
escalavee said:
E: corrupt file: system/framework/com.htc.resources.apk
E: verification failed.
I am redownloading now. I thought of that a few minutes ago.
Yes, I have full use of the track ball. I don't know what bootloader version I have, and it is rebooting again, so I can't check right now...
Thank you for trying to help!
ETA: HBOOT v 1.49
recovery v 1.6.2
radio 2.42.01.04.27
Click to expand...
Click to collapse
If it doesn't work this time, download it with a different web browser.
gnarlyc said:
If it doesn't work this time, download it with a different web browser.
Click to expand...
Click to collapse
Will do. Thanks.
What happened? I can't access the page now to redownload...
I said screw it and tried to open it with IE, and I got a 404.
Nevermind. I got it. Durf.
escalavee said:
I do have amon-ra recovery. When I flashed it aborted. The error message states a corrupt file. My phone is rebooting now. I am going to reflash to tell you the exact corrupt file. Give me a minute?
Click to expand...
Click to collapse
bad download or you corrupted it when you transfered it from your pc.
Use AFV the from the market to verify the checksum of the zip file on the SD card.
When you transfer large files from the PC you always always need to perform a "safely remove hardware" before you unmount from the Eris or remove the USB cable.
bftb0 said:
bad download or you corrupted it when you transfered it from your pc.
Use AFV the from the market to verify the checksum of the zip file on the SD card.
When you transfer large files from the PC you always always need to perform a "safely remove hardware" before you unmount from the Eris or remove the USB cable.
Click to expand...
Click to collapse
Good to know! Thanks. I will try again and let you guys know.
Again, I really appreciate all the help.
workshed said:
btw bftb0, thank you for all the help with the uber technical issues around here. Your knowledge is very much appreciated, yeah I'll say it, thank you bftb0
Click to expand...
Click to collapse
+1 bftb0 helped me figure out my first bricked eris was fubar, more importantly helped me understand why, so the next time I had a soft brick I had taken the preemptive steps necessary to save it. Thanks bftb0
This is making me crazy!
Another corrupt file: system/framework/framework.odex
I did safely remove hardware, and this download was done on IE instead of FF.
I am going to keep trying until I get this done.
USSENTERNCC1701E said:
+1 bftb0 helped me figure out my first bricked eris was fubar, more importantly helped me understand why, so the next time I had a soft brick I had taken the preemptive steps necessary to save it. Thanks bftb0
Click to expand...
Click to collapse
Hey I saw the post about the thanks cherry... that made me giggle on the inside a little...
ETA: I am a dirty lurker...
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Hey do I need the radio image? I can try downloading the one without the radio image...
USSENTERNCC1701E said:
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Click to expand...
Click to collapse
You know, I tried flashing nonsensikal 15.2 a couple days ago, and I kept getting a corrupt file error with that as well.
Maybe my recovery IS corrupted!
This is insane.
USSENTERNCC1701E said:
Try flashing a different custom ROM, possible your recovery has become corrupted. If flashing another ROM doesn't work reinstall AmonRA and try FlashBack again. If it does work, I'd try FlashBack again, just for ****s and giggles.
Click to expand...
Click to collapse
Do I have to uninstall my old version of amon-ra before I reinstall?
escalavee said:
This is making me crazy!
Another corrupt file: system/framework/framework.odex
I did safely remove hardware, and this download was done on IE instead of FF.
I am going to keep trying until I get this done.
Click to expand...
Click to collapse
Uh, I know you are in a hurry, but ...
It is impossible for Amon_RA to install a corrupted ROM file.
Read that again: It is impossible for Amon_RA to install a corrupted ROM file.
If it passes the verification step in Amon_RA, then the ROM .zip file is OK
Now, if something fails during the install, then there are three possible causes:
- The SD card is flaky, and file reads are erratic (which could allow the verification pass in Amon_RA to succeed, but the subsequent read to fail).
- Prior operations on the phone have corrupted one or more partitions on the phone so that insufficient space remains in the partition you are writing to.
- Flaky hardware.
Does the error with the specific file you mentioned happened during verification or afterwards during the install process?
bftb0
BTW, there are two different "1.49.nnnn" bootloaders - you need to be precise.
escalavee said:
Hey do I need the radio image? I can try downloading the one without the radio image...
Click to expand...
Click to collapse
escalavee said:
Do I have to uninstall my old version of amon-ra before I reinstall?
Click to expand...
Click to collapse
Not unless you have flashed a new radio at some point, and I would recommend avoiding that. I've lost recovery twice, one of the times I was able to just use jcase's 1 Click Eris Root and the other time I had to reflash the recovery, try the 1 Click first, I need to research the procedure for a Terminal Emulator flash again, last time I used FastBoot instead.
Nevermind, I'd follow bftb0, he's far wiser, and I was doing some rather whimsical stuff with my phone and KGB when I lost my recovery.
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 was flashing MeanBean to the newest version 3.09 from 3.07 i was currently on. I cleaned delvik and cache hell I even did the system and it sits in boot. So after many reflashed of 3.09 i finally decided to flash a different rom all together. That rom stays in boot. I'm S-on btw. I dont know what to do. I'm disabled and live alone so I need my phone. Thank you guys very much in advanced.
Sounds like your TWRP may need to be upgraded to the latest. You will have to go to the teamwin website and update using fastboot since you can't boot into the rom. If you have a nandroid backup you should try to restore that first.
cruise350 said:
Sounds like your TWRP may need to be upgraded to the latest. You will have to go to the teamwin website and update using fastboot since you can't boot into the rom. If you have a nandroid backup you should try to restore that first.
Click to expand...
Click to collapse
Or he can just flash the latest TWRP from recovery since he can get in there.
exSD said:
Or he can just flash the latest TWRP from recovery since he can get in there.
Click to expand...
Click to collapse
I have a newer version ive been meaning to flash thats on my sd card. I have no naindroid backup. Please let me know the steps to installing the newest twrp from bootlaoder. Thank you.
I need the newest twrp zip. All i can find are images for the newer version. the last .zip is the version im actually using 2.3.3.0 . If anyone has the newest one, please email it to me at [email protected].
http://techerrata.com/browse/twrp2/jewel
Download 2.4.3.0 .img.
Fastboot flash it. http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
Ill try thank you. I was thinking I needed to be able to boot up to use that. Thank you. Hang tight as Ill update this asap. Note to self, Update twrp every new version that drops unless told to go back one version.
parasurfer1979 said:
Ill try thank you. I was thinking I needed to be able to boot up to use that. Thank you. Hang tight as Ill update this asap. Note to self, Update twrp every new version that drops unless told to go back one version.
Click to expand...
Click to collapse
You just need to be able to get to the bootloader. So long as you have your PC/Linux set up with adb you can run the adb fastboot command and install the recovery then adb reboot.
exSD said:
You just need to be able to get to the bootloader. So long as you have your PC/Linux set up with adb you can run the adb fastboot command and install the recovery then adb reboot.
Click to expand...
Click to collapse
Ok I'm in fastboot and theres a usb unrecognize flag. I go to program manage and My HTC under Android phones has a "hazard". With the following after I open it...
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Im on Windows 8 btw. Im headed over to the HTC site to see if maybe there are updated drivers.
Any Ideas? Thank you guys for responding so expiditiously.
parasurfer1979 said:
Ok I'm in fastboot and theres a usb unrecognize flag. I go to program manage and My HTC under Android phones has a "hazard". With the following after I open it...
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Im on Windows 8 btw. Im headed over to the HTC site to see if maybe there are updated drivers.
Any Ideas? Thank you guys for responding so expiditiously.
Click to expand...
Click to collapse
Download these drivers:
http://downloadandroidrom.com/file/HTCEvo4GLTE/drivers/HTC_Driver_64.zip (64 bit)
http://downloadandroidrom.com/file/HTCEvo4GLTE/drivers/HTC_Driver_32.zip (32 bit)
---------- Post added at 10:59 AM ---------- Previous post was at 10:49 AM ----------
Here's a zip of 2.4.1.0 I found from the TWRP thread in the Original Android Dev board. Can't find a zip of the latest. This one should serve you well though.
Rename to PJ75IMG.zip and place in the root folder of your SDCARD, then boot to bootloader.
http://db.tt/lMZDGfOU
GOD bless YOU...
I noticed before i red your post my HTC drivers were very old. version 1.07 lol. Thanks HTC for telling use we might want to update. And thank you for the twrp file. That helps big time. Keep you all Posted.
parasurfer1979 said:
I noticed before i red your post my HTC drivers were very old. version 1.07 lol. Thanks HTC for telling use we might want to update. And thank you for the twrp file. That helps big time. Keep you all Posted.
Click to expand...
Click to collapse
Im putting in sd card but when bootloader scans, its not finding. Is there a specific place i should be putting this?
parasurfer1979 said:
Im putting in sd card but when bootloader scans, its not finding. Is there a specific place i should be putting this?
Click to expand...
Click to collapse
First, make sure you renamed it properly.
Then, make sure you're putting it in your external SD card, not your internal. If you don't have an external, then just place it in /sdcard
You would be right!!!
exSD said:
First, make sure you renamed it properly.
Then, make sure you're putting it in your external SD card, not your internal. If you don't have an external, then just place it in /sdcard
Click to expand...
Click to collapse
It loaded. Gonna flas a rom now. Ill keep you posted. BRB in 5-10min.
parasurfer1979 said:
It loaded. Gonna flas a rom now. Ill keep you posted. BRB in 5-10min.
Click to expand...
Click to collapse
When i bring up the bootloader it update twrp and when i select recovery, it reboots to a black screen. How do i pull out the file so it doesnt reinstall twrp every time. It wont open twrp so i can remove the zip. Could that zip file be bad?
Do i need to select clear storage in bootloader?
Does it take time for twrp to load? I dont remember my phone doing this on the last twrp install.
Just remove the SDCARD from the back and you won't have it try to install it every time.
It doesn't take long for TWRP to load really. After the installation, boot into the Recovery through the bootloader.
If he is s-on I didn't think he could flash a recovery through the bootloader.
Update your drivers and try to install the recovery through fastboot.
You didn't need to make a new thread in the wrong section for help as people were already helping you.
Sent from my EVO using xda app-developers app
NaterTots said:
If he is s-on I didn't think he could flash a recovery through the bootloader.
Update your drivers and try to install the recovery through fastboot.
You didn't need to make a new thread in the wrong section for help as people were already helping you.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It indeedworked after removing sd card loading rom again now. I've been rooted so long that i forgot. ill update again shortly.
parasurfer1979 said:
It indeedworked after removing sd card loading rom again now. I've been rooted so long that i forgot. ill update again shortly.
Click to expand...
Click to collapse
Im still getting stuck in boot. I'll try another rom I use.
After many lost hours of sleep, I finally give up and come to the community for help. I've seen the problems I'm having posted a lot, but I've not yet found a solution.
To start, all was well with my KitKat 4.4 ROM, except that my SIM would not read. So in my troubleshooting process, I did a full system wipe of everything through TWRP v2.6.3.0 (including internal memory), knowing that my ROM and other necessary files were saved on my SD card. The problem now is that TWRP will not show that I actually have an SD, so I'm stuck with no OS now. I've tried everything I've seen, such as formatting and properly "ejecting" the SD from my computer after doing so. I've tried three different SD cards, two 16gig and one 2 gig. Still won't read.
The only other thing I can think to do is use ADB to push or sideload - my device does not show at all when I try. Same result with fastboot. I'm suspecting that the issue with this is the driver. So far, after searching for hours and hours, the only driver I've found to use with the E970 is the usb_driver downloaded through SDK Manager. When I use this driver, it shows my phone as Google Galaxy Nexus ADB Interface in the Device Manager. But still no luck with ADB or Fastboot.
So I apologize if either of these has been solved one or more times before, but I'm desperate for help. Thanks!
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Rishi. said:
AFAIK , there is a special modded TWRP version for KK Geeb that is patched to read SD Cards.
You'll have to search it or wait till someone who has it posts it here. But I have read about that somewhere , it's just that I am not able to recall. If I find it , I'll post asap.
Click to expand...
Click to collapse
As of right now, my phone has no ROM installed. I'd be willing to bet that it wouldn't read from an SD even before I tried my first ROM, but I don't really know since I never tried. Stupid on my part for not doing so before the wipe. I'll look into the modded TWRP, and hopefully it'll get me somewhere. Thanks for the help!
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Rishi. said:
I assume it shouldn't be hard to push the modded recovery to the phone via ADB. Then you would be able to get the SDcard recognized and flash the rom of your choice.
Or second choice stands as LGNPST , then flash alt./orig. teenybins , which'll give you TWRP 2.5.0.0 or something similar to it. You can flash the new modded TWRP using that as well.
Click to expand...
Click to collapse
The problem with this is that I can't get ADB to find my device. If that were the case, I'd just push the ROM straight to my internal memory since that's the only one it sees. I've tried and double checked many times to make sure I was doing the ADB process properly. As far as I can tell, I am. Which leads me to think its not the proper driver for my phone. But I can't find any others.
I thought about LGNPST, but I can't get the phone into download mode without an OS. And that's the only way I know to use LGNPST.
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Rishi. said:
You can get the phone to download mode , even without a ROM. The Download mode is initiated , right at phone start up. I think you may be doing it in a wrong way or so , that's why it's not booting up in dload mode. Check the TeenyBins thread , and see if you are doing it right way.
If your phone is booting then LGNPST will work most probably.
Click to expand...
Click to collapse
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
SmithZ33 said:
You're absolutely right! I had entered download mode more than a few times before, so I knew how to do it. But I guess in my sleep-deprived and frustrated state, I must have been forgetting something. Just got it into download mode on the first try. I feel like starting fresh with a stock ROM is best, so it's working on that right now.
Thanks coming your way!
Click to expand...
Click to collapse
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Rishi. said:
Take enough sleep , before flashing next time. Last time I remember when I was sleep deprived and did some flashing , I ended up with a partial brick. :lol:
Start fresh with teeny bins. Then FLash the stock rom using recovery. ( Don't LGNPST the stock .tot file.( Use LGNPST just to throw in the correct TWRP recovery and update partitions with TeenyBins ). I would recommend flashing the stock JB .zip file using TWRP recovery . (Created by SnowLeopardJB ). ) Check his thread.
Post if you face any issues. ::highfive:
Click to expand...
Click to collapse
Well, I opted to use LGNPST to flash TeenyBins and a TWRP that read my SD. Flashed the KitKat ROM just to try it, and it boots perfectly but I'm back to no SIM. So I'll be moving on to this new issue... haha
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Rishi. said:
So you didnt slept...huh .. lol.
Sent from my LG-E970 using Tapatalk
Click to expand...
Click to collapse
Haha, no I didn't. Between work and travel, I'm still trying to figure out this sim issue. It won't detect my sim on this ROM, or others it seems. I tried on a LiquidSmooth 4.3.1 ROM just now and it had the same issue. It's almost as if it has the detection set backwards. When I insert the sim, it thinks I've removed it and says ”sim removed." Then when removed, it says ”sim inserted” or something along those lines, and wants to restart. I'm at a loss, and I'm wondering why it could be doing this.
[SOLVED]
Turns out CMW 6.0.4.7 will not flash to this device - solution was to use the app "Flashify" from the play store which simply and easily installed TWRP
Thanks joshm.1219!
[SOLVED]
I am at a complete loss for a fix. Short story is: I wasn't receiving any MMS, so I finally decided to ODIN back to stock and used this method so I could keep my data. Here's what happened next:
- ODIN passed but I couldn't get past the Verizon logo
- Tried several suggested fixes but the last resort one worked; I wiped data & factory reset (thus defeating the purpose of the no-wipe ODIN... w/e)
- Everything loads fine, TouchWiz works but I get a Factory Mode popup and can't lock my screen. (still can't lock my phone even now but will use this method if I think I'm stuck with TouchWiz)
- I use this method to unlock bootloader and root - root confirmed.
- Try to install CWM recovery or TWRP (btw, where the hell did GooManager go and why is it so hard to find now) and they say successful but I simply can't boot into them, just keep getting the factory recovery screen which won't let me flash any roms or any non-signed .zips
- MMS Still doesn't work!
- I call VZW in desperation and somehow they magically reset my account services and MMS works again! (I probably could have done this in the first place and not lost my ROM/Data and sanity if I'd known)
I have looked high and low for a solution but have found none. I also have been unable to find a REGULAR stock MDK file to flash on this phone - I can only find the NO-WIPE version which doesn't even allow you to keep your data. I'm confused and frustrated and would love some active help, I just can't find the right threads/posts/ect.
Thank you kindly for any advice.. I love my S4 and have been using PA, PAC, CM and other ROMS since the day I got it - I need that back! TouchWiz is just... I just don't like it.
Try this one.
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
FernBch said:
Try this one.
link
Click to expand...
Click to collapse
Thanks for the original stock.. sadly I am still ending up with the Android System Recovery and despite installing CWM Recovery, I just can't get to it. I also still get the ridiculous Factory Mode popup.
Any ideas? I'm so sad :'(
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
FernBch said:
From off it's either home+volume down+power or home+volume up+power. One boots into stock recovery the other will boot into CWM.
Hold all three until you see some small blue text in the upper left of the screen.
Click to expand...
Click to collapse
Thanks for the effort but I'm well aware of that. As I said in the OP, I've been using custom ROMs on this since day one - the issue is that I cannot boot into CMW Recover, despite having a successful install via the app.
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
877
FernBch said:
Dumb question, which app are you using? I use RomManager to install CWM (up to 6.0.4.7) and I have a flashable zip of 6.0.5.0.
Click to expand...
Click to collapse
I'm using ROM Manager but it won't work. I'd love to try ODIN flashing the CWM Recovery if you have the file for my MDK build.
I may have it on my PC at home. When I get there (60-90 min) I'll look. If I do I'll post up to Dropbox and give you a link.
Ok, I've searched my HDD and I don't have the CWM file. What I do have is the MDK all-in-one root+recovery tool for the I545. I can put it up and upload it if the file isn't too large but I don't know if that'll help you.
CWM 6.0.5.0 flashable zip is in the CM11 thread but I don't know if the recovery image in the file is good for you, either
Just use Flashify to get TWRP
joshm.1219 said:
Just use Flashify to get TWRP
Click to expand...
Click to collapse
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
voice.lex said:
I was about to complain about your assumption that I knew what that was.. then I found it on the play store and it actually worked! Thank you so much - now here's to hoping I can find a nice stable 4.4.4 ROM to put back on here!
I'm still at a loss for why ROM Manager was unable to flash CWMR but I guess I don't _need_ to know, I am so happy this is a big step after 3 days of touchwiz hell!
Click to expand...
Click to collapse
As far as I know, the latest CWM doesn't work on our devices.
joshm.1219 said:
As far as I know, the latest CWM doesn't work on our devices.
Click to expand...
Click to collapse
Well, that explains it - Thank you so much!
voice.lex said:
Well, that explains it - Thank you so much!
Click to expand...
Click to collapse
No problem :thumb:
This thread might be dead, but rather than starting a new one for what is probably a stupid question, I'll ask it here and see what happens. I've been having major trouble flashing any 5.0 rom on my MDK VZW S4....Seems like every ROM fails when flashing. I have a feeling my issue is an outdated version of TWRP (2.5.0.2), but I am very hesitant to update because it seems like everyone has been having issues with 2.8.1.0. With this being said, are you guys currently running the most current version of TWRP and would you mind advising which .img file worked via Flashify? Not sure whether to use the jfltexxx or jfltevzw...or if it even matters.
I'm sure I've left out pertinent information, but let me know what I'm missing and I'll update accordingly.
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
760hacker said:
I've been using the latest version of TWRP 2.8.1.0 and running Euroskank Lollerpop with zero issues. Coincidentally, TWRP just got updated today to 2.8.3.0 which i have yet to flash but will do so shortly. I would recommend JFLTEVZW based on my usage. Not sure if the other variant works or not but it appears you have a verizon device so stick with JFLTEVZW.
Click to expand...
Click to collapse
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
swh969 said:
Thank you very much for getting back to me. When you flashed 2.8.3.0, was it a .zip file from recovery or a .IMG through flashify or another app? Thanks again for your help!
Click to expand...
Click to collapse
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
760hacker said:
.IMG file, flashify is so simple!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm going to give it a shot! Thanks again for your help.
Worked like a charm. Thanks @760hacker