Related
Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.
I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.
Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work
vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8
I'm facing an issue that I've been able to narrow down to this :
- I install stock JVT (odin with re-partition)
-> no issues
- I then install Semaphore 1.8.0 kernel using odin
-> no issues
- I install and run ext4 1.3 from cf-root
-> install seems ok, I launch it, no issue, tell it to conver to ext4, the process starts, the phone reboots, the conversion processe takes a minute or two and the phones reboot.
-> at first, all seems ok, the phone operates as i should, BUT it looks like I've lost root :
- semaphore apps cannot be run because of permission issues
- same goes for ext4, cwm,...
I've tried to reflash semaphore in a hope for a fix, but it did not help.
Any guess ?
Thanks in advance, jc
the ext4 tool has several different versions: step 1 is to use a different version. The tool itself can by a bit buggy.
You can also look at other ways to convert your file system using another kernel.
Was you using the ext4 app 1.3?
If you run it now does it say your file systems are rfs or ext4?
Sent using TCP/IP
Yes, I'm using ext app 1.3.
The first time I run it, jus after semaphore install, it says my files are rfs.
I launch the conversion process, it reboots as normal, does the conversion, phone seems ok, but you cannot relaunch it to check because it wont recognize the kernel and fail (I believe it is permission issues, as my phone seem to have lost it's root in the process).
Good idea about trying another kernel jus for the ext4 migration, now I need o find one that does not leave anything behind when I move back to Semephore
jc
Yeah, You can use chainfires kernel to get root back and convert file systems to ext4.
Then use SGS flasher to flash semaphore.
yes, but I'm wondering if the issue is not somewhere else. I believe I might not have enough space on /system to do the conversion.
What is the required free space ? Arround 6 Mb ?
jc
Yes, that was the issue, not enough space on /system, which made the convert fail, and all my problems where comming from that.
Remove some apps with nitrality, got 7 mb free, and it worked !
jc
There seems to be an issue with the Slim Bean i897 2.7.0 zip. I downloaded and verified the zip file, but when I went to install it I get the following message: "E:error in /sdcard/Slim-i897-2.7.0-OFFICIAL.zip (Status 0) Installation aborted". I was originally on the latest available build of SGSICS.
Next, I tried downloading the 2.6.0 zip and installing that. This time it told me my partition format would be changed and to run it again. So I did that, it rebooted and then I ran it again and successfully installed 2.6.0.
After booting up 2.6.0, I shut it down and went back into recovery. Now I followed the steps for upgrading from one Slim Bean version to the next, using the same 2.7.0 zip file I had copied to my phone earlier and this time it installed without any issue.
I think perhaps whatever part of the install script that doe the repartitioning check in 2.6.0 is missing from 2.7.0.
Same issue here
I have the same issue. I have been using SlimICS from some months now, opting to wait to update to SlimBean to allow the pros to work out the kinks. I have now decided to upgrade but having an issue. I wiped data/factory reset, wiped cache partition, wiped dalvik cache, formated and mounted system, mounted data. How ever when i try to flash Slim-i897-2.7.0-OFFICIAL i get error 0 and message to "format and mount system, mount data"
Same thing happened for me too when trying from CM9. When I put CM10 and then tried 2.7 it went without a glitch.
Yes this Status 0 message is quite the bother, I did a total back to stock, rooted, went to CM9, tried to install, get status 0, tried on CM10, still status 0, tried to install 2.6 and that tries to install, at reboot it just shows an android and under says powered by Semaphore.
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.
I am rooted with customer TWRP recovery. I have a custom ROM installed based on the latest touchwiz, few actual changes. ROM is [ROM][Kernel][G900F|I|M|T|W8][XXU1ANH6][26Sep] Omega v9.0●Omega Files.
I have had problems with unexpected SystemUI crash on v.8.1 of Omega, so I updated to Omega's v.9 when it was released a few days ago, no issues at first. But two nights, as I was grabbing my phone to plug it in, it was in this loop again trying to boot but giving the "unfortunately your systemui has closed". So, I managed to boot to recovery from the power menu (not easy as the error flashes every second), installed the ROM again (no wipe). Installed the latest Framework (which seems to always need an install and re-boot when I install the ROM), the ROM worked again for a few minutes, and then the errors started.
So I installed the ROM with a clean install, full wipe. Can't boot at all after the initial boot when I activated the framework. At first I thought it was one of the modules. I had the following modules installed:
Application Settings
Disable clear defaults dialog
Greenify
Wanam
Xposed G Touchwiz
So I did another full wipe install, ONLY installed the framework, activated the Xposed framework, and it won't boot, same error. I try clearing the cache, dalvik cache, nothing works. So I was forced to do another full wipe install and I'm now running without Xposed. A few other people are having the problem on the OMEGA S5 forum, but it seems very rare and most people running Xposed without a problem. I have the Canadian G900W8 version of the phone, don't know if that's the difference.
harry_fine said:
I am rooted with customer TWRP recovery. I have a custom ROM installed based on the latest touchwiz, few actual changes. ROM is [ROM][Kernel][G900F|I|M|T|W8][XXU1ANH6][26Sep] Omega v9.0●Omega Files.
I have had problems with unexpected SystemUI crash on v.8.1 of Omega, so I updated to Omega's v.9 when it was released a few days ago, no issues at first. But two nights, as I was grabbing my phone to plug it in, it was in this loop again trying to boot but giving the "unfortunately your systemui has closed". So, I managed to boot to recovery from the power menu (not easy as the error flashes every second), installed the ROM again (no wipe). Installed the latest Framework (which seems to always need an install and re-boot when I install the ROM), the ROM worked again for a few minutes, and then the errors started.
So I installed the ROM with a clean install, full wipe. Can't boot at all after the initial boot when I activated the framework. At first I thought it was one of the modules. I had the following modules installed:
Application Settings
Disable clear defaults dialog
Greenify
Wanam
Xposed G Touchwiz
So I did another full wipe install, ONLY installed the framework, activated the Xposed framework, and it won't boot, same error. I try clearing the cache, dalvik cache, nothing works. So I was forced to do another full wipe install and I'm now running without Xposed. A few other people are having the problem on the OMEGA S5 forum, but it seems very rare and most people running Xposed without a problem. I have the Canadian G900W8 version of the phone, don't know if that's the difference.
Click to expand...
Click to collapse
Took some advice in the S5 developers forum. Backed up my SD card. Formatted all partitions on phone. Re-formatted SD card with FAT32 in Windows. Made sure everything was cleared out. Copied the ROM (in a PC reader) to the newly formatted SD card. Re-inserted card. Installed 9.1, including Xposed Framework and all the modules I use. Restored my backed up files (pictures, music, TB backup files) to my SD card. After boot I did NOT get the systemui closed error that have been plaguing me for 3 days..
So, it may be that there was something in my configuration, either prior to using Omega or on an earlier version of Omega that caused these problems when I installed Xposed. Hoping that's the end of it. Will let you know.
Lesson for everyone, if there is an issue that is not generally being experienced by everyone else, don't just to a full wipe install, delete everything from everywhere with formats, including your SD card.