It's been months since I had the rom 4.2.1 official from samsung with root access. The phone is somehow a lot slower than earlier and I wanted a fresh rom install. I tried to download the latest cyanogen through CWM but it gave me error. I wanted to flash the omni 4.4 kitkat through Philz but it was always giving me an error no file_contexts set_metadata_recursive and aborting installation.
I then had the insane idea of clicking 'factory reset - wipe data' I thought it would bring back to the last rom flashed....but it didn't. Now whatever I do, I go into the philz menu (i have all my data backed up I only worry about putting a fully working and FAST rom, the phone was getting stuck every few seconds).
I can access to philz and I can access to odin. What is your advice? What could I flash next? I also read that kitkat is not running well on the gt n7000....anything recommended for my situation?
******SOLVED
I flashed from Philz 5 with CWM 6.0.3.2 a cyanogen 10.1.3 from the microsd and it worked. I wrote on the microsd from a microsd reader.
Flash stock rom through odin.
Enviado desde mi GT-N7000 usando Tapatalk 4
majaretilla said:
Flash stock rom through odin.
Enviado desde mi GT-N7000 usando Tapatalk 4
Click to expand...
Click to collapse
odin detects the device on com port, kies detects the phone and I installed the usb drivers. BUT kies stays stuck on 'connecting...'
The only possibilities I have are philz and odin. Device is detected but cannot connect looks like. So I cannot flash anything apparently.
¿Did you try Odin with phone in download mode? Vol- + home + power
Enviado desde mi GT-N7000 usando Tapatalk 4
yes phone is in odin download mode. i connect the phone, kies stuck on 'connecting'. odin on windows find the com port but cannot connect.
If I try to flash .zip files from microsd through philz 5 interface, i get the "set metadata recursive some changes failed" error....followed by 'installation aborted' press any key.
This means I am stuck because I cannot flash stuff with odin from windows, and I cannot install zips on the phone from the phone.
rogermorse said:
odin detects the device on com port, kies detects the phone and I installed the usb drivers. BUT kies stays stuck on 'connecting...'
The only possibilities I have are philz and odin. Device is detected but cannot connect looks like. So I cannot flash anything apparently.
Click to expand...
Click to collapse
Remove Kies completely.
ThaiDai said:
Remove Kies completely.
Click to expand...
Click to collapse
i just installed it....today exactly because i had to connect the phone for odin...
should kies recognize the device even while in odin download mode ???
rogermorse said:
i just installed it....today exactly because i had to connect the phone for odin...
Click to expand...
Click to collapse
Use a separate Samsung USB driver package (please search for it yourself) , do not install it with Kies.
ThaiDai said:
Use a separate Samsung USB driver package (please search for it yourself) , do not install it with Kies.
Click to expand...
Click to collapse
i think something has changed just now. i'll wait till i finish downloading the stock rom to flash with odin and then see what happens.
But actually main question is: why can't i flash a rom with philz? I have put two roms on the microsd (one omnirom and one cyanogen official stable) and I keep getting the installation aborted message
ThaiDai said:
Use a separate Samsung USB driver package (please search for it yourself) , do not install it with Kies.
Click to expand...
Click to collapse
I agree, that should be ur next step.
Enviado desde mi GT-N7000 usando Tapatalk 4
rogermorse said:
i think something has changed just now. i'll wait till i finish downloading the stock rom to flash with odin and then see what happens.
But actually main question is: why can't i flash a rom with philz? I have put two roms on the microsd (one omnirom and one cyanogen official stable) and I keep getting the installation aborted message
Click to expand...
Click to collapse
Did you ever consider (in the nearly 5 years of XDA membership) that it might be a good idea to read the installation instructions for the rom you want to install or to search for an error happening to you. If you didn't consider this until now: the time has come to start.
And if you do not like to accept the help members offer it is essential to do these two activities youself.
ThaiDai said:
Did you ever consider (in the nearly 5 years of XDA membership) that it might be a good idea to read the installation instructions for the rom you want to install or to search for an error happening to you. If you didn't consider this until now: the time has come to start.
And if you do not like to accept the help members offer it is essential to do these two activities youself.
Click to expand...
Click to collapse
I read instructions of course....my problem was not related to instructions (although i think my recovery mod was not compatible with the omni rom i was trying to install) and that kies thing was an anomaly. I had to wait till the stock rom finished downloading to reboot (windows asked to reboot after some time....maybe related to the installation of usb drivers but i am not sure).
Finally through Philz I was able to install a cyanogen 10.1.3 from the microsd....why I got the error with those other roms is only part of my ignorance, as I said maybe the recovery i have was not compatible (???)
thanks anyway, if I need odin to recover root access or something I'll follow your instructions in case it still doesn't recognize the connected device.
Of course your problems are related to instructions and not reading/understanding. Because these problems occured many times and were solved and got part of tutorials, q&a etc.
i searched the forum, found a couple thread entitled exactly like mine. I think one of them even had the tag 'solved' in the title. Problem is, who solved the problem never included the solution, so what is the point....And I don't get this aggression, obviously if I have a problem I try everything to fix it. I would read instructions and I also googled a lot to understand why i was getting that error from the recovery zip installation....it is not like I don't try, why wouldn't I want to solve my own problems? Also people were receiving that same error with compatible recovery / roms images....and got around the problem with many tries but I did not find any particular solution written anywhere.
Related
Good evening everyone. :3
My I wanted to root and put a new ROM in my phone, and it didn't succed so well as I'd hoped for. /:
First off I I did a factory reset using the tool in settings. (That's a full wipe, right?)
After that I rooted my phone using this root thingie, and I chose to use Method 2: Root + CWM recovery, and I followed everything correctly and it seemed to have worked out fine, I had the CWM & the superuser app in my phone after the restart. c: I did not touch them though!
Anyways, before the rooting, I put the ROM in my DCIM library, and I chose to use the CHECKROM, V4.
So when I finished the rooting, I went to this ''volume up'' mode, and installed the ROM. C:
Once again everything seemed to go with the flow.
When the installation was complete & it said ''Everything is good, restart your phone''. I did, and now the screen is black, the only thing I see when I start it is the white text saying ''Samsung GT-N7000'', and it blurs/fades away.
I can't enter volume up mode (Recovery mode?), but I can enter the download mode.
FYI: After the rooting and the installtation of the ROM I made a backup!
I can't find my phone in my computer either, so I can't reach any files. /:
Please users of XDA, help me. :3
Yours sincerely Viktor
Edit: The phone is up and running now, flashed it back to the stock rom using Dr.Ketan's guide. .
Thanks a lot for that mate. C:<3
Now I'll try to root it & put a new ROM it again, I'll update this post wheter or not I succed.
Theres a thread like this at the top of the other forum. Enter download mode and flash stock rom using odin.
Sent from my GT-N7000 using xda premium
Yup, I've read it.. x:
But flashing this & dat, it doesn't make any sense to me. /:
And I've said I've been up all night reading, trying to learn how to do etc etc. x:
It's so frikkin' hard. o:
Did you flash the stock rom and is it ok now?
Sent from my GT-N7000 using xda premium
Uhm, I have no idea.. x:
When the phone didn't start I used Odin, followed a guide and ''put in a'' stockrom in the phone, but it was so buggy, I couldn't be in the menus because it crashed... x:
So I had to do a factory reset, and now the phone is working, but I can't use the Zergrush & the other guides to root it now.. :c
Yours sincerely Viktor
Viktorsvediin said:
Uhm, I have no idea.. x:
When the phone didn't start I used Odin, followed a guide and ''put in a'' stockrom in the phone, but it was so buggy, I couldn't be in the menus because it crashed... x:
So I had to do a factory reset, and now the phone is working, but I can't use the Zergrush & the other guides to root it now.. :c
Yours sincerely Viktor
Click to expand...
Click to collapse
You probably flashed a kl7 / 8 / la1-4 rom which are not directly rootable. You need to flash a older rom. Go to development forum and find out more.
Sent from my GT-N7000 using xda premium
Viktorsvediin said:
So I had to do a factory reset, and now the phone is working, but I can't use the Zergrush & the other guides to root it now.
Click to expand...
Click to collapse
I would download and flash a older rootable firmware version (afaik anything before KL7/KL8/LA1 ...) using Odin.
After that root and flash CF-Root kernel using Method 2 as described here.
Important: You need to use the right CF-Root kernel for the firmware version you flashed!
Next step would be booting into recovery and making a backup with CWM.
After that flash the rom you want to try using CWM in recovery mode.
Some devs advice to reboot twice after each flashing.
Search the instructions in the thread of the rom you want to flash for info about wiping (checkrom devs advise to do fullwipe before flashing).
First boot after flashing a rom might take some time, just wait a few minutes.
This is the CF-Root thread, also worth reading.
Nixchecker said:
I would download and flash a older rootable firmware version (afaik anything before KL7/KL8/LA1 ...) using Odin.
After that root and flash CF-Root kernel using Method 2 as described here.
Important: You need to use the right CF-Root kernel for the firmware version you flashed!
Next step would be booting into recovery and making a backup with CWM.
After that flash the rom you want to try using CWM in recovery mode.
Some devs advice to reboot twice after each flashing.
Search the instructions in the thread of the rom you want to flash for info about wiping (checkrom devs advise to do fullwipe before flashing).
First boot after flashing a rom might take some time, just wait a few minutes.
This is the CF-Root thread, also worth reading.
Click to expand...
Click to collapse
Are you sure I don't have the right firmware right now?
I got this one, N7000XBKK4 ------ 2.3.6 2011 November------- N7000OXXKK5--------------------- Nordic countries -----------------. And I downloaded and flashed it with Dr.ketan's guide.
I have tried to root it with CF now several times, but all it says when I start the root thingy is ''--- STARTING ----
--- WAITING FOR DEVICE''
After that it doesn't move at all. ):
Did you make sure to
- enable "USB DEBUGGING" (Menu\Settings\Applications\Development)?
- enable "UNKNOWN SOURCES" (Menu\Settings\Applications)?
Don't have Kies/Odin running while rooting, exit antivirus, pc suites, etc.
If it still doesn't work after that I'm afraid I can't help you.
Nixchecker said:
Did you make sure to
- enable "USB DEBUGGING" (Menu\Settings\Applications\Development)?
- enable "UNKNOWN SOURCES" (Menu\Settings\Applications)?
Don't have Kies/Odin running while rooting, exit antivirus, pc suites, etc.
If it still doesn't work after that I'm afraid I can't help you.
Click to expand...
Click to collapse
Yup, both of those where enabled, and kies were closed.
At this moment I am rooting using the zergrush exploit, I found the problem in the Rooting thread.
About Win7 64 bits user:
please try to run the "runme.bat" before connect the phone to computer.
1.disconnect your phone & computer
2.run "runme.bat", you can see cmd box, and process will stop on:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully * <---here
then connect the phone, and go on..
Click to expand...
Click to collapse
Yes I made an hard reset before I started the rooting.
I'll try to fix the ROM, again.. x: I'll be back soon to inform you of my success.. (;
Yours sincerely Viktor
H'okai, the rooting and the installation of the ROM was succesful.
Thing is that the booting loops all the time, and I never come to the home screen.
First it starts with the Samsung GT-N7000, and moves on to the blue stripes & dots(looks like your in space or something. :3 )
After that it gets stuck on the part when it says Samsung and it pulsases in blue around the logo.
After that the booting sequence restarts, and I've tried to install the ROM using CWM Recovery three times, and it still loops. /:
Yours sincerely Viktor
Edit: Googled and found this thread.
After the wipe in recovery mode the boot loop started and I can now enter the phone.
Quite interesting with this WIN7 64bit thing, didn't know about that.
Glad you got it running.
Don't forget to backup. ;-)
I have tried to install a custom rom (S5570XWKC1) but when i open odin it detects my device and then i add the TASS and everything works fine until i add the image:APBOOT_S5570XWKC1_CL935856_REV02... Odin stops responding and closes. I have tried different versions of odin and a different computer but its always the same. :s
use the latest odin version and follow all the steps carefully and it should work
kyrpäsieni said:
I have tried to install a custom rom (S5570XWKC1) but when i open odin it detects my device and then i add the TASS and everything works fine until i add the image:APBOOT_S5570XWKC1_CL935856_REV02... Odin stops responding and closes. I have tried different versions of odin and a different computer but its always the same. :s
Click to expand...
Click to collapse
Try downloading a new copy of odin and a new copy of the firmware as well..
I have now tried the different versions of odin and even different roms but it always does the same :/
are u putting the phone in download mode and then connecting to odin
and if its so try doing all the steps properly because normally this problem does not occur
Hmmm.. I agree with you buddy. Something's wrong here. You have to put all the files first in odin before you connect your phone in download mode..
Sent from my GT-S5570 using XDA App
I got it working... but now i have another problem D i was installing clockworkmod and it started bootlooping... i have done the wiping and tried different roms and everything but it keeps looping any idea what i should do? all i want now is my phone working :s
u are very confused in doing all these things so u are getting problems
please read the threads about flashing and installing rom and cwm carefully and it will work
kyrpäsieni said:
I got it working... but now i have another problem D i was installing clockworkmod and it started bootlooping... i have done the wiping and tried different roms and everything but it keeps looping any idea what i should do? all i want now is my phone working :s
Click to expand...
Click to collapse
It seems like you are new to eveyrhting and thus getting into problem with each step... Don't worry, no one can get it right the first time. What you ought to do is read through the thread and learn a lot of information. I have also made it easy for new Samsung Galaxy Mini Users and have posted clear step by step instructions on flashing, rooting, installing CWM recovery and many more at http://yagyagaire.blogspot.com
Visit that too (link on my signature) and you will know everything and will be able to do it without any errors. I am sure you will find it useful
Now everything is ok. I have the cyanogen mod 7.1 installed and an overclocked kernel (782Mhz) but i have seen videos where its 825 or 864. Does anyone have a link to an overclocked kernel for CM7.1, that would be 800Mhz or over or do i have to have CM7.2?
How did you get it to work and respond?
kyrpäsieni said:
Now everything is ok. I have the cyanogen mod 7.1 installed and an overclocked kernel (782Mhz) but i have seen videos where its 825 or 864. Does anyone have a link to an overclocked kernel for CM7.1, that would be 800Mhz or over or do i have to have CM7.2?
Click to expand...
Click to collapse
I'm having issues with version 3.07 and 3.09 of Odin on a HP windows 7 PC. It keeps saying "Not responding" immediate. I'm on a Samsung Galaxy S5 Developers Edition. http://forum.xda-developers.com/showthread.php?t=2747156&page=3
Today I tried to update my phone to a new custom rom.
I followed the instructions of the threads and tried to get it to work.
Of course it didn't work or else I wouldn't be here right now asking for help.
Here's the current situation.
I am able to boot into download mode + recovery mode and also boot into cwmr and install a different kernel.
I used pc odin to install it each time and it does pass and the rom (i've tried installing a gingerbread rom so that I can try everything again) does install.
the problem is that it is currently stuck in a boot loop at the "Samsung galaxy note gt-N7000" screen.
I have looked up dr.ketan's posts and tried some too.
currently i am booting abyss note kernel 42cwt touch original. (I know for sure it is a workable kernel because I've been using it this whole time.
here's what i've done. please tell me what i've done wrong and the possible ways to reverse it.
1. backed up everything
2. went into recovery
3. factory reset/cache clear
4. use pc odin to install new kernel (since I was looking into switching to another kernel anyways)
5. use pc odin again to install gingerbread rom (I do get the green light saying it did get installed
6. phone auto reboots
7. it gets stuck at the boot loop like i have mentioned above
i will try to attach a few pictures of my note as soon as I can so you can see what's going on with it.
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
nokiamodeln91 said:
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
Click to expand...
Click to collapse
Right now it reboots to 3e recovery.
The rom that I tried to inject to it is currently a the stock gingerbread rom from dr. Ketans thread.
The rom that I had on it is the official ics rom for the hk region.
The rom that I wanted to inject to it was a custom jb rom that uses hydracore as a kernel.
Thanks!!
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
nokiamodeln91 said:
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
Click to expand...
Click to collapse
If I do a stock ics update can I just do it through kies or do I have to do it through pc odin? Also. Would abyss or hydracore considered as a safe kernel???
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
nokiamodeln91 said:
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
Click to expand...
Click to collapse
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Well I am not sure but I soft bricked my phone when I tried that Abyss Kernel. In my view Hydracore is safe. Philz is super safe.
Flash ICS which matches your region using Odin. If phone boots flash Philz, If not, then be ready to read a lot of stuff or get phone repaired.
asian_boi said:
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Click to expand...
Click to collapse
instead of flashing kernels. flash a complete rom using PC odin.
nokiamodeln91 said:
instead of flashing kernels. flash a complete rom using PC odin.
Click to expand...
Click to collapse
You have so much patience
Sent from my Amazon Kindle Fire using Tapatalk 2
the only thing i have...
Hey guys. my note seems to have cooperated and allowed me to flash a new rom and also a new kernel. Here's the catch though, now it's stuck in the samsung logo and won't boot beyond that. Any suggestions of what to do? I am continually searching on the forums to find a solution.
At least I'm happy to know it's not a brick that can't be fixed.
Thanks nokiamodeIn91 for your help so far. I really appreciate it.
which rom did you flash and which kernel? how?
He spent a lot of time helping you. Be sure to hit thanks button
Sent from my GT-N7000 using Tapatalk 2
I currently flashed the abyss note kernel 42 cw touch and I downloaded an old gb rom from sammobile .
Here's what I did.
1. Put my phone into download mode
2. Run as admin on PC Odin
3. Selected the Abyss kernel then flashed it.
4. Boot into the cmw, wiped cache then booted the phone into download mode again.
5. Then I installed the old GB Rom on to my phone and restarted it.
6. Phone starts, loads past the GT-N7000 logo and goes into the samsung boot logo.
7. Phone repeats the animation of the samsung logo a time or two then restarts on its own. This loops until the phone is completely drained. I know that the rom works because that was the rom that I used to root my phone. I definitely don't mind downloading another rom if I have to.
my current goal, if we can fix this, is to quickly just update to the official jb rom for n7000 and not play around with the rooting and such until I have even more time to learn more.
at least I know for sure my phone isn't hardbricked, I would imagine I have either missed a step or something that caused the problem.
I have read through the forum and I did come across one post talking about checking my phone's partition and such.
I got to be honest, I'm really not technically skilled enough at this point in time to dare to mess around with that type of thing yet especially with so much coding to make sense of it. (I know this is kind of dumb to say especially when I rooted my phone and screwed up this bad). More importantly, I don't even know for sure if I need to do a partition or not.
Please let me know what I did wrong and how I can fix it.
I got a question though (out of curiosity), how come there's no toolkit for the n7000 like the S3 and also the note 2???
this is the name of the old gb rom that I tried flashing.
N7000ZSKJ6_N7000OZSKJ6_N7000XXKJ6_HOME.tar
I actually have tried several other roms as well (from GB-JB, official and custom) and all of them so far has gotten to the samsung boot logo
I have read on the forums to try using Philz-cwm 6 kernel but I don't know if it'd solve my problem.
let me show you one of the threads I have read, if I dived into the wrong material let me know and I won't consider using it (or learn how to use it) for my current situation
http://forum.xda-developers.com/showthread.php?t=1661590&highlight=samsung+logo+bootloop&page=2
like I was saying before, I really have no experience in coding so all the things that really made near no sense to me. I understand the basic concept of what its trying to do it's just seems like a very unsafe method for me to try especially when I lack the necessary knowledge in this area of expertise.
did you flash the GB rom using the standard PIT file ?
also you could try with the 5 file flashing method from this thread
http://forum.xda-developers.com/showthread.php?t=1530501
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
asf58967 said:
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
Click to expand...
Click to collapse
Yeah true... should also format system..
**** if you can boot into recovery , do a facotry wipe now
Hi guys.
My S3 mini is so freaking slow when opening the camera and when ending a call. There's 2-3 seconds of idle before it "gets on with the show".
Do you know of any roms that don't have these lags? I don't use any of the samsung stuff, so a clean rom would be ok as well..
Also - I'm on a Mac - so any rom images that will flash via Heimdall would be prefferred (all the roms I've tried gives a bad checksum error and won't flash)
A million thanks in advance
Sendt fra min GT-I8190 med Tapatalk2
i use dmodv5 , search it on development section , got aroma installer and is smooth . Ain't got a lag on calling / camera
alecore said:
i use dmodv5 , search it on development section , got aroma installer and is smooth . Ain't got a lag on calling / camera
Click to expand...
Click to collapse
Agree, flash it with CWM or TWRP, so, no matter if you are on a Mac
But my problem also concerns CWM which I have downloaded from www.clockworkmod.com - all roms and cwm packages I have tried gives me a checksum error in heimdall - and then refuses to flash anything towards the phone.
(and I have NO access to a Windows with Odin)
Sendt fra min GT-I8190 med Tapatalk2
If your phone is rooted than install rom manager and install cwm recovery via the rom Manager app
And dont use the computer for flashing, use the recovery.
Sent from my GT-I8190 using Tapatalk 4 Beta
Just to clarify: my phone is NOT rooted, as i have yet to find a rom that heimdall will let me flash.
I have bought Mobile Odin, Rom Manager and many other like that on Play Store, but they have no effect until I can flash a CWM or the like on my phone (and then another rom ofcourse).
So first things first, you have to root your phone..
It would be easiest if you could get a hold to a windows pc.. Some friend's pc..
Sent from my GT-I8190 using Tapatalk 4 Beta
Yes i know - but that's not an option right now.
(all my windows friends are leechers on pirate bay or the like, running virus infected pirated windows - an therefore unclean systems)
I only have access to Mac OS X and Ubuntu in terms of systems i know to be legit and clean / safe..
/BBK
Have you checked this guide? http://forum.xda-developers.com/showthread.php?t=2066668
Here is a rom who was flashed in ubuntu.
Once you got root, you can flash any rom.
Thank you rafo. I'll check it out when I get home from work
/BBK
So - I've been trying that Ubuntu rooting - but without luck. ADB can see my device and so can Heimdall, but I get a libusb error 3 no matter what i try, when i try reading PIT or sending anything towards the phone.. Any ideas?
Any help is greatly appreciated
/BBK
So.. I've given up on Ubuntu and gone back to the Mac OSX. Anyway the commands are the same in ADB and such..
BUT how do i flash the clockworkmod.img or a rooted rom on to the phone without Odin ? - Heimdall won't read any of the files I've tried, so I'm stuck with only having the Android Developer Tools at my disposal.
When the phone is turned on and started up, I can see it using "adb devices" - but then what ?
I can get into Download Mode and the stock Recovery - but where do I go from here ? (I can't find anything on the forum)
I have downloaded a rooted rom and cwm touch just waiting for more help
I know this is probably the stupidest thing one can do and since I mediocre knowledge about Android stuff I just did that. While I was on CWM recovery mode I was tinkering around the settings and I accidentally deleted the OS, this leaves me soft-bricked (is that the term)? When I boot up on recovery mode again it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." But when I connect it to Kies it doesn't detect the phone! And when I boot up download mode it says I have Custom binaries (it says 3) which I suppose is because I had CWM? I have no idea how I could re-install my OS back to my phone and am panicking since this was my first phone. Is flashing back to stock firmware a viable option if I accidentally deleted my OS? Or so I have to do some other process? Please I am in dire need of assistance here!
Xbrekker said:
I know this is probably the stupidest thing one can do and since I mediocre knowledge about Android stuff I just did that. While I was on CWM recovery mode I was tinkering around the settings and I accidentally deleted the OS, this leaves me soft-bricked (is that the term)? When I boot up on recovery mode again it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." But when I connect it to Kies it doesn't detect the phone! And when I boot up download mode it says I have Custom binaries (it says 3) which I suppose is because I had CWM? I have no idea how I could re-install my OS back to my phone and am panicking since this was my first phone. Is flashing back to stock firmware a viable option if I accidentally deleted my OS? Or so I have to do some other process? Please I am in dire need of assistance here!
Click to expand...
Click to collapse
Yes just flash back stock firmware with Odin.
That custom binary is probably from the time of GB because root method was increasing it. You can use Triangle away to reset it, it is free on xda.
shut_down said:
Yes just flash back stock firmware with Odin.
That custom binary is probably from the time of GB because root method was increasing it. You can use Triangle away to reset it, it is free on xda.
Click to expand...
Click to collapse
Do you have any idea which version of Odin can detect the S Advance because one's I have have seem to not detect them at all. Specifically 4.43 3.07 and 1.85. Thanks.
Xbrekker said:
Do you have any idea which version of Odin can detect the S Advance because one's I have have seem to not detect them at all. Specifically 4.43 3.07 and 1.85. Thanks.
Click to expand...
Click to collapse
You have Samsung USB drivers installed? If you have kies - kill it in Windows. I used 3.07.
shut_down said:
You have Samsung USB drivers installed? If you have kies - kill it in Windows. I used 3.07.
Click to expand...
Click to collapse
I have kies and I always close it before opening, doesn't appear. Even the switch port thing doesn't. I'm going to try out 3.09. Since I accidentally deleted my OS doesn't that mean Windows won't detect it even if it's on download mode? Sorry I really have no idea what I'm doing. oh yes I have the Drivers installed.
Xbrekker said:
I have kies and I always close it before opening, doesn't appear. Even the switch port thing doesn't. I'm going to try out 3.09. Since I accidentally deleted my OS doesn't that mean Windows won't detect it even if it's on download mode? Sorry I really have no idea what I'm doing. oh yes I have the Drivers installed.
Click to expand...
Click to collapse
Odin does not have anything to do with system partition, I mean it will work anyway. Do not just close Kies, go to task manager and kill it (in Windows).
P.S. If you have any ROM in your sd card, you can go to CWM and install it. Or if you have some other phone, put SD card in it, copy ROM and install it in CWM.
Gonna use this topic becaus i think i have simmilar problem.
So i rooted my phone and installed sucsesfully a custom rom with this guide: http://forum.xda-developers.com/showthread.php?t=2198341
Then i wanted to install another cutom rom and i booted into recovery and it was not TWRP as i used it when i installed custom rom but CWM, and i dont know what was i thinking i installed over it again CoCore + TWRP
So i do have acces to TWRP but i cant install anything, i get constalty this error:
E: Unable to mount /preload
How can i fix it?
Thanks for help