Is there an sbf to flash clockworkmod recovery similar to the SPRecovery file used in the "how to root any droid regardless..." method? I've tried flash_image from terminal but get a not found error even though i know the clockwork.img file is right there at /sdcard. RomManager reports that it's flashed clockworkmod but when i reboot into recovery there's SirPsycho's green droid. Some alternate method to change my recovery back to clockworkmod would be greatly appreciated.
Background: Last night I restored my original rooted 2.1 nandroid backup to retrieve some notes and got distracted by a phone call and left it on too long. Maybe I missed my chance to avert disaster, so be it, but when i picked up my phone it was at the "ready to install update" screen and i *think* i just turned it off and tried to reboot into recovery. ( i was still distracted ). I became undistracted when i found that instead of good ol' CWR i had the white triangle / phone icon and no user recovery. So I sbf'd SPR onto it, then the busybox/su/root file, then rebooted, opened RomManager, flashed CWR, set up a restore to my current CM6.1RC3 and let it reboot. No joy; SPR came up instead and just sat there. Since then i've gone back into RM and "reflashed" CWR a few hundred times, tried several times to unsinstall and reinstall RM (same result). I've also downloaded the correct CWR.img file and tried to flash it from terminal emulator, no joy. I've tried using ROM Manager to flash an older version of CWR and can't, getting "An error occured while flashing your recovery."
lol i've also (inadvertantly/frustratedly) ended up removing the recovery altogether (probably from accidentally initiating an SPR backup and then battery pulling when it was an hour later and still not finished); after that booting while holding the "X" was stuck at "M"; but reflashing the SPR file from RSDLite got me the SPRecovery again.
When I have freshly flashed the SPR.sbf file, or flashed alternate recovery in RomManager, it reports SPR as the current recovery, and when i "flash" CWR from RomManaGER, it changes and reports that CWR 2.5.01 is the currently installed recovery, but no matter what i've tried, when i boot into recovery the text is blue not green. grr.
i've searched quite a bit before posting and am quite frustrated at this point. i've got a bazillion nandroid backups, but they are all clockwork and not SPRecovery format. The only way I now seem to be able to flash a different recovery is via RSDLite.
SO, either an sbf file to flash ClockworkModRecovery, an alternate way to change my recovery, or if there were some way to use SPR to restore from a nandroid backup created with CWR, but i'm not sure if the recovery itself is in the nandroid backup?
not pulling my hair out yet, but quite a bit past simple frustration.
TIA!
nevermind. after trying everything including reformatting my SD card, i took the latest update to RomManager and it successfully reflashed CWM. lol 69 views. Thanks for the tips.
Clockwork only sbf
Teddy helped me immensly on droid-forum when i had this issue, but i came across one of the things i could have used back then recently so wanted to post it up here if anybody else ends up in this situation.
Here's an .sbf that will reflash clockworkmod recovery, from Raidzero's thread on his RZRecovery:
http://rzdroid.com/ftp/recovery/Clockwork_2.5.0.1_sholes_recovery_only.sbf
CWM for Milestone?
Are U sure?
No, not at all. Forgot this was a combined device forum; I'm only talking about the Droid.
If all the recoveries and tools I've mentioned work on a milestone too I don't know. Apologies for not being more specific.
Sent from my Droid using Tapatalk
No problem... just that milestone uses Open Recovery...
Sent from my Milestone using XDA Premium App
Related
Here's the sequence of events, wonder if anyone can point me in the right direction for repair.
I am on Froyo, the initial leak rooted by Paul.
I wanted to get my market working, so I found this billg market fix + busybox update zip.
I installed RomManager, and it suggested I flash ClockworkMod Recovery, so I did. It guessed my phone correctly (I think) as the "Nexus One (GSM)". I'm now no longer totally sure - but that IS the T-Mobile version right?
Anyway, I flashed clockworkmod recovery, and then I chose the market fix, and then I rebooted.
Everything seemed OK but the first warning sign was no graphical boot screen (no sparking multi-colour X). It booted up OK but no connection to the network at all. I can not even enable wi-fi.
Not I'm not too sure what to do, would hate to make matters worse. I can boot into recovery and it is ClockworkMod recovery, but of course there are no backups on that thing I can restore to. I was using AmonRA recovery before.
Any thoughts?
TIA Paul
paulvallee said:
Here's the sequence of events, wonder if anyone can point me in the right direction for repair.
I am on Froyo, the initial leak rooted by Paul.
I wanted to get my market working, so I found this billg market fix + busybox update zip.
I installed RomManager, and it suggested I flash ClockworkMod Recovery, so I did. It guessed my phone correctly (I think) as the "Nexus One (GSM)". I'm now no longer totally sure - but that IS the T-Mobile version right?
Anyway, I flashed clockworkmod recovery, and then I chose the market fix, and then I rebooted.
Everything seemed OK but the first warning sign was no graphical boot screen (no sparking multi-colour X). It booted up OK but no connection to the network at all. I can not even enable wi-fi.
Not I'm not too sure what to do, would hate to make matters worse. I can boot into recovery and it is ClockworkMod recovery, but of course there are no backups on that thing I can restore to. I was using AmonRA recovery before.
Any thoughts?
TIA Paul
Click to expand...
Click to collapse
find a froyo radio update from somewhere. there on alot of the rom pages
and flash a new rom after the radio and see what happens
The latest clockworkmod is buggy for me too. You can flash back to amon's recovery in fastboot.
Quick update
Flashing the Froyo radio update was no help.
I re-flashed Amon RA recovery and now I'm reapplying the original Paul's frf50.
Fingers crossed.
Phew, OK I'm back on the air.
Now I have to try to figure out how to apply the market fix without using ClockworkMod!!!
Thanks for help/advice.
Paul
paulvallee said:
Phew, OK I'm back on the air.
Now I have to try to figure out how to apply the market fix without using ClockworkMod!!!
Thanks for help/advice.
Paul
Click to expand...
Click to collapse
Is it a zip you flash in recovery?
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
JohnPublic said:
Ok. I was running completely stock 2.32.651.2 on my HTC Hero CMDA. I had never rooted before. In the past as various points I had tried a few of the one click methods here and there with no luck, but I never had really done my homework and gave it a serious shot. Over the christmas break my brother in law and I were discussing phones and he told me that he thought Z4root would one click root me and encouraged me a bit not to be scared about trying it. This, combined with my dwindling internal memory gave me the push I needed to be serious about getting a custom rom onto the phone, but no matter what I do I can't seem to get anything to work. Here is an account of the steps I have taken so far.
-Downloaded Z4Root
-Ran Z4Root. It seemed to lock up, and after about 15 minutes I pulled the battery.
-Ran Z4Root again. It stuck on "Rebooting...", but phone was not locked up.
-Checked Apps drawer and found Superuser installed.
-Downloaded Rom Manager and successfully flashed ClockworkMod Recovery.
-Booted to recovery with Rom Manager and manually made a nandroid backup.
-Selected a custom rom (CM6.1) with Rom Manager with "wipe data and cache" selected. Phone booted to recovery and seemed to successfully load CM6.1, phone rebooted itself back into recovery. Whenever I selected reboot phone it would reboot back into recovery.
-Restored my nandroid.
-I then tried to load AOSPmod and NFXStock using the Rom Manager. Both locked up on the initial white HTC screen.
-I then tried to load CM6.1, AOSPmod, and NFXStock manually in recovery, making sure to wipe boot, system, data, and cache in the partitions menu with no success.
-I then ran z4root again and unrooted/rerooted. Each time I run it, it sits on the "rebooting" screen for up to 30 minutes. Phone is not locked up and if I rerun the program it tells me I have root.
-After speaking with some people on AOSP's irc channel I was able to get S-off (I was following instructions and don't recall the exact steps to do this), but with S-Off I tried flashing various roms using the H-boot method with them named HERCIMG.zip Same results: CM 6.1 booted to recovery, AOSPmod and NFXStock both lock on HTC screen.
Next I flashed 2.31.651.7 with the Hboot using a HERCIMG.zip I downloaded via this thread: http://forum.xda-developers.com/showthread.php?t=804692. I then used this thread to root the phone: http://forum.xda-developers.com/showthread.php?t=804296. After rooting I installed Rom Manager, flashed my recovery, and made a nandroid. I then tried to load CM 6.1. Same result; it loaded to the recovery screen. AOSP and NFXSTock both stuck on the HTC screen. I flashed my original nandroid back to my rooted 2.32.651.2
This morning I decided to try the PC RUU route and downloaded the official 2.27.651.5 RUU as provided in this thread: http://forum.xda-developers.com/showthread.php?t=694572. When I try to run it however, I get an error on my PC screen: Error [140] Bootloader version is incorrect.
ARG! Please help me to get a custom running!
Thanks,
JohnPublic
Click to expand...
Click to collapse
try amon ra recovery, full wipe including dalvik and flash one of the roms you listed above, like cm6.1 stable (from cyanogenmod.com) with the gapps (from jaybob413's rom thread in hero development). once it starts the boot, give it time, it may take a long time (10 min.) Hope it works.
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Now don't I feel silly! I re-downloaded CM6.1 and put it on the card and it seems to be firing up. I'm on the CM logo bootscreen right now. I have no idea how three separate zips all got corrupted en route to my card, but I suppose that must be what happened. Thanks for the help!
JohnPublic said:
I flashed RA 1.6.2
Wiped Data/Factory Reset
Wiped Dalvik Cache
Install zip from sd:
When I try CM6.1 I get the error:
E:Corrupt file: system/fonts/DroidSansFallback.ttf
E:Verification failed
When I try NFXStock I get the error:
E:Corrupt file: system/lib/libiconv.so
E:Verification failed
I don't have AOSP on my card right now to try it.
Click to expand...
Click to collapse
have you tried re-downloading the roms? it sounds like something is missing in them, which shouldn't be. if you are downloading from your phone, try a download from a computer and see what happens. where are you dl'ing the roms from? verification failure makes no sense..... also, did you recently update rom manager from market to 3.0.0.7? there was something listed in the changelog about verification failure fixed when using other recovery, i think....
EDIT: saw your last post, maybe your browser was acting up? delete the bad ones, get new ones, flash away
Is there a way to get rid of the clockwork mod boot on the nook color
As per onstuctions on this site, I got a 1.1 pre roote version and installed it
from the sd card with the clockwork menu which informed me that the
"NookColor" install complete.
when I reboot, it starts with the welcome message,but then only reboots into the same recovery menu.
At this point I would just like to go back to a stock rom, but cannot boot anything but the recovery.
By the way, I can boot froyo from the sd card
Please help me
I've moved your thread to the correct forum.
So you dont have the CWR sdcard in? Because if you did, you would need to remove that first. Sorry if this dumb, but thats all I can think of right now. Maybe reflash the 1.1 pre rooted rom? Or follow the instructions in Samuelhalff's "Easily restore to stock" thread located here in the Nook forums.
The "Easily restore to stock" saved the day. I am now up and running.
Thanks
How did you do that? I have CWR on mine and I went to buy a book from the shop on the Nook and it downloaded and installed 1.1... Now when I try to go back and restore from backup CWR doesn't respond... All it does is sit there and if I select something from the menu it goes to the background image (the circle with the top hat) and sits there. I would like to remove this so I can reroot my Nook...
Thanks for any help.
Bob
See the other thread or sticky that's labeled "How to Restore to Stock easiliy." I believe you can also use the power down and on 8 times trick to restore to stock as well.
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
porear said:
Same thing happened to me. I used Clockwork to flash the CWR-removal.zip on the restore thread mentioned above and it fixed my boot, everything else was OK.
Click to expand...
Click to collapse
Ditto that. I reinstalled CW and everything seems to be working fine. Has anyone else had issues with using Rom Manager on the NC? I've had to go back to stock twice whenever I've used it.
I had a problem when trying to roll my 1.1 rooted NC back to stock because I futzed it up that I ended up in a CWR loop. 8 resets didn't get me a reflash, it got a recovery. Took me finally getting the NC flashed and rerooted at 1.1 a second time when I reinstalled ROM Manager and ended up with the problem again. Took me this wasted effort to realize that CWR runs in lieu of the reflash if CWR is installed and that's an obvious problem when I wanted a reflash and not restore a different backup.
There is a thread with a zip that CWR can run that blasts CWR off and reflashs stock and getting that done put me back both times I messed up above.
Seems to me that perhaps the whole "can never brick" response when people ask for help needs to have an addendum about how CWR gets in the way of an 8 reboot reflash and provide guidance on how to get that update file and use it instead to get back to square one. (Plus some advice on when to clear caches and data partitions to avoid weirdness later).
Now rerooted on 1.1 with no ROM Manager running but I'm missing the nandroid bacjup capability, so maybe I reinstall but stay away from the recovery option until I need it?
I reinstalled CW after I rerooted 1.1 and have had no problems with it so far, but I also haven't tried to backup or anything since the first time (which initially got me into this mess).
I do think you're right about having some sort of addendum thrown in. I was running circles around the XDA forums for a few hours trying to find some sort of fix the first time my Nook started acting weird. The 8-reboot trick just wouldn't work, and my battery was more or less drained because CW was interfering. Maybe this is just understood by most, but it certainly would have saved me some time (and some gray hairs) if someone had mentioned it earlier.
So what is the conclusion of this thread? I have a new NC, updated to 1.1 and installed AutoNooker 3.0, immediately installed Clockwork and did a NAND backup... bad thing is that it won't boot off the eMMC anymore, only CW.
I can boot roms off of the SD card (ie Honeycomb) but this isn't want I want. I've downloaded and flashed several roms but its looped at CW. So the rom isn't the problem.
If we can't install Clockwork Recovery, then how can we flash new roms to the eMMC?
[UPDATE]
Found a flashable file which removes Clockwork Recovery.
http://www.etoile-laconnex.com/CWR-removal-rootsafe.zip
After I flashed that I am now booting off the eMMC froyo rom. Nice! Saved me from Restoring it, updating it, and reRooting it.
[UPDATE 2]
Well while it worked initially, it loaded the homescreen and reset. Now it is stuck at the "Touch the Future of Reading" screen with no Recovery... which worse off. Now I have to make a CWM bootable SD, flash the restore, and start over. Nice.
[UPDATE 3]
Finally got it back to stock after hours. I found a "MonsterPack" here:
http://forum.xda-developers.com/showthread.php?t=922870
Even this was more complicated then it needed. I had to download the 128mb RootPack image, and get it going so I can grab the needed root files. Then download the right size Clockwork image for my memory card and get it going. The end result ended in a Clockwork SD card. Then I made a "sdcard" folder from where I added the rootpack files and the stock image 1.0.1 flashable zip file.
Format the system and boot partitions, then flash the stock zip.
I just upgraded stock to 1.1, then will proceed to boot off the microsd and root, install GAPPS, etc.
I wish I knew of a great custom rom to flash. I flashed Nookie Froyo 0.6.8 and it powers down immediately (several complaints about this). Maybe CM7?
Ditto
I'm having this problem as well, but I can't seem to do anything to fix it. I was running 1.1, and auto-nootered using v3.0. Everything was hunky dory until I installed CWR. I flashed, shutdown, restarted, then chose to perform a backup which brought me down into CWR and I was never able to get out. I used the Monster pack zip to remove CWR, and now I boot to the "n" screen and sit forever. I tried the 8 hard resets and it said it installed on two different occasions, but still I sit on the "n" screen during boot. I tried the 1.0.1 restore zip as well, but to no avail. What do I need to do to get back up and running?
CW Recovery only
So I flashed my NC with both the pre-dualboot and the dual-honeycomb rom, but every time I reboot with the SD card inserted, it only boots to CW recovery. When I take it out..it boots to NC stock OS.
Am I suppose to remove clockwork recovery with the CW-removal zip? I tried that.. once it rebooted it went right back to CW. Should I be using two different SD cards? One for CW recovery and one to load the eMMc?
So confused...
What I need to know is what should be on the SD card after everything is flashed.
Mw : you could use a bootable cwr sdcard and flash 'emmc recovery repair', then format data and restore your backup.
Ehamonn: you have to remove cwr from the sdcard. Format should do the trick. But you'll loose the data on it..
Sent from my Desire HD using XDA App
Do I need to keep a boot image on the card after I format?
Well, if you only want to boot from internal memory, no.
I have installed Rom Manager (paid version), and clicked the "Install ClockworkMod Recovery" button.
It asks for the device - selected Samsung S Captivate (which is what my phone is).
It asks for (and gets) root, pops up a message saying that it has downloaded ClockWorkMod Recovery, then seems to do nothing else.
If I then click on Backup Current ROM, it presents a name for the backup (date and time), then re-boots the phone into recovery.
No backup happens, and the recovery is the Samsung one.
So the installation of ClockworkMod Recovery seems to have failed.
Tried several more times - same result. Tried installing recovery a few times too.
Looked at the filestore -- the clockworkmod recovery download is there.
Deleted Rom Manager, re-installed - tried again - same results.
Any suggestions???
PhilipPeake said:
I have installed Rom Manager (paid version), and clicked the "Install ClockworkMod Recovery" button.
It asks for the device - selected Samsung S Captivate (which is what my phone is).
It asks for (and gets) root, pops up a message saying that it has downloaded ClockWorkMod Recovery, then seems to do nothing else.
If I then click on Backup Current ROM, it presents a name for the backup (date and time), then re-boots the phone into recovery.
No backup happens, and the recovery is the Samsung one.
So the installation of ClockworkMod Recovery seems to have failed.
Tried several more times - same result. Tried installing recovery a few times too.
Looked at the filestore -- the clockworkmod recovery download is there.
Deleted Rom Manager, re-installed - tried again - same results.
Any suggestions???
Click to expand...
Click to collapse
First, you need to be rooted. If you are rooted already, when you get to the Samsung recovery, is it the 3e recovery? if so, you need to get around that first be reading here: http://forum.xda-developers.com/showthread.php?t=909213
Once you get around 3e recovery you can flash whatever you want. Report back, let us konw how it goes.
edit: oops, just noticed that you did say you have root when you mentioned you allowed root access for Rom Manager.
Reboot to Recovery and select "reinstall packages". --- u may have to do it twice, but then u should be in CWM Recovery... Unless u have the stock 3e recovery as stated above.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Ok - loaded the modified 3e recovery binary.
Seems to be working, because now when I boot into recovery I see:
-- Movi_check Start..||
checksum confirmation need_checksum[0]
Not need checksum confirmation
...
But still can't get clockworkmod recovery to load.
Tried loading an old version, followed by re-loading the current version.
Backup Current ROM ... and still see the Samsung recovery utils message,
and of course, no backup.
Ok -- lets try reinstall packages twice ...
Ok - that did it.
Thanks!!
As said in the post above your last one, you do have to select Reinstall packages twice to get into CWM. Are you selecting it twice?
edit: just saw your post above. glad you got it working.
Ok - now some random questions (for my education):
First, any idea why it might take TWO re-installs of packages for things to work?
It always makes me a bit nervous when repeating an operation has different effects. Software is supposed to be deterministic!
Next, I assume that installing clockworkmod recovery just replaces the "recovery" binary in /system/bin (?).
If so, why didn't (couldn't?) I just get hold of a single binary and drop it into /system/bin in place of the standard recovery binary?
PhilipPeake said:
Ok - now some random questions (for my education):
First, any idea why it might take TWO re-installs of packages for things to work?
It always makes me a bit nervous when repeating an operation has different effects. Software is supposed to be deterministic!
Next, I assume that installing clockworkmod recovery just replaces the "recovery" binary in /system/bin (?).
If so, why didn't (couldn't?) I just get hold of a single binary and drop it into /system/bin in place of the standard recovery binary?
Click to expand...
Click to collapse
As far as the re-installing packages twice, you should only have to do that once. now when you reboot to recovery, or 3-button boot to recovery it should go right to CWM.
And I have no idea about the single binary thing. I just followed instructions as you did to get it working. Hahaha!
Honesty on a forum -- I like that!
Just did a bit of poking around ... it doesn't replace the restore binary, looks like it uses that to load CWM -- if you issue a "reboot recovery" you end up in the standard recovery. If you run reboot into recovery from Rom Manager, you can see it loads the original recovery first, then jumps into CWM.
I suppose this is actually a good thing, because you always have the old recovery to fall back to.
Thanks a lot ... I would probably never have found the 3e restore replacement without that pointer.
Philip
I was running Rogers 2.3.3 stock on my i896. I then tried to install a couple ROMs (Effin Eh 4, and Illuminance 3). They both had the same result being stuck on the boot screen. I've attached a log, it's basically stuck in a loop trying to lookup something (provider info?) in the DB. The root of the problem seems to be this:
java.io.FileNotFoundException: /dbdata/system/packages.xml (Read-only file system)W/PackageManager
I guess this file is built by the system? So maybe there was an incorrect file there that should have been deleted, or maybe the directory didn't exist? I'm hoping someone recognizes what's going on so I don't have to learn the entire boot process.
If you want to know how I got there, I used Samurai 1.3 to get CWM (with ODIN). I then used CWM to "install from SD" the Effin EH 4.zip. That zip uses Samurai 1.4.2. It did the normal bootloader splashes and the 5 mins of building cache, then stuck. I did a reboot to recovery. Cleared all the caches, retried "install from SD" in CWM, still stuck. Tried once more with the Illuminance ROM instead(same issue), then used an ODIN one-click to get back on Rogers 2.3.3 (which booted fine).
TIA
I think I forgot to attach the log. Maybe seeing the log will tip somebody off as to what went wrong.
Thanks.
This may be a silly question but was your phone rooted?
prostar said:
I was running Rogers 2.3.3 stock on my i896. I then tried to install a couple ROMs (Effin Eh 4, and Illuminance 3). They both had the same result being stuck on the boot screen. I've attached a log, it's basically stuck in a loop trying to lookup something (provider info?) in the DB. The root of the problem seems to be this:
java.io.FileNotFoundException: /dbdata/system/packages.xml (Read-only file system)W/PackageManager
I guess this file is built by the system? So maybe there was an incorrect file there that should have been deleted, or maybe the directory didn't exist? I'm hoping someone recognizes what's going on so I don't have to learn the entire boot process.
If you want to know how I got there, I used Samurai 1.3 to get CWM (with ODIN). I then used CWM to "install from SD" the Effin EH 4.zip. That zip uses Samurai 1.4.2. It did the normal bootloader splashes and the 5 mins of building cache, then stuck. I did a reboot to recovery. Cleared all the caches, retried "install from SD" in CWM, still stuck. Tried once more with the Illuminance ROM instead(same issue), then used an ODIN one-click to get back on Rogers 2.3.3 (which booted fine).
TIA
Click to expand...
Click to collapse
Sent from my SGH-I897 using XDA App
Yes, using the fugu kernel swap method. But I'm pretty sure that doesn't matter because I flashed the Samurai kernel to use it's built in CWM. It would be rooted by default.