Hi there,
I just flashed my SGS with a new kernel ( speedmod kernel K13C ) and tried multiple roms (Darkys and Ultibread).
The major problem is that on the Ultibread rom my data connectivity doesn't work. It just won't show up, which is a real pain because I'm tethering my 3G to my PC.
With the Darkys rom, the 3G fixed itself. But now I'm having issues with the internal storage, which shows up as 0,00b. Also, i can't unmount/remount the internal SD. A format doesn't help either.
The flashing procedure I followed is like this:
Used Odin to flash the kernel.
I put the new rom on the root of the SDcard using update.zip as it's name and then flashed it at the recovery menu.
I hope someone can help me out with my (one day old) SGS!
I'm guessing you flash BETA stock JV1 before?
JV1 contains new sbl.bin and boot.bin (i'm not sure if GB sammy custom ROM had it), so if you flashed it, most likely you have messed your bootloader, and it'll give you the bug you have right now. (kinda...with some people, external-sd won't mount not internal sd)
The only way to fix it is, you need to flash another ROM which had old sbl.bin/boot.bin with re-partition. Some people stated JPO and JM2 eclair can fix this.
Regarding your data connection, have you check you APN settings. If the problem persist, you should post your issue in related thread. Goodluck
Hope it helped.
PS. Here's one for some reference
I upgraded from a stock Froyo installation to the current setup (Speedmod + Darkys).
I also had the graphical glitch (bootloader fail?) with the Ultibread rom.
But i'll try to go back to the stock 2.1 eclair rom and then retry the entire procedure.
Yay for being a noob at Android flashing
Edit:
Almost forgot. My USB Mass storage mode is also not functioning using Darkys rom..
But i'll try to go back to the stock 2.1 eclair rom and then retry the entire procedure.
Then dont use the roms that give you so much trouble .Go to the rom kitchin and build your own less problems that way .
http://forum.xda-developers.com/showthread.php?t=817703
jje
Hi. I was running CM7 fine and then flashed MIUI last night and now i can't change the kernel or modem no matter how many times i try and flash in clockwork or clear caches or factory reset. I've lost cell network completely. Wifi works interestingly. Any ideas?
Anyone got any ideas how to fix this so I can actually flash new modems and krnels? They show as successfully flashing in CWM but About Phone doesnt change!
Would love to avoid going to sto ck via Odin if I can.
Th an ks
TheMathMan said:
Anyone got any ideas how to fix this so I can actually flash new modems and krnels? They show as successfully flashing in CWM but About Phone doesnt change!
Would love to avoid going to sto ck via Odin if I can.
Th an ks
Click to expand...
Click to collapse
what modem and kernel are you trying to flash. you need the update .zip to be designed for gingerbread, different scripting for gb. so the kernel shouldn't be a problem unless you are trying to revert to 2.2.
im not sure if gingerbread is weird but maybe you can extract the zimage and modem.bin you are trying to flash and archive them in .tar files and odin flash. as long as you are not flashing anything with boot.bin or sbl.bin it shouldn't break the ability to odin back to stock.
A word of caution: If u get on GB kernel, and go to recovery, and try to use these kernel zips to flash back, they won't work. I realized this the hard way last night.
diablo009 said:
A word of caution: If u get on GB kernel, and go to recovery, and try to use these kernel zips to flash back, they won't work. I realized this the hard way last night.
Click to expand...
Click to collapse
if you read any cm7 or other gingerbread thread they say you need 3 button recovery/download. this is one reason why! i think there should be a generic froyo kernel in the proper type of update file to revert. but maybe they are trying to scare away newbs till they complete cm7 or atleast have a release candidate.
Sorted in the end.
I just formatted every partition in Mounts and Storage first before a reflash.
Sent from my Armani S i9010 (CM7)
I am currently running a stock XXJVQ firmware with Galaxian 2.1 kernel installed. I have a few backups to it made in CWM.
My question is - if I try to flash Darky's ROM, will I lose CWM and all the backups I made to my previous ROM?
Also - it says that I should have lagfix turned on before trying to flash Darky's ROM. I used the CF tool to convert all my rfs memory to ext4. I suppose that's the same as a lagfix, meaning that I already have my lagfix turned on, right?
vladbaca said:
I am currently running a stock XXJVQ firmware with Galaxian 2.1 kernel installed. I have a few backups to it made in CWM.
My question is - if I try to flash Darky's ROM, will I lose CWM and all the backups I made to my previous ROM?
Also - it says that I should have lagfix turned on before trying to flash Darky's ROM. I used the CF tool to convert all my rfs memory to ext4. I suppose that's the same as a lagfix, meaning that I already have my lagfix turned on, right?
Click to expand...
Click to collapse
your nandroid backups will remain intact, and just use cf tool to convert back to lagfix disabled(all on rfs) and you should be set to go....remember to follow darkys instructions to the word and then you should have no problems....happy flashing
Hi there,
I have the stock JVQ flashed via odin from samfirmware, I would really like to use this rom. However, I was following the steps documented on this link which was successful (I reverted back to the rom on this page just to make things simpler, and to ensure that there wern't going to be any glitches):
http://www.darkyrom.com/community/index.php?threads/guide-installing-stock-rom-gt-i9000-only.486/
and then started to follow this:
http://www.darkyrom.com/community/i...rkys-rom-on-2-2-2-2-1-i9000-i9000m-only.1041/
However got to part 2, and the kernel flash didn't work (didn't get the dark core recovery part written on the recovery screen). So I clicked on the 'Alternate Method to Get Working Kernel' and the links dead!
Is there another method I can follow step by step, I currently have no root on the phone, but I can easily root using CF root if that helps, however previously I found no lagfix option! I'm completely a noob at this so any help would be appreciated...I want to try the rom that everybody's talking about
Many Thanks
slaphead20 said:
your nandroid backups will remain intact, and just use cf tool to convert back to lagfix disabled(all on rfs) and you should be set to go....remember to follow darkys instructions to the word and then you should have no problems....happy flashing
Click to expand...
Click to collapse
If you flash 10.2 Resurrection Edition you don't have to worry about lagfix on or off!
It will give you a CLEAN, FAST phone.
From there you can install, tweak, modify to your hearts content!
mitster said:
Hi there,
I have the stock JVQ flashed via odin from samfirmware, I would really like to use this rom. However, I was following the steps documented on this link which was successful (I reverted back to the rom on this page just to make things simpler, and to ensure that there wern't going to be any glitches):
http://www.darkyrom.com/community/index.php?threads/guide-installing-stock-rom-gt-i9000-only.486/
and then started to follow this:
http://www.darkyrom.com/community/i...rkys-rom-on-2-2-2-2-1-i9000-i9000m-only.1041/
However got to part 2, and the kernel flash didn't work (didn't get the dark core recovery part written on the recovery screen). So I clicked on the 'Alternate Method to Get Working Kernel' and the links dead!
Is there another method I can follow step by step, I currently have no root on the phone, but I can easily root using CF root if that helps, however previously I found no lagfix option! I'm completely a noob at this so any help would be appreciated...I want to try the rom that everybody's talking about
Many Thanks
Click to expand...
Click to collapse
As the above poster said, just flash Darky 10.2 RE instead. You can flash it with Odin regardless of the ROM you have before. Just follow the guide on this page:
http://www.darkyrom.com/community/index.php?threads/odin-darkyrom-10-2-resurrection-gt-i9000.4272/
does this rom work on m110s (korean I9000).. is there anyone who tested it?
I've been asking for help after screwing up my Tab while trying to restore my Roto Backup with Odin, and the thread has been completely quiet.
I just wanted to ask an easier question, and see if that might tell me everything I need to know: Has anyone other than rotohammer ever actually successfully restored their Roto Backup? Second question, has anyone, including rotohammer, ever restored their Roto Backup with Odin?
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
Thanks for the help. So you've managed to get your Roto Backup to work before?
So if I can't flash a bootloader from Roto backup, how do you recommend I flash back to the Froyo bootloader?
Also, any recommendations on a Froyo standard stock firmware image I can flash safely on an AT&T tab?
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
and
I'll explain
=-=-=-=-=-=
I got 2 Tab's same STOCK ROM's...
on one of them installed overcome...
then i took roto backup the other and restored with odin on the overcome..
wait wait... i restored a stock GB from samfirm first and then used my Froyo backup...
kinda the same like you explained not to do... and guess what?!
tab died needed jtag... after jtag they gave me back the tab with stock froyo from samfirm...
now i'll explain
=-=-=-=-=-=-==
i restored again my backup with odin and original rom is now installed perfectly.. i did had an error when it reached boot.bin though..
but i restarted the tab and it's up and running...
too bad i didn't saw your message before...
i just have a question..
so lets say i'm now in overcome.. want to install 2.2
you say that i'll should use lets say stock rom from samfirm
with odin... with p1 pit file
check repartition, areboot, freset and start...
when done restore using my backup created using RB
with odin... areboot, freset and start (pda with the tar file and no pit)
but in the 'tar' file not to include boot.bin and SBL.bin files? just those files?
sorry for bad english...
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
nevermind it's working...
cymagnus said:
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
Click to expand...
Click to collapse
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
avishai0528 said:
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
Click to expand...
Click to collapse
I have a Roto Backup, made from my own tab right after I got it, just no stock AT&T ROM to use as a base.
manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
That is correct. The backup made does not contain all the files.
DarkPal said:
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
Click to expand...
Click to collapse
I've done some research based on your recommendations. JK5 is actually no good I think, since it isn't a full ROM, and can't be used to re-partition.
JJ4, however, worked a charm. I downloaded it from samfirmware.com, and it came with all files necessary in the rar. Re-flashed pit, pda, modem and csc. Everything booted up as expected in Russian.
Then I used my Rotobackup, and re-flashed my pit and pda.
For the most part, everything is working, and restored, but for whatever reason, the boot animation is missing, and after the Galaxy Tab screen, it just turns black, and then after a while if I turn the screen off and on, I find it's already booted up (but booted with screen off). Any thoughts on why this occurs or how I can fix it?
My situation is that I'm increasingly beginning to suspect that my data connection is fritzy because of a hardware defect. I was on Overcome, and the data would just not be working when I turned on the Tab. The symptoms are one of the following: (1) data shows as connected and you can see the Tab sending but not receiving on the status bar, or (2) data shows as disconnected and then will show as connected for a moment and then show as disconnected again, or (3) data shows as disconnected, period. To fix any of these, I would have to either cycle the data or sometimes re-select the APN and reboot and then it would work. I then flashed to and used JPE for a few days, and observed today that my data showed as connected but would only send and not receive until I cycled the packet data setting.
Flashing back to stock, which I've now (mostly) done, is pretty much a last resort. I want to confirm whether this problem still exists on stock firmware, and if it does, I want to be in a condition to send in my Tab for repairs.
Just an update, I found this thread, which sounded a lot like my problem:
http://forum.xda-developers.com/showthread.php?t=899196
However, flashing jj4_bootloaders hasn't helped my missing logo problem. There is sound now, but still a black screen on bootup.
and none from samfirm are working? couldnt be.
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
cymagnus said:
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
Click to expand...
Click to collapse
As with the people that had the white line problem, with the corrupted graphics on the bootloader, I can't see recovery, just a black screen.
Under settings is reporting wrong kernel and no baseband. I recently flashed back to stock and then to a few roms. my bootanimations always shows semaphore kernel when booting up altough i have used roms with icy glitch and now flashed corn. My settings/about still refelect sema kernel so do the boot animations. The semaphore kernel came from the first rom i flashed about go back to stock. It seems stuck on there somehow. any ideas?
ODIN
Hey there! To me it sounds like you need a complete wipe through ODIN. Find any ODIN ROM (Darky ROM is the one i am most familiar with) and flash the Odin Package with the "wipe" option ticked. This will clean up your phone entirely (except for SD card, so you can backup your apps to that with titanium backup) and flash it, works wonders =) Good luck! Let me know if you need any help with ODIN