Android OS Forum banner
1 - 6 of 31 Posts

· Developer
Joined
·
709 Posts
Hey sorry I guess I don't know the backstory to this. Why does this process even need to be done? I flashed from the older droid x 2nd-init to 5.0.1.0 then a few days later to 5.0.2.0 all with rom manager, no problems. What problem are other people having?
 

· Developer
Joined
·
709 Posts
to the guys having problems, i propose an experiment....

in root explorer, go to /preinstall/recovery/ and put this inside: http://dl.dropbox.com/u/11695745/recovery.zip

go to the root of your sdcard and put this inside: http://dl.dropbox.com/u/11695745/cwm.sh

now go to terminal emulator, type sh /sdcard/cwm.sh

if it works let me know and ill upload a little fix package for you guys so that rom manager will work.
 
  • Like
Reactions: Iceman0803

· Developer
Joined
·
709 Posts
Iceman0803 said:
So far no go. Not enough space in /preinstall/recovery/ for recovery.zip. Is it safe to delete any files from that folder?
you should already have a recovery.zip in there. if not, that's your problem right there. rommanager calls

Code:
dd if=/sdcard/clockworkmod/download/download.clockworkmod.com/recoveryies/recovery-clockwork-5.0.2.0-shadow.zip of=/preinstall/recovery/recovery.zip
that right there says you need a /preinstall/recovery/recovery.zip file to convert and copy to! if its not there, its because rom manager hasn't been able to create the file, probably because of this memory issue.

so if you have a recovery.zip already in there, delete it and replace it with mine. if it's not there... post back here to comfirm.

EDIT: go into /preinstall/app/ and delete nfsshift, you'll have room then for sure. if my suspicions are correct, rom manager might even work after that without you having to do anything lol... as it will now have room to convert and copy the 5.0.2.0 into /preinstall/recovery/, allowing it to load that recovery
 

· Developer
Joined
·
709 Posts
go into /preinstall/app/ and delete any apk's you don't use, NFSShift would be a great one to delete if its there because its huge.

after that, try using rommanager without even doing anything else... it might work if my suspicions are correct.

if it doesnt work, then go back and do what i told you with the recovery.zip and cwm.sh.
 

· Developer
Joined
·
709 Posts
Are you able to use rom manager now or do you have to use my script every time?
 
1 - 6 of 31 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top