I'm looking for a download of an older ROM. I want to try the RDLV root method but I want my original (or close to it) ROM ready in case of problems. Sammobile seems to only have MJ7 or thereabouts. Unless there's an older ROM link I am missing?
I am currently on MI7 and in download mode it's a TGY (Hong Kong) CSC. Ideally I'd like Australian or UK CSC and MI7 or less ROM.
Then I can try the root method and if I have a problem I am not reduced to using a ROM that will prevent me from trying again unless I want to break Knox.
As a side issue, when going into DL mode, I get the android bot, then a smaller one, on its back with a red exclamation above the open chest. Is that a usual picture or is it indicating something wrong?
NVM on the older ROM issue - I was looking at a post by brangalm re rooting and s/he mentioned entering the CSC in the search box. (I had tried puting in SM-N9005. I also found an older XSA version.
But I am still curious as to the sick android/exclamation mark in Download.
it's normal, it's recovery mode after all, normally used to upload firmware when things go belly up, wipe cache when it doesn't work right etc.
I'm not even sure it was intended for user access, more likely service centers.
Well things went belly up and that mode isn't there anymore. All I get now is the error screen - phone -- yellow exclamation -- PC picture. And Odin will not go past a system.img.ext4 error.
Related
OK, clearly I missed something when I did all my reading. I've got an SM-N9005, LTE, 32GB.
I downloaded an XSA ROM from Sammobile, N9005XXUBMI7_N9005XSABMI1_XSA.zip then unpacked it and ran Odin to flash it. My plan was to have an AU ROM before I tried RDLV root process.
Instead I got an Odin error on system.img.ext4 followed by the error screen. (phone - yellow exclamation - PC. The list there says:
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox Kernal: 0x0
Knox Warranty Void: 0x0
Qualcomm Secure Boot: Enable
RP SWREV:S1, T1, R1, A1, P1
Write Protection: Enable
Nothing I have been able to do since then has helped. Even tried DL'ing Heimdall but it uses tar.gz packages and I don't have one. I downloaded Kies3 and it tells me my phone is not supported by v3. Clicking Confirm doesn't help nor does the 'Checking' link. The other Kies give a connection error and the Troubleshoot Connection option doesn't help.
The only thing I can think I might have got wrong is trying to install an Aussie package over a TGY (Hong Kong) system, but there are plenty of comments saying that is OK.
I found a PIT file that is supposed to be OK, (CSB_signed_HLTE_EUR_OPEN_32G_0718) but I am not sure a pit is the answer, and if that was the cause, I think I'd need a PIT to match my ROM... right?
By preference I'd like to keep under the level where I trip Knox, but if I have to use a Recovery or CF-Root to get my phone working I'll do it.
Any advice please? Also, any ideas on what went wrong?
With some difficulty in downloading (I have a PC problem where it just seizes up for no traceable reason - going back to shop as soon as I can get it to Melb) with it taking 4 times to DL, and after some dismay that XDA'ers hadn't responded to my problem (how dare you lot sleep when my phone isn't working! :laugh I tried the Hong Kong version this morning and it ran beautifully. :victory: Not only that, my phone set up is intact.
So, what did I just learn?
Was it that, on an unrooted phone you cannot flash a stock from a different country?
Is it that HK ROM's are just different?
Or was it that some ROM's, even from Sammobile, don't run?
I am fairly sure it wasn't just a corrupt DL; IIRC Odin checks the MD5 number before flashing - pretty sure I saw that in a thread while I was trying to work out what had gone wrong. And my PC problem didn't happen when I was DL'ing the XSA version.
On a brighter note, I have my RDLV setup mostly ready to go. RDLV was going to be the next thing I tried to fix the problem so I have CYGWIN and the files all set up. Better not tell the missus I am about to do it - she's already upset enough with me for bricking my brand new phone. :laugh:
I'd like some advice if you don't mind. In the future I may have to unroot my phone, either for warranty purposes or to sell it. I'd like to be able to put the XSA stock version on it at that point. I'm presuming I could run it over a rooted phone (& lose root) to produce an Aussie phone? But was it reasonable to expect the XSA version to run on my phone while it was not rooted?
Journyman16 said:
With some difficulty in downloading (I have a PC problem where it just seizes up for no traceable reason - going back to shop as soon as I can get it to Melb) with it taking 4 times to DL, and after some dismay that XDA'ers hadn't responded to my problem (how dare you lot sleep when my phone isn't working! :laugh I tried the Hong Kong version this morning and it ran beautifully. :victory: Not only that, my phone set up is intact.
So, what did I just learn?
Was it that, on an unrooted phone you cannot flash a stock from a different country?
Is it that HK ROM's are just different?
Or was it that some ROM's, even from Sammobile, don't run?
I am fairly sure it wasn't just a corrupt DL; IIRC Odin checks the MD5 number before flashing - pretty sure I saw that in a thread while I was trying to work out what had gone wrong. And my PC problem didn't happen when I was DL'ing the XSA version.
On a brighter note, I have my RDLV setup mostly ready to go. RDLV was going to be the next thing I tried to fix the problem so I have CYGWIN and the files all set up. Better not tell the missus I am about to do it - she's already upset enough with me for bricking my brand new phone. :laugh:
I'd like some advice if you don't mind. In the future I may have to unroot my phone, either for warranty purposes or to sell it. I'd like to be able to put the XSA stock version on it at that point. I'm presuming I could run it over a rooted phone (& lose root) to produce an Aussie phone? But was it reasonable to expect the XSA version to run on my phone while it was not rooted?
Click to expand...
Click to collapse
1st step, exit Kies... It will stuff up an ODIN flash...
2nd, what was the original rom on the HK phone? If it's MJ3 or above it had the new bootloader on it that won't allow you to go back to an earlier version...
ultramag69 said:
1st step, exit Kies... It will stuff up an ODIN flash...
2nd, what was the original rom on the HK phone? If it's MJ3 or above it had the new bootloader on it that won't allow you to go back to an earlier version...
Click to expand...
Click to collapse
I may have written it wrong but I wasn't running Kies and Odin at the same time; they were alternative ways to try to get things going.
MI7 was the original and also the one I used to finally get things working again. Then I figured I'd try the RDLV process but still had issues with files - I posted all that on the RDLV thread.
Currently I am all working but unrooted, Knox = )x) and I am waiting for an updated HK version to DL.
I eventually got root on my Note. Had to DL the same country version of an update (MK1) and run RDLV process on that, then it all worked flawlessly. I'm still puzzled as to why I couldn't do the equivalent on an Aussie ROM version and use that. Only thing I can think of is the partition size is different for Hong Kong versions so it give the errors as you try to flash a different version.
Annoying but it doesn't appear to have happened to others - maybe they are content to use ROMs from the country their CSC is set to?
I rooted my phone two weeks ago with towelroot and disabled Knox with supersu.Note: my device status said official I'm still running stock firmware. Have to send my phone back for warranty problem so I unrooted with supersu and reset my phone. So now when I look at my device status it says custom (never flashed any roms or nothing) so I factory reset and notice unlock padlock and custom on my reboot startup screen. I also put phone in Odin mode the binary still said Samsung official but now the other say custom. And Knox says 0×0. I was told to use Odin so I installed odin3v3.09, drivers, stock firmware on the PC tried to flash it but got a Auth: Fail in the left lower box.
My replacement phone will be here today and will send the old back Monday to give me a couple more days to figure this out. What did I do wrong?
PLEASE HELP!
UPDATE
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Try going to the sammobile website (cant post link because I'm a new member). It should be there
Sent from my SM-G900F using XDA Premium 4 mobile app
tmadekush said:
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Click to expand...
Click to collapse
Your warranty should be honoured because it still shows Knox 0x0. But it would be prudent to resolve the custom message as you are trying to do. It's showing custom because you disabled Knox. Flashing a full stock firmware should restore Knox and resolve the custom message.
Odin flashes can fail for many reasons e.g. trying to flash non-Odin versions of firmware, bad signatures, poor quality USB cables, wrong firmware version e.g. one meant for a different phone, et cetera.
Back up your files, then do a full system reset from the settings menu. Then put your phone into download mode and use Odin to flash a full stock firmware. Ideally use the latest firmware version for carrier that the phone originally came from (i.e. it should match the baseband). Google will find many firmware repositories e.g. sammobile, samsung-updates and this site.
.
I wanted to root my Galaxy Note 4 (SM-N910F UK carrier H3G) so I could use the mirroring option in Airdroid.
Long story short, I'm severely disabled so wanted full access to my phone whilst on my pc, without struggling to get my phone all the time. (SWTOR Security Key is one of the many reasons for wanting to not have to grab my phone every time I need to do something on it)
(I can't put phone where it's easily accessible whilst on pc, because of the board I use for keyboard and mouse rested across the arms of my chair)
I THOUGHT I had it sussed, as I had successfully rooted and booted my S3, S4 and Note 2, 3 and 8.0 devices.
However, I didn't read the fine print when using CF-autoroot in that it doesn't work on 5.1.1 atm. Or something along those lines...
Anyway, with my usual eagerness and impatience to do geeky/nerdy deeds, I ended up with my phone in a constant boot loop no matter what I tried.
I scoured the Internet for 3 hours, trying to find the original stock rom for my device and was livid that my usual Google-Fu was failing miserably.
I found one, so I thought, installed the kernel, (couldn't find stock kernel either) installed SuperSU, installed Twprs or whatever it is, (excuse my lack of knowledge please) then installed this "stock" rom.
Turns out it possibly IS the H3G network's Stock Note 4 (SM-N910F) ROM. IF I lived in Italy.
I still would like root access on my phone, but I would like to try and get stock rom back, or something EXCEPTIONALLY similar.
Please, again, excuse my apparent thickness... (and I'm not talking sliced bread here) is it the kernel where rooting takes place, the ROM, or do both have to be involved in the adaptation?
I know very very little about Linux and kernels etc.
I hope that I have described my predicament clearly, and that when one has picked oneself up off the floor from rolling around with much merriment, one (anyone) is able to assist with my screw up.
Best wishes,
(Applebogies for waffling on more than the meat content of a Belgian Blue, (I'm not talking Blue Waffle, but of four legged animals that chew the cud)
(Applebogies also for mentioning The Waffle of Blue-ness in more than one sense of the word, if it makes you Google it and you only just ate and you've never seen it before)
(Finally, applebogies for my rotten and feeble attempts humour, please try to cut through my crap and get to the point ofwhat my conundrum actually is)
So basically in a nutshell, you've bricked your phone? I do know that when I flashed stock ROM the other day, I had to pull the battery, boot into recovery (vol up + home + power) and wipe data/factory reset and wipe cache too. Then it booted just fine try that.
you can find different stock roms for your phone at sammobile (google it) download the firmware from there and flash it with odin. Watch youtube videos on how to flash firmware with odin. its simple
See if you can boot the phone into Download Mode via volume up+home+power. If it boots into download mode that means its not hard bricked. If it doesnt boot into DL the first time you try, do a battery pull for 15-20 seconds, then try again. If that doesnt work, then check your specific device versions forum for an unbrick method, and check for a general unbrick that can be used for all N4's.
If it does boot into download mode, download the stock firmware for your specific N4, flash it via Odin, (instructions are generally included in the thread where you find the stock ROM download) and you should be good to go after that.
Edit: SamMobile does indeed have a firmware for your specific device. Do a google search for sammobile, go to that site, and input SM-N910F into the device search bar. That will take you to a page with a list of firmwares. Theres a list box where you can select your country, that includes country and carrier combinations. Yours will be listed as United Kingdom (H3G)(H3G). Select firmware with PDA version N910FXXU1COJ3.
Not sure why you all think my phone is bricked, I am on it now?
I am however, currently running the Italian version of 3 mobile rom. Looks like asrah has solved that problem though xD
To shorten my previous post:
Where does root happen, on kernel or rom?
Ie - can I have stock rom but still have root access on my phone?
Thank you to asrah for finding my rom.
Thanks all and a very Merry Christmas!
Hello everyone, I'd like to start off by saying I am a complete newcomer to all this so please explain literally all of the terminology/jargon you intend to use and correct me when I use it wrong.
I have a Chinese version of the Samsung Galaxy Note 4 SM-N9109W and up until yesterday it was running out of the box on android 4.4.4. I care not for any of the data on the phone nor the warranty as there was none to begin with when it was gifted to me.
I attempted to "root" it as I didn't want any of the Chinese apps/restrictions on it but have failed miserably and now my phone is stuck in a bootloop.
I was following this guide if it helps: http://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948 and downloaded the appropriate Snapdragon version (SM-N9109W).
I cannot enter recovery mode by holding down *power+vol up+home* as it just keeps on rebooting. I can, however, get into the downloader by holding down *power+vol down+home*.
I have tried for the entirety of today to find a specific guide for the Chinese note 4 on xda, youtube and google but to no avail - nothing that I can find is identical to my situation and I am hesitant to do anything further to it by following a similar guide in case I make it worse.
I have repeatedly seen suggestions to "flash" stock rom and as I can get into the downloader I believe this would be a great starting point, but once again I am afraid to do anything without a specific guide for the N9109W.
A few people have referred to SamMobile to download stock rom, but a search for SM-N9109W lists 8 files for 4.4.4 and I believe I have no way of working out my PDA or CSC, yet again I don't know what these even are and they might not be relevant?
Any assistance in getting my phone's software back to "out of the box" conditions would be GREATLY appreciated.
Thank you for your time and patience,
Ryan
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
ithehappy said:
If you can enter Download mode then you can flash that firmware you found matching your device's exact model no. via Odin. Just put the ROM in AP/PDA tab (PDA for older Odin versions, AP for new) and hit start.
Click to expand...
Click to collapse
Thank you ithehappy for the reply,
When I search for the stock firmware on SamMobile, I type in my exact model number (SM-N9109W). This search returns with a list of multiple different versions for my phone, of which 8 are 4.4.4 (my initial version).
Does it matter which version I download and install?
To my knowledge, I have no way of finding my CSC or PDA unless you know of a database I can use to search the information that is physically on my phone? Once again, does it matter that I know what these are or can I simply download, for example, version 5.1.1 and flash that on instead of my original 4.4.4? Or, will this just cause further possibly unfixable problems?
Thank you for your help
Anyone?
No, you can download any one you want.
Thank you for the help, ithehappy. I now have a working phone!
For future readers, I downloaded the latest version of 4.4.4 that SamMobile had (2015-03-27) for my model (SM-N9109W):
PDA: N9109WKEU1ANL3
CSC: N9109WCTC1ANL3
It failed the first time I tried flashing with Odin 3.10.7, but whilst I was hastily taking screenshots of my problem to post here I accidentally started the transfer again and it successfully installed that time.
I followed the instructions on SamMobile for the installation.
This version of the firmware I installed does not have any google services (thank China for that), so keep that in mind.
Thank you
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.