Hello so I flashed a rom and it decided to put me in a bootloop after trying everything couldnt fix it and i really didnt want to lose a chance of getting my pictures back etc so i made a backup even though i had a bootloop so i then restored and flashed rom again and was fresh again, Then tried restoring to the backup and went to a bootloop again which i expected is there any way to get my files back really need the pictures sentimental value..
Im sorry if whatever i said or did is not smart I checked everywhere but couldnt find a direct solution so wanted to try here. Thanks in advance!
if you changed bootloader & Modem then try stock bootloader & Modem.
Related
So... After trying to flash a different modem believing it would get me better signal on a custom ROM, I got stuck in a bootloop. I restored my EFS backup as suggested, but that did nothing. Now my phone will not get past the dancing Google circles, and nor will it get recognized by my computer. How, at the very least, would I go about getting my computer to recognize it so I can put the proper files on my phone needed to fix it? I have some really important files on there, so a hard reset is not an option
Nevermind restored to stock
Hey guys. I know for sure there is another thread about a similar problem but the biggest problem I'm having is figuring out what to do next, or better yet, what did I even mess up?
I made a thread a couple days ago here asking about the LTE option on my phone and how there was none. It's an Intl' phone and therefore I guess doesn't work on Canadian LTE networks.
Before we start, I'm using TWRP 2.7.0.0 . My phone is the UAE version of the D802, which is the D80220C. My current custom rom is Liquidsmooth MS3.2 .
So I found a list of modems and flashed the one for Bell. It was for the D803, but the thread I was looking at said it was cross-compatible so I assumed that meant it's okay for me to flash it on my phone.
Even so, I backed up my EFS partitions just to be 100% sure. I even used the .zip file that automatically backs up the current modem files. So I thought there was definitely a way out if it didn't work.
I will give you the full story of what was done and maybe I can get some guidance on maybe something I did wrong.
1) I flashed the D803 Bell modem.
2) Reboot to system, LS3.2 hangs on start up. Tried a hard restart to see if it wasn't a fluke. Nothing. Still hanging.
3) Figured the EFS files were toast, so I ran the restore .zip for my EFS. Reboot, and still hanging.
4) Said WTF? and restored my first stable rooted stock rom. It booted into the rom fine, but when it got to the lock screen I saw the "Service Disabled" and the phone quickly crashed.
5) Didn't even attempt to restart on that rom. So I tried a couple terminal commands to copy the modems1.img and modemst2.img files to corresponding partitions. Copied both just fine, but no change. Still screwing up.
So, this is where I am so far. I am in the process of downloading the D80220C UAE .kdz file so I can try to flash that one first. If that doesn't work, I'm really at a loss.
When I read into this some more, all I see is people who have totally wiped their EFS files and having to spend a whole bunch of time using a bunch of different programs to get in an recover the IMEI number.
What do you guys think?
Some good news right off the bat. I found a KK baseband for D802 and flashed it. So now I was able to restore my LS3.2 rom and boot into it fine. I see my IMEI and MAC address and can get WiFi at last!
Mods, you can delete this thread if you wish.
i have searched for several hours now about 12 for a fix and this makes no sense to me so i'm thinking this thread may help or just piss people off idk how forums work any way
after installing this lollipop ROM(link) everything was working perfect very smooth very few bugs almost perfect. i flashed back to unrooted stock after this and now i do not have an imei or a network but i can use my data..... i have tryed the following fixes
1. turn it off and then back on again.....
2. re flash the stock rom with odin
3. use efs professional backup then restore with adb
if i go back to the lollipop rom that i tested i have back the network but my wifi will not work on this rom -.- very confused about what is going on and do not want to risk re flashing the radio if that will brick it
any ideas?
Hello everyone.
N910W running stock Samsung firmware, 5.1.1 Lollipop.
I had my phone rooted a few months back and decided I wanted to try a Marshmallow rom. I created a backup of my pre-rooted device a few days prior, so I wasnt worried.
The rom I flashed for some reason would not allow me to use my carriers network, but only other networks. So i restored my unrooted backup.
Now whenever I try to root my phone, I get a bootloop. Every method I've tried so far (TWRP flash and ODIN, pretty much) has produced similar results. I could find the original samsung firmware for the device and flash it over and start from scratch, but I don't want to lose my data if I don't have to.
Halp. Send halp.
thanks guys.
P.s. i tried using the search, but this is either a unique problem or the search bar sucks.
Hi all, as the title says, my efs folder is inaccessible. Firstly let me explain. I bought a phone, it had the Paul pizz rom in it and I didn't like it. So I flashed the resurrection remix rom. It didn't have all the bells n whistles I wanted, so I tried the official res remix rom. Somehow I ended up with an efs problem. I ended up with an efs invalid argument error and from what I read, I did the whole adb efs fix. The error was gone. I ended up flashing a repair firmware back to bog5 and started from scratch. I worked my way back up to installing the modest rom and it works 99% flawlessly and I am happy enough to keep it. Here is the catch, I used kingo root and have ended up with a bad keyboard lag that's driving me nuts. It is unknown to me if the kingoroot caused the efs corruption or if it was just a bad flash going from one rom to another. I have tried several root browsers, made sure they all had root privileges, and no matter what, I can NOT get access to what's hidden in my efs folder. They always say it's empty. Now, here is the kicker, I got another note 4 for my son. Downgraded from 6.01 to 5.01 bog5, then up to 5.11 and flashed the modest rom on his. Instantly his phone has access to the efs folder. My note 4 works, can make calls, text etc. Imei is shown in settings, all info shows in settings as normal except one thing, on my phone it says configuration version not available whereas on my sons phone it gives a configuration version. I just can't figure out how to gain access to the efs folder to try to fix this extremely annoying lag. I DID make a complete backup of my system from when it had the Paul pizz rom, so the efs partitions should be intact there but I don't know if that would help or even where to start. Can someone please help?
Well, I just fixed my phone and thought I would share what happened. It seems that the guy that loaded the paulpizz rom on the phone before I bought it used a different version of twrp. He used a version for n910f, whereas when I began my rom search, I used one for a n910v because thats what the phone is. I was having a hard time with it so I reverted to stock, rooted, installed verizon twrp, and bam! No efs access. The difference in recovery programs is what screwed me up in the first place. I figured it out when I tried to restore his rom backup I made. The efs files were not working when it restored. I remembered what version of rom it was, and tried a twrp for 910f, and voila! So, now I have all functions working as blazing speeds, can actually access the efs folder, and no more damned lag! Big thumbs up button to me!