Database Users

Zpad Clean v1.x (1106)

Zpad clean v1.x will be based off the Zpad 1106 firmware.
Thanks to my friends in the QQ Zpad VIP user group for providing this. A very stable build and look forward to working on more.
ZPad Clean v1.1 Download: http://www.multiupload.com/FIMODMW4T6
Gapps Update.zip v2: http://www.multiupload.com/VFDQ8Q4NC0
Much better gapps pack with working youtube, new TnT Keyboard, and no screens at startup.
Fixes over 1029:
-Flash preloaded
-Date/time reset fixed (no clocksync needed)
-Timezone are added to build.prop (will need to edit)
-build.prop UI tweak for responsiveness
-No battery waste on cell signal search
v1.1
-Build.Prop Tweaks
-Angry Birds video library (mount sdcard to computer, then install)
-Trimmed down further
-ADW is default launcher
-Audio lib update
-Camera lib update
-Wifi driver update
-Update TnT Keyboard (smaller/faster)
-Any other TnT updates
-This is very lean, and the UI is responsive
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install:
This is an update.zip with system.img and boot.img which are flashed. It is easiest to run this update from Clockwork Recovery.
Issues:
Timezone broken:
Edit this line to your timezone:
persist.sys.timezone=WHATEVER
change to
persist.sys.timezone=America/Chicago or equivalent for you TZ

Galaxy S Theme ported from here: http://forum.cyanogenmod.com/topic/2048-theme-morph-gs-theme-desire-hd-themes-92810/
Download: http://www.multiupload.com/IKWS80QSRX

I cannot get past the setup screen after installing the gapps.zip, any information would be helpful.

rms1776 said:
I cannot get past the setup screen after installing the gapps.zip, any information would be helpful.
Click to expand...
Click to collapse
got to skip the install enable wireless, then relaunch the setup.

It wont let me do anything at the screen that had the little android guy, first i installed zpad 1. reboot went back into clockwork and flashed gapps, rebooted then the screen with android guy poped up, that is where i am stuck.

rms1776 said:
It wont let me do anything at the screen that had the little android guy, first i installed zpad 1. reboot went back into clockwork and flashed gapps, rebooted then the screen with android guy poped up, that is where i am stuck.
Click to expand...
Click to collapse
See above post. I have also noticed that after completing it the first time it sometimes loops back to the android guy and starts the setup wizard all over again. Just hit the Home button and you're good.

I fixed it by removing the setup.apk and the one time initalizing.apk from the TNT_Gapps_LiveWP and re-zipping the file and re-installing.

Did anyone have success flashing this from CW Recovery? I have never been able to flash any of the Zpad Clean ROMs that way. I put the zip on my internal storage and in CW choose to install zip from SDCARD. They ALWAYS fail with:
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/zpad_clean_v1(1106).zip
I have had luck in the past using the stock recovery image and placing the update.zip and recovery folder on the root of SDCARD, but this release does not seem to be structured that way.

photonmedia said:
Did anyone have success flashing this from CW Recovery? I have never been able to flash any of the Zpad Clean ROMs that way. I put the zip on my internal storage and in CW choose to install zip from SDCARD. They ALWAYS fail with:
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/zpad_clean_v1(1106).zip
I have had luck in the past using the stock recovery image and placing the update.zip and recovery folder on the root of SDCARD, but this release does not seem to be structured that way.
Click to expand...
Click to collapse
Has anyone else experienced this? What I did was just remove the two lines from the update-script to flash the bootloader and recovery from the update.zip I received from Zpad guys.
My reading has only come down to people believing that that have some bad blocks in the boot recovery.
I also included the nandroid.md5 file in the update.zip. So you could try placing boot.img, system.img, and nandroid.md5 in the backups folder for clockwork. Then try flashing it as a recovery.

rothnic said:
Has anyone else experienced this? What I did was just remove the two lines from the update-script to flash the bootloader and recovery from the update.zip I received from Zpad guys.
My reading has only come down to people believing that that have some bad blocks in the boot recovery.
I also included the nandroid.md5 file in the update.zip. So you could try placing boot.img, system.img, and nandroid.md5 in the backups folder for clockwork. Then try flashing it as a recovery.
Click to expand...
Click to collapse
Rothnic,
I'll try the Nandroid Restore method you mentioned and let you know how it goes. Do you know if maybe these were designed to be flashed from an actual SDCARD rather than the internal memory that mounts as SDCARD? The error seems to indicate there is either a problem extracting the boot.img file to /tmp/boot.img or with the write_raw_image command finding said boot.img file.
BTW,
I'll be glad to test anything you need in the future.

photonmedia said:
Rothnic,
I'll try the Nandroid Restore method you mentioned and let you know how it goes. Do you know if maybe these were designed to be flashed from an actual SDCARD rather than the internal memory that mounts as SDCARD? The error seems to indicate there is either a problem extracting the boot.img file to /tmp/boot.img or with the write_raw_image command finding said boot.img file.
BTW,
I'll be glad to test anything you need in the future.
Click to expand...
Click to collapse
I think that statement just means a problem was occured in writing the boot.img. I read some more and it seems like they say a small percent of people have had this problem, and it usually deals with kernels that are bigger than stock. This would explain why it only happens with Zpad firmware.

Update:
I copied the boot.img, system.img, and nandroid.md5 files to /sdcard/clockworkmod/backup/zpad-clean-1106/
I then modified the nandroid.md5 file so it only contained md5's for boot.img and system.img
When I try to restore from that backup, it starts to perform the restore but when trying to "restore boot" it throws "Error while flashing boot image!"
I'm at work and have to leave my desk for a bit but I'll check back shortly and test any other suggestions...
I know at least one other person on the zpad clean 1029 thread was getting the same errors trying to flash that ROM with CW recovery, so hopefully we can figure this out.

rms1776 said:
I cannot get past the setup screen after installing the gapps.zip, any information would be helpful.
Click to expand...
Click to collapse
If you get stuck at the Android screen, you can get past it by pressing all four corners of the screen starting from top left and going clockwise (thanks McPhist0)

rothnic said:
I think that statement just means a problem was occured in writing the boot.img. I read some more and it seems like they say a small percent of people have had this problem, and it usually deals with kernels that are bigger than stock. This would explain why it only happens with Zpad firmware.
Click to expand...
Click to collapse
The strange thing is the kernel in these ROMs is 16MB. That is the same size as the kernel in the TnT Full Vanilla Restore which I have been able to flash (using the stock recovery)
I really wanna stick with CW Recovery and I REALLY wanna check out this Zpad ROM, but I'm hitting this roadblock.
I also tried to manually flash boot.img using the "flash_image boot boot.img" command and I get an error that there is no space left on the device.
I also tried and advanced Nandroid restore to restore on the System from this ROM and then a Boot from a separate backup of another ROM. I was successfully able to restore that Boot with this System but all I get are Veiwsonic/Gtablet screens looping.
UPDATE:
Code:
/sdcard # flash_image boot boot.img
mtd: not writing bad block at 0x003e0000
error writing boot: No space left on device
/sdcard #
Yep,
I'd say that's a bad block in the boot partition....
What's so strange is that I can run that same command, pointing to a different boot.img (also 16MB in size) and though I still get the bad block skipping, it flashes successfully.

rothnic said:
If you get stuck at the Android screen, you can get past it by pressing all four corners of the screen starting from top left and going clockwise (thanks McPhist0)
Click to expand...
Click to collapse
Thanks a lot for the 4 corner solution! I had tried the method of removing setup and onetme apk's but had to reflash cause my home button stopped working for some reason.
Side note, I'm no developer so I probably have no idea what I'm talking about, but I noticed each time I flashed, the SD card was not mounted. Could this be causing the initial setup to not work??? Again, I don't know much about programming, just an observance.
Thanks again to everyone who's been providing help. (now if I could just get subsonic working....)

I have been using the internal storage (which gets mounted as /sdcard). Unfortunately I have killed my battery will all this testing and flashing. When I get home I think I am going to throw a microsd in there and see if I have any better luck with that.

rothnic said:
Zpad clean v1.x will be based off the Zpad 1106 firmware.
Thanks to my friends in the QQ Zpad VIP user group for providing this. A very stable build and look forward to working on more.
v1.0 Download: http://www.multiupload.com/4R4ELKGN1U
Fixes over 1029:
-Flash preloaded
-Date/time reset fixed (no clocksync needed)
-Timezone are added to build.prop (will need to edit)
-build.prop UI tweak for responsiveness
-No battery waste on cell signal search
Install:
This is an update.zip with system.img and boot.img which are flashed. It is easiest to run this update from Clockwork Recovery.
Extras:
Gapps Update.zip: http://www.megaupload.com/?d=EJQP1OW5
If you get stuck at the Android screen, you can get past it by pressing all four corners of the screen starting from top left and going clockwise (thanks McPhist0)
Click to expand...
Click to collapse
How did someone figure the four corners out?

rushless said:
How did someone figure the four corners out?
Click to expand...
Click to collapse
McPhist0 searched, found something for one of the Droids and posted it in the IRC chatroom (irc.freenode.net #tegratab)

photonmedia said:
The strange thing is the kernel in these ROMs is 16MB. That is the same size as the kernel in the TnT Full Vanilla Restore which I have been able to flash (using the stock recovery)
I really wanna stick with CW Recovery and I REALLY wanna check out this Zpad ROM, but I'm hitting this roadblock.
I also tried to manually flash boot.img using the "flash_image boot boot.img" command and I get an error that there is no space left on the device.
I also tried and advanced Nandroid restore to restore on the System from this ROM and then a Boot from a separate backup of another ROM. I was successfully able to restore that Boot with this System but all I get are Veiwsonic/Gtablet screens looping.
UPDATE:
Code:
/sdcard # flash_image boot boot.img
mtd: not writing bad block at 0x003e0000
error writing boot: No space left on device
/sdcard #
Yep,
I'd say that's a bad block in the boot partition....
What's so strange is that I can run that same command, pointing to a different boot.img (also 16MB in size) and though I still get the bad block skipping, it flashes successfully.
Click to expand...
Click to collapse
The kernel is contained inside the boot.img with the ramdisk. Is the boot.img 16MB or is it literally the kernel?
I suggest exchanging while you can. It really does seem like a hardware issue that happens from time to time.

rushless said:
How did someone figure the four corners out?
Click to expand...
Click to collapse
that has been a feature in android since the begining...

P6800 - Enter your password - Problem after trying to instal custom ROM

Hi there
I am sorry if my post is there before but I tried many of the solutions there without any results.
I tried to install a custom ROM as I wanted to try something new. I am familiar with all the steps as I am using S2 from a year and flashed many many many Roms before. I flashed also a rom for my P6800 when it was using HoneyComp. Everything were great. After upgrading to the official ICS, I tried to install custom ROM and it failed. Tried many times to restore the official ROM using Odin without any results. I tried downgrading it to HoneyComp and this is what I ended with
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after booting
I didn't know how to use adb shell method so I didn't try to not make it worse.
Hope I can get help

same problem
I've the same problem as shown above
please help my tab is dead

HELP pleaseeeeeeee :crying:

I had the same problem and I found the solution that restored my tab back to life. After two weeks playing dead it works now with ICS. Only method that had results for me was flashing STOCK recovery from P6800XXLA1 and after that Wipe data/Factory reset. I found out that our CWM recovery does not wipe data in our situation so only official recovery does the trick. This fixed my tab (after trying everything) so you should also try it.
P.S If this does not work then try flashing only PIT (for me it didn't do much or maybe it did something but I'm not sure) file and then flash stock recovery and wipe.
Report back !

HapaBiH said:
I had the same problem and I found the solution that restored my tab back to life. After two weeks playing dead it works now with ICS. Only method that had results for me was flashing STOCK recovery from P6800XXLA1 and after that Wipe data/Factory reset. I found out that our CWM recovery does not wipe data in our situation so only official recovery does the trick. This fixed my tab (after trying everything) so you should also try it.
Click to expand...
Click to collapse
when i try to wipe data/factory reset it hang then restart showing samsung logo forever

massdown said:
when i try to wipe data/factory reset it hang then restart showing samsung logo forever
Click to expand...
Click to collapse
It worked for me :/ If nothing helps then try re-partitioning with proper pit for your model and then try again. This "error" happens when system can't access internal memory so it thinks that it's encrypted(that is what i found out). Worst case is that internal memory is lost and the best case is one that I had, bad partition or incomplete wipe.

HapaBiH said:
It worked for me :/ If nothing helps then try re-partitioning with proper pit for your model and then try again. This "error" happens when system can't access internal memory so it thinks that it's encrypted(that is what i found out). Worst case is that internal memory is lost and the best case is one that I had, bad partition or incomplete wipe.
Click to expand...
Click to collapse
please if u know where can i get the pit file for GT6800 ??? i tried a couple of pit files but no good

massdown said:
please if u know where can i get the pit file for GT6800 ??? i tried a couple of pit files but no good
Click to expand...
Click to collapse
Having the same problem. Tryied to flash any original HC ROM, ICS ROM, ICS + QuickSilver - i may have flashed my tab 10 times and the problem is still there.
Done several wipes/factory resets, both from STOCK and CWM recovery (data wipe,davlick cache, etc.
With stock HC - i get sometimes the same password request, and sometimes it remains stuck at the Samsung Galaxy TAB 7.7 logo
With stock ICS - i get samsung boot animation - and then black screen.
I'm having this problem for the past week and since then none was able / willing to give a solution....
Can anyone help?
Thx,

massdown said:
please if u know where can i get the pit file for GT6800 ??? i tried a couple of pit files but no good
Click to expand...
Click to collapse
I used this one, flash at your own risk! This is for 16GB version.

HapaBiH said:
I used this one, flash at your own risk! This is for 16GB version.[/QUOTE
Now i have a new problem. Tryed with the PIT file, but when i go back to HC stock ROM and i try to enter recovey mode i get:
#Manual Mode
--Updating application...
And then it restarts by it self.
So i can''t get in Recovery mode...
Any ideeas?
Click to expand...
Click to collapse

Can you get in Download mode?* Try flashing new rom from ODIN and CWM first if you didn't already. Or flash only cwm and install system using external sd. After that try wiping with stock recovery.

same problem !
HELP !

HapaBiH said:
Can you get in Download mode?* Try flashing new rom from ODIN and CWM first if you didn't already. Or flash only cwm and install system using external sd. After that try wiping with stock recovery.
Click to expand...
Click to collapse
I will try this tonight to see if it works. Thx
Well, i tryed about anythnig i could think of.
I've instaled CWM - and tryed to install ICS or HC from SD card but i get the same eror:
e: can''t open /emmc/p6800xxlq....... .zip
(bad)
instalation aborted.
Also when i try to do a full wipe from CWM i get :
error mounting /data
skipping format...
then it goes and formats /cache and /sd-ext with no error but then it start to format /sdcard/.android_secure... when it gives the same mounting eror.
In the end it says :
Data wipe complete.
Also when i try to wile Davlick Cache i don't think it does so, because CWM usually askes me if i really want to do it but when i try to wipe it on my tab the text dissapeares for 1 second and gets back to the menu, without any confirmation/infirmation of the action.
Any ideeas regarding what to do?
I also tryed flashing the .pit file, and also flashe 2 versions of HC for Romania and the Austrian version of ICS several times.
I can get intro download mode and recovery.

I flashed HC stock recovery on ICS rom and did full WIPE, my internal memory come back to life. after that I flashed CWM and all was good. This helped me but maybe it is different for everyone :/ Only difference from your case is that I was able to install rom from ext SD.

HapaBiH said:
I flashed HC stock recovery on ICS rom and did full WIPE, my internal memory come back to life. after that I flashed CWM and all was good. This helped me but maybe it is different for everyone :/ Only difference from your case is that I was able to install rom from ext SD.
Click to expand...
Click to collapse
There seems to be a solution to the problem : http://forum.xda-developers.com/showthread.php?t=1763348&page=2
I will try it later today....

The best I can suggest is for you to follow these few steps....I had same thing happen to me after build.prop change fail.
Get the tablet into download mode
Open Odin on the computer
Have an Official ICS ROM
Connect Tablet to PC Odin
Replace only the PDA file
Hit the Start button
All should be good after that, worked for me and I had the same logo reboot logo story

slide200sx said:
The best I can suggest is for you to follow these few steps....I had same thing happen to me after build.prop change fail.
Get the tablet into download mode
Open Odin on the computer
Have an Official ICS ROM
Connect Tablet to PC Odin
Replace only the PDA file
Hit the Start button
All should be good after that, worked for me and I had the same logo reboot logo story
Click to expand...
Click to collapse
I for one, have done this with Stock ICS,Stock HC wit/without wipe for 20 times....

ionutcostea said:
HapaBiH said:
I used this one, flash at your own risk! This is for 16GB version.[/QUOTE
Now i have a new problem. Tryed with the PIT file, but when i go back to HC stock ROM and i try to enter recovey mode i get:
#Manual Mode
--Updating application...
And then it restarts by it self.
So i can''t get in Recovery mode...
Any ideeas?
Click to expand...
Click to collapse
The problem is PIT issues are not compatible with your stock rom. I have experienced this problem, many pits and stock rom I have tried but can not be resolved.
But finally I solve it.
You Need
Odin3 1.87, Stock Rom and the right Pit.
1. Open odin and tab to downloading mode.
2. Select PIT that you can get here PIT
3. Open Austria Stock Rom = P6800XXLQ1_P6800OXALQ1_ATO
4. REMEMBER to tick Re-Partition, Auto Reboot and F Reset Time
5. Start.... and you Done.
Hope this will Help.
Click to expand...
Click to collapse

Hi, I am a noob and also like to try something new.. I flashed some custom roms and had error on my P6800 several times. And the solution are with PC Odin (Odin 3 v1.85). The worst error I ever got is an error while I still in cm10 and I accidentally wipe/factory reset from stock recovery mode and I do not have nandroid backup.
I remember I did the following:
I go to stock recovery mode and run CMW.zip from microSD (this CWM.zip was used for rooting my ICS)
You can get it here:
http://forum.xda-developers.com/showthread.php?t=1756304
After the CWM open, I choose factory reset/wipe, and then wipe partition cache, and wipe dalvik cache.
Then, I went to download mode and then flash stock HC (we can get from sammobile, just choose one) with Odin3 v1.85 (PC Odin). And it worked, my tab back with fresh HC. however sometime the reboot process will takes longer than usual, it can takes 5 minutes since the Odin did its process and start to reboot.
If the above step not work, you can flash again with stock ICS, still with PC Odin, it can work too (at least with me).
Hope this way will work with you too..

[Q] Can't Install Cyanogen ROM on Nook Color

Hi,
First post so if it's in the wrong place, please let me know. I have installed Cyanogen Mods on my Nook Color dozens of times without any problems. Suddenly I began getting errors no matter which ROM I try. Here is an example of my process:
wipe data/factory reset
wipe cache partition
Wipe Dalvik Cache
install zip from sdcard
choose zip from sdcard
Choose - cm-10.2-20130824-NIGHTLY-acclaim.zip
-- Installing: /sdcard/cm-10.2-20130824-NIGHTLY-acclaim.zip
Finding update package ...
Verifying update package ...
Installing update ...
E:Error in /sdcard/cm-10.2-20130824-NIGHTLY-acclaim.zip
(Status 0)
Installation aborted.
Does anyone know what is going on and how to fix it?
There is 12 GB of free space on my SD card.

cafalstrom said:
Hi,
First post so if it's in the wrong place, please let me know. I have installed Cyanogen Mods on my Nook Color dozens of times without any problems. Suddenly I began getting errors no matter which ROM I try. Here is an example of my process:
wipe data/factory reset
wipe cache partition
Wipe Dalvik Cache
install zip from sdcard
choose zip from sdcard
Choose - cm-10.2-20130824-NIGHTLY-acclaim.zip
-- Installing: /sdcard/cm-10.2-20130824-NIGHTLY-acclaim.zip
Finding update package ...
Verifying update package ...
Installing update ...
E:Error in /sdcard/cm-10.2-20130824-NIGHTLY-acclaim.zip
(Status 0)
Installation aborted.
Does anyone know what is going on and how to fix it?
There is 12 GB of free space on my SD card.
Click to expand...
Click to collapse
cm-10.2-20130824-NIGHTLY-acclaim.zip
You are flashing a ROM meant for the Nook Tablet onto a Nook COLOR. Nook Color's codename is encore. Sorry, I just have to post the following meme (jokingly of course, no hard feelings?):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

separate icertsou
Hi!
I enjoyed the meme. I must have had a brain fart when I wrote Nook Color.
In fact, I do have a Nook Tablet. I have been using the process outlined to successfully install CM nightly builds for months now. I started getting the "E:Error in /sdcard/cm-10.2-20130824-NIGHTLY-acclaim.zip (Status 0)" on the 20130824 release and I have not been able to install a new rom since.
I have no idea even to know where to start troubleshooting this problem.

cafalstrom said:
Hi!
I enjoyed the meme. I must have had a brain fart when I wrote Nook Color.
In fact, I do have a Nook Tablet. I have been using the process outlined to successfully install CM nightly builds for months now. I started getting the "E:Error in /sdcard/cm-10.2-20130824-NIGHTLY-acclaim.zip (Status 0)" on the 20130824 release and I have not been able to install a new rom since.
I have no idea even to know where to start troubleshooting this problem.
Click to expand...
Click to collapse
If you have a tablet, maybe post in the tablet section? This is the Nook Color forum.
Have you tried wiping data/factory reset + wipe cache + wipe system + wipe dalvik cache + wipe battery stats, and then installing the ROM?

Can't install CM Nightly ROMs
Hi!
Thank you for the reply.
I will open a new thread in the Tablet Forum.
The process you suggest is the way I have been installing new builds. It has worked dozens of times. Now, whichever ROM I try I get the error unpacking the zip file.
Moving to the Tablet Forum...

I am getting the same issue. went to reboot my nook color, and it wouldn't come up. so I got a CWM 3.0.2.8 image, did a winimage restore to sd card. copied over gummy and cm10.2 for the encore, boot to cwm, go to install either of those two and get the same error Status 0 Instalation aborted, I did a factory wipe, fixed permissions, re-downloaded the gummy rom. Could it be the version of CWM? Any thoughts?

Yes that CWM version is too old. Go to my NC Tips thread linked in my signature and look for the bootable CWM SD version 5.5.0.4. Burn that image to SD and try.
Sent from my BN NookHD+ using xda premium

leapinlar said:
Yes that CWM version is too old. Go to my NC Tips thread linked in my signature and look for the bootable CWM SD version 5.5.0.4. Burn that image to SD and try.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
Trying that now. Thanks for the fast response!
Todd

Problem with my nook color
I'm having trouble with the status 0 error on my nook color. it's cm-11-20140613-encore.zip on cwm 6.0.4.7. it says the same as the one from the guy at the top of the forum. but i'm trying to flash a nook color rom with an up to date recovery and it still won't work. i've tried different sd cards and i tried different nook colors. it just isn't working.
any ideas thanks

MrGHLover said:
I'm having trouble with the status 0 error on my nook color. it's cm-11-20140613-encore.zip on cwm 6.0.4.7. it says the same as the one from the guy at the top of the forum. but i'm trying to flash a nook color rom with an up to date recovery and it still won't work. i've tried different sd cards and i tried different nook colors. it just isn't working.
any ideas thanks
Click to expand...
Click to collapse
The latest CM11 nightlies for the NC require CWM v6048. Get it at the CM11 thread in the development forum.
Sent from my BN NookHD+ using XDA Premium HD app

[Q] i9505 won't start after changes to framework-res.apk [SOLVED]

Guys, I tried making some changes to framework-res.apk on my i9505, to change the background color...
but when I pressed to overwrite the original framework-res.apk to my modified one, the phone freezed and restarted, but now it wont start...
it's stuck on a screen where's written "SAMSUNG" and there's a glowing blue/purple behind it
is there anyway I can reach the root without turning the phone on again, so I can put the original framework-res.apk again?

Specht77 said:
Guys, I tried making some changes to framework-res.apk on my i9505, to change the background color...
but when I pressed to overwrite the original framework-res.apk to my modified one, the phone freezed and restarted, but now it wont start...
it's stuck on a screen where's written "SAMSUNG" and there's a glowing blue/purple behind it
is there anyway I can reach the root without turning the phone on again, so I can put the original framework-res.apk again?
Click to expand...
Click to collapse
If you have an SD card on your phone just remove it and put it on your Laptop/PC and make a flashable zip with a stock framework and and copy it to your sd card and flash the zip file via recovery. and that should fix your problem. If not then you need to reflash the rom in order to make it work

Repulsa said:
If you have an SD card on your phone just remove it and put it on your Laptop/PC and make a flashable zip with a stock framework and and copy it to your sd card and flash the zip file via recovery. and that should fix your problem. If not then you need to reflash the rom in order to make it work
Click to expand...
Click to collapse
That sounded a good and simple idea, but I think i'm doing something wrong, I tried doing like you said, making a flashable zip with the stock framework...
So I put my S4 on recovery mode, when to "update from external storage" (or something like that), and tried to flash the zip, some text showed up on the screen, I didn't had the time to write it all down, so I wrote only the red part:
E:footer is wrong
E:footer is wrong
E:signature verification failed
could it be that the apktool made some changes to the original apk while I was making a modified one?
edit: I tried flashing a new zip now, with the modified framework... and it got the same 3 errors messages, and still wont boot :/
I have a backup on the internal storage, of a version of the framework that i'm sure is not modified, is there anyway I can access it?

Specht77 said:
That sounded a good and simple idea, but I think i'm doing something wrong, I tried doing like you said, making a flashable zip with the stock framework...
So I put my S4 on recovery mode, when to "update from external storage" (or something like that), and tried to flash the zip, some text showed up on the screen, I didn't had the time to write it all down, so I wrote only the red part:
E:footer is wrong
E:footer is wrong
E:signature verification failed
could it be that the apktool made some changes to the original apk while I was making a modified one?
edit: I tried flashing a new zip now, with the modified framework... and it got the same 3 errors messages, and still wont boot :/
I have a backup on the internal storage, of a version of the framework that i'm sure is not modified, is there anyway I can access it?
Click to expand...
Click to collapse
Do you even have a custom recovery ? and What kind of custom recovery do you have?ie Philz/TWRP and Give me the original file and ill make a flashable zip for you

Repulsa said:
Do you even have a custom recovery ? and What kind of custom recovery do you have?ie Philz/TWRP and Give me the original file and ill make a flashable zip for you
Click to expand...
Click to collapse
I'm using the original recovery...
here's the original file: https://www.dropbox.com/s/ntij1ptio0tucz7/framework-res.apk
edit: tried doing it by "update from ADB", got the same 3 errors, but this time it didn't even went to the finish and restarted, it aborted and went back to the recovery screen

Specht77 said:
I'm using the original recovery...
here's the original file: https://www.dropbox.com/s/ntij1ptio0tucz7/framework-res.apk
Click to expand...
Click to collapse
Bro there's No way you can flash any zip file since your using a stock recovery... You need atleast a custom recovery such as Philz/TWRP. and flashing a recovery more likely will void your warranty. But if you dont care about warranty then flash a custom one but if you do care about that warranty then the only fix is to Flash a stock Rom , Its all up to you. Let me know.

Repulsa said:
Bro there's No way you can flash any zip file since your using a stock recovery... You need atleast a custom recovery such as Philz/TWRP. and flashing a custom recovery more likely will void your warranty. But if you dont care about warranty then flash a custom recovery but if you care about your warranty then the only fix is to Flash a stock Rom , Its all up to you. Let me know.
Click to expand...
Click to collapse
Damn... I don't want to void warranty... if I flash a stock rom, I'll loose everything on the internal storage?

Specht77 said:
Damn... I don't want to void warranty... if I flash a stock rom, I'll loose everything on the internal storage?
Click to expand...
Click to collapse
That is correct Im sorry mate , You can Either boot into recovery and Do Factory reset /wipe cache , Or Flash a stock rom. Or either check On How to restore a backup in Google.com You might save the backup on SD card.But im Not sure how does it work Since im using Google account to backup and restores my Stuff..
Boot into recovery mode (power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!

Repulsa said:
That is correct Im sorry mate , You can Either boot into recovery and Do Factory reset /wipe cache , Or Flash a stock rom. Or either check On How to restore a backup in Google.com You might save the backup on SD card.But im Not sure how does it work Since im using Google account to backup and restores my Stuff..
Boot into recovery mode (power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Click to expand...
Click to collapse
I noticed that even stuck on the samsung message, it at least is recognized @ the USB, so I tried doing "adb push framework-res.apk /system/framework", and just when I was getting happy, it said:
failed to copy 'framework-res.apk' to 'system/framework/framework-res.apk': Read-only file system
is there any command to "untick" the read-only via adb?
after searching on the internet, I found some people saying that you shoud type:
"adb shell
su"
and remount
but after I type su, any new command I type, wont work, it only repeat what I type...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sorry for the double post, but this is sad:
I installed CWM, and installed the zip with the original framework, and also tried with the modified framework...
but... it still get stuck at the same samsung logo

Sorry for the triple post, but since nobody is answering me, and the topic was almost at the second page, I had no other option...
I made a video of what's happening...
at the beggining, it show how the files are stored inside the flashable zip
then I show the zip being flashed with the CWM
then I show the device restarting (everytime I try to restart via CWM, flashing zip or not, it ask if it should fix root, what does it mean?)
and, the device getting stuck at the same SAMSUNG screen
https://www.youtube.com/watch?v=c-uJC9NZV8s
ok, finally I made it, I went to the "mount unmount" and mounted the system before flashing the zip, restarted, and it's working perfectly now

Specht77 said:
Sorry for the triple post, but since nobody is answering me, and the topic was almost at the second page, I had no other option...
I made a video of what's happening...
at the beggining, it show how the files are stored inside the flashable zip
then I show the zip being flashed with the CWM
then I show the device restarting (everytime I try to restart via CWM, flashing zip or not, it ask if it should fix root, what does it mean?)
and, the device getting stuck at the same SAMSUNG screen
https://www.youtube.com/watch?v=c-uJC9NZV8s
ok, finally I made it, I went to the "mount unmount" and mounted the system before flashing the zip, restarted, and it's working perfectly now
Click to expand...
Click to collapse
then I show the device restarting (everytime I try to restart via CWM, flashing zip or not, it ask if it should fix root, what does it mean?) When you press and hold Power+Volume up and You will see that Msg Recovery booting on top of your screen (Blue Letter)then Just let go both of your Finger's mate , and that should boot you into recovery and No need to Hold Menu anymore Just Power+VolUp and if it asked you to fix root /Recovery always Say NO to it But congrats tho

[Best Ever][Noob-friendly] ROM Flashing Guide

Here I start my new thread:
Best Ever Flashing Guide!​
I've started this thread to give you my own experienced flashing guide. This thread/guide will provide you easy and step-by-step tutorial to flash a ROM. If I'm wrong, please don't hesitate to correct me.
You'd say what's new in this thread? I say, "None other guide provide a deep-through guide and these type of new processes that can help you in better ROM flashing."
Before starting I'd like to say:
Anything you're doing is your own responsibility and I'm not responsible for any type of damage to you device.​​(As seen on many thready, I found this interesting) If you point your finger towards me in case of any damage, I'll LOL at you!​
Now let's start with part 1:
Backing-up: When you're switching to a new ROM it's better to back-up your important apps that you need in your new ROM. Because if you don't do this, you've to re-download your apps which is time, data & battery consuming. Here you need a File Explorer such as MiXplorer or ES File Explorer or Root Explorer (Get 'em by clicking on names). Now follow these steps:
Open your File manager and goto Root directory.
Head to "data" folder and then open "app" folder. Here you can see all your installed apps. These are 'User Apps'.
Now select the apps that you want to backup.
Now press "Copy" button to copy you apps.
Head to your SD Card. (You can find "sdcard" folder back in root directory.)
Just paste them wherever you want.
That's it! You've backed-up you apps!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now let's move to part 2:
Pre-flash initial wipe: Yeah! Pre-flash wipe! This means that you're wiping your installed apps' data. Sometimes in flashing instructions of some ROMs, it is not given to wipe \data because that wouldn't install your new ROM. SO here's the manual way:
Open you file manager.
In your SD Card, there's a folder named "Android". Just delete it!
Now head back to "data>app" select 'em all and delete 'em! (As you've backed-up, don't fear to delete 'em.)
Part 3:
Pre-flash final wipe: This is the final step of wiping manually. CAUTION: After this wipe you MAY NOT be able to use your phone, so before this, finish your any other precious work then head to this part. Now follow these steps:
Open your file manager and again head to Root directory.
Now goto "data" then again "data" folder. Here you'll see lots of folders.
Just select 'em all and press "Delete". SOME FOLDERS MAY NOT BE DELETED as they are currently in use.
Now Reboot or power-off your phone! (If you're unable to reboot/power-off, just pull-out your phone's battery)
Part 4:
Flashing Kernel:Before Installing/flashing a ROM you must install a Kernel otherwise you'll get error in Flashing ROM or get bugs in installed ROM. You can get the kernel to flash inside you ROM's zip. (Just open the ZIP file and extract boot.img) Here are the Kernel Flashing instructions:
Open FlashTool. If you don't have FlashTool, get it here!
Click the Lightning Icon and choose Fastboot mode.
Click Select Kernel to flash and choose your kernel. (if it is .elf file choose .elf format from dropdown menu and if it is .img file choose it from same.)
Before clicking Open, Turn-off your phone. Wait at-least 5 sec. press and hold vol+ (volume increase) button and simultaneously insert data cable into your phone.
A Blue LED will light-up and here you can remove finger from the button. (On some Xperias that light will glow-up in the Illumination bar). Now Press Open by clicking on your kernel.
It'll flash kernel to your device in just 3-5 seconds then you can reboot and Install your desired ROM.
Part 5:
Flashing ROM: This part relates to your respective ROM's flashing instructions. Some important points here can help you:
Most of the Stock, Stock-based and CyanogenMod10, 10.1 ROMs use this wiping precess in Clockworkmod Recovery:
Wipe data/factory reset.
Wipe cache partition.
Goto advanced and wipe dalvik-cache.
Install ROM.
Most of the CyanogenMod 9 ROMs use this wiping procedure:
Install ROM
Install GAPPS
Wipe data/factory reset.
Most of the CyanogenMod 10.2 ROMs use this wiping procedure:
Wipe data/factory reset.
Wipe cache partition.
Goto mount & storage and do a format system.
Install ROM.
Most of the Kit-Kat 4.4 ROMs use this wiping procedure:
Wipe data/factory reset.
Wipe cache partition.
Install ROM.
IMPORTANT: Some ROMs have different wiping procedure, please follow them. This is just for reference purpose if wiping procedure isn't provided in the ROM's thread. Also, DON'T FORGET TO FLASH THE KERNEL every time before you Install a ROM.

For most Xperia Devices the fastboot key is vol+ not vol-. Vol- is for flashmode which is for flashing a stock ftf firmware.

No mention of unlocking bootloader or how to do it, can't flash a kernel without unlocked bootloader. No mention of losing Bravia Engine/X-Reality and DRM keys if bootloader is unlocked. No mention of backing up TA partition. No mention of installing recovery. No mention of the fact that specific versions of recovery are required to flash Kitkat ROMs. Most custom ROM instructions I've seen have the user flashing ROM before kernel.

On #4 you need to add...
Advanced/System
Sent from my SGH-M919 using XDA Premium 4 mobile app

1. Backup data - Better backup using PC Companion or Backup and Restore app (Sony has include this app in stock fw)
2. To enter fastboot mode must be hold volume up (+) not volume down(-) [Flashmode]
Btw nice tutorial for noob

@paxy97 @Levered Oops! Well.... I read this post many times before posting but can't find this mistake. Though I did the flashing procedure hundred of times, I made mistake in writing. Thank you both. Rectifying it now.

gandalf_grey91 said:
No mention of unlocking bootloader or how to do it, can't flash a kernel without unlocked bootloader. No mention of losing Bravia Engine/X-Reality and DRM keys if bootloader is unlocked. No mention of backing up TA partition. No mention of installing recovery. No mention of the fact that specific versions of recovery are required to flash Kitkat ROMs. Most custom ROM instructions I've seen have the user flashing ROM before kernel.
Click to expand...
Click to collapse
Cool man cool! This proposed that the person coming to this thread had already done that and basically and specifically, this is a 'Flashing Thread', not a complete thread..... Chill and Enjoy XDA!

The Sickness said:
On #4 you need to add...
Advanced/System
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where? I can't find. Can you please copy-paste the line where the mistake is...?

cy56 said:
Where? I can't find. Can you please copy-paste the line where the mistake is...?
Click to expand...
Click to collapse
I'm on my cell at the moment...In TWRP there is a Advanced tab, which allows you to wipe System.
Sent from my SGH-M919 using XDA Premium 4 mobile app

The Sickness said:
I'm on my cell at the moment...In TWRP there is a Advanced tab, which allows you to wipe System.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh! That's for CWM not for TWRP..... As most of users use CWM, I've written instructions for TWRP. Also, TWRP doesn't supports 2.3 & 4.0 ROMs ans CWM has total support for all Android versions, that's why....

cy56 said:
Oh! That's for CWM not for TWRP..... As most of users use CWM, I've written instructions for TWRP. Also, TWRP doesn't supports 2.3 & 4.0 ROMs ans CWM has total support for all Android versions, that's why....
Click to expand...
Click to collapse
You are mistaking. TWRP has a Advanced tab. I use it daily. The Advanced tab allows you to wipe the system, dalvik, cache, etc. Basic wipe does not wipe System.
Lack of support you are correct on.
Sent from my SGH-M919 using XDA Premium 4 mobile app

The Sickness said:
You are mistaking. TWRP has a Advanced tab. I use it daily. The Advanced tab allows you to wipe the system, dalvik, cache, etc. Basic wipe does not wipe System.
Lack of support you are correct on.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh man! I know this, I also have used TWRP many times but as I said this thread doesn't follows the TWRP.

But will it work if I have "Bootloader unlock allowed: No"?

cahir1495 said:
But will it work if I have "Bootloader unlock allowed: No"?
Click to expand...
Click to collapse
Dude! There's no issue of Locked Bootloader here. This issue arises when you're installing a ROM. Most of the times you just need to delete boot.img from ROM.zip and it installs but still there are many ROMs that are specifically made for Unlocked Bootloaders. For this refer to your ROM maker's guide.
P.S.: In many ROMs' description there's written "UB" which means only Unlocked Bootlodaer and "LB" which means Locked Bootloader and sometimes both "LB" & "UB" which means that ROM is made for both Locked and Unlocked Bootloaders but each may have different installation method.