Hi guys, anyone updated to OL1? I tried to flash TWRP recovery or Philz recovery but both failed as seem nothing happen after flash... just the software status changed to custom now. please help, i need root very much
it says "recovery is not seandroid enforcing"
i have tried google but non fix my problem
I updated but he never tried to flash so can't help there. Trying to figure out what improvements it has.
casper1 said:
it says "recovery is not seandroid enforcing"
i have tried google but non fix my problem
Click to expand...
Click to collapse
that message appears everytime i boot to recovery; it means you aren't using a stock recovery. from power off, did you reboot holding the Home Button, Volume UP and Power Button all at the same time? that would boot you to recovery. From there, i would wipe caches or perform a factory reset if your phone does not boot up normally. by the way, this new release is available at sammobile.com for the N9208 with the BRI CSC code. i just downloaded it, but will hold off flashing till i'm sure it's rootable.
cortez.i said:
that message appears everytime i boot to recovery; it means you aren't using a stock recovery. by the way, this new release is available at sammobile.com for the N9208 with theBRI CSC code. i just downloaded it, but will hold off flashing till i'm sure it's rootable.
Click to expand...
Click to collapse
but if i tried to go back to recovery the next time, the stock 3e recovery still appears. could i still root it then, and how?
casper1 said:
but if i tried to go back to recovery the next time, the stock 3e recovery still appears. could i still root it then, and how?
Click to expand...
Click to collapse
read the recovery thread (where you posted the same questions) and look for post number 323; it suggests using an older bootloader to flash recovery and further in the thread i believe there's a link for "rootable" kernal from gundal. good luck!
---------- Post added at 04:07 PM ---------- Previous post was at 03:42 PM ----------
also wanted to know if you tried flashing the tar files that contained rooted kernels from the Original shipping firmware and the AOJ3 update.
casper1 said:
Hi guys, anyone updated to OL1? I tried to flash TWRP recovery or Philz recovery but both failed as seem nothing happen after flash... just the software status changed to custom now. please help, i need root very much
Click to expand...
Click to collapse
OL1 still rootable. But OK3 blocked non Samsung recovery. So you would need to downgrade bootloader to OK2.
Boot loop if you try to flash custom recovery without OK2 bootloader.
Mr. Gundal ..we love you!!
cortez.i said:
read the recovery thread (where you posted the same questions) and look for post number 323; it suggests using an older bootloader to flash recovery and further in the thread i believe there's a link for "rootable" kernal from gundal. good luck!
Thank you thank you... the Sboot solved the problem, appreciate that very much... i have been trying that for 2 days...
Click to expand...
Click to collapse
Related
Hi,
other day I was playing game on my note 1 and then battery ran out and now my phone wont boot up and it is stuck at animated samsung logo.
It was running on stock rom and it was never rooted.
Now when i go in recovery mode it gives this error:
failed to mount /efs
I tried installing the stock rom but with no luck.
I am newbie into this all, so can you please guide how to fix this ..
Regards
ahmedmasu said:
Hi,
other day I was playing game on my note 1 and then battery ran out and now my phone wont boot up and it is stuck at animated samsung logo.
It was running on stock rom and it was never rooted.
Now when i go in recovery mode it gives this error:
failed to mount /efs
I tried installing the stock rom but with no luck.
I am newbie into this all, so can you please guide how to fix this ..
Regards
Click to expand...
Click to collapse
You should try to put your Note in download mode and flash a stock rom with Odin.
You must flash the PIT file to repartition your phone's storage, chose the right one (16 or 32 Gb).
I am almost sure that your phone is soft bricked and it is recoverable.
If it don't work, thant mean that your have bad blocks in your phone's storage. Have you wiped your note while under ICS android ?
what rom were you on? if JB, try a factory reset.
nokiamodeln91 said:
what rom were you on? if JB, try a factory reset.
Click to expand...
Click to collapse
I was on latest stock rom which is ICS.
Btw I tried to reset it to factory but with no luck
lionelia said:
You should try to put your Note in download mode and flash a stock rom with Odin.
You must flash the PIT file to repartition your phone's storage, chose the right one (16 or 32 Gb).
I am almost sure that your phone is soft bricked and it is recoverable.
If it don't work, thant mean that your have bad blocks in your phone's storage. Have you wiped your note while under ICS android ?
Click to expand...
Click to collapse
Thank for your reply.
I tried flashing the stock rom with Odin but the error remained there
Can you please give me a link from where I can get PIT file?
ahmedmasu said:
I was on latest stock rom which is ICS.
Btw I tried to reset it to factory but with no luck
Click to expand...
Click to collapse
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
nokiamodeln91 said:
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
Click to expand...
Click to collapse
Is there any guide\link to do this ?
http://forum.xda-developers.com/showthread.php?t=1901191
nokiamodeln91 said:
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
Click to expand...
Click to collapse
I have successfully flashed rom on my phone which is : N7000ZSLPF_N7000OZSLPF_OZS
My phone is now out of bootloop but now I face a different issue that I cant get my sim card work, it gives no signal and I noticed one more thing that IMEI of my phone is blank.
I went into recovery mode and it is still showing that efs error as it was showing before...
Any suggestion what should I try to fix this ?
So you never installed any rom or a custom kernel?
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
Look for a file on your storage named efs.autobackup.img. If nothing like that, check on this site http://www.cvxcvx.pl/en/podstrona-0/naprawa-efs-w-i9100-n7000/ for some instructions. Read carefully and proceed.
nokiamodeln91 said:
So you never installed any rom or a custom kernel?
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
Look for a file on your storage named efs.autobackup.img. If nothing like that, check on this site http://www.cvxcvx.pl/en/podstrona-0/naprawa-efs-w-i9100-n7000/ for some instructions. Read carefully and proceed.
Click to expand...
Click to collapse
I followed the instructions provided by the manual ... after step 2 I get imei but after step 3 it get empty again.
Signals do come after step 2 but when I try to make some call it says "Not registered on network".
Looking forward to your reply.
i cannot help you in this case if there is no efs backup.. so.. you on your own..
nokiamodeln91 said:
i cannot help you in this case if there is no efs backup.. so.. you on your own..
Click to expand...
Click to collapse
Thanks for your help so far...
I currently have an imei but it is some random number starting with "004999" and I do get signals but cant make a call .. Do you know if there is some hope for me or not .. and what else I can try.
This is the developer imei. You may be able to make calls of you try a GB rom. Or there is one rom by ThaiDai which had some work around built into it. I don't know which one.
Else the site I mentioned earlier has contact info of cvxcvx. He can fix your phone remotely but by charging about 10 euros.
Need help for a bricked N7000
Hi guys,Im a complete newbie to the whole custom rom scenario. Yet, after being fed up of touchwiz on my N7000 i decided i wanted to taste some KitKat on my phone. After seeing many videos with positive reviews I thought it would be a rather easy process. But somehow I seem to have made a mistake and now my phone is stuck on Samsung Galaxy Note N7000 logo. I cant get into recovery mode as suggested on most places. As of now I only have access to the download mode but dont know what to do with it.
Here's what I tried doing :
1) I was on stock OS, and these are my specifics : Galaxy Note N-7000 running JB 4.1.2
Baseband version : N7000DDLS6
Kernel version: 3.3.31-906407
BUild number:JZO54K.N7000DDLSC
2) As I was following the procedure from Omnirom's official website, I first rooted my phone using Framaroot's single click root app. This gave me SuperSU app.
3) Then I tried installing TWRP recovery (recommended by Omni) but they dont support the N7000. I read a few other tutorials where it was stated the CWM recovery and that too Philz CWM recovery is the best to go with. Apparently it is just stock kernel with CWM recovery. Since the latest one(philz_touch_6.07.9-n7000) was not being installed, I installed the one before that which worked (PhilZ-cwm6-DDLSC-ODD-5.11.2-signed).
4) I even installed the ROM Manager as per the tutorial. However, uptil now I could access recovery mode ( Vol UP+Home+Power) and i saw the touch enabled philz recovery mode once. Then i did system reboot.
5)After reboot, this is where I did a mistake in my opinion. I opened ROM Manger and clicked on "open in recovery mode" option. Since then the phone is stuck on the Galaxy Note N7000 logo. Please help me revive the phone. Thanks in advance. Again, Im doing this for the first time and most terms are new to me. So please explain the procedure as other tutorials are not very clear.
You missed on reading the most important instructions.
Rom manager will not work with note. Recovery is built into the kernel on note and not as a separate partition.
Try harder to get into recovery mode. If you still can't, get the ddlsc Philz kernel tar version. Flash it using Odin. Then power off the device and boot into recovery. Then flash raw kernel. Reboot recovery. Flash omni and other required zips.
nokiamodeln91 said:
You missed on reading the most important instructions.
Rom manager will not work with note. Recovery is built into the kernel on note and not as a separate partition.
Try harder to get into recovery mode. If you still can't, get the ddlsc Philz kernel tar version. Flash it using Odin. Then power off the device and boot into recovery. Then flash raw kernel. Reboot recovery. Flash omni and other required zips.
Click to expand...
Click to collapse
How do I do i install the kernel using ODIN? I can only access download mode and nothing else. I cant access recovery mode. Please help.
PhilZ kernel has two versions, zip and tar. Use the tar version to flash via odin.
Sent from my GT-N7000 using Tapatalk 2
forest1971 said:
PhilZ kernel has two versions, zip and tar. Use the tar version to flash via odin.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Bro can i ask for the link of philz kernel and raw kernel. I'm new here. Thanks in advance.
ANDROID-000 said:
Bro can i ask for the link of philz kernel and raw kernel. I'm new here. Thanks in advance.
Click to expand...
Click to collapse
http://www.mediafire.com/?ep82ku4c6...o6dtlx8lbc3xz,ob3q9g36b9b3w22,d3v1gys7cbckiet
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes
Hello,
I'm trying to root my S5830 but it's not working. I have had it rooted before because I installed Samsung's stock android version 2.3.6 (The phone originally came with 2.2.1 I think).
The exact stock firmware on the phone is GINGERBREAD.XWKTQ.
I tried applying the universal_gb_root_v25 file in recovery mode and it seems to be working. There's no errors or anything and it tells me the device has been rooted and to restart. However after restarting, the device does not appear to be rooted at all, RootValidate tells me root access is not available. What am I doing wrong?
Thank you!
Cannot root S5830 2.3.6
brummbeere said:
Hello,
I'm trying to root my S5830 but it's not working. I have had it rooted before because I installed Samsung's stock android version 2.3.6 (The phone originally came with 2.2.1 I think).
The exact stock firmware on the phone is GINGERBREAD.XWKTQ.
I tried applying the universal_gb_root_v25 file in recovery mode and it seems to be working. There's no errors or anything and it tells me the device has been rooted and to restart. However after restarting, the device does not appear to be rooted at all, RootValidate tells me root access is not available. What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
have you just installed custom recovery?
I remeber you need first to root the phone and later install custom recovery.
If you not installed custom recovery, try to flash the attached file.
daniga74
daniga74 said:
have you just installed custom recovery?
I remeber you need first to root the phone and later install custom recovery.
If you not installed custom recovery, try to flash the attached file.
daniga74
Click to expand...
Click to collapse
Thanks, what custom recovery are you talking about? I just entered the default android recovery mode by pressing HOME and POWER buttons on startup. I tried the upd_1 file in recovery mode and it ran okay, but unfortunately it didn't fix the problem.
brummbeere said:
Thanks, what custom recovery are you talking about? I just entered the default android recovery mode by pressing HOME and POWER buttons on startup. I tried the upd_1 file in recovery mode and it ran okay, but unfortunately it didn't fix the problem.
Click to expand...
Click to collapse
I talk about CWM /clockwork) 5.0.2.6
This fixed it for me:
http://forum.xda-developers.com/showthread.php?t=1850070
So it seems the problem was there was not enough space left and I first had to run Delete_thinkdroid.zip to free up some space. After that I applied upd_1.zip and now the phone is rooted.
Please click one of the Quick Reply icons in the posts above to activate Quick Reply.
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
glad to know now it works!!!
Well done
If you need to root your device, I've a post too when you can find a couple of script to get some free internal space in order to achieve your goal
Hi,
I tried to root my N-920W8 with Nobel Kernel and it keeps restarting during phone calls.
And I found a post in XDA about the SkyHigh Kernal (which has fixed the call reboot bug) for N-920W8 but it is in .zip format where I can not use ODIN.
Tried to convert the .zip into .tar and failed.
I tried to connect my phone to my PC and place the .zip file into my phone USB file as there is no external SD for Note 5.
(Not sure whether there is a particular location to place the .zip file.)
After place the .zip, tried to flash it in the download/recovery mode (volume down+power+home botton),
it said could not find sd card/failed to do so.
Tried to go to SAMMobile.com to find stock rom, can not download anything...seems like it's empty or the link is not working.
I tried to search stock rom from other sites and found nothing as well.
I saw someone posted similar threads and suggested to try arter97 root but it will have slight lag which I do not want.
Plus, the person with the problem did not confirm whether or not it fixs the problem.
I am really frustrated with a lot searching and browsing so I decide to open a new thread to ask.
Do I have to flash back to stock rom in order to root properly? Or can I just find a stable kernel and flash it with ODIN and everything will work fine?
Could you provide step-by-step instructions and links as well? I am a noob but I am not taking it for granted but it's just that I am afraid I might mess things up...
*Also, I am not sure whether the following problem relates to the one above...
When I am rebooting, it says "KERNAL IS NOT SEANDROID ENFORCING"
Is it the same issue? Or a different one?
Thank you for taking your time to read my thread.
I will be really thankful for the solution. Thank you!
search arter97 kernels for the Note5...
cortez.i said:
search arter97 kernels for the Note5...
Click to expand...
Click to collapse
hi, I have the same problem with my N9208, someone told me to try installing arter 97 but in this link http://forum.xda-developers.com/note5/development/arter97-kernel-galaxy-note-5-t3189907 they said that this kernel is not compatible with the n9208 that is the model that I have, this is the list with the compatible models;
--- Galaxy Note 5 ---
SM-N920C
SM-N920I
SM-N920G
SM-N920S
SM-N920K
SM-N920L
SM-N920T
SM-N920W8
but I saw that you also have the n9208. I am going to flash the new stock rom that is on sammobile http://www.sammobile.com/firmwares/download/60964/N9208ZTU2AOK2_N9208ZZT2AOK2_BRI/
did you know how can I get succesfully rooting with no reboot problem?
Try this works great no drop call it is the best
http://forum.xda-developers.com/showthread.php?t=3214659
---------- Post added at 09:31 PM ---------- Previous post was at 09:15 PM ----------
First I was with space x but I had reboots and drop calls but I root with auto root xiaolu and everything works fine in my N9208
I fully support N9208 with SkyHigh kernel. You just have to read Posts 1-3 including requirements and install instructions. ... you don't use Odin !!
US Cellular Samung Note 5 stuck in seandroid no kernal enforce
I flashed TWRP to my phone and now it is stuck in boot loop. I need firmware to fix this problem?
uncled74 said:
I flashed TWRP to my phone and now it is stuck in boot loop. I need firmware to fix this problem?
Click to expand...
Click to collapse
I'm pretty sure your next step is to wipe all data , for your phone to boot. I had to do this when I first rooted my device (N-920w8 telus). I had followed this guide :
http://galaxynote5root.com/galaxy-n...alaxy-note-5-on-android-6-06-0-1-marshmallow/
On page 2 , steps 11 , 12 and 13.
Your phone will be stucked in a boot loop until you "format data" . Unfortunately , you will lose everything in your phone by doing this.
Once you've installed TWRP , so that you never have to "format data" again if you try other updates , i recommend "Flashfire" . This tool can install full firmware packages for updates , but without removing your recovery partition, leaving TWRP intact , which you can then use again to reflash SuperSU and the "no-verify-opt-encrypt.zip"
Good luck
stuck in FRP
got everything to work beautifully! Then I went to go to TWRP and forgot to take OEM lock off!! What can I do to get out of the FRP Lock? Kies wont except my serial number for some reason and I DON'T KNOW WHAT ELSE TO DO...
https://dl.google.com/dl/android/aosp/hammerhead-mmb29v-factory-62a68ee9.tgz go and get some'
Sent from my Nexus 5 using XDA Free mobile app
Thanks for the heads up. I think I'm going to wait for the OTA with this one. I'm hoping there's more than just security updates here, fingers crossed for some 800MHz LTE capability with my carrier.
dkconor said:
Thanks for the heads up. I think I'm going to wait for the OTA with this one. I'm hoping there's more than just security updates here, fingers crossed for some 800MHz LTE capability with my carrier.
Click to expand...
Click to collapse
I read they were going to fix the bug related to volume control arrows disappearing :fingers-crossed:
Kustaa said:
I read they were going to fix the bug related to volume control arrows disappearing :fingers-crossed:
Click to expand...
Click to collapse
Oh I hope that's true.. that has been driving me insane!
I flash it and rooted, but I can´t change build.prop anymore. strange.
edit: only one build prop editor worked. trough kernel auditor and throug explorer cant´t change.
Google Keyboard
error stop work
I just flash factory images without wipe. Everything worked fine as usual. But afterwards, I tried to flash the last twrp recovery, 3.0 but I can't flash it!!! After I flash it, via fastboot commands, when I try to enter recovey all I get is the stock recovery!!!
The other times I did this and twrp did flash ok!! Am I doing something wrong?!? Help me please!!
After flashing TWRP, are you booting directly to recovery using the buttons or are you rebooting the phone and then trying to enter recovery?
audit13 said:
After flashing TWRP, are you booting directly to recovery using the buttons or are you rebooting the phone and then trying to enter recovery?
Click to expand...
Click to collapse
I think I did both, and it didn't work on both methods after glashing two times...
I would try 2.8.7.1 instead of 3.0. I have seen a couple of posts from other XDA member with phones that work fine with 2.8.7.1 but not 3.0.
Hello! After flashing this, I've got Google Services battery drain again. Anyone else? Regards, Zagor
Hope it's the System UI memory leak fix...
the sound bar bug is not fixed
---------- Post added at 03:51 AM ---------- Previous post was at 03:51 AM ----------
[/COLOR]
onesolo said:
I just flash factory images without wipe. Everything worked fine as usual. But afterwards, I tried to flash the last twrp recovery, 3.0 but I can't flash it!!! After I flash it, via fastboot commands, when I try to enter recovey all I get is the stock recovery!!!
The other times I did this and twrp did flash ok!! Am I doing something wrong?!? Help me please!!
Click to expand...
Click to collapse
Recovery Fix -
Flash recovery in Fastboot
Use power button to manually power off
Reboot bootlader, then recovery. Voila.