Related
OK, so I have the Galaxy Tab 2 7.0 (I couldn't find a 7.0 section here, so I picked the next closest) it's not through any phone company. I tried to root, but it failed, so I did a restore bluh bluh bluh. Once I restored I went to update to the latest for my device. It said my system has been modified so there is no update (something along those lines). What do I do to fix this? This is my first android device and I am trying to learn the ropes. I hope I didn't mess this up too badly. Thanks for the help.
I do believe it has Ice cream sandwich on it.
No worries, just register at Sammobile & download a fresh new stock firmware, maybe even the latest one, from there. Use ODIN to flash it and you are good to go again.
wwe9112 said:
OK, so I have the Galaxy Tab 2 7.0 (I couldn't find a 7.0 section here, so I picked the next closest) it's not through any phone company. I tried to root, but it failed, so I did a restore bluh bluh bluh. Once I restored I went to update to the latest for my device. It said my system has been modified so there is no update (something along those lines). What do I do to fix this? This is my first android device and I am trying to learn the ropes. I hope I didn't mess this up too badly. Thanks for the help.
I do believe it has Ice cream sandwich on it.
Click to expand...
Click to collapse
jaydaman said:
No worries, just register at Sammobile & download a fresh new stock firmware, maybe even the latest one, from there. Use ODIN to flash it and you are good to go again.
Click to expand...
Click to collapse
do exactly what Jaydaman says, but check on your download screen that you custom counter has not increased, why did you restore bluh bluh bluh if the root failed? if your counter has increased you will need to run the triangleaway app to reset your counter, this requires root however!
squ89r97 said:
do exactly what Jaydaman says, but check on your download screen that you custom counter has not increased, why did you restore bluh bluh bluh if the root failed? if your counter has increased you will need to run the triangleaway app to reset your counter, this requires root however!
Click to expand...
Click to collapse
How do I check that counter thing? Sorry I am new to this. I've only ever jailbroken my Ipod lol. But I restored it because that's how I reset my iPod when a Jailbreak failed once . Bad Idea. Thanks for all the help. I appreciate it.
If the counter did go up, and since the root is failed, how would I root it to reset the counter-thing?
You can checkl the counter IN download mode. It will show as Something Something counts = X
squ89r97 said:
do exactly what Jaydaman says, but check on your download screen that you custom counter has not increased, why did you restore bluh bluh bluh if the root failed? if your counter has increased you will need to run the triangleaway app to reset your counter, this requires root however!
Click to expand...
Click to collapse
As long as it says official firmware and not custom binary, he should be able to update. My counter was at like 13 last time i did an ota update, but that was a couple months ago. I just flashed the official firmware and updated, no triangle away.
Sent from my GT-P3110 using xda app-developers app
I got it to work. I rooted it. I jsut reran everything. I wouldn't mind having a different kernal to check out what all android has to offer.
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
pedrohell said:
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
Click to expand...
Click to collapse
Welcome to the club. Take a look at all the sections for the tablet and make sure you read the stickies too.
Method #2 and youl be good to go.
http://forum.xda-developers.com/showthread.php?t=1831152
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
Let me ask you this, why no flashing? As far as I know it's either Odin or flash. You need to get a custom recovery on it in order to root.
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Also with the s2 the recovery and kernel are in one. This is not.
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
No problem, but it don't get any easier than odin or recovery.
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
There was an Exynos exploit method but Samsung patched the security hole a few updates ago.
The method in the link that was posted does alter your flash count and that can be correct but you are the owner of the device and if you are not comfortable flashing you tablet I wouldn't.
I have flashed mine and tried a few rom's but I always ended up resetting my flash counter and going back to stock.
Folder mount works great and that was the reason I rooted in the first place but you can store your files on the ext drive and transfer them back and forth manually but I found with my fast wifi I'm better off re-downloading the data along with "Helium - App Sync and Backup" to backup and restore my data and you do not need root, only draw back is that you have to have a computer connection for backup and restore to work.
.
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
I don't think you read that right. You're not flashing a ROM, just a custom recovery through ODIN, then a root app. It's actually very simple. (Any simpler and I would be concerned about rogue app exploits)
Fyi: I'm also new to Samsung devices and bought my tablet this week. Rooted it this morning by following the stickies, but sticking with the stock ROM for now. I'm more than happy with the tablet so far.
Sent from my GT-N8013 using xda app-developers app
pedrohell said:
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
Click to expand...
Click to collapse
There is no flashing a rom with method 2. You Odin the custom recovery then you have to flash the superuser into the system. You need superuser to get root and Odin is the easiest way.
Trust me we have all been in your shoes about being nervous, I've been doing this a long time and this method is really easy.
You can also use this method - http://forum.xda-developers.com/showthread.php?t=1957002
It does require ODIN but as has been stated this is the norm. You are not replacing any kernels or flashing another rom, you are just adding the root components. Using this method also leaves stock recovery intact...
If you woory about flash counter then run triangleaway after to reset the flash counter and recoveries....
I found doing this, doing a factory reset from settings then reflashing the Stock rom using Mobile ODIN pro gave me a stock standard, but rooted, rom with all statuses "Official" and 0 flash count....
A lot of work I know but then worthwhile things generally require it...
Ok, I followed the Method 2 made everything like on video, after pressing Power+Volume Up, I entered on STOCK Recovery, not the CWM,even so, I apply the .zip and I get:
MANUAL MODE
--Appling Multi-CSC....
Applied the CSC-code:LUX
Successfully applied multi-CSC.
--Install /sdcard....
Finding update package....
Opening update package....
Verifying update package.....
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:signature verification failed
I also retryed and turned off auto-reboot in Odin before starting the process but I get the same thing, now what should I do?
Its not rootable?
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
I see that I'm probably too late now to answer the OP.
But maybe others can be interested.
I find that the easiest way to root (without odin and without installing a custom recovery) is Framaroot.
It uses some Exynos exploits, and has been also recently updated by the developer to counteract Samsung's patches.
It may work or it may not work on some devices and with some of the more recent firmware.
In any case giving it a try doesn't cost anything. It's just an app.
If it works the app can also be used to temporarily remove the root.
For me it worked with Firmware N8000XXCLL3 and I know that it works with some more recent fw too.
Furthermore it doesn't change the counter and even the Devices Status remains "Official". Well, actually the devices status may change to "Custom" after few days with the tablet on, but it returns Official after a simple reboot.
pedrohell said:
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
Click to expand...
Click to collapse
Awesome to hear! I ran into the same thing you did, forgot to go straight to recovery from odin.
Enjoy!
Stuck
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
What were your options on the page right before that? What option did you select to initiate that?
Maybe try using the files from here instead:
http://droidviews.com/2013/root-and...ung-galaxy-note-10-1-n8000-n8010-n8013-n8020/
bigtoysrock said:
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
Click to expand...
Click to collapse
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
brix696 said:
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
Click to expand...
Click to collapse
I would use the touch cwm, and what rom are you trying to install?
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse
TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?
dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.
nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM
back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...
nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?
I'm ready to root but virtually every email I see identifies problems rooting with the latest OTA updates. Even the experts appear to have a problem. Is there a reliable method that does not involve extensive after the fact troubleshooting.
Thanks,
Keith
stedmakr said:
I'm ready to root but virtually every email I see identifies problems rooting with the latest OTA updates. Even the experts appear to have a problem. Is there a reliable method that does not involve extensive after the fact troubleshooting.
Thanks,
Keith
Click to expand...
Click to collapse
You could use my rom or one of the others without any issue or work really.
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
Gatsrom said:
You could use my rom or one of the others without any issue or work really.
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
Click to expand...
Click to collapse
Gatsrom thanks for responding. I gave it a shot and don't know where I am at. I am not rooted. I downloaded and installed Odin and following all the precautions I could find I downloaded TWRP and went through the installation process. Odin showed RESET then PASS. I did this twice and it passed both times. I also tripped knox (which I expected to do). When I boot into recovery there is no sign of TWRP. I go to the standard system recovery.
Did I need to be rooted before TWRP will work? If not, could you point me in the right direction.
Thanks,
Keith
stedmakr said:
Gatsrom thanks for responding. I gave it a shot and don't know where I am at. I am not rooted. I downloaded and installed Odin and following all the precautions I could find I downloaded TWRP and went through the installation process. Odin showed RESET then PASS. I did this twice and it passed both times. I also tripped knox (which I expected to do). When I boot into recovery there is no sign of TWRP. I go to the standard system recovery.
Did I need to be rooted before TWRP will work? If not, could you point me in the right direction.
Thanks,
Keith
Click to expand...
Click to collapse
Hmm let's see what we can do. If you are booting into stock recovery it's not flashing the recovery. You grabbed the recovery for the v1awifi right? https://goo.im/devs/OpenRecovery/v1awifi/openrecovery-twrp-2.8.0.0-v1awifi.img.tar
You put the tar file in the pda slot? It says successful (1/1) in the info/log window at the bottom?
Gatsrom said:
Hmm let's see what we can do. If you are booting into stock recovery it's not flashing the recovery. You grabbed the recovery for the v1awifi right?
You put the tar file in the pda slot? It says successful (1/1) in the info/log window at the bottom?
Click to expand...
Click to collapse
Gatstrom, I believe yes to all of the above. I attached a file that shows the Odin screen (didn't take - screen readout below). The successful line says (succeed 1 /0 failed) The recovery file is correct. Odin 3.09 does not say Note pro. I have also tried Odin 3.09 from a different source with the same result. The other thing I can think of is after flashing and I take the usb cord from the phone my steps are to turn off the phone and turn it on to recovery with the three finger steps. Is their anything else I need to do at this point. Should I be in TWRP now? I find myself in stock recovery system and it gives me I think 5 options. I am just rebooting. Should I be using one of the other options.
I unzipped Odin with 7z. I am using an original samsung USB cable connected directly to the computer and I turned off antivirus before flashing. There is no indication that Kies is operating any services in the background. I also downloaded he latest drivers
Pass
02:02
Auto reboot and f.reset time checked
From message block
added
recovery.img
Nand Write Start!
RQT_CLOSE !!
RES OK!!
Removed!!
Remain Port.... 0
All threads completed. (Succeed 1 / failed 0)
Binary size 8.2mb
Thanks,
Keith
I got it to work. On the TWRP thread at original development forum on page 48 or 49 there was someone with the exact same problem. Bigbiff told the user to uncheck auto reboot in odin and then to boot directly into recovery. I did and it worked. I was unaware that you could root directly from TWRP and a quick stop at the play store. I then loaded your debloated rom and I'll see how it goes once everything updates.
I am so F$%^King excited. I have spent scores of hours attempting to get this to work.
Thanks for all of your help (it helped)
Keith
Ya that was my next suggestion to not reboot and go into twrp directly. Let me know how the rom works. If you have any questions/bugs throw them in the rom thread. I'll see it quicker and it keeps problems and solutions centralized.
I would say give the xposed framework a shot. I put a list of the ones I use. They are incredibly useful.
I have an AT&T GS6 (SM-G920A). The new update isn't working for me.
I rooted it temporarily using PingPing root, since I wanted to use AdAway to modify the hosts file, and PingPong doesn't trigger the KNOX flash counter.
Anyway, I tried unrooting using SuperSU, but it just got stuck at "uninstalling", so I used root browser to manually delete SU and the SuperSU apk file. After that, I did a full wipe.
Anyway, it still isn't letting me update with the latest version. It says it is unrooted and KNOX is still at 0x0. However, in the Odin screen, one of the options DOES say custom. (the binary one is Samsung Official, but the other is Custom.)
So after looking around, I found out that flashing a stock MD5 will not trigger KNOX, so I figured I would try that. I found a stock GS6 MD5 and downloaded, but Odin said it failed the hash check. This was the same error I got when trying to update. (dafuq?)
ANyone know how to get my phone back enough to update? I might leave it that way until I decide if samsung pay is work giving up custom roms.
In the ping pong thread is mentioned that you have to Odin back to stock, let the OTA update run, and then re-root using ping pong again.
Sent from my SAMSUNG-SM-G920A using Tapatalk
PMDColeslaw said:
In the ping pong thread is mentioned that you have to Odin back to stock, let the OTA update run, and then re-root using ping pong again.
Click to expand...
Click to collapse
Yeah, I tried that, hence this line:
"So after looking around, I found out that flashing a stock MD5 will not trigger KNOX, so I figured I would try that. I found a stock GS6 MD5 and downloaded, but Odin said it failed the hash check."
Most places didn't seem to offer a stock ATT ROM anyway. I finally found one, but it seemed to say "REV_02" at the end. I gave it a try but it failed the hash check.
Thanks for the reply, though.:good:
OK, I was able to get the System back to official using the ROM I found.
Now it starts updating properly in that it gets to the loading bar.
However, it fails at about 25%. According to the log, I'm getting Status 7.
Jonathanese said:
OK, I was able to get the System back to official using the ROM I found.
Now it starts updating properly in that it gets to the loading bar.
However, it fails at about 25%. According to the log, I'm getting Status 7.
Click to expand...
Click to collapse
Try downloading the latest firmware from sammobile , flash it by Odin , then re-root with pingpong again , no need for OTA if the new firmware is there for donwload .
OK, I found out the problem. There are 4 files INSIDE the file I downloaded. I had to flash all 4 of them (Bootloader, AP, CSC, and something else). From there it worked just fine! I consider this solved! No knox trip, either!:good:
For future reference, I'll see if I can post a link to the ROM I used.
Found it in the OP here.
Or if the direct link stays up, try this direct link.
Remember to flash all 4 files using Odin (I would post a link but they keep changing). I used 3.10.