Hi, I have pretty annoying problem. The current details of my device is like this:
Product Name: GTI9300
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
As good as it has to be, right?
But as I see recently, sometimes the last line changes itself as "System Status: Custom" although I'm doing nothing. After that, when I turn on the device, in the settings menu it says "Device Status: Modified", so it prevents me to make update too. But in another day, when I turn on it, it can say "Device Status: Normal"
To be honest, I'm really so close to get mad about this issue. It's like my device is kidding with me and I want to fix this problem as soon as possible. So that's why as a last hope, I'm telling this problem here. Please help!
Thanks in advance
You must be doing something for that to change, not flashing any custom ROMs?? Kernels?? Modems?? It doesn't just change for no reason dude.
Sent from my GT-I9300 using xda premium
speedyjay said:
You must be doing something for that to change, not flashing any custom ROMs?? Kernels?? Modems?? It doesn't just change for no reason dude.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
No really, I don't know how to flash kernel or modem. I just flashed an official stock rom by odin and also that's why my counter is still 0. After flashing I made both resets on recovery mode and that's all I'm from Austria bought the phone from Austria and it was an Austria stock rom 4.0.4 i've installed. After reset, it did an automatic update to 4.1.1 and here we are
Its really strange....not saying I don't believe you, its just odd. It only usually says "modified" or "custom binary" if some sort of modification has been made to the device but as you're running stock 4.0.4 with 0 on your flash counter, I honestly don't know buddy.
Sent from my GT-I9300 using xda premium
Boot to download mode then vol up and check custom rom count .
jje
speedyjay said:
Its really strange....not saying I don't believe you, its just odd. It only usually says "modified" or "custom binary" if some sort of modification has been made to the device but as you're running stock 4.0.4 with 0 on your flash counter, I honestly don't know buddy.
Click to expand...
Click to collapse
That's right, its really odd and annoying too. But anyway thanks for your interest.
JJEgan said:
Boot to download mode then vol up and check custom rom count.
Click to expand...
Click to collapse
Just as I said, the counter says "Custom Binary Download: No", and "Current Binary: Samsung Official". But after restarting, "System Status" line says sometimes Custom, sometimes Official.
I've never installed a custom rom, kernel or modem but long time ago i've rooted my device with Odin + CF-Root-SGS3-v6.3.tar (it was before flashing my current stock rom and factory resetting). After rooting operation, my counter has changed to "1". After that, I used "TriangleAway v2.36" to reset my counter. It has done successfully. Counter was "0", binary and status lines were "Official". As a final step, I flashed my current official stock rom and made a factory reset. That's all i've done to my device since i've bought it.
I was just wondering if you had a different setting in the rom counter when setting change to modified ..
Obvious that judged by info on the last post that the reinstall of stock rom and factory reset has not cleared the status .
The post that says something like Samsung have modified custom rom counter may have more information .
jje
Sry I misunderstood. No, I didn't do any different setting in the system or counter. Since my last stock rom flasing and factory resetting I'm using the device just as other regular users (messaging, calling, using non-"root required" apps, games etc.).
Btw currently I'm not using the same stock rom which was installed when i bought the device. It was carrier branded stock rom and I wanted to get rid of carrier's booting and turning off logos. But it was an austria stock rom and my current is an austria stock rom too. Does this information make a difference maybe?
Sorry to flood but it still keeps doing the same thing when I restart the device. 10 minutes ago "Device Status" was "Normal". I waited a little, restarted and it is now "Modified".
Please help...
Do you think, If I flash another stock rom and do a factory reset, will it fix this issue??
Sorry for you to to hear that.
I had a similar issue (as I reported in CFAutoroot thread), just the opposite
While it was rooted and had a custom recovery, showing "Modified".
After a reboot(*), it showed as "Normal"
Until the next reboot where it went back to its "Modified" state.
(*) It suddenly rebooted (after switching off wifi, switching on data). This happened only once since I bought it (thank god)
I kept the last_kmsg after this happened.
I'm happy with the Modified state, just wanted to bring my discovery too..
So there is something not working properly with this detection.
Thank you for your reply, its pretty better to know that not to be alone about this "unsteady" issue. If it stays as Custom permanently, I would do something to fix or if it stays as Official, I'll not think about it anymore. But current situation is REALLY annoying. I'm not using this device for a long while, but honestly I hate it right now.
My problem is still valid, so please feel free to share your opinions about possible solution...
Still no one? Come on, you guys are Android freaks, I don't think that there isn't anyone here who knows the solution
Well, I flashed another stock rom of another region via Odin, used it 2 days (without root), restarted the device several times to be sure, "Device Status" was "Normal" all the time. I was starting to be happy about it......
And here it is:
the damned "Device Status" started to say "Modified" again.... Just like before flashing, it is sometimes normal, sometimes modified after restarting the phone.
Cannot find the solution alone. I'm really gonna throw away this damned phone through the window.. Please give me some advices, please help
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
hi guys!
i recently flashed uk stock lfb rom over my orange stock rom, i rooted my s3 using chainfire cf-root 6.4 and i used triangle away to reset the counter.
everything went smooth, counter shows 0, but in settings/about device/status/ device status is now MODIFIED and not NORMAL as it used to be.
even if the counter is reset to 0, isn't this an obious proof for servicing companies that phone has been modified and loosin warranty? is any way to go back to normal? i searched the forum and i didn't find a solution.
thank you!
flash stock rom and your phone will show that normal status again. samsung will never know what you did to the poor phone. double check that you don't have supersu or superuser app or else something bad might happen
stfudude said:
flash stock rom and your phone will show that normal status again. samsung will never know what you did to the poor phone. double check that you don't have supersu or superuser app or else something bad might happen
Click to expand...
Click to collapse
i already tried that, but a lot of apps didn't start corect, phone became very unstable and unusable. i even couldn't check if the status went back to normal. could it be because the original version seems to be an earlier release compared to lfb release?
i flashed stock rom, ALE8 to be exact, a few days ago, after having a few problems with wanam 1.9. the status changed to normal after flashing. i use desktop odin to flash. after flashing wanam 2.0 the status changed to modified. tried triangle away, but the status still doesn't change to normal even though flash counter has been succesfully reset.
The full steps are: (in that order)
- Triangle Away
- Flash Stock ROM
- Flash correct CSC / Modem (optional, not required)
- Factory-reset the phone
Reset the flashcounter, update rom and after boot do a facory reset.
flash stock rom, wipe everything, doesn't mean that the phone back to normal. for example, i always set my line to wcdma only. after flash any rom, reset everything, that setting still wcdma only. the only way to have absolutely format, is change csc code. it's truly format back to stock. but, be warning, you will lose everything, backup 1st.
so the trick is factory reset? good to know! i will not try it btw, because i need a working phone for this 2 months. OP, is your question answered now?
I don't know yet
I have to try that first, but i can't do IT right now. I hope that after flashing my original orange rom the phone will be stabile enough to perform a factory reset.
Thank you guys for your suggestion.
noris08 said:
hi guys!
i recently flashed uk stock lfb rom over my orange stock rom, i rooted my s3 using chainfire cf-root 6.4 and i used triangle away to reset the counter.
everything went smooth, counter shows 0, but in settings/about device/status/ device status is now MODIFIED and not NORMAL as it used to be.
even if the counter is reset to 0, isn't this an obious proof for servicing companies that phone has been modified and loosin warranty? is any way to go back to normal? i searched the forum and i didn't find a solution.
thank you!
Click to expand...
Click to collapse
Hey dude. I'd just stick with it
even if you should have to send it in, they'll pretty much only look at the counter (If possible) and if that is not possible, then they'll JTAG it; meaning that EVERY tiny piece of information on that phone is gonna be wiped... Just make sure you don't send it in, just because of a small SIM failure. (Because that's caused by bad radios/basebands). Only send it in, if it's proper bricked, and they'll not no a thing (I've done this loads of times, they haven't noticed a thing to date )
yep, factory reset did the trick.
as i said, after flashing original orange rom over lfb rom the phone became unstable.
i booted into mini cwm that came original with the phone and there is an option to do a factory reset, et voila, no more modified status.
thank you guys!
No problem hit thanks button )
I have a brand new s3 from orange which has not been rooted or anything and the device status shows as modified. i have used the Samsung GS3 Int ToolKit and odin to flash an unsecure boot image so i could back up my phone which i still havent yet as i need to root and install busy box. i have not rooted the phone or changed the rom so why does it say device status modified. I did a factory reset but it still shows as modified.
I will be flashing the rom once i know how to backup the orange rom and data. I want to remove the modified status incase i want to return the phone to orange so they can give me an unbranded phone in the first place.
daflex86 said:
I have a brand new s3 from orange which has not been rooted or anything and the device status shows as modified. i have used the Samsung GS3 Int ToolKit and odin to flash an unsecure boot image so i could back up my phone which i still havent yet as i need to root and install busy box. i have not rooted the phone or changed the rom so why does it say device status modified. I did a factory reset but it still shows as modified.
I will be flashing the rom once i know how to backup the orange rom and data. I want to remove the modified status incase i want to return the phone to orange so they can give me an unbranded phone in the first place.
Click to expand...
Click to collapse
If you flashed an insecure kernel, you did modify the state of the device. Are you saying that it showed as modified out of the box?
same problem
I have never rooted my device, never intended to either. However my device status appears as modified. While I personally feel there arent many glitches in my phone (s3), I'm worried i wont be able to upgrade to jellybean when the update comes out.
Any help?
Which firmware/ROM are you using? Are you rooted?
I'm asking this cause if you bought it second-hand the previous owner could have modified it.
Sent from my Nexus 7 using Tapatalk
would having this status affect OTA updates?
Yep, it generally means the phone is running a custom rom/recovery and is rooted. OTA updates only work on non rooted stock recovery roms... However this doesn't mean you can't update through ODIN...
ultramag69 said:
Yep, it generally means the phone is running a custom rom/recovery and is rooted. OTA updates only work on non rooted stock recovery roms... However this doesn't mean you can't update through ODIN...
Click to expand...
Click to collapse
I don't think so. As long as you're on an official ROM it doesn't matter if you're rooted or not.
donalgodon said:
If you flashed an insecure kernel, you did modify the state of the device. Are you saying that it showed as modified out of the box?
Click to expand...
Click to collapse
Thanks, I realised that later on and was just about to re-edit the post. Im sure it didn't say modified when out of the box. Orange won't replace the mobile as they say all their phones are branded and the replacement would be branded anyway. Im gonna flash with unbranded software as i dont want orange bloatware. Just need to know how to back up this useless orange rom and then i can flash!
---------- Post added at 08:12 PM ---------- Previous post was at 07:59 PM ----------
Lunchbox115 said:
I don't think so. As long as you're on an official ROM it doesn't matter if you're rooted or not.
Click to expand...
Click to collapse
Yep as long as i've read you can download as long as your on official ROM. You might lose your root but you can just re-root again.
Not my first time to root and install a custom rom on other phone, but this phone isn't treating me well.
So I followed the root guides to root the phone.
Downloaded an insecure kernel for i9100. Although, oddly enough, I bought this phone 2nd hand, and when I went to the "about" part for the kernel look up before tried to root it, the kernel info just contained ICS3.?? (forgot) and the date. There was no four or five letter kernel code like I've been seeing. But according to cnet (one of many rooting tutorials), the kernel version doesn't matter as you can change the kernel anytime, or after rooting in this case.
So I installed Kies to get the Samsung drivers installed. Done.
Restarted phone to download mode (volume down, home, power)
Started Odin 3 v1.83
Phone was recognized. Click the 2 boxes (Auto reboot and F. Rest Time).
Clicked PDA, loaded up an insecure kernel.
Status went through OK, ended up with "Pass!"
Phone automatically restarted.
Now the problem. It restarts, shows the Samsung Galaxy S2 logo with the big triangle underneath it, and thats it. Never leaves this screen. I thought maybe it's a kernel problem, so I tried several different insecure kernels, all with no change. I have no idea how to find what kernel was the original one that came with this phone. Would using Odin with the original secure kernel (or even insecure) solve this problem? Otherwise, what else can I do? My note 2 was stolen so I bought this s2 second hand until I can scrape up enough money for a note 2 again, but the damn thing won't even boot up now. :crying:
How can I get this working again, even to have it stock again I'd be fine (though obviously putting on a custom room with root would be best).
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
TheATHEiST said:
Well you dont seem to mention what you have tried after flashing your kernel?
Have you tried going into download or recovery mode, do they work? If so simply flash another kernel or rom.
Also, I my be wrong but there isnt a China i9100 afaik so you may have flashed incorrect kernel so system isnt booting.
Remove battery and tell/show us what label says.
Click to expand...
Click to collapse
There wasn't much to try, at least as far as my noob self knows about. I tried flashing 6 other kernels I found, merely taking guesses at which might possibly be the Chinese s2 one, I remember from flashing other phones that i had to look for Z or D in the kernel ID. But all of them just led to the same problem of not booting past the logo screen.
Besides just trying to start it up as normal (which doesn't work) and starting it up in download (by holding down vol+home+power), what others ways can I start it up? I don't know how to boot into recovery, and I didn't know I can flash a rom without first rooting it, which I haven't done yet because it's still stuck in start-up.
Searching enough xda threads and just googling seems show a pretty large consensus supporting the existance of a China i9100, plus I see them everywhere (as well as s3, s4, and notes), so I'm 99% sure they are an official and semi-large market for them here (after iPhones unfortunately). But even still, that doesn't help me locate the original kernel.
Under the battery, is says this:
Samsung WCDMA
Model #: GT-I9100
CMIIT ID: 2011CP2751
Do these help? So is any of the steps I did wrong, or can you otherwise point me in the right direction? Appreciate the help.
Don't post your IMEI (or your SN for that matter).
MistahBungle said:
Don't post your IMEI (or your SN for that matter).
Click to expand...
Click to collapse
Thanks for the tip MistahBungle. Edited out.
Hate to say it, but found more help on youtube... Found a guide that walked me through replacing all the files (not just kernel) in Odin that got it back up and running. I'll follow the xda guides again and hopefully it'll work this time... Thanks anyways...
Hey everyone,
I have an unrooted Samsung Galaxy S3 GT-i9300 on T-Mobile (UK). I recently updated firmware 4.3 and noticed the battery drained really quickly. After a lot of researching, I found that a factory reset should fix the issue, which it did!
I have since discovered that when in recovery mode, everything seems normal (as in the menu is displayed, including the option "Wipe Cache Partition") the words "No Command" is displayed under the Android robot, with a red exclamation mark. If I choose an option, whether it's Wipe Cache Partition" or "Reboot Now" it seems to do the actions(it shows "Erasing" once "Wipe Cache Partition" has been selected and also reboots the phone) but the word "Error" is displayed under the robot when the action has been done or just before the phone reboots, after selecting "Reboot Now"
Is this normal? Why all of a sudden does it say "No Command" and "Error"?
I haven't tried to root my phone or install any custom roms or try to modify the phone in any way since I got it.
Can anyone out there please let me know why these words have started to appear in recovery mode?
I'd really appreciate it!!
P.S. I searched the forums before posting and although some were similar, they didn't cover my exact problem.
Try downloading the same official firmware and flashing with odin, there is a guide in general forum. Factory reset then try again.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try downloading the same official firmware and flashing with odin, there is a guide in general forum. Factory reset then try again.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply. I found the guide to flashing the phone with Odin and I'm a little worried in case I mess up and brick the phone, I read that if you make a mistake, that can happen.
Just to say, I checked the recovery mode again and it seems to do everything normally, such as wiping the cache(it says so in the log) but it just says "No Command" after each action. The word "Error" only appears the very first time you see the robot, and when you select "Reboot Now" just before it reboots "error" shows up under the robot and then the phone restarts.
So, do you know if this is normal? Or do you think it's something to do with the way the firmware 4.3 works?
I'd just like to know whether it's normal or if there's something wrong behind the scenes in the phones firmware.
Hope you can help and thank you again.
MasterfulNinja said:
Thank you very much for your reply. I found the guide to flashing the phone with Odin and I'm a little worried in case I mess up and brick the phone, I read that if you make a mistake, that can happen.
Just to say, I checked the recovery mode again and it seems to do everything normally, such as wiping the cache(it says so in the log) but it just says "No Command" after each action. The word "Error" only appears the very first time you see the robot, and when you select "Reboot Now" just before it reboots "error" shows up under the robot and then the phone restarts.
So, do you know if this is normal? Or do you think it's something to do with the way the firmware 4.3 works?
I'd just like to know whether it's normal or if there's something wrong behind the scenes in the phones firmware.
Hope you can help and thank you again.
Click to expand...
Click to collapse
Honestly, I'd quite like to see a pic of the errors in recovery. Meanwhile if you don't feel like using Odin (if you stick tight to the tutorials nothing bad will happen) you can try to repair with Kies, you might have installed it anyway. Here is a detailed guide http://forum.xda-developers.com/galaxy-s3/general/guide-how-to-reinstall-stock-firmware-t1978840
If this fails for any reason go ahead and try Odin using this noobproof guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081. That should almost certainly eradicate any errors.
Benko111 said:
Honestly, I'd quite like to see a pic of the errors in recovery. Meanwhile if you don't feel like using Odin (if you stick tight to the tutorials nothing bad will happen) you can try to repair with Kies, you might have installed it anyway. Here is a detailed guide http://forum.xda-developers.com/galaxy-s3/general/guide-how-to-reinstall-stock-firmware-t1978840
If this fails for any reason go ahead and try Odin using this noobproof guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081. That should almost certainly eradicate any errors.
Click to expand...
Click to collapse
Thank you so much for the links! I actually just tried the update via Kies, reinstalling the stock firmware and it took a while and I did everything it said but the messages still show in recovery mode, just like before. So I'm wondering if it's actually supposed to normal to display those words, and maybe that's just that way it is now?
I took some pics of the screen, so you can see what I'm talking about.
Here's the "No Command" message displayed. As you can see, it has wiped the cache partition after I selected it.
https://www.dropbox.com/s/irolo6rp8wh5ibf/Photo 27-04-2014 23 39 34.png
And here's the "Error" message it says just after I've selected "Reboot Now" and before the phone restarts.
https://www.dropbox.com/s/9o0yuopkf3dov76/Photo 27-04-2014 23 40 17.png
Have you seen or heard of this before?
No problem. And no, not in this context. But then again, I haven't had a stock recovery (nor a stock ROM) on my phones for years.
But I do get tons of phones in for repair every week, have not really noticed these 'errors' anywhere.
It seems to execute everything fine.
Would be interesting if you'd flash a TWRP recovery what it says then. You can easily replace it by your stock recovery again.
If everything looks good there then it probably is just the way it is.
Benko111 said:
No problem. And no, not in this context. But then again, I haven't had a stock recovery (nor a stock ROM) on my phones for years.
But I do get tons of phones in for repair every week, have not really noticed these 'errors' anywhere.
It seems to execute everything fine.
Would be interesting if you'd flash a TWRP recovery what it says then. You can easily replace it by your stock recovery again.
If everything looks good there then it probably is just the way it is.
Click to expand...
Click to collapse
That would be interesting, but doing so would require me to root my phone, right?
Oh I see, so it's a quite an unusual thing to happen . . . The fact that it says "Error", yet executes things fine anyway.
I've come to a possible conclusion that it's probably down to that particular version of the stock rom? Maybe people how have updated in the UK, using that version would experience the same? Because, after reinstalling it via Kies, and there being no change regarding those messages in recovery mode, doesn't that point to the firmware being the cause? For example, if I flashed the phone with a custom rom(that didn't have any error messages) surely, those messages wouldn't show up after I'd installed it, right?
Does what I'm saying make sense?
Sorry if I'm going on, I'm not too familiar with the technical side of Anroid systems.
MasterfulNinja said:
That would be interesting, but doing so would require me to root my phone, right?
Oh I see, so it's a quite an unusual thing to happen . . . The fact that it says "Error", yet executes things fine anyway.
I've come to a possible conclusion that it's probably down to that particular version of the stock rom? Maybe people how have updated in the UK, using that version would experience the same? Because, after reinstalling it via Kies, and there being no change regarding those messages in recovery mode, doesn't that point to the firmware being the cause? For example, if I flashed the phone with a custom rom(that didn't have any error messages) surely, those messages wouldn't show up after I'd installed it, right?
Does what I'm saying make sense?
Sorry if I'm going on, I'm not too familiar with the technical side of Anroid systems.
Click to expand...
Click to collapse
No, you don't need root for flashing TWRP via Odin. Use this great and easy guide (if the guide helped you hit the users thanks button):
http://forum.xda-developers.com/galaxy-s3/help/twrp-flashing-tar-t2680354
I'm not sure if this is really the UK-ROM or just a common thing under certain circumstances and I've just never noticed it, but I really doubt it.
If everything is fine with TWRP and also installing ROMs causes no problems I would just accept this as one of the never solved mysteries - which I rarely do normally
we have same issue i already flash custom recovery via odin stil no command when i rebooting into recovery. . did you fix it?
Hi,
I have a S3 model GT-I9305 (2GB) for like 7 months. It had 4.3 version installed, and I wanted to downgrade to 4.1.2 or 4.2.2. In the about menu Baseband version was i9305xxuemk1. Phone does not have any recovery software installed, except the default Odin download mode (Home+Down+Power), and I am able to enter it.
Since I am not sure for which country / carrier the phone is made (here people sell everything from everywhere), I do not know the original version of ROM, and there is no official ROM for my country (sammobile / Serbia). I have tried several 4.1.2 ROMs for different zones, and almost all of them failed, except for one - I9305XXALI5_I9305EVRALI5_EVR, which is reported as successful installation in Odin, but after restart it hangs on samsung logo.
Anyone has any ideas?
So, it seems that I can install any 4.3 version, but cannot install any 4.1 version. Some fail on nand, most fail on sboot. Any ideas? Basically what I do is, put the phone into download mode, and load firmware in odin and flash it.
Don't install 4.1 roms.
After you flash in odin boot into recovery and do a factory reset and and wipe cache and delvik cache then reboot
I am not sure what you mean? My goal is to install 4.1.2 version.
I have followed instructions from this link, but it doesn't work. In final step, when I need to go into recovery mode (Up+Home+power), I cannot enter it, it just hangs on samsung logo.
However, this link helped, I was able to downgrade using Odin mobile
Goran_ said:
I am not sure what you mean? My goal is to install 4.1.2 version.
I have followed instructions from this link, but it doesn't work. In final step, when I need to go into recovery mode (Up+Home+power), I cannot enter it, it just hangs on samsung logo.
However, this link helped, I was able to downgrade using Odin mobile
Click to expand...
Click to collapse
Why do you want to downgrade all the way down to a 4.1 rom.
Are you sure you are powering off then entering the combo to start it?
Because I have a major battery drain, which last from 6-10 hours, depending on usage (mostly calls 1-2h, very rarely internet). Hard reset did not help.
As I have learned, it is a known KNOX problem, that I was not aware of (I also have another S3, which does not have KNOX on it).
Goran_ said:
Because I have a major battery drain, which last from 6-10 hours, depending on usage (mostly calls 1-2h, very rarely internet). Hard reset did not help.
As I have learned, it is a known KNOX problem, that I was not aware of (I also have another S3, which does not have KNOX on it).
Click to expand...
Click to collapse
I have just read your topic title again, im sorry but i have no knowledge of knox since the i9300 does not have it, please get a mod to move this to the i9305 section where they can help you
Could you uninstall KNOX rather than going back to 4.1.2? http://www.androidpit.com/how-to-uninstall-knox