I think someone already answered this bit can I flash a 4.4 rom if I'm on stock 4.3??
Jairsantana said:
I think someone already answered this bit can I flash a 4.4 rom if I'm on stock 4.3??
Click to expand...
Click to collapse
Yes, but you will have to either modify the assert lines to reflect your new bootloader or delete the assert lines completely. Just be sure you have downloaded a d2spr ROM. And by stock 4.3, did you take the official Knox update or flash a modified Knox-free version?
Mr. Struck said:
Yes, but you will have to either modify the assert lines to reflect your new bootloader or delete the assert lines completely. Just be sure you have downloaded a d2spr ROM. And by stock 4.3, did you take the official Knox update or flash a modified Knox-free version?
Click to expand...
Click to collapse
i took the stock 4.3 with the knox ... im wondering the same thing
xmacx97 said:
i took the stock 4.3 with the knox ... im wondering the same thing
Click to expand...
Click to collapse
My understanding is that you can still root and flash custom ROM's as long as you don't care about permanently tripping the Knox flag. What you definitely do not want to do is try to use Odin to push a stock .tar with a bootloader that is an earlier (pre-Knox) version because Knox will interfere and hard brick your phone.
Mr. Struck said:
Yes, but you will have to either modify the assert lines to reflect your new bootloader or delete the assert lines completely. Just be sure you have downloaded a d2spr ROM. And by stock 4.3, did you take the official Knox update or flash a modified Knox-free version?
Click to expand...
Click to collapse
It is a stock rooted rom without the knox apps!!
Jairsantana said:
It is a stock rooted rom without the knox apps!!
Click to expand...
Click to collapse
That's good, should save you the headache of re-rooting and disabling Knox apps. If you don't know how to modify/delete the assert lines let me know.
Mr. Struck said:
That's good, should save you the headache of re-rooting and disabling Knox apps. If you don't know how to modify/delete the assert lines let me know.
Click to expand...
Click to collapse
Hey can I flash any 4.3 rom without any problems Like cm10??
Jairsantana said:
Hey can I flash any 4.3 rom without any problems Like cm10??
Click to expand...
Click to collapse
That should be a yes. I need to clarify as well, I think I got a little mixed up about who had what with your question and the other question from the user who took the OTA. You will need to know which bootloader you have, if it is the newest MK3 version, then the updater-script will not have your bootloader listed in the assert lines and you will then be required to modify the asserts to reflect your specific bootloader or delete the assert lines altogether. The user who took the OTA should definitely have this version installed. If you are on a previous bootloader like MD4, no modifying or deleting will be necessary with the asserts.
Mr. Struck said:
That should be a yes. I need to clarify as well, I think I got a little mixed up about who had what with your question and the other question from the user who took the OTA. You will need to know which bootloader you have, if it is the newest MK3 version, then the updater-script will not have your bootloader listed in the assert lines and you will then be required to modify the asserts to reflect your specific bootloader or delete the assert lines altogether. The user who took the OTA should definitely have this version installed. If you are on a previous bootloader like MD4, no modifying or deleting will be necessary with the asserts.
Click to expand...
Click to collapse
Ok long story short I did flash the ota zip then root my phone but now I'm runing staticpower rom!!!
Jairsantana said:
Ok long story short I did flash the ota zip then root my phone but now I'm runing staticpower rom!!!
Click to expand...
Click to collapse
OK, so your boot loader should be MK3 then, it is listed under Settings/About Phone if you need to find out for sure, In that case the original info about the assert lines will hold true if you want to flash 4.4; the exception will be the latest builds by Cjen1987, he has already modified the updater-script to remove the asserts and allow TWRP or CWM to flash.
Mr. Struck said:
OK, so your boot loader should be MK3 then, it is listed under Settings/About Phone if you need to find out for sure, In that case the original info about the assert lines will hold true if you want to flash 4.4; the exception will be the latest builds by Cjen1987, he has already modified the updater-script to remove the asserts and allow TWRP or CWM to flash.
Click to expand...
Click to collapse
Ok so that means that I can flash any 4.3 or 4.4???
Jairsantana said:
Ok so that means that I can flash any 4.3 or 4.4???
Click to expand...
Click to collapse
Yes, but again remember that the updater-script contained in most of them will not recognize your boot loader, you will need to modify the updater-script if you flash and get an "Error7" message. The thing everyone with the Knox boot loader needs to keep in mind is that trying to push a .tar file via Odin in order to restore a previous stock build with an older version of the boot loader (I.e. MD4) will hard brick your phone beyond even the help of Chuck Norris because Knox will step in and give you an expensive paperweight!!
Mr. Struck said:
Yes, but again remember that the updater-script contained in most of them will not recognize your boot loader, you will need to modify the updater-script if you flash and get an "Error7" message. The thing everyone with the Knox boot loader needs to keep in mind is that trying to push a .tar file via Odin in order to restore a previous stock build with an older version of the boot loader (I.e. MD4) will hard brick your phone beyond even the help of Chuck Norris because Knox will step in and give you an expensive paperweight!!
Click to expand...
Click to collapse
I need to know how to change the updater-script and will i be able to have the apps2sd opyion like on stock MK3???
Jairsantana said:
I need to know how to change the updater-script and will i be able to have the apps2sd opyion like on stock MK3???
Click to expand...
Click to collapse
I have a tutorial posted on Android Forums for my fellow VM SGS3 users. I will link you to that so that I don't have to type out a long explanation here; doesn't matter what carrier you are on to use this method, it is universal, but it is a must for anyone on VM or Boost to be able to use Sprint ROM's. It has only become an issue lately for Sprint users due to the newest bootloader.
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
Mr. Struck said:
I have a tutorial posted on Android Forums for my fellow VM SGS3 users. I will link you to that so there hat I don't have to type out a long explanation here; doesn't matter what carrier you are on to use this method, it is universal, but it is a must for anyone on VM or Boost to be able to use Sprint ROM's. It has only become an issue lately for Sprint users due to the newest bootloader.
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
Click to expand...
Click to collapse
Hey so I was able to flash the official CM11,everything fine the only problem is that I couln't move the apps to my sdcard like on the mk3 rom is there anything I can do or I just have to deal with it???
Jairsantana said:
Hey so I was able to flash the official CM11,everything fine the only problem is that I couln't move the apps to my sdcard like on the mk3 rom is there anything I can do or I just have to deal with it???
Click to expand...
Click to collapse
I think apps to SD card is an issue specific to 4.4 currently, I have seen other people with this issue as well. Just opened Titanium Backup on my phone to see, option used to be available but is currently not there. Maybe will be addressed further down the line, don't really have an answer though.
Mr. Struck said:
I think apps to SD card is an issue specific to 4.4 curreI was tly, I have seen other people se ingth this issue as well. Just opened Titaium Backup on my phone to see, option used to be available but is currently not there. Maybe will be addressed further down the line, don't really have an answer though.
Click to expand...
Click to collapse
Ok let me re ask the question because you may or may not answer my question the way i referring about....when you go in the mk3 to settings/applications manager/ we have some options like....downloaded/sd card/running/all..... but in CM11 i don't see the sdcard option!!!
Jairsantana said:
Ok let me re ask the question because you may or may not answer my question the way i referring about....when you go in the mk3 to settings/applications manager/ we have some options like....downloaded/sd card/running/all..... but in CM11 i don't see the sdcard option!!!
Click to expand...
Click to collapse
I think we are on the same page or real close communication wise. I don't think apps can go to SD card on 4.4, which is why I checked Titanium to see if it still supplied that option. Just make sure to free up as much internal space as possible by putting any file that you can on SD card instead of internal storage.
Mr. Struck said:
I think we are on the same page or real close communication wise. I don't think apps can go to SD card on 4.4, which is why I checked Titanium to see if it still supplied that option. Just make sure to free up as much internal space as possible by putting any file that you can on SD card instead of internal storage.
Click to expand...
Click to collapse
Alright yeah that was my question and how about cm10.2???
Jairsantana said:
Alright yeah that was my question and how about cm10.2???
Click to expand...
Click to collapse
MK3 is the only rom, including both AOSP and TW, that lets you move apps to sdcard
Related
Hi guys I was just wondering if I unlock and root my stock GSM Nexus, not installing CWM or any custom roms at all just keeping it stock (aside from Superuser, root). Does that stop or affect the OTA updates from google at all.
I did a search but its all basically about putting on CWM and flashing roms and pretty much all rooting help apps I found seem to want to install cwm as well so I'm curious if once I root it is my only way of updating is manually flashing roms myself
http://forum.xda-developers.com/showthread.php?t=1441478
Ahh damn my search skills must suck but I still have to say that the answer was a little vague too
Rooting will not affect OTA updates. If you make any changes to anything outside /sdcard/ it'll cause problems. Manual update will not wipe the device.
Click to expand...
Click to collapse
I guess it means your fine and update will work as long as you don't go modding the original files ?
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Laynee1 said:
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Click to expand...
Click to collapse
You should still get your OTA updates. They may break the root on your phone though but thats not really a big deal.
Sent from my XT860 using XDA App
Laynee1 said:
The thing is that i asked this question several times, and every time i get different answer..
I have also rooted my phone and unlocked bootloader, without any custom cWM or custom rom.. I have changed bootanimation (its in system, so its outside sdcard).
Will i be able to get OTA update, to see it and to install it ?
Thanks in advance
Click to expand...
Click to collapse
You get a different answer because there are a lot of people who have no clue what they are talking about, passing on wrong information.
First of all, there is a difference between "getting" an OTA update notification, and having it install. Those are two separate things. You will get the OTA update notification. Whether or not it will install depends on many things, and it changes with every update. The update has a series of "asserts" or verifications that it runs through to make sure all the files it is going to update are there. You wanna know which files it checks? Don't be lazy - open up an OTA zip file and look at the updater-script file and go through it. There you will see yourself what files need to be stock. Doing it yourself is the only way to learn. Trusting a bunch of xda members who don't know what they are talking about is not the way to learn...
Having said all that, having an unlocked bootloader or having root will in no way impact your ability to receive OR install an OTA update.
Sent from my Galaxy Nexus using Tapatalk
Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed..
Laynee1 said:
Thanks to both of you... The thing is that i really look forward to get 4.0.3 .. I dont want to flash custom roms, i want it all stock .. Im not asking about ETAs or smt.. Im just wishing for 4.0.3 . I heard that a lot of things are settled into 4.0.3.. Lags are gone, bugs are fixed..
Click to expand...
Click to collapse
Unlocking or rooting does not mean you are going to flash custom ROMs...
Sent from my Galaxy Nexus using Tapatalk
The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!
Edit - These things also can affect OTA
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
efrant said:
Unlocking or rooting does not mean you are going to flash custom ROMs...
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ye i know .. I have unlocked bootloader and rooted phone.. But i dont want to flash any custom rom.. I wanna keep it stock.. Just , im saying i cant wait for OTA 4.0.3
jd1001 said:
I have seen this questions posted a number of times from the same user. The only thing that will affect OTA is when you load a custom recovery onto the phone. THAT'S THE ANSWER!
Click to expand...
Click to collapse
..and an incorrect one at that. That is not the only thing.
Having a custom recovery will:
Prevent being able to install the OTA
Not stop the ota notification or being able to download it.
Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).
adrynalyne said:
..and an incorrect one at that. That is not the only thing.
Having a custom recovery will:
Prevent being able to install the OTA
Not stop the ota notification or being able to download it.
Other things that will break your ability to install an OTA, even if you do not have a custom recovery loaded (you can still get notified and download):
Modifying or removing a file that is checked/patched.
Having a different radio installed.
Having a different bootloader installed (possibly).
Having a different kernel installed.
Have modified your build.prop to show a different version.
You can install an ota if you modify the udapter-script if you know what you are doing even in the above scenarios (using a custom recovery).
Click to expand...
Click to collapse
Well thanks for correcting me eventhough I wasn't actually wrong in what I said.
Thanks for adding those bits too I had no idea that other mods could affect OTA although I have read here a few times that the bootloader won't affect OTA. There should be an actual topic on this because with all the information floating around it is confusing.
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
danger-rat said:
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
Click to expand...
Click to collapse
Totally agree! Sometimes it's just frustrating becaus eeveryone thinks they know the right answer when in actual fact people post rubbish that is incorrect. I am guilty of it too but I always go back and edit when I make a false statement.
danger-rat said:
Just a nuance in your choice of words...
Having a custom recovery will not prevent you from installing an OTA, but it will prevent the OTA from installing automatically on its own - you can still manually flash it through your custom recovery...
The second list should be items that "may" affect OTA, rather than "will", since it is dependent on the individual updater-script...
I think we're on the same page though...
Click to expand...
Click to collapse
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.
Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.
This is the sort of uncertainty I am talking about. We should create a new topic and nail it down finally!
Here is a way to nail it down:
If you have modified your system in any way aside from rooting, then your chances of being able to install an ota update are greatly diminished.
adrynalyne said:
Here is a way to nail it down:
If you have modified your system in any way aside from rooting, then your chances of being able to ota are greatly diminished.
Click to expand...
Click to collapse
Ha ha ha sorted!
adrynalyne said:
No. Any signed ota package...the above will affect it. Going by what JBQ said, where every ota should include radios...I'd say I worded it ok.
Also, there is a darn good chance that the custom recovery will stop the install even manually...if it checks the recovery version for an update. That is fairly common. That said, if you remove asserts and know what you are doing, then sure you can flash manually.
Click to expand...
Click to collapse
No OTA update to date has checked the recovery. In fact, every OTA update to date has forced a flash of the stock recovery.
Sent from my Galaxy Nexus using Tapatalk
Here we go again!
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
tn6 said:
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
Click to expand...
Click to collapse
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Worked, I think
MrHaPpY66 said:
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Click to expand...
Click to collapse
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
tn6 said:
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
Click to expand...
Click to collapse
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
No luck
MrHaPpY66 said:
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
Click to expand...
Click to collapse
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
tn6 said:
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
Click to expand...
Click to collapse
for the supersu, you probably need to go update it on the market or disable KNOX
assert failed... getprop("ro.bootloader")
MrHaPpY66 said:
for the supersu, you probably need to go update it on the market or disable KNOX
Click to expand...
Click to collapse
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
tn6 said:
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
Click to expand...
Click to collapse
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
MrHaPpY66 said:
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
Click to expand...
Click to collapse
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
tn6 said:
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
Click to expand...
Click to collapse
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
MrHaPpY66 said:
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
Click to expand...
Click to collapse
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
resolved
tn6 said:
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
Click to expand...
Click to collapse
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
tn6 said:
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
Click to expand...
Click to collapse
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
MrHaPpY66 said:
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
Click to expand...
Click to collapse
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
tn6 said:
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
Click to expand...
Click to collapse
so how's the rom so far? probably going to get it myself.
MrHaPpY66 said:
so how's the rom so far? probably going to get it myself.
Click to expand...
Click to collapse
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
tn6 said:
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
Click to expand...
Click to collapse
so i see it's a lot better than stock. i'll install it as soon as i can and thanks for the link to the rom
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!
Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app
@bkong
Link is bad, clicking it links to a url with "..." in the middle
CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms
Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?
So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.
stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.
Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.
Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"
As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.
Here is the info mrrocketdog
Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.
audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse
KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?
Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop
I'm somewhat certain I already know the answer to this but I just need confirmation.
With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.
So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?
Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.
In case it matters:
Model: SAMSUNG-SM-T807A
Android version: 5.0.2
Baseband version: T807AUCU1BOD4
Kernel version: 3.4.39-4727547
Build number: LRX22G.T807AUCU1BOD4
Device Status: Custom
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.
I've used thus before on other devices and it work well but do your research . Flash at own risk.
Sent from my SM-T800 using Tapatalk
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
ashyx said:
DO NOT flash a custom recovery or kernel on a bootloader locked device!
Unless you want a nice brick.
If you want xposed use Flashfire.
Click to expand...
Click to collapse
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
thorvindr said:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
Click to expand...
Click to collapse
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
ashyx said:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.
Click to expand...
Click to collapse
Having trouble finding documentation on this device's partitions, which are (it seems) not quite the same as most Android devices. To make sure I can recover from (for example) a bad ROM flash, what should I backup? Is flashfire the thing to use for making such a backup?
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
ashyx said:
You can use Flashfire to make a backup, but it's not going to help you in a no boot situation. Be very careful what you flash. Some things such as xposed can leave you in a no boot situation if incorrectly flashed.
My first port of call would have been capturing the ota for backup purposes. Unfortunately that is probably out of the window now you have rooted.
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
If I can boot to recovery, won't I be able to access the flashfire backup on my microsd card? As long as I don't try to flash a custom recovery, shouldn't I always be able to work from that backup? Or does a flashfire backup need the flashfire app to be useable?
thorvindr said:
Or does a flashfire backup need the flashfire app to be useable?
Click to expand...
Click to collapse
You just answered your own question.
ashyx said:
You just answered your own question.
Click to expand...
Click to collapse
No, I didn't. I assume you're telling me the answer to my first question is no?
ashyx said:
There is apparently a way to get kies/smart switch to redownload the firmware, so I'd be going down that root first.
Click to expand...
Click to collapse
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
thorvindr said:
No, I didn't. I assume you're telling me the answer to my first question is no?
Click to expand...
Click to collapse
I quoted your last question. The answer is you need flashfire.
---------- Post added at 07:24 PM ---------- Previous post was at 07:06 PM ----------
thorvindr said:
Anywhere you could point me to figure out how to do that? If I had that, I'd be golden. Hell, I'd share it with the world since for whatever reason nobody seems to have stock ROMs for the 807a.
Click to expand...
Click to collapse
Tbh I don't use kies/smart switch much, but you will find information on it on the net.