Related
I had an odd thought. A lot of us like to test out other ROMs, but NANDROID backups and restores result in significant downtime. I'm curious if it would be possible to nest a fully installed ROM inside a subdirectory of the current running one and then swap them out in Recovery by rewriting the pertinent directory paths.
Obviously, there would be a requirement that both ROMs be compatible with the file system in question (Ext4 , etc.)
I mention all this because I would like to be able to quickly boot into Cyanogen 7 every now and then for the bluetooth stack and some of the other features here and there, but my daily driver is Bionix.
Obviously, a nice chunk of space would be "wasted" having duplicate copies of lots of files for apps and such (in addition to the space used having a second ROM) but I think the Galaxy S series NAND space is sufficient to try something like this.
Holy crap that's an amazing idea!!!
Theres already a way to do this its called dual booting and uses your internal memory.
Complicated though.
Are there any guides?
Yes, their in the android section (lol)
http://forum.xda-developers.com/showthread.php?t=847423
work in progress.....close to alpha release
Aww I thought it could already be readily available .
Nice though can't wait .
edit nevermind
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab
As of you guys have found out there has been a few threads that have been started that throw around theories about getting CWMR to work and such and I'm here to finally give you guys the progress from the dev that's working on it.
I have been working on getting CWMR working off and on for a few months now to some avail. I have been slowly testing it and sending out alphas to people on the IRC and now I'm here to tell you where I'm at and what has been accomplished.
Part 1: Getting into CWMR
I started working with our current bootstrap recovery as a base for CWMR. It was of course in charge mode, but it was a step that had to be done first. I got a hold on a CWMR binary and after a bunch of shell commands managed to get the mangled version of CWMR that we've seen before. From there I had the idea to inject the ATRIX binary into the recovery and try it from there. It was a big success and I could use some (very few) of the functions that if offered. But I was finally in CWMR on the X2. (I posted the picture on my twitter).
Part 2: Making the Functions Work
From here the first thing I decided to do was to get the "Fix Permissions" script working. By getting this to work I know I could place my own code in there that will log to the file that I could open up and see whatever I wanted as ADB didn't work YET (more on that later). I fiddled with it a bit and got it working.
This also allowed me to access the log and find out why the unmounting and formatting wasn't working either. This was due to an issue with the mke2fs and other complementary binaries not being appropriately compiled for our phone. As I was working on CM7 at the time, i had access to the sources of these and to the recovery binary as well. I decided to build a recovery binary that was tailored to our phone and not the ATRIX and the binaries that handle formatting partitions, etc. These worked on some partitions I could wipe data and cache properly by reformatting, I could easily erase a partition at will except for one: /system.
Part 3: Getting /system Formatted (WIP)
At this point I decided to find out why /system could never be formatted. When a partition needs formatting it must be unmounted first. But I could never unmount /system. By using the logs I found out that the partition was still in use. By using the "Fix Permissions" script, I managed to find that a lot of daemons (aka services) were being ran from the /system sub directories. This meant that in order to format, I had to have them not running. Easy enough as there's a script in CWMR that allows us to kill certain processes before the new recovery starts. I decided to kill all of the services with this script but found that the display would go blank. From there I found that two services are REQUIRED to be running on the phone for drawing (making things show on the screen) to take place: servicemanager and nvrm_daemon.
The servicemanager does exactly what it's title says: it manages the currently running services. This has to be running to keep nvrm_daemon running or else things get kinda freaky.
nvrm_daemon is what is used to manage drawing commands to the screen (the nv stands for nVidia which is who made the Tegra 2). With this service running I was able to (while in charge mode still) draw to the screen and show all of the menus for CWMR.
This created a problem. As these HAD to be running /system could never unmount because they were in there. Unless we used 2nd-init. From here I created my own hijack script that allowed me to copy over the necessary daemons into /sbin (which is just a sub directory of the rootfs). Then by using a new init.rc I could start these daemons from /sbin and see if they worked for CWMR.
After a lot of coding I managed to get the daemons running from /sbin and I thought I was free from there. And while I was at it, I might as well tried to get it out of charge mode.
Part 4: Untethering the Recovery (WIP)
I figured that since I was using 2nd-init anyway that I might as well have been working on trying to get it untethered also. After a bunch of looking into why charge mode was the only way to get it working, I found that before charge mode was started the init.rc started the "pre-zygote" services. These include usbd (the usb daemon), battd (the battery daemon), etc. What was also started was nvrm_daemon (another proof that we needed this running) to draw on the screen (charge mode draws the battery indicator to show charging progress).
I decided to move to mot_boot_mode to do the hijacking. I eventually managed to get things running but it still wouldn't draw to the screen. A look at the logs showed that for whatever reason we still didn't have access to the framebuffer (the memory space aka buffer that is drawn to the screen). I was tired of rebooting over and over again to get results and by now I had SBF'd I don't know how many times, only to not be able to access the logs due to a wipe. So next thing I decided was to get ADB working at boot.
Part 5: Starting ADB at Boot (The Short Version)
I took a look through the init.rc and found that Motorola had disabled the default way to get ADB working at boot. Through a bunch of digging I found that I could re-enable the method but it started usbd also (yet another daemon I'd have to move and thus more time, etc.). But eventually I found another property (aka system variable) that i could set that would start ADB without having usbd started: persist.adb.enable_NV_DISABLED. Setting that to 1 started ADB whenever I wanted it to. This allowed me access to the system (as root actually) without having to reboot and try to get into logs and whatnot. I could see everything that was running, mount/unmount and do everything I normally could and see better why they were failing.
Part 6: Recent Discoveries (as of 1/3/12) On the /system Unmount
I decided that I was going to go back to charge mode for now. After causing too much pain with framebuffer access I decided to look into why /system STILL wouldn't unmount after moving everything out of there. With the help of mastafunk and DrPenguin I was able to get a hold of a program named strace. This allows you to debug what binaries are doing down to pretty much every comparison, file opening, memory mapping, etc. I had found that nvrm_daemon (although started from /sbin) was looking for and loading drivers found in /system/lib. This was a problem and I thought that we may never get /system unmounted. Until I found out one other thing.
The nvrm_daemon doesn't look for the drivers inside of /system/lib first. It looks for them in /vendor/lib first and then if it can't find them, goes to /system/lib. So simple enough. I thought I could just make a /vendor/lib directory, copy the libs over and have them load from there. Well it's not that simple as there is already a file in the rootfs named vendor. But the file is a symlink to /system/vendor so if it looks at /vendor/lib it really looks at /system/vendor/lib. I thought I was stuck again until I took a closer look at the /system directory. There is no ./vendor sub directory in /system. That being said, I was able to delete the symlink in the rootfs and then create a /vendor/lib directory copy over the libs to it and nvrm_daemon successfully loaded the libs from there and not from system.
Conclusion
You are now caught up on when we've basically done to try to get CWMR working on the X2. Being that we're the only Tegra 2 phone from Motorola that is locked, we're kinda stuck trying to get things working. For now I consider this progress. Albeit slow progress, but progress none the less. If you took the time to read this, I hope you now understand the frustrations I've had to deal with this. All the while trying to help masta get 2nd-init fully working for our phones.
Thank you.
Thank you very much for the detailed explanation - well written so that even a novice like myself could understand your progress and frustrations. Thank you to you and your peers also for your hard work and determination to see this through. I think I can speak for all X2 users and say this is most appreciated!
Great writeup. Very informative. Thank you for your dedication.
I thought 2nd init was done and masta was working on aosp? I mean we can log from our new init.rc so it is using it. In the meantime i've been working on my barebones so we can get new blood using 2nd init and because I want a decent daily driver in the event we cant get stuff going.
To echo what others have said, thank you very much for the information. This kind of transparency is always very much appreciated when there's some spare time to put that out there. It not only is really helpful to make it understandable, but it's nice to know that these projects are still active.
Perhaps most importantly though in the context of potential progress: having specific information is a great way for knowledgeable people reading to recognize if they might be able to help out in certain areas. You might get some fresh ideas from people who hadn't considered themselves familiar enough with the situation to be useful. Who knows.
Anyways, thank you very much again. It's very encouraging to hear progress reports in general, not to mention ones like this that involve so many successes.
Wow thanks so much for your hard work and dedication can't wait until you conquer this sounds like you are closer then ever
Sent from my DROID X2 using XDA App
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
skwoodwiva said:
I am so glad to hear the "behind the scene" drama. Thank You DK sharing. I AM sorry for what bad drama I may have started. Will you forgive me?
Click to expand...
Click to collapse
No need to appologize man... Stuff like this should have been posted or known. To be honest, I thought Masta was finishing 2nd INIT and starting to work on getting AOSP running and CWM was out the window, thats why I jumped in to try and get progress on CWM. Thanks DK and now I know the IRC is more active, I will be on there more to try and help out.
Thank you!
Thanks a ton for all the effort you're putting in. When I got my DX2 I thought that despite the crazily over-bloated Motoblur, I would be OK due to the Tegra 2 power and wonderfully innovative developer community. I didn't count on their being such a small number of us out there for this device or the complexity that Moto would unnecessarily bake in. So, after many months of gut wrenching disappointment, I finally have hope again.
You are a true nerd hero, sir!
Its nice to have an explanation of things and why they work or dont work. A lot of us are just trying to learn so we can be useful.
Sent from my Eclipsed and ICS themed X2.
Dragonz...after reading the info about 1/3/12 I am curious...
Does this mean that you might be able to get it working and unmount system as u need it to?
Or were there still other processes using system that you will need to mess with and change around as you did with the vendor ?
Do you still need to move the servicemanager also?
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
PM me with a copy of your nightly so I can help as well please
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
drapp said:
Kali send me a pm, I have the week off and work as a mobile developer... would like to help get rid of some of those crashes. Send me a link to that irc and ill get cracking on it 2moro
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
kaliblazin707 said:
O btw imma start Hopn on the irc. I have a cm7 nightly booting thanks to second init but am having some crashes, not to mention other horrific bugs.. I need some help
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
dragonzkiller said:
I know why you have a cm7 nightly "booting" and I'm sorry to say that it's not for good cause. What is happening is that the system isn't being formatted properly (hence a point in my post) and you're just flashing a bunch of new APKs from CyanogenMod on top of BLUR. I'm sorry to say, but it's not CyanogenMod.
Click to expand...
Click to collapse
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
aceoyame said:
I honestly think the way to go is to get back to that step with proper 2nd init and then replace everything blur with as much CM as possible
Click to expand...
Click to collapse
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
dragonzkiller said:
But that's not the right way to go. All that is is basically taking the BLUR base ROM and replacing the things with CM7's stuff. That's basically taking the stock rom and turning it into another blur-based ROM with CM7 apks. That's basically like Eclipse.
Click to expand...
Click to collapse
Let me rephrase that, add CM stuff and then remove Moto stuff. So get back to that, delete moto apk's and then edit init.rc for the framework. All those FC's we are getting if when were in that state are vital clues as to whats isn't playing nice with CM's apk's and framework. The fact it can even somewhat boot in a state like that means it's fairly close to how it wants. If it didn't wipe /system/ then it sounds like you just need to properly 2nd init that ***** and then in moto's init.rc remove moto jar's and apks's. Remember if it didn't wipe then you replaced the framework with CM and it's blur running ontop of it.
ashclepdia said:
Webchat.freenode.net
Channel #X2-AOSP
AND #DX2 for "off topic"
Click to expand...
Click to collapse
Thanks ashclepdia.... helpful as always...
Sent from my DROID X2 using xda premium
I've been trying to build a ROM over on the US variant all day (T-Mobile) but I can't get the Cygwin Kitchen to work properly (its something with the updater-script that's causing an installation abort). I played with it for a while and figured out (or I'm assuming at least) that it's related to /tools/edify_defs folder needing the creation of the necessary "d2tmo" file to point out mounting points.
I've read over and over and over the template for creating the file, but I can't seem to figure out how to script the necessary file. I lack the experience. I've tried referencing the SGS2 template, as well as others, plus referencing the original updater-script to try and find the mount points, but I can't seem to get it.
There aren't very many of us on the US variant just yet, due to the small quantity release, so there aren't many people to reference for help.
Any help at all would be GREATLY appreciated...
uoY_redruM said:
I've been trying to build a ROM over on the US variant all day (T-Mobile) but I can't get the Cygwin Kitchen to work properly (its something with the updater-script that's causing an installation abort). I played with it for a while and figured out (or I'm assuming at least) that it's related to /tools/edify_defs folder needing the creation of the necessary "d2tmo" file to point out mounting points.
I've read over and over and over the template for creating the file, but I can't seem to figure out how to script the necessary file. I lack the experience. I've tried referencing the SGS2 template, as well as others, plus referencing the original updater-script to try and find the mount points, but I can't seem to get it.
There aren't very many of us on the US variant just yet, due to the small quantity release, so there aren't many people to reference for help.
Any help at all would be GREATLY appreciated...
Click to expand...
Click to collapse
Ok, we got all the proper mounting points now but we're getting no SIM card reading now.
Any suggestions?
Sent from my SGH-T999 using xda premium
Here is our progress if anyone could be so nice to give it a look over and see if you could lend a hand.
http://forum.xda-developers.com/showthread.php?t=1729966
hey, I'm in the process of trying to build for tmoUS too. using dsixda kitchen but keep getting stuck at the "extracting ROM", the process just doesn't seem to want to complete. any help?
Hi all. New to ROM cooking, so be patient with me please
I am working on a creating a CWM flashable "custom" ROM (actually it's stock ROM with updated preloader, EBR files, performance scripts that is pre-rooted) for a device that currently has no flashable zip ROMS (I can currently only flash stock via SP Flashtool). It uses an Octa core Mediatek MTK8392 chipset, which is basically the tablet version of the 6592 (they are in fact mostly the same processor, and scatter file even shows it as a 6592).
I have got the device rooted, CWM installed (generated with MTK Droid Tools) busybox intalled, everything deodexed, and zipaligned via dsixda kitchen, and the ROM itself is packaged and ready to go. But..after multiple Status 0 attempts in CWM, I realize that my updater script is the issue. I have used kitchen to modify "update" script to "updater", but still no luck. I have attempted to use other updater scripts from similar devices, but even after 1 or 2 of those stated "installation successful", it was clear that the ROM actually wasn't flashed.
I have tried soooo many combinations, and this tool on XDA to generate a working script, but apparently I am just too stupid to get this done (using a master script also didnt work for me). After literally 11 hours of working on this yesterday and trying this method repeatedly, I thought I should ask the pros here on XDA.
I have attached the script from the ROM I recently compiled, and the blocks map file for my device generated from MTK Droid Tools. Could anyone point me in the right direction to FINALLY get this ROM booting? I would greatly appreciate some help.
Also, I have used modded EBR files to extend the internal system storage (1gb for installing apps is a joke). Partition was extended to around 9gb and is working fine, but could it be causing me issues? I basically used EBRs (attached..im using 10GB 1 and 2) to reduce the 12gb USB storage down to around 2.5, and extend internal memory to around 10gb.
@moderators - Sorry, I put this in the wrong section. Could you kindly move it to the Q&A Troubleshooting section?
EDIT: Thanks mods
So I just flashed stock ROM with original EBRs and will try to compile this way. I dont think it will make a difference, but it's worth trying. Maybe the new partitions negatively effected the blocks that need to be written to?
Bump.
Ah common guys. Surely someone here can give a little assistance with an updater script?