Related
Hi. I recently tried to update my rom to on from the rom kitchen and something didnt work. so after waiting 1.5h on the boot screen i opened clockwork and tried to restore a backup I made right before flashing. The thing is that what ever I do I always end up booting into clockwork again.
I did not disable lagfix prior to first flash and now I cant because it reboots to clockwork.
Anyone have an idea, or solution? Can I install another rom through odin with my ext4 lagfix on?
in clockwork do a factory reset and also clear cache and so on.
go and flash a stock rom thru odin from here http://forum.xda-developers.com/showthread.php?t=846913 and then start all over again
providing you have download mode you should be ok
Thanks!
Are you shure that I can flash a stock rom on a ext4 filesystem? everyware I read thay say I must disable lagfix before start
If you want to return to RFS by default just flash a stock ROM and then do a wipe/factory reset into Recovery 3e.....it should work (it works for me! XD)!
Should re partition be on in odin?
only if you have all 3 files, if not dont use pit or re partition. flashing a stock will erase the ext4 and convert back to rfs so dont fret about that.
ideally you would want a 3 file firmware so you can re partition but most firmwares now only come in 1 file, so you may need to dig a little deeper if the 1 file doesnt fix your problem. i've never had to use a 3 file firmware so i couldnt direct you to one sorry.
if you really want the 3 file + pit + repartition on samfirmware.com there is the JS3 in Yellow.....it's the 3 file rom with pit and repartition!!
simone201 said:
if you really want the 3 file + pit + repartition on samfirmware.com there is the JS3 in Yellow.....it's the 3 file rom with pit and repartition!!
Click to expand...
Click to collapse
cheers man, il get downloading that too,, ya never know when summit like that comes in handy... (luckily) iv'e still yet to brick my phone... at least il have this to bring it back to life
I think it was released a few weeks ago.....
I used it last week and it was perfect!! Better than Darky's Resurrection!!
Hi! I'm planning to install custom rom on my sgs gt-i9000 by Darky (either 9.5 or 10 RC).
But Darky uses DarkCore as kernel, and I want to use speedmod kernel (as I understood this one of the best kernels out there).
What is the right process to install this?
Flash the kernel via odin (PDA right?) the use Darky's Rom Configuration with "Skip Kernel" and then use recovry to install the ROM?
Also can I stay with my current modem which is I9000XXJPY? I really afaird to flash the modem (and CSC).
One last question is how to backup my current kernel/modem/csc/rom?
Also as I understood I need to backup /efs right? Is there something else I need to backup (my contacts are saved on the sim card so I dont mind loosing those and I dont mind loosing my current applications and their settings).
Thanks a lot!
if you are not rooted, get rooted !!
download CF-Root, or speedmod kernel, flash it through ODIN and make a full nandroid backup. Also backup efs just in case your IMEI gets corrupted.
i have used speedmod kernel with older versions of darkys roms, but voodoo kernel is recommended.. But you can try which ever kernel you like, providing you know how to fix if something goes wrong.
you can skip modem in the darky app if you are happy with your current modem.
and once you install cf-root or speedmod you will be rooted, so download 'titanium backup' from the market and that will back up all your apps
1 last thing, i cannot emphasise this enough.. be sure you know how to fix a bricked phone before going ahead with the flash. i myself - along with many others - have had 'issues' with darkys roms.... I am not saying you will, but be careful and always have a current backup !!
DarkCore is based on Voodoo kernel right?
1 last thing, i cannot emphasise this enough.. be sure you know how to fix a bricked phone before going ahead with the flash. i myself - along with many others - have had 'issues' with darkys roms....
Click to expand...
Click to collapse
I dont know. What should I read?
Thanks!
yes it is
and read this http://forum.xda-developers.com/showthread.php?t=723596
if you ever get stuck in a bootloop, boot into recovery do a factory reset.
if you have serious issues, boot into recovery, do a factory reset along with formatting, cache / data / system, then re flash.
if you have even more serious issues, then you need to boot into download mode and flash a 3 file stock rom with 512 pit and re-partition checked.
thats all there is to fixing a bricked phone. Always make sure 3 button combo works before taking on any sort of flashing.
Thanks a lot!!
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.
Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.
Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?
btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?
N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.
Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]
Was in the process of IMEI repair. (Just for reference.)
My phone use to be rooted and on a custom rom. It was previously reverted back to stock DOK2 5.1.1. My phone cannot be flashed anymore for some reason. I cant even flash the DOK2 file that goes in AP. I tried flashing the trlte pit file and now my phone doesn't boot past the T-Mobile logo. I think im missing some files to do a full ODIN flash.
U need to flash trltetmo pit file. Trlte is for N910F I believe and I think it's 16gb internal sd. U need to flash 100% stock dok2 with the pit file and make sure repartition is checked. If it fails....try renaming the .tar.md5 to just .tar (remove md5) for some reason I can't flash stock any other way
Karina Kapri said:
Was in the process of IMEI repair. (Just for reference.)
My phone use to be rooted and on a custom rom. It was previously reverted back to stock DOK2 5.1.1. My phone cannot be flashed anymore for some reason. I cant even flash the DOK2 file that goes in AP. I tried flashing the trlte pit file and now my phone doesn't boot past the T-Mobile logo. I think im missing some files to do a full ODIN flash.
Click to expand...
Click to collapse
I don't have a specific answer to your problem, but make sure you try and wipe the cache as well. I remember having a situation where I was trying to flash my device back to stock and it was bootlooping. The problem ended up being that I hadn't properly wiped everything from the custom ROM I had been on.