[FBOOT][MULTIROM] FOTA -Noob edition - Android Development on Bada

I worked a bit on FOTA bootloader, and i'd like to share some of my work.
Few words about Fota in general
I think lot of people here don't understand fully how Fota work, and this may prevent a lot of questions, please read it.
We use Fota in Badadroid project as a bootloader, it's the piece of code loading modem and android kernel in RAM, and starting android kernel.
Fota decide what key combination does, which system is to be launched if no key are pressed, and where kernel file is searched.
Fota doesn't care if a kernel is Nand or SD or Loop. It just search for a file with a certain name, load it and launch the execution of its code.
This Fota is compatible with ALL roms and ALL versions (nand, SD, loop).
About keys : power key isn't important for Fota, the only function power key have is to power on the device. Once device is powered on (you can use power key but also plug charger or use reboot function), fota will check for other keys. So if i write "Recovery mode : home key", you'll have to press home key and then manage to power on the device, it won't boot if you just press home key.
About this Fota
This Fota is able to load two different kernel. It can be used to load two rom (one Nand and one SD, one Loop and one SD) or if you have a "test" kernel.
If you have only one rom or one kernel, no problem, it will work the same, all the stuff related to second kernel won't work, that's all.
This Fota doesn't allow two Nand rom or two SD rom.
This Fota provide a default "Silent boot" displaying default Bada bootscreen (no more ugly ASCII), however boot is slow so it will be displayed for maybe 15 seconds. If there is an error with kernel, ugly ASCII will appear and tell you there is something wrong.
This Fota also provide an "interactive" mode (or Noob mode). If you press any keys during boot (home, call or volume), it will boot in interactive mode. It's simple and you'll understand fast how it work. Control are vol + and vol - and home key to select.
It also support usual key combination, if you press keys to boot recovery, and when white screen appear you stop pressing, it will boot "interactive mode" and after few seconds boot recovery IF no keys are pressed. If you press sth at this moment, interactive mode will be active.
Test it, you'll understand.
This Fota also boot faster in recovery (no Modem init, who need modem in recovery ?)
However, battery reading won't work anymore in recovery because of that, so don't spend hours in recovery mode.
README
First kernel : boot.img on SDcard
Second kernel : boot_2.img on SDcard
Boot 1st kernel : default
Boot recovery 1st kernel : vol up
Boot 2nd kernel : home
Boot recovery 2nd kernel : vol up + home
Boot bada : call
Yeah, you read well, kernel must be named boot.img and not zImage.
If your rom came with a file named zImage, just rename it boot.img it will work the same. I could have chosen to load a file named MyLittleKernel. Name doesn't matter, only file content is important.
And all the same, rename the second kernel (for your secondary rom, test kernel...) boot_2.img.
All the kernels must be placed on SDCARD
REQUIREMENTS
Bada 2.0
Android Bootfiles (if you have an android rom on your phone, you have it, else, see in badadroid thread to download it.
Bugs
Bada boot doesn't work in interactive mode, it's stuck after Bada bootanimation, maybe someone know why.
Just boot with call key pressed to boot bada.
Please report if there is any other bugs.
Thanks
Big thanks to all Fota contributors, Rebellos, Mijoma, Tigrouzen, ihavenick, Volk204 and all the others i forgot
Sources
My github here, see branch sd.
Downloads
Fixed dual boot broken by little mistake (20/07/2014) :
Mega (s8500 & s8530)
Alternative links :Google Drive
Just flash it with Multiloader

WoW.. Awesome BenzoX.. Congrats for ur work.. Thank u so much..
Regards,
Abhijeet....

Any other links other than mega..??

abhijeet1331 said:
Any other links other than mega..??
Click to expand...
Click to collapse
Updated (Google Drive)

BenzoX said:
Updated (Google Drive)
Click to expand...
Click to collapse
Oh thanks man..

Duude.
Bada+ Android LOOP + Android on SD - It work
Thaaankss

bada is not booting ..
is it possible to boot only bada by using this fota in s8530 ??
when i try to boot bada using press call button ...it won't boot
if it's work then i will boot also android ....but i need bada.
any suggestion...plz
thanks in advanced..

mishail said:
is it possible to boot only bada by using this fota in s8530 ??
when i try to boot bada using press call button ...it won't boot
if it's work then i will boot also android ....but i need bada.
any suggestion...plz
thanks in advanced..
Click to expand...
Click to collapse
For me bada boot work well if i press call key. Not from menu (i have s8530 too).

bada not boot proper
BenzoX said:
For me bada boot work well if i press call key. Not from menu (i have s8530 too).
Click to expand...
Click to collapse
Hi , Benzox
when i boot bada , screen display horrible line with different color (like my bada is crashed).
is it booting normal ??. what should i do. I am using CFW 10.1 Turko
thanks for giving answer ..

mishail said:
Hi , Benzox
when i boot bada , screen display horrible line with different color (like my bada is crashed).
it's booting normal. what should i do.
thanks for giving answer ..
Click to expand...
Click to collapse
I think that's because you have/had a Nand rom installed. Just flash bada (not Fota file) and it will work (you'll loose your nand rom thought)

bada is not booting.
BenzoX said:
I think that's because you have/had a Nand rom installed. Just flash bada (not Fota file) and it will work (you'll loose your nand rom thought)
Click to expand...
Click to collapse
Hi Benzox ,
When u write about this fota like " It can be used to load two rom (one Nand and one SD, one Loop and one SD)" .
So i thought i boot two OS ( bada & nand ) while flash my bada 2.0 with this new fota file.
is it not possible to load Nand & Bada alternative ?
Thanks in advanced.

mishail said:
Hi Benzox ,
When u write about this fota like " It can be used to load two rom (one Nand and one SD, one Loop and one SD)" .
So i thought i boot two OS ( bada & nand ) while flash my bada 2.0 with this new fota file.
is it not possible to load Nand & Bada alternative ?
Thanks in advanced.
Click to expand...
Click to collapse
Nand format and install on nand memory, bada is installed on nand memory...
You need Loop rom (such as badadroid) if you want both to be on internal. memory.
I can allow two kernel but i don't know how to make partitions and storage space appear from nowhere

Questions ...
I want to install two android roms NAND and SD
What do I install first nand ram or rom SD?
The reason for my question is that when a rom on the SD card installed to do partition SD and lost all the contents of the SD.
If installation nand rom first
And after install the second rom in sd
Does the second rom could not delete the first installation nand?
I want to install nand rom and sd rom but not in what order I have to do
I do not want a rom overwrite the other rom because the two are installed in the SD

tofifo said:
Questions ...
I want to install two android roms NAND and SD
What do I install first nand ram or rom SD?
The reason for my question is that when a rom on the SD card installed to do partition SD and lost all the contents of the SD.
If installation nand rom first
And after install the second rom in sd
Does the second rom could not delete the first installation nand?
I want to install nand rom and sd rom but not in what order I have to do
I do not want a rom overwrite the other rom because the two are installed in the SD
Click to expand...
Click to collapse
Nand rom partition Nand (and delete it's content)
SD rom partition SDcard (and delete its content)
A nand rom will never overwrite a SD rom and vice versa, whatever fota you use.
Order doesn't matter.
Of course if you do Nand rom first you'll have to put its kernel on SD again.
You can't install two rom on SD, nand rom is installed on nand (internal memory) and sd rom is installed on SD.
Only kernel is on SD for both rom.

@BenzoX i forgot your codes but if you want to boot from interactive mode to bada mode i remember you must turn on mmu and disable modem (its opens again )

ihavenick said:
@BenzoX i forgot your codes but if you want to boot from interactive mode to bada mode i remember you must turn on mmu and disable modem (its opens again )
Click to expand...
Click to collapse
But in my code Modem init and mmu is called only after the "return rm_BL3 (which is the signal to start bada if i understood well)
Only thing made from the start of Fota.c are
Code:
int mmuctrl = MemMMUCacheEnable(gMMUL1PageTable, 1);
disp_FOTA_Init();
__PfsNandInit();
__PfsMassInit();
MemoryCardMount();
Rest is only displaying and setting some variable used only in Fota.c

I must be doing something wrong
If I knew cuel is my error.... not would have error haha
I installed a rom sd using the SD kernel.
I installed a rom nand using the nand kernel.
But the fota of menu always starts the same rom both when select kernel 1 o when select kernel 2
I have noticed one thing, we make a sd installation or nand installation the folder Android always appears on the sd card.
I see it almost impossible to install two android roms even if one is nand and the other sd because the folder Android always overwrite rom to another rom

tofifo said:
I must be doing something wrong
If I knew cuel is my error.... not would have error haha
I installed a rom sd using the SD kernel.
I installed a rom nand using the nand kernel.
But the fota of menu always starts the same rom both when select kernel 1 o when select kernel 2
I have noticed one thing, we make a sd installation or nand installation the folder Android always appears on the sd card.
I see it almost impossible to install two android roms even if one is nand and the other sd because the folder Android always overwrite rom to another rom
Click to expand...
Click to collapse
If it start the same rom, it's a kernel for same type (SD/Nand)
Take your kernel for SD and name it boot.img, take your kernel for Nand and name it boot_2.img (or vice versa). Put both on sdcard.
I'll test again my Fota but i'm almost sure it work (i did small modification and haven't tested both boot, but it should work)
This folder is not "essential" and distinctive to both rom.
Only issue may be if you have different version of the same apps on both rom, or if you use same apps on both rom. In this case (and only IF apps data are stored on SD, which is a minority), thing may be a bit confused.

nice.. good job.. this is what im waiting for.. something that will replace ugly ASCII on boot.. got some questions though,.
i have bada installed with sd rom and sd kernel installed on a partitioned sd card.. so my questions are..
1) can i install 3 OS?.. 1 bada(call) on nand, 1 android sd (end) and 1 android nand/loop (middle) on nand again?..
2) so if i put ALL kernels in sdcard by just renaming it.. what about the 2 roms, both in sd card as well?.. how will it know which rom the kernel will boot if same on sd card?
3) how long does the new boot take?.. can u show some screenshot or video?
4) what rom and kernel are u currently using?
again.. thank u for this fota!

BenzoX said:
If it start the same rom, it's a kernel for same type (SD/Nand)
Take your kernel for SD and name it boot.img, take your kernel for Nand and name it boot_2.img (or vice versa). Put both on sdcard.
I'll test again my Fota but i'm almost sure it work (i did small modification and haven't tested both boot, but it should work)
This folder is not "essential" and distinctive to both rom.
Only issue may be if you have different version of the same apps on both rom, or if you use same apps on both rom. In this case (and only IF apps data are stored on SD, which is a minority), thing may be a bit confused.
Click to expand...
Click to collapse
I've the 2 kernels renamed boot.img and boot_2.img
But I noticed that only detects one of the kernels
When you start the menu fota options
KERNEL 1
KERNEL 2
No matter which you select because it always opens the same kernel
Do not know if that will be a mistake, it's a question is not affirmation

Related

{26/JAN/2012}SD ROM+DualModeRecovery -MultibootCWM+XRecovery[Stock Kernel&Alfs Kernel

{26/JAN/2012}SD ROM+DualModeRecovery -MultibootCWM+XRecovery[Stock Kernel&Alfs Kernel
Multiboot+DualRecovery (CWM with multiboot & XRecovery together at last!)
What is multiboot CWM by nobodyAtall?
It is a recovery that allows us to boot ROMs (with certain changes made) from our sd-cards!
Have one ROM on your NAND(internal memory) and as many ROMs as you can fit(400mb each) on your sd-card.
What is DualRecovery?
It is the option to: (in this case)
Boot into XRecovery by tapping the back button while your phone is turning on.
&
Boot into CWM multiboot by repeatedly tapping the screen while your phone is turning on.
Install Instructions:
Have approx. ~900mb free on your sd-card.
1:Simply download the "Multiboot+DualRecInstaller+FPv24SD.zip" & flash in ClockWorkMod.
2:Reboot phone + while rebooting tap the touchscreen like crazy!
3:In CWM multiboot, go to multiboot settings, choose "Select default boot option"
4:Select "FroyoProv24SD.StockKernel" then reboot.
Read Post#3!
DOWNLOAD:
Download "Multiboot+DualRecInstaller+FPv24SD.zip" Here~100mb.
This is for STOCK KERNEL, everyone else read post #2!
No Mirrors! I will make a mirror soon!!!
If you are on stock kernel this should work on ALL Roms...however I have only tested a few.
Credits:
Multiboot CWM= nobodyAtall.
XRecovery= zdzihu.
Dual Mode XRec+MultiCWM= [email protected] (me)
AutoInstaller+Extras= [email protected] (me)
This is not a new idea, I have just made the necessary changes, packaged dual mode recovery with multiboot CWM, made an AutoSDROMInstaller package, as well as offering your first ROM(FPv24SD).
Users were asking for this, so I made it.
Alfs Kernel Users:
What is DualRecovery?
It is the option to: (in this case)
Boot into CWM by tapping the back button while your phone is turning on.
&
Boot into CWM multiboot by repeatedly tapping the screen while your phone is turning on.
Install Instructions:
Have approx. ~900mb free on your sd-card.
1:Simply download the "AlfsMultiboot+DualRecInstaller+FPv24SD.zip" & flash in Alfs ClockWorkMod.
2:Reboot phone + while rebooting tap the touchscreen like crazy!
3:In CWM multiboot, go to multiboot settings, choose "Select default boot option"
4:Select "FroyoProv24SD.AlfsKernel" then reboot.
Read Post#3!
Download:
Download "AlfsMultiboot+DualRecInstaller+FPv24SD.zip" here~100mb.
No mirrors! I will add a mirror later! Please be patient!
Please note:
You can flash this at any time but if installing a new NAND(internal memory) ROM...
This is the last thing that should be flashed, if you flash Alfs kernel fix after this, you will break DualRecovery functionality.
Important Information:
1. Not all sd-card are supported!!! If you set a default boot option but your phone phone boots into your normal rom then your sd-card is NOT supported. (Try a different sd-card.)
2. Each boot option(ROM) takes up around 400mb of space on your sd-card.
3. However you need 800mb(+100mb for the installer) free on your sd-card to install this as I have included a 512mb data.img with this package so you can go crazy installing apps.
4. First boot will be SLOW. We are booting from the sd-card remember?
5. Slow sd-cards will mean a really sluggish multiboot.
6. Performance is very different compared with ROMs on your NAND(internal memory), you shouldn't compare them.
Explanation of multiboot functions:
-Select default boot option: Set the external(SD) ROM in which you want the phone to boot from now on.
-Unset default boot option: Unset booting of external(SD) ROM so that the phone will boot from NAND (internal memory).
-Create boot option from zip: Select and install an SD ROM in sdcard (requires 400mb free).
-Delete existing boot option: Delete an already installed ROM from your sdcard.
-Flash zip to boot option: Flash updates to an already installed (SD) ROM.
Bugs:
Stock Kernel:
--Some sd-cards are not supported -If you set default boot option but your NAND(internal memory) ROM loads, then your sd-card is not supported.
Alfs Kernel:(This may just be for the sd-card I have here, please try yourself.)
--SD-Card can not be accessed, not from USB or from file explorer
You can still download and install all your favourite games with the large data.img provided. (Alfs vold is already included, it doesn't magically fix this lol.)
--Cannot 'Create boot option from zip'+'Flash zip to boot option'=Same bug as above really.
This will either need ramdisk changes in Alfs kernel (probably wont happen) or ramdisk changes in ROM, or recompile of nAa's CWM multiboot 4 Alfs (probably wont happen).
To ROM devs:
Just give me a thanks & nobodyAtall a thanks before using this stuff, that's all I ask.
Devs using Alfs:
Due to the sd-card bug at the moment you will have to provide your rom in either:
1. A package like this one. -Use mine as a base, so users can auto install easily through CWM.
2. A system.img that users can put in a folder in the 'multiboot' folder of their sdcard with a cache.img & data.img (they can just copy the ones I have provided from one folder to another folder of there sd-cards).
3. Fix the sd-card bug, I haven't even looked at this yet, I have spent too much time on this already.
A lot more information can be found here & (for x10mini)here.
These links are old though so many of the stuff may not work anymore or cause weird bugs with current ROMS!
Not really advised to do it yourself, wait for your ROM developer to release a multiboot patch!
This seems really crazy, will try it out asap there are a bit more infos!
Will it be possible to eventually have boot images of 4 different Android versions?
will be the rom faster if it boots from sd class 10 card? Or nand is faster? Sorry, i have no time to test. I will be thanksful if you give me answer
Hefko said:
will be the rom faster if it boots from sd class 10 card? Or nand is faster? Sorry, i have no time to test. I will be thanksful if you give me answer
Click to expand...
Click to collapse
NAND ofcourse, there's still the bridge to the SD card.
You can compare it with your PC, the speed of your HDD is still faster than any USB pen you plug in.
Well in some ways & doing some things, SD ROMS will be faster.
But overall probably NAND is slightly faster.
For benchmarking scores SD ROMS will definitely mark higher.
This is so easy, on stock kernel or Alfs Kernel, you just install it in ClockWorkMod & hey presto dual mode recovery with XRecovery, Multiboot-ClockWorkMod and a flashy new SD ROM.
It works great for me...I play all my games on my SD ROM then I don't lose my save games when flashing new test updates of my NAND ROM.
It seems this was just a big waste of time for me though. No one interested in this??
i know it sounds stopid,but what is ETA? i really dont know
shadik555 said:
i know it sounds stopid,but what is ETA? i really dont know
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Estimated_time_of_arrival
Google is your friend.
thnx
this could be handy if i ever manage to download the link, makes me wait then goes wrong then tells me to try again in a hour, plz could you make another link thanks
suppose i wanna mutiboot ics and gb what should i do
ankitxperia said:
suppose i wanna mutiboot ics and gb what should i do
Click to expand...
Click to collapse
stop daydreaming XD
ics needs nAa 11 or nAa ics,and multiboot only worksbon alfs and stock kernel.not nAa!!
Sent from my X8 using xda premium

[Discussion] [q/a] Development for flashing kernel image from cwm for xperia devices

Disclaimers :
#i am no-developer.im just a geek xperian..like many of u.i have created this ,my first ever thread typing on my mob keypad.so forgive me for short words and untidy post.
#links included below is noway related to me.respective links are included as per my findings to support the main moto of this thread.im thankfull to all of them who have tried to scratch on this through their posts and threads
#with all do respect,this thread is intended for our devs who can take this as pre-requsites for development.
#its a humble request for devs to put there effort on this.
#i request all xperians...from devs to simple users...whoever thinks this post worth discussing/developing,ur valueable words on this are highly appreciated.
#and please no trollers
Click to expand...
Click to collapse
I was doodling around today,i got my eyes poped-up wen i encounterd this
[samsung kernel flashing from cwm zip] -> http://forum.xda-developers.com/showthread.php?t=1301756 and this
[samsung general cwm kernel updater] ->http://forum.xda-developers.com/showthread.php?t=2132208
It all began then when i had to be far from my pc.then flashing new kernls for new custom roms began to be a problem.i presume their are a lot of users like me who cant access pc with as ease as many can.or simply to them who dont want to connect to pc just to flash kernels.if this would be success,just imagine how ease it would be?
But before starting to dream lets put together what i have come across till now.
Then i started digging more...on google & found this Tutorial [many devs might be intrestd &could help xperia users& start to run xperiment in our xperia ] --> http://www.modaco.com/topic/360180-howto-build-and-update-kernel-using-cwm/
In my findings i did aknowledge that this matter has/have/had been left out in corner just for some taboos/nerms like our xperia doesnt ship with normal recovery partition or like our custm recovry doesnt support some disk formats.
But whatsoever, i was little arosed by above things....then came a point whereafter i was too excited,wen i found this in our very xperia forum,xperia p forum ->> http://forum.xda-developers.com/showthread.php?t=2409021
Here the dev has created a zip with updatr script writng the kernel image,which stays inside the boot.img file .i couldnt dig more on this zip,as it was not so popular thread.i dont even know for it works or not,all i know is there are devs wanting to build,which is the main moto of this thread to let devs rethink the possibilty.
And yes, its a convincing reason for acceptance that our xperia doesnt have recovry partition like as other vendors device..and what we get as a recovry is hard coded to ramdisk.but like as ,A xperia s user,i too want to question an enlightning point on this...like using recovry fota partition,wich gets blokd and remains unusable aftr bootloader unlockd....why not use that...if not what about repartitioning empty space in device for recovry usage partition... http://forum.xda-developers.com/showthread.php?t=2163643
i too presume, even though we dont have that heavy intrnl space,but i guess we have enough for just a recovry partition.i guess so.correct me.
FOTA partition :
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Kernel changes : extract_elf_ramdisk setup in kernel
if some body wants a detailed info it can be found here (( **thanks to @officiallysonyrebel ,for the supportive conversation.above words are his ** )) -- http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
*** Summing up in total ***
It may b a horizon-touching dream..but as a geek user, like me,we dream of it.
Our charming devs can unlock bootloaders/root/giv us custm roms/give us a taste with unimaginable upgrowing ever, android version updates in roms/ ports.these all would also be impossible without their immense hardwork/researchs/xperimnts...i do aknowledge its a lot to ask for this.but with all do respect i wish devs get ther hands on it.
I predict most of xda-ians might already know abt all this,if yes do enlighten us more...ur comments and findings are most needed thing currently.
but truely saying i really dream of using cwm @ its maximum capacity,as of its easeness,isnt it? Different vendors like samsung,zte,etc evn can get rooted simply from cwm only...even most htc can. So why cant our xperia?is it coz of less devs in our xperia?i humbly request all devs to put some work on this so that me,like users who cant access pc with ease/dont want to,can easily get the work done.i also presume there r a lot of xperians,who want this.it cant be more handy than this...can it?
Hope in near future ,we xperians could getwith like these features as others.(rootng/flashng kernels from cwm).
Cheers!!
Xperia-lover!!
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
officiallysonyrebel said:
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
Click to expand...
Click to collapse
Ya i had read in the link u dirctd...i got to know that aftr unlockng bootloadr, that partition becomes unusuable/inaccessble.if that could be attained...then we can hope...isnt it?if i undrstud... wish devs could wave their magicstick soon.
Sent from my Xperia Ray using xda premium
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Nope...You are still using the same kernel....just booting from different ramdisk when "installed in /system"...
We need to boot from a "second" kernel which can be used to flash the primary kernel ...Most other phone can boot into two kernels ,one stock and one recovery ,hence they can be used to flash kernels via recovery and use flash_image to install recovery in system ...
The problem is not where kernel/recovery is installed
The problem is how to boot the secondary kernel after installation ...It's very difficult to do that ...
lets say I dd the recovery.img to /mmcblk0p4 which is the fourth partition in an SD card
How do I instruct the bootloader to boot the device from /mmcblk0p4(or fota 1 or whatever) instead of /boot ...Thats the problem ...
Okay that's sad
But what about checking the partitions and if we know which blocks contain the Fota partition, could we try to mount it?
The problem would be how to tell the bootloader to boot the recovery or the 2nd kernel right?
Sent from my Nexus 4 running Android 4.3
Still the same problem ,how to instruct the bootloader to boot from fota 1 instead of /boot !!
Check that. It's exactly the same what we want to do, right?
Okay not exactly but we could use that too. But I'm not sure if he is able to install another kernel in the recovery...
Sent from my Nexus 4 running Android 4.3
mihahn said:
Check that. It's exactly the same what we want to do, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
karandpr said:
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
Click to expand...
Click to collapse
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
mihahn said:
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
karandpr said:
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
Click to expand...
Click to collapse
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
mihahn said:
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
karandpr said:
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
Click to expand...
Click to collapse
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
mihahn said:
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
karandpr said:
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
Click to expand...
Click to collapse
Yes the HTC HD2 has great development support and I already worked with a HD2 of a friend, but I have actually no idea how to use the method they are using for the HD2 for our devices. I think I will dive into it when I'm back at home from my vacation trip
Sent from my Nexus 4 running Android 4.3
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
officiallysonyrebel said:
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
Click to expand...
Click to collapse
Ehh...no it won't work ...the S1boot boots only from /boot...
The thread you cited is too old and worked probably due to an exploit in nook color ...
I think something like LK should work ,provided it waits for sd card to mount...
officiallysonyrebel said:
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
Click to expand...
Click to collapse
Correct me if i m wrong.its a noobish thought.
Can we access fota partition before bootloader is unlocked?if we can so what r we waiting for?
lets rehearse for the magick show,do what u have thought of.
(I presume when device is still locked....or if we revert back to locked state from unlocked... we could acces that partition.. .we get space for secondry kernel...if still quesn is letting bootloader know we want to boot from that,then again we r far behind)
Sent from my Xperia Ray using xda premium

[Q] Galaxy GT-S3839i boot loop

Hello members hoping I can get some guidance.
Damaged my old phone in a accident the other week so I used my wife's old spare (unlocked) Galaxy Ace GT-S5839I.
As you all know it's a bit dated and slow so I decided to read (a lot) of this forum and decided a rom update was in order.
Looked at the CynagenMod roms. Read the tutorials and downloaded necessary files for the update from SD Card.
Started with CM9_cooperve_Beta_05, excellent rom, used it for 24 hrs but it's unsupported and has a few bugs.
So I decided to go for cm-11.0.0-GT-S5830i-cooperve, again excellent rom but it wouldn't boot with my sim card installed which defeats the objective of having a phone for communication.
I read about installing the modem file to overcome this sim problem and so installed MODEM_S5360_XXMK1.
This did not solve my sim boot issue, so the decision was made to revert back to CM9_cooperve_Beta_05 till I found something withy less issues.
This is when I started having an issue with the rom, though I can't remember the exact phrasing but it was something like Encryption Error when the rom booted, my only option was to reboot and wipe cache etc, which I did, however this did not solve the the issue. It just booted again, every time, with the same encryption issue.
So I came back to these forums and read many threads, some advice was that the intenral sd card was now unreadable, which I guess is real bad.
Other suggestions were to flash a stock rom to the phone, using odin, this could solve the issue, so I have, except now the phone is in a kind of boot loop. Showing a brand logo (used vodaphone and orange roms amongst others) then the Samsung logo then brand logo and so on, stuck in a boot loop I guess.
I have also read that to overcome this boot loop, if the internal sd is damaged, is to use my sd card as an external sd replacement for the internal sd.
This is as far as I got as its 6.15am and I haven't been to sleep yet.
Now most advice on the internet is a little flaky at best so im hoping any members here may be able to give me some good solid advice as to how to best rescue this phone as I really don't want to give up yet.
I can still enter download and recovery modes with the phone.
So please, someone throw me a bone here.
@ cbagy , So your internal partitions at first was transformed into EXt4 if I am not mistaken (CM9_cooperve_Beta_05) , then you decided to convert them into MTD through CM11 , which I have no idea what was your guideline to do so . Finally to make the long story short you couldn't revert back to clean installation state << RFS partitions> ( stocked in endless boot loop I assume ).
First few tips about ICS based Roms ( i.e : Beta 5 CM9 ) : "Encryption Unsuccessful - Reset Android" warning is due to a bug in the firmware for the memory card in your phone, which might be triggered by ICS incorrect function << I am just a novice Android guy, So I might be wrong on many counts ,, just trying to help though >> (/data and /sdcard partitions are no longer accessible). So lets not assume we have a worst case scenario , which is Samsung Captivate/Hardware related problems ; a.k.a : Bad internal SD.
S5839i and s5830 i have a very similar CSC/PDA/MODEM functions , so just grab one of the newest Wipe flash able package made by splitfus2 app ( preferably based on your region /Country, if you insist ) >> I need you to read post#8 starts from the line "-from sammobile database; this page......." to the end of my comment to get to clean state, which is required for rest of the process .
Requirements :
Temporary CWM zip flash able file( 5.0.2.6) or ( 5.0.2.8) , CooperVe compatible; obtainable from >> 1 , 2 , 3 , 4
Proper drivers installed inside your PC; Download Odin3.v3.07.Cooperve ( i,e : this post or any official sticky topic) >> pit file is also resided inside the file .
Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar > or any working version for this device you got . ( could be found in post 8 )
After bypassing loop issue , I would like to suggest downgrading to CM7.2 based Rom, using EXT formatter tools to convert into EXT4 manually;installing CM Specific Basic Kernel - BroadcomCM[COOPERVE][v4.0 ]; and rest of story @ post#3,4 .
Before starting with your CM7.2 based, You need to Re-partition your 2 gb SD card through your Temp-CWM >> Go to "Advanced" >Select "Partition SD Card>Choose your SD-ext size (/data is bound to be the first size you choose << for 2 GB, 512 MB max>>, the rest would be /sdcard ; swap "0" MB)
last resort is Editing "etc/vold.fstab" and swap path of internal and external SD card as you have suggested for possible bad SD .
So , for now proceed with initial boot loop issue and report back ,,,
Edit : Reading at least few pages of this topic is recommended, if you like to learn more about ICS problems.
Excellent news, all working, thank you so much you are a star.
All ready had most (if not all) the tools required.
Phone back to stock using a Euro/Russian split rom.
Seems the split roms work with through Odin where as the one file rom doesn't.
Phone reports a S5380I device rather than a S5839i but that doesn't matter.
Im ready to move to a 7.2 rom.
Continuing to read the last part of your post regarding reformatting etc but it's all a little hazy for me right now but I will continue reading.

[Q] S5839i stuck at boot - how to rescue data?

Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
nashsx said:
Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
Click to expand...
Click to collapse
Humm,, Please define the version of Temp-CWM you did flash( CooperVe compatible assuming)
Define 'flashed a kernel' please, Your stock firmware already contains a stock kernel, which is quite capable of performing what we are expecting from basic kernel. ( Explains in details how did you install custom kernel or custom Roms etc etc,,)
Always do your Nandroid/EFS/Data back up prior to tinkering though.
IF the only option available to you due to soft bricking is , Downland mode >> upon flashing over Odin your /data partition will be wiped out for successful restoration of your device.
waiting for your through explanation,,,,,,
Hello,
thanks for your reply. Unfortunately I cannot specify the CWM version anymore, but I flashed a custom kernel via the CWM, it was a flashable zip file downloaded somewhere in this forum that I flashed using CWM (which I installed using ODIN, iirc). The reason I cannot say what CWM I installed is, I had a data loss on the hard drive inside my computer where I downloaded the files to. If it's really important to know what kernel it was, then I believe I could reconstruct this by searching the custom kernel section for the specific device in this section, I am sure I will know when I read the name again. While waiting for a new reply I'm gonna do this to find out what kernel I flashed via CWM.
The problem with the last resort suggested by you, ODINand download mode and this stuff, is that the data I need to restore is located in data partition if I am correct. Or maybe I'm wrong? The data is from the android text editor notepad which I found out doesn't store data in /sdcard partitions, neither internal nor external, so if I'm right, this means it's being stored in the application's data directory. Please tell me if I'm wrong with this guess.
.
Regards,
Nash.
@nashsx, I fully understand your concern in regards of sensitive data recovery from internal SD partition. However you need to be more specific with all of the tools and Roms you did use whenever you ask for accurate assistance .
Nevertheless I am going to explain all of the errors and possible symptoms you might encounter during CWM flashing to Kernel procedure .
First , You need to comprehend that for your device's ( known as CooperVe) safety we need to use compatible temporary CWM flash able zip file or CWM comes with kernel . The latter is not recommended though for many reasons I would not engage at the moment ( files could be found here or here for instance,,,OR any official sticky topic )
As for kernel Let me be clear : We do not flash custom kernel on top of stock firmware for s5830i/C/M/5839i devices under any circumstances. This is a correct order >>
Stock Firmware >Custom Rom based on stock kernel > Custom kernel
Alternative : flash Custom Rom comes with custom Kernel , and there are so many wiping and formatting process will be involved in between flashing I would not go into more details .
Basically we are obtaining an exclusive right to use Mods/Scripts/Tweaks : performance , battery ,, etc etc at boot time , by activating our init.d support with the help of custom kernels and much more stuff we can perform after flashing. ( Well established name you requested : Rafael.Baugis ; ThunderKernel ; CyanogenMod 7.2 Specific BASIC Kernel ; Hells Fusion )
Now a little educational standard internal memory partitions one- on-one :
/boot
/system
/recovery
/data
/cache
/misc
SD card partitions :
/sdcard
/sd-ext
/data or User data , is the part in question you are trying to access via recovery , which is not an option anymore sadly.
This is where your contacts, messages, settings and apps that you have installed go. Wiping this partition over Odin with the help of wipe - flash able 3 parts package made by splitfus2 app( and other options ticked : re-partition and pit & boot loader selected ) for example ;essentially performs a factory reset on your device; restoring it to the way it was when you first booted it.
We only have 2 options ( if you can call it an option at all in reality ) for recovery procedure , since you don't have access to either of stock e3 / CWM recovery consoles .
1.Normally During boot loop ADB won't work, but we can give it a try ( ADB debugging option must be ticked inside Developer settings inside your Android OS ; platform-tools is required or any GUI based app such as Droid manger will do .
2. Flashing only one part file ( xxx.tar.md5) Over Odin3.v3.07.Cooperve ; you may pick your file from here < registration is required >. Proper drivers installed inside your PC; Put the file into PDA part and do not touch anything else ( Factory reset and Re-partition not selected, Reboot option is OK though ) > click start. ( Do not remove USB cable till the process being terminated and take a complete screen shot of Odin log file entries for me.
This method does not wipe the partition in question., but there is a strong possibility you can not bypass the initial boot loop to get into the OS though.

[ROM] [lolipop 5.1.1] [omni] [NAND] LionDroid V8

Hi All,
Android Lolipop 5.1.1
​
features
Android 5.1.1
kernel of badadroid
change or delet Some app
smooth
stable
Battery is very good
Downloads
v8
http://www.mediafire.com/download/qhuk4ypwhialp21/omni+5.1.1+LionDroid+V8.zip
V7
http://opizo.com/N1ATZ
V6
http://opizo.com/Xakla
V4
http://opizo.com/F2bZr
V3
http://opizo.com/J1PpH
V2
android 5.1.1
http://opizo.com/f2eWy
V1.1
http://opizo.com/nHkIT
2015/02/25 Initial release
http://opizo.com/A2Tvt
changelog ROM
better battery & smoother
more optimization
more speed & free ram
more stable
update source
and other...
INSTALLATION
FIRST INSTALLATION
Bada 2.0 is required
Warning! It will remove Bada!
Download BOOTFILES, Kernel and FOTA for your device:
for 8500:
BOOTFILES https://yadi.sk/d/KhxqKyg4bP2nu
"start" kernel https://yadi.sk/d/ilhyKTaEfTo6L
FOTA https://yadi.sk/d/OtpVoaXpfNggE
for 8530
BOOTFILES https://yadi.sk/d/cBPD41VEbP2od
"start" kernel https://yadi.sk/d/wVGzUA96fGW55
FOTA https://yadi.sk/d/-WnbHbFHfNgZK
Flash BOOTFILES, "start" kernel and FOTA using Multiloader.
After reboot it will open android recovery
Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back -> Reboot -> Recovery -> Swipe to Reboot
Mount -> Enable MTP (if you see disable MTP - it is already activated) on this step PC can ask to install driver, use Android MTP driver
Copy Zip with ROM to Internal Storage or Sdcard -> Disable MTP -> Back
Install -> choose zip with ROM(mount point /sdcard for Internal storage and /external_sd for SD card) -> Swipe to Confirm Flash
Wait for flashing (about 10 min) -> Reboot System
First start take about 10-15 min, be patient.
Enjoy OMNI!
ROOT
Omni is without root support from default
To activate root flash zip via Recovery from XDA thread http://forum.xda-developers.com/showthread.php?t=1538053
GAPPS
GAPPS make our ROM slowler, because also slim GAPPS take about 15-20 MB RAM permanently
https://mega.co.nz/#F!G0QXXRAC!pZ063qCaa5lxdD73SarU6Q
Thanks to
volk204 [for any things]
omni team
code rom team
@jeffreyvh
Rebellos
blue59
hero355
Tigrouzen
Benzox
and other Badadroid devs
reserved ....
first build android 5.1.1 but very Slow
now build android 5.0.2 smoother and more ram
please test rom and tell me bug
thnaks
good news!!!!!!
Sent from my GT-P5100 using Tapatalk
thank you nima
new version uploading ....
edit: uploaded
Thanks for your dedicated work to support the Waves!
One question: Will updating from Omni4.4 work in the same manner as described here?
Renth said:
Thanks for your dedicated work to support the Waves!
One question: Will updating from Omni4.4 work in the same manner as described here?
Click to expand...
Click to collapse
your welcome
Yes, the same is
nima.yavari said:
your welcome
Yes, the same is
Click to expand...
Click to collapse
Thanks again. Forgot to ask: Will it remove Bada and all its contents or stay in parallel like the OMNI does?
And is there a list of problems/missing features or similar regarding this version?
Renth said:
Thanks again. Forgot to ask: Will it remove Bada and all its contents or stay in parallel like the OMNI does?
And is there a list of problems/missing features or similar regarding this version?
Click to expand...
Click to collapse
remove Bada and all its contents.But then returned Flash Bada
i can't found bugs
features on post 1
nima.yavari said:
remove Bada and all its contents.But then returned Flash Bada
Click to expand...
Click to collapse
Thansk again. That's a little bit of a pitty since I am still regularly using Route66 navigation of Bada (bought the lifelong version) - did not find any reliably and suitably working free offline Android navi app.
Unfortunately I cannot copy over the zip when mounting the USB from recovery, in Windows Vista it is only shown as %SingleADBInterface% so I cannot copy data onto it.
Is there any way to get this fixed? Search in Google and here did not help yet (still investigating).
Ok. Managed to copy it via ADB push but cannot install: Flashing gives error:
executing updater ... failed
and before
failed to mount dev/lvpool/system ... ... ..at /system no such file or directory AppliedParsedPerms: ... removeexeattr of /system/binbackuptool.sh to 0 failed: operation not supported on transport endpoint
ß
When copying the zip into / folder I get:
Unable to find partition for path /omni 5.0.2 LionDroid V1.1.zip
Anything I can do here? Do I have to copy the .zip file to a special place? Or do I have to extract the boot.img and copy it separately (since the one in the 5.0.2 Liondroid is different from the one of OMNI4.4.4 which is currently on my S8500)?
Currently I've got the OMNI4.4.4 on SDCard, booting from SDCard. So I have not /external_sd as a directory. So maybe I need to set something as mountpoint (if so - how?) or have to copy the ROM ZIP to another place?
Renth said:
Thansk again. That's a little bit of a pitty since I am still regularly using Route66 navigation of Bada (bought the lifelong version) - did not find any reliably and suitably working free offline Android navi app.
Unfortunately I cannot copy over the zip when mounting the USB from recovery, in Windows Vista it is only shown as %SingleADBInterface% so I cannot copy data onto it.
Is there any way to get this fixed? Search in Google and here did not help yet (still investigating).
Click to expand...
Click to collapse
Renth said:
Ok. Managed to copy it via ADB push but cannot install: Flashing gives error:
executing updater ... failed
and before
failed to mount dev/lvpool/system ... ... ..at /system no such file or directory AppliedParsedPerms: ... removeexeattr of /system/binbackuptool.sh to 0 failed: operation not supported on transport endpoint
ß
When copying the zip into / folder I get:
Unable to find partition for path /omni 5.0.2 LionDroid V1.1.zip
Anything I can do here? Do I have to copy the .zip file to a special place? Or do I have to extract the boot.img and copy it separately (since the one in the 5.0.2 Liondroid is different from the one of OMNI4.4.4 which is currently on my S8500)?
Currently I've got the OMNI4.4.4 on SDCard, booting from SDCard. So I have not /external_sd as a directory. So maybe I need to set something as mountpoint (if so - how?) or have to copy the ROM ZIP to another place?
Click to expand...
Click to collapse
It is a bad copy
you can't copy files on recovery
go to bada or with ram reader and copy .zip
after go to recovery and install rom
nima.yavari said:
It is a bad copy
you can't copy files on recovery
go to bada or with ram reader and copy .zip
after go to recovery and install rom
Click to expand...
Click to collapse
Already tried this (copied within Bada) when I posted/edited my entries above - the error keeps the same - I cannot install this ROM (I used the one from V1.1 download)! Do I have to copy it on a certain place?
I took the OMNI4.4.4 from here (German only) which leaves Bada unharmed and completely runs from SD card. I managed to install that version again after wiping but whenever I try to install the version from here I get this very long cryptical error message from above (the one ending with "operation not supported on transport endpoint").
Since the boot.img of OMNI4.4.4 is different from the one contained in the OMNI5.0.2 here. Do I have to extract and copy it manually before trying to flash this rom here?
Ok, tried that but it damaged Bada installation and also Android did not work anymore. Had to flash a Bada update version and my previous OMNI4.4.4 FOTA to restore everything.
Any hints appreciated (cannot get rid of this cryptic error)!
Renth said:
Already tried this (copied within Bada) when I posted/edited my entries above - the error keeps the same - I cannot install this ROM (I used the one from V1.1 download)! Do I have to copy it on a certain place?
I took the OMNI4.4.4 from here (German only) which leaves Bada unharmed and completely runs from SD card. I managed to install that version again after wiping but whenever I try to install the version from here I get this very long cryptical error message from above (the one ending with "operation not supported on transport endpoint").
Since the boot.img of OMNI4.4.4 is different from the one contained in the OMNI5.0.2 here. Do I have to extract and copy it manually before trying to flash this rom here?
Ok, tried that but it damaged Bada installation and also Android did not work anymore. Had to flash a Bada update version and my previous OMNI4.4.4 FOTA to restore everything.
Any hints appreciated (cannot get rid of this cryptic error)!
Click to expand...
Click to collapse
full flash bada
format memory to fat32
flash fota and start kernel and bootfile JUST for this rom
now go to recovery Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back ->wipe every thing without external ->Swipe to wipe
now you can install rom
nima.yavari said:
full flash bada
format memory to fat32
flash fota and start kernel and bootfile JUST for this rom
now go to recovery Advanced -> Terminal Command -> Select -> Type "sh partition.sh"
Wait before on screen you will see "Partitions had been prepared"
Back -> Back -> Back ->wipe every thing without external ->Swipe to wipe
now you can install rom
Click to expand...
Click to collapse
Meanwhile I already did so. Partitioning worked, installation worked but after reset Wave only shows its startscreen (Samsung Wave GT-S8500 in white letters) for about 15 minutes now and nothing happens (besides Wave getting really warm, nearly hot). Also restarting the wave does not change anything!
Anything else I can try? Do I have to checkmark Master Rom in Multiloader?
Renth said:
Meanwhile I already did so. Partitioning worked, installation worked but after reset Wave only shows its startscreen (Samsung Wave GT-S8500 in white letters) for about 15 minutes now and nothing happens (besides Wave getting really warm, nearly hot). Also restarting the wave does not change anything!
Anything else I can try? Do I have to checkmark Master Rom in Multiloader?
Click to expand...
Click to collapse
sure flashed fota this rom?
wave 1 or 2?
nima.yavari said:
sure flashed fota this rom?
wave 1 or 2?
Click to expand...
Click to collapse
It is Wave 1. Yes I flashed all 3 parts: Bootfiles, FOTA and kernel. But not sure what to checkmark in Multiloader. Decided to go with Master Rom.
Meanwhile tried a 2nd time with full flash of bada + the wipe you mentioned (but no formatting of SD since it already has been for OMNI4.4.4). Still no change. Everything worked fine but Wave stays in Start Screnn (Samsung Wave GT-S8500 in white letters) for 20 minutes now - just getting very warm.
And now? Doesnt seem to work for my devive.
Renth said:
It is Wave 1. Yes I flashed all 3 parts: Bootfiles, FOTA and kernel. But not sure what to checkmark in Multiloader. Decided to go with Master Rom.
Meanwhile tried a 2nd time with full flash of bada + the wipe you mentioned (but no formatting of SD since it already has been for OMNI4.4.4). Still no change. Everything worked fine but Wave stays in Start Screnn (Samsung Wave GT-S8500 in white letters) for 20 minutes now - just getting very warm.
And now? Doesnt seem to work for my devive.
Click to expand...
Click to collapse
to multiloaeder just chek bootfile / rc1 / fota
nima.yavari said:
to multiloaeder just chek bootfile / rc1 / fota
Click to expand...
Click to collapse
For flashing bootfiles you need either checkmark "Boot Change" or "Full Download" in Multiloader. Otherwise Boot will be grayed out.
But as said - already did so 2 times: Flash Bada (Full flash at 2nd time), wiped everthing (2nd time) partitioned everything, flashing omni5.0.2. Everything worked but wave1 stays in Startscreen forever afterwards. Neither bada nor android starts at all.
Any idea on how I can support hunting down this problem?

Categories

Resources