Related
Hello,
I tried to install the latest version 7 CyanogenMod Typhoon v2.8.6 + RC3 [2.3.3] [A2SD] [tytung r8.3] CWM but comes installed with the "nand kernel open failed" I have the version with 150 MB partition, I read that I should use the 400 mb but how can I change the recovery?
go to the cement recovery thread. it will have links for CWM 1.13 in different sizes, 150, 250,400mb. pick whichever size is suggested by the rom u want to flash. boot into magdlr by turning off phone and then power back on and just hold power button down till a black screen pops up with 12 different options. choose USB FLASHER. plug phone to computer. unzip whichever cwm version u downloaded to your desktop. run daf.exe
Sent from my HTC HD2 using XDA Premium App
Ok, is possible overwrite the old cwm? But my previous partition will be erased with my data....
Sent from my HTC HD2 using XDA App
Yes its possible to flash over the top.
I use typhoon with 140meg size, u don't need 400 and indeed will have 250meg wasted space.
I'd look at the versions of magldr and cwm you are running,. There are differences.
also, no need to download the different cwm sizes, if you want 400 just edit the flash.cfg file and change the system size line to whatever you want.
samsamuel said:
Yes its possible to flash over the top.
I use typhoon with 140meg size, u don't need 400 and indeed will have 250meg wasted space.
I'd look at the versions of magldr and cwm you are running,. There are differences.
also, no need to download the different cwm sizes, if you want 400 just edit the flash.cfg file and change the system size line to whatever you want.
Click to expand...
Click to collapse
wanna give him atleast a tiny clue of how to do that???
Sent from my HTC HD2 using XDA Premium App
chrisgto4 said:
wanna give him atleast a tiny clue of how to do that???
Click to expand...
Click to collapse
well for checking magldr and cwm versions, i wouldnt bother, id just go get the latest versions and flash them. Ten minutes to be sure you're bang up to date.
For editing flash.cfg, (mine pasted below for reference) open notepad, drag and drop into it the flash.cfg file.
Each line is for the creation of one partition, so look for the system line, and change it to the size system partition you want.
=============<paste of flash,cfg contents for setting a 135meg partition,>
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 135M
cache ya 44M
userdata ya|asize|hr allsize
=============</paste>
example for 250 meg system use
system ya 250M
save the file, flash cwm and it is now a 250meg system partition..
Sorry,.... my error. I try to update a rom for clk with MAGLDR :-(
I'm stupid....now it works. Thanks
Sent from my HTC HD2 using XDA App
Well that doesn't help me at all, I've got the clk version of the latest typhoon, tried installing with clk...
Nand kernel open failed...
Tried clean install of clk, still fails.
I guess I'll try a clean install of MAGLDR, too...
Okay, I get it now, clk is not CLocKworkmod, I needed the MAGLDR version.
any news on that? I also get this error.
nand open kernel failed
do all beginners understand this? you are probably putting the 'clk' version of the rom in your storage card for installation. you need the 'magdlr' version of the rom for clockwork mod to correctly install android
Hey Folks!
I´m with CM7 now for several weeks and i´m quite happy with it! Just for my personal interest I wanted to give WP7 a try, so I´m very interested in the possibility to make a full backup of my Android System with Clockwork Recovery (where it is possible to get a full working ROM file including all data and apps, isn´t it?)
But here´s the problem now: as soon as I want to use CW (point 9: AD Recovery), it says das there´s an "invalid boot image header" and I can´t use any of CWM´s functions. It seems like this is based on the fact that I´ve installed Rom Manager and updated my CW with it, ignoring (or more "not knowing") that this can only by used when having clk installed and NOT Magldr...
The question for now is: what possibilities do I have now to make a full backup of my system, including all data, all programs, dictionaries and settings I made? Are Titanium Backup/BackupEverthing the only two ways to get out of this chaos? Has anybody some experience with those apps? Will everything work again after a fresh ROM install?
Tried to use the magldr SD Version...it didn´t work...
I´m still hoping for help, friends
brooon said:
Hey Folks!
I´m with CM7 now for several weeks and i´m quite happy with it! Just for my personal interest I wanted to give WP7 a try, so I´m very interested in the possibility to make a full backup of my Android System with Clockwork Recovery (where it is possible to get a full working ROM file including all data and apps, isn´t it?)
But here´s the problem now: as soon as I want to use CW (point 9: AD Recovery), it says das there´s an "invalid boot image header" and I can´t use any of CWM´s functions. It seems like this is based on the fact that I´ve installed Rom Manager and updated my CW with it, ignoring (or more "not knowing") that this can only by used when having clk installed and NOT Magldr...
The question for now is: what possibilities do I have now to make a full backup of my system, including all data, all programs, dictionaries and settings I made? Are Titanium Backup/BackupEverthing the only two ways to get out of this chaos? Has anybody some experience with those apps? Will everything work again after a fresh ROM install?
Click to expand...
Click to collapse
Hi,
Rom Manager only works with cLK.
If you use it with MAGLDR ,it will screw up your CWM.
Unless you made a NAND backup before you started all of this ,you are, indeed, in deep doo-doo...
If you now go and try to re-install clk or magldr,it will wipe your rom,data etc.
Your only hope to save your data now,is something like Titanium Backup,or similar.
Once you re-install clk or magldr,flash CWM partition for your new ROM and flash ROM,everything will work again,but obviously without your data and settings.Titanium Backup will back up and restore apps and data to a degree,but not as well as a NAND backup.
Try and re-install a similar rom to the one you have now.Then restore Titanium backup,then make a NAND backup,to protect you against any future folly...
Thank you for your help!
I´ve tried to get into the SD magldr CWM version again...and finally, I won!
- Services
- Bootsettings
- AD SD Dir
- (choose folder with SD magldr CWM inside)
- --> Boot SD AD
Click to expand...
Click to collapse
I was able to make a backup of my Android...it´s flashing-time now
Tell me please, where did you get SD magldr CWM version?
This should be it: Klick
Explain please
brooon said:
Thank you for your help!
I´ve tried to get into the SD magldr CWM version again...and finally, I won!
I was able to make a backup of my Android...it´s flashing-time now
Click to expand...
Click to collapse
Could you please explain how you(won) managed to fix "invalid boot image header" I would also like to take a backup, but facing the same problem. Thanks a lot.
And I am newbe in this "game".
PS! I have installed this ROM : TyphooN CyanogenMod 7 Nightly v3.3.2
This saved me a tremendous headache TY!
Can't dd do something?
I have the recovery partition image file that came with the DAF flash tool:
# ls -l /mnt/sdcard/r*
----rwxr-x 1 system sdcard_r 4005888 Mar 26 00:38 /mnt/sdcard/recovery-raw.img
The recovery partition is mtd1:
# cat proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "misc"
mtd1: 003e0000 00020000 "recovery"
mtd2: 00500000 00020000 "boot"
mtd3: 09600000 00020000 "system"
mtd4: 00500000 00020000 "cache"
mtd5: 30000000 00020000 "userdata"
Can't the partition be fixed somehow with dd?
I tried:
# dd if=/mnt/sdcard/recovery-raw.img of=/dev/mtd/mtd1 bs=4096
978+0 records in
978+0 records out
4005888 bytes transferred in 0.982 secs (4079315 bytes/sec)
But no luck.
golagha11 said:
Could you please explain how you(won) managed to fix "invalid boot image header" I would also like to take a backup, but facing the same problem. Thanks a lot.
And I am newbe in this "game".
PS! I have installed this ROM : TyphooN CyanogenMod 7 Nightly v3.3.2
Click to expand...
Click to collapse
It worked for me:
unzipped the file to a directory - say ADRecovery
Then from MAGLDR
- Services
- Bootsettings
- AD SD Dir
- (choose folder with SD magldr CWM inside -ADRecovery)
Go back to main menu and select Boot AD SD
It came to the AD Recovery menu of MAGLDR.
john0902 said:
I have the recovery partition image file that came with the DAF flash tool:
# ls -l /mnt/sdcard/r*
----rwxr-x 1 system sdcard_r 4005888 Mar 26 00:38 /mnt/sdcard/recovery-raw.img
Click to expand...
Click to collapse
This command got me back to the originally flashed working NAND recovery partition:
flash_image recovery /sdcard/recovery-raw.img
This thread has more info on the issue, as well as downloads, etc.
The problem seems to that earlier recovery partitions were under 4MB and newer ones are around 5MB. My original partition config included this line:
recovery rrecov|ro|nospr filesize recovery-raw.img
Iow, it made the recovery partition the 'filesize' of the older recovery image size. Newer recoveries don't fit. If you want a newer recovery partition, you need to partition your NAND with a bigger recovery partition, or run the newer recoveries off SD.
follow this thread
http://forum.xda-developers.com/showthread.php?t=1090783
akshan said:
It worked for me:
unzipped the file to a directory - say ADRecovery
Then from MAGLDR
- Services
- Bootsettings
- AD SD Dir
- (choose folder with SD magldr CWM inside -ADRecovery)
Go back to main menu and select Boot AD SD
It came to the AD Recovery menu of MAGLDR.
Click to expand...
Click to collapse
Thx, simple and detailed explanation
link is not working
akshan said:
It worked for me:
unzipped the file to a directory - say ADRecovery
Then from MAGLDR
- Services
- Bootsettings
- AD SD Dir
- (choose folder with SD magldr CWM inside -ADRecovery)
Go back to main menu and select Boot AD SD
It came to the AD Recovery menu of MAGLDR.
Click to expand...
Click to collapse
Could you please share your link to sd magldr cwm once more - the link above doesn't work anymore...
thx
just managed to find a working link for sd magldr: link
This error happened to me before, and it was fixed by restoring the CWM backup and then flashing the kernel via CWM before rebooting.
akshan said:
It worked for me:
unzipped the file to a directory - say ADRecovery
Then from MAGLDR
- Services
- Bootsettings
- AD SD Dir
- (choose folder with SD magldr CWM inside -ADRecovery)
Go back to main menu and select Boot AD SD
It came to the AD Recovery menu of MAGLDR.
Click to expand...
Click to collapse
Hi! The "file" link doesnt work.. could anyone help plz?
brooon said:
This should be it: Klick
Click to expand...
Click to collapse
Link not working. Please help
Same problem here! I really dont want to loose my files. Please can someone post the right file or help me with a workaround.
Hey everyone.
Can any senior member write me a bit of a guide as of what do I have to do in order to switch ROMs with different partition requirements?
I am looking for as little work as possible. I am having problem making ADB run on my computer, so I need a way to do it without need of ADB. Preferably something straight from the phone. So:
Of course, first I do nandroid backup through CMR. Then what?
Do I have to get to fastboot somehow and manually change values?
Or when I download the cLK ROM version, do I just flash it through CMR by zip from SD and it will repartition automatically to fit the requirements?
Currently my system partition is 190MB, and I'd like to try a 2 roms that are 150MB and 220MB required.
Thanks in advance.
while you wait for someone to link you to the (easily findable ) guide stickies, you can flash a 150 rom to a 190 partition if you are just playing. you will waste 40 meg, but if you're planning to flash again it hardly matters.
Yeah, I figured that, but I am more interested in a quick and safe way to switch system partition size, without ADB.
and when looking at roms, i only see different requirements, but no way to change the sizes.
Would you be so kind to explain, how this repartitioning works for flashing new roms? (clk)
When you flash clockwork, there is a file in the clockwork folder on your PC called flash.cfg (beware of the second file flash.cfg.txt, , if you only see "flash" and "flash.cfg" then you need to unhide file extensions)
anyway, open notepad, drag the flash.cfg file into it and you will see something like
Boot yaffs 8m
System yaffs 150m
Data allsize
(More than just that but you get the idea)
Well, if I change the 150m to 200m, save the file, run daf.exe to instal clockwork, it will be flashed with a 200 Meg system partition.
That's all there is to it.
Each line is one partition, boot, cache, system, data,, data doesn't have a size, it has allsize so will take up whatever space is left. You generally only ever alter the system.
The nand toolkit is the easier way to do it. Same principle, but point and click.
Either way, you perform this from within magldr, "USB flasher" option.
If you are on clk not magldr, I can't help, never used it.
Edit - "without adb " ... hmm, do you mean without USB? You can't.
If you are just having driver problems, there's an install drivers (or something) button in nand toolkit, try it.
samsamuel said:
When you flash clockwork, there is a file in the clockwork folder on your PC called flash.cfg (beware of the second file flash.cfg.txt, , if you only see "flash" and "flash.cfg" then you need to unhide file extensions)
anyway, open notepad, drag the flash.cfg file into it and you will see something like
Boot yaffs 8m
System yaffs 150m
Data allsize
(More than just that but you get the idea)
Well, if I change the 150m to 200m, save the file, run daf.exe to instal clockwork, it will be flashed with a 200 Meg system partition.
That's all there is to it.
Each line is one partition, boot, cache, system, data,, data doesn't have a size, it has allsize so will take up whatever space is left. You generally only ever alter the system.
The nand toolkit is the easier way to do it. Same principle, but point and click.
Either way, you perform this from within magldr, "USB flasher" option.
If you are on clk not magldr, I can't help, never used it.
Edit - "without adb " ... hmm, do you mean without USB? You can't.
If you are just having driver problems, there's an install drivers (or something) button in nand toolkit, try it.
Click to expand...
Click to collapse
Thanks mate. That's exactly the problem, I have found guides for magldr, but never for clk.
And about adb - my pc would need an OS reinstall to run well again - vista, and i already got it pretty screwed up.
Anyway, thanks for your help, I understand it more!
THIS IS NOT CWM FLASHABLE. YOU MUST USE NVFLASH
Edit: It has come to my attention that the CWM is 5.5.0.2. This error has since been corrected. Sorry folks. I'm an idiot.
Hey, i hope this doesn't bother anyone but i compilied and easy zip for NVFLAshing the new CWM.
Thanks Fosser, Team DRH, and the BishopofTechnology (all of whoms work this is, i just put it in one place)
Included is the NVflashable info, the drivers for APX, and the new version of CWM.
Do this @ your own risk, i'm not responsible for any problems (i did test it three times, with each version of CWM, if that counts for anything)
Step 1) Get into APX mode (power + Vol-) [the screen will go black. that's what you want
Here's what the Bish says:
Step 2) Connect the GTab to the PC via the USB cable.
if your PC loads the USB driver and connects to the GTab, SKIP to the “Using NVFlash” section.
if the WINDOWS PC fails to load the driver, just click through Start/Control Panel/Device Manager and find “APX” listed in the devices with a yellow “!” (exclamation point) on the icon.
Select the APX item and find the “Update Driver” button and click it.
When it asks where to search, choose the “local computer” manual selection choice and tell it to Browse to the "Flash USB Drivers".
If you go back to Device Manager after the Windows install has completed, it will show the nVidia USB drivers near the top of the USB device list.
Click to expand...
Click to collapse
Step 3) Run the "nvflash_gtablet.bat"
A CMD prompt will pop up, let it do it's thing (don't stop or unplug during). Give it about a minute or until the CMD prompt disappears. You will the get a message that says "Entering NvFlash recovery mode / Nv3p Server"
At this point is should be okay to restart your tab. I'm running Flashback and had no problems staring up.
If you want to check the new CWM, hold the power + Vol+ when restarting and it should put you into recovery.
CONGRATS! You have the new recovery in preparation for ICS.
Once again, none of this is my work--i just put it into a convenient place.
Thanks again to all the Devs and enthusiasts. You make the Gtab worth having!
Edit 1:
Here is the MD5 check: 3DD468C48A3515E6E5A1C1236FF5068E
Edit 2:
The update recovery is with the normal sized Recovery.
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED
Alright. Download tested and verified. this is deff 5.5.0.4!
sorry again folks
Anyone that is interested in installing this via CWM, I created a CWM flashable verison from fosser2's download. Here is a link to the "normal font" version http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. If you want the "big font" version, all you have to do is open the zip, delete the recovery.img, rename the Team DRM/fosser2/plastikman supplied version to recovery.zip & then add it to the zip.
I have installed this on 2 of my gTabs (one gTab Comb v3.3, the other CCCv8) and did not had any issue installing it this way.
Just a few notes on this version; it does give you the ability to flash from both the internal sd & external sd but uses a different naming convention though..."sdcard" is the name used for the external microsd slot and "internal sd" is what we would normally call sdcard. This version also appears to have fixed the "reboot recovery" bootloop bug of cwm3.0.2.8 (or aleast bypassed it)...when I selected "reboot recovery" it did the same as "reboot system now" (as I was doing this I crossed my fingers hoping it wasn't going to bootloop me...yea..no bootloop).
CWMR is touch capable. You scroll/select in 3 different ways...you can either use the capacitive buttons (which have been remapped to...Search is "select", Home is "scroll up", Menu is "Scroll down" and Back is "back"), you can also use the on screen touch controls (back, up, down & return), or you can also swipe up and down to scroll up/down and swipe sideway to select.
Al
PS:
WARNING: This is the beta6 release. The op page over in the Slatedroid gTablet Laboaratory says that selecting repartition will only repartition the EXTERNAL SD. Two users have reported magic value mismatch after repartioning with this version. plastikman, who created it says he is looking into it.
So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App
why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x
Yes but beware of repartition bug
lsu205 said:
So u can install from the older cwm that's in flashback like any other zip?
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Yes you can. I installed on both mine from CWM 3.0.2.8.
Please note the warning I put on my previous post! It probably isn't a good ides to "repartition" with this version until plastikman finds the bug. If you need to repartition (which shouldn't be very oftern) you can always flash the old CWM (or stock recovery) via this version. The recoveries are so small that I keep a copy of each on the tablet just in case.
is the download ok i have try to unzip it and it gives me an error file is not a zip file
Alternate location
wuilly said:
is the download ok i have try to unzip it and it gives me an error file is not a zip file
Click to expand...
Click to collapse
You don't need to unzip it but it does need to be a vailid zip.
Yes, the download is OK from dropbox. I just redownloaded it to my PC & tested the archive. No erors found.
I also put it on mediafire...try this link http://www.mediafire.com/download.php?qg3n084hfu783i2 & see if it's any different for you.
Al
---------- Post added at 09:23 PM ---------- Previous post was at 09:15 PM ----------
jamcar said:
why does it only boot into CWM mod now? it would boot normally when i was on CWM 3.x.x.x
Click to expand...
Click to collapse
It shouldn't (and didn't for me). Are you sure you didn't select accidentally hit "reboot recovery" instead of "reboot system now" (since you were still in CWM3.0.2.8 untill you reboot)? If you did accidentally hit reboot recovery then it would have put you in a CWM bootloop.
There are 2 ways I've used to fixed a CWM bootloop (yes I've accidentally hit reboot recovery too)..one was is to use nvflash to format partition 7 (MSC) and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery. Formatting MSC is the fastest, but most people I suggest these fixes to choose to do the stock recovery route. If you want detailed instruction for either, let me know.
Al
Great work and thanks for putting in one spot. I'll probably wait till a ICS ROM is released with but must say that this is a great first step till we get it. Cant wait for 10" of ICS....my cappy luvs ICS...
J017373 said:
Edit 3: 1) It seems this version partitions the external sd card when you choose to partition sd card. 2) choose zip from internal sdcard seems to use the internal memory 3) "FORMAT SDCARD" will FORMAT MICROSD CARD! YOU WERE WARNED
Click to expand...
Click to collapse
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
aabbondanza said:
and the other way is to use CWM to flash stock recovery and then install CWM3.0.2.8 (for b/l1.2) via stock recovery.
Click to expand...
Click to collapse
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.
Just installed using CWM recovey and all is well. Just to test I took out my external sd card and when I went to update from sdcard it showed the content of the internal. So I am guessing that if one would decided to partition there internal sdcard they might need to pull there external out first. Then boot up recovery for there updates.
rajeevvp said:
What does the recovery do when you don't have a microSD card in the slot. The /etc/recovery.fstab file is setup to fall back to using the internal SD card like CWM-4.0.1.5 is. Does it work on the internal SD card if no external one is present?
---------- Post added at 09:23 PM ---------- Previous post was at 09:19 PM ----------
That procedure only works as a side effect. Simpler to wipe MSC directly. See post #3 of this thread.
Stash that zip file on you SD card, and if you accidentally select "Reboot recovery", just "flash" it to fix the always boots-to-recovery problem.
Click to expand...
Click to collapse
Just can't keep up with you raj...why did it take you 2 months to come up with the flashable msc format? Just kidding. I got the format msc from that very thread back in October. Everyone I've run into that is in a CWM loop I've given them the option of formating msc (via nvflash) or flashing stock recovery/then CWM. In every case they have always chosen to flash stock recovery & then flash 3028 (probably because most of the people I help are pretty new to the gTab). I think now they will choose the format via flash method. Thanks for the tip.
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop? I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing). But if that is correct then why does flashing stock recovery, doing a normal boot & then flashing CWM fix the problem too (so I'm guessing I am wrong about my guess)? In any case can you explain why it works that way?
Al
When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.
nobe1976 said:
When ahead and changed back. When trying to downgrade to a 2.2 rom ended up with a mix match error on boot up. Looked good for what it is. Expecially liked the touch option on it, but it needs some work.
Click to expand...
Click to collapse
There are a couple of problems that I noticed with this version of CWM, and which might be responsible for your problems.
1. Roebeet's gtablet.cfg file which almost everybody uses to nvflash back to the 1.2 stock ROM has a bug in the system.img size calculation:
Code:
$ [B]fgrep size= roebeet.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]259715200[/B]
size=0xFFFFFFFFFFFFFFFF
The second last line is the size of the "system" partition and it is misaligned. Every other partition is correctly rounded up to end at the gTablet's NAND flash erase size (128K). Compare with bekit's gtablet.cfg:
Code:
$ [B]fgrep size= bekit.cfg[/B]
size=3145728
size=131072
size=2097152
size=131072
size=4194304
size=16777216
size=33554432
size=16777216
size=16777216
size=[B]209715200[/B]
size=0xFFFFFFFFFFFFFFFF
Here all the partitions--including the last which uses the remaining available space--are rounded up to a 128K boundary. Looks like roebeet just added 50M to bekit's system.img size without rounding it up. The correct value should've been (using roebeet's system.img size as NUM):
Code:
$ [B]( NUM=$((259715200)); echo $(( (NUM + ((1<<17)-1)) & ~((1<<17)-1) )) )
[/B]259784704
--which brings us to problem no. 2:
2. The CWM-5.5.0.4 Beta 6 has a "cmdline" file containing NAND flash partition sizes which overrides the user's partition sizes read from the Partition Table. This is fine if the sizes are the same, but, a bad idea otherwise. In this CWM, the cmdline file sets "system" to be what we calculated above (259784704) but, which disagrees with the size in the PT (259715200).
Use the zip file in the attachment to empty the cmdline file out. This will cause the partition sizes to be read from the PT on the NAND flash.
My recommendation is that:
1. Users nvflash to 1.2 using either
a) the attached gtablet.cfg which has all the partitions correctly ending at 128K boundaries or
b) bekit's original gtablet.cfg. (This option is what I recommend. The "cache" partition is used for OTA updates and if it is much smaller than the "system" partition--like in roebeet's gtablet.cfg, then, depending on the size of the image, automatic updates might fail.)
2. Install the new CWM-5.5.0.4 Beta 6, and then immediately flash the attached zip file to empty out the cmdline file.
aabbondanza said:
why did it take you 2 months to come up with the flashable msc format?
Click to expand...
Click to collapse
Didn't think adb was going to be difficult for people who have no problem with nvflash...
Just a question though. Exactly what is the CWM kernel writing to MSC to cause the loop?
Click to expand...
Click to collapse
I looked at this sometime back and its complicated. I'll make a post on this later this weekend after I've looked at VS's newly posted 1.2 kernel patch.
I assume it is the bootloader that checks for the rocker switch position & some mysterious bit on MSC to determine which kernel to load (but I'm just guessing).
Click to expand...
Click to collapse
For "mysterious bit" substitute "string", but, you are correct.
Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al
CWMR5504 Fixed
aabbondanza said:
Have a user over at slatedroid tried it & still got this error.
Magic value mismatch
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002)
Trying to get more info on exactly what he did to get the error.
Al
Click to expand...
Click to collapse
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al
aabbondanza said:
Thanks to rajeevp!!
Plastikman verified rajeevvp was correct and has issued an updated CWMR. Here it is in a flashable format http://dl.dropbox.com/u/36150173/CWMR5504_recovery.zip. He switched from using pershoot's kernel (which required the command line) to using the stock kernel. I tested the new version to install a rom, do a factory data reset, a wipe cache, a wipe dalvik & a fix permissions. All worked normally. Give it a try. I also corrected the links in my previous posts to point to the updated version.
Al
Click to expand...
Click to collapse
Thank you. This worked well for me, since I was not inclined to do the nvflash thing. I was able to boot back into my Beasty+Clemsyn rom without incident. Tested by rebooting again and was able to boot into the rom with no issues.
aabbondanza said:
He switched from using pershoot's kernel (which required the command line) to using the stock kernel.
Click to expand...
Click to collapse
... and in the process also brought back the always-reboots-into-recovery problem, right? Whereas with the pershoot kernel "Reboot Recovery" would just reboot the tablet into the ROM?
BTW, the pershoot kernel doesn't need a cmdline file: craigacgomez's CWM-4.0.1.5 too has a pershoot kernel and its cmdline file is empty. As I mentioned before: if the cmdline file is empty, then the bootloader will construct a cmd line for the kernel.
to install the cwm recovery do I simply transfer the zip to the internal sdcard and flash zip from sdcard as if it were a rom?
Hello, am new here so if I did something wrong please correct me OK
-presentation:
we all love running latest android versions and install big a** games like asphalt 8 and have all the Google apps that we love
But in Janice it's some kind of impossible to do all of that ( come on its only 4 years old!!)
As they say no impossible under the sun now you can easily increase system or data or what ever partition your want just by flashing a Lil file and without losing a single file
-Warning:
Me and XDA are not responsible for any soft hard leaks or what ever you are doing this by your self!!!
Make a full backup(system data boot) before starting..
DO NOT USE THIS FILE WITH ROMS THAT USE CACHE (CM10.2)
-Requirements:
1. Janice or Janice-p(not tested)
2. TWRP Recovery (Any Version)
3. The attached file
Instruction:
1. Download the repartition file
-rename the file with your favorite partition sizes like "lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip" which means 1gb system 2gb sdcard and the rest will go to data partition so you will be able to install more apps
2. Boot into TWRP and make a backup
3. Flash the repartition file of your desire
4. Take a nap or watch big bang theory just waste some time
5. When the script finish restore your backup and reboot
6. Enjoy your games or what ever
-Credit:
1. @Lanchon
2. @madkita
If you want a file with your own sizes just write or in comments and i'll do my best to offer it to you
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=0.0625+wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add '+wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Lanchon said:
hi,
thanks for the guide! a couple of comments:
1) i suggest people get REPIT from its main site:
https://github.com/Lanchon/REPIT
the files posted here are already very old, i've updated REPIT several times.
also, i only provide support for the latest version. older versions are unsupported.
2) if you download the files from here, they will not work.
(XDA messes with the filenames changing = for -)
3) you don't need to backup anything unless you want to revert the flashing of the kernel.
4) you don't need to flash any particular kernel to run REPIT, you just need a recent TWRP build.
5) TWRP with gparted is not needed anymore: REPIT now bundles gparted and other tools.
6) the configurations proposed here are incorrect. you should use:
a) if you want 3GB data and rest as internal sdcard:
-system=1.0-data=3.0-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=max.zip
b) if you have an external sdcard, and want 6GB data and a very small internal sdcard:
-system=1.0-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=0.0625 wipe.zip
then your internal sdcard will be useless. so you need to swap internal and external sdcards as detailed here:
http://forum.xda-developers.com/gal...ment/mod-internal-memory-repartition-t2863629
these configurations will keep contents of system and data. if you don't care about their contents, configure wiping (add ' wipe') for those partitions and REPIT will repartition much faster then.
7) read REPIT manual before using!
https://github.com/Lanchon/REPIT
Click to expand...
Click to collapse
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
madkita said:
Thus settings are right this is the same file I used and it worked perfectly and I told you I created this threat for noobs who can't understand github and there download section is not working for me it says "try again in 30 minutes" that's why I use old files
Click to expand...
Click to collapse
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Lanchon said:
lol no, without the '-sdcard=...' specifier those files won't work, trust me.
Click to expand...
Click to collapse
Yeah thank you updated OP
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
TheSteve87 said:
first of all thank you both
just to be sure, i have a couple of questions:
- how much space does a full backup take?
- what is the limit to the repartition? right now i'd like to add one gigabyte to system for apps, which numbers do i need to write in the zip name?
- what does the "wipe preload" and "wipe fota" strings do?
Click to expand...
Click to collapse
In TWRP it will be around 500-600mb with compression
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice.zip
Just rename the file to this and your will have 1gb system 2gb SD card and the rest well go to data if you want to edit a partition size for example the number 1 after system means the system will be 1gb and the number 2 in front of SD card means the SD card will be 2gb and max in front of data means the rest well go to data partition
Preload and fota are partition used in only stock ROMs and stock based ROMs so if you are running a custom ROM this will give you more space in the partition your set to max
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
TheSteve87 said:
i just did everything but i'm not sure it worked
i used this name for the flashable zip
lanchon-repit-20160317-system=1-data=max-cache=0.03125 wipe-preload=min wipe-fota=min wipe ext4-sdcard=2-janice
but in system info it still says that data is 3.91GB, and i have 1.84GB for SDcard
maybe i should have gone further and give 3GB to SDcard?
Click to expand...
Click to collapse
Yup it works if your wanna check system download a small app called disk info
If you want 3gb on sdcard change the 2 number in front of it this will give you 2gb on data
DaksAnkit said:
thanks to both devs, i have one question is it compatible with cm13 ?
will i be able to re-size F2fs or i need a EXT4 to use this tool .
Click to expand...
Click to collapse
Yup 100%
Make a backup first and when resizing all partitions will be formated to ext4 then restore your backup it will automatically format them to f2fs
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
DaksAnkit said:
ayt man thanks , trying it right away !!
edit : getting error 1 in twrp 3.0.0 on cm13 rom I THOUGHT IT WAS compatible with repit , as said on the GITHUB
also i tried flashing zip from github page of lanchon , that zip also did not worked it said something like couldn`t find meta-inf lanchon REPIT.
??? where did i went wrong i just flashed the zip from twrp it did nt worked i moved the file to /tmp then tried there also same error .
Click to expand...
Click to collapse
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
madkita said:
Cm13 recovery doesn't have parted script you have to use the recovery I provided in first post just follow it
Click to expand...
Click to collapse
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
also so i have to now restore my backup to get back to cm13 coz i am stuck at recovery ? any shortcut,like(flashing cm13 kernel) to go back to system as it was before or i have to restore the backup ?
DaksAnkit said:
nope , it says error 1
invalid partition configuration ,.. sdcard : sdcard=max.zip
i flashed the kernel then renamed the file attached to ..
-system=1.0-data=3.0-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max.zip
something is not right can you please help , i would like to have 1 gb system n 2 or 3gb in data partitions correct me if i am wrong if the size configuration is wrong ?? what should i do.
Click to expand...
Click to collapse
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
madkita said:
Use this and don't miss with it
lanchon-repit-20160317-system=1-data=2-cache=0.03125+wipe-preload=min+wipe-fota=min+wipe+ext4-sdcard=max-janice.zip
Click to expand...
Click to collapse
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i just install my backup and that is it ? right !!
DaksAnkit said:
Thanks man , i sorted it out the problem was silly , i had checked option in windows to
HIDE EXTENSION NAMES OF KNOWN FILE TYPES , so i was just copying and the .zip kepton adding twice
.zip.zip and that is what was happening anyhow the device has started reparting , so one last question after when this process is over , i ust install my backup and that is it ? right !!
Click to expand...
Click to collapse
Yup just restore your backup and you're done ?
madkita said:
yup just restore your backup and you're done
Click to expand...
Click to collapse
alrighty then !!
:good:
I`ll post how did it go later in the thread .
you have a good day bro enjoy sunday .. cheers
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
TPD-21 said:
Can someone here confirm that the kernel cm12.1 (OP) can be installed in the latest CM11 ROM by epirex? And if repit could work after 12.1 Kernel installed in CM11 ROM? Thanks in advance.
Click to expand...
Click to collapse
First make a backup with your cm11's kernel then flash cm12.1 kernel then flash the script and the kernel doesn't t care about your current rom so it should work every where