I had rooted this phone, and yesterday, gave ti to my son. We paid it off yesterday. He went home and wanted to downgrade, because he had read that the home button issue we were having was related to an update. I am actually not sure whether the phone was running 4.4.2 or 4.4.3, as of the time I rooted the phone. It's been months.
The phone is now in a state of being write protected from any attempt made to flash it using Odin. The message, with a Yellow Triangle, on the phone was "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." In the upper left corner of the screen was a message of several lines in length, the last two lines are greyed:
"WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled"
Today, after school, we tried to flash it using Odin again. He has found basically the same information I have, but he understands it better than I do. I fear I do not grok the vernacular very well (recovery, rom, flash, PIT,... ) I am only a Linux guy.
Now the results, over and over, are "FAIL!" in red on Odin, and approximately "write failed."
We are all distraught about this. I rooted the phone because an application I needed required it to be rooted, and never felt comfortable with the process. Pleased it worked. My son had no idea of all this, but has gallantly trudged onward as he ploughs through the various web sites offering soliutions.
We would all be very pleased to find a way out of this. Is there hope?
Second, we don't know what kind of shops might exist that can help us out. Who can perform the procedures, for a fee. Maybe T-Mobile or Samsung?
Thank you in advance. Heck I'd even be stoked to receive some suggestions for "Android unrooting for dummies" reading.
Thank you,
Alan
Flash latest 4.4.4 NH7 in Odin, should fix you right up. Links to firmwares are in general section
You bricked your phone. Check out this link...
http://www.androidayos.com/2014/03/...-s4-m919-t-mobile-unbrick-and-recovery-guide/
Related
Hello all. I am new to this, so please bare with me and understand I am just looking for help and not a hard time. I have an ATT Note 2, which I had rooted with Cyanogenmod (I believe 10.2). It was very easy with the helpful installer that is supplied, so easy even I could do it. However, shorty after running that mod, I realized why I had the Note 2 to begin with, the S Pen! Long story short, I did what I could to get the original Touchwiz/stock rom back.
I did NOT create a back up, which was where my problem starts. Now to remedy my problem, I had to find a stock rom through this site and other means. I don't remember what rom I actually used because it was on a previous PC I was using. But, I was able to go from Cyanogenmod back to Touchwiz. Thank god! Problem gets worse. I was on vacation, and all of a sudden I recieved an OTA update. Like I said, I was on vacation, not paying attention, the update started and was in progress when I started thinking, oh ****, I wonder if there is going to be a problem. Yep, there was a problem...
After the update installed, on reboot, the phone was stuck on the "Samsung Galaxy Note II" screen. I tried recover mode, no go. I tried recovery mode multiple times, no go. DAMN! No phone on a road trip is horrific! So when it wasn't my turn to drive, I attempted to flash stock roms back onto my phone as I originally did, via Odin, and same deal. I CAN find roms that will "succeed" in Odin, and on reboot, gets stuck on the same screen.
Out of frustration, I have tired other roms, some succeed, some fail. When they succeed, all have the same result, back to the same screen I previously described. However, when they fail, they bring me the the "firmware update" screen(sorry if I can't describe that screen better, but its the screen that suggests using Kies to fix the problem and update firmware. I have searched about as much as I can handle online and in forums about how to fix this. I have tried every approach. Different roms, I have tried the Kies method (which has attempted to work), however when its completed updating on Kies the phone says "unsupported version", which leads me to believe I am stuck half way in Root and half way stock.... or something, remember, I am no pro at this.
My phone isn't damaged, although I am not sure if the happenings have stressed the internals enough to fry anything. All I know is that its frustrating and would greatly appreciate any help that could be offered. I halfway thought about that $40 service that remotes your PC and will root your phone for you, but had a moment of clarity and decided a bunk phone and virus infected laptop wouldn't make anything better.
So in ending, be gentle, but please, give me any way I can fix my phone, whether it be back to stock or rooted, either way. Thanks
Boot into recovery and factory reset.
your device is modified so no update available
Hi
I am new in this forum. I have note 2 i317m locked to rogers. I rooted it using odin and now current version is 4.1.1 and then I unlocked it.
I am trying to update software to 4.3 but it is showing a msg.... your device is modified so update is not available. Can anyone tell me how can I update it and will that updating keeps my phone unlocked or not.....
thanks
again
rangercaptain said:
Boot into recovery and factory reset.
Click to expand...
Click to collapse
again.... I can't put the phone into recovery mode... I am able to get into download mode, or the "Samsung Galaxy Note II" screen, that is it. That is why I am requesting help from the pros out there.
update locked?
meharkhera said:
Hi
I am new in this forum. I have note 2 i317m locked to rogers. I rooted it using odin and now current version is 4.1.1 and then I unlocked it.
I am trying to update software to 4.3 but it is showing a msg.... your device is modified so update is not available. Can anyone tell me how can I update it and will that updating keeps my phone unlocked or not.....
thanks
Click to expand...
Click to collapse
Thanks for replying to this post. But I can not help you with your question. I am trying to tackle the issue with my phone... Is there a way I can root ANYTHING on my phone? or back to 4.1.1 or anything?
titostats said:
Thanks for replying to this post. But I can not help you with your question. I am trying to tackle the issue with my phone... Is there a way I can root ANYTHING on my phone? or back to 4.1.1 or anything?
Click to expand...
Click to collapse
Go to galaxynote2root.com and find the 4.1.1 firmware and instructions. ....that works for me......
gud luck
---------- Post added at 08:17 PM ---------- Previous post was at 08:09 PM ----------
You can try this link to see the solution to ur problem or the site to find suitable answer
true-android.blogspot.ca/2013/11/install-vlucmk5-android-43-jb-firmware.html?m=1
Gud luck
First off stay away from 4.3 lol. Anyways to get back to take ota you need to get chainfire autoroot and run in Odin, run triangle away, full unroot in super user. Reboot.
Check status if still says modified go into recovery pwr+vol up+home button and do reset.
You should be good to go. Good luck.
Hello all! Let me start by saying that i have researched a ton and there is a lot of great information on here. The info I've read however doesn't seem to work for me.
My situation is I spilled a little bit of water on my phone (really not much), but it got inside my phone a little, which was already rooted using auto root. My power button thinks its constantly being pushed (i think). It doesn't bootloop, but as soon as i pop the battery in it turns on, and my phone was unresponsive to me clicking the power button. The rest of the phone was fully functional and i checked with Tmobile and it is still under warrenty (didn't mention the water). They told me to backup the phone which i was able to do in kies with no problem. Then they said do a factory reset, which again I did with no problem. It didn't solve my issue which i kinda knew it wouldn't, so the next step for me was to unroot my phone so i can return it. I popped it in odin, selected the original firmware and it started , then it disconnected by itself. Now the firmware upgrade screen pops up, but i am still able to get it into download mode (for me since the power button is suspect) i just have to hold the home and volume down, pop in the battery and it goes to download mode. The problem is that every time i try to hit start in Odin it gets to the part about the PIT partition and disconnects and says there is no PIT partition. Everywhere i've read says to either use a PIT partition (can't find one for the M919) or that the partition is in the m5 file, which as far as i can tell it is not (at least not it's own file). I've tried downloading the stock firmware from a multitude of different places even Sammobile with no luck and I've also tried different computers, different cables, and all the USB ports available to me.
Can anyone please tell me where to go from here please? I need to get this replaced asap!
Are you asking for a .pit file to repartition? If so, I've attached one for a 16GB SGH-M919 ONLY, dumped from my own SGH-M919 through Heimdall. Download the .zip, unzip it somewhere. In Odin, check repartition, and click PIT and select this file. Hopefully this fixes your problem, but use this at your own risk.
View attachment SGH-M919.zip
Hey everyone! So I kinda messed up when I was rooting my phone. I ended up using Kingo Android ROOT to Root my Samsung S III. Well, things didn't exactly go quite as planned (person left out a step which caused it to mess up). Through some online research I downloaded the latest Samsung update from samsung-updates. I extracted the .md5 file into Odin and followed someone else's online steps. I noticed in the videos that in both Kingo and Odin beside the name it says the model number, and it did for me the first time. Now Odin just says "Odin3 Model Name " and nothing there. It went through the process and said Pass! at the top and the (success 1/fail 0) however when I go to restart the device it just stays at the "Samsung" screen with the LED light fading in and out.
The mess up with Kingo was I didn't reset it with the cable still attached, it said it was finished so I unplugged it - I guess that's where I went wrong.
With Odin I only left "Auto Reboot" and "F. Reset Time" checked, I didn't do anything else.
Does anyone know how to fix this issue from here? I feel like I'm right on the edge of fixing the phone but not quite there.
As with many people I seriously need my phone right now, my girlfriend and I are moving from Alberta (Canada) to B.C. (also Canada) at the end of the month as well as buying a new car... I need my phone right away for everyone to be able to contact me.
If anyone has questions, I'll do my best to answer them as clearly and with as much information as possible.
Thanks!
Boot recovery and factory reset. Hopfully thatll take care of it. (It will wipe internal sd card and apps)
When I flash with Odin, I often manually restart the phone rather than using Odin. I remove the cable when I see the word "reset" appear in the status window and it hasn't caused a problem for me yet.
I'm a total newb at hacking on my device, and my device wont start. I've got a bone stock t889, never been rooted or tampered with. for the last month or so when i reboot the device, i'm greeted with something about my UUID's being messed up (please forgive my lack of proper terminology here, i can't remember exactly and thats what my memory serves) and to proceed with caution. So i click the "I'm feeling lucky button" and continue on with normal use. Things were'nt totally right, apps wouldnt work and would randomly shut off. I let the device die one night. it got stuck and wouldnt reboot - hangs on the "Samsung Note 2" screen. If i plug in the charger it hangs on the image of the drained battery (wont show the battery with a little bit of green).
Now really getting to the point ... Just for poking around's sake i gave it the 3 finger salute and brought up recovery - which worked. It however speaks of system errors. Here what i see verbatim `E:failed to mount /system (Invalid arguments)`. It also says something about `# Manual Mode #` and then some more failed to mount (same as before).
So, can someone shed some light on whats going on? I did a factory reset/cache reset if that matters. Ultimately id like to just wipe everything and a newer os on it like 5.0.
So my second question is, with my device in this jacked up state, can/how would i go about flashing everything?
Like i said, im new to all this and have googled around on lunch breaks and have come across all kinds of stuff on rooting the device / copying files to it first then going into recovery ... / using odin to just do it / < enter x amount of articels on the subject >. I'm not totally sure where which way to turn.
Thanks for any help!
i would say try to odin it back to stock 4.3 with the factory image available on sammobile.com. read up before you do it though. theres plenty of walkthroughs for it
thanks, but im still on 4.3. i've done nothing to the device. i'm gathering intel before doing something.
initial post was long winded, togonna boil it down:
- can i recover from an error such as "E:failed to load /system (invalid arguments)" ?
- can i recover my device if and only if its booting only into recovery.
i know its a possibility, but i dont want to permabrick this thing if i can help it.
thats why you odin it back to stock. it'll put it or should put it back to the way it was when you took it out the box
tmobile hasn't released 4.4.2 for our note 2's yet let alone 5.0, which is why i said 4.3
sounds to me like a hardware issue which odin won't fix but worth A shot to get it working.
other then that i don't know what to tell ya.
ok understood re the versions.
im on a mac, so i dont have odin. i tried jodin3/heimdal, but given the state of my device i can't connect to it. adb wont detect. however, if i putthe device into "apply update from adb" or "apply update from external storage" i can get adb to _see_ the device.
idk, so far no good.
@overdrive, what makes you think this is a hardware issue?
based on original post. system sounds borked to me. almost sounds like internal storage space could be having problems reading. i could be wrong though
you don't have access to a pc? borrow a neighbors long enuff to run odin, put your device in download mode and connect it. let odin find it and load the md5 file and start it. see if it has any problems when restoreing system partition. it'll tell you. if it works fine then your device is fine and will boot right up when it's done.
So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.