The stock ROM shows me a problem .. bootloop on the logo Samsung
Yes .. bootloop Samsung logo and never starts
Then we see a problem here... If stock ROM cannot boot, you have to be careful!
I was worried that your EFS went bad. Try do a factory reset in recovery after you flash stock rom and see it it can boot.
What I must do after?
What I must do after the flash stock ROM.. im doing g ood the steps?
You need to make sure you can boot your Stock ROM first. Did you flash the stock ROM with a valid PIT file?
I hace one file with that name
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
I have one file called q120110914 16gb.pit
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
I have one file called q120110914 16gb.pit I put Ed into pit odin.. and then start.. pass.. bug the logo of Samsung loads and returns again to Samsung logo..
Try a factory reset after you flash stock in odin. See if it boots.
I cant go into recovery
I cant go in into recovery... the androide green apears. then the screen turnos black and then .. Samsung logo again and again
Screen turns black? Impossible...
I'm not saying the recovery after you flash stock ROM, I hope you didn't confuse. Because after flash stock ROM in odin, it will go to recovery by itself for a couple of seconds. What i means is that, after it bootloop, you manually enter the recovery and do a factory reset.
Also maybe you can look up the forums on solving softbrick because your device can't boot other ROM and also the stock ROM, it's not a problem related to the ROM anymore.
I did like to ask, what is your device state before you flash my ROM?
Status
Im gonna Fix the softbrick.. I had other ROM.. Xperia ROM for n7000.. my n7000 was working fine.. I dont know what can be the problem..hope that i can install this ROM.. ID Like to use pie on my Galaxy note
It's strange that now all rom bootloops on your n7000 even for stock. What if you flash back the Xperia ROM then?
Now im on the instalation of the versión 225 of 16.0
Hello .. now im on the versión 225 of lineage pie from your folder.. I found two files... one zip... one md5zip.. I must do something with the md5 zip ?
Hello my Friends ^^.
Since my English is not so good I use DeepL.
I found out today that I had exactly the same problem. I installed Android 2.3.6 on my N7000 as a 3 part firmware and saw that my EFS is broken. I googled for a long time and was able to restore my EFS by installing the 4-part Android Ice Cream Sandwich. I could upload my EFS backup as an attachment and link it with the App KTool. With KTool you can backup or restore the EFS. My Efs is on the level of Android 4.1.2 Jelly Bean. Now I can continue experimenting without any danger
!Now I will try again to install Android Pie.
md5 is a checksum to check if your file is corrupted or not. Normally you won't need that if you felt that your download is ok.
Hello my Friends ^^.
Since my English is not so good I use DeepL.
I found out today that I had exactly the same problem. I installed Android 2.3.6 on my N7000 as a 3 part firmware and saw that my EFS is broken. I googled for a long time and was able to restore my EFS by installing the 4-part Android Ice Cream Sandwich. I could upload my EFS backup as an attachment and link it with the App KTool. With KTool you can backup or restore the EFS. My Efs is on the level of Android 4.1.2 Jelly Bean. Now I can continue experimenting without any danger
Now I will try again to install Android Pie.
That's great! I hope it works well for you.
Because there is a wait flag for /efs in fstab, so my guess is that /efs might be corrupted, preventing the device from booting. @lowe77 that's the reason I mentioned about /efs.
There is also a "reverse-engineered" (you should know what I'm trying to say) version of octoplus, that you can connect your phone directly to computer using usb (without the box) and repair the efs. I repaired one of my n7000's efs with this.
Every users are advised to backup their /efs and store it in a safe location (ie. Google Drive). If your /efs is broken, immediately flash back to stock ROM first if you do not have a efs backup.
Nice
I have now efs.tar.. for odin but gives me fail... im gonna download the stockrom again.. thanks..
No. Wait... what do you mean by efs.tar? Where you get it???
You seriously should do some research on xda instead of flooding my thread with such stuffs.... I really doubt if you understand what you are doing all the while...
I never knew that you can fix EFS by flashing an EFS provided by other people. Since all EFS is unique (like sony's TA).
Wish you best of luck... feel free to ask if you have any problems.
True
I think that I Will not gonna have luck... I dont have the imei to repair with octoplus.. so I cant fix the efs...too.. ..im lost.. mi imei its all detroyed con the back of my note I cant read IT.. And I dont remember how is...wish I could find an efs flashable for twrp...bug as you said.. each phone its unique
This is incredible work, thank you so much for keeping this amazing phone alive! Everything works so far, and the phone isn't even that slow considering its specs. I have two questions though. Does this support encryption? I'm asking because a lot of custom ROMs don't really do encryption right or at all. And the second one is about Magisk. I installed it successfully, it works, and while at first it was passing the SafetyNet checks, after a reboot it just stopped passing them (both). I had Magisk hidden (and the manager as well). I tried unhiding it and rehiding it but still, the tests won't pass. It's very strange because there was a moment that the phone passed them both.
Does anyone have valid fingerprints for the N7000 so I can try using MagiskHide Props Config?
Does anyone have valid fingerprints for the N7000 so I can try using MagiskHide Props Config?
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone