Hey guys,
I have looked around for the solution to this but can't find one.
Starting out rooted, I updated my phone to SkyNote 4.3 (not sure if that helps) and still had root for a minute. I went through the process of setting up the phone how I like it, and after a few restarts, the root went away. This has happened twice. I've read posts where people talked about Android 4.3 deleting root but here's where the story gets interesting:
The threads/posts that people are pointing to to fix it is pretty much centered around Chainfire's post on Google+ https://plus.google.com/+Chainfire/posts/Jkuu84odnx6 .
The difference between the similar posts are that Chainfire has updated the version over the months. I have tried flashing that update zip over and over but I still have no root and the SU app is still buried in my system/app folder, which of course I can't delete because I have no root. I guess my questions are does anyone know how to delete this system/app apk for SU without wiping and starting from another ROM or know how to correct it in general?
Thanks you guys for reading.
Search the skynote thread your answer is there its called 1click
Sent from my SAMSUNG-SGH-I317 using Tapatalk
420techcloud said:
Search the skynote thread your answer is there its called 1click
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Thanks, I didn't think about that, but because of my unique situation, I couldn't even get 1click to recognize my phone. So after searching more and more, the answer is exactly what I was doing but a more updated SU zip. It's in the second post of SkyNote 4.3 http://forum.xda-developers.com/showpost.php?p=46798454&postcount=2
That may help another Android 4.3 ROM user
**
I have the exact same issue with my SGH_I317M. I rooted with CF-Root, flashed TWRP, flashed Skynote 4.3, flashed the update, flashed the Rogers modem and flashed the WIFI fix all with ODEN. Everything works. Even WIFI. But I lost Root. I made 2 full backups with TWRP. 1st. right after flashing TWRP still with 4.1.2 ROM and the 2nd after flashing 4.3 and all the patches. When I restore back to 4.1.2 all is good. When I restore to 4.3 Skynote, I loose Root. I tried flashing the SuperUser Update but it fails. Any help would be much appreciated.
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
StevieG_007 said:
I have the exact same issue with my SGH_I317M. I rooted with CF-Root, flashed TWRP, flashed Skynote 4.3, flashed the update, flashed the Rogers modem and flashed the WIFI fix all with ODEN. Everything works. Even WIFI. But I lost Root. I made 2 full backups with TWRP. 1st. right after flashing TWRP still with 4.1.2 ROM and the 2nd after flashing 4.3 and all the patches. When I restore back to 4.1.2 all is good. When I restore to 4.3 Skynote, I loose Root. I tried flashing the SuperUser Update but it fails. Any help would be much appreciated.
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
My last comment should help. When you flash the update, make sure it's the one from the post above. It carries the latest SU. If that doesn't work, I'm not sure what to do, but it worked for me because the SU binaries want to update but it needs the correct one.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Thank you Deon. I was reading this thread yesterday using the XDA app on my mobile for the first time. I downloaded the updated binary from this thread using my mobile. After several install failures I opened propertie for the zip and discovered it was empty. I downloaded the update from the OP through my PC, transferred the file to my SD and now all is good again with my root. CHEERS!
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
Is there any chance that flashing the zip on ChainFire's page will brick your phone?
doran10 said:
Is there any chance that flashing the zip on ChainFire's page will brick your phone?
Click to expand...
Click to collapse
It won't brick your phone its pretty hard to trust me lol I used cf auto root tho
Related
Hi, So about 5 days ago I rooted my Sprint Samsung Galaxy Note II using the video Max Lee made from galaxynote2root(dot)com, and about 36 hours later I get a notification for an OTA update. I kept off updating because I didn't really know what to do. I'm really new to this and there's still a lot I have to learn. Anyway, I ran the update and it restarted my phone and went to the TWRP screen. I restarted the system and it stopped notifying me about the update. And I checked and it says that my system is up to date. And I also checked to see if I still have root with a root checker app I downloaded, and it said I still had root also. So, was the app wrong and I don't have root anymore? And after I updated should I have restored the backup I made when I originally rooted? Also, thanks for any help, I've looked around and couldn't find anyone else with this question.
Your phone automatically downloaded the update and was waiting to be powercycled to install. However it failed to install because it requires stock recovery to install and you dont have it. So your phone boots back up and all is good with no changess.
Sent from my SPH-L900 using xda app-developers app
Reply
xKrisx said:
Your phone automatically downloaded the update and was waiting to be powercycled to install. However it failed to install because it requires stock recovery to install and you dont have it. So your phone boots back up and all is good with no changess.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
So my phone is not updated, but what if I want to update in the future? I just download and run stock recovery?
same issue
Sandelorian said:
So my phone is not updated, but what if I want to update in the future? I just download and run stock recovery?
Click to expand...
Click to collapse
I also have the same issues. I did a back up of my original roms and re installed using twrp . I down load the new update and when its going to restart it goes into to twrp menu. From there i am stuck on what to do.
It failed because you're not on stock recovery. If flashing the stock ota, you need stock recovery.
If you have twrp recovery, read and review this thread:
http://forum.xda-developers.com/showthread.php?t=2148604
thunderwagn said:
It failed because you're not on stock recovery. If flashing the stock ota, you need stock recovery.
If you have twrp recovery, read and review this thread:
http://forum.xda-developers.com/showthread.php?t=2148604
Click to expand...
Click to collapse
Before I rooted my note I made a back up using twrp. Is that not a stock recovery file ?.
Yes and no. That's basically just a backup of the stock rom that's only flashable via twrp since that is the recovery used to create the nand. So yes it is a recovery but only flashable thru twrp.
Sent from my SPH-L900 using xda app-developers app
thunderwagn said:
Yes and no. That's basically just a backup of the stock rom that's only flashable via twrp since that is the recovery used to create the nand. So yes it is a recovery but only flashable thru twrp.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Ok well I did recovered using twrp and it installed and took me back that state before the root. I was thinking that took me back to original state and then update . I did download the update but as it was restarting the twrp home sceen would pop up and not update. So now I have no root or new update. Its funny it was easier to root then to unroot.
The link I posted above would have allowed you to flash new firmware and ma7 through twrp. No unroot reroot required. ..
And like stated, you can't update the stock ota update without stock recovery.
Sent from my SPH-L900 using xda app-developers app
Confused about all the links!
thunderwagn said:
The link I posted above would have allowed you to flash new firmware and ma7 through twrp. No unroot reroot required. ..
And like stated, you can't update the stock ota update without stock recovery.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
There are 6 links on that thread, one for odex and deodex (which I have no idea what it does), and then the 2 links for ma7 one all in one, and one just regular. And then there are another set of 2 links for the kernals, one regular and one modified. I guess what I'm asking is, how do I install these and which ones should I install? I have no idea what any of them do anyway.
How
how do we go about it and what files exactly do we need? why is everyone so vague?
thunderwagn said:
The link I posted above would have allowed you to flash new firmware and ma7 through twrp. No unroot reroot required. ..
And like stated, you can't update the stock ota update without stock recovery.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Links go to mystical places with instructions and posts and helpful comments and answers. All you have to do is click and read and absorb the knowledge.
thunderwagn said:
The link I posted above would have allowed you to flash new firmware and ma7 through twrp. No unroot reroot required. ..
And like stated, you can't update the stock ota update without stock recovery.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I have flashed over 30 SPH-L900 (Note 2) fron Sprint to Boost.
I do everything on CDMA (paid version) 3.9.
Since the L.900VPAMAZ update I can no longer change the esn to Boost because the 16 digit CDMA passcode is no longer the default passcode for the Note 2. The old pascode: 01F2030F5F678FF9 still works for the Galaxy S2 and S3 but is no longer recognized on CDMA Workshop or QXDM.
If anyone knows the new passcode please let me know.
If I find it I will post it so that noone else has this problem.
Thanks!
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Is it supposed to use T999 firmware?
Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium
re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.
tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!
How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done
Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app
You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium
Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app
No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium
Hello,
So, I have the T-Mobile S4, obviously, and I updated to 4.3 using Kies. Well, long story short, after the updated I couldn't use WiFi at all. I ended up using Odin and putting the stock firmware back on, and that fixed everything.
Now, I rooted it using this thread http://forum.xda-developers.com/showthread.php?t=1980683 but, the SuperSU root isn't letting me use OBackup, now. Before, when I had Superuser, it let me use it just fine.
Is there any way to switch from SuperSU to Superuser? I've been reading a few threads but they are all for 4.2.2 and I'm not sure if it'll work on 4.3. I read on one of the threads to use "CWM recovery" and use Odin and that would work, but again, that's 4.2.2.
Any ideas would be great.
Have you tried downloading it from the playstore?
Sent from my SGH-M919 using XDA Premium 4 mobile app
re: root issue
PwnYourFace said:
Hello,
So, I have the T-Mobile S4, obviously, and I updated to 4.3 using Kies. Well, long story short, after the updated I couldn't use WiFi at all. I ended up using Odin and putting the stock firmware back on, and that fixed everything.
Now, I rooted it using this thread http://forum.xda-developers.com/showthread.php?t=1980683 but, the SuperSU root isn't letting me use OBackup, now. Before, when I had Superuser, it let me use it just fine.
Is there any way to switch from SuperSU to Superuser? I've been reading a few threads but they are all for 4.2.2 and I'm not sure if it'll work on 4.3. I read on one of the threads to use "CWM recovery" and use Odin and that would work, but again, that's 4.2.2.
Any ideas would be great.
Click to expand...
Click to collapse
The easiest way to solve the problem is to re-odin flash stock 4.2.2 firmware.
After that download CF-AUTOROOT and odin flash it.
After that you will be fully rooted and all apps which require root will work again.
Here is the direct download link for cf-autoroot: http://download.chainfire.eu/328/CF...jfltetmo-jfltetmo-sghm919.zip?retrieve_file=1
p.s. you might need to re-flash cwm or twrp custom recovery.
Good luck!
Android_Monsters said:
Have you tried downloading it from the playstore?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah; I tried downloading it from the playstore, but all it tells me once I open it is that the it is oudated and needs to update. I hit "Update" and then it crashes the app, and restarts the phone into recovery mode with no prompts except "reboot phone".
And the thing is I do NOT want to go back to 4.2.2. I want to find a way back to Superuser instead of SuperSU.
Misterjunky said:
The easiest way to solve the problem is to re-odin flash stock 4.2.2 firmware.
After that download CF-AUTOROOT and odin flash it.
After that you will be fully rooted and all apps which require root will work again.
Here is the direct download link for cf-autoroot
p.s. you might need to re-flash cwm or twrp custom recovery.
Good luck!
Click to expand...
Click to collapse
The thing is I don't want to go back to 4.2.2. I like 4.3, I just need Superuser instead of SuperSU.
Sent from my SGH-M919 using xda app-developers app
(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Have you tried uninstalling and reinstalling SuperSu?
Since SuperSU was flashed to the device via Odin, it is registered as a system app. The app store only has the open option, and I can't access the app in the system folder without root privileges, which it won't give me, so...
Yeah. Unless there's a script I can run through recovery, that's a dead end.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
there is a zip of SuperSU you can flash from recovery
Sent from my SGH-I747M using Tapatalk
I've tried this. In fact, that was when SuperSU began force-closing. I just need to completely uninstall it and start fresh, I think.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Have you tried the cleanup/unroot options inside supersu settings? Then starting over?
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
pre4speed said:
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
Click to expand...
Click to collapse
Thank you for that. It's always good to have a fallback option.
I'm still wondering though, is there a script I could flash that would completely remove SuperSU / BusyBox / superUSER (CWM) to scratch and allow me to re-flash CF-Autoroot? Barring that, how difficult would it be to code one myself?
FIXED IT.
Apparently, flashing the latest version of SuperSU from the developer's website (1.86) will not work on Android 4.3. I flashed version 1.65 as provided in the original 4.3 Rooting Guide, then updated it in the Play Store followed by a binary update and re-installed BusyBox, and everything is back to running order. Thank you all for your help and advice!
I did a search and couldn't find an answer. I got the OTA (Thanks to my wife, while I still sleeping) I did get it rooted and knox disabled. Don't care about the knox flag because my warranty is already gone. So now my question is do any of the 4.3-4.4 ROMS work (Skynote, Ditto etc)? Can I flash TWRP with goo manager?
Thanks in advance!
Geeve
geeve420 said:
I did a search and couldn't find an answer. I got the OTA (Thanks to my wife, while I still sleeping) I did get it rooted and knox disabled. Don't care about the knox flag because my warranty is already gone. So now my question is do any of the 4.3-4.4 ROMS work (Skynote, Ditto etc)? Can I flash TWRP with goo manager?
Thanks in advance!
Geeve
Click to expand...
Click to collapse
I haven't flashed TWRP thru goo manager but I have thru ODIN. You can get it from here.
http://goo.im/devs/OpenRecovery/t0lteatt
I just got done flashing SKY NOTE 4.3 Edition MJ4-4.3 (AT&T Leak).
I can confirm twrp installs from goomanager as thats how I installed it and successfully flashed an aroma addon (just a mod NOT a rom) with no issues
Did you thank your Developer today?
Thanks to both of you! Getting goo now. Not sure if I am brave enough to flash a ROM yet though till i can see what others have done.
Geeve
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
geeve420 said:
Thanks to both of you! Getting goo now. Not sure if I am brave enough to flash a ROM yet though till i can see what others have done.
Geeve
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I'm not brave enough yet to rom either but I can confirm Xposed installs perfectly and gearbox works just enough that pie controls work.
If you do that don't turn ANYTHING else in gearbox on. Use Wanam to mod out with as its built for the note 2.
Did you thank your Developer today?
Thanks Jspex! Looking into them now
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
4.3 OTA to custom ROM
geeve420 said:
I did a search and couldn't find an answer. I got the OTA (Thanks to my wife, while I still sleeping) I did get it rooted and knox disabled. Don't care about the knox flag because my warranty is already gone. So now my question is do any of the 4.3-4.4 ROMS work (Skynote, Ditto etc)? Can I flash TWRP with goo manager?
Thanks in advance!
Geeve
Click to expand...
Click to collapse
I decided to be the sacrificial lamb and I can confirm that yes definitively you can go from stock 4.3 OTA to a custom 4.3 ROM. I updated to 4.3 OTA (dumb) and just now successfully flashed Ditto 3.1.1.
1. Root 4.3 OTA
2. Flash TWRP
3. Flash custom rom.
4. Run SuperSU
Some additional notes:
Did a dirty flash the first go around. The device didn't boot. Used the pull battery method to get into recovery (probably not necessary but oh well). Reflashed the rom this time using full wipe in AROMA (not in TWRP) and the device booted like a charm (even got an OTA Ditto 3.2 update bonus!).
Additionally AROMA didn't delete my data so I got to keep all my data from 4.3 OTA.
Last note my baseband is still MK6. I guess that's good because Ditto is still on MK5.
Lots of people have done this. What's so scary?
Sent from my GT-N7105 using XDA Premium 4 mobile app
JediMasterX V2 runs great on 4.3 bootloader. If you took the OTA to get to 4.3 then you are ready to go with JediMasterX just download the zip and follow the instructions in the OP.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
4.3 OTA to custom ROM
joe3681 said:
Lots of people have done this. What's so scary?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you knew this information already, it would have been helpful of you to share this information with the group instead of chiming in after the fact.
Just read this but a quick read anywhere around here would've been an answer
Sent from my GT-N7105 using XDA Premium 4 mobile app
Thanks everyone!!
Why it was scary is when I posted there was a lot going on. I hadn't seen where someone had taken the update, then flashed a ROM. I had seen a lot about the leak but not MK6. There were quite a few folks having trouble restoring backups, soft bricking etc. and it was due to the locked down boot loader being hostile to changes. I just didn't want a soft brick and have to use my Infuse till I could get it back up.
As far as what I have read so far, no one has been able to get back to MK6 after downgrading or roming and the backups of the stock MK6 aren't working. The reason I asked is because not much was being said about how ROMs were acting with the locked bootloader. No one was talking about steps to take if you have the MK6 update to ROM.
I have since flashed and I am running Sky Note Air Vaniila now and all is well. Just wanted to see what troubles if any others were having to help keep ducks in a row That way when folks want to ROM they know which ones work with the new Bootloader.
Geeve