Hello guys, so yesterday i have managed to make my Device Status to Official by flashing I9500-OFFICIAL-STATUS-MOD.tar through Odin v3.04
I did a factory reset, restored my backups through titanium rebooted 2-3 times to confirm everything and everything was perfect. But this morning when i powered on my device it said custom again. what happened? what did i do wrong?
andys93 said:
Hello guys, so yesterday i have managed to make my Device Status to Official by flashing I9500-OFFICIAL-STATUS-MOD.tar through Odin v3.04
I did a factory reset, restored my backups through titanium rebooted 2-3 times to confirm everything and everything was perfect. But this morning when i powered on my device it said custom again. what happened? what did i do wrong?
Click to expand...
Click to collapse
If u have used titanium backup then u have rooted phone if it's rooted it has to be custom only
If u want all Official u must have every thing stock
.
to be honest, that status thing is a joke.....i'm on totally stock rom, never rooted, never unlocked or flashed any custom rom, the only thing i've done is put a memory card in it (a samsung branded one at that) and it keeps changing to "custom". madness.
Related
Alright, I have a Virgin Mobile S4. I rooted it a year ago with towelroot and installed clockwork mod on it to install cyanogenmod. I tried it, didn't like it so I restored my backup of the stock rom using CWM.
Fast forward to now. I tried to update my S4 OTA for Lollipop, but it would give me an error. I figured it was because I had changed the recovery software. So I went and downloaded the virgin mobile lollipop stock rom from sammobile. ( I337MVLUGOC4_I337MOYAGOC4_VMC ).
I tried to flash it onto my S4 using Odin 3.09. To no avail, it always failed at the system4.img.ext or something. From there I tried to make it work by using 3.10. Still failed. I googled for a fix or workaround and found something about reinstalling clockwork mod. I also tried reinstalling the PIT file for I337M. It was still not working. So I tried to flash back to my stock backup.
1st time I flashed, I kept having program that didn't want to start errors. I wiped dalvik, I wiped cache, I factory reset. Still bugged. So as a last resort I restored the backup again after having done all this. It worked! But...
Well, I'm at a lost now, I can't update using OTA, I can't update with Odin, I can't update with Kies. Now what? Is there a way to go back to the stock recovery and let the OTA or Kies update go through unhindered?
BTW, I had a problem when trying to use EFS professional to backup my EFS before the procedure. No matter which port I used ( front port or back motherboard port ), I could never make the backup, it said something about the phone currently being offline or something.
Anyway, I'd prefer to be able to switch back to the stock recovery and let the OTA or Kies do its thing. Any clues?
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
See first post edit^^
Diabo|ik said:
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
Click to expand...
Click to collapse
Did you check the APN settings? Make sure you have the right one for your carrier.
Hi All,
I was on some Lollipop rom for a few weeks and decided to try something new so downloaded one jackaway rom l2 and did the usual backup, factory reset and flashed the rom. All good but after say 30mins i decided to go back and restore my previous rom. Went to recover did a cleanup to install new rom and then started restoring the backup previously made however after sometime in the restore process the screen dimmed and then just blacked out without any warning.
Now my phone does boot up into recovery after removing the battery and putting it back again but any thing like flashing a new rom or restoring causes it sometimes suddenly blackout or goes through the screen dimming and blackout.
I have never experienced this before so can someone pls advise if they know as to whats happening and if Odin flashing is the only way left for me. Thanks
Forgot to mention, mine is a N9005.
bump.
Can someone help me pull the cwm backup from internal memory using adb. Thanks
What recovery are you using?
Sent from my SM-N9005 using Tapatalk
Good morning,
I'm stuck with a big problem on my Note 3 HLTE.
Here's the story : I was previously on the PAC Rom 5.1 and I wanted to change to get the CM13.0 that was just released. So I've performed the full wipe (dalvik, cache and factory reset) and then when I wanted to update the OS, it didn't work. I ended up with a phone in recovery, telling me that there was no OS installed on it.
after several attempts, I then tried to revert back to a stock ROM based on 4.4.2 with Odin. The installation went on without any problems, I was able to get through the first install with my Gmail account and then the phone rebooted, and that's where I got the bootloop curse.
what I did then, was to redo an install via Odin with my carrier stock rom, and I got a FAIL message. So, I retried an install with Odin by adding a PIT file and another ROM still based on 4.4.2. the install worked, as I was able to set up my Gmail account and so on. At this stage, I wasn't able able to get any signal for calls, 4G . In parameters, the baseband was identified as "Unknown". Then, the phone rebooted again, and I got the bootloop curse again...
My last attempt has been to install my carrier stock ROM after performing a full wipe, with ODIN. The install was successful and I got the phone rebooted to stuck on bootloop.
So, here's where I am, and I would like to solve this problem, please. What I think is that, due to the fact that I was on Lollipop, the bootloop might be due to the downgrade attempt to KK. So if there's any way to solve this problem, I'm eager to take it.
Thank you !
Hey Guys,
I've been able to resolve my bootloop problem.
I've installed TWRP with Odin, made a full wipe including data (I've saved them before), and I installed the CM12.1 by Temasek, and way to go, the phone is running fine ^^
Now, I'm just stuck with the lost IMEI thing and baseband. SO my question now is : if I want to install my operator stock ROM for getting back, should I just choose the Lollipop ROM, or can I take the KK one without getting stuck in bootloop again ?
Thank you !
Hey guys,
First of all sorry for my not perfect english
Well pre story: my mom and me using both Note 4 but my one has WiFi issues since day 1 and she told me today to change the phones bcuz she dont care if 1mb/s or 5.
So I did something i never done before -.- rooted her Phone, installed twrp and made a full backup via twrp(ticked everything active) so.. moved the backup file into my SD and restored on my Phone.
Everything went good but i recognized a lot of lag after first Boot AND WiFi dont remember the saved Networks. Turning WiFi off happens instantly but turning back on Takes around half to a whole Minute.
What i tried so far:
- factory reset via twrp
- factory reset via Standard cwm
- flashed Modem and bootloader with odin (cok1)
- reverted back to kitkat
- flashed clean 5.1.1 cok1 with odin
Tried something with .pit file while installing but didnt recognize any difference..
So.. May the restore file destroyed some specific partitions? I havent got any clue What to do next :/
Any help or advise ?
Maybe i shouldnt restore efs to my moms N910F?
Nvm solved after i restored my luckily made efs backup
I side loaded the N OTA on my 100% stock 6p. All went well and it booted fine, everything was good for over 24 hours, until i rebooted for the simple curiosity of how much faster the boot time might be. Well, after that boot, my phone wont read a sim card, the imei and baseband are unknown and all cell service is gone. I did a factory restore with no luck and have fully flashed back to stock MM twice now and the problem remains. Some googling points to a corrupted EFS partition. Any methods to getting this fixed on a 6p?
Thanks
Jaa-Yoo said:
I side loaded the N OTA on my 100% stock 6p. All went well and it booted fine, everything was good for over 24 hours, until i rebooted for the simple curiosity of how much faster the boot time might be. Well, after that boot, my phone wont read a sim card, the imei and baseband are unknown and all cell service is gone. I did a factory restore with no luck and have fully flashed back to stock MM twice now and the problem remains. Some googling points to a corrupted EFS partition. Any methods to getting this fixed on a 6p?
Thanks
Click to expand...
Click to collapse
Do you have a backup of your EFS partition?
Nope, didnt have a backup of anything, was running 100% stock. No root, no custom anything.
Funny how i rooted and ran custom recovery and firmware on all my other devices, but when i get my first nexus, i run 100% stock.
Jaa-Yoo said:
Nope, didnt have a backup of anything, was running 100% stock. No root, no custom anything.
Funny how i rooted and ran custom recovery and firmware on all my other devices, but when i get my first nexus, i run 100% stock.
Click to expand...
Click to collapse
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.