Related
I have a SGS GT-I9000 rooted n a ICS ROM
but when i tried to restore my default ROM back with CWM it got stuck on boot splash screen.
I also tried flashing the same kernel again but it didnt worked.
And when i boot into recovery mode it gives me errors like
E:can't mount/cache/recovery/log
E:can't open/cache/recovery/log
E:unknown volume for path[/cache/recovery/last_log]
and so on......
any solution anybody????plss.......
Hi.
You can't restore your old gingerbread stock from ICS via nandroid.
You must flash the Stock ROM with Odin.
Befor that maybe you can flash the ICS kernel again and boot into ICS, then backup your clockworkmod folder via USB. After the Backup flash a stock ROM and cf-root or semaphore 2.5.0 via Odin.... after that load your clockworkmod folder to your internal SD-Card and boot into CWM. Now you can restore your Backup from gingerbread.
Sorry for my poor english. I hope you understand me.
// use the semaphore 0.8.1 kernel for ics. Than boot your phone and save the clockworkmod folder. When dosn't work, 1. flash the stock ROM 2. flash cf-root 3 boot in cwm go to restore and look for the backup... it must be in there
daggi78 said:
Hi.
You can't restore your old gingerbread stock from ICS via nandroid.
You must flash the Stock ROM with Odin.
Befor that maybe you can flash the ICS kernel again and boot into ICS, then backup your clockworkmod folder via USB. After the Backup flash a stock ROM and cf-root or semaphore 2.5.0 via Odin.... after that load your clockworkmod folder to your internal SD-Card and boot into CWM. Now you can restore your Backup from gingerbread.
Sorry for my poor english. I hope you understand me.
// use the semaphore 0.8.1 kernel for ics. Than boot your phone and save the clockworkmod folder. When dosn't work, 1. flash the stock ROM 2. flash cf-root 3 boot in cwm go to restore and look for the backup... it must be in there
Click to expand...
Click to collapse
Thanx mate thanx a lot
u saved my mobile from dying.
You're welcome.
my act is:
1. do a nandroid Backup of the system befor flash a new one.
2. Save the hole Backup folder on my PC and rename it like " system_old_date "
3. Flash the new system.
4. do a nandroid backup from the new system.
5. Save the hole Backup folder on my PC and rename it like " system_new_date "
With this 5 steps I'm always on the safe side.
i do the same but this time dont kno how but it went wrong and those errors poped out
Sent from my GT-I9100 using XDA App
I think:
The problem is ICS and Gingerbread are differnet systems, with different Kernels and paths.
When you start the restoreprocess the systemdata will be restored but not the kernel with CWM. Both systems have different paths, and so you get this error.
Please correct me if I'm wrong.
daggi78 said:
I think:
The problem is ICS and Gingerbread are differnet systems, with different Kernels and paths.
When you start the restoreprocess the systemdata will be restored but not the kernel with CWM. Both systems have different paths, and so you get this error.
Please correct me if I'm wrong.
Click to expand...
Click to collapse
may be ,but it didnt happned when i restored my SGS2 from CM9 to my rooted kernel
it only happned in my SGS
Sent from my GT-I9100 using XDA App
That's strange. Perhaps a developer knows why that is?
Reflash
Perhaps, the instruction to installing ICS states that you should have done a full wipe (data + partition) and installed the ROM/Kernal again. It would have worked...anyways you are back on GB, enjoy
I have the wifi only 7310 model of the 8.9
Overcme CwM Recovery 5.1.2.6
ROM was Galaxian Soup AOSP 1.6
My tablet resets during recovery. Half through a data wipe ROM install ROM backup or ROM restore it will reset and reboot.
It first happened when i booted into recovery and triedROM issue. to make a back up of m y current ROM and attempt to flash the aokp one. It reset during the backup process.
It shouldn't be a ROM issue. My tablet did this once before, it would reset when i did anything involvng dataon an Overcome ROM i think. Data wipe/backup etc. I left it alone while the ROM still worked and tried again a week later with no issues.
Any ideas? Now i have a soft brick that cant boot past the Samsung Screen. I can get into recovery and download modes.
EDIT* added a video
EDIT2:
The issue was solved.
What ended up happening what i attempted to flash back to stock software, ODIN would stall during the system.img. From this point i thought it was done, but i could still get into the stock recovery, i used the stock recovery to wipe the data after several failed attempts in a similar manner to this video.
One day it just worked. I could finally wipe data and cache without a reset. But i could't flash a file because ODIN would still freeze on the system.img. It was suwandiapr who showed me his walkthrough to push an file to recovery from adb. Thank you so much
I do NOT know why it my tablet/recovery starting resetting when i wanted to do a data/cache wipe/restore or why it decided to start doing it again. I tried the 5.5 cwm, the overcome 5.1 and the stock and none of them worked. Today i tried it on an off chance of boredom and it started working again. It is a confusing situation but that is what happened.
Again that you so much to Mr.Home and especially suwandiapr for all your help
> If you had a back up you can do advanced restore of just your system partition to get you tablet back on, though you will probably still have problem with the recovery
> If not, download the stock firmware tar.
Boot up to download mode using the power + vol combo.
flash the stock tar through odin.
boot up to download mode again.
this time flash the cwm recovery.
boot up to recovery mode.
wipe dalvikcache and data.
install aokp and gapps.
if it fails (cwm recovery stuck and reboots by itself during wiping /data partition or dalvik cache)
,chances are your data partition had been corrupted.
You can try fixing this by reflashing the stock firmware tar through odin again
just this time you need to have re-partition ticked.
and repeat above steps.
Take note that this will format the content your sd card too apart from the /data partition
EDIT: Please post this on the general section next time
MrHome said:
> If you had a back up you can do advanced restore of just your system partition to get you tablet back on, though you will probably still have problem with the recovery
> If not, download the stock firmware tar.
Boot up to download mode using the power + vol combo.
flash the stock tar through odin.
boot up to download mode again.
this time flash the cwm recovery.
boot up to recovery mode.
wipe dalvikcache and data.
install aokp and gapps.
if it fails (cwm recovery stuck and reboots by itself during wiping /data partition or dalvik cache)
,chances are your data partition had been corrupted.
You can try fixing this by reflashing the stock firmware tar through odin again
just this time you need to have re-partition ticked.
and repeat above steps.
Take note that this will format the content your sd card too apart from the /data partition
EDIT: Please post this on the general section next time
Click to expand...
Click to collapse
Sorry for the wrong section, it didn't seem like a general question to me. How do i use ODIN?
bdfull3r said:
Sorry for the wrong section, it didn't seem like a general question to me. How do i use ODIN?
Click to expand...
Click to collapse
Download Odin 1.85
Install Samsung USB drivers (should come with Kies)
Download stock firmware from samfirmware
Check the box beside PDA
Put the .md5 file into the PDA slot
Leave all other options on defaults
Put tablet into Download Mode (power and vol -, select the one that isn't recovery)
Connect it to your PC
Press START in Odin
Wait ~10 minutes
NOTE: this shouldn't wipe the internal sdcard. if you need to wipe that, select repartition and give Odin a PIT FOR THE P7310/7300 MAKE SURE IT'S THE RIGHT ONE OR YOU WILL BRICK BADLY.
Moved To General​
I understand this might be a development related question, but questions do not belong here.​
im still bricked so if ANYONE has any ideas please let me know.
Do you have a backup of yours in computer? If yes.. Push your file to device with adb...
Or replace with cwm 5.5.0.4.. ( if you not familiar with odin)
From cwm recovery 5.1.2.6 mount your /data and /system..
After that push your file (cwm 5.5.0.4. Zip and your backup file) to sdcard trough adb
Install cwm 5.5.0.4 from your recovery..then reboot..
Before you install your backup file.. Try to wipe and reboot your phone.. If problem still exist.. Your assumption about ROM may right.. But if your booting problem disappear.. I think its because yor recovery..
suwandiapr said:
Do you have a backup of yours in computer? If yes.. Push your file to device with adb...
Or replace with cwm 5.5.0.4.. ( if you not familiar with odin)
From cwm recovery 5.1.2.6 mount your /data and /system..
After that push your file (cwm 5.5.0.4. Zip and your backup file) to sdcard trough adb
Install cwm 5.5.0.4 from your recovery..then reboot..
Before you install your backup file.. Try to wipe and reboot your phone.. If problem still exist.. Your assumption about ROM may right.. But if your booting problem disappear.. I think its because yor recovery..
Click to expand...
Click to collapse
I've tried switching recoveries, the device still resets like in the video posted above
bdfull3r said:
I've tried switching recoveries, the device still resets like in the video posted above
Click to expand...
Click to collapse
I never try it before.. how about stock recovery? It will wipe your data partition include SD card..But it worth to try if you dont like ODIN..
here is the zip version..Instal from recovery..
Edit: Do with your own risk..
After looking at the video, I noticed something similar that had happened to me before.
It happened when I tried to wipe the "cache" first, instead of wiping only the "dalvik cache".
After that, whenever i tried to wipe the dalvik cache/reset factory data,
the recovery reboots by itself halfway through.
MrHome said:
After looking at the video, I noticed something similar that had happened to me before.
It happened when I tried to wipe the "cache" first, instead of wiping only the "dalvik cache".
After that, whenever i tried to wipe the dalvik cache/reset factory data,
the recovery reboots by itself halfway through.
Click to expand...
Click to collapse
But how do i fix it?
bdfull3r said:
But how do i fix it?
Click to expand...
Click to collapse
Check the thread in my signature on the ODIN How-To, Drivers (no Kies/Bloat needed for drivers) and more. If I were you I'd ODIN so the Stock Recovery is restored in place. Looks like something went wrong in your CWM Recovery's installation (could be a bad download you had, it happens). All the files you need (except for the ODIN image) are in my General Guide.
nirogu325 said:
Check the thread in my signature on the ODIN How-To, Drivers (no Kies/Bloat needed for drivers) and more. If I were you I'd ODIN so the Stock Recovery is restored in place. Looks like something went wrong in your CWM Recovery's installation (could be a bad download you had, it happens). All the files you need (except for the ODIN image) are in my General Guide.
Click to expand...
Click to collapse
Its not the recovery, i have changed recoveries two or three times now through ODIN and they all perform the same way
bdfull3r said:
But how do i fix it?
Click to expand...
Click to collapse
Well, i just don't wipe cache. Only the dalvikcache and all went well..
I have a soft brick, no memory or sd card data. I can get into recovery but i don't have any files on the tablet to flash.
Are you windows user? if yes..
Just like my answer from previous post.. See page one!
Mount your /system and /data partition from recovery menu..(from cwm)
From your computer.. Use this tools for pushing the file flashable.zip to device..
After that you can flash a new rom from recovery..
http://forum.xda-developers.com/showthread.php?t=1539352
Thank you so much sir. I worked and I no longer have a brick
bdfull3r said:
Thank you so much sir. I worked and I no longer have a brick
Click to expand...
Click to collapse
Glad to hear that..
Add your thread subject with [solve] for closing the thread..
2 days ago I had to reinstal system on my Note. I decided to flash stock GB rom using odin with re-partition (SGN 16bg pit file). After that I flashed once again using stock GB rooted rom, and install CF kernel with CWM using mobile odin. Everything was fine. Next I installed a cooked rom (CleaNote v5, ). I thought that everything is fine till i decided to install TouchwixUX Launcher prepared to Note. The instalation process stucks on about 20%, I thought that maybe package is corrupted, I downloaded it again, but it didn't help, so I decided backup my phone using nandroid and wipe to factory data. And there is a problem:
1. I try to make a backup using nandroid, and it stops on some *.txt file and stucks. (backup include 3 files)
2. I can't do the wipe. I launched full wipe and nandroid returned a message "can't open /SDCARD/.amndroid_secure ..."
3. When I try to mount SDCARD, CWM Recovery show's the message "Cant mount SDCARD"
There is a one thing which make me sad. I tried to install CleaNote .zip by CWM Recovery once again, and instaltion process stucks to. It means that i probably wont be able to flash any other rom.
Is there any way to solve this problem?
Pre100n said:
2 days ago I had to reinstal system on my Note. I decided to flash stock GB rom using odin with re-partition (SGN 16bg pit file). After that I flashed once again using stock GB rooted rom, and install CF kernel with CWM using mobile odin. Everything was fine. Next I installed a cooked rom (CleaNote v5, ). I thought that everything is fine till i decided to install TouchwixUX Launcher prepared to Note. The instalation process stucks on about 20%, I thought that maybe package is corrupted, I downloaded it again, but it didn't help, so I decided backup my phone using nandroid and wipe to factory data. And there is a problem:
1. I try to make a backup using nandroid, and it stops on some *.txt file and stucks. (backup include 3 files)
2. I can't do the wipe. I launched full wipe and nandroid returned a message "can't open /SDCARD/.amndroid_secure ..."
3. When I try to mount SDCARD, CWM Recovery show's the message "Cant mount SDCARD"
There is a one thing which make me sad. I tried to install CleaNote .zip by CWM Recovery once again, and instaltion process stucks to. It means that i probably wont be able to flash any other rom.
Is there any way to solve this problem?
Click to expand...
Click to collapse
Can you go download mode and flash gb rom in pc odin? After flashing gb rom in pc odin if still stuck go to recovery and wipe data and cache.
The way you explained it i dont believe it is superbrick.
NO NO NO - there is no superbrick My phone works, I can connect phonr to Odin, Mobile Obin, I can run in Recovery mode, but i can't for example do a nandroid backup or ful wipe under cwm recovery. I think, that there is some problem with permition to files on SD card, but I didn't meet with that problem on other rom (I used Paranoid Android (CM9 and CM10) and there was everything fine).
The reason I wrote is that I am worry if some parts of internal memory maybe corrupted, and flashing rom using Odin/Mobile Odin may caused superbrick.
Pre100n said:
NO NO NO - there is no superbrick My phone works, I can connect phonr to Odin, Mobile Obin, I can run in Recovery mode, but i can't for example do a nandroid backup or ful wipe under cwm recovery. I think, that there is some problem with permition to files on SD card, but I didn't meet with that problem on other rom (I used Paranoid Android (CM9 and CM10) and there was everything fine).
The reason I wrote is that I am worry if some parts of internal memory maybe corrupted, and flashing rom using Odin/Mobile Odin may caused superbrick.
Click to expand...
Click to collapse
Download EMMC CHECK from google play and after you run it check your heart also.
I used eMMC Brickbug Check. Result - Congratulation, test pass.
So I understand, that if there is some bug, there is caused by software, not hardware problem and I can reflash phone using Odin.
BTW - what means "Brick Bug ? - Yes. Insane chip." ?
I change kernel from stock to CF 5.3 before flashing to CleaNote. I found some info, that this kernel (cf 5.3) is not safe. Kernel after flashing ia NoteCore 12,3. Can it be the reason why i couldn't do a full wipe?
... I almost forgot - I used TriangleAway to remove flash counter. Maybe this is a problem?
Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help
Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.
if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom
Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!
glad you solved it.. :good:
I tried an upgrade to C-ROM with its TWRP backup. I want to go back to CM11 and I have two CWM backups.
C-ROM grabs a reboot to Recovery and shows a screen with options, none of which is useful to me.
ROM manager won't install as incompatible.
Please tell me what to do?
Richard
Flash CM11 nightly and after reboot into the OS, reboot recovery and restore your backup. Optionally, you can just flash the CM11 stock kernel and reboot into its CWM recovery and restore your backup then.
Recovery on i9000 is part of the kernel, so you can totally forget ROM Manager app for flashing the recovery.
tetakpatalked from Nexus 7 flo
Thanks, I hope
tetakpatak said:
Flash CM11 nightly and after reboot into the OS, reboot recovery and restore your backup. Optionally, you can just flash the CM11 stock kernel and reboot into its CWM recovery and restore your backup then.
Recovery on i9000 is part of the kernel, so you can totally forget ROM Manager app for flashing the recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks, that sounds easy. I considered doing something like that but lacked confidence to do it.
Richard
Questions about Recovery
Richard Hallett said:
Thanks, that sounds easy. I considered doing something like that but lacked confidence to do it.
Richard
Click to expand...
Click to collapse
Hi tetapetak
I get trapped in the TWRP menu screen whenever I try to boot into Recovery. I tried Install and went to the CM zip file and was able to get to the com folder but didn't know where to go next. Should I go deeper.
While browsing I found an app called Flashify. Would that help"
I also found a youtube video Change Custom Recovery from TWRP to ClockworkMod on HTC One that sounded good but Galaxy and HTC are different.
I would have to chose between TWRP for Samsung Galaxy S2 Exhilarate SGH-i577 or TWRP for Samsung Galaxy S3 (Canada) if I wanted to follow the directions.
Richard
Richard Hallett said:
Hi tetapetak
I get trapped in the TWRP menu screen whenever I try to boot into Recovery. I tried Install and went to the CM zip file and was able to get to the com folder but didn't know where to go next. Should I go deeper.
While browsing I found an app called Flashify. Would that help"
I also found a youtube video Change Custom Recovery from TWRP to ClockworkMod on HTC One that sounded good but Galaxy and HTC are different.
I would have to chose between TWRP for Samsung Galaxy S2 Exhilarate SGH-i577 or TWRP for Samsung Galaxy S3 (Canada) if I wanted to follow the directions.
Richard
Click to expand...
Click to collapse
Don't worry mate, you will get your phone working. You can not follow the threads for other phones. HTC has separately flashable recovery, unlike the i9000 which uses the same partition for recovery and kernel. That is the reason why i9000 gets easier light-bricked, because as soon as the kernel doesn't boot also the recovery mode often won't work anymore.
The most reliable way to unbrick, tough bit longer one, is to flash a stock firmware with Odin. For downgrading to 2.3.x from 4.3+ roms using the PIT file with repartition is obligatory. So as you use KitKat (and other system partition sizes than stock) it would be easier and faster to flash just a kernel that will boot.
So, how is the situation exactly now: do you get just TWRP recovery splash screen but can not enter it? If so, please flash in download mode with Odin v.1.82 or v.1.83 the Semaphore kernel v3.4.3 with unchecked auto-reboot and unchecked re-partition (use tar file under PDA in Odin). Then turn off and reboot into the recovery with 3-buttons combo.
You will possibly can restore whole CM11 backup with Semaphore recovery if you have used CM11 stock kernel to create backup. I am not sure for that, but what would ceirtanly work would be to wipe data, cache, dalvik cache and system, to flash CM11 nightly and then reboot once into the OS and reboot recovery to restore nandroid backup.
tetakpatalked from Nexus 7 flo
Progress report
tetakpatak said:
Don't worry mate, you will get your phone working. You can not follow the threads for other phones. HTC has separately flashable recovery, unlike the i9000 which uses the same partition for recovery and kernel. That is the reason why i9000 gets easier light-bricked, because as soon as the kernel doesn't boot also the recovery mode often won't work anymore.
The most reliable way to unbrick, tough bit longer one, is to flash a stock firmware with Odin. For downgrading to 2.3.x from 4.3+ roms using the PIT file with repartition is obligatory. So as you use KitKat (and other system partition sizes than stock) it would be easier and faster to flash just a kernel that will boot.
I would be happy to get to a stock firmware. But Odin is not working well with the phone, more below.
So, how is the situation exactly now: do you get just TWRP recovery splash screen but can not enter it? If so, please flash in download mode with Odin v.1.82 or v.1.83 the Semaphore kernel v3.4.3 with unchecked auto-reboot and unchecked re-partition (use tar file under PDA in Odin). Then turn off and reboot into the recovery with 3-buttons combo.
I don't get any recovery screen now. All I get is the Samsung page.
You will possibly can restore whole CM11 backup with Semaphore recovery if you have used CM11 stock kernel to create backup. I am not sure for that, but what would ceirtanly work would be to wipe data, cache, dalvik cache and system, to flash CM11 nightly and then reboot once into the OS and reboot recovery to restore nandroid backup.
Currently I cannot do all that stuff.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
tetakpatak said:
Don't worry mate, you will get your phone working. You can not follow the threads for other phones. HTC has separately flashable recovery, unlike the i9000 which uses the same partition for recovery and kernel. That is the reason why i9000 gets easier light-bricked, because as soon as the kernel doesn't boot also the recovery mode often won't work anymore.
The most reliable way to unbrick, tough bit longer one, is to flash a stock firmware with Odin. For downgrading to 2.3.x from 4.3+ roms using the PIT file with repartition is obligatory. So as you use KitKat (and other system partition sizes than stock) it would be easier and faster to flash just a kernel that will boot.
So, how is the situation exactly now: do you get just TWRP recovery splash screen but can not enter it? If so, please flash in download mode with Odin v.1.82 or v.1.83 the Semaphore kernel v3.4.3 with unchecked auto-reboot and unchecked re-partition (use tar file under PDA in Odin). Then turn off and reboot into the recovery with 3-buttons combo.
I did this and when Odin said it was a success, the phone said it was still working. I gave up after 15 min. and tried the booting. A recovery boot or normal boot just gives me the Samsung page. The download boot gives me the still working screen. So phone still thinks it is downloading. I should mention that I was unable to get in to developer mode using tap 7 times. I read that developer mode is important with Odin
You will possibly can restore whole CM11 backup with Semaphore recovery if you have used CM11 stock kernel to create backup. I am not sure for that, but what would ceirtanly work would be to wipe data, cache, dalvik cache and system, to flash CM11 nightly and then reboot once into the OS and reboot recovery to restore nandroid backup.
I'd like to do that.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Thanks for your help. I need more.
Richard
Good progress, almost there.
Richard Hallett said:
Thanks for your help. I need more.
Richard
Click to expand...
Click to collapse
Things are going well, not perfect but well. That sticking is download position was not a problem. You just have to download something else that will complete. To use Odin (Kies didn't work) I needed a tar of a system. I tried a Samsung JB that I found on SamMobile, using Odin. It loaded are booted when complete. Got the Samsung screen and those wavy lines with music but nothing more. Tried the Recover button trick and it worked. So the phone is fixed except for picking up a tar to start and then I can recover a CM11 backup of mine.
I think I need a KK tar to get the CM11 backups to work. I did try restoring one and got an error saying that "this package is for "galaxys2.i9100 .." devices; this one is a "", There was nothing between the quotes. The tar system I used was a JB so that may be the problem.
So all I need to know of a KK tar or I could try changing the tar to a zip to please Odin.
Thanks again for your help tetapetak
Richard
Are you trying to flash a i9100 rom onto i9000? That won't have a happy end.
Richard Hallett said:
. I tried a Samsung JB that I found on SamMobile, using Odin.
Click to expand...
Click to collapse
No stock JB exists for the i9000, the last firmware was GB 2.3.6
tetakpatalked from N7100
Typo not i9000
tetakpatak said:
Are you trying to flash a i9100 rom onto i9000? That won't have a happy end.
No stock JB exists for the i9000, the last firmware was GB 2.3.6
tetakpatalked from N7100
Click to expand...
Click to collapse
That was a typo. I meant i9100 international M
More than a typo I just noticed I in the wrong group. Sorry, but I have found it to be very useful.