hi to all. is anyone having issus with latest DLL7?
what i mean is that i made a clean install of LL7. after rooting with autoroot i installed TWRP 2.3.2.3 cause latest gave me only black screen.
but if i want to update from 2.3.2.3 to 2.3.3.1 it does never boot to recovery bur instead it gives broken Samsung n7100 screen.
it is the same if installing any CWM recovery. so Sammy has made some really weird changes with this update.
any other info. maybe bootloader downgrade just as in S3 thread. Advices
This is a little bit like my problems but I have random reboots instead. They occur almost immediately on a clean XLL7 install flashed from Odin without any root or apps installed.
Everything works perfectly in 4.1.1.
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
mariosraptor said:
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
Click to expand...
Click to collapse
I will try that and see what will happen.
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Click to expand...
Click to collapse
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
JCVD_ said:
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
Click to expand...
Click to collapse
do not worry. he means with stock rom.
in ARHD and other custom roms bootloader is left ou of flash.
anyway. i think that sammy has changed the some partitions. twrp works but only 2.3.2.3
No the roms who are based on dll7 are safe.
The recovery imao needs to be updated.
Sent from my GT-N7100 using xda app-developers app
Do you mean that it is dangerous to flash the CWM recovery to the device when it runs XXDLL7?
I flashed the root and CWM package after flashing XXDLL7 and it seems to work (my random reboot problem is unrelated I guess since it happened even with just stock recovery in place).
Now, I have the new bootloader and radio and flashed BatteryPlus 0.2 from CWM without any problems. I flashed the CWM-root-package through Odin after flashing XXDLL7, also from Odin.
So the question is: is there a problem with CWM and other custom recoveries and the XXDLL7?
Or are we talking about flashing mods?
No it can be an issue. It's not recommended at this stage.
Sent from my GT-N7100 using xda app-developers app
If there is a problem with CWM and XXDLL7, that could perhaps explain my reboot problem in that case.
If so, I will hold off for a while and stay on my current configuration.
I have the new bootloader and radio already.
i have noticed that 4.1.2 isnt so friendly with custom recovery. I had cwm recovery and going into it, took a lot of time with 4.1.2 firmware. Maybe samsung is trying to make some higher security in 4.1.2 against custom recoveries and etc.
If they wanted they could have made it absolutely protected. No I don't think they actually wanted to increase security.
I just think the new bootloader isn't friendly with the old recovery.
Sent from my GT-N7100 using xda app-developers app
Related
I did some searching and did not find a direct answer to this. Feel free to lock this thread if this has been answered.
I flashed back to my original stock ROM from when I rooted my device. I went through the series if updates, to this morning and and updated to ics. I have lost root access. So the question is.... Is there a way to root my device on ics without downgrading. I got to have my AD free and battery saving app
Sent from my ADR6350 using xda premium
Or if someone could post a link that would be great! Thank you!
Sent from my ADR6350 using xda premium
this worked for me: http://forum.xda-developers.com/showthread.php?t=1546593
I saw this earlier. I guess the leak could be what I have? I will have to check the firmware and compare it to what is listed. Thanks btw I will try this later tonight and update if this worked.
Sent from my ADR6350 using xda premium
I have same situation. I had rooted HC 3.2.1. Yesterday I made the update to stock ICS. I have to say that I am not happy with this new rom. It is not so smooth and fast that I expected. I am intrested to install some nice and fast custom rom. How to do it? What is need to be done to root and install the ClockworkMod??????
Worked perfectly and easily on mine. Acer_AV041_A500_1.033.00_PA_CUS1
I used the method as above, coming from the stock ota. And it worked I was able to use the battery saver and TB. I don't have a custom recovery, in order to do a back up for the time being but that is okay for now.
Edit: I see there is a bunch more threads started with this same topic so feel free to shut this down.
Hey did you unroot before installing the OTA ICS update? Also, what about recovery?
Acer_A500_041.205.01_COM_GEN2
Just to clarify, the root method for the ICS leak works on the US ICS OTA? (Acer_A500_041.205.01_COM_GEN2)
I just want to make sure, as I am being offered the OTA update from stock rooted Acer_A500_7.014.02_COM_GEN2. I want to make sure I can re-root if I do the update. Otherwise, I'll just wait for a CWM-flashable rooted version. Or has someone already posted that that I've missed?
Yes I was rooted. Then went back to my original stock ROM and stock recovery then went through all the updates. I updated this morning to the stock ics from Acer. Then used the thread above to root again. However I do not have a custom recovery at the moment but root access apps are working just fine. Which is all I need for now.(I live in southern Michigan)
thanks. A question about your custom recovery...Does Acer Recovery Installer no longer work to install CWM again? Or have you just not attempted to re-install CWM?
Kinz1980 said:
Yes I was rooted. Then went back to my original stock ROM and stock recovery then went through all the updates. I updated this morning to the stock ics from Acer. Then used the thread above to root again. However I do not have a custom recovery at the moment but root access apps are working just fine. Which is all I need for now.(I live in southern Michigan)
Click to expand...
Click to collapse
okay cool thanks. What did you use to unroot? For flashing back to stock recovery I will use "Acer Recovery Installer".
I tried using iconiaroot which I used to root but it still won't unroot my tablet. I even tried restarting and still nothing.
I lost root when doing the updates to clarify. And no I do not have a recovery at the moment, which I don't need because I am running ics with rooted apps that is all I need. I have no reason to flash a custom ROM. I will let the developers work with this for a bit and I will probably check it or later
Sent from my ADR6350 using xda premium
Kinz1980 said:
I lost root when doing the updates to clarify. And no I do not have a recovery at the moment, which I don't need because I am running ics with rooted apps that is all I need. I have no reason to flash a custom ROM. I will let the developers work with this for a bit and I will probably check it or later
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Okay great thanks. Glad to know it still worked, flashing the ota update with still having root. Only thing that worries me is I flashed back to stock recovery using that program an went I booted to recovery, it was exclamation point inside a triangle. Hope that doesn't affect my update process.
Sent from my Galaxy Nexus using XDA
I hope a root option comes out that doesn't require a ROM like gingerbreak. Maybe it's not possible for ICS or there aren't any developers interested in working on it, I don't know, but I'll wait.
It shouldn't your stock recovery is different then a custom recovery ie cwm. You will have to find another thread or something to flash a custom recovery. If your wanting to have a custom ROM. I have no need for it. So to put this into a nut shell.
Flash back to stock ROM (honeycomb)
Flash stock recovery.
Except the ota.
Use the link in first post to"re root"your device.
You will have a stock ROM from Acer that has root access. No recovery.
I Hope this makes it clear as mud:sly:
Hit the thanks button if any of this helped you, good day.
Sent from my ADR6350 using xda premium
Kinz1980 said:
It shouldn't your stock recovery is different then a custom recovery ie cwm. You will have to find another thread or something to flash a custom recovery. If your wanting to have a custom ROM. I have no need for it. So to put this into a nut shell.
Flash back to stock ROM (honeycomb)
Flash stock recovery.
Except the ota.
Use the link in first post to"re root"your device.
You will have a stock ROM from Acer that has root access. No recovery.
I Hope this makes it clear as mud:sly:
Hit the thanks button if any of this helped you, good day.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Just to let you know that you will have recovery if you follow this link.
http://forum.xda-developers.com/sho...ader+and+fixing+broken+recovery+in+leaked+ics
Wouldn't Rootkeeper be able to restore root after the update? It worked when I updated my Razr to the leaked ICS.
Kinz1980 said:
It shouldn't your stock recovery is different then a custom recovery ie cwm. You will have to find another thread or something to flash a custom recovery. If your wanting to have a custom ROM. I have no need for it. So to put this into a nut shell.
Flash back to stock ROM (honeycomb)
Flash stock recovery.
Except the ota.
Use the link in first post to"re root"your device.
You will have a stock ROM from Acer that has root access. No recovery.
I Hope this makes it clear as mud:sly:
Hit the thanks button if any of this helped you, good day.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
okay. sorry for all the questions, but does it matter what version of HC I'm on? You say flash back to stock, is that just if I was running a custom rom? I can't find the sdcard I have my backups on but I'm running completely stock 3.2.1 HC. Just rooted and running CWM.
No ICS Update for me, Rooted 3.2, Need Help!
I thought having my tablet simply rooted wouldnt cause a big issue, i didnt flash it, im still running 3.2 gen 2 but no update for ics has appeared, when checking for update it says im up to date, ive checked several times, tried looking into it seeing if i had to unroot somehow which ive found no program that will unroot my tablet successfully i do not want to wipe because last time i rooted it wiped and i lost alot of important data i couldnt back up. Someone please advise me or send me the Canadian/USA Update Zip or other location for the official ics. Thanks!
Well I tried cm9 and latest 4.0.4 from Germany... In both I had a screen yellowish tint blinking issue... After flashing stock 4.0.4 I managed to root it via Dr . Ketan method... And also got cwm but cwm won't stick
That said I was looking forward to flash a safe kernel but I was afraid of doing it via cwm because I handle 4.0.4 as non safe (super brick bug infested) so I didn't dare to do so... So with no other option but Odin I didn't want to activate the binary counter because I wanted to return the phone because the yellow screen issue..
In was OMG how can I get rid of this w/o bricking my phone.. Well I have downloaded abyss kernel then momentary flashed cwm and then flashed abyss... When I rebooted the recovery a counter started and freaked me out... I let it count to 10.000 and got tired of it... I thought my phone was dead...
Then I turned it off and did the recovery sequence and it booted into the red cwm(abyss recovery) then wiped everything from there and installed a custom gb rom.
.. Luckily everything went fine and the custom rom booted perfectly.. In fact I'm using it right now checkrom notehd v6 its smooth as hell...
I can not reproduce the yellowish tint here and will try stock gb tomorrow and see if I can get the issue running... I'm worried because if I can't get the issue in gb then I can't claim warranty because it clearly says that I lose it if I change the software and it says the phone comes with android 2.3.6 so that means I'm stuck with gb..
I rebooted into Odin mode to see if something happened to the binary counter..
. And well everything seems fine but but but... I'm really worried about the screen issue as I proved its not hardware issue... How can I claim my warranty?
And wow what a pain in the ass to get rid of 4.0.4 without voiding warranty...
Sent from my GT-N7000 using xda premium
to get back to gb you just have to flash any gb rom through odin... There was not need to go through the custom kernel for downgrade. .also on Ics, as long as you don't factory reset/wipe you are safe from any brick provided you know what you are doing with the phone and what apps you are installing.
to get back to gb you just have to flash any gb rom through odin... There was not need to go through the custom kernel for downgrade. .also on Ics, as long as you don't factory reset/wipe you are safe from any brick provided you know what you are doing with the phone and what apps you are installing.
Click to expand...
Click to collapse
Yeah but as there is some roms that performs full wipe or non wipe and I'm not really sure that's the case for the stock roms from sammobile and or if Odin do a factory reset before flashing I was scared as hell
Noone provides clear steps here for doing things... So I followed what seemed more logical... Wich was getting a safe kernel to wipe without increasing the binary counter
Those "how to upgrade" guides should include at least a link for the safest way to "how to downgrade"
Nvm the point it's still the screen issue I want to know why it happens un ics and not in gb at least in this custom rom... I'm on... I want to change my phone but if I can not prove the issue I can not get a replacement
Sent from my GT-N7000 using xda premium
You can get any rom from SAMMOBILE that says "kies" after the version... those are official roms rolled over kies which are always non wipe...
Or you could flash speedmod kernel 3-7 using ODIN, that's a safe kernel (brickbug free), on 4.0.4 and then flash anything you want, no worries about brick...
Enviado de meu GT-N7000 usando o Tapatalk 2
mtdelnero said:
You can get any rom from SAMMOBILE that says "kies" after the version... those are official roms rolled over kies which are always non wipe...
Or you could flash speedmod kernel 3-7 using ODIN, that's a safe kernel (brickbug free), on 4.0.4 and then flash anything you want, no worries about brick...
Enviado de meu GT-N7000 usando o Tapatalk 2
Click to expand...
Click to collapse
Yeah and increasing binary counter and lose warranty? No thanks Btw im on gb several hours ago just sharing my experience and still asking about the screen issue
Sent from my GT-N7000 using xda premium
I just downloaded the firmware, put it into recovery mode (power + home + vol. up) and then selected the file from PC Odin in the PDA box and that's it!
I'm not trying any more ICS roms from Sammy. They all suck.
Final5k said:
to get back to gb you just have to flash any gb rom through odin... There was not need to go through the custom kernel for downgrade. .also on Ics, as long as you don't factory reset/wipe you are safe from any brick provided you know what you are doing with the phone and what apps you are installing.
Click to expand...
Click to collapse
How do u flash the speedmod kernel w pc odin what gets ticked?
Btw didn't make that kies icon non-wipe connection, thanks
Sent from my GT-N7000
where is the problem with the binary counter? just install the triangle away app from chainfire and you are fine
Sent from my GT-N7000 using xda app-developers app
k!DDa said:
where is the problem with the binary counter? just install the triangle away app from chainfire and you are fine
Click to expand...
Click to collapse
+1 - Triangle Away is your friend to remove this!
zkyevolved said:
I just downloaded the firmware, put it into recovery mode (power + home + vol. up) and then selected the file from PC Odin in the PDA box and that's it!
I'm not trying any more ICS roms from Sammy. They all suck.
Click to expand...
Click to collapse
This +1
And didn't know about such app(triangle away), should be sticked as a main thread, only knew about this jigs Wich I can not get in my country
Sent from my GT-N7000 using xda premium
You could just install any gb rom via Odin and one install get into stock recovery and clean and wipe data and cache is easy
And if you downloaded a rootable gb rom you can simply follow the rooting method as per the sticky and install cm9 from there
And no binary counter
Sent from my GT-N7000 using Tapatalk 2
msedek said:
Well I tried cm9 and latest 4.0.4 from Germany... In both I had a screen yellowish tint blinking issue... After flashing stock 4.0.4 I managed to root it via Dr . Ketan method... And also got cwm but cwm won't stick
That said I was looking forward to flash a safe kernel but I was afraid of doing it via cwm because I handle 4.0.4 as non safe (super brick bug infested) so I didn't dare to do so... So with no other option but Odin I didn't want to activate the binary counter because I wanted to return the phone because the yellow screen issue..
In was OMG how can I get rid of this w/o bricking my phone.. Well I have downloaded abyss kernel then momentary flashed cwm and then flashed abyss... When I rebooted the recovery a counter started and freaked me out... I let it count to 10.000 and got tired of it... I thought my phone was dead...
Then I turned it off and did the recovery sequence and it booted into the red cwm(abyss recovery) then wiped everything from there and installed a custom gb rom.
.. Luckily everything went fine and the custom rom booted perfectly.. In fact I'm using it right now checkrom notehd v6 its smooth as hell...
I can not reproduce the yellowish tint here and will try stock gb tomorrow and see if I can get the issue running... I'm worried because if I can't get the issue in gb then I can't claim warranty because it clearly says that I lose it if I change the software and it says the phone comes with android 2.3.6 so that means I'm stuck with gb..
I rebooted into Odin mode to see if something happened to the binary counter..
. And well everything seems fine but but but... I'm really worried about the screen issue as I proved its not hardware issue... How can I claim my warranty?
And wow what a pain in the ass to get rid of 4.0.4 without voiding warranty...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ever since I aware of the "brick" problem, I have not done a single wipe whenever I need to flash a new ROM. I have not encountered any big problem. :fingers-crossed:
So, for me, is just 2 steps:
1. Flash Abyss kernel.
2. Flash the ROM.
That is it (of course you need get it rooted 1st). The only thing is, 1st boot after flash ROM would take longer to boot up. I did run adb logcat to view the output to make sure the phone is still running/loading though...
So far, Criskelo ROM is the best for me. So I would stick with this ROM for now.
msedek said:
This +1
And didn't know about such app(triangle away), should be sticked as a main thread, only knew about this jigs Wich I can not get in my country
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
You would have known if you know how to search and patiently read the threads.
Sent from my GT-N7000 using xda app-developers app
Hey I'm new to the forums but been reading them for a while and I just have a question with OTA updates. I have a nexus 4 that's been rooted and have clockwork mod. I have also flashed the .33 baseband on 4.2.2. I have stock rom but Franco kernel however I backed up the stock kernel with his updater app.
I know I can't OTA with the kernel but flashing the stock one is no big deal. Can I OTA with the rest being on there?
Also if I do the lte wifi hotspot fix will that stop the OTA update as well?
Thanks in advance.
Sent from my Nexus 4 using xda premium
As long you have clockwork mod on the rom you can not OTA...its always going to be manual way of flashing the OTA and that process will remove clockwork mod but using apps like voodoo keeps you rooted so you can easily install clockwork mod again after the update.
No Recovery+Stock ROM+Stock Kernel+Stock Latest Radio= auto OTA update.
I hope that made sense..but i could be wrong but that's what works for me.
Sent From My Beasty Nexus 4 with Awesome Beats.
ROM: Mysterious AOKP 4.2.2
Kernel: Faux 123 latest tbm.
Recovery: TWRP
Helderg1984 said:
Hey I'm new to the forums but been reading them for a while and I just have a question with OTA updates. I have a nexus 4 that's been rooted and have clockwork mod. I have also flashed the .33 baseband on 4.2.2. I have stock rom but Franco kernel however I backed up the stock kernel with his updater app.
I know I can't OTA with the kernel but flashing the stock one is no big deal. Can I OTA with the rest being on there?
Also if I do the lte wifi hotspot fix will that stop the OTA update as well?
Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
You CAN ota if you have a custom recovery.
However, the WiFi hotspot fix will kill it.
I made a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=2145848
Sent from my Nexus 7 using xda premium
So if anything is modded at all except for basic root I won't be able to apply the update that arrives to my phone directly right? I will have to flash it in cwm? I assume I will have to wipe cache and such before I apply the zip right?
Do I have to revert anything back stock or can I just flash the zip directly over what I have now and just re apply the kernel and baseband?
Sent from my Nexus 4 using xda premium
Sorry one more thing with the latest SU I will stay rooted I think but I will lose cwm and have to re obtain it or will I keep it if survival mode is checked?
Sent from my Nexus 4 using xda premium
Helderg1984 said:
Sorry one more thing with the latest SU I will stay rooted I think but I will lose cwm and have to re obtain it or will I keep it if survival mode is checked?
Click to expand...
Click to collapse
If you flash it from CWM then you will keep CWM and also keep root (if you say yes when it asks you).
Sent from my Nexus 4
Sorry I am a bit confused still, when I get the update.zip and flash it in CWM do I have to wipe or no? and if I don't will everything stay the same? or will I lose my 0.33 baseband and kernel? I'm also wanting to do the lte hotspot fix so would I lose that too?
steviewevie said:
If you flash it from CWM then you will keep CWM and also keep root (if you say yes when it asks you).
Sent from my Nexus 4
Click to expand...
Click to collapse
Helderg1984 said:
Sorry I am a bit confused still, when I get the update.zip and flash it in CWM do I have to wipe or no? and if I don't will everything stay the same? or will I lose my 0.33 baseband and kernel? I'm also wanting to do the lte hotspot fix so would I lose that too?
Click to expand...
Click to collapse
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
You actually can accept a ota update with a custom recovery but you have to be stock everything else, no other mods or anything. The ota will install fine and youll see that it goes through your custom recovery when updating. After the update you will lose root and your custom recovery however unless you recovery someone holds onto it.
As I know, we need to modify something after installing custom recovery. Else, stock recovery will be installed upon reboot. So even after modifying, OTA still works ?
Rizy7 said:
You actually can accept a ota update with a custom recovery but you have to be stock everything else, no other mods or anything. The ota will install fine and youll see that it goes through your custom recovery when updating. After the update you will lose root and your custom recovery however unless you recovery someone holds onto it.
Click to expand...
Click to collapse
Sent from Mako
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applyng the update.
heat361 said:
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
Click to expand...
Click to collapse
heat361 said:
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
Click to expand...
Click to collapse
Everything about this post is incorrect.
I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.
Helderg1984 said:
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applying the update.
Click to expand...
Click to collapse
Just read the thread I linked earlier. It has answers to your questions.
Sent from my Nexus 4 using xda premium
El Daddy said:
Everything about this post is incorrect.
I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.
Just read the thread I l
Can you tell me what's wrong with what I said? I was assuming he was on stock rooted with a custom recovery. Is it not true that if you get an ota update and it contains a new baseband and new stock kernel it will overwrite the last last stock kernel and baseband.
Click to expand...
Click to collapse
heat361 said:
El Daddy said:
Everything about this post is incorrect.
I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.
Just read the thread I l
Can you tell me what's wrong with what I said? I was assuming he was on stock rooted with a custom recovery. Is it not true that if you get an ota update and it contains a new baseband and new stock kernel it will overwrite the last last stock kernel and baseband.
Click to expand...
Click to collapse
No it doesn't overwrite anything. It just fails.
OTA's contain patches. Not complete files. If the original file isn't there it will abort.
I can see how this can be confusing because it is different from custom roms.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
But thats only if he has the lte fix right. So if he just flashes a stock kernel without that patch, the ota could work.
For example the stock boot.img
I'm rooted with cwm, custom kernel and old baseband, stock rom. I mean I can very easily revert my kernel back to stock and flash the newest baseband.
The only thing is there's a bunch of stuff I might want to do more but don't want to make it hard to update since it's important to me.
Sent from my Nexus 4 using xda premium
Sent from my Nexus 4 using xda premium
heat361 said:
But thats only if he has the lte fix right. So if he just flashes a stock kernel without that patch, the ota could work.
For example the stock boot.img
Click to expand...
Click to collapse
Yep. The phone needs to be 100% stock with the exception of the recovery to complete the OTA. If the files,kernel,radio, etc. are replaced to the original state you'd be good to go.
PS. Sorry if I came off as a jerk this morning. I had a case of the Mondays.
Helderg1984 said:
I'm rooted with cwm, custom kernel and old baseband, stock rom. I mean I can very easily revert my kernel back to stock and flash the newest baseband.
The only thing is there's a bunch of stuff I might want to do more but don't want to make it hard to update since it's important to me.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Just as I wrote above, You can do as many modifications as you want, just make sure you bring the phone back to stock before you flash the OTA.zip, otherwise it will fail.
When the new OTA comes out I will update my OTA Help-Desk thread with all the new requirements.
Helderg1984 said:
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applyng the update.
Click to expand...
Click to collapse
Just watch this its eazy as 1 2 3!!!
http://www.youtube.com/watch?v=ky5miA8ilr0
Anyone else have the issue of it just continuously trying to boot? I'm using the CWM auto-loki that's in the development section.
Reflashed it three more times. Now it freezes @ Samsung battery screen when charging, or if I wait long enough it'll unfreeze. Still loops at Slim Bean startup, what sucks though is that for one thing it mounts as an MTP device so it seems like it's on but just not initializing, another thing is that the original flash I was able to get to the slim bean battery charging screen (but obviously still couldn't turn it on)
Thinking it might be a kernel issue, since I installed ktoonsez's AOSP kernel when I installed it. Any recommendations of a kernel to use? I'm using the CWM recovery that has auto loki so, I could probably use ones made for 9500,9505, etc.
(Pasted this from the Slim Bean thread, haven't gotten an answer in like 5 hours and it's a little urgent xD. I'm on the AT&T S4 of course, any other information I'll be glad to provide. Hopefully this is just a simple fix)
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Spunjah413 said:
I bet is related to the kernel. I have been using Slim Bean flawlessly, with none of the issues you mention. Using TWRP to flash and recover.
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you on then, just stock?
Stock Kernel.
Sent from my SGH-I337 using xda app-developers app
I installed Slim Bean with Ktoon kernel and it worked fine. Just make sure to wipe system and the caches. It did take a little longer to boot the first time but after that it was all good.
Sent from my SGH-I337 using xda app-developers app
Isn't ktoonsez kernel for a Touchwiz based ROM?
Slim Bean is AOSP, therefore i'm not sure they jive correctly, which would clearly explain the OP's problem.
EDIT: Didn't realize he updated an AOSP based Kernel. In anycase OP, I would still attempt using the stock kernel to see if you problems get fixed.
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
_Dennis_ said:
Patching a patched kerenel changes nothing. Dan said if you run loki on a patched recovery or kernel it just send the original to the output. Nothing happens.
Sent from my AT&T S4 running an international ROM.
Click to expand...
Click to collapse
Thanks for clarification.
LostInMyHead said:
Slim is already LOKI patched, so don't use the CWM that auto-patches, use TWRP
Click to expand...
Click to collapse
I know someone else clarified this already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
iKat said:
I know someone else clarified htis already, but when I downloaded Slim it actually wasn't Loki patched for whatever reason, and I couldn't boot without reinstalling stock. I did download the one in the right thread, it just didn't have a boot.lok in it for whatever reason. Anyways, I'm gonna try reflashing and wiping /system another time, wish me luck. I don't have the original kernel backed up though because I'm an idiot, so does anyone have a link to that? If not I could probably scour it out somewhere, but just wondering for convenience's sake.
Click to expand...
Click to collapse
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
LostInMyHead said:
In advanced restore boot is the kernel.
Download the ROM and addons again, you shouldnt have any issues... If you are currently on stock, do a comprehensive wipe, a manual format of system and data
Click to expand...
Click to collapse
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
iKat said:
No files found :/ I guess I'll reinstall stock, back stuff up, and do the comprehensive wipe like you said. I really, really want Slim, lol.
Edit: Well, ****. Reinstalled stock with Odin and now no matter how many times I reboot I only have a status bar.. phone is fairly hot too. So, now I don't even have access to recovery ;-;
Click to expand...
Click to collapse
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
LostInMyHead said:
Flash back to stcok with ODIN
Use the one click tool to get LOKI recovery
The ROM and addons are in the OP of the SLIM LOKI Thread
Click to expand...
Click to collapse
Oh my lord, thank you good sir. Slim Bean is up and working as of right now ^^;. May be a little bit before I apply a custom kernel though o.o
So, I am still running MF9. I am rooted, and sporting a custom rom, albeit a fairly old one: Sacs_Custom 4.X with the included kernal. I want to flash a newer rom, especially since new bugs are starting to crop up. I know that newer ones are on MJA (right?) and are based on 4.3 or 4.4. So, assuming I have selected my Rom, can I simply factory reset and then flash the new rom? Or do I need to take factory updates after reset, then re-root the device to flash these newer roms?
Go get the MK2 modem without the bootloader from development section. Odin it and flash whatever ROM your heart desires
Sent from my SPH-L720 using Tapatalk
Here's a good place to start...
http://forum.xda-developers.com/showthread.php?t=2277480
bgibs1 said:
Here's a good place to start...
http://forum.xda-developers.com/showthread.php?t=2277480
Click to expand...
Click to collapse
This seems very helpful, and I will tackle it as soon as my battery recharges. The one thing I want to be sure about first...I of course have TWRP recovery installed already. Flashing Philz without removing it (I assume Philz would overwrite it?) is fine, right?
beerindex said:
This seems very helpful, and I will tackle it as soon as my battery recharges. The one thing I want to be sure about first...I of course have TWRP recovery installed already. Flashing Philz without removing it (I assume Philz would overwrite it?) is fine, right?
Click to expand...
Click to collapse
Yup, here is the link to the newest Philz
http://d-h.st/fGN
You can flash Philz right through TWRP and vise versa. Flash, wipe cache and dalvik if you want. Reboot to recovery and it'll change.
Sent from my SPH-L720 using xda app-developers app
also wanting to update
So I'm in the same boat, I'm running triforce mf9.
If I'm understanding this right I should;
-flash philz(which I can do from twrp?)
-Then I can flash triforce's new mja?
That seems a little too easy with how complex http://forum.xda-developers.com/showthread.php?t=2277480 seems.
seanwn86 said:
So I'm in the same boat, I'm running triforce mf9.
If I'm understanding this right I should;
-flash philz(which I can do from twrp?)
-Then I can flash triforce's new mja?
That seems a little too easy with how complex http://forum.xda-developers.com/showthread.php?t=2277480 seems.
Click to expand...
Click to collapse
It depends on if you want to keep mf9 as your bootloader and knox out of your hardware. If you want a little more flexibility in the long run, use the guide you linked to. If you don't care about your bootloader then follow the steps in this thread
Sent from my Nexus 7 using XDA Premium 4 mobile app
seanwn86 said:
So I'm in the same boat, I'm running triforce mf9.
If I'm understanding this right I should;
-flash philz(which I can do from twrp?)
-Then I can flash triforce's new mja?
That seems a little too easy with how complex http://forum.xda-developers.com/showthread.php?t=2277480 seems.
Click to expand...
Click to collapse
I used odin to flash unknownforce's mk2 firmware. And flashed the TriforceV5 with the latest TWRP no problem. Made backups, switched between roms. Super easy.
Sent from my SPH-L720 using xda app-developers app
imbmiller said:
It depends on if you want to keep mf9 as your bootloader and knox out of your hardware. If you want a little more flexibility in the long run, use the guide you linked to. If you don't care about your bootloader then follow the steps in this thread
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
HPferoxCraft said:
I used odin to flash unknownforce's mk2 firmware. And flashed the TriforceV5 with the latest TWRP no problem. Made backups, switched between roms. Super easy.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
How do I check/verify my bootloader after I update?
HPferoxCraft; did you keep mf9 bootloader?
I flashed philz recovery, and was going to odin the mk2 firmware, then flash triforceV5. Just want to double check before I do this.
seanwn86 said:
How do I check/verify my bootloader after I update?
HPferoxCraft; did you keep mf9 bootloader?
I flashed philz recovery, and was going to odin the mk2 firmware, then flash triforceV5. Just want to double check before I do this.
Click to expand...
Click to collapse
Hey. I did keep it for a bit. Until I set everything up and made backups and ran it for awhile. Then curiosity had me update to mk2. Every things running fine/better connection. Seeing 4g more where I see 3g normally.
Sent from my SPH-L720 using xda app-developers app
So I'm updated now, but it appears I've lost SuperSU.
I open mybackuppro, it says I'm rooted, and asks if I want to ask for super user permission. But SuperSU never pops up, and I don't see it in the app drawer.
Thoughts, ideas?
seanwn86 said:
So I'm updated now, but it appears I've lost SuperSU.
I open mybackuppro, it says I'm rooted, and asks if I want to ask for super user permission. But SuperSU never pops up, and I don't see it in the app drawer.
Thoughts, ideas?
Click to expand...
Click to collapse
Try flashing the supersu zip found here http://forum.xda-developers.com/showthread.php?t=1538053 in recovery and you should be good to go.
imbmiller said:
Try flashing the supersu zip found here http://forum.xda-developers.com/showthread.php?t=1538053 in recovery and you should be good to go.
Click to expand...
Click to collapse
Thank you very much. Downloading/flashing now.
Minor question, what's the difference between this and the super user that I had before that had like a superman triangle logo?