yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] anuseb89:
wow guys..check this out..you made to xda page... :)

http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook

congrats...
[Galaxy S Plus I9001 Android Development] h0rn3t:
Thank you very much!

Stay tuned because very soon will be a new version with a new useful function.
[Galaxy S Plus I9001 Android Development] Xami:
Any chance you guys [MENTION=4674443]h0rn3t[/MENTION] [MENTION=4922835]educk[/MENTION] makie this for I9000
[Galaxy S Plus I9001 Android Development] Stefano187:
Guys you are on xda portal!

http://www.xda-developers.com/android/dual-boot-on-the-samsung-galaxy-s-plus/

Inviato dal mio GT-I9001 utilizzando Tapatalk
[Galaxy S Plus I9001 Android Development] h0rn3t:
Yees... [MENTION=4937058]anuseb89[/MENTION] bring the news a bit faster that you !!!:laugh:
[Galaxy S Plus I9001 Android Development] h0rn3t:
version 1.6

Added new feature: Backup/Restore secondary ROM

Other changes:

UI change: added Tools section with following functions: Prepare flashable zip, Backup Secondary ROM, Restore Secondary ROM, Reboot Recovery

In Prepare flashable zip section, use menu to choose between ROM and other types

Backup can be done from both roms.

Restore can be done only from primary rom (may take several minutes so be patient !). To delete a backup from list longpress on it.

remove boot.img 4.2.2 from apk (smaller apk)

Have fun !
[Galaxy S Plus I9001 Android Development] educk:
Kernels updated

Updated 4.2.2 and 4.3.1 secondary kernels (with new sensor drivers) and uploaded new 4.2.2 ION kernel for booting the ADC-Team CM-10.1 ION Preview ROM as secondary.

IMPORTANT ! Each new kernel ZIP (except the ION one) contains the modules which must be manually pushed to /system/lib/modules (on the secondary ROM) with RW-R-R (644) permissions using Root Explorer or anything similar in order to get WiFi working.

Enjoy :)
[Galaxy S Plus I9001 Android Development] Rhonin86:
DualBootSplus 1.6 File size

Hi guys,

i wanted to try the new version but i'm unsure concerning the file size. The former files were about 4 MB in size - the new one is only 286 kb.

Has s.o. already tested it ?

Cheers

Rhonin

And btw. good work h0rn3t and Educk :good:
[Galaxy S Plus I9001 Android Development] darsh11192:
Yeah it is 286kb... And it works...

Educk which module we have to transfer to system lib?? Can you just give us the file name...
[Galaxy S Plus I9001 Android Development] nuck1982:
module are included in the kernel zip. extract the zip.

Gesendet von meinem C64
[Galaxy S Plus I9001 Android Development] h0rn3t:
Initial aplication included a 4.2.2 boot.img file. We decided to remove it , so the apk is now smaller.

And I forgot to mention the vibration alert at the end of long operations!
[Galaxy S Plus I9001 Android Development] tsirhcitna:
I messed with the application, went back to first partition rom and did a format factory, forgetting to save my photos (taken with secondary rom). Is it still possible to get them them back? I didn't touch the secondary partition on the sd card (it still shows 11 GB instead of 16).
[Galaxy S Plus I9001 Android Development] polluzet:
Reboot your Secondary, and you'll see ;):)

from my SGS+, S4 or NEXUS 10
[Galaxy S Plus I9001 Android Development] tsirhcitna:
Oh now it works (before it gave me errors) but my photos on secondary rom are lost because of the format factory on the first rom :( I'm using a recover data app and luckily it's working and I've got some of them back :)
[Galaxy S Plus I9001 Android Development] h0rn3t:
V1.7

Fixed an incompatibility with 4.4

EDIT: Sources available at: https://github.com/horn3t/DualBootSplus
[Galaxy S Plus I9001 Android Development] Rhonin86:
A first step nearer to KitKat :good: Let's just wait for the DualBoot Image for test purposes - but no hurry :highfive:

Cheers

Rhonin
[Galaxy S Plus I9001 Android Development] h0rn3t:
Kernel is ready !
[Galaxy S Plus I9001 Android Development] Rhonin86:
Remark on newest DulBoot-Kernel

Hi h0rn3t, hi educk,

i tested your newest child immediately after publication and i have two remarks:

Bootimage should be renamed to boot2.img (it's boot.img)

I cant get WiFi working though i installed the modules manually and set the right permissions

THX for all

CU soon

Rhonin
[Galaxy S Plus I9001 Android Development] educk:
Hi Rhonin!

Thank you for reporting!

You could try the following:

While you are on secondary ROM, make sure you don't have any libs in /lib/modules and then flash the attached ZIP in recovery.

Let me know :fingers-crossed:
[Galaxy S Plus I9001 Android Development] Rhonin86:
WLAN is working again

Hi Educk,

your provided zip is working :good:

I erased all files within the modules folder and flashed your zip from recovery which i entered from the secondary ROM.

THX for your effort...

Rhonin
[Galaxy S Plus I9001 Android Development] h0rn3t:
Hi, Rhonin,

I made a new version of the application that takes care of ko modules. All you need to do is to extract ko files from zip and put in the same folder with coreboot2.img, then just switch.... Please test it when you have time and report. Thanks!

View attachment DualBootSplus1.8.apk
[Galaxy S Plus I9001 Android Development] Rhonin86:
DualBoot V1.8

Hi h0rn3t,

I can report that your newest release works as it should :good:

I installed the newest KK from ADC-Team with it, also the Gapps and after that i put Educks posted *.ko files in the folder sdcard/DualBootSplus/4.4 where the boot2.img is located and

tada.... :D I've got the new KK runing as a secondary ROM

THX 2 U

And have a nice Rest-WE

Rhonin
[Galaxy S Plus I9001 Android Development] h0rn3t:
V1.8

If your secondary ROM's kernel require additional modules (ko files)...

Extract these files from zip archive, put into the same folder as boot2.img and let the application (version 1.8) do the rest.

EDIT: [MENTION=5359028]theloneseeker[/MENTION] made some useful tutorials at: http://xdaforums.com/showpost.php?p=48060599&postcount=57
[Galaxy S Plus I9001 Android Development] markey97:
You are awesome guys! :good:

I'm glad that i kept my i9001 as a 2nd device after switching to the S3 i9300.

Will definitely get to use this by tommorrow evening. Our S+ is close to be better concerning to software than the S3 soon..you guys rock!!!:cool:

We got a fully functional 3.4.x Kernel -> S3 doesn't have this (yet)

We have a great dev team and a great community -> S3 doesn't have a dev team like ADC Team

We some more nice features than the S3 -> OK, S3 also has some good features we don't have, but i still think the S+ got better ones in my opinion and it also is and will be an awesome phone whole time :good::D

Greets and thanks,

markey97
[Galaxy S Plus I9001 Android Development] Rhonin86:
Compatibility of bootimages

Hi h0rn3t, hi Educk,

maybe i'm wrong but due to my last tests with new kernels on "old" ROMs it comes to my mind, that the provided dual-bootimages of 4.2.2 and 4.3 ROMs might be not working with the newest ROMs. The new kernels contain the new touchscreen-driver while the old ones contain the old one. Therefor libinput.so of the new ROMs and the "old" DualBoot-imgages could result in a not working touchscreen - i have encountered this problem the other way round new Kernel old rom :o

So maybe someone who hast tested one of the above mentioned constellations gives me/us a hint if it works or not. Otherwise new bootimages should be provided or at least a big hint should me made to prevent problems...

Cheers

Rhonin
[Galaxy S Plus I9001 Android Development] jolo32:
I think this is the problem I faced. I tried 3 times to install the 2nd ROM using the dual boot App, v1.8. Every time after the install and reboot I would get stuck on the first screen (language selection) as the touch doesn't work.
[Galaxy S Plus I9001 Android Development] Rhonin86:
Hi just an idea....

Which ROM did you try to install as a secondary ROM ? I assume you tried one of the newest ones and i further assume that the provided boot2.img files are not compatible with them due to the fact, that the newest ones have a new touchscreendriver. (Have a look at the upload dates of the dualboot-kernels ) So i think it is a problem of compatibility. For example CM 10.1 Dualboot-Kernel runs only with CM 10.1 R 8 from ADC Team.... That is my status quo of knowledge.

Cheers

Rhonin
[Galaxy S Plus I9001 Android Development] jolo32:
Hi Rhonin,

I had tried to install 4.3.1 Alpha 1 and 4.4 alpha 1 from ADC team as the secondary ROM. Those were the latest available about 7-8 days ago.
[Galaxy S Plus I9001 Android Development] Rhonin86:
Kernel images doesn't fit to the newest ROM

OK, sry for not answering - simply thought i have already answered :o

The new ROMs are based upon other drivers / libs and the kernel must be adjusted to this changes. And this is not given at the moment - so we have to be patient and wait for new boot2.img files. :cowboy:

The whole team was so engaged in such big projects that the time was simply too short - but on the other hand we got so awesome results from them. But i understand you if you want to verify my statement you need a fitting kernel .... just wait and see :D

A merry X-Mas to all of U

Rhonin
[Galaxy S Plus I9001 Android Development] h0rn3t:
Merry Christmas

I just want to wish everyone Happy Holidays !
[Galaxy S Plus I9001 Android Development] h0rn3t:
Thanks to [MENTION=4922835]educk[/MENTION] we have now the latest ION kernels ready for dualboot.
[Galaxy S Plus I9001 Android Development] ze7zez:
" Applies to:

Samsung Galaxy S I9000"?

It's truth?
[Galaxy S Plus I9001 Android Development] h0rn3t:
I9001
[Galaxy S Plus I9001 Android Development] ze7zez:
Please improve the content of pages:

http://xdaforums.com/devdb/project/dl/?id=2648

http://xdaforums.com/devdb/project/dl/?id=2649

http://xdaforums.com/devdb/project/dl/?id=2650
[Galaxy S Plus I9001 Android Development] educk:
Hello!

In the page you linked, it is clearly stated that:

So, only for i9001...

Unfortunately, this is how DevDB works and there is nothing we can do about it. The i9001 doesn't have its own sub-forum so these are the consequences.

We have to be just a little more careful when downloading and falshing, that's all...
[Galaxy S Plus I9001 Android Development] Rhonin86:
Kernels for ION-ROMs

Hi Educk,

first of all THX for your precious work - when i see the downloadsection i noticed that all ION-Kernels are adapted stock kernels ? Or is it a "stock kernel" with phenom features ?

THX for your answer

(OK - meanwhile i tested it: This are really simple stockkernels, not as usual boot2.img with phenom characteristics - please this is just an information )

Cheers

Rhonin

AND an additional question:

Is the following workflow required or can i just use the boot2.img without the modules ???

THX in advance

( I just copied the boot2.img in the folder 4.2.2 and it works without any moduls - just for additional information.)
[Galaxy S Plus I9001 Android Development] educk:
Hello Rhonin!

Yes, the provided boot2.img's for the ION ROM's are plain stock. They are the same as the ones used in the release, the Ramdisk is different only. Due to this, at the moment there is no need to push any modules because they are the same ones which are already in /system/lib/modules so there's no need to overwrite them.
[Galaxy S Plus I9001 Android Development] h0rn3t:
DualBoot Kernel for CM11 BETA 2

Hello guys, and Happy New Year !
[MENTION=4922835]educk[/MENTION] just uploaded the dualboot kernel for newest ADC CM11 Beta 2.

Enjoy!
[Galaxy S Plus I9001 Android Development] Revontheus:
Wow, Nice to see a device getting dual-boot. Hope they could get this done on some Sony Devices like Xperia SP
[Galaxy S Plus I9001 Android Development] foxmcc8:
Hello guys,i have a question regarding the requirements. When you say minimum 350mb internal storage that's internal sd or the phone's 1.2gb storage?

Thnx in advance.
[Galaxy S Plus I9001 Android Development] h0rn3t:
Internal SD (sdcard0).
[Galaxy S Plus I9001 Android Development] foxmcc8:
Hello h0rn3t....will there be an updated dual boot kernels for the latest ADC roms?sorry for asking of ETA's.
[Galaxy S Plus I9001 Android Development] h0rn3t:
I dont know! [MENTION=4922835]educk[/MENTION] is the kernel's dev and he switched to N5.
[Galaxy S Plus I9001 Android Development] Martin_Devil:
Please, port this DualBoot for Samsung Vibrant (T959)!:highfive:
[Galaxy S Plus I9001 Android Development] educk:
New Kernel for CM11 RC2

DualBoot kernel for latest CM11 Release 2 is available.

Attached to this post because currently XDA DevDB doesn't want to upload anything...

Enjoy!
[Galaxy S Plus I9001 Android Development] Martin_Devil:
Say, would run on Dual Boot Vibrant? This is something like the Devil DualBoot Kernel? The main bootloader does not change?
[Galaxy S Plus I9001 Android Development] ktulu84:
this zips are only for i9001
[Moto X Q&A] gregwaw1981:
Hi,

Where can I unlock sim Moto sprint running on the network?
[Moto X Q&A] 0utkast:
The official way is by talking to sprint, the unofficial way... So far I believe there is none. And hoping someone figures it out
[Moto X Q&A] chinawro:
i hope a man hack it
[Moto X Q&A] ysabxe:
ok... I know how to unlock it, but I need all files from already unlocked MOTO X via OTA by Sprint, please make CWM (TWRP) Backup or just copy all files in root folder / and upload it to server, here my Thread
[Moto X Q&A] gregwaw1981:
GREAT news who help's?
[Samsung Galaxy Star] prbluebottle:
New poster here. Been compiling Linux and FreeBSD since 1998, built OpenWRT firmwares, done BIOS mods, etc. But I have to post here until I get 10 posts...

This is the partition layout for the phone in the title:

Partition name Partition 512-byte blocks Bytes MB (^2)

ProductInfo1 -> /dev/block/mmcblk0p1 7680 3932160 3.75
ProductInfo2 -> /dev/block/mmcblk0p2 7680 3932160 3.75
ProductInfo3 -> /dev/block/mmcblk0p3 10240 5242880 5
DSP -> /dev/block/mmcblk0p4 10240 5242880 5
KERNEL -> /dev/block/mmcblk0p5 20480 10485760 10
RECOVERY -> /dev/block/mmcblk0p6 20480 10485760 10
modem -> /dev/block/mmcblk0p7 20480 10485760 10
reserved -> /dev/block/mmcblk0p8 1024 524288 0.5
SBL1 -> /dev/block/mmcblk0p9 4096 2097152 2
SBL2 -> /dev/block/mmcblk0p10 4096 2097152 2
PARAM -> /dev/block/mmcblk0p11 16384 8388608 8
FIXNV1 -> /dev/block/mmcblk0p12 7680 3932160 3.75
FIXNV2 -> /dev/block/mmcblk0p13 7680 3932160 3.75
RUNTIMENV1 -> /dev/block/mmcblk0p14 7680 3932160 3.75
RUNTIMENV2 -> /dev/block/mmcblk0p15 7680 3932160 3.75
FOTA -> /dev/block/mmcblk0p16 512 262144 0.25
SEC -> /dev/block/mmcblk0p17 512 262144 0.25
Odin -> /dev/block/mmcblk0p18 512 262144 0.25
efs -> /dev/block/mmcblk0p19 20480 10485760 10
CSC -> /dev/block/mmcblk0p20 1048576 536870912 512
system -> /dev/block/mmcblk0p21 1835008 939524096 896
HIDDEN -> /dev/block/mmcblk0p22 262144 134217728 128
MODEM -> /dev/block/mmcblk0p24 20480 10485760 10
userdata -> /dev/block/mmcblk0p25 4243456 2172649472 2072
PIT -> /dev/block/mmcblk0p26 16 8192 0.0078125
MD5HDR -> /dev/block/mmcblk0p27 2048 1048576 1

I got this by look at:

/dev/block/platform/sprd-sdhci.1/by-name/

and cross-referencing those symlinks with the contents of:

/sys/block/mmcblk0/mmcblk0p??/size

which appears to be a count of 512-byte blocks. For those interested, these commands in a Bash shell on the phone helped me to get the information in an automated manner:

ls -al /dev/block/platform/sprd-sdhci.1/by-name/|awk '{print $8}'| xargs -t echo |sed 's/dev\/block/sys\/block\/mmcblk0/g'
for i in (output from the previous command);do cat $i/size;done

I hadn't seen any partition info for this phone anywhere, so I had to go looking for it, and here it is. :)

Now if I could only get CM10 to build (flashable) EXT4 images for it instead of YAFFS2 images...
[Samsung Galaxy Star] atocruz:
Thanks buddy!
[Samsung Galaxy Star] prbluebottle:
No problem. Just trying to help get some form of CM on the S5282. :)
[Samsung Galaxy Star] prbluebottle:
can i reply to my own thread?

OK...

This is a starting point for the BoardConfig.mk:

(code block that ALWAYS gets "flagged")

annoying++!
[Samsung Galaxy Star] prbluebottle:
Despite the boot/recovery image unpacker telling me that the only kernel parameter is a "console=...", looking at "/proc/cmdline" on stock firmware produces a much more complicated situation:

initrd=0x5500000,0x128524 ram=512M fixnv=0x480000,0x10000 productinfo=0x490000,0xc00 runtimenv=0x4a0000,0x40000
sec_debug.reset_reason=0x1A2B3C00 sec_debug.level=0 androidboot.debug_level=0x4f4c loglevel=0 sec_log=0x200000@0xfe00000 lpcharge=0
cordon=709bd173bf5b2391d489a2a24ae4bb5e androidboot.emmc_checksum=3 androidboot.serialno=4d02c5be86f26000
show-guest-banks=0x4 no_console_suspend Oonsole=ttyNK viomem=* linux-timer=virtual root=/dev/ram0 rw init=/init

The only place I can think of for all this to be included is as part of the kernel zImage itself. I still can't find any info on even what the second argument to "initrd=" means. Length? :eek:
[Samsung Galaxy Star] prbluebottle:
OK, the second initrd argument is the length of the compressed ramdisk, in hex, divided by 2. Why divided by 2? No idea.

Anyway, I can now get a CWM6 recovery booting on the S5282 to the point where it starts USB with all the correct IDs, etc. But there's no ADB daemon running, despite the following in the recovery's init.rc (customised):

service adbd /sbin/adbd recovery
enabled

# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
setprop adb.recovery 1
setprop service.adb.root=1

on property:adb.recovery=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04e8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/functions adb
write /sys/class/android_usb/android0/enable 1
write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iSerial $ro.serialno
start adbd

# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1

Relevant BoardConfig.mk:

# For debugging
ADDITIONAL_DEFAULT_PROPERTIES += ro.secure=0
ADDITIONAL_DEFAULT_PROPERTIES += ro.allow.mock.location=0
ADDITIONAL_DEFAULT_PROPERTIES += ro.debuggable=1
ADDITIONAL_DEFAULT_PROPERTIES += persist.service.adb.enable=1
ADDITIONAL_DEFAULT_PROPERTIES += ro.config.sec_storage=1
ADDITIONAL_DEFAULT_PROPERTIES += persist.sys.usb.config=mtp,adb

Anybody got an idea why I can't get ADB to start/connect even in recovery? Permissions?
[Samsung Galaxy Star] ironman38102:
It might be probably because device tree being not completed. Im going to push the missing files to github when I get time.
[Samsung Galaxy Star] ironman38102:
[MENTION=5462581]prbluebottle[/MENTION] read my pm
[Samsung Galaxy Star] ironman38102:
Just pushed missing device tree files to Github. [MENTION=5462581]prbluebottle[/MENTION] try compiling again and notfiy me for any issues
[Samsung Galaxy Star] prbluebottle:
Sent you a PM: your setup-makefiles.sh and extract-files.sh look, ummm, not right.
[Samsung Galaxy Star] ironman38102:
Well seems like Ill need to download those as RAW but if it was in html the script wont work?

***Its Going To Be LEGEND--wait for it--DARY*** Tapatalk now Free
[Samsung Galaxy Star] ironman38102:
Pushed proper extract-files.sh and setup-makefiles.sh to github [MENTION=5462581]prbluebottle[/MENTION] I hope its okay now. Please try to compile again and notify for any issues
[Samsung Galaxy Star] ironman38102:
[MENTION=5462581]prbluebottle[/MENTION] read my pm. Might fix that issue you are having with cwm6.
[Samsung Galaxy Star] prbluebottle:
Both the scripts have a problem:

DEVICE=i9500

should be:

DEVICE=mint

Other than that, they look quite vanilla. I'm not using any proprietary files yet anyway, in my attempts with CM10.2, because I'm just focusing on the recovery. In any case I wouldn't use those scripts - I use a build server that doesn't have my phone connected to it.
[Samsung Galaxy Star] prbluebottle:
Yes, thanks for that, [MENTION=228890]ironman[/MENTION] and [MENTION=4523387]mackief[/MENTION]. Unfortunately, there's no change. :(

This is part of the resulting default.prop in my recovery ramdisk (recommended changes in italics):

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
[I]persist.sys.usb.config=mass_storage,adb[/I]
[I]persist.adb.notify=0[/I]

The ",adb" gets added automatically by the build process, so my ADDITIONAL_DEFAULT_PROPERTIES line for that just sets it to "mass_storage".

The relevant part of the recovery ramdisk's init.rc (recommended changes in italics):

service adbd /sbin/adbd recovery
[I]disabled[/I]

# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
setprop adb.recovery 1
#setprop service.adb.root 1

on property:adb.recovery=1
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 04e8
write /sys/class/android_usb/android0/idProduct 6860
write /sys/class/android_usb/android0/functions adb
write /sys/class/android_usb/android0/enable 1
#write /sys/class/android_usb/android0/iManufacturer $ro.product.manufacturer
write /sys/class/android_usb/android0/iManufacturer Samsung
#write /sys/class/android_usb/android0/iProduct $ro.product.model
write /sys/class/android_usb/android0/iProduct GT-S5282
#write /sys/class/android_usb/android0/iSerial $ro.serialno
write /sys/class/android_usb/android0/iSerial 19761202
start adbd

# Restart adbd so it can run as root
#on property:service.adb.root=1
# write /sys/class/android_usb/android0/enable 0
# restart adbd
# write /sys/class/android_usb/android0/enable 1

[I]on property:persist.service.adb.enable=1
start adbd

on property:persist.service.adb.enable=0
stop adbd[/I]

There's two separate ways for adbd to be started. Neither of them seem to work. I commented out that root-restart stanza.

Linux dmesg when connecting the phone:

[66873.231724] usb 2-1.2: new high-speed USB device number 66 using ehci-pci
[66873.325035] usb 2-1.2: New USB device found, idVendor=04e8, idProduct=6860
[66873.325045] usb 2-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[66873.325051] usb 2-1.2: Product: GT-S5282
[66873.325057] usb 2-1.2: Manufacturer: Samsung
[66873.325062] usb 2-1.2: SerialNumber: 19761202

So, it is reading the init.rc, and it is setting all the necessary USB properties. But either adbd isn't starting (unlikely), or there's some other thing that is stopping it from binding to the USB device stack. Everything else is set and the USB device port is enabled.
[Samsung Galaxy Star] ironman38102:
Fixed the extract-files.sh and setup-makefiles.sh and pushed to github. [MENTION=5462581]prbluebottle[/MENTION] any luck finding solution of the problem? I have PM'ed [MENTION=4523387]mackief[/MENTION] for the latest issue and Im waiting for him to reply.
[Samsung Galaxy Star] ironman38102:
I cant get what he meant by that. :confused:

Its Going To Be LEGEND--wait for it--DARY!- Barney Stinson(How I Met Your Mother)
[Samsung Galaxy Star] prbluebottle:
I can't either. This is Samsung and Spreadtrum we're dealing with here! ;)

The default CM recovery simply doesn't work for us. Even stock is far away from a default AOSP recovery, at the script and init level.

And I did already try his suggested changes. They didn't help, unfortunately. Without ADB we can't debug /sbin/recovery and it's (current) refusal to start or initialise the graphics.
[Samsung Galaxy Star] ironman38102:
Well spreadtrum and samsung are really hard to hack actullay. I cant get that why ADB is refusing to start or initialise! Its like impossible to make cwm6 for this phone

***Its Going To Be LEGEND--wait for it--DARY! -Barney Stinson(How I Met Your Mother)*** Crapatalk now Free
[LG Optimus 2x] lyhengboy:
I can't update my phone since the b2capp not install..how can i install it...? Help..
[LG Optimus 2x] amarprat87:
B2c app is not an installable file. Download a fresh copy from LG website, extract, double click and you can use it.

In case you face further issues, post more details.
[LG Optimus 2x] lyhengboy:
Yes, it has alot of problem like...

In pic. It stock...