I just repackaged Raver's latest valhalla black as a heimdall oneclick file. Should automatically convert your /system partition ext4 too!
If you want to test this out for me I'd be grateful. I already flashed it myself and it worked out fine. This should help whoever is having issues (most likely caused by not formatting their partitions before the flash)
TESTING DONE. Download link gone.
I'll try it later on,
but just a quick question though:
in the:"About the ROM" section it is listed as:
"Official KJ6 With bhudven's Kernel
Gingerbread 2.3.6"(which I guess comes from the firmware.xml file) - is that on purpose?
isn't it suppose to be Valhalla Black or something
Again 10x
Alon
Oh yes, that's not on purpose, I left it in the firmware.xml file and forgot to edit it, but I did place the correct (valhalla black) files into the oneclick.
FBis251 said:
I just repackaged Raver's latest valhalla black as a heimdall oneclick file. Should automatically convert your /system partition ext4 too!
If you want to test this out for me I'd be grateful. I already flashed it myself and it worked out fine. This should help whoever is having issues (most likely caused by not formatting their partitions before the flash)
http://sourceforge.net/projects/teamacid/files/fb/roms/one_clicks/valhalla-black-rc3.2-One-Click.jar
Click to expand...
Click to collapse
I'll give it a go this morning.
As soon as I update my TB backups and run a nand.
I'm not having any issues at the moment, well, none related to the phone/rom anyway... so not sure I'm a good test subject...
Did you add the gps fix in? or does it need flashed after?
Well it's just a repackaged version of 3.2, so it should work exactly the same, just need to make sure it installs correctly on other people's phones.
Nope, no gps fix in there.
Downloading now; will let you know as soon as I'm done.
-- Update --
I rebooted my phone into CWM & disabled voodoo
booted into download mode & ran the one-click without issue
Phone rebooted itself and immediately Linda began converting partitions
Linda said "Voodoo lagfix now disabled"
Standard recovery appeared:
* Successfully installed package.
* -- Deleting files...
* Successfully deleted files.
* -- Updating filesystem...
* verifying the filesystem. please wait.
* already updated filesystem. finished
* Successfully updated filesystem.
* -- Wiping cache...
* Formatting cache...
* E:format_volume: rfs format failed on /dev/block/stl11
* Cache wipe failed.
* -- Appling Multi-CSC...
* Installing Multi-CSC
* Can't access to '/system/csc/TMB/system/'.
* Successfully applied multi-CSC.
Selected 'reboot system now'
Waiting on it to boot, then waiting some more
-- Update #2 --
When it booted and it came up to the Google setup, I had no data connection. I had to set up wi-fi to get through the process. Seems the APN was missing.
-- Update #3 --
/system is mounted rfs, not ext4.
Maybe I did something goofy to make all of that happen? I've never had my APN disappear before.
stephen_w said:
Downloading now; will let you know as soon as I'm done.
Click to expand...
Click to collapse
Yea... what he said...
---------- Post added at 12:48 PM ---------- Previous post was at 12:33 PM ----------
FBis251 said:
Well it's just a repackaged version of 3.2, so it should work exactly the same, just need to make sure it installs correctly on other people's phones.
Nope, no gps fix in there.
Click to expand...
Click to collapse
Ran okay, heard Linda zapping things...
then it booted into stock recovery
got the following:
installing update...
Successfully installed package.
--Deleting files..
Successfully deleted files.
--Updating filesystem
E:failed to mount /data (invalid argument)
E:discard_filesystem_for_rfs:Can't mount /data
--Wiping cache...
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Cache wipe failed.
Appling Multi-CSC (Note that's not a typo on my part, it says Appling)
Installing Multi-CSC
Can't access to '/system/csc/TMB/system'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
Rebooting now, it didn't boot itself.
Update: No data connection
Booted back to CWM recovery, Mounts were UUUU -couldn't change them
W
Hmm odd. Well thanks for testing I'll take down the link since Raver posted the latest version now. I'll probably look into this again once he releases a final.
FBis251 said:
Hmm odd. Well thanks for testing I'll take down the link since Raver posted the latest version now. I'll probably look into this again once he releases a final.
Click to expand...
Click to collapse
No problem... I ended up jumping through a few hoops and just flashed rc3.3.
Was going to make sure it was good and then rerun the one-click...
This is the first one-click I have had any issues with, didn't get a chance to log any of it though... I'm at the office, so limited on what I can get my hands on directly...
Core618 said:
No problem... I ended up jumping through a few hoops and just flashed rc3.3.
Was going to make sure it was good and then rerun the one-click...
This is the first one-click I have had any issues with, didn't get a chance to log any of it though... I'm at the office, so limited on what I can get my hands on directly...
Click to expand...
Click to collapse
I kinda threw it together. I dumped the /system partition and threw that in with the rest of the KJ6 stock Odin files into a Heimdall package. Technically it should work even though the partition itself was dumped as ext4 not the traditional rfs that is used in Odin packages.
FBis251 said:
I kinda threw it together. I dumped the /system partition and threw that in with the rest of the KJ6 stock Odin files into a Heimdall package. Technically it should work even though the partition itself was dumped as ext4 not the traditional rfs that is used in Odin packages.
Click to expand...
Click to collapse
Weirdness. I appreciate your continuing efforts into making things easier to do and manage with this phone.
FBis251 said:
I kinda threw it together. I dumped the /system partition and threw that in with the rest of the KJ6 stock Odin files into a Heimdall package. Technically it should work even though the partition itself was dumped as ext4 not the traditional rfs that is used in Odin packages.
Click to expand...
Click to collapse
why didn't you factory reset, clear cache, clear dalvik, and dump all of it?
Sent from my SGH-T959V using XDA App
Bassmanjames said:
why didn't you factory reset, clear cache, clear dalvik, and dump all of it?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
There's no need to dump /cache or /data since they get formatted when you do a factory reset anyway. It's only the /system partition that matters.
FBis251 said:
There's no need to dump /cache or /data since they get formatted when you do a factory reset anyway. It's only the /system partition that matters.
Click to expand...
Click to collapse
Exactly my point. couldn't you use the "empty image". I have extracted the stock images for data and cache and both contain files. I would think that with all the tw dependencies that raver has removed it is somehow interfering.
Sent from my SGH-T959V using XDA App
Bassmanjames said:
Exactly my point. couldn't you use the "empty image". I have extracted the stock images for data and cache and both contain files. I would think that with all the tw dependencies that raver has removed it is somehow interfering.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I'll keep that in mind when I make the next one. Gonna wait until a stable version is out. Very possible to make it happen though since we could just fill up the partitions with a huge file from /dev/zero just to zero out the blocks and make the images compress well.
I have a personal backup that I made and I converted to rfs before the dump. If I use it and my system was rfs it auto converts to ext4 on first boot. I think it is because the kernel is set to ext4 by default. Something else to keep in mind.
Sent from my SGH-T959V using XDA App
Bassmanjames said:
I have a personal backup that I made and I converted to rfs before the dump. If I use it and my system was rfs it auto converts to ext4 on first boot. I think it is because the kernel is set to ext4 by default. Something else to keep in mind.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
There's a a directory /sdcard/Voodoo/ that has files that tells the kernel to convert.
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
I've been running CM7 for a month or so and I started having some stability problems. So I decided to try DarkyRom.
I did everything like normal (used heimdall).
Upon boot it had an error.
Failed to mount /efs while applying multi-csc.
I'm dead in the water. I tried to flash back to stock. I get an error and thrown into samsung recovery. I can reboot from that and I boot to the gui with no radio. Phone info says "Unknown" Hardware and Baseband Version.
No. I did not backup any EFS (news to me). I do have access to the same model phone, my son has one he just uses as a fancy MP3 player (no phone/data plan).
Is there anything I can do? I did use the ADB Shell and ran "mount" to see if the EFS was mounted. It was a negative...
-MT
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
mainethoughts said:
Could this have something to do with the file system?
I don't have CWM working. I'm going to work on that. Right now I juast have Samsung Rec. Utils. The error that is in there is:
E:Can't mount /dev/block/mmcblk0p1 (Invalid argument)
Click to expand...
Click to collapse
First off,are you even on the right forum? Darky rom isn't built for this phone so it's not going to work.
Sent from my SCH-I500 using XDA App
Ugh...an unfortunate response. Yes...I'm on the right forum.
I did make a CWM backup from a couple weeks ago. Not sure if that helps.
mainethoughts said:
Ugh...an unfortunate response. Yes...I'm on the right forum.
Click to expand...
Click to collapse
Them why are you flashing roms from other forums/phones? Use odin and check repartition.
Sent from my SCH-I500 using XDA App
*hangs head* Admonishment accepted. I really don't know what I was thinking.
Here is my progress. I tried using Odin to just Re-partition. No go.
<ID:0/003> Can't open the specified file. (Line: 1455)
So then I downloaded stock EC10 (That was factory on my phone). I flashed that via Odin with "Success".
The same error as initially posted was on the phone. I rebooted from the stock recovery console and I was able to boot. 3g works. The hardware and baseband are now accurate. I'm getting a lot of force closes however. The twlauncher is constantly crashing.
So now the phone is semi-functional but there are still errors. (I was getting more forces than normal in CM7 that caused me to dive into this process in the first place).
I could be way off base but I'm thinking that possibly there is corruption (or wrong file system?) problems with the internal SD (I did format the External SD at the start of this).
I appreciate your help. Any suggestions from here?
-MT
Additional Note: Settings are not saved between reboots.
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
mainethoughts said:
-Rooted
-Installed ROM Manager
-Installed CWM 3
-Reboot into Recovery Mode
No go. Same /dev/block/mmcblk0p1 error (installation aborted)
The 3e recovery also says:
"your storage not prepared yet, please use UI menu for format and reboot actions."
I tried both wipes. Errors.
Click to expand...
Click to collapse
Use the full odin restore package and make sure you use pit and pda files. Repartition must be checked. Wiping data might be a good idea as well.
Sent from my SCH-I500 using XDA App
I would odin the full mesmerize package EE19. http://forum.xda-developers.com/showthread.php?t=881064
That is what I have already done I believe. Followed instructions from:
http://forum.xda-developers.com/showthread.php?t=881064
-MT
If you've done that, then i'm at a loss. That usually is my solve-all solution... Sorry man.
Thank you much. Is it possible that I could have a faulty internal SD? I had suddenly started getting a lot of force closes in CM7. I guess I'm just wondering if I'm fighting two separate issues here. (My bonehead move vs. a real problem)
-MT
I think I'm FIXED!
I was finally (I don't know how) able to get Odin to Flash CWM 4 (The Blue one needed to install CM7).
I got ZERO errors in CWM. So I took the opportunity to clear caches, format data...I got destructive.
I then installed the CM7 Rom. -SUCCESS
Installed GAPPS - SUCCESS
I hope everything is OK at this point. I know CM7 is booting in about 20 seconds opposed to 5 minutes like it was before I decided to try to morph my phone into an I9000.
I actually saw the black screen with the little phone to PC icons at one point tonight. I think I came real close....
Thanks for your help!
PS: CONFIRMED mmcblk0p1 is mounted! (EFS, etc) PHEW!
I had this happen to me right after a Odin even did the rfs formatter tool exact same problems not saving settings upon reboot and it saying something along the lines of process.android.blah blah blah and double vibrate when booting before the fc anyhow I just reflashed miui to get cwm4 wiped everything reflashed cm7 no probs since
Sent from my SCH-I500 using XDA App
Does anyone have tips on extracting RFS images on a Linux box?
So far everything I've found on extracting RFS images indicated to either:
1) Use MagicISO/PowerISO - these are proprietary Windows tools, I'd prefer not to have to reboot or move to another machine
2) Mount it as a VFAT filesystem - this didn't work for me last time I tried it
Any other suggestions? It's not something I usually bother with as I'm almost always doing kernel work or working with already-extracted userland filesystems, but with all of the AT&T Gingerbread leaks coming out I'd like to be able to analyze these without waiting for someone to CWM it up.
Mount it as loop.
http://forum.xda-developers.com/showthread.php?t=751827
LinuxBozo said:
Mount it as loop.
http://forum.xda-developers.com/showthread.php?t=751827
Click to expand...
Click to collapse
That's what I tried before (see 2) above) - didn't work. Tried both autodetect and forcing vfat.
Maybe just that particular RFS image (was one of the ones from gtg's Ultimate Unbrick packages) was wonky... Will try again tonight with I3/I4.
Works Here (TM) ;-)
LinuxBozo said:
Works Here (TM) ;-)
Click to expand...
Click to collapse
Weird. Whatever RFS image I was trying to mess with last time around must've been mangled... UCKI3 mounts fine.
i missed this thread, i was messing with the kk1 leak and wanted to create a rooted package without flashing it rooting and dumping it, problem is i cant set permissions when i mount the image to a loop. i can read and write but i cant change the permissions of su to 6755 or antthin other than 0755 it just says operation not permitted. i tried to fdisk the loop and turn off dos compatibility mode which seemed to cause issues on my flash drive, though it might work but it wont stick.
any suggestions from the local gurus? im sure the fix is simple but from how much time ive spent on it it might make more sense to flash it root it and dd the rooted /system partition
Dani897 said:
i missed this thread, i was messing with the kk1 leak and wanted to create a rooted package without flashing it rooting and dumping it, problem is i cant set permissions when i mount the image to a loop. i can read and write but i cant change the permissions of su to 6755 or antthin other than 0755 it just says operation not permitted. i tried to fdisk the loop and turn off dos compatibility mode which seemed to cause issues on my flash drive, though it might work but it wont stick.
any suggestions from the local gurus? im sure the fix is simple but from how much time ive spent on it it might make more sense to flash it root it and dd the rooted /system partition
Click to expand...
Click to collapse
You can't really do anything but read only operations from vanilla linux because while RFS is VFAT under the covers, there are other things to it. Writing to it once mounted as loop will cause havoc. You would have to actually have RFS driver in the kernel to do anything other than read operations. Which means, mounting as loop on your phone, or getting RFS into your own linux kernel (not gonna happen, since it's closed source)
LinuxBozo said:
You can't really do anything but read only operations from vanilla linux because while RFS is VFAT under the covers, there are other things to it. Writing to it once mounted as loop will cause havoc. You would have to actually have RFS driver in the kernel to do anything other than read operations. Which means, mounting as loop on your phone, or getting RFS into your own linux kernel (not gonna happen, since it's closed source)
Click to expand...
Click to collapse
Ok so if I wanted to release an Odin package it would mean dumping it from my phone then. Gotcha!
Thanks.
The Goal: To create a CWM flash-able .zip that will convert a BML formatted phone to MTD without the need to be included in a rom, creating a standard and simplicity for end-users.
RDU
ROM DEVELOPERS UNITED
AS ONE
CWM BML to MTD Conversion Utility​Supported ROMs:
- Any BML Setup
So here's how it works:
This file will convert your phone's kernel and boot recovery to MTD. Afterwards, you will be able to flash an MTD rom.
ALWAYS make a backup of your data before flashing anything.
If you flash this over an already MTD rom, it will simply abort.
The Latest Version Here. After it finishes, your phone will be stuck in a loop. Pull the battery and 3-finger back into recovery to flash an MTD rom.
UPDATE: (--/--)
Further ideas or customizations from fellow rom developers welcome.
First
This sounds vary usefull on my firends Epics. I think it will speed thing up for me at times depending what they want
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
zman519 said:
First
This sounds vary usefull on my firends Epics. I think it will speed thing up for me at times depending what they want
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
Click to expand...
Click to collapse
Please note, this is a test version.
It's based on a version I used myself, but being on MTD, I can't test it easily.
There are 3 current scenarios it could yield:
1. Nothing happens.
2. It works perfectly.
3. It works, but puts the phone into a bootloop. This is what the old version did to me... Pop the battery. Boot into recovery. Profit.
So this would theoretically convert a BML ROM to MTD on a person's phone. Sounds great.
As a note to all remember as always to back up before flashing ANYTHING.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
So this would theoretically convert a BML ROM to MTD on a person's phone. Sounds great.
As a note to all remember as always to back up before flashing ANYTHING.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Right now it should format your phone and prep it for a Rom. If it works properly, I'd like to rewrite it to convert and PRESERVE a BML Rom into an MTD Rom.
RandomKing said:
Please note, this is a test version.
It's based on a version I used myself, but being on MTD, I can't test it easily.
There are 3 current scenarios it could yield:
1. Nothing happens.
2. It works perfectly.
3. It works, but puts the phone into a bootloop. This is what the old version did to me... Pop the battery. Boot into recovery. Profit.
Click to expand...
Click to collapse
I understand ;-)
If my budy ever gets a new sdcard, I'll use his phone as a test dumey. The worst that could happen is I have to bust out the usb cable & fire up ODIN
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
Ok so currently no data or apps are preserved. It is mostly a blank MTD slate?
Sent from my SPH-D700 using xda premium
kennyglass123 said:
Ok so currently no data or apps are preserved. It is mostly a blank MTD slate?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yup. I need someone to confirm that it works properly. As I mentioned, I previously used a simpler version to convert myself to MTD and it worked, but it put me in a bootloop. I'm hoping to solve the bootloop so I can create a version to preserve a setup.
RandomKing said:
Yup. I need someone to confirm that it works properly. As I mentioned, I previously used a simpler version to convert myself to MTD and it worked, but it put me in a bootloop. I'm hoping to solve the bootloop so I can create a version to preserve a setup.
Click to expand...
Click to collapse
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
Because formatting destroys the existing file structure (it doesn't actually erase files, just overwrites the data that maps out the locations of those files), everything would need to be copied to a temporary location before converting the original location to the new partition type. Then the temp data (backup) would need to be copied back to the original location using the new format.
It is not possible to just change the format while leaving the data in place - those warnings on every format command (in every computerized device - windows, mac, etc) were not a design decision, but a result of a design limitation. The backup/format/restore method is the only way.
flastnoles11 said:
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
Click to expand...
Click to collapse
He also said he was trying to solve the boot-loop problem, not a formatting problem. The clarification was not to assert that the formatting worked - the focus was on explaining the cause of the boot loop, to point out that there is no problem to be solved there because a BML kernel should boot loop when the rest of the partitions are freshly formatted MTD partitions.
The standard BML kernel can't read MTD, so the fact that those partitions are empty is irrelevant. Even if the partitions were converted without data loss (via a backup/convert/restore), the kernel would still need to be MTD-capable (so this by itself will not convert a BML rom to MTD)
Hopefully this clears up some of the confusion...
Sent from my SPH-D700 using XDA
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
A kernel that supports MTD and copy all system, data and cache folder then paste it back after the conversion with the new kernel.
Sent from my SPH-D700 using xda premium
flastnoles11 said:
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
Click to expand...
Click to collapse
Yes he did. I too read his reply.
My response to Random was that since he's put in the bootloop, then it worked for him due to the lack of converting the rom over. Therefore my reply implied that testing more won't hurt anything at all and would be good protocol, but may not be needed since it worked for him given his output.
styles420 said:
Because formatting destroys the existing file structure (it doesn't actually erase files, just overwrites the data that maps out the locations of those files), everything would need to be copied to a temporary location before converting the original location to the new partition type. Then the temp data (backup) would need to be copied back to the original location using the new format.
It is not possible to just change the format while leaving the data in place - those warnings on every format command (in every computerized device - windows, mac, etc) were not a design decision, but a result of a design limitation. The backup/format/restore method is the only way.
Click to expand...
Click to collapse
Ahh yea, I wasn't 100% sure if this was the case. Good breakdown though.
Doesn't seem to be working, I'll be uploading the version I use later on with directions.
I understand the theory, prepping a 100% BML setup for it's MTD future; just out of curiosity, Q: would there be a way to reverse this process so that if you arrive at your destination MTD ROM + change your mind, would it be possible to choose to convert an MTD ROM back to BML w/out having to ODIN (md5.tar + pit...........the way we do currently)?
BTW, am looking forward to testing your proposed conversion utility, just wondering.
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
All I know is that it'd need an mtd kernel. Also, maybe it could work like rfs to ext4 where it backs everything up then restores and flashes an mtd compatible kernel. Theoretically, that should work on samsung tw based roms.
Sent from my SPH-D700 using XDA
Randomking, to fix the bootloop issue, try having it reboot recovery like the cm/miui mtd install scripts do (I think).
Sent from my SPH-D700 using XDA
sonarchist said:
I understand the theory, prepping a 100% BML setup for it's MTD future; just out of curiosity, Q: would there be a way to reverse this process so that if you arrive at your destination MTD ROM + change your mind, would it be possible to choose to convert an MTD ROM back to BML w/out having to ODIN (md5.tar + pit...........the way we do currently)?
BTW, am looking forward to testing your proposed conversion utility, just wondering.
Click to expand...
Click to collapse
Not possible since BML is proprietary. Odin is the only way to get this top secret partition information on our phone.
Sent from my SPH-D700 using xda premium
Thank You!
Edit
NVRMIND
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .
I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium
rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system
rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium
Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.
I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition
I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.
can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you