I am trying to get back to stock firmware/rom after having LineageOS.
I got Odin and downloaded several stock rom files and none of the work properly, I can flash them and the tablet starts in what looks to be the default initial setup but the apps keep stopping before I an even tap anything, sever apps like keyboard, one drive and so on, basically all apps crash at the same time.
I believe I am not getting the right rom, but I have no idea how to find out what the right one is, does the country really matter that much ?
Nrby said:
I am trying to get back to stock firmware/rom after having LineageOS.
I got Odin and downloaded several stock rom files and none of the work properly, I can flash them and the tablet starts in what looks to be the default initial setup but the apps keep stopping before I an even tap anything, sever apps like keyboard, one drive and so on, basically all apps crash at the same time.
I believe I am not getting the right rom, but I have no idea how to find out what the right one is, does the country really matter that much ?
Click to expand...
Click to collapse
Where did you get them from?
I used SamFirm_Reborn and got the correct multiple part 9er as I've flashed back to stock twice already.
Although my T825 is on LOS19.1 atm.
Were you using single or multiple part ROM?
bmwdroid said:
Where did you get them from?
I used SamFirm_Reborn and got the correct multiple part 9er as I've flashed back to stock twice already.
Although my T825 is on LOS19.1 atm.
Were you using single or multiple part ROM?
Click to expand...
Click to collapse
i downloaded from several sites, always the 4 part, always android 9 latest patch, tried the romanian version since I it was bought new in romania but that's probably not a guarantee
@Nrby I recommend using Samfirm as it downloads directly from Samsungs servers.
Just to make sure you get an original.
@Nrby btw which Odin version?
finished downloading/decrypting with SamFirm_Reborn_0.3.6.3, used Odin3_v3.14.4 to flash the files, worked well and I get the same issue after the reboot, it tries to initialize and then just keeps trying to close apps until it reboots, could this have something to do with the wrong rom ? how can I even determine what region I need at this stage ?
@Nrby which region code did you use?
checked here?
Samsung CSC Codes List (All) | Change CSC on Samsung Devices
Today, we'll explain Samsung CSC codes. Besides, we also have a list of CSC codes or region codes with a method to change CSC on Samsung.
www.droidviews.com
Was it at that stage connected to Wifi or mobile already?
bmwdroid said:
@Nrby which region code did you use?
checked here?
Samsung CSC Codes List (All) | Change CSC on Samsung Devices
Today, we'll explain Samsung CSC codes. Besides, we also have a list of CSC codes or region codes with a method to change CSC on Samsung.
www.droidviews.com
Was it at that stage connected to Wifi or mobile already?
Click to expand...
Click to collapse
never got there, the Samsung Keyboard is also one of the apps that keep crashing so I can't enter the password.
I'm not even sure if it has anything to do with the CSC, I can see the build in the recovery menue, the questions is am I seeing the original firmware code or the one I flashed now ?
Nrby said:
.... , the questions is am I seeing the original firmware code or the one I flashed now ?
Click to expand...
Click to collapse
Afaik you only see what you flashed.
Original ROM might be noted on the box it came with.
I'm no step further, I have no idea what the original rom was, and not sure how to find out
I don't even know if that might solve the problem
I've attached all the information I can gather from the box/tablet in it's current state
@Nrby I've compared on sammobile some stock ROM versions for Europe and for T825XXU3CTD1 and the CSC is at least identical between Romania, Greece, Czech, Germany, Poland. They all have the OXX.
I doubt that your problem has anything to do with the CSC as apps crash even before connecting to any mobile provider.
Tried flashing stock ROM several times one after another while staying in download/Odin mode all the time?
I remember that this helped me once on a different device.
thanks a lot, worked after around 4-5 flashes, it's a bit slow, might still have some issues but seems to run stable for now, really didn't expect this to work
Nrby said:
thanks a lot, worked after around 4-5 flashes, it's a bit slow, might still have some issues but seems to run stable for now, really didn't expect this to work
Click to expand...
Click to collapse
Glad that my hint helped.
Perhaps useful for other users if you mark the thread as solved then they find the solution when having the same issue.
Related
Seeing as I`m still a relatively noobish poster I`m unable to ask this question in the relevant thread. I`ve just debranded the phone following the 8 step guide but I had issues following step 8 where you change the CSC code. I couldnt quite figure it out so step 8 never got followed. As a result, despite losing the Three branding on the phone I now have a phone that displays the CSC as "unknown" and may well explain why Kies cannot pick up the firmware version on the phone. If I follow step 8 and key in *#272*<your IMEI># on my phone it then shows me a screen headed "Preconfig" with "Sales Code" underneath and "H3G" in the box to the right. Underneath is a radio button thats deselected. if I press to highlight it then press "install" at the bottom of the screen I keep getting an error saying "Must be THREE chars".
Can anyone shed any light on this and give me any hope of rectifying?
Will I need to manually input the Three APN settings once I successfuly change the CSC code?
Thanks in advance. I have spent ages scouring the web but there`s not a great deal of info out there about the CSC part of the debranding process.
id like some more info on how important the csc is too, im got told it hold some carrier information but i dont know if that is true or not.
the reason you cant pick on is probably as since debranding you havent flashed the csc you need, you could find the one you need for your firmware over in the dev section.
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
RedAl said:
Cheers for the reply, interestingly i`ve just re-flashed the phone and this time it is showing my CSC as XEU. Even so, I still cannot follow step 8. When I input that code including my IMEI in it shows XEU but when I press "install" it gives me the same old error of "Must be THREE chars". So not sure whether its worked or not and what diference it makes. At least Kies now shows something in the firmware field, even if it doesnt show what I was expecting. Hopefully someone can assist with this at some point later.
Click to expand...
Click to collapse
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
redbullman said:
Hi there
If it says XEU after inputting the imei then it's working fine. You're not supposed to have to press install at this stage. Also to make sure it's working fine, I always boot into recovery mode. If you look down the code as recovery is loading, it will say which csc is being used/implemented (xue etc). Always reset data in recovery after rom flash from (especially from different csc.
I've had issues in the past when I flashed back to T-Mobile (after originally flashing ke7 stock) and then back again to T-Mobile. When I re-flashed back to stock after this, I couldn't get it to change from tmu (t-mobile) csc back to xeu, no matter how I flashed it. In the end the only way I could revert csc back to xeu was using the jig I had purchased. Apart from resetting the customer binery counter, it seemed to reset other settings, as once I had done this, I was able to install stock ke7 with xeu csc.
Click to expand...
Click to collapse
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
RedAl said:
Cheers for that. I just did a recovery as you suggested and saw it was done using the Multi-CSC so hopefully that means its all sorted.
Does this mean I should now be able to see the latest Firmware update available in Kies?
Click to expand...
Click to collapse
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
redbullman said:
Yes you should be able to see the latest available update for your csc via kies. Although kies seems much slower to get the updates. It's much easier to use Odin. Most people update by this method. It's really easy and pretty safe.
Click to expand...
Click to collapse
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
redbullman said:
The csc will be sorted now. Also if you plug your phone into kies, this will confirm what csc you are using.
Click to expand...
Click to collapse
Cheers Redbullman. I can get into Kies now but on the firmware information section it says "Current Firmware Version : PDA:KDD / PHONE:KDH / CSC:KD1 (H3G)"
Its not telling me there`s a firmware update available so I have a horrible feeling something`s still not quite right but I`ve flashed it twice now and done 2 factory resets.
Would it be easier to find the stock KE7 kernel (forgive me if I`m using the wrong words) in Odin to flash it that way? If I can manually do it then I`d rather do it that way. Only problem is I`ve not yet found any tutorials on doing that, unless its the same (mostly) as the tutorial for debranding, except using a different .tar file (KE7).
Hello!
I've been researching a lot the last few days about flashing ROMs, Unbranding and Root etc..
i currently have SGS2 which is also my first Smartphone / Andriod Phone.
So even tho I've read FAQ's Wikis guides. etc i still have some things to get cleared up. which i hope some here could help me with ^_^.
1. I live in Scandinavia, more specific Denmark. Do i have to use Certain "CSC" and "PHONE" Number/Codes, for the phone to work, where i live. afaik. the CSC and Phone is the things that controls WIFI BT GPS, and the 2g/3g networks.
2. Sometimes i see people mention "Kernel" and that its important to use a rom based on the same "kernel" is kernel just another word for firmware? the thing is i think its entirely different. some clarification is needed here.
3. If i flash a modified Stock rom To my phone. with ROOT CWM for example this one (http://forum.xda-developers.com/showthread.php?t=1103399). is it possible to undo Root and CWM. i'm in doubt because further down in the thread, he states by flashing a stock rom onto the phone, you can remove the triangle but not the root and cwm.
This is the things that is still unclear for me. and since it's my first time to try and do all this, i must be 100% sure, i understand it all correctly.
Thanks!
Edited the first post.
If the questions is hard to understand, i can try and Re-formulate them.
//Tolana
1. I live in Scandinavia, more specific Denmark. Do i have to use Certain "CSC" and "PHONE" Number/Codes, for the phone to work, where i live. afaik. the CSC and Phone is the things that controls WIFI BT GPS, and the 2g/3g networks.
on your dialler enter *#1234# and look at the last 3 letters of the description under PDA.
- You will also find this info if you go in to settings\about phone\Baseband Version
2. Sometimes i see people mention "Kernel" and that its important to use a rom based on the same "kernel" is kernel just another word for firmware? the thing is i think its entirely different. some clarification is needed here.
Similar to what I mentioned above, use one of the ROMs that has the same 'extension' as your phone now as it is most likely using the same modem etc..
3. If i flash a modified Stock rom To my phone. with ROOT CWM for example this one (http://forum.xda-developers.com/showthread.php?t=1103399). is it possible to undo Root and CWM. i'm in doubt because further down in the thread, he states by flashing a stock rom onto the phone, you can remove the triangle but not the root and cwm.
If you flash a stock, unmodified ROM, it will remove root. It's like getting an update from Samsung directly.
Tolana said:
Hello!
I've been researching a lot the last few days about flashing ROMs, Unbranding and Root etc..
i currently have SGS2 which is also my first Smartphone / Andriod Phone.
So even tho I've read FAQ's Wikis guides. etc i still have some things to get cleared up. which i hope some here could help me with ^_^.
2. Sometimes i see people mention "Kernel" and that its important to use a rom based on the same "kernel" is kernel just another word for firmware? the thing is i think its entirely different. some clarification is needed here.
Kernel is not firmware its the base below OS level that communicates with the CPU . Firmware is a full package CSC Modem OS Kernel APPS .
Kernels can be mixed but thats a user choice and user accepts it may not work well .
3. If i flash a modified Stock rom To my phone. with ROOT CWM for example this one (http://forum.xda-developers.com/sho...ecovery jig .
Makes it much easier .
jje
Click to expand...
Click to collapse
Thanks for the answers.
I'm still a bit unclear on my first subject.
The Modem/PHONE number, does it have to be a specific "Scandinavia Compatible" Number/Code for my phone to function with calls etc.
the same goes for the CSC code.
Thanks again.
//Tolana
Some users report that particular radios/modems work better in certain countries than others, but you sohuld be able to use ANY of the modem/radios found on these forums on your SGS2.
For example, my phone came with KE1 radio. I flashed KE7 to match the cf kernel installed when rooting. It works fine
Right. Thank You!
Hi all....
I am an infrequent user of this site, the last time I pored over the information housed in here was a couple of years ago when I found the site and various threads invaluable for me when rooting my old and trusty HTC Desire.
I am now the owner of a fab and groovy galaxy S3 which I aquired in the UK from carphone warehouse.
I am using Vodafone as a carrier, but my understanding is that the stock phone was not tied in any way to a carrier.
It didn't take me long to root the phone, I only rooted the device because I wanted to get rid of various bits of samsung/bloatware, not in order to Flash a new rom to the phone.
I was more than happy with this until I received a notification that there was an OTA update, this I deemed to be the JB OS, which of course would not install due to the fact the phone was rooted and was using cwm etc.
After a week of cancelling the update and being reminded of it every three hours I decided that it was maybe time to update, I discovered that in order to do this I needed in effect to put the phone back to its factory state, soo I completed a factory reset on the phone and in no time at all I was up and running again with an unrooted S3....however, despite this in the last three weeks I have seen hide nor hair of the update that seemed to be banging at my door for so long!
My question therefore is:
is there something I am unaware of that is now stopping my phone from receiving the OTA update via settings/about device/software update/update(check for updates)?
To help those of you that know about this stuff here are the details from the phone that may help you to help me...and anyone else not in the know enough!
Device Status = Normal (while rooted this obviously showed as being modified)
Model Number GT-19300
Android version 4.0.4
baseband version - 19300XXLG8
kernel version - 3.0.15-928452-user [email protected] #1 SMP PREEMPT Thu Jul 26 12:06:08 KST 2012
Build Number IMM76D.19300XXBLGB
In addition prior to unrooting the phone the foillowing info was parsed and returned :
AP: 19300XXBLG8
CP: 19300XXLH1
CSC: 19300OXABLG8
Following unrooting and completing a factory reset.....the same process returns this information.....
AP: 19300XXBLG8
CP: 19300XXLG8
CSC: Unknown.
My apologies for the length of the post for what is probably a trivial matter, but as a Phone noob (but a systems pro) you can never have too much info!
many thanks in anticipation!
It's because your CSC was lost when you unrooted and hence OTA won't work. You would have been better off using the toolkit (see original development forum) to simply download and flash the JB ROM yourself, then no need to unroot etc.
You can still do this and you'll also get updates usually faster than OTA.
Regarding your bust CSC, try:
http://forum.xda-developers.com/showthread.php?t=1845103
Hmmm...well...
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
I'm not quite sure why you want to fix it, flashing jb yourself is much quicker, but a quick search found:
Q. I have flashed XXXX ROM and now my CSC is unknown?
A. Generally Speaking CSC does not make much of a difference. If you are really facing a problem which is related to CSC such as some specific apps not working, some language not there etc. Either:
Use
Type *#272*Device IMEI# at Phone dial pad.
Select the CSC that you want.
Click Install.
or Install CSC changer app from the Market and change the CSC
Both ways yopur device will be factory resetted.
Good luck.
I can....
...find all of that myself, It doesn't really help much if the person searching amongst the huge amount of disarticulated information liberally strewn around this forum is faced constantly with broken links or unhelpful replies and threads that vanish up their own orifice.
In order to decorticate that information it helps if some form of standardisation or common language is employed.
I have my reasons for asking the original question.
I am facing a problem and asking for advice and help in order to rectify the issue.
I have tried to flash the JB ROm myself, I am despite what you may consider not stupid, however, I am receiving errors when flashing the rom from the 'update' menu from the recovery menu within the phone.
Elsewhere on this forum I discover that it may be an issue with the csc being in an unknown state, hence my post in the first place, If I was able to follow the instructions and all was working as it should I would not bother anyone here or indeed waste my time doing so.
by querying the csc by using the dial pad it shows me that the correct one is still there, so installing it seems pointless, however, as stated at the very beginning of the question, when parsing the phone for detail info it tells me that the csc is 'UNKNOWN'
Greywolf907 said:
many thanks for the info re the cause of the issue, however, having looked at the following I still am having no joy.
1) downloaded a correct csc file and using odin flashed it to my phone, however, it is still showing the same information as before.
2) Found a stock Rom. the exact same Rom as that which is installed, that has been flashed using Odin and once again, upon reboot the information is exactly the same.
Click to expand...
Click to collapse
Try installing this from the Android Market
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&
Run it and update your CSC to your correct one
EDIT :- Just looked at your phone info in post 1 again, this relates to UK unbranded version so your CSC should be BTU
You shouldn't normally have a problem updating a rooted phone to newer versions provided the base rom is still stock I have never had a problem with mine but everyone is different I guess, I did mine via Kies then just re-rooted afterwards.
...well...
ag4751 said:
Try installing this from the Android Market
Run it and update your CSC to your correct one
Click to expand...
Click to collapse
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Greywolf907 said:
Hi and thank you also...however, I have checked the sales code and it is properly installed and shown as being BTU, which is correct, this is shown of course by typing into the dial pad...et al ad nausea....whatever, it is correctly displayed, the issue is that when typing into the dial pad *#1234# in order to retrieve the information contained there, it is returning CSC UNKNOWN.
Click to expand...
Click to collapse
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
http://www.sammobile.com/firmware/?page=3&model=GT-I9300&pcode=BTU&os=1&type=1#firmware
......not
ag4751 said:
OK you wrote this while I was writing my edit in the previous post.
Have you tried just installing the latest 4.1.1 BTU version using Odin you can get it from the Sammobile web site its the PDA version I9300XXDLJ4
....that version no........I did d/l and try this version
United Kingdom 8 Sep 2012 4.1.1 I9300XXBLG8 I9300XXDLI4 283.2 MB Download
which seemed to be relevant to my original build, this is the one that I have been having issues with.
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
I am as I type sucking the file you suggest down and as soon as hotfile finishes dribbling it into my machine I'll give it a bash and let you know what happens.....many many thanks for taking the time to help me and do it with such good grace and civility, it's refreshing.
Cheers for now!
PS: I tried Kies, on three different machines, two running XP and one running Seven, each time it just doesnt want to know that the phone is even connected...ie. it knows its there, but just doesnt want to actually connect to it...just whirrs and clicks until I get fed up and unplug it....hence the grief I am having one way or another trying to update the O/S...so I can root it again!
Click to expand...
Click to collapse
I am also somewhat confused as to how to install the zip file via Odin, I more or less think that the pda file needs to be a single tar/md5 file and of course these things are coming as zips...well..at least the last one I d/l'd did.....
Click to expand...
Click to collapse
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
mucho...
ag4751 said:
You need to extract the file located inside the zip file, then start Odin, click the PDA button and find the extracted file, put your phone in download mode, connect to your PC, wait for Odin to connect then start the update.
Click to expand...
Click to collapse
yes I understand all that bit, I didn't make myself clear maybe....The problem I had was that the file I had downloaded seemed to be a zip file containing the whole system, i.e a cloned image, it didn't work...however, the link you so very helpfully provided was just waht i was looking for and couldn't find myself, a single tar/md5 file which has been downloaded, installed and is up and running....I now have JB, but still the csc is classified as unknown...anyhow, that doesn't matter much until the next time I need to update.
My very best regards to you and huge thanks.
have a good 'un
:good:
Got there eventually, strange abut the CSC
If you want to root your phone use this thread, 3rd post if you don't already have it
http://forum.xda-developers.com/showthread.php?t=1957273
Then install this for easy access to recovery
http://forum.xda-developers.com/showthread.php?t=1768142
So here's my problem: I bought my SGS3 in China (CHU firmware)but it doesn't come stock with Google Play Store and a bunch of bloatware I can't even read, Every time I update my firmware (KIES/OTA) i lose my root and all my Google apps. And now I cannot install Gapps on the new 4.3 CHU firmware (recovery gives me error). I'd like to switch to a different firmware that has Google apps native to it. I tired Cyanogenmod for a time but missed some of the features that the Samsung stock firmwares provided. I've also heard about a leaked BTU firmware from the UK that sounds appealing but every time I try to flash (via Odin) it fails. I've also heard that I would need to change my CSC in order to use Kies with a new firmware but my phone only has a single CSC and errors out every time I try to change the CSC. Now quite sure how to proceed.Everything on my phone is in English but sometimes the Chinese still come through ie. error message and even the prompts to get into download mode.
So, does anyone have experience completely changing a phone from one country to another, firmware and all? What about the problems installing Gapps, any ideas?
Help, please!
notalocalpeople said:
So here's my problem: I bought my SGS3 in China (CHU firmware)but it doesn't come stock with Google Play Store and a bunch of bloatware I can't even read, Every time I update my firmware (KIES/OTA) i lose my root and all my Google apps. And now I cannot install Gapps on the new 4.3 CHU firmware (recovery gives me error). I'd like to switch to a different firmware that has Google apps native to it. I tired Cyanogenmod for a time but missed some of the features that the Samsung stock firmwares provided. I've also heard about a leaked BTU firmware from the UK that sounds appealing but every time I try to flash (via Odin) it fails. I've also heard that I would need to change my CSC in order to use Kies with a new firmware but my phone only has a single CSC and errors out every time I try to change the CSC. Now quite sure how to proceed.Everything on my phone is in English but sometimes the Chinese still come through ie. error message and even the prompts to get into download mode.
So, does anyone have experience completely changing a phone from one country to another, firmware and all? What about the problems installing Gapps, any ideas?
Help, please!
Click to expand...
Click to collapse
You can flash stock ROMs compiled by different devs which are deodexed and prerooted(with supersu as system app) and with some performance tweaks like init.d support etc..go to s3 general section and you can find those compiled zip files flashable thru any custom recovery.. But follow the instructions given to flash it and done...you will have the best stock experience and that too which you can customise and with performance and battery tweaks..
Sent from my GT-I9300 using xda app-developers app
Hi all,
I have the SM-N9005 Galaxy Note 3 (Snapdragon) running android 4.4.2. I had a bit of a **** up the other day and finally managed to get my phone booting again. My issue now is that I can't seem to root my phone at all.
A copy of SuperSU was installed (by a failed CF-Auto-Root while trying to fix my device), but wouldn't run when I tried it. I've now tried to root the device by:
CF-Auto-Root - Runs smoothly but still no root
Towelroot - Device not supported message
CWM -> Install via zip - Says it worked but root unsuccessful
Kingo - Failed to root
I've tried multiple things now but no matter what I do, the final result will be a device that isn't rooted even if whatever rooting method says it was successful. I also can't run apps that won't run on rooted devices because they think my device is rooted (not sure if this is knox? mine has been tripped).
Anyone have any idea?
Try root genius it works
Downloaded root genius, ran it, everything went perfect and it said "Gratz".
Still no root according to root checker and Xposed. I have Kinguser installed now too which says root access is "ON".
Sidalol said:
Downloaded root genius, ran it, everything went perfect and it said "Gratz".
Still no root according to root checker and Xposed. I have Kinguser installed now too which says root access is "ON".
Click to expand...
Click to collapse
Anyone giving you advice on how to root without knowing your build version of the software you are currently using shouldn't be trying to "help". Since you have not had any success and having leftover apps / files that you can't delete without root means you should reinstall the stock operating system via Odin and restart the process. You absolutely need to be aware of the build version - just saying I have 4.3 or 4.4.2 installed is not enough information and the methods can vary depending on that and even, sometimes, via carrier or region.
es0tericcha0s said:
Anyone giving you advice on how to root without knowing your build version of the software you are currently using shouldn't be trying to "help". Since you have not had any success and having leftover apps / files that you can't delete without root means you should reinstall the stock operating system via Odin and restart the process. You absolutely need to be aware of the build version - just saying I have 4.3 or 4.4.2 installed is not enough information and the methods can vary depending on that and even, sometimes, via carrier or region.
Click to expand...
Click to collapse
Oh man that's how I broke it the first time. I didn't realise I needed version numbers etc, I simply followed te "how to unroot galaxy note 3" guide on galaxynote3root. The guide looked simple enough and linked me to the SM-N9005 firmware so I just followed the instructions. The flash failed in ODIN, phone wouldn't boot, and I was stuck in this mess of trying to learn about all these different ways of flashing with no idea what my version numbers were as I couldn't boot the phone.
After trying to flash all kinds of versions on to it (didn't really have much choice) I luckily stumbled across an old cwm backup, so I got cwm and restored that backup. Turns out it was a backup I did for my ex's phone (also Galaxy Note 3 but from Bulgaria, no idea which model, mine is from UK). I reset factory settings and that's where I am now.
If I post my version numbers here could you show me where to find the right files for Odin? I really had such a hard time trying to figure out what the hell was what with the million different firmware versions...
Model Number: SM-N9005
Android Version: 4.4.2
Baseband Version: N9005ZHUENE2
Kernel Version: 3.4.0-1955971
Build Number: KOT49H.N9005XXUGNG1
SE for Android Status: Enforcing
Security Software Version: MDF v1.0 Release 3
Edit: Been looking at firmware on sammobile and there's multiple versions of stock for N9005XXUGNG1 in all different languages, the difference is the CSC code however there isn't one for mine (mine seems to be from hong kong or something), does the CSC matter or can I download the United Kingdom N9005XXUGNG1 and flash that regardless of matchng CSC? Or can I fix my CSC? :/
Could someone move this thread to http://forum.xda-developers.com/galaxy-note-3/help please I think it would be a better place.
Sidalol said:
Oh man that's how I broke it the first time. I didn't realise I needed version numbers etc, I simply followed te "how to unroot galaxy note 3" guide on galaxynote3root. The guide looked simple enough and linked me to the SM-N9005 firmware so I just followed the instructions. The flash failed in ODIN, phone wouldn't boot, and I was stuck in this mess of trying to learn about all these different ways of flashing with no idea what my version numbers were as I couldn't boot the phone.
After trying to flash all kinds of versions on to it (didn't really have much choice) I luckily stumbled across an old cwm backup, so I got cwm and restored that backup. Turns out it was a backup I did for my ex's phone (also Galaxy Note 3 but from Bulgaria, no idea which model, mine is from UK). I reset factory settings and that's where I am now.
If I post my version numbers here could you show me where to find the right files for Odin? I really had such a hard time trying to figure out what the hell was what with the million different firmware versions...
Model Number: SM-N9005
Android Version: 4.4.2
Baseband Version: N9005ZHUENE2
Kernel Version: 3.4.0-1955971
Build Number: KOT49H.N9005XXUGNG1
SE for Android Status: Enforcing
Security Software Version: MDF v1.0 Release 3
Edit: Been looking at firmware on sammobile and there's multiple versions of stock for N9005XXUGNG1 in all different languages, the difference is the CSC code however there isn't one for mine (mine seems to be from hong kong or something), does the CSC matter or can I download the United Kingdom N9005XXUGNG1 and flash that regardless of matchng CSC? Or can I fix my CSC? :/
Click to expand...
Click to collapse
Yea, it does get a little tricky since there are so many different versions of the software for Samsungs like these that are world phones. So your Build Number suggests that it's the version for the UK firmware, yet the baseband is from the Hong Kong region. You mentioned that the Odin install failed so I wouldn't think that the baseband had been changed, suggesting that originally it was an HK phone. With most of the unlocked non-carrier specific Note 3s, you should be able to install the official firmwares from whichever region, though there might be differences in service from the modem/baseband version or apps and languages specific to that region, but these problems should be easily solveable. I think I would try this one: http://www.sammobile.com/firmwares/download/38070/N9005XXUGNG1_N9005OXAGNJ3_BTU.zip/ This is the unbranded version for the UK region.
http://www.cpkb.org/wiki/Samsung_firmware_naming_conventions#2._Region_code
http://forum.xda-developers.com/showthread.php?t=2666907
Another thing I was thinking...you obviously have a custom recovery if you restored your gf's backup and tried to install SU that way...why not just pick a custom rom which is already rooted and could contain other fun / useful mods?
es0tericcha0s said:
Yea, it does get a little tricky since there are so many different versions of the software for Samsungs like these that are world phones. So your Build Number suggests that it's the version for the UK firmware, yet the baseband is from the Hong Kong region. You mentioned that the Odin install failed so I wouldn't think that the baseband had been changed, suggesting that originally it was an HK phone. With most of the unlocked non-carrier specific Note 3s, you should be able to install the official firmwares from whichever region, though there might be differences in service from the modem/baseband version or apps and languages specific to that region, but these problems should be easily solveable. I think I would try this one: http://www.sammobile.com/firmwares/download/38070/N9005XXUGNG1_N9005OXAGNJ3_BTU.zip/ This is the unbranded version for the UK region.
http://www.cpkb.org/wiki/Samsung_firmware_naming_conventions#2._Region_code
http://forum.xda-developers.com/showthread.php?t=2666907
Another thing I was thinking...you obviously have a custom recovery if you restored your gf's backup and tried to install SU that way...why not just pick a custom rom which is already rooted and could contain other fun / useful mods?
Click to expand...
Click to collapse
Thanks so much. Do I have to download one of the CSC files from the bottom link to use at the same time in Odin? I want to reset everything back to stock first as it feels pretty screwed atm but afterwards is there any custom rom you recommend for note 3?
Sidalol said:
Thanks so much. Do I have to download one of the CSC files from the bottom link to use at the same time in Odin? I want to reset everything back to stock first as it feels pretty screwed atm but afterwards is there any custom rom you recommend for note 3?
Click to expand...
Click to collapse
No, the full firmware flash has the CSC built in, I just provided the other link for further info. As far as roms, I can't really say. I mod phones for people as part hobby / extra money and don't see the international version often enough to know the roms that well as I tend to just get the carrier specific ones to work on. Now that Lollipop is out for it, looks like there are a lot more choices which we don't have here in the US yet. Just think about what you want to focus on (battery life, mods, stability, etc) and read through the reviews to see if people are experiencing good things. I personally don't care for Touchwiz and the Samsung devices I've owned, I just jump straight to something CM based, but it's not for everyone and you might lose some functionality in some respects (some S-Pen features) and gain it in other places (ability to mod almost everything, slimmer, no bloat, etc) For my customers though, I almost always recommend something stock based as there tends to be less of a learning curve and thus less issues I have to help people navigate through.
es0tericcha0s said:
No, the full firmware flash has the CSC built in, I just provided the other link for further info. As far as roms, I can't really say. I mod phones for people as part hobby / extra money and don't see the international version often enough to know the roms that well as I tend to just get the carrier specific ones to work on. Now that Lollipop is out for it, looks like there are a lot more choices which we don't have here in the US yet. Just think about what you want to focus on (battery life, mods, stability, etc) and read through the reviews to see if people are experiencing good things. I personally don't care for Touchwiz and the Samsung devices I've owned, I just jump straight to something CM based, but it's not for everyone and you might lose some functionality in some respects (some S-Pen features) and gain it in other places (ability to mod almost everything, slimmer, no bloat, etc) For my customers though, I almost always recommend something stock based as there tends to be less of a learning curve and thus less issues I have to help people navigate through.
Click to expand...
Click to collapse
Crap, just tried to load that one...same problem I had the first time round. It gets to "system.img.ext4" then fails. My phone will stay on the downloading screen now until I reboot it then I probably can't boot
Phone shows:
UDC START
ODIN: Invalid ext4 image
Odin shows:
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Yeah I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Won't work in Kies though it'll say unsupported version.
Edit 2: Tried again with a different cable (official samsung also) and different usb port, same result. Also ran files from desktop instead of usb this time but didn't help.
Sidalol said:
Crap, just tried to load that one...same problem I had the first time round. It gets to "system.img.ext4" then fails. My phone will stay on the downloading screen now until I reboot it then I probably can't boot
Phone shows:
UDC START
ODIN: Invalid ext4 image
Odin shows:
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Edit: Yeah I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". Won't work in Kies though it'll say unsupported version.
Click to expand...
Click to collapse
That' s really odd... Maybe try the HK version then, matching the baseband version you have. Sucks that all the links are so darn slow. You might want to spring for the premium Sammobile account to expedite the process. They have a week membership for 5 pounds and should provide a significant increase in download speeds if you need to get your phone back up in a hurry.
You might try the Emergency mode in Kies to described here: http://www.samsung.com/us/support/faq/FAQ00059169/81100 to see if that helps anything.
es0tericcha0s said:
That' s really odd... Maybe try the HK version then, matching the baseband version you have. Sucks that all the links are so darn slow. You might want to spring for the premium Sammobile account to expediate the process. They have a week membership for 5 pounds and should provide a significant increase in download speeds if you need to get your phone back up in a hurry.
Click to expand...
Click to collapse
I already got the week membership 2 days ago when I was trying this the first time Downloads were going to take 6 hours each and I'd already signed up to like 5 other sites (free) which all turned out useless anyway lol. Will try the HK one now (http://www.sammobile.com/firmwares/download/29373/N9005ZHUENE3_N9005ZZHENE3_TGY.zip/) Hope it's right
Sidalol said:
I already got the week membership 2 days ago when I was trying this the first time Will try the HK one now (http://www.sammobile.com/firmwares/download/29373/N9005ZHUENE3_N9005ZZHENE3_TGY.zip/) Hope it's right
Click to expand...
Click to collapse
Won't make it any worse.
es0tericcha0s said:
Won't make it any worse.
Click to expand...
Click to collapse
Well damn it actually worked! Something is wrong through because apps are crashing and constantly spamming error boxes making it unusable...would it be some compatability thing with it being the kong kong firmware and me in uk? Don't know if it matters whether it's the hong kong one.
"Unfortunately, the process android.process.acore has stopped."
endless spam.
Edit: Ok I reset factory settings and now it works but it's in chinese. If I simply change the language to english is that it? It's the same as having everything back at stock and will work fine in uk? Or can I change to a proper uk stock?
Sidalol said:
Well damn it actually worked! Something is wrong through because apps are crashing and constantly spamming error boxes making it unusable...would it be some compatability thing with it being the kong kong firmware and me in uk? Don't know if it matters whether it's the hong kong one.
"Unfortunately, the process android.process.acore has stopped."
endless spam.
Edit: Ok I reset factory settings and now it works but it's in chinese. If I simply change the language to english is that it? It's the same as having everything back at stock and will work fine in uk? Or can I change to a proper uk stock?
Click to expand...
Click to collapse
That should be it. You have the same baseband with this version as you had so you should not notice any difference in service or the like. I WAS going to suggest the HK version first but you said you got it in the UK so thought it should work that way. Sorry!
es0tericcha0s said:
That should be it. You have the same baseband with this version as you had so you should not notice any difference in service or the like. I WAS going to suggest the HK version first but you said you got it in the UK so thought it should work that way. Sorry!
Click to expand...
Click to collapse
Thanks so much man, this was driving me mad for a few days. One final thing if you don't mind, it's offering me a samsung update to the firmware, it says it's for VoLTE support and after updating the firmware I will be unable to downgrade due to the security policy. Is it fine to update or will it interfere with things in future like using a custom rom?
Thanks again really.
Sidalol said:
Thanks so much man, this was driving me mad for a few days. One final thing if you don't mind, it's offering me a samsung update to the firmware, it says it's for VoLTE support and after updating the firmware I will be unable to downgrade due to the security policy. Is it fine to update or will it interfere with things in future like using a custom rom?
Thanks again really.
Click to expand...
Click to collapse
My pleasure. I know how frustrating these things can be and I have a crazy amount of experience with this kind of stuff. You shouldn't have an issue with the update or doing custom things afterwards as the bootloader on that model is not locked, so you would still be able to install a custom recovery and custom rom, if you would like. If it's the 5.0 update, then you might have trouble using KK roms and you definitely can't go back to official 4.4.4 at that point, but it's probably just a minor update for the modem and not the full 5.0 update yet.