Related
I am unable to try my progress that i've made so far on a rom i tried configuring. i'm still new to this stuff. I don't have a right-click command to re-sign roms, so i use autosign out of the dev box (android sdk tools) and everytime i sign the rom, i don't get error, yet i try booting them up on my CDMA HERO.....NO LUCK
Any tips?
bmxerkid954 said:
I am unable to try my progress that i've made so far on a rom i tried configuring. i'm still new to this stuff. I don't have a right-click command to re-sign roms, so i use autosign out of the dev box (android sdk tools) and everytime i sign the rom, i don't get error, yet i try booting them up on my CDMA HERO.....NO LUCK
Any tips?
Click to expand...
Click to collapse
Do you get an error when you try to flash the ROM?
I've used both EasySign (http://android.grdlock.net/index.php?&direction=0&order=&directory=HTC Droid Eris/Extras) and dsixda's kitchen (link at top of this forum) to sign with no issues.
gnarlyc said:
Do you get an error when you try to flash the ROM?
I've used both EasySign and dsixda's kitchen (link at top of this forum) to sign with no issues.
Click to expand...
Click to collapse
I don't get an error when trying to flash the rom onto the phone. It goes about saying:
*opening packages.......
Installing packages.......
*
and cuts out and doesn't install the rom. I wipe data all the time and sometimes dalivck cahce.
Its takes me back to the menu of:
Install update.zip
chose zip.......
When i sign, no errors appear. I'm using clockwork mod.
But i will try EasySign
I downloaded the kitchen and the cywgin packages were claimed to be installed but it doesn't work? Anything going wrong?
bmxerkid954 said:
I downloaded the kitchen and the cywgin packages were claimed to be installed but it doesn't work? Anything going wrong?
Click to expand...
Click to collapse
Do you get any errors? I use the kitchen in Windows everyday, so it should work for you too.
No, i get absolutey no errors whatsoever, i will re-download and install and ill get back to you.
Got it. Its works now......except, i got rid of my hero. I'm getting an evo tomorrow. So i will see if i can resign a already signed rom. I'll get back to you.......
I am trying to change my wifes rom on her phone and her trackball is broke. So I installed the latest version of CWM to see if it would enable and need features so I could navigate in recovery. No luck and now I can't back up her via rom manager either I just get an error. So what I am wondering is the an alternate way to work through cwm without the trackball and whats up with this error after I updated it. Thanks in advance for your help
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
superdusto said:
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
Click to expand...
Click to collapse
Make sure the backup file has no spaces between anything like backup-4627 not backup 4627 no spaces you'll get an error
Sent from my ERIS using Tapatalk
TheGratefulDead said:
Make sure the backup file has no spaces between anything like backup-4627 not backup 4627 no spaces you'll get an error
Sent from my ERIS using Tapatalk
Click to expand...
Click to collapse
That wasn't the problem just tried and am still getting the same error
Sent from my Thunderbolt using XDA Premium App
superdusto said:
The error is e: can't open /cache/update.zip
(Bad)
Installation aborted
Sent from my thunderbolt using XDA Premium App
Click to expand...
Click to collapse
I believe that this message implies that the download was bad (i.e., and incomplete file or a mis-matched MD5 signature).
I'm not that familiar with ClockworkMod or ROM manager, but have a peek at this thread: http://www.droidforums.net/forum/koush/47399-upgrade-rom-rom-manager-problem.html since it seems to describe what you are seeing.
If you are downloading your first directly to your phone, you can check your MD5 with Astro File Manager (long-press file name, select details, and wait a little bit for the MD5 checksum to appear).
You could also try my app, AFV (Android File Verifier). It has several checksum options, including MD5 and SHA1. You can use its "Verify Jar-type File" to verify the integrity of a signed file even if you don't know the MD5 checksum.
Cheers!
scary alien said:
I believe that this message implies that the download was bad (i.e., and incomplete file or a mis-matched MD5 signature).
I'm not that familiar with ClockworkMod or ROM manager, but have a peek at this thread: http://www.droidforums.net/forum/koush/47399-upgrade-rom-rom-manager-problem.html since it seems to describe what you are seeing.
If you are downloading your first directly to your phone, you can check your MD5 with Astro File Manager (long-press file name, select details, and wait a little bit for the MD5 checksum to appear).
You could also try my app, AFV (Android File Verifier). It has several checksum options, including MD5 and SHA1. You can use its "Verify Jar-type File" to verify the integrity of a signed file even if you don't know the MD5 checksum.
Cheers!
Click to expand...
Click to collapse
I am not downloading a rom I have the rom. So that doesn't help much. Any other ideas? no recovery options that doesn't use track ball?
superdusto said:
I am not downloading a rom I have the rom. So that doesn't help much. Any other ideas? no recovery options that doesn't use track ball?
Click to expand...
Click to collapse
Yeah, sorry...I wasn't exactly sure...
I know that ClockworkMod lets you navigate its menus without using the trackball, but most rooted folks use Amon_RA's custom recovery.
A while back, I created a trackball-optional version of Amon_RA's recovery for the Eris. Here's the thread I created over on AF re. this:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Here's the post in RA's thread over here on XDA: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Hope this helps!
Cheers!
Not sure if this helps but I had the same problem when I flashed my friend fascinate. But they use odin to flash their clockwork (voodoo) I had to run the root script then install the rom to fix the update.zip. Any ideas?
superdusto said:
Not sure if this helps but I had the same problem when I flashed my friend fascinate. But they use odin to flash their clockwork (voodoo) I had to run the root script then install the rom to fix the update.zip. Any ideas?
Click to expand...
Click to collapse
lol...sorry, no. I've only heard that Odin (timely Thor-related reference, eh? ) is used for the Samsung phones.
There are others around that know and have used ClockworkMod on the Eris, but they are relatively few and far between (plus, things certainly seem to be slowing down in the various Eris forums recently). There have also been some unexplained brickings of phones using CWM that have scared off potential users of that custom recovery, so most have stayed with and use Amon_RA's.
scary alien said:
lol...sorry, no. I've only heard that Odin (timely Thor-related reference, eh? ) is used for the Samsung phones.
There are others around that know and have used ClockworkMod on the Eris, but they are relatively few and far between (plus, things certainly seem to be slowing down in the various Eris forums recently). There have also been some unexplained brickings of phones using CWM that have scared off potential users of that custom recovery, so most have stayed with and use Amon_RA's.
Click to expand...
Click to collapse
Well thanks for your help so far is their a post on how to set up adb so I can flash Amon_RA. I think my problem is that I rooted with amon and just downloaded rom manager so I put CWM on it.. Must be affecting my update.zip
superdusto said:
Well thanks for your help so far is their a post on how to set up adb so I can flash Amon_RA. I think my problem is that I rooted with amon and just downloaded rom manager so I put CWM on it.. Must be affecting my update.zip
Click to expand...
Click to collapse
Yes, at the bottom of the first post in the AF forum thread are the installation instructions and one of them is how to do it with adb ("Scenario 4").
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Sounds like you are already familiar with adb, so you should be very close .
Let me know if you need anything else.
Cheers!
You saved me Thank you so much for your time here have some thanks!!!
superdusto said:
You saved me Thank you so much for your time here have some thanks!!!
Click to expand...
Click to collapse
You are most welcome! Glad you got things going .
I keep getting these warm-and-fuzzies from folks that my efforts for building the trackball-optional recovery was well worth it (with kudos and thanks again to RA for his help in filling-in the key gaps in how to build it).
Cheers!
My trackball has not worked pretty much since I bought the phone. I have found is you plug in your usb charger and lift up firmly the trackball works with no issues at all. Just FYI. And here's to the dev's that keep our end of life eris fast and up to date. And no sense thank GOD. lol
Yep, that is a definite way to work it ... I was unable to ROOT for over 2 months after getting my Eris b/c my trackball didn't work. It wasn't until I found this advice over in DF that I was finally able to negotiate the recovery menu.
HOWEVER (!!!) After almost a year of moderate flashing/recovery use, my USB/AC charger barely works anymore. I have to put weight on the USB near the connec w/ the phone to get it to recognize & charge.
I have tried to install the Amon_ra trkball not req script but couldn't get it to work ... I just use CWM these days b/c I don't need to use the damn thing !
Good thing I am coming up for an UPGRADE
Sparticusx said:
My trackball has not worked pretty much since I bought the phone. I have found is you plug in your usb charger and lift up firmly the trackball works with no issues at all. Just FYI. And here's to the dev's that keep our end of life eris fast and up to date. And no sense thank GOD. lol
Click to expand...
Click to collapse
Hey guys, i don't usually make posts for every question i have, unless i absolutely don't find an answer searching or googling. I find myself in the position where i want to customize my Hyperdroid ROM and i can't manage to install DOC's Surgeon.
I think maybe the file i find in AndroidMeda Rom Tool is just an update, and not a full release, but being a noob is difficult, and i really didn't managed to pass this!
So, long story short, how can i flash a surgeon that is on androidmeda rom tool? I tried the Surgeon_Lucid_v5.0.zip and i can't get through, it fails to install under recovery mode.
I would very much appreciate a solution to my dumb question, hope i don't irritate somebody.
mightyvenom said:
Hey guys, i don't usually make posts for every question i have, unless i absolutely don't find an answer searching or googling. I find myself in the position where i want to customize my Hyperdroid ROM and i can't manage to install DOC's Surgeon.
I think maybe the file i find in AndroidMeda Rom Tool is just an update, and not a full release, but being a noob is difficult, and i really didn't managed to pass this!
So, long story short, how can i flash a surgeon that is on androidmeda rom tool? I tried the Surgeon_Lucid_v5.0.zip and i can't get through, it fails to install under recovery mode.
I would very much appreciate a solution to my dumb question, hope i don't irritate somebody.
Click to expand...
Click to collapse
You should download again, and apply the surgeon in the rom tool!
sonyz7 said:
You should download again, and apply the surgeon in the rom tool!
Click to expand...
Click to collapse
I have already done that...
Have you asked on the Hyperdroid thread. I think you may have more luck.
Sent from my GT-I9100
sxi200 said:
Have you asked on the Hyperdroid thread. I think you may have more luck.
Sent from my GT-I9100
Click to expand...
Click to collapse
Unfortunately i can't post there, i don't got the minimum 10 posts...ridiculous i know :-<
Quote from Android system recovery <3e>:
"E: missing bitmap password_retry_45 (Code -1)
E: missing bitmap password_notmatched_45 (Code -1)
E: missing bitmap password_max16_45 (Code -1)"
When installing multi-csc it says the following (also in android system recovery):
"-- Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/KOR/system/'.
Successfully applied multi-CSC."
Have you changed the kernel from the one that comes with Hyperdroid? As the OTA tool will only work automatically with the kernel the rom comes with.
If so you will need to download the file via the OTA tool, find where it saves, should be somewhere in the SD card (Hint /sdcard/Hyperdroid_Androidmedia)
Reboot into CWM recovery
Flash the zip manually.
veyka said:
Have you changed the kernel from the one that comes with Hyperdroid? As the OTA tool will only work automatically with the kernel the rom comes with.
If so you will need to download the file via the OTA tool, find where it saves, should be somewhere in the SD card (Hint /sdcard/Hyperdroid_Androidmedia)
Reboot into CWM recovery
Flash the zip manually.
Click to expand...
Click to collapse
Thanks, i will try that right away and report back
mightyvenom said:
Thanks, i will try that right away and report back
Click to expand...
Click to collapse
even if you changed kernels you can still flash stuff that you download from the OTA tool. So say you want to download Docs surgeon. Download it through the OTA app and then rather than apply now press apply later. Then try and get into recovery..there install zip and go through the folder were it says hyperdroid androidmeda...there you have all the files you have downloaded and just flash like you would normally do something...But only use this if you want to change kernels..My advice is the same as the guy above posted..Use the kernel provided by the team and you should not have any problems flashing stuff through the OTA app...
It worked fine, thank you again. Now i figured, indeed the change of my kernel led to that conflict.
Cheers guys!
mightyvenom said:
It worked fine, thank you again. Now i figured, indeed the change of my kernel led to that conflict.
Cheers guys!
Click to expand...
Click to collapse
Huh, I didn't think about you changed the kernel. Pongster's HDK kernel is very good, don't change that in my opinion.
So, Im glad that your problem solved.
Tapatalk
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
vectorer said:
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
Click to expand...
Click to collapse
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
superbay said:
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
Click to expand...
Click to collapse
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
vectorer said:
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
Click to expand...
Click to collapse
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
superbay said:
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
Click to expand...
Click to collapse
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
vectorer said:
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
Click to expand...
Click to collapse
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
superbay said:
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
Thanks. It's HTC One X+, I got there from a Google search for sideload as I know zero about it. As it turns out it didn't work, got to 22% then failed every time. I'll check out that link now.
Thanks again.
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
vectorer said:
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
Click to expand...
Click to collapse
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
Click to expand...
Click to collapse
how would i do this operation??
now no matter what i try i get
error: closed
vectorer said:
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
Click to expand...
Click to collapse
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
vectorer said:
how would i do this operation??
Click to expand...
Click to collapse
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
vectorer said:
now no matter what i try i get
error: closed
Click to expand...
Click to collapse
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
superbay said:
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
Click to expand...
Click to collapse
thanks I'll keep trying this weekend
vectorer said:
thanks I'll keep trying this weekend
Click to expand...
Click to collapse
Just keep posting here to see how far your effort is with it. Good luck
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
vectorer said:
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
Click to expand...
Click to collapse
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
superbay said:
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
Click to expand...
Click to collapse
Well nothing is working.
I guess my device is a paperweight even if I can get into recovery.
Can't flash anything, not even the RUU, can't sideload........nothing.
Tried Hassoon's instructions for the RUU but it won't reconise that a device is attached to go into Bootlaoder, sideloading ALWAYS fails at 22%. Others seem to overcome this but I cannot. It's frustrating reading how many problems are solved when nothing works for me.
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.