Zpad Clean v1.x (1106) - G Tablet Android Development

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...

Related

[Q] Cannot install non-stock kernels.

Okay, so I got the leaked Acer generic Honeycomb 3.1 "update.zip" and it installed without issue. However, after gaining root access (verified via root check), installing Busybox v1.18.4 (1.9 didnt like my device), and installing clockworkmod rev 1.3.4 via Acer recovery I find that I cannot complete the ROM installation. I have tried numerous kernels supposedly geared towards my device to no avail. I did boot into recovery mode, factory reset/wipe, wipe cache, wipe battery statistics, and clear dalvick cache....but it didnt work. None of the three kernels I've tried actually install. So far I have tried "UNITY_V1_2.6.36.4_OC1600_SLQB_CIFS_TUN_VR", "unity_v3_picasso_acer", and "Virtuous_Picasso_v1.0.8_Acer_based_thor-kernel v1.1-beta" They say installation from sd completed, (even though the progress bar lasts all of 3 seconds and the text doesnt properly populate) but I get the boot hang upon power cycle. I did verify that the kernels werent corrupted, and I have been able to unbrick via the 3.1 update.zip. Any help would be appreciated.
Oh and also of note, is that I have two mico SD cards, one 16GB SDHC which for some reason wont mount, and a 2GB SD that mounts properly. Both sd cards were formatted from the tablet.
Try to format /system and /flexrom in the 'mounts and storage' menu of cwr. Then try to reinstall a ROM
Sent from my HTC Desire using XDA App
sc2k said:
Try to format /system and /flexrom in the 'mounts and storage' menu of cwr. Then try to reinstall a ROM
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I will try that and get back to you. Thank you for the suggestion.
edit...
Okay, I followed your suggestions and it didnt make a difference(custom ROM install from SD card completes in 3 seconds, then hangs on the Acer splash screen upon reboot), also while reinstalling the leaked 3.1 stock ROM it gives me a stop error? "random offset 0x339", but completes the installation of said stock 3.1 ROM.
cq842000 said:
I will try that and get back to you. Thank you for the suggestion.
edit...
Okay, I followed your suggestions and it didnt make a difference(custom ROM install from SD card completes in 3 seconds, then hangs on the Acer splash screen upon reboot, also upon reinstalling the leaked 3.1 stock ROM it gives me a stop error? random offset 0x339, but completes the installation of said stock 3.1 ROM.
Click to expand...
Click to collapse
Strange. Check if all partitions can be mounted (from 'mounts and storage' menu). Also, is there anything interesting in /tmp/recovery.log?
According to recovery, everything but the 16GB SD card can be mounted successfully. As for the second suggestion, where would I find the tmp directory? I dont see it in root so where would it be?
cq842000 said:
According to recovery, everything but the 16GB SD card can be mounted successfully. As for the second suggestion, where would I find the tmp directory? I dont see it in root so where would it be?
Click to expand...
Click to collapse
You need adb for this. If you do not have adb, see this guide how to install it (but skip step 7).
Then boot into recovery and try to install a ROM (which will most likely fail). Next, from the console on your pc (the one where you also typed "adb devices") type:
Code:
adb pull /tmp/recovery.log
This will pull the file from your device and save it in the folder where adb is installed.
Alright, I'll get right on it, and get back with some text.
i see here, after u wipe data, u install kernel only zip file???
then you dont have OS flashed, how can it boot
u sholud flash full rom after wipe data, not kernel only..
interqd said:
i see here, after u wipe data, u install kernel only zip file???
then you dont have OS flashed, how can it boot
u sholud flash full rom after wipe data, not kernel only..
Click to expand...
Click to collapse
Lol, I should read the post better next time
@OP: interqd is right. You have to install a full ROM, not just the kernel.
Sent from my HTC Desire using XDA App
interqd said:
i see here, after u wipe data, u install kernel only zip file???
then you dont have OS flashed, how can it boot
u sholud flash full rom after wipe data, not kernel only..
Click to expand...
Click to collapse
Well it looks like I have some more research to do.
These are the instructions I was following...
Overclock Acer Iconia
To begin, copy the kernel you downloaded from the link above, to the root of your SD card.
Once the file is copied, reboot your device into recovery mode. (Power off the device and hold the Power button and Volume down until text in the upper left corner appears. When it does, release the Volume down button.)
Once in the recovery, make a NANDroid backup.
Now, wipe cache and dalvick cache.
Once done, simply flash the kernel you copied to your SD card and let it install and then simply reboot your device.
My n00bish terminology was incorrect, I am trying to flash a custom kernel.
Everytime I try to flash any of those kernels in the original post now I get the garbled screen. What am I doing wrong with the kernels? I followed the instructions to the letter.
Are you trying to install a custom kernel over stock ROM? If so, that's why it's not working. Try with a full custom ROM image.
FloatingFatMan said:
Are you trying to install a custom kernel over stock ROM? If so, that's why it's not working. Try with a full custom ROM image.
Click to expand...
Click to collapse
I suppose I need to find one then. This one that I am using is 3.1 stock but rooted. At any rate, thanks to everyone who took the time to help me find my roots. I've been overclocking notebooks and desktops for years and I thought I'd jump right into the tablet sector as well. Anyways thank you all for your help and guidance.
cq842000 said:
I suppose I need to find one then. This one that I am using is 3.1 stock but rooted. At any rate, thanks to everyone who took the time to help me find my roots. I've been overclocking notebooks and desktops for years and I thought I'd jump right into the tablet sector as well. Anyways thank you all for your help and guidance.
Click to expand...
Click to collapse
There are several in the dev section.
Okay, I just wanted to come in and update. I got the virtuous picasso rom and unity V3 kernel installed and running flawlessly. I am loving it by the way, so now I can get down to what I intended...overclocking and benchmarking. Thank you all for your help.
My goodness it's so easy to overclock these tabs, no doubt due in magnitude to the hard work of the developers of these custom kernels/ROMs.
@ 1.6ghz on Quadrant Standard
{
"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"
}

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..

[ROM Release] Customized ICS B928 GaDaNa v5.2.1 (bronxitas)

Hello u8800pro Owners!
I want to share bronxitas (GaDaNa team) work, a customized rom, based on the latest Ice Cream Sandwich official ROM.
Everything was done for bettter performance and usability.
Features:
ICS 404029 baseband is now available (read more how to install it below)
Better multitasking
Root.
ODEX.
Better and extended Power Widgets.
Setup wizard disabled.
Unlocked FPS.
"Smooth Scroll".
Volume Rocker (Wake up phone with volume buttons).
Customized build.prop.
Battery showing in percentage.
Updated Host.
Radio.
Optimized the GPS config.
Chrome synchronizing .
Updated GAPPS.
Better sound in call volume.
Better video rendering.
Some unuseful scripts was deleted.
Modificated boot.img (by giris) with init.d.
Some apps was deleted (youtube, maps, etc.), but you can download it from Gplay.
AND MUCH MORE!..
Installation:
You must be on 2.3 based ROM:
1) You need to flash Step1 from official B926 for bigger system partition capacity,
you can download it here:
http://www.mediafire.com/?u9mvoxjf4lmlu8p
2) Download ZIP;
3) Shutdown your smartphone and to be really sure unplug the battery;
4) Insert your battery and power on your smartphone into recovery mode holding down VOL+ and the power button (be sure that you have the CWM 5.0.2.7);
5) Go to advanced ---> reboot recovery;
6) Wipe data/factory;
7) Wipe cache;
8) Wipe Dalvik Cache;
9) Wipe Battery Stats;
10) Install zip from sdcard;
11) Choose zip from sdcard and select the downloaded zip file;
12) Install complete!
13) Reboot system now.
IF YOU WANT ICS 404029 BASEBAND:
remember, that ICS baseband libs are also diffrent from GB libs.
ICS baseband https://docs.google.com/file/d/0B_kPUrNkk3T0TzFsMzZoMjg0QlU/edit?pli=1
Do not quit cwm after rom installation and then install this baseband.
2.3 baseband https://docs.google.com/file/d/0B_kPUrNkk3T0QmRkTld5SFh5Vm8/edit?pli=1
If you want your baseband back, you should keep it in your SD card if you want another rom.
Download:
5.2 http://www.mediafire.com/?uht9vo12cbol12d
5.2.1 http://www.mediafire.com/?ckhnjh1ud4e8yff
Special thanks:
- bronxitas (amazing rom)
- giris (boot.img and power widgets);
{
"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"
}
Had the pleasure to recieve infos about this ROM already a few days before the release, i can tell you it is a sick job, this rom is pure awesomeness
Great job Bronxitas & Giris! :good:
Edit: installing the newest and fixed version, we forgot i was still on a sort-of beta release
please help!
I have Rom Official ICS 4.0.3 V100R001C00B927
Today I've decided to up [ROM Release] Customized ICS GaDaNa b927 (by Bronxitas)
but I have to CWM to CWM is the machine that is not CWM 5027.
I transcribed the CWM 5027 and I press vol + vol-machine power but not the pink screen but the screen firmware update and stood there.
now I have to do? please help!
thanks everyone!
sorry my bad english!
The procedure is fairly simple my friend, you have to be in a 2.3 based ROM, official or custom, no matter, with root permissions and Clockworkmod 5.0.2.7.
Connect your sd-card on your PC, format it in FAT32, create a folder named [dload] and copy in it the file called Update.APP. At this point shutdown your phone, press Power vol+ and vol- and the firmware update should start, let him keep rebooting a few times, at the end of the procedure you should be booted into CWM Recovery. Advanced->reboot recovery->mount and storage -> mount USB->copy the ROM zip into your sd card (and delete the dload folder while you are there!)->isntall zip from sd card and flash it.
What are you missing?
Very good
5 minutes ago I put it ... well it works!
May I ask, in Poer Widgets can you put an option Screenshot?
And...boot.img for OC?
In the [Quick Panel Settings] - found in the app drawer - you can change the Power Widget buttons and their order as you may pelase
dingila said:
And...boot.img for OC?
Click to expand...
Click to collapse
for OC we will wait geno kernel, in this rom is small bug, in call volume is pretty low (if you are close to road or something) so again, we will wait geno for better incall volume (maybe Bronxitas will fix incall volume, i dunno)
How to install this rom?
I have the B876_KALO Rom, also I have the CWM 5.0.2.7 I can install as per instructions of kalo is 2.3.6, plus I have a U8800-51, other times I have not worked on wifi
Thanks for your reply
Can't flash repartition.
Daniel 07 said:
The procedure is fairly simple my friend, you have to be in a 2.3 based ROM, official or custom, no matter, with root permissions and Clockworkmod 5.0.2.7.
Connect your sd-card on your PC, format it in FAT32, create a folder named [dload] and copy in it the file called Update.APP. At this point shutdown your phone, press Power vol+ and vol- and the firmware update should start, let him keep rebooting a few times, at the end of the procedure you should be booted into CWM Recovery. Advanced->reboot recovery->mount and storage -> mount USB->copy the ROM zip into your sd card (and delete the dload folder while you are there!)->isntall zip from sd card and flash it.
What are you missing?
Click to expand...
Click to collapse
It keeps showing"Step 2/2" and below, a warning sign saying: "Update Failed"
What am I missing?
lucmhv said:
It keeps showing"Step 2/2" and below, a warning sign saying: "Update Failed"
What am I missing?
Click to expand...
Click to collapse
you see this then installing repartition step1 update.app?? if yes, try to install update without battery just with usb pluged in and start updating with combination of vol+vol-power, if it still wont work, try to change recovery to stock and flash again
My current machine after I copy the folder recovery 5.0.2.7, the machine does not cust back on again. It reported image recovery failed due to copy errors (I get the calories burned to recovery). now I have to do? My love
Available means when I remove the memory card and press vol + vol - and the power it out pink screen connected to the computer does not see the drive to copy the recovery should not know how! hu hu
quangcon1980 said:
My current machine after I copy the folder recovery 5.0.2.7, the machine does not cust back on again. It reported image recovery failed due to copy errors (I get the calories burned to recovery). now I have to do? My love
Available means when I remove the memory card and press vol + vol - and the power it out pink screen connected to the computer does not see the drive to copy the recovery should not know how! hu hu
Click to expand...
Click to collapse
i think that you trying install rom on android 4.0.3, read the instructions, please, PLEASE READ THE INSTRUCTIONS, and then everything will be ok
pauliuxxx said:
i think that you trying install rom on android 4.0.3, read the instructions, please, PLEASE READ THE INSTRUCTIONS, and then everything will be ok
Click to expand...
Click to collapse
.I have installed 4.0.3 Official ICS V100R001C00B927 rom. and I flash the rom of you and you say need CWM 5.0.2.7, and when I press CWM 5.0.2.7 by kalo's .but i press vol + and power, the machine is not in recovery. Now I do? expect people to help.
and now my machine does not use anymore.
and as well as the problems I asked above.
Thanks a lot
Downgrade to official B572, root, CWM recovery. At this point unrar the file you have downloaded from the first link, put the update.app in the sd card in a folder named dload, power off the phone and press power vol+ vol-. When it finishes the process, you should boot into recovery to flash the ROM zip.
Daniel 07 said:
Downgrade to official B572, root, CWM recovery. At this point unrar the file you have downloaded from the first link, put the update.app in the sd card in a folder named dload, power off the phone and press power vol+ vol-. When it finishes the process, you should boot into recovery to flash the ROM zip.
Click to expand...
Click to collapse
how Downgrade to official B572 ? i dont know. thank you!
machine error on startup :
image signature verify fail!
your boot/recovery image may have an incorrect signature
plesea update you image to a signature official one.
you canremove battery for power down.
quangcon1980 said:
how Downgrade to official B572 ? i dont know. thank you!
machine error on startup :
image signature verify fail!
your boot/recovery image may have an incorrect signature
plesea update you image to a signature official one.
you canremove battery for power down.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1793014&page=3
It's stop here step 1/2 unpacking not run again.near 30 minute.
pink screen is not connected to the computer?not see its drive.
way connection?
quangcon1980 said:
It's stop here step 1/2 unpacking not run again.near 30 minute.
pink screen is not connected to the computer?not see its drive.
way connection?
Click to expand...
Click to collapse
You haven't downgraded to 2.3. Why? I posted a link where all is explained.
i dont't know.
I copied the recovery 5.0.2.7 of Kalo, and it was like that until now.
How do you connect your phone to a computer from a pink screen?
it does not see my drive.
You must downgrade to 2.3 first. Then do as writed in instructions.
Sent from my ragelis

[GUIDE]Those having problems with flashing TWRP 2.6.3.1

Ok, first of all. I've been in your steps whoever is having the data mounting error and is preventing them from installing CM11. SO here's what you gotta do.
1. Factory reset your WHOLE device before flashing this.
2. Convert your bin file into a zip and name it update.zip (go into properties and make sure your well known file extensions aren't hidden)
3a. Go into old TWRP (don't flash 2.6.3.1 just yet)
3b. Wipe Data, Cache, and Dalvik Cache. DO NOT wipe system.
4. Flash the update.zip. You shouldn't have any problems with flashing it and it should boot up when you restart it. (if you have troubles flashing it, go into ubuntu and change the update-script in the first few lines (codename) from "blaze" to "otter". Save it. Now put it into your SD card and flash it and NOW it should work.)
5. Go into Kindle Fire Utility (found here), run "run" and install FFF 1.4a (make sure you have drivers installed before doing this, duh )
6. Press Shift and Right click the "tools" folder in the KFU folder and click on "Open command window here"
7. Download TWRP 2.6.3.1 found here (select otter 2.6.3.1)
8. Restart your kindle fire and type in "fastboot flash recovery twrp.img" (rename it twrp.img or it won't detect it but move it inside the "tools" folde" so it'll find it). When your kindle starts up, it will detect it and flash the image.
9. Congratulations, you have successfully installed TWRP 2.6.3.1 without data mounting problems anymore. (this is what I followed to fix my problem.)
10. Flash CM11 and Enjoy
Also, if you want to dualboot, just use this and follow the guide..
Credit to:
FuZZ_+Hashcode for CM11
awidawad for KFU
Dees_Troy for TWRP
Amazon for the firmware
Me for discovering this
Please click thanks this guide helped/inspired you.
Hope it helped anyone who had the same problem
New way
Sorry i can't post link.
Download newest recovery file (*.img) at:
techerrata*com/browse/twrp2/blaze
It can found in twrp-2.6.3.1-otter.zip.
Install Flashify (for root users)
Flashify (for root users)
Open Flashify, allow root
Flashify (for root users)
Choose tab FLASH->recovery image->file explorer->your *img file
Restart and done.
LGHater said:
Ok, first of all. I've been in your steps whoever is having the data mounting error and is preventing them from installing CM11. SO here's what you gotta do.
1. Factory reset your WHOLE device before flashing this.
2. Convert your bin file into a zip and name it update.zip (go into properties and make sure your well known file extensions aren't hidden)
3a. Go into old TWRP (don't flash 2.3.6.1 just yet)
3b. Wipe Data, Cache, and Dalvik Cache. DO NOT wipe system.
4. Flash the update.zip. You shouldn't have any problems with flashing it and it should boot up when you restart it. (if you have troubles flashing it, go into ubuntu and change the update-script in the first few lines (codename) from "blaze" to "otter". Save it. Now put it into your SD card and flash it and NOW it should work.)
5. Go into Kindle Fire Utility (found here), run "run" and install FFF 1.4a (make sure you have drivers installed before doing this, duh )
6. Press Shift and Right click the "tools" folder in the KFU folder and click on "Open command window here"
7. Download TWRP 2.3.6.1 found here (select otter 2.3.6.1)
8. Restart your kindle fire and type in "fastboot flash twrp.img" (rename it twrp.img or it won't detect it but move it inside the "tools" folde" so it'll find it). When your kindle starts up, it will detect it and flash the image.
9. Congratulations, you have successfully installed TWRP 2.3.6.1 without data mounting problems anymore. (this is what I followed to fix my problem.)
10. Flash CM11 and Enjoy
Credit to:
FuZZ_ for CM11
awidawad for KFU
Dees_Troy for TWRP
Amazon for the firmware
Me for discovering this
Please click thanks this guide helped/inspired you.
Hope it helped anyone who had the same problem
Click to expand...
Click to collapse
What if you are dualbooting?
Vlasp said:
What if you are dualbooting?
Click to expand...
Click to collapse
Follow this guide for using dualboot.
Also, my apologies. I'm not good at explaining how to dualboot so that's the reason I didn't include how to dualboot in this guide. Sorry
duanpv said:
Sorry i can't post link.
Download newest recovery file (*.img) at:
techerrata*com/browse/twrp2/blaze
It can found in twrp-2.6.3.1-otter.zip.
Install Flashify (for root users)
Flashify (for root users)
Open Flashify, allow root
Flashify (for root users)
Choose tab FLASH->recovery image->file explorer->your *img file
Restart and done.
Click to expand...
Click to collapse
I don't recommend flashify because it caused problems with mounting partitions for me.
duanpv said:
Sorry i can't post link.
Download newest recovery file (*.img) at:
techerrata*com/browse/twrp2/blaze
It can found in twrp-2.6.3.1-otter.zip.
Install Flashify (for root users)
Flashify (for root users)
Open Flashify, allow root
Flashify (for root users)
Choose tab FLASH->recovery image->file explorer->your *img file
Restart and done.
Click to expand...
Click to collapse
Did you try it?
Sent from my air powered ceiling fan
I can confirm that using flashify ends up causing problems with mounting data partition.
What's the best way to get out of having no way to mount data? Should i use FFF to return to an earlier version of twrp?
Sent from my ADR6400L using Tapatalk
androvista said:
Did you try it?
Sent from my air powered ceiling fan
Click to expand...
Click to collapse
yes, i did.
A screenshot:
{
"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"
}
I tried to do this, install hashcode's CM 11.0, and set up dual-booting with a modded stock ROM. I did finally get it working, just from the info here and here, and wiping everything a few times.
I installed TWRP 2.6.3.1 through fastboot just fine.
I did run into the problem with mounting /data, but not until after I had CM 11.0 installed and running. I had to go through the dual-boot set up in KFU a couple of times before I could get the alternate ROM to boot properly. I don't quite remember what steps I actually took that finally got everything working correctly.
( I tried to reply to hachcode's thread, but I realize I haven't made enough posts to be able to post in the dev forum. I've just been lurking here for a year or so).
The problem is that my usb port doesnt work so I can't connect via fastboot.
duanpv said:
Sorry i can't post link.
Download newest recovery file (*.img) at:
techerrata*com/browse/twrp2/blaze
It can found in twrp-2.6.3.1-otter.zip.
Install Flashify (for root users)
Flashify (for root users)
Open Flashify, allow root
Flashify (for root users)
Choose tab FLASH->recovery image->file explorer->your *img file
Restart and done.
Click to expand...
Click to collapse
Thanks, this worked very well for me too. It is worth a try since it is so easy. I am loaded up with twa_priv's cm 11.0 rom now.
missing command?
LGHater said:
8. Restart your kindle fire and type in "fastboot flash twrp.img" (rename it twrp.img or it won't detect it but move it inside the "tools" folde" so it'll find it). When your kindle starts up, it will detect it and flash the image.
Click to expand...
Click to collapse
"fastboot flash twrp.img" didn't work for me but it might for others.
Changing it to fastboot flash recovery twrp.img worked....to get 2.6.3.1 to flash *but* it didn't fix the Data Mount Error for me after following your steps (going back to OEM rom, etc). Oh side note, for some reason, I can only flash the Amazon OEM Stock Kindle Fire Rom update-kindle-6.3.2_D01E_4110520.bin (changed to Update.zip) by installing this version of TWRP (openrecovery-twrp-2.3.3.1-blaze.img)
I've tried every technique I can find here and it seems flashing 2.6.3.1 works with all of these techniques:Hashcode's original instructions, Using Kindle Fire Utility, your technique above, upgrading TWRP step by step from version 2.4.x., using Flashify - *but* I end up with data mount error every time.
TWRP 2.6.3.0 works fine for me (no error) but it won't flash any of the KitKat builds I've found here.
I had to run the Utility while I was in TWRP mode.
there, windows found the ADB device and I was able to select normal mode and online,
then select update TWRP to latest,
then device rebooted.
I could not get the drivers installed thru windows, no matter what I tried
Thanks
NotQuiteANoob said:
"fastboot flash twrp.img" didn't work for me but it might for others.
Changing it to fastboot flash recovery twrp.img worked....to get 2.6.3.1 to flash *but* it didn't fix the Data Mount Error for me after following your steps (going back to OEM rom, etc). Oh side note, for some reason, I can only flash the Amazon OEM Stock Kindle Fire Rom update-kindle-6.3.2_D01E_4110520.bin (changed to Update.zip) by installing this version of TWRP (openrecovery-twrp-2.3.3.1-blaze.img)
I've tried every technique I can find here and it seems flashing 2.6.3.1 works with all of these techniques:Hashcode's original instructions, Using Kindle Fire Utility, your technique above, upgrading TWRP step by step from version 2.4.x., using Flashify - *but* I end up with data mount error every time.
TWRP 2.6.3.0 works fine for me (no error) but it won't flash any of the KitKat builds I've found here.
Click to expand...
Click to collapse
I did the process stated in the OP too, and it failed to fix my mounting data/cache issue. Like you, everything I have tried has failed: flashify method, do a silly dance method, etc. Nothing works, and have tried many things. THIS might work, but it seems a daunting process that may or may not help.
Also, I have tried multiple sources for 2.6.3.1 in both img and zip formats.
I used the version of TWRP you cited to flash the OEM kindle fire update. This wiped everything: system, bootloader, recovery, everything. Then I used KFU to flash FFF and TWRPs from 2.5xx to 2.6.3.1, one by one, and it still wouldn't mount data. :/
I honestly cannot see how formatting things being some help is going to explain how from TWRP version 2.6.3.0 down to the first one I ever used have never had this mounting issue once, and if I re-flash an old TWRP....bam....I can mount things and backup/restore just fine again. This (and I'm no expert) tells me that my formatting is just fine. Interestingly, the 2.6.3.0 TWRP made by Hashcode to support SELinux can't mount data/cache in the same way as 2.6.3.1.
Not being able to mount data seems to be happening randomly, which is too weird, but even after formatting everything possible TWRP 2.6.3.1 won't mount data while every other version will. TWRP 2.6.3.1 is just kinda screwed, unless I'm way off. In the end, I may just go back to ICS or JB and stick with TWRP 2.6.3.0 until some more headway is made in the KF 4.4.x dev scene.
KitKat is worth it.
dwarf_t0ssn said:
Not being able to mount data seems to be happening randomly, which is too weird, but even after formatting everything possible TWRP 2.6.3.1 won't mount data while every other version will. TWRP 2.6.3.1 is just kinda screwed, unless I'm way off. In the end, I may just go back to ICS or JB and stick with TWRP 2.6.3.0 until some more headway is made in the KF 4.4.x dev scene.
Click to expand...
Click to collapse
I can tell you that I will never go back once I figured out how to flash Kitkat here "http://forum.xda-developers.com/showthread.php?p=48416534#post48416534". KitKat is nirvana for me on this old KF. With 10.1/10.2 I was always having FC, crashes, SOD, but KK has been great. The only issues I've had are with Amazon MP3, Google Music and youtube apps which won't run for me at all. I have no idea if they are related to KK, a rooted KF, the data mount issue or what. I hate that I can't backup so I'm hesitant to update to new nightlies but I have once already and it worked ok. To update to a new nightly, I use the "about tablet / update cyanogenmod" method. For some reason while TWRP won't flash CM11 for me directly, if I use that built in updater, it ignores the errors and works.
NotQuiteANoob said:
"fastboot flash twrp.img" didn't work for me but it might for others.
Changing it to fastboot flash recovery twrp.img worked....to get 2.6.3.1 to flash *but* it didn't fix the Data Mount Error for me after following your steps (going back to OEM rom, etc). Oh side note, for some reason, I can only flash the Amazon OEM Stock Kindle Fire Rom update-kindle-6.3.2_D01E_4110520.bin (changed to Update.zip) by installing this version of TWRP (openrecovery-twrp-2.3.3.1-blaze.img)
I've tried every technique I can find here and it seems flashing 2.6.3.1 works with all of these techniques:Hashcode's original instructions, Using Kindle Fire Utility, your technique above, upgrading TWRP step by step from version 2.4.x., using Flashify - *but* I end up with data mount error every time.
TWRP 2.6.3.0 works fine for me (no error) but it won't flash any of the KitKat builds I've found here.
Click to expand...
Click to collapse
Oh yeah, thanks. I fixed it. It took me THAT long to realize it, lol.
If this guide did not work for you, here is another flashify method(no IMG file, this is different from the actual flashify method)
Download this file(coming soon)
Install flashify
Paste the file here: /sdcard/Android/data/com.cgollner.flashify/files/flashify-backup/recovery
Go to flashing and restore backup of twrp_2.6.3.1.
If I helped, press the thanks button!
Sent from my Amazon Kindle Fire using xda app-developers app
2 things you need to know and Viola! all is good.
First of all. I had the data mounting issue with TWRP 2.6.3.1 . Hashcode posted a fix and it worked for me. CAUTION: It also did a factory reset on my KF so do a backup first. I ended up just wiping everything with TWRP 2.6.3.0, then install 2.6.3.1 and run Hashcode's fix. Then you can install KitKat 4.4 and the right gapps with no problems.
Here's the fix from this page
http://forum.xda-developers.com/showthread.php?t=1591850&page=294
all credit to Hashcode
"First make sure in the recovery "Mount" screen that "Data" and "Cache" are unchecked.
Then try this from your PC via command window:
adb shell
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
exit
This should to a full format of those 2 partitions using ext4 fs w/ XATTRs enabled. "
-------------------------------------------------------------------------------------------------------------------------
2nd, I had the other common problem with most of the Amazon Apps crashing at start up. You'll see someone reference this problem and fix on the same page where I got the Hashcode fix. Here's where you can download the zip http://forum.xda-developers.com/showpost.php?p=48462264&postcount=338 Installing this from TWRP fixed the issues with the Amazon apps for me.
*I just updated to the newest nightly 1225 and it removed/overwrote the nexus zip. I could tell because as soon as it rebooted, the KF started reporting the kindle app had crashed. I confirmed the model number in "about tablet" had changed back to kindle fire. After reinstalling the nexus zip everything works again. I guess you have to reinstall the nexus zip everytime you update the ROM."
i am not able to flash stock rom..says unknown command get("ro.build.product") == "blaze". i am using windows 7..
please help
Use twrp 2.2.2.1 or lower to install stock kindle firmware.
Flashable zip in my list sd_shadow's collection of links for: Kindle Fire 1
Sent from my Amazon OtterX using Tapatalk

[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

Categories

Resources