Dear geniuses,
I'm fairly new to these things and could really use some help. I rooted my galaxy s i-9000 which was on gingerbread(2.3.6 JW3) with CF-Root and then flashed the newest cm9.1 successfully. I then tried to flash the latest cm10.1.2 )after wiping data,cache and dalvik cache) but got a warning that the partiton layout was incompatible (status 7). I rebooted normally and everything was fine. To make it wasn't a bad download I re-downloaded cm10.1 and tried to flash it again in the exact same way, got the same warning and rebooted just like last time. However i ended up in a bootloop at the second screen which says galaxy s with cyanogenmod written under it. I can not boot into recovery but I can boot into download mode. I tried to flash back to stock but Odin is getting stuck at "Setup Connection".
Any help would be greatly appreciated
remove the battery (be sure it is fully charged!!),
wait 5 mintes, put it back and retry the flash
Try a different Odin version. May be that will help.
The Man With The Plan said:
.... I tried to flash back to stock but Odin is getting stuck at "Setup Connection".
Any help would be greatly appreciated
Click to expand...
Click to collapse
OK, don't worry, it isn't serious.
Few information/questions:
- do you use Odin version compatible with the i9000? I think 1.82 or 1.7? are for the i9000, later versions can not connect to the i9000, check that!
- as long as you have download mode, no problem. Do you have the CWM recovery mode and is it still accessible?
- it is correct, that CM10.x uses different repartitions, did you make nandroid backup of your CM9?
- if you can enter recovery mode, install zips of CM10.1.2 anyway, and right after that the gapps for android 4.2.2 and reboot, you will have CM10.1.2 on your phone.
You stuck now in bootloop only because you've erased by wiping something....your phone is just bit nervous now, don't worry
BTW, nightlies 10.1 by developer pawitp are newer than stable 10.1.2
And CM10.2 nightlies are kind of getting stable (today's nightly build seems to be excellent) and will provide you about double battery life than cm10.1x
The Man With The Plan said:
but Odin is getting stuck at "Setup Connection". Any help would be greatly appreciated
Click to expand...
Click to collapse
common error when you have KIES running in the background, meaning KIES and ODIN are trying to talk to your phone at the same time...so kill Kies.exe , KiesTrayAgent.exe, and KiesPDLR.exe using task manager .
look in My Android solutions, link below about problem 3.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
pryerlee said:
remove the battery (be sure it is fully charged!!),
wait 5 mintes, put it back and retry the flash
Click to expand...
Click to collapse
Thanks for the reply but i already tried that(using Odin). No luck
tetakpatak said:
OK, don't worry, it isn't serious.
Few information/questions:
- do you use Odin version compatible with the i9000? I think 1.82 or 1.7? are for the i9000, later versions can not connect to the i9000, check that!
- as long as you have download mode, no problem. Do you have the CWM recovery mode and is it still accessible?
- it is correct, that CM10.x uses different repartitions, did you make nandroid backup of your CM9?
- if you can enter recovery mode, install zips of CM10.1.2 anyway, and right after that the gapps for android 4.2.2 and reboot, you will have CM10.1.2 on your phone.
You stuck now in bootloop only because you've erased by wiping something....your phone is just bit nervous now, don't worry
BTW, nightlies 10.1 by developer pawitp are newer than stable 10.1.2
And CM10.2 nightlies are kind of getting stable (today's nightly build seems to be excellent) and will provide you about double battery life than cm10.1x
Click to expand...
Click to collapse
Firstly thanks for the useful reply
-I am currently using 1.85 which i used to flash stock and cf-root mutliple times .I'll try downgrading and let you know,
-Yes i did make a nandroid but I cant enter recovery, thats the whole problem
I'll be sure to try them once you guys help me sort this out
xsenman said:
common error when you have KIES running in the background, meaning KIES and ODIN are trying to talk to your phone at the same time...so kill Kies.exe , KiesTrayAgent.exe, and KiesPDLR.exe using task manager .
look in My Android solutions, link below about problem 3.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Click to expand...
Click to collapse
kies is diabled on startup but i will try uninstalling it. Thanks
btw big fan of your work
Just fyi: if you flash cm10 over cm9 you have to flash twice without leaving the recovery.
Sent from my GT-I9000 using xda app-developers app
The Man With The Plan said:
kies is diabled on startup but i will try uninstalling it. Thanks
btw big fan of your work
Click to expand...
Click to collapse
It is good idea to uninstall Kies, but be careful as sometimes Kies uninstalls Samsung driver as well. That's why be sure you still have Samsung mobile driver on your PC....
You can download the driver on many sites in www
The Man With The Plan said:
-I am currently using 1.85 which i used to flash stock and cf-root mutliple times
Click to expand...
Click to collapse
Yep... it was wrong version for your needs, you need Odin v1.82 or v1.83.
Also several of 1.7x work well, but try to use the newest version for i9000: 1.83
Ver 1.85 is newer generation and it is made for SGS2 and other, newer devices
For some things it will work, for others not. I didn't know myself about it for long time and I was wondering why my flashing didn't work sometimes.....
1.82 worked just always for my i9000
tetakpatak said:
Yep... it was wrong version for your needs, you need Odin v1.82 or v1.83.
Also several of 1.7x work well, but try to use the newest version for i9000: 1.83
Ver 1.85 is newer generation and it is made for SGS2 and other, newer devices
For some things it will work, for others not. I didn't know myself about it for long time and I was wondering why my flashing didn't work sometimes.....
1.82 worked just always for my i9000
Click to expand...
Click to collapse
Thanks for your reply it was really helpful.I installed 1.82(couldnt find a link for 1.83) and tried flashing with it. It got past setupconnection and odin registered it as pass however the phone did not reboot but gave me a recovery 3e screen with multiple errors(which i have attached). When i rebooted it started at the galaxy s screen, then showed me the boot animation that says 3 uk(the carrier whom this phone was previously locked to). After that it showed me the screen with the animated s and after a minute or two it went back to the 3uk animation(and repeats). I can access download mode and 3e recovery but the recover is giving a few errors. Any ideas? Anyone?
This seems similar http://forum.xda-developers.com/showthread.php?t=1432915 but what should i do, i really dont want to make things worse again.
The Man With The Plan said:
Any ideas? Anyone?
This seems similar http://forum.xda-developers.com/showthread.php?t=1432915 but what should i do, i really dont want to make things worse again.
Click to expand...
Click to collapse
just flash the dbdata.rfs file in the link ,
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
trying to fill up 10 post required , sorry
xsenman said:
just flash the dbdata.rfs file in the link ,
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Click to expand...
Click to collapse
Thank You so much for your help but unfortunately I'm a noob so i don't know how to. Should i flash it as pda in odin? Should I flash stock rom after, before or not at all? Should I keep the reboot box checked? I'm sorry for wasting your time like this but if you could provide detailed instructions i would be forever grateful
The Man With The Plan said:
Thank You so much for your help but unfortunately I'm a noob so i don't know how to.
Click to expand...
Click to collapse
Don't worry, mate. Flashing seems to have been successful, it's just some trash ROM that you've got. It is now probably unrooted so of course you have stock recovery.
Find some other 2.3.6 rom and flash it via Odin 1.82 same way (if it is after unzipping only one file, set it under PDA, reboot checked, repartition UNCHECKED) if the ROM is OK then you will just flash rooted kernel Semaphore that features CWM recovery already.
Let know what happened. If you don't quote my text I don't get notification that you have answered.....
______________________________
Sent from my amazing i9000
powered by pawitp's CM10.2
The Man With The Plan said:
Dear geniuses,
I'm fairly new to these things and could really use some help. I rooted my galaxy s i-9000 which was on gingerbread(2.3.6 JW3) with CF-Root and then flashed the newest cm9.1 successfully. I then tried to flash the latest cm10.1.2 )after wiping data,cache and dalvik cache) but got a warning that the partiton layout was incompatible (status 7). I rebooted normally and everything was fine. To make it wasn't a bad download I re-downloaded cm10.1 and tried to flash it again in the exact same way, got the same warning and rebooted just like last time. However i ended up in a bootloop at the second screen which says galaxy s with cyanogenmod written under it. I can not boot into recovery but I can boot into download mode. I tried to flash back to stock but Odin is getting stuck at "Setup Connection".
Any help would be greatly appreciated
Click to expand...
Click to collapse
if closing kies not work,try to reboot your pc.
that works for me :good:
The Man With The Plan said:
....so i don't know how to. Should i flash it as pda in odin?
Click to expand...
Click to collapse
Yes, xsenman has sent you dbdata as direct download link. Just flash it in Odin 1.82 as PDA
If still crappy ROM angers, do further as in my previous post.
tetakpatak said:
Yes, xsenman has sent you dbdata as direct download link. Just flash it in Odin 1.82 as PDA
If still crappy ROM angers, do further as in my previous post.
Click to expand...
Click to collapse
First thanks for all your help, i would not have been able to get till here without it. I dont think the problem is with the rom because i flashed it twice, with both times being successful before all this (with a wrong version of odin).This file seemed to work for some people at the link i gave so I think I'll try it in a few hours. Just to be sure i shouldnt flash something else, before,after or during right?
The Man With The Plan said:
Just to be sure i shouldnt flash something else, before,after or during right?
Click to expand...
Click to collapse
yes, just flash dbdata.rfs (select the file under PDA in Odin3, do not tick anything else, and press start) .
its basically. clearing the data partition, which seems to be the problem that you had posted in your screenshot.
sorry I did not post all the details last night, as I wanted to quit and take a rest.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Related
Hi XDA members! Very excited to join this community and expand my knowledge or rather learn about development. I know NOTHING so please bare with me. I'm trying to root my Galaxy S Vibrant and I've been reading about rooting for months now with the hope of installing a custom ROM(?) like Cyanogenmod, but when I actually set out to do this I've been more confused. I guess there's different ways of rooting depending on carrier, version number, build type, os version, etc. I've tried to read the step by step processes of doing it, but I can't find links or the proper files to do it. I'm such a noob to this that I'm finding it discouraging. I'm not sure exactly of some of the terminology that is being used on these forums so that's why I need a walk through with all the links of what I need to do. I know that there's a learning curve and I'm willing to go through it, but I don't even know where to start. Can someone please walk me through this step by step on how I can root my phone and I'll worry about installing Cyanogenmod later?
Some phone details:
OS version: 2.3.3
kernal version: 2.6.35.7-I9000UGKG3
build number: GINGERBREAD.GKG3
Why stay on 2.3.3 when you can upgrade to 2.3.5? There are next to no custom roms available for your version of firmware. Your phone is basically the same as an I9000 international. Pretty much everything made for the i9000 will work on I9000M, the only thing that I do after I flash a new rom is flash my modem back to UGKG3, which is the modem you are using right now....check your phone in settings>phone>baseband version and you will see this is so. Go to this link:http://forum.xda-developers.com/showthread.php?t=1102881 and download 2.3.5 Europe: XXJVT/XXJVT/OXAJVT/Sbl (MultiCSC), extract the files. You want to use the one that says CODE. Now download 2.3.3 North America: UGKG3/UGKG3/BMCKG3/Sbl (MultiCSC), extract the files. You will use the ones that say CSC and PHONE. Now download (from the same link) Odin and pit files. Its under How to flash (you should read all of that about 5 times over) extract the files. You will have your Odin tool and 3 pit files. Your gonna use the one that says 512pit. So open up Odin...put the file from XXJVT that says CODE in the pda section....where it says phone use the file from UGKG3 that says PHONE...where it says CSC use the file from UGKG3 that says CSC...where it says PIT use the file 512pit.
Next you need to put your phone in download mode. Power it down and wait for it to vibrate about 10 seconds after screen goes black. Now hold down all together volume down + home key + power button. You should see download mode. Hook your phone up to your computer...you will see a com port on Odin go yellow...that means your connected. Press start....Its will take about 10 minutes. After Odin will say Pass, and reset...your phone will begin resetting. Once it reboots you will be running the XXJVT but with the North American modem.
Now you want to root...You need to choose a kernal that is made for XXJVT. I currently use Semaphore 1.8.0, there are newer versions of this kernal available and many other XXJVT kernals available. This is just my preference. You can find the download here:http://forum.xda-developers.com/showthread.php?t=1112908 Its at the bottom of the first post.
semaphore_kernal_jvt_1.8.0.tar....this file does not need to be extracted.
Power down your phone again and put it in Download mode....reset odin to remove the previously used file...now put the semaphore download in PDA....connect phone....com port goes yellow....press start....after 10 seconds it will say pass, reset...phone will reset and voila you have rooted your phone.
There is a tone of information on this site, just read up and learn...Its almost impossibe to mess up your phone beyond repair....Just read everything 3 or 4 times before doing anything.
GL
vanisleryan said:
the only thing that I do after I flash a new rom is flash my modem back to UGKG3
Click to expand...
Click to collapse
what do you mean by flashing back to the UGKG3 modem?
also, are there any other kernels beside the Semaphore one that you mentioned? Cuz i'm reading the changelog and it saids that the 720p video recording is broken and I really rely on my phone for videos....
I thought CM7 runs its own kernels ... can I use that instead?
After you are rooted, you might flash a rom on your phone like me Im on Simplicity rom, once I flash it, it changes my modem, so I flash my UGKG3 modem back in odin, since that is the north american modem that gives me the best signal.
As for the semaphore kernal I suggested, yes there are many. The one I suggested does not break 720 recording. Your are talking about semaphore 1.8.0bm...the bm means big memory, it has a bit more ram. I suggest semaphore 1.8.0...without the bm it does record 720 no problem, I use it all the time. As for CM7, I dont know...But I do know you need cwm in order to flash it.
Like I said there are more current versions of Semaphore available, just make sure you get the one that doesnt say bm at the end. The reason I suggest 1.8.0 is because it comes with superuser app and cwm app. Although Im hearing 1.9.1 is very good, I dont believe it has thes apps included so you would have to go and get them seperate...not a huge deal, Im just trying t make this easier for you.
ok... got rooted and new kernel....
time to play around to see if I can get CM7 on it
thanks again for all the help
chan1628 said:
ok... got rooted and new kernel....
time to play around to see if I can get CM7 on it
thanks again for all the help
Click to expand...
Click to collapse
How did you do it so quickly? I read all of vanis' stuff, which was very helpful, but since I'm a noob I don't even know where to start. I was passionate about doing this, but every time I re-read what I have to do I get confused, frustrated and give up. It seems overwhelmingly enough that it would take me an entire weekend to do
pk1025 said:
How did you do it so quickly? I read all of vanis' stuff, which was very helpful, but since I'm a noob I don't even know where to start. I was passionate about doing this, but every time I re-read what I have to do I get confused, frustrated and give up. It seems overwhelmingly enough that it would take me an entire weekend to do
Click to expand...
Click to collapse
Well, lets get something clear first... i got it rooted and flashed the kernel, i'm still having problems flashing to CM7 ... for some reasons, i'm having a boot loop during the installation process. So everytime, I need to re-ODIN with vanisleryan's instructions again just to get the phone to stop bootlooping. Since it doesn't look like ppl on this thread is familiar with CM7, i've gone looking for help on anther thread.
As for the ODIN part, i know it does seem overwhelming, but this is not the first 'droid device i've rooted, this is just the first Samsung device i'm rooting (hence my problems )
If you read vanisleryan's instructions, its really as straight simple as that.
Just download the 4 files that was indicated:
1) 2.3.5 Europe: XXJVT/XXJVT/OXAJVT/Sbl (MultiCSC)
2) 2.3.3 North America: UGKG3/UGKG3/BMCKG3/Sbl (MultiCSC)
3) Odin tool and 3 pit files
4) Semaphore 1.8.0 (this is optional because there are other suitable kernels, but I'm using this one too just for convenience)
get that done first and we can take it one step at a time.
first big question before you start:
- do you know how to get your SGS into Download Mode and does ODIN recognize your phone?
To get on cm7 from stock bell i9000m
Put latest cm7 nightly and latest gapps on internal sd
Get gingerbread ezbase
Flash ezbase
reboot iinto recovery
flash cm7
Flash gapps
Reboot
Done
Sent from my GT-I9000 using xda premium
pk1025 said:
How did you do it so quickly? I read all of vanis' stuff, which was very helpful, but since I'm a noob I don't even know where to start. I was passionate about doing this, but every time I re-read what I have to do I get confused, frustrated and give up. It seems overwhelmingly enough that it would take me an entire weekend to do
Click to expand...
Click to collapse
I learned how to use Odin the hard way (issue following a Kies upgrade), so I'll pass on what I've learned. Hope this will help.
If you have the abomination known as Kies installed, you already have the USB phone drivers on your PC.
As noted in vanisleryan's post, download the JVT, KG3, Odin, and Semaphore rooted kernel files.
The JVT, KG3, and Odin files are self extracting archives, so just double click and indicate where you want them to extract to.
Leave the Semaphore tar file as-is.
Locate the directory where Odin unpacked itself to and run Odin.
Click on PIT and select s1_odin_20100512.pit from the directory where Odin is extracted to.
Click on PDA and select PDA_XXJVT_Sbl.tar.md5 from the GT_I9000_XXJVT_XXJVT_OXAJVT_Sbl directory
Click on PHONE and select PHONE_UGKG3.tar.md5 from the GT_I9000M_UGKG3_UGKG3_BMCKG3_Sbl directory
Click on CSC and select CSC_BMCKG3.tar.md5 from the GT_I9000M_UGKG3_UGKG3_BMCKG3_Sbl directory
After you have selected the files, your Odin should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put your phone in download mode (You should see this guy):
connect the phone to your computer, wait for Odin to recognize the phone (yellow coloured background in ID:COM box) and then press Start.
After you have performed the initial flash and it succeeds, disconnect your phone from your computer and close Odin.
Open Odin again, click PDA and select Semaphore_kernel_JVT_1.8.0.tar
Do not select anything else. Put your phone in download mode again, connect to your computer.
When Odin indicates it has recognized your phone, press the Start button.
Once complete, you'll be running a rooted i9000m with JVT codebase and will be using the Bell modem and related info.
Jason123420 said:
To get on cm7 from stock bell i9000m
Put latest cm7 nightly and latest gapps on internal sd
Get gingerbread ezbase
Flash ezbase
reboot iinto recovery
flash cm7
Flash gapps
Reboot
Done
Click to expand...
Click to collapse
Hi,
so i have a few kinks with the instructions provided here....
flashing to ezbase was straight forward, no problems there...
however, when i rebooted into recovery, i noticed that it was the 3E recovery and not a CMW recovery...
I've never flashed a CM7 ROM w/o CMW, but I gave it a try anyway...
and of course, i got an error ... "E:failed to verify whole-file signature" and "E:signature verification failed"
any suggestions?
To add another voice to the chaos:
The JVT modem is working well for my Bell gt-i9000m. I'm on Telus but they share frequencies so Bell should be cool too. If you're on cm7 check out siky_dude's modem thread in the developer forum.
Beware ... once you start flashing roms you're going to be doing it constantly. Get to know your backup/restore tools....
roboticly yours
chan1628 said:
Hi,
so i have a few kinks with the instructions provided here....
flashing to ezbase was straight forward, no problems there...
however, when i rebooted into recovery, i noticed that it was the 3E recovery and not a CMW recovery...
I've never flashed a CM7 ROM w/o CMW, but I gave it a try anyway...
and of course, i got an error ... "E:failed to verify whole-file signature" and "E:signature verification failed"
any suggestions?
Click to expand...
Click to collapse
It shouldn't have been 3e recovery.. it should have been cwm3 did you flash the rom that came with the ezbase download?
Sent from my GT-I9000 using xda premium
badgerpapa said:
To add another voice to the chaos:
The JVT modem is working well for my Bell gt-i9000m. I'm on Telus but they share frequencies so Bell should be cool too.
Click to expand...
Click to collapse
Did you need to do anything special to enable the 850 frequency, or is that what the KG3 CSC addresses (still a noob at some of this myself)?
Jason123420 said:
It shouldn't have been 3e recovery.. it should have been cwm3 did you flash the rom that came with the ezbase download?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Well, i'm pretty sure is the correct correct thread for ezbase
http://forum.xda-developers.com/showthread.php?t=991792
however, the links in the OP are all broken, so somewhere on pg10 of that thread, someone posted a new link to d/l ezbase (http://nfye.eu/autoindex/index.php?dir=EZbase/&sort=filename&sort_mode=d)
and that's what i'm using...
chan1628 said:
Well, i'm pretty sure is the correct correct thread for ezbase
http://forum.xda-developers.com/showthread.php?t=991792
however, the links in the OP are all broken, so somewhere on pg10 of that thread, someone posted a new link to d/l ezbase (http://nfye.eu/autoindex/index.php?dir=EZbase/&sort=filename&sort_mode=d)
and that's what i'm using...
Click to expand...
Click to collapse
Well this is strange to me.. everytime I do a clean flash I use ezbase 4... let the phone boot.. turn off 3 button combo into recovery and its always cwm3.. then flash cm7
Sent from my GT-I9000 using xda premium
badgerpapa said:
To add another voice to the chaos:
The JVT modem is working well for my Bell gt-i9000m. I'm on Telus but they share frequencies so Bell should be cool too. If you're on cm7 check out siky_dude's modem thread in the developer forum.
Beware ... once you start flashing roms you're going to be doing it constantly. Get to know your backup/restore tools....
roboticly yours
Click to expand...
Click to collapse
You're right the jvt modem will work but you'll find your reception a hell of alot better if you use the KG3 modem.
Jason123420 said:
Well this is strange to me.. everytime I do a clean flash I use ezbase 4... let the phone boot.. turn off 3 button combo into recovery and its always cwm3.. then flash cm7
Click to expand...
Click to collapse
would you happen to have a copy of the EZbase MD5 files that you can share?
i dunno what else i can do.. every link I find is either broken or it leads me to the same place that I d/l it from yesterday
also, a couple other questions
1. can i flash a different kernel with while running ezbase (ie: Semaphore_kernel_JVT_1.8.0)
2. in ODIN, i know PDA = kernel, but when ppl say flashing the modem, does the modem = PHONE .... or does modem = CSC?
modem = PHONE
chan1628 said:
would you happen to have a copy of the EZbase MD5 files that you can share?
i dunno what else i can do.. every link I find is either broken or it leads me to the same place that I d/l it from yesterday
also, a couple other questions
1. can i flash a different kernel with while running ezbase (ie: Semaphore_kernel_JVT_1.8.0)
2. in ODIN, i know PDA = kernel, but when ppl say flashing the modem, does the modem = PHONE .... or does modem = CSC?
Click to expand...
Click to collapse
flash this with odin
http://forum.xda-developers.com/showthread.php?t=1326416&highlight=rooted+odin
make sure you follow the instructions exactly
then enter CWM factory reset and wipe dalvik cache then flash CM7.. then gapps then your cm7 radio from here
http://forum.xda-developers.com/showthread.php?t=1158783
if your from canada use KG3
let me know if this works
Jason123420 said:
flash this with odin
http://forum.xda-developers.com/showthread.php?t=1326416&highlight=rooted+odin
make sure you follow the instructions exactly
then enter CWM factory reset and wipe dalvik cache then flash CM7.. then gapps then your cm7 radio from here
http://forum.xda-developers.com/showthread.php?t=1158783
if your from canada use KG3
let me know if this works
Click to expand...
Click to collapse
Hi,
for some reason, the DJBROM wouldn't flash successfully. I was still getting the 3E recovery and nothing flashed properly with the stupid recovery.
anyhoo, i ended up flashing ezbase 4.0 with TalonDev 2.2 kernel
finally, using that combination, I was able to get CWM3 onto the phone
and from there, I knew what to do and now I finally got CM7 nightly running
thanks again for all your help
Hello everyone
I hope one of you might be able to help. I wanted to downgrade my Note to stock GB because I lost root on an ICS leak. I have done this successfully before but today pc odin suddenly hangs in the middle of flashing the factoryfs.img of a stock kernel (I used this one but tried others as well: N7000XXKJ4_N7000VD2KJ1_N7000XXKJ4_HOME.tar.md5).
Because of this I can now only boot the phone into download mode. I have also tried to use a pit file (as you can see in the screenshot, where I used this file: Q1_20110914_16GB.pit), because I thought the partitions might have been corrupted or changed by the ICS ROM but this didn't help either.
Do you have experienced this before? What else could I try?
Thanks a lot for any help
suxi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
+1 same issue here
your Re-Partition is on.
you phone is dead.
avetny said:
your Re-Partition is on.
you phone is dead.
Click to expand...
Click to collapse
OMG what's happening today, people's Notes are dying in droves!!!
razorhanny said:
OMG what's happening today, people's Notes are dying in droves!!!
Click to expand...
Click to collapse
yes it sad, people need to carefully read the instructions
suxi said:
Oops, sorry for posting this in the wrong section. Mods, please delete! Thanks.
Hello everyone
I hope one of you might be able to help. I wanted to downgrade my Note to stock GB because I lost root on an ICS leak. I have done this successfully before but today pc odin suddenly hangs in the middle of flashing the factoryfs.img of a stock kernel (I used this one but tried others as well: N7000XXKJ4_N7000VD2KJ1_N7000XXKJ4_HOME.tar.md5).
Because of this I can now only boot the phone into download mode. I have also tried to use a pit file (as you can see in the screenshot, where I used this file: Q1_20110914_16GB.pit), because I thought the partitions might have been corrupted or changed by the ICS ROM but this didn't help either.
Do you have experienced this before? What else could I try?
Thanks a lot for any help
suxi
Click to expand...
Click to collapse
Reset computer
endprogess kies (kiesELDR and kiestray..) in task manager.
Reoot again downloader
open odin
reconnec phone via usb port (in main ).
and reflash.
googluck.
Why dont people make backups before flashing new roms
Takez 5-6min in CWM to make a backup of your current rom
If any thing goes wrong or you just want to go back to the old rom you just run the restore and you are back up and running in under 10min
Shouldnt have needed Odin to downgrade, if ya created a firmware folder on ya sd and followed ketans cwm guide to flash bk to rooted stock ya wouldt have an issue.
As for odin you flashed wrong, previous comments are right, your re-partition shouldnt have been on if you were flashing the all in one firmware thru pda, and you certainly shouldnt have been using the pit file to do that.
Hope you sorted the issue out, seriously, its risky business, the guides here on xda are perfect working guides, make sure you read them thoroughly and familiarize yourself with what your doing beforehand.
Also noted your using odin 1.85, i had issues with this, i reverted to odin 1.83 and have never had a problem since, give it a try, but if ya can enter download mode then ya shouldnt have an issue, i would reccomend downloading firmware KL8, set the pit file, re-partition and the other 2 leave ticked, set modem, code and multi csc, and flash and dont touch it till its finished and reboots, after that ya can then go and do whatever, but this should work, i downgraded from ics to kl8 no problem with odin 1.83.
Relax fellas! Your Notes are not committing mass suicides... just yet. Use the pit file attached below to flash your favorite (rootable) stock Gingerbread ROM. Just hit the "PIT" button in ODIN and select the pit file. And ALSO the PDA field should also be selected. Just use one of the guides. You need to extract the rar to get the pit file. I hope this helps.
Edit. When you select the PIT file, the repartition box will check itself, don't uncheck it.
acidburn89 said:
Relax fellas! Your Notes are not committing mass suicides... just yet. Use the pit file attached below to flash your favorite (rootable) stock Gingerbread ROM. Just hit the "PIT" button in ODIN and select the pit file. And ALSO the PDA field should also be selected. Just use one of the guides. You need to extract the rar to get the pit file. I hope this helps.
Edit. When you select the PIT file, the repartition box will check itself, don't uncheck it.
Click to expand...
Click to collapse
I Tried your PIT file. Does it really take long to SET PARTITION?
same issues here. anyone can confirm that the PIT file is working?
Good morning and thanks a lot for your help!
your Re-Partition is on.
Click to expand...
Click to collapse
Only as a last resort. As I wrote, before I tried flashing several ROMS without PIT files and got stuck the exact same way.
yes it sad, people need to carefully read the instructions
Click to expand...
Click to collapse
My words and I followed exact instructions from a different post.
Reset computer
endprogess kies (kiesELDR and kiestray..) in task manager.
Reoot again downloader
open odin
reconnec phone via usb port (in main ).
and reflash.
Click to expand...
Click to collapse
I tried this several times with no success.
Why dont people make backups before flashing new roms
... If any thing goes wrong or you just want to go back to the old rom you just run the restore and you are back up and running in under 10min
Click to expand...
Click to collapse
I do, but unfortunately instructions from a different thread advised to do it "the odin way".
Shouldnt have needed Odin to downgrade ...
Click to expand...
Click to collapse
graemeg, yes, probably, but those instructions ...
i reverted to odin 1.83 and have never had a problem since,
Click to expand...
Click to collapse
I'll do that, too. Thanks.
i would reccomend downloading firmware KL8
Click to expand...
Click to collapse
I did this with LA1, it also includes the different files.
Use the pit file attached below
Click to expand...
Click to collapse
Thank you for the link. That's the exact file I used before.
Any other ideas?
Thanks for your help
suxi
Had the same problem.
Have managed to get CWM back - but I have made no back-ups to restore. Stupid me.
cemstro said:
Had the same problem.
Have managed to get CWM back - but I have made no back-ups to restore. Stupid me.
Click to expand...
Click to collapse
how did you get cwm back??
ArchaosAngel said:
how did you get cwm back??
Click to expand...
Click to collapse
By flashing CF-Root kernel through ODIN.
cemstro said:
By flashing CF-Root kernel through ODIN.
Click to expand...
Click to collapse
are u able to flash a rom and get it to work?
ArchaosAngel said:
are u able to flash a rom and get it to work?
Click to expand...
Click to collapse
Tried flashing multpile ROM's (GB and ICS), but even when they do succesfully finish I get stuck when booting at the "Samsung Galaxy Note" screen - with a nice yellow triangle.
So I'm done with it for now. Not trying anything new, until the guys in the Dev section find a way to fix it.
suxi said:
I do, but unfortunately instructions from a different thread advised to do it "the odin way".
Click to expand...
Click to collapse
I am one of those who flashed TRR 1.6 with the angelom 1.2 kernel,
and while it didn't, luckily enough, brick my phone, it caused all sorts
of weird stuff, like gmail crashing etc.
I then flashed, as advised in the TRR thread, abyssnote 3.9, plus restored
a RR v22 backup, I'm back just fine now.
armic said:
I Tried your PIT file. Does it really take long to SET PARTITION?
Click to expand...
Click to collapse
Take Seconds..... been there done that.....
MrIT said:
Reset computer
endprogess kies (kiesELDR and kiestray..) in task manager.
Reoot again downloader
open odin
reconnec phone via usb port (in main ).
and reflash.
googluck.
Click to expand...
Click to collapse
Hi
I did not run it the way you train is the factoryfs stops
My mobile partition is unmount
Help me
Hi there! I have a galaxy mini s5570. tried to install cwm recovery on it! first rooted it by recovery. then tried to install cwm by stock recovery by renaming the cwm package to update.zip and applying update from sdcard. Unsuccessful! then tried to install cm10 using the stock recovery by renaming it again to update.zip using stock recovery. got success message in recovery. but wen i rebooted, it got stuck at samsung. tried to flash cwm via odin. failed in first turn but den i got successful at once. then even the stock recovery is gone! now odin won't flash anything in my galaxy. tried to flash stock rom but it stuck on "mibib download". when flashing recovery, it gets stuck on "recovery.img download". wen booting the phone or getting into recovery, a strange ""[pc]---[exclamation mark]---[phone]"" icon appears! tried everything but can't get rid of it! HELP PLZ!
abhijeetdahiya said:
Hi there! I have a galaxy mini s5570. tried to install cwm recovery on it! first rooted it by recovery. then tried to install cwm by stock recovery by renaming the cwm package to update.zip and applying update from sdcard. Unsuccessful! then tried to install cm10 using the stock recovery by renaming it again to update.zip using stock recovery. got success message in recovery. but wen i rebooted, it got stuck at samsung. tried to flash cwm via odin. failed in first turn but den i got successful at once. then even the stock recovery is gone! now odin won't flash anything in my galaxy. tried to flash stock rom but it stuck on "mibib download". when flashing recovery, it gets stuck on "recovery.img download". wen booting the phone or getting into recovery, a strange ""[pc]---[exclamation mark]---[phone]"" icon appears! tried everything but can't get rid of it! HELP PLZ!
Click to expand...
Click to collapse
What u just did was absurd. NOBODY flashes a custom rom on stock recovery! Also, NOBODY flashes CWM by changing the file name to update.zip!
Here's what you should do next:
That phone--!--PC image ur seeing, something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's just another form of download mode. It's the download mode when there isn't any rom installed on your phone I think. What you should do is to go to that screen, plug in your USB cable, and flash stock rom via odin.
Try following the guide in my sig.
tried your method also but still it got stuck at mibib download! can't get it further!
abhijeetdahiya said:
tried your method also but still it got stuck at mibib download! can't get it further!
Click to expand...
Click to collapse
You should've done some reading before even trying to flash your phone. Tietgan's guide is 100% legit, so I guess problem is in you...
yackovsky said:
You should've done some reading before even trying to flash your phone. Tietgan's guide is 100% legit, so I guess problem is in you...
Click to expand...
Click to collapse
dude i have one samsung galaxy y gt-s5360 and samsung galaxy 5 gt-i5500. i have flashed those two a hundred times using odin and never got any problem! den why i am getting stuck in galaxy mini only? even the procedure is all the same if flashing via odin in any of these samsung android phones!
Since you have experience in flashing phones you should've know that stock recovery is useless for custom roms... try getting USB jig, it might help... you can make your own very cheap, tietgan posted guide about it and I know that guide works, bcause I made one on my own and tested it
abhijeetdahiya said:
dude i have one samsung galaxy y gt-s5360 and samsung galaxy 5 gt-i5500. i have flashed those two a hundred times using odin and never got any problem! den why i am getting stuck in galaxy mini only? even the procedure is all the same if flashing via odin in any of these samsung android phones!
Click to expand...
Click to collapse
Flashing via odin only, doesn't mean u know how to flash custom roms. Anyways, u should've flashed cwm via odin and then using cwm for custom rom. So last resort is usb jig (as said by yackovsky) which should work most of the time. Else its service centre with the excuse u updated OS and the phone does not work now. Gud luck. Hope u get the mini back from the dead.
kirakun said:
Flashing via odin only, doesn't mean u know how to flash custom roms. Anyways, u should've flashed cwm via odin and then using cwm for custom rom. So last resort is usb jig (as said by yackovsky) which should work most of the time. Else its service centre with the excuse u updated OS and the phone does not work now. Gud luck. Hope u get the mini back from the dead.
Click to expand...
Click to collapse
I had successfully installed cm9 in my galaxy 5, now running cm10 in my micromax funbook tablet, and creed's in my galaxy y. all my mistake was i tried to install custom rom using stock recovery! never faced such a problem in the past! but now i got it dat custom rom can't be installed via stock recovery...
as far as i got, the usbjig will only take my galaxy mini to download mode. but still my phone gets in download mode even without usbjig. so...i didn't get what is the difference between both these download modes..??
abhijeetdahiya said:
as far as i got, the usbjig will only take my galaxy mini to download mode. but still my phone gets in download mode even without usbjig. so...i didn't get what is the difference between both these download modes..??
Click to expand...
Click to collapse
if u get into download mode simply flash a firmware via odin...
Android_United said:
if u get into download mode simply flash a firmware via odin...
Click to expand...
Click to collapse
yeah i tried to but it always get stuck on mibib download and wen flashing recovery, at recovery.img download!
abhijeetdahiya said:
yeah i tried to but it always get stuck on mibib download and wen flashing recovery, at recovery.img download!
Click to expand...
Click to collapse
Are u sure ur using the correct Tass.ops file? Try downloading another OPS file.
abhijeetdahiya said:
yeah i tried to but it always get stuck on mibib download and wen flashing recovery, at recovery.img download!
Click to expand...
Click to collapse
Rename ur ops file to TASS_v1.0.ops (for galaxy mini). This should work. Mbib download problem occurs only due to wrong name of ops file.
Also, note that if ur ops file name is wrong, You'll not see ur device model number on odin's title bar.
Hope this helps!!
Sent Via XDA™ Premium
tietganFTW said:
Are u sure ur using the correct Tass.ops file? Try downloading another OPS file.
Click to expand...
Click to collapse
Galaxy_Rohit said:
Rename ur ops file to TASS_v1.0.ops (for galaxy mini). This should work. Mbib download problem occurs only due to wrong name of ops file.
Also, note that if ur ops file name is wrong, You'll not see ur device model number on odin's title bar.
Hope this helps!!
Sent Via XDA™ Premium
Click to expand...
Click to collapse
finally shifted from my laptop to pc, download a new ops for mini from cyanogen wiki....and got the rom flashed! den successfully installed cwm and now my mini is running cm10 perfectly! Thanx ALOT guys for so great help!!! :highfive:
tietganFTW said:
It's just another form of download mode. It's the download mode when there isn't any rom installed on your phone I think. What you should do is to go to that screen, plug in your USB cable, and flash stock rom via odin
Try following the guide in my sig.
Click to expand...
Click to collapse
Or just turn it off and then press Volume Up and power key,then will show you fora updating then it will close and will work again.
abhijeetdahiya said:
as far as i got, the usbjig will only take my galaxy mini to download mode. but still my phone gets in download mode even without usbjig. so...i didn't get what is the difference between both these download modes..??
Click to expand...
Click to collapse
If both download modes don't work, then its service center. They may even reject the repairs, but all up to u.
abhijeetdahiya said:
finally shifted from my laptop to pc, download a new ops for mini from cyanogen wiki....and got the rom flashed! den successfully installed cwm and now my mini is running cm10 perfectly! Thanx ALOT guys for so great help!!! :highfive:
Click to expand...
Click to collapse
dahh...see, even a small mistake like that can't be seen by some one who has a lot of experience in flashing via odin like you...be more gentle :good:
Flash cwm with odin.... And make sure your drivers are up to date.
emanoN v7
many thanx
Galaxy_Rohit said:
Rename ur ops file to TASS_v1.0.ops (for galaxy mini). This should work. Mbib download problem occurs only due to wrong name of ops file.
Also, note that if ur ops file name is wrong, You'll not see ur device model number on odin's title bar.
Hope this helps!!
Sent Via XDA™ Premium
Click to expand...
Click to collapse
thanx thanx thanx thanx I've tried every thing ,and the problem was with the name:laugh:
i got same problem, i tried to instal tass-recovery-cwm via odin or rename to update.zip ( then press volume Up + Home + Power ) still doesnt work.. fail to instal cmw, now my phone still reboot every i press power button..
anyone have link to full packaget like S5570XXKPK (2.3.4) ?.. ( i mean include file BOOT, PDA, PHONE, CSC ) not single file ?..
Problem Solved..
thanks everyone )
Hi there,
This is my first Android phone, so I'm a bit lost. Any help would be greatly appreciated.
I have done some research, but I'd like to confirm that this is the way to do it. My phone is not rooted.
Firmware 2.3.6
Kernel 2.6.35.7-I9000BUJVI-CL1076478 [email protected] #2
GINGERBREAD.BUJVI
This is the steps I think I must follow:
1) Install CF-Root with Odin 1.83 (that's the version under which the I9000 is listed as compatible) - which CF-Root version should I use? Since I have BUJVI, do I need a JVI version? I found and downloaded CF-Root-XW_DBT_JVI-v3.7-CWM3RFS - will it work?
2) Install CWM 2.5.1.2 (this is the correct version for I9000 according to the official CWM website)
3) Install CM10.2
Is this correct? Is there anything else I should know?
Thanks!
Here is an thread about:
http://forum.xda-developers.com/showthread.php?t=2434225
bockyPT said:
Hi there,
This is my first Android phone, so I'm a bit lost. Any help would be greatly appreciated.
I have done some research, but I'd like to confirm that this is the way to do it. My phone is not rooted.
Firmware 2.3.6
Kernel 2.6.35.7-I9000BUJVI-CL1076478 [email protected] #2
GINGERBREAD.BUJVI
This is the steps I think I must follow:
1) Install CF-Root with Odin 1.83 (that's the version under which the I9000 is listed as compatible) - which CF-Root version should I use? Since I have BUJVI, do I need a JVI version? I found and downloaded CF-Root-XW_DBT_JVI-v3.7-CWM3RFS - will it work?
2) Install CWM 2.5.1.2 (this is the correct version for I9000 according to the official CWM website)
3) Install CM10.2
Is this correct? Is there anything else I should know?
Thanks!
Click to expand...
Click to collapse
Hi there,
My phone is stuck in boot loop, what can I do?
I did just point 1) above: Install CF-Root with Odin 1.83, CF-Root-XW_DBT_JVI-v3.7-CWM3RFS
bockyPT said:
Hi there,
My phone is stuck in boot loop, what can I do?
I did just point 1) above: Install CF-Root with Odin 1.83, CF-Root-XW_DBT_JVI-v3.7-CWM3RFS
Click to expand...
Click to collapse
1) Hope you had flashed the correct CF ROOT JVI would be for JVI ROM
2) You should include screen shot or more details as to what kind of bootloop you have, if it says
E:failed to mount /sdcard (files exists),
E:copy_dbdata_media:Can't mount /sdcard.
E:Can't mount /dev/block/stl10 (invalid Argument)
than flash the attached file Edit: removed
3) to solve bootloop as above flash attached file as PDA using Odin3 1.83
4) But the problem seems to be you have BUJVI and you flashed XWJVI, DBT means its meant for germany
Galaxy S GT-I9000 EUR I9000XWJVI Android 2.3.3
Galaxy S GT-I9000 TCL I9000BUJVI Android 2.3.6
Galaxy S GT-I9000 DBT I9000XWJVI Android 2.3.3
so now you need to flash the original BUJVI kernel or flash that original ROM to solve it or flash a semaphore kernel to solve it or follow this and change to JVU rom and upgrade to ICS or Jelly Bean
xsenman said:
follow this and change to JVU rom and upgrade to ICS or Jelly Bean
Click to expand...
Click to collapse
Hi there,
Thank you for your answer! The phone shows only the Samsung Galaxy logo for a few seconds, then goes black and the logo shows up again, ad infinitum. I can get to download mode. My goal is to install CM10.2, so I should follow that tutorial and install JVU rom, right? However, I'm still not sure what file to download, they all have different version numbers and I don't know what they mean. I found these two JVUs, which should I use?
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
CF-Root-XW_TMN_JVU-v4.3-CWM3RFS.zip (OLD !! Not the 2012 version !!) ---> This has my carrier on the file name (TMN), but I have no idea what it means to not be the 2012 version.
I also found the following original ROM, but it obviously doesn't have CWM.
I9000XWJW9_I9000TMNJV4_TMN.zip
Thank you for the help!
bockyPT said:
I also found the following original ROM, but it obviously doesn't have CWM.[ !
Click to expand...
Click to collapse
the bootloop you have is due to your ROM being 2.3.6 and you flashed a kernel was meant for 2.3.3
Basically, IF you are flashing the JVU, I had already attached the correct CF root file for it in that thread ( so no need for you to worry about it), Now if you are worried about the Modem which is what TMN means ( Portugal) It can be swapped after the upgrade if your reception is poor or fails.
look here for a guide on the ROMS meant for Portugal (look for region TMN), if you want one that must match with CF root kernel
But on the other-hand look here for all the stock Modems that you can flash at any time or simply serch for the BUJVI modem you have been using in google and here for ICS & Jelly Bean Modems that will work better with ICS and JellyBean ROM's
Frankly its not an issue, unless your phone is locked by contract with Portugal vodophone
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
Basically, IF you are flashing the JVU, I had already attached the correct CF root file for it in that thread ( so no need for you to worry about it)
Click to expand...
Click to collapse
Thanks again! I'm sorry but I dont see what file you're talking about. Is it any of the two I mentioned on my previous post?
bockyPT said:
Thanks again! I'm sorry but I dont see what file you're talking about. Is it any of the two I mentioned on my previous post?
Click to expand...
Click to collapse
This already had the JVU plus CF root with CWM downloads in it
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
This already had the JVU plus CF root with CWM downloads in it
Click to expand...
Click to collapse
Thanks! I flashed PDA only but the same problem persists. Should I use all files (PIT, PDA, PHONE, CSC)?
bockyPT said:
Thanks! I flashed PDA only but the same problem persists. Should I use all files (PIT, PDA, PHONE, CSC)?
Click to expand...
Click to collapse
you need to follow the details as mentioned, if you just want to flash kernel use the semaphore kernel that I advised you about earlier. But if you use the JVU package than flash everything that is mentioned on that thread.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
you need to follow the details as mentioned, if you just want to flash kernel use the semaphore kernel that I advised you about earlier. But if you use the JVU package than flash everything that is mentioned on that thread.
Click to expand...
Click to collapse
Thank you, it's working now!
bockyPT said:
Thank you, it's working now!
Click to expand...
Click to collapse
Well... It's not working anymore. I tried to install CM9.1 using this tutorial: http://forum.xda-developers.com/showthread.php?t=2434225
However... After installing it (as well as GApps), I restarted the phone and now it's stuck in boot loop again. I can access Download mode but not CWM recovery. What should I do?
bockyPT said:
Well... It's not working anymore. I tried to install CM9.1 using this tutorial: http://forum.xda-developers.com/showthread.php?t=2434225
However... After installing it (as well as GApps), I restarted the phone and now it's stuck in boot loop again. I can access Download mode but not CWM recovery. What should I do?
Click to expand...
Click to collapse
ok, ICS ROMS need to be flashed twice ( was mentioned in that post) , since you are now in bootloop use Odin in download mode (not CWM recovery mode) to flash this ICS semaphore kernel
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
xsenman said:
ok, ICS ROMS need to be flashed twice ( was mentioned in that post) , since you are now in bootloop use Odin in download mode (not CWM recovery mode) to flash this ICS semaphore kernel
Click to expand...
Click to collapse
Hi there,
I flashed that kernel and it got stuck in "powered by Semaphore" logo screen. I tried flashing it again but it's still stuck in that screen.
bockyPT said:
Hi there,
I flashed that kernel and it got stuck in "powered by Semaphore" logo screen. I tried flashing it again but it's still stuck in that screen.
Click to expand...
Click to collapse
power it down, remove battery, remove SIM card and Ext SD card and press and hold your power button for at least 30 seconds to a min, before reinserting battery and power ON.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
bockyPT said:
I flashed that kernel and it got stuck in "powered by Semaphore" logo screen. I tried flashing it again but it's still stuck in that screen.
Click to expand...
Click to collapse
Mate, you make huge chaos there. Xsenman has written you all the time step by step exactly what to do and you were improvising. Nobody knows now anymore which files did you flash and how did you set Odin.
Check my new thread for the whole proceeding: unbricking, upgrade or downgrade to CM10.2, root and all else. It contains valid download links for all files:
http://forum.xda-developers.com/showthread.php?t=2444308
For upgrading to CM10.2 it seems to work anyway better to take off from Froyo and SpeedMod kernel, as many people upgrading from Gingerbread have either bootloops or buggy CM10.2.
xsenman said:
power it down, remove battery, remove SIM card and Ext SD card and press and hold your power button for at least 30 seconds to a min, before reinserting battery and power ON.
Click to expand...
Click to collapse
Still no luck.
tetakpatak said:
Mate, you make huge chaos there. Xsenman has written you all the time step by step exactly what to do and you were improvising. Nobody knows now anymore which files did you flash and how did you set Odin.
Click to expand...
Click to collapse
What do you mean? I have not flashed anything that xsenman didn't suggest. I know exactly which steps I took:
Install all files from the JVU package (I9000XXJVU CFROOT) via Odin 1.83 following the tutorial on http://forum.xda-developers.com/showthread.php?t=2434225. It worked.
Flash CM9.1 via CWM from this tutorial http://forum.xda-developers.com/showthread.php?t=1592131 - got stuck at boot without CWM recovery, so I could not reflash CM9.1.
Flash Semaphore as suggested by Xsenman - still stuck so I tried again - still stuck.
bockyPT said:
Still no luck. .
Click to expand...
Click to collapse
ok , no worries, you can access CWM recovery mode by combo keys, so just flash the CM 10.2 or the CM 9.1 again
or you can take @tetakpatak advise and try it from froyo as the CM 10.2 is what you intent to have finally and it should work .
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
OK: if all the files were correct and you didn't check the repartition in Odin, you could find out with ADB why doesn't your i9000 reboot into OS.
But if you aren't familiar with ADB, rather save your time and just go towards my guide. That procedure already unbricked many i9000s.
xsenman said:
ok , no worries, you can access CWM recovery mode by combo keys, so just flash the CM 10.2 or the CM 9.1 again
Click to expand...
Click to collapse
I flashed CM 10.2 and it's working now, thanks a lot for your efforts! The only problem I have detected so far is that it's telling me I have an invalid IMEI. Can I change it? I do know my original IMEI.
tetakpatak said:
But if you aren't familiar with ADB, rather save your time and just go towards my guide. That procedure already unbricked many i9000s.
Click to expand...
Click to collapse
tetakpatak, thanks for your help as well. Since I started following xsenman's guide I stuck with it, but your guide seems to be very helpful as well. I'll be sure to take a look should the need come.
All, Please Help! I am not a newbie when it comes to Samsung Phones, Flashing, Odin, Root, Etc. I picked up a used Galaxy S6 off Ebay for dirt cheap, but now I see why. It is stuck on the Samsung Galaxy S6 boot screen. I have literally tried EVERYTHING to fix the phone, and I cannot get it to boot. I've flashed the Stock Firmware in Odin, and it has flashed successfully, but is still stuck on the Samsung Boot Screen. I've gone into recovery and performed a Factory Reset, with no avail. I am able to get into Recovery and Download mode with no trouble. I've flashed several different Stock Firmware Versions, several of which succeeded, but no boot.
I've tried to flash a Custom Kernel (UniKernel). but it fails when I try and flash through ODIN. Does anyone have any ideas what I can do ?
Thank you all in Advance!
Ethan9987 said:
All, Please Help! I am not a newbie when it comes to Samsung Phones, Flashing, Odin, Root, Etc. I picked up a used Galaxy S6 off Ebay for dirt cheap, but now I see why. It is stuck on the Samsung Galaxy S6 boot screen. I have literally tried EVERYTHING to fix the phone, and I cannot get it to boot. I've flashed the Stock Firmware in Odin, and it has flashed successfully, but is still stuck on the Samsung Boot Screen. I've gone into recovery and performed a Factory Reset, with no avail. I am able to get into Recovery and Download mode with no trouble. I've flashed several different Stock Firmware Versions, several of which succeeded, but no boot.
I've tried to flash a Custom Kernel (UniKernel). but it fails when I try and flash through ODIN. Does anyone have any ideas what I can do ?
Thank you all in Advance!
Click to expand...
Click to collapse
What s6 u have and what version are u trying to Odin flash ?
Sent from my SM-G920T using Tapatalk
try this... flash twrp and do a complete format. Go to odin and flash Full Stock FW. If it doesnt boot, your flash memory is corrupted I/O means DEAD MEMORY. OR in twrp try to flash bootloader, modem, ckernel and any room compatible.
SM-G920T. Not the edge model. I tried to flash several versions. Latest I tried was DOJC. It flashed successfully too. I downloaded the firmware from SamMobile.
genuine55 said:
What s6 u have and what version are u trying to Odin flash ?
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
SM-G920T. Not the edge model. I tried to flash several versions. Latest I tried was DOJC. It flashed successfully too. I downloaded the firmware from SamMobile.
yowy777 said:
try this... flash twrp and do a complete format. Go to odin and flash Full Stock FW. If it doesnt boot, your flash memory is corrupted I/O means DEAD MEMORY. OR in twrp try to flash bootloader, modem, ckernel and any room compatible.
Click to expand...
Click to collapse
How do I flash Twrp? I tried to flash one version in Odin and it failed. Do you have a link to the Twrp I should be using?
Thanks for your help!
Ethan9987 said:
How do I flash Twrp? I tried to flash one version in Odin and it failed. Do you have a link to the Twrp I should be using?
Thanks for your help!
Click to expand...
Click to collapse
This post contains info and links to odin flashable versions of TWRP for LP and MM.
If you successfully install TWRP and boot to recovery you should be good?
Most likely you will be fine!
If it fails try every different variation possible to find the right combo of USB cable, USB port, different pc's, different versions of odin.
Eventually you will get the perfect combo and it will boot.
If you flashed the full odin, it been awhile since I've done it with a stock device, but if I remember correctly there is something about booting back to recovery before the os can boot which will cause the custom recover to be overridden with the stock recovery?
Like I said, been awhile and that info might not even pertain to this device.
Figured I would just throw that out there to give more info for troubleshooting.
Also, no biggie, but this is a "development" forum and troubleshooting issues unrelated to a development project here don't belong here.
All good and best of luck to you!
Let us know how it goes along with what did out didn't work. Someone down the road may benefit from what you're going through right now
stangdriver44 said:
This post contains info and links to odin flashable versions of TWRP for LP and MM.
If you successfully install TWRP and boot to recovery you should be good?
Most likely you will be fine!
If it fails try every different variation possible to find the right combo of USB cable, USB port, different pc's, different versions of odin.
Eventually you will get the perfect combo and it will boot.
If you flashed the full odin, it been awhile since I've done it with a stock device, but if I remember correctly there is something about booting back to recovery before the os can boot which will cause the custom recover to be overridden with the stock recovery?
Like I said, been awhile and that info might not even pertain to this device.
Figured I would just throw that out there to give more info for troubleshooting.
Also, no biggie, but this is a "development" forum and troubleshooting issues unrelated to a development project here don't belong here.
All good and best of luck to you!
Let us know how it goes along with what did out didn't work. Someone down the road may benefit from what you're going through right now
Click to expand...
Click to collapse
Thank you so much for the suggestions! I tried to flash both twrp files from the link you sent me, and they both fail in Odin.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ethan9987 said:
Thank you so much for the suggestions! I tried to flash both twrp files from the link you sent me, and they both fail in Odin.
Click to expand...
Click to collapse
Update:
I flashed 920T_EPD1_BOOTLOADER.tar in Odin in the BL section, assuming that is for bootloader. It was successful, but still stuck on the boot screen
Ethan9987 said:
Update:
I flashed 920T_EPD1_BOOTLOADER.tar in Odin in the BL section, assuming that is for bootloader. It was successful, but still stuck on the boot screen
Click to expand...
Click to collapse
.
It's kind of hard to say what's going on with your complete file system?
What what the last "FULL" odin firmware you flashed?
not that you've odin'd the EPD1 files, try and ODIN the twrp-3.0.2-zeroflte.img.tar.
Try to see if it work in the order. make sure you've flashed EPD1 bootloader first, then the twrp.
I am making an ODIN file of the stock 920T boot.img to try as well. the boot.img will be here shortly. uploading now
Here is the kernel for use in odin
If Odin isn't working, maybe trying it with admin permissions and a usb connection to the backside of your pic (the usb port that's directly attached to your motherboard). If this fails as well try samsung's smart switch, it has its own flash tool (http://www.samsung.com/us/smart-switch/). You need the s/n of your device and model (SM-G920T) , you can look up the s/n in download mode by first launching download mode then press the home button and youll be able to write it down somewhere. On the smart switch software, launch the emergency options and follow through the wizard setup by first entering in the s/n and model to identify what device you have to get the proper firmware.
stangdriver44 said:
.
It's kind of hard to say what's going on with your complete file system?
What what the last "FULL" odin firmware you flashed?
not that you've odin'd the EPD1 files, try and ODIN the twrp-3.0.2-zeroflte.img.tar.
Try to see if it work in the order. make sure you've flashed EPD1 bootloader first, then the twrp.
I am making an ODIN file of the stock 920T boot.img to try as well. the boot.img will be here shortly. uploading now
Here is the kernel for use in odin
Click to expand...
Click to collapse
I appreciate you're help!
The FULL Odin fireware I flashed originally was G920TUEU3COK1 from: http://www.sammobile.com/firmwares/download/61037/G920TUEU3COK1_G920TXAR3COK1_XAR/
I tried this one, because when I got the phone, and I booted into the Stock Recovery, this is the build # that it was showing at the top of the screen in Stock Recovery. I've tried several versions since, and they fail. G920TUEU3COK1 was the only one that was successful. I just did what you suggested. I flashed the 920T_EPD1_BOOTLOADER.tar FIRST, it was successful. I immediately held Power + Volume Down + Home to reboot into Download mode after the Bootloader flashed. I than tried to flash the twrp through AP in Odin.... and it Failed. I repeated again, flashing the bootloader first, booting back into Download Mode, tried to flash the 920T_EPD1_boot.img.tar, and it fails too.
DroneDoom said:
If Odin isn't working, maybe trying it with admin permissions and a usb connection to the backside of your pic (the usb port that's directly attached to your motherboard). If this fails as well try samsung's smart switch, it has its own flash tool (http://www.samsung.com/us/smart-switch/). You need the s/n of your device and model (SM-G920T) , you can look up the s/n in download mode by first launching download mode then press the home button and youll be able to write it down somewhere. On the smart switch software, launch the emergency options and follow through the wizard setup by first entering in the s/n and model to identify what device you have to get the proper firmware.
Click to expand...
Click to collapse
Thank you for your suggestion! Do I put the phone in Download Mode for Smart Switch to see it? That is what I tried, and it shows Unsupported Device. Am I missing something?
The process requires the phone to be in download mode the entire time. Most likely you entered the model or s/n incorrectly. It's real strick about the exact format to identify your device. You said you have a g920t but the software will only read it as SM-G920T (it may have a slightly different variation depending on where you got this model). the s/n should have no hyphens, just numbers and letters.
DroneDoom said:
The process requires the phone to be in download mode the entire time. Most likely you entered the model or s/n incorrectly. It's real strick about the exact format to identify your device. You said you have a g920t but the software will only read it as SM-G920T (it may have a slightly different variation depending on where you got this model). the s/n should have hyphens, just numbers and letters.
Click to expand...
Click to collapse
Thank you! I figured it out, finally Right now it is 30% and the progress bar is moving across the screen. I am really crossing my fingers and hoping this works!
Ethan9987 said:
Thank you! I figured it out, finally Right now it is 30% and the progress bar is moving across the screen. I am really crossing my fingers and hoping this works!
Click to expand...
Click to collapse
Okay, it was successful. It finished and rebooted, but now it shows "device does not have drk please install drk first" .
Now what?
I found this thread:
http://forum.xda-developers.com/galaxy-s6/help/help-device-drk-please-install-drk-t3321212
Tried to flash the Kernel file that was listed in that thread through ODIN, but it failed. Imagine that.
Ethan9987 said:
Okay, it was successful. It finished and rebooted, but now it shows "device does not have drk please install drk first" .
Now what?
I found this thread:
http://forum.xda-developers.com/galaxy-s6/help/help-device-drk-please-install-drk-t3321212
Tried to flash the Kernel file that was listed in that thread through ODIN, but it failed. Imagine that.
Click to expand...
Click to collapse
It seems drk binary is kernel related or maybe I'm wrong. Is the warranty bit set to 1 in download mode? If so maybe the previous owner screwed with the efs partition and now passed the problem onto you. Try smart switch one more time and see if you can boot normally. OEM may still be locked preventing you from using Odin, so that may be the end of the road because I have no other solution.
Edit: if you can boot into stock recovery, maybe you could manipulate an update zip package to install a custom kernel specifically for the g920t. This is just a theory, not sure if stock recovery does some checking before flashing.
an example kernel you can incorporate: https://www.androidfilehost.com/?fid=24591023225178101 (twisted kernel v8)
Ethan9987 said:
Thank you! I figured it out, finally Right now it is 30% and the progress bar is moving across the screen. I am really crossing my fingers and hoping this works!
Click to expand...
Click to collapse
DroneDoom said:
It seems drk binary is kernel related or maybe I'm wrong. Is the warranty bit set to 1 in download mode? If so maybe the previous owner screwed with the efs partition and now passed the problem onto you. Try smart switch one more time and see if you can boot normally. OEM may still be locked preventing you from using Odin, so that may be the end of the road because I have no other solution.
Edit: if you can boot into stock recovery, maybe you could manipulate an update zip package to install a custom kernel specifically for the g920t. This is just a theory, not sure if stock recovery does some checking before flashing.
an example kernel you can incorporate: https://www.androidfilehost.com/?fid=24591023225178101 (twisted kernel v8)
Click to expand...
Click to collapse
Knox Warrenty Void is set to : 1.
Balls! This sucks. I tried Tried Smart switch a second time already with no luck. I think you may be right, the previous owner did something. I like the idea of manipulating a update zip package.... Just have no idea how to do that.
Thanks for all your help
Ethan9987 said:
Knox Warrenty Void is set to : 1.
Balls! This sucks. I tried Tried Smart switch a second time already with no luck. I think you may be right, the previous owner did something. I like the idea of manipulating a update zip package.... Just have no idea how to do that.
Thanks for all your help
Click to expand...
Click to collapse
Also, I don't think I have the ability to flash an update.zip without an SD Card right? Which this phone doesn't take one
Ethan9987 said:
Knox Warrenty Void is set to : 1.
Balls! This sucks. I tried Tried Smart switch a second time already with no luck. I think you may be right, the previous owner did something. I like the idea of manipulating a update zip package.... Just have no idea how to do that.
Thanks for all your help
Click to expand...
Click to collapse
the warranty bit just proves the phone has been rooted before and the owner was messing around with the phone carelessly. Assuming youve been flashing official samsung tar files only, you weren't the one who triggered it.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Ethan9987 said:
Also, I don't think I have the ability to flash an update.zip without an SD Card right? Which this phone doesn't take one
Click to expand...
Click to collapse
Yeah I forgot that you cannot access internal memory in the situation you are in and also the no SD part kind of makes the whole thing worse.