Sorry but I need some help. When upgrading roms a few times, no problems ever occurred. CWM always worked smoothly. Now, I have the Resurrection Remix 1.0 Pro installed and was attempting to upgrade to Resurrection Remix 1.2 AOKP. I see that when running CWM I only had to choice to access the "download" folder on the scard. When attempting to install the Remix 1.2 rom, I always end up with an e signature fail. I tried several times but had the same results. I had to reboot and stay with Remix 1.0 until someone can help me get the upgraded rom installed. I wiped all the data and reset, and don't know what else to do.
Please help!!
OK, not sure the procedure you made... but might also be that some files you got were corrupted. Check to see they all are fine before going ahead with this way to install:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*if have more problems, just reply here.
Is the file on an external SD?
It's wherever you put it, though some files will only flash properly from external SD.
I think it's the internal sd
felixg123 said:
Is the file on an external SD?
Click to expand...
Click to collapse
At first I thought I had the files on the external sd card, but when rebooting in recovery with CWM it looked like it was only allowing me to access the download folder on the internal sd card.
Thanks for any suggestions.
cyberboob said:
It's wherever you put it, though some files will only flash properly from external SD.
Click to expand...
Click to collapse
The CWM that came with the remix 1.0 pro rom is that weird one that seems to have to boot from the other little app. Do you recall this is the CWM zip file that was added to the files to download for the remix 1.0 pro rom. It doesn't appear to have the same flexibility that the CWM had that came with my previously used rom...remix 9.4
Any comments??
With 1.0 its 3e (stock recovery) so you have to put cwm.zip in your external SD or your cache then flash it through 3e. Now you have cwm. If its the one from westcrip its touch so don't use the volume buttons.. actually touch the screen.
Hopefully that helps.
Sent from my GT-I9100 using XDA
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
cyberboob said:
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
Click to expand...
Click to collapse
Now, I'm really scratching my head. When I try installing the 1.3 rom it begins ....but returns this message and then aborts.
E: failed to verify whole-life signature
E: signature verification failed
I re downloaded the rom 1.3 to make sure it wasn't corrupt, and it did the same thing. Then I downloaded remix 1.2 just to see if this would install properly. I got the same result with the failed signature coming up in red and then it aborts. So something is not allowing me to change roms?? At present I have remix 1.0 installed.
Please I need some assistance figuring this out. I don't know what to do now?
Thanks in advance
Check if your current rom is having any beta releases of siyah 3.0, if so then it would be the cause, download cf root, or any latest version of custom kernel in tar format and flash it via Odin, now enter cwm and flash the new rom, you would be good to go
#*posted on the move *#
Works fine ....but is there a GPS problem?
I got the darn thing installed. Thanks. I was able to install the CWM......one that worked properly and the remix 1.3 got installed without a hitch. One problem I'm noticing the the GPS taking a whole bunch of time trying to locate sats. Is there is gps fix ??
Thanks
go to the Emergency FAQ for 1.3 (in my sig)
Related
I am trying to install the new Obsidian based on froyo 2.2 with the Samsung Vibrant. I rooted it using the one click root and downloaded ROM manager. When I try to back up my current ROM the phone reboots and says E: Can't open /cache/update.zip (bad) Installation aborted.
Because of this I cannot install the Obsidian ZIP file because the same error message pops up.
redownload rom and dont use rom manager, it will erase your internal sd card. Use clockwork recovery and then flash a fresh downloaded obsidian rom
crxforya said:
redownload rom and dont use rom manager, it will erase your internal sd card. Use clockwork recovery and then flash a fresh downloaded obsidian rom
Click to expand...
Click to collapse
I use ROM Manager like 50 times a day and my SD card never gets wiped.
is clockwork recovery within ROM manager? So i click on Reboot into recovery or Flash ClockworkMod Recovery? Thanks for the help also.
Wait, is this your first time flashing a ROM? Walk us through what you've done so far.
I'm guessing you had your USB plugged in, and didn't get a good flash of clockwork. Unplug your USB, go into clockwork, and flash the latest version of clockwork. Then reboot, go back into clockwork, try to backup and see what you get
Here is what I did:
1. One-click root
2. Download ROM Manager from market
3. Downloaded Obsidian and placed it on my SD card via USB
4. Opened ROM Manager and clicked Backup current ROM, which is where i got the error message that /cache/update.zip could not be read
5. Tried to install obsidian by clicking Install ROM from SD Card and choosing the obsidian that I put on my SD card and I get the error saying /cache/update.zip could not be read (bad) installation aborted.
FIRST WRONG SECTION
notw thats out of the way, In Rom manager click reboot into recovery, then if you have blue text on your screen click reinstall packages, thenmanually pick thee rom to flash from the other (green text) recovery
PS WRONG SECTION
Iuse think free office. Navigate to download folder. Click the zip. Hit Clockworkmod recovery. Ok. Ok. Now let it do its thing. Enjoy. Personally I don't like it.. im back to fusion... didn't like lack of black. and double tap features... big down sides for me... and twiz.. so I'm back to fusion1.2... and LOVE IT! Only one to beat it is Bionix themselves and I'm waiting very patiently!
sgsV bionix.. If ya don't got it GET IT!
DanglaGT said:
Here is what I did:
1. One-click root
2. Download ROM Manager from market
3. Downloaded Obsidian and placed it on my SD card via USB
4. Opened ROM Manager and clicked Backup current ROM, which is where i got the error message that /cache/update.zip could not be read
5. Tried to install obsidian by clicking Install ROM from SD Card and choosing the obsidian that I put on my SD card and I get the error saying /cache/update.zip could not be read (bad) installation aborted.
Click to expand...
Click to collapse
Was your USB mounted to your computer when you clicked "Flash ClockworkMod Recovery" in ROM Manager? That will cause the error you have.
If so, disconnect from the computer, reboot, launch ROM manager, flash clockworkmod, and then try to backup your current ROM again.
WoodDraw said:
Wait, is this your first time flashing a ROM? Walk us through what you've done so far.
I'm guessing you had your USB plugged in, and didn't get a good flash of clockwork. Unplug your USB, go into clockwork, and flash the latest version of clockwork. Then reboot, go back into clockwork, try to backup and see what you get
Click to expand...
Click to collapse
Yes this is my first time.. I have never really had the motivation to, but I want froyo really bad so I am trying to get this down. I don't really know what clockwork recovery is or how I get it, all I have is ROM Manager and a rooted Vibrant.
DanglaGT said:
I am trying to install the new Obsidian based on froyo 2.2 with the Samsung Vibrant. I rooted it using the one click root and downloaded ROM manager. When I try to back up my current ROM the phone reboots and says E: Can't open /cache/update.zip (bad) Installation aborted.
Because of this I cannot install the Obsidian ZIP file because the same error message pops up.
Click to expand...
Click to collapse
Read my other post... don't check either one.. back up all your stuff with pc or titanium. I used tbu its wonderful.
sgsV bionix.. If ya don't got it GET IT!
DanglaGT said:
Yes this is my first time.. I have never really had the motivation to, but I want froyo really bad so I am trying to get this down. I don't really know what clockwork recovery is or how I get it, all I have is ROM Manager and a rooted Vibrant.
Click to expand...
Click to collapse
One in the same here brother. Read my posts before. I'll try to help you through here, but you are in the wrong section, and this post isn't long for this world. A couple tips for you:
1) Read up on these programs you are using. Thankfully you're dealing with a mostly unbrickable phone, but I don't think anyone here is looking forward to walking you through an Odin recovery. You can **** stuff up. Write that down on a piece of paper in front of you.
2) Read the forum guidelines. People will be a lot nicer if you post in the correct forum.
Ok, sorry for not posting in the appropriate forum. I think I got it and my mistake was not flashing clockwork because when I backup my current ROM I no longer get that error. Right now I am using Titanium Backup to backup my stuff and then I am going to try the Obsidian flash again.. but does the Titanium Backup save my text messages?
DanglaGT said:
Ok, sorry for not posting in the appropriate forum. I think I got it and my mistake was not flashing clockwork because when I backup my current ROM I no longer get that error. Right now I am using Titanium Backup to backup my stuff and then I am going to try the Obsidian flash again.. but does the Titanium Backup save my text messages?
Click to expand...
Click to collapse
Good, good. A bad clockwork flash is the only thing I've ever seen cause that error message. At least you've given a good google reference for other people that mess that up.
I've never used Titanium backup for anything other than app backup, so I don't know about texts. I believe it can be done, but I don't know what to select. Maybe take a look in the market? I think there are some SMS backup apps there if that's all you're concerned about.
OP -
I had the exact same problem as you, and I tried everything. Surprisingly enough, what fixed it for me was how I copied the ROM zip file to the phone. When I mounted the phone to the computer and dragged and dropped, I got the error. I had tried copying the file at least 3 or 4 times this way, and I always got the error. The error went away when I decided to try an ADB push of the zip file to the Internal memory card. I still don't know why it fixed it for me, but it's worth a try.
DanglaGT said:
Here is what I did:
1. One-click root
2. Download ROM Manager from market
3. Downloaded Obsidian and placed it on my SD card via USB
4. Opened ROM Manager and clicked Backup current ROM, which is where i got the error message that /cache/update.zip could not be read
5. Tried to install obsidian by clicking Install ROM from SD Card and choosing the obsidian that I put on my SD card and I get the error saying /cache/update.zip could not be read (bad) installation aborted.
Click to expand...
Click to collapse
Wrong section dude. But um when you said u only opened rom manager to press back up current rom?..if so you got that error cause the wrong update.zip is on the root of sd...go back to rom,manager and click flack cwm click allow when it asks for root,n then pick the vibrant one.
OP - Do not worry about backing up your current ROM. You are going to 2.2 and your ROM now is 2.1. IF you decide to go back to a 2.1 ROM flash an all new one (ie. Bionix Fusion or Final) that comes with a 2.1 Kernel. If you try to go to your backed up ROM though Rom manager without getting a new kernel you will soft brick your phone, and as you stated this is your first try, a soft brick can be a little scary. To be on the safe side delete your backup in your phone now so you won't forget and be tempted to go back to that old ROM without the proper kernel installed and ready to be flashed also in your phone. Just wanted throw that out there for ya!
Anderdroid said:
I use ROM Manager like 50 times a day and my SD card never gets wiped.
Click to expand...
Click to collapse
+1. Never had an issue with my sd being wiped. I use clockwork at lest once a day.
Sent from my SGH-T959 using XDA App
Thread moved to Q&A.
Maybe it's a noob question, but after update to 2.2, how do I revert all the apps and games I have currently on Bionix 1.1. I can reinstall them, but what about save states? Any way to transfer that when update is done to Froyo, or we always need to start from scratch on every new update?
Hi, I tried installing CM7 via the CWM/zip method, which appeared to succeed by actually resulted in a boot loop. Found a couple of messages from people with the same problems but no solution.
So. Does anyone have one of the CM7 ROMs in tar image format?
Timmmmmm said:
Hi, I tried installing CM7 via the CWM/zip method, which appeared to succeed by actually resulted in a boot loop. Found a couple of messages from people with the same problems but no solution.
So. Does anyone have one of the CM7 ROMs in tar image format?
Click to expand...
Click to collapse
You'll find it here:
http://forum.xda-developers.com/showthread.php?t=1151396
This is the direct link to the uploading site, but it's not connecting now.
http://www.multiupload.com/N8VH6IUWOP
That's for CWM recovery, not CM7.
Also, you have heard about megaupload ... haven't you?
Timmmmmm said:
That's for CWM recovery, not CM7.
Also, you have heard about megaupload ... haven't you?
Click to expand...
Click to collapse
Sorry, I'm tired and read it wrong.
But it's worth trying to reflash Clockworkmod. Make sure it's the EXT4 and not the RFS version. I made that mistake before which got my CM7 stuck in a bootloop.
CM7 doesn't come in .tar format. It only comes in .zip format, which can be downloaded here:
http://www.clockworkmod.com/rommana...t.js&name=psyke83&deviceName=Samsung Galaxy 5
Don't forget the Google Apps Package as well:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
And the link I gave was multiupload, not megaupload.
Heh, I am also tired! Thanks for the hint...
Timmmmmm said:
Heh, I am also tired! Thanks for the hint...
Click to expand...
Click to collapse
my personal suggestion is to use Odin to flash the CWM recovery (use the 0.5 or 0.7 version, NOT the v0.6 tar files): once booted in the recovery, do the 4 wipes (if you have the phone fully charged; if not don't do the Battery Stats Wipe); usually I also use to format the partitions, you'll find that in the Mounts menu.
Now, always from the Mounts menu, mount the sdcard as USB mass storage and copy here all the files you need to flash: usually a upgrade-****** package, an hotfix and gapps (full or minimal package that's your choice). Unmount from PC and then unmount fro phone.
Now flash normally by Install zip from sdcard and do as always: first the update-***** archive, than the hotfix and finally the gapps ones.
Now reboot and enjoy!
That's my personal how-to, which never makes me falling into a bootloop!
brainvision said:
my personal suggestion is to use Odin to flash the CWM recovery (use the 0.5 or 0.7 version, NOT the v0.6 tar files): once booted in the recovery, do the 4 wipes (if you have the phone fully charged; if not don't do the Battery Stats Wipe); usually I also use to format the partitions, you'll find that in the Mounts menu.
Now, always from the Mounts menu, mount the sdcard as USB mass storage and copy here all the files you need to flash: usually a upgrade-****** package, an hotfix and gapps (full or minimal package that's your choice). Unmount from PC and then unmount fro phone.
Now flash normally by Install zip from sdcard and do as always: first the update-***** archive, than the hotfix and finally the gapps ones.
Now reboot and enjoy!
That's my personal how-to, which never makes me falling into a bootloop!
Click to expand...
Click to collapse
hi brainvision im new to the gti5500 forum but hav been flashing roms on my wildfire for ages, my wife asked me to sort her mob out coz it kept messin up. so i did the dutiful thing and followed status's thread in the dev section and got a bootloop like a few other peeps on that thread but it doesnt seem to be any answer to this problem. i hav also tried installing the official firmware from sammobile but that jst loads the 3 screen then flashes samsung at me foreva. do you hav any suggestions of how i can fix this, im not bothered wot rom goes on as long as the mob is opperational for my wife.
thank you for your time
Did you perform data and cache wipe before flashing CM7 files and gapps package?
The way to install is always the same, so provide me some details or I cannot tell you more than that..
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
This thread is for noobs by noobs , a place to talk about the app so that we don't clutter the ROM threads .
I hope this works out and helps anyone including myself with using this app.
Here is another GUIDE by JJsax posted on The Root Of All EVO that is a lot more detailed then this one.
The Official forum for BootManager is Init2winit if you would like to learn even more about the app.
As I learn about this app ,as to how and what works with it I'll update this and maybe it will help everyone out that is trying to use BootManager.
This app also works with EVO 3D's with hboot 1.50 s-on
Thank XDA member mnomaanw for that information.
If you use this app and have the time to reply to this post , please share what ROMs you've got to work and a little info on how you installed it. This way I can add it to the op to make it easier and faster for everyone to find.
This is what I've learned so far.
How to install* ROMs via Boot Manager...
Thank seraph863 for filling me in and writing this up. I just changed a few details cause his was for a specific ROM.
MAKE SURE THE ROM IS ON THE ROOT OF YOUR SD CARD NOT IN ANY FOLDERS
1.)* PURCHASE Boot Manager. It does a License check upon boot, so your jacked version will just give you a headache. Seriously, I tried it. Doesn't work.
Here is a Market link to Boot Manager if you didn't already purchase it.
1.a) IF you didn't purchase it... WIPE ALL Boot Manager data and files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging.
3. Open BootManager. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now. [ You will need to set up your Phone ROM any time you flash a new ROM or kernel to your phone ROM.]
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded ROM.zip file. Make sure to check the Wipe System, Data, and Cache boxes so that it will wipe before it flashes the ROM. Select EXT4 as the file structure.
[This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.]
8.) Once the install has been successful if you need to flash a kernel , theme gapps etc..., go back to Slot 1 and select Install .zip (again). Choose the .zip file. Do NOT wipe system, data or cache. It will ask you to over write it just hit OK.
9.) You should now be ready to boot to your new ROM! Celebrate!
Since this is for the EVO 3D I recommend to always use ext4 as your file structure.
If you get any error messages start over.
Known working ROMs to my knowledge.
These are ROMs that I've set up.
Infected Eternity Phone ROM and sd ROM
KMyers CM7 beta 7.4* with gapps ext4 sd ROM
MeanROM ext4 sd ROM
TrevE Zone v2.3.12 ext4 phone and sd ROM
Mikrunny ext4 phone ROM and sd ROM
XDA members setups
JJsax setup
CDMA Evo3D
hboot 1.50 s-on
TWRP 2.0 touch recovery
Phone ROM SteeleROM 2.73
ROM1 CM9 (The latest version couple days old)
ROM2 Evervolve ICS
mnomaanw's set up
PhoneROM: ViperROM Redline v2.5 RC2
ROM1:CyanogenMOD9
ROM2:MIUI v2.1.6
I've found it to work better to flash and set up my ROM on the phone ROM and then back it up and restore it to a slot.
If your having problems restoring backups and your using TWRP recovery try using CWM. I was having issues with TWRP and since I went back to CWM (touch and 5.0.2.0 both work great but there is no usb mount on the touch version) and I haven't had a single issue restoring a backup to a ROM slot.
My setup will be changing all the time.
CDMA EVO 3D
Eng Hboot s-off
Radio 1.06.00.1216
Phone ROM Infected Eternity Sense 3.0
ROM1 Mikrunny
ROM2 EVOZone
ROM3 SteelROM
ROM4 MeanROM Aria51
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
JJsax said:
Thank you for putting this here. I know I'm to blame for going off topic in some threads about Boot Manager.
I too am having issues getting a ROM to load into slot 1.
Here's my setup...
SteeleROM 2.73
Anthrax #2 kernel
Over 5GB of storage space available.
HBOOT 1.50
TWRP 2.0 recovery (the newest touch one)
I load steele just fine as the phone ROM then try to load CM9, or whatever other ROM into slot 1 it goes through everything then it get's killed at mounting img's. I have it setup for screen on, to load large files, and I even have SU logging turned off. This happens everytime I try to load a ROM into slot 1 it just kills it and never finishes 100%
Click to expand...
Click to collapse
Mine say they install fine and they finish but when I hit boot to the slot it just gets stuck on the splash screen.
I had TrevE Zone on my phone ROM but just switched to eternity. I got MeanROM to install in slot 2 and it booted up fine and is running great but thats the only one I out of the 3 I tried. I set the boot.img to large or what ever the setting is cause thats what they said to do in the video on the site for the app. My real issue though is that restoring my backup to a slot it installs to my system memory. I would like to be able to install backups cause I've read they run better. Hopefully some that knows more about this will come in here and school us a little, I'll even add it to the op and make this a guide if we get enough info.
Here's my quick and dirty instructable I posted in the CM9 thread.
How to install this via Boot Manager...
1.) PURCHASE Boot Manager. It does a License check upon boot, so your cracked version will just give you a headache. Seriously, I tried it. Doesn't work.
1.a) IF you didn't purchase it... delete ALL Boot Manager files, including the folder on your SD Card. Then buy it and let it setup again.
2.) Open SuperUser. Hit Menu -> Settings -> Disable Logging
3. Open BM. If you're at work and on Wi-Fi, you may not pass the License check due to firewall issues. If you get a black screen, or license failures, uninstall BM and delete the folder. Switch to 3/4G and try again.
4.) If all is good, you're asked to Setup the Phone. Do so now.
5.) Once installed, hit Menu -> Settings -> Force Large Boot.img
6.) Swipe right to Slot 1. Hit Install .zip and browse to your downloaded CM9 .zip file. Wipe System, Data, and Cache. Select EXT4 as the file structure
7.) This is the important part. This build will take a LONG time. Do NOT use your phone while it is running.
8.) Once the install has been successful, go back to Slot 1 and select Install .zip (again). Choose the Google Apps .zip file. Do NOT wipe system, data or cache.
9.) You should now be ready to boot to your new ROM! Celebrate!
Warning: Several users report to NOT use any Backup app such as Titanium to restore your apps and data, since the apps on this ROM are very very different. Your mileage may vary.
FYI I'm doing this by memory, so the minor steps might not be accurate (i.e. disable Superuser logging).
If you get any error messages, start over. I assure you, this process worked for me step by step.
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
kylon said:
Go to their official forum
Applications-->boot manager
You will find my thread named [REF]working and not working rom list
There are many phones
And if you test a rom that is not listed please report if it is working or not
Thanks
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I was on there I even posted my issue and my log but haven't gotten any help. I did see your list of ROMs but didn't know if its up to date.
I'll have another look at it cause I really want to get this to work and its driving me crazy cause I can usually figure problems out on my own or by searching but I just can't get this.
Thanks for the replies.
linsalata28 said:
I saw your guide in the cm9 thread and tried it with no luck I did exactly what you said and everything seemed to go fine but when I hit boot to ROM on slot one where I installed the ROM I'm stuck on the splash screen. Any ideas why? Thanks for the help also.
Click to expand...
Click to collapse
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
seraph863 said:
Which ROM are you using?
I would start over. Use a file manager to delete your ROM from the SD Card and take another image. Make sure you have plenty of storage on your SD card. You could also try clearing the Cache and Dalvik.
You can always get back to your phone ROM manually by booting to Recovery and flashing sdcard\bootmanager\phonerom\update.zip
Edit: Don't forget to check "Use Large boot.img" within Boot Manager
Click to expand...
Click to collapse
Should I just delete the whole bootmanager folder and clear the data for the app also?
another thing is why when I restore a backup to a slot its installing to my internal memory?
Yeah I just had another look at your list and there aren't many ROMs for this phone on there and they look old.
Thanks again for the help.
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
I wiped everything out and starting over. I'm going to just try and install viperom in one slot and see if that boots, then I'm going to try and restore a backup to another slot from within a ROM slot to see if that will fix my internal memory issue cause it wont have anywhere to install to . I'll post back with what happens.
kylon said:
It up to date
Anyway gflame is busy
What do you do to install the rom
And wich rom?
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
linsalata28 said:
I went into recovery to go to flash the update zip to restore my phone ROM but when I open the bootmanager folder I don't see anything in it. I'm using twrp 2.0 recovery. Could this have something to do with my problems?
Click to expand...
Click to collapse
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
seraph863 said:
The steps in your previous post were all correct, except you said you turned OFF "Use large boot.img" ? Make sure that option is ENABLED (has an X on it)
I'm confused as to why the app is trying to install to your internal memory... Mine installs to my SD Card. Make sure the USB cable is not plugged into the phone, and try increasing your screen timeout so it doesn't sleep during the install.
The fact that you're getting the splash screen means you're getting somewhere. Maybe you're being too impatient on the install? Wait a few minutes even after it says Install Complete before continuing.
Click to expand...
Click to collapse
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
linsalata28 said:
I disabled logging in su checked off larg boot.img then whet to slot one hit install zip choose cm9 ext4 then checked all the wipe opinions, when that finished I flashed the gapps the same way but without wiping . Everything finished with that I didn't get any errors but when I went to boot to that slot it just hung at the splash screen.
I did that 2 times with cm9 , 1 time with the Eternity ROM sense 3.0 r130 , 1 time with Team Nocturnal's Blackened ROM and they all got stuck at the splash screen.
I did get MeanROM to work using those same steps last night.
Now with the restore of my backup I did basically the same thing but it doesn't give any wipe options when you install it but it would get an error saying boot.img something like that and then I would get a low memory popup saying I only had about 30mb left internal memory when I had over 800mb when I started.
Edit: I have about 6gb free on a 16gb class 10 sd card. I believe its a Samsung card I think.
Edit2: I finished flashing viperom and now that to is stuck on the splash screen. Is there a way to wipe caches for that slot and fix permissions like you would for a regular ROM in recovery if something like this happened.
I'm really starting to think I wasted $3 this is very frustrating sorry.
Thanks for your replies and trying to help.
Click to expand...
Click to collapse
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
linsalata28 said:
I said I checked the larger boot.img off meaning it was enabled sorry for that misunderstanding. I flashed 2 of the slots last night and didn't even test them till today so I don't think that its cause I'm not waiting long enough. Why would none of the folders inside of the bootmanager folder show up in twrp recovery? Could I copy and paste the phone update.zip to the root of my sd card so that I can recover without having to nand restore cause I've already wiped and restored about 10 times trying to get this to work.
Sent from my Eternity 3D using tapatalk
Click to expand...
Click to collapse
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
spookytay said:
My phone:
Phone ROM: SteelROM 2.72
Slot 1: AOSP ICS - wifi doesn't work
Slot 2: CM9 - (google talk and books FC)
Slot 3: MIUI
Slot 4: CM7 (kmeyers)
Boot Manager has a problem trying to restore from a NAND backup, it did the same thing to me where it was installing to the phone's internal memory. I was trying to figure out the problem, but I moved on without success.
I've had the best time installing tricking ROM's by this method. I installed CM7 to a slot, booted into CM7 and installed the ICS and CM9 from there. It's been pretty successful.
If you are getting it to freeze with mounting images, I came across this issue because my SD card did not have enough room. You can try to free up some more space to see if this is the same issue.
I had most problems installing due to not enough space on my SD card, I now have a 32gb card, and have had no issues
Also, I've never had to set it to large boot.img to get things to work, and make sure you disable logging in SU, and use EXT4
---------- Post added at 02:08 PM ---------- Previous post was at 02:04 PM ----------
To quickly get back to your phone ROM (make sure you setup your phoneRom in boot manager first to create the update.zip file, you need to recreate this anytime you change the ROM or Kernel for your phoneROM)
Boot into Recovery
Install the update.zip inside the \boot manager\phonerom\update.zip (not sure if location is accurate, but you get the idea)
Reboot system
Phone should boot to phone ROM, or you can install any other update.zip from your slots, to boot to them etc
Click to expand...
Click to collapse
What cm7 ROM would you recommend ? For some reason I couldn't see files inside of the BootManager folder but I checked and they are there. I have about 5gb free on a 16gb card ,I was looking into getting a 32gb if I get this app working.
Sent from my Eternity 3D using tapatalk
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
I've purchased boot manager and when i run it, it says "application not licenced" Any fix?
spookytay said:
try
http://forum.xda-developers.com/showthread.php?t=1393613
I upgraded my card, I had about 3-4 gb free and was having problems, but once I upgraded I haven't had many since
Click to expand...
Click to collapse
cm7 worked thanks.
Hi
I have flashed the cyanogenmod 7.1.0 on my htc legend which went fine, but after som time i realized the gps wasn't working, i tried for severel hours all kinds of gps fix advices i found in google but without any luck.
Because of this i want to go back to stock android 2.2 or 2.3 if possible.
I am having some problems returning to stock android and again tried severel guides.
I tried downloading the newest htc sync and run a RUU update but the updater can not connect to the phone, no htc sync support in cyanogenmod is the problem i think.
I tried downloadning severel different image files of different versions of android on to the sd card and rebot to recovery mode throug clockwork and tried flash a zip file from sd card. But either the update stops because the file is "bad" or it need a newer version of something the cyanogenmod updated when it was installed.
I can see i should be able to do a nandroid backup if i have made such one, guess the guide i used didnt mention that, only i shoud remember to backup my pictures/music/sms....
If you need any more information please ask
Hi,
try this sequence:
1. Open ROM manager application
2. Scroll down to "All clockworkMod recoveries" and click on it
3. choose from that list 2.5.0.7 and press OK
4. Now download a sense ROM from XDA like Blay0's ROM here http://forum.xda-developers.com/showthread.php?t=866849 (if you want to keep this rom download also the patch for upgrade to b0.8.4)
5. Copy the ROM and patch to the SD card
6. From the ROM manager reboot into recovery
7. In recovery mode wipe data and cache
8. Still in recovery mode instal zip from SD card: first the b0.8 ROM and then the b0.8.4 patch
9 Reboot
Now you should have a stock based ROM and do whatever you like (go back to really stock rom which I don't reccommend)
Let me know how it works!
Thanks ill give it a try
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
rudyo78427 said:
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
Click to expand...
Click to collapse
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
also, you need to be on software 2.17.605.2-which I assume you are to be unlocked
Aldo101t said:
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
Click to expand...
Click to collapse
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
yes the zip needs to be on ext-sdcard not the internal card.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
rudyo78427 said:
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
Click to expand...
Click to collapse
what version of twrp are you using-the is an official twrp 2.4.3 now
http://techerrata.com/file/twrp2/fireball/openrecovery-twrp-2.4.3.0-fireball.img
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
rudyo78427 said:
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
there is an option under wipe for system.
---------- Post added at 01:16 PM ---------- Previous post was at 01:10 PM ----------
Aldo101t said:
rudyo78427 said:
there is an option under wipe for system.
Click to expand...
Click to collapse
you should wipe data/factory reset--wipe cache--wipe dalvic--wipe system then install rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
rudyo78427 said:
...I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen...
Click to expand...
Click to collapse
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Atomic83 said:
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Click to expand...
Click to collapse
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Success!!!
rudyo78427 said:
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Click to expand...
Click to collapse
Success!!!!! Thanks for the last tip to try a lower recovery version. Seems TWRP 2.4 on up didn't work allowing the Aroma Installer to complete installation. I have downgraded to twrp version 2.3.3.0 and the ROM's flash now. Thank you XDA community!!! :laugh:
rudyo78427 said:
... I erase every thing 3x as stated in various posts ....
Click to expand...
Click to collapse
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Edit: TWRP 2.4.3.0 and newer seem to have trouble with Aroma
mdmower said:
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Click to expand...
Click to collapse
Thanks for the feedback, mdmower. I had done a complete format of my sd card on the comp and loaded only the zip file on the card. I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe. All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully. I have since flashed Pizzuto claw's and now running ViperLTE. I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
rudyo78427 said:
I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe.
Click to expand...
Click to collapse
First thing, drop this habit. A single factory reset will suffice.
rudyo78427 said:
All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully.
Click to expand...
Click to collapse
Issues with aroma and TWRP versions 2.4.3.0 and greater have been confirmed (possibly other 2.4.x releases). The folks behind TWRP suspect a problem with make_ext4fs, but it is unclear whether the blame lies within TWRP, the update_binary, or the particular make_ext4fs called by Aroma.
rudyo78427 said:
I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
Click to expand...
Click to collapse
Read the first post in the CM thread. Others have successfully used CM outside the U.S.