I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.
Related
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
gooberdude said:
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
Click to expand...
Click to collapse
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
sashusmom said:
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
Click to expand...
Click to collapse
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
gooberdude said:
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
Click to expand...
Click to collapse
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
sashusmom said:
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
Click to expand...
Click to collapse
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
gooberdude said:
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
Click to expand...
Click to collapse
Great info! Thank you Gooberdude! And I don't Jump .LOL. I just take it one step at a time....Smoothe, then if things are screwed up, I jump around!!! And call out for help!!! And duh- I forgot custom recovery is a problem.
I think I have access to both recoveries. Is that possible? I think I can get into the stock recovery by holding down the correct buttons sequence, but can get into Philz by using my cheat app that I really love, Flapps PowerTool. I'll review what I have and how to do the button sequence to pull up stock recovery and post back.
Thank you for the detailed instructions...Appreciate it. It will probably be awhile before kit kat is put out for our Note 8's anyway.
*********************************************************
Nope. Just Philz custom.
sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?p=50156744
Sent from my SM-N900V using Tapatalk
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
ladd76 said:
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
Click to expand...
Click to collapse
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Larry2999 said:
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Click to expand...
Click to collapse
yes i747 thanks
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
That is actually what i was flashing when I encountered my problem. I was finally able to get one of my old ROM's to install after re-flashing the newest CWM through ODIN and reinstalling my bootloader. I am not sure what the problem was as the stock rom 4.3 shouldnt have downgraded it? Perhaps a random crash which corrupted something. The developer on the stock rom has provided a tar file which I may try this time around. Thank you all for your help.
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
JaedenRuiner said:
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
Click to expand...
Click to collapse
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
lvpre said:
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
Click to expand...
Click to collapse
I eventually found a 4.4.2 full stock ROM and was able to get that over. Of course this wasn't until after some sight suggested a wipe user data could help, so I'm re-building the phone from the base...*sigh* It happens. I'm about due for an upgrade anyway, so I can make due.
Thanks for the response,
J"SD"a'RR
I used factory reset and now my phone is stuck at the tmobile logo. I was rooted before but I removed SuperSU before doing the factory reset. I also tried wiping out the data at recovery mode but I'm still having the same problem. Is there anyone that can help me fix my Note 2?
kevzz01 said:
I used factory reset and now my phone is stuck at the tmobile logo. I was rooted before but I removed SuperSU before doing the factory reset. I also tried wiping out the data at recovery mode but I'm still having the same problem. Is there anyone that can help me fix my Note 2?
Click to expand...
Click to collapse
I hope you didn't wipe system my mistake
Wiping /system is a trivial problem to solve, just flash again and voilà.
What are you trying to accomplish exactly? If you want back to stock, flash the appropriate ROM with Odin, boot to stock recovery, factory reset and call it a day. Unless you've messed up your NV items or done something incorrect with the bootloader, that's pretty much all there is to it.
I wiped out the cache partition at recovery mode and now my phone is working just fine. The reason I factory reset my phone because I want to try if the system will let me update OTA after a reset. Unfortunately it won't let me update still because my phone was rooted. Is there a way to bypass this so I'd be able to update my phone?
Ah! Flashing back to a non-rooted ROM would allow the OTA mechanisms to work normally.
There's inherently a risk for a ROM update to patch something that's been modified in ways it does not expect, such as root on a stock ROM.
In the case of Samsung devices, you could always Odin flash back to stock, or a pre-rooted stock image.
Darkshado said:
Ah! Flashing back to a non-rooted ROM would allow the OTA mechanisms to work normally.
There's inherently a risk for a ROM update to patch something that's been modified in ways it does not expect, such as root on a stock ROM.
In the case of Samsung devices, you could always Odin flash back to stock, or a pre-rooted stock image.
Click to expand...
Click to collapse
Well I've always been on stock. I just rooted my phone before for some apps and that's it. I never use any custom rom. Im still at stock but wont let me update still
Consider yourself as "custom" the moment you change anything on your /system partition, that includes root.
Samsung ROMs have this check that's displayed somewhere in settings, where your ROM will say if it thinks it's been modified. If so, OTA updates will be disabled.
Factory reset alone won't completely unroot you. You must unroot, then factory reset.
At this point, since you just want a stock rooted ROM and have already factory reset, you could flash the latest pre-rooted ROM with Odin. Will probably be simpler than prodding the phone into getting the OTA.
Hi All,
I have been having some issue with one of my box, it is rooted running stock version 51.1.0.1 .
i have completed the following steps of the rooting process.
1) block updates on router
2) rooted (installed towleroot, supersu, busybox)
3) disabled update on AFTV box via adb command
4) Unlock partial bootloader
5) installed latest CWM at this point fire tv restarts but does not boot up in to CWM recovery.
I can get into CWM via Alt + prntscr + i using my keyboard. i did the wipe data/factory reset thru CWM and it clean up everything i rooted again installed CWM and it still wont boot up in CWM so may the firmware is corrupt?
What should i do? Should just flash pre roted rbox ROM and installed Rbox boot menu and see if i can get in CWM or should i wipe everything from AFTV and start again.
How do i wipe everything out using CWM? I read a lot tread on xda forms but didn't see a detail guide, i would appreciate if someone could give me all the baby step in exact order i should perform and if you could use the same terminology that is used in CWM menu that would be great, please.
Please note i have rooted at least 8 box before (updates blocked, rooted, bootloader unlock, install cwm, installed pre-rooted ROM and Rbox manu) so i am familiar with the process but one can always mess up.
Thank you
You're approaching this in a differnt angle than I'm used to--is there a reason you use stock firmware? With custom recovery, I'd venture to say a factory reset will do what you want it to and performing it will give you a clean slate and though updates will try to download they won't install.
I do this but I run rbox firmware...
1. Reboot recovery
2. Factory reset in cwm
3. Confirm it (this will wipe user data)
4. Reboot system
This should get you back to the registration page. You'll lose EVERYTHING except su. First thing I do is pm disable updates again. Once that's done you should be good tonset it all up--install busybox, all your apps.
I just worry because I use custom ROMs and never did this with stock. On your average android device keeping stock firmware wouldn't bother me but aftv is a little different since there's no doubt they don't want you rooted with custom recovery. I'd go to the dev threads and ask questions or flash prerooted ROMs. You might want to update incrementally as some have reported issues when they skip updates, not critical but it might be in your best interest.
And of course when I refer to updates I mean preroot not stock.
KLit75 said:
You're approaching this in a differnt angle than I'm used to--is there a reason you use stock firmware? With custom recovery, I'd venture to say a factory reset will do what you want it to and performing it will give you a clean slate and though updates will try to download they won't install.
I do this but I run rbox firmware...
1. Reboot recovery
2. Factory reset in cwm
3. Confirm it (this will wipe user data)
4. Reboot system
This should get you back to the registration page. You'll lose EVERYTHING except su. First thing I do is pm disable updates again. Once that's done you should be good tonset it all up--install busybox, all your apps.
I just worry because I use custom ROMs and never did this with stock. On your average android device keeping stock firmware wouldn't bother me but aftv is a little different since there's no doubt they don't want you rooted with custom recovery. I'd go to the dev threads and ask questions or flash prerooted ROMs. You might want to update incrementally as some have reported issues when they skip updates, not critical but it might be in your best interest.
And of course when I refer to updates I mean preroot not stock.
Click to expand...
Click to collapse
Hi,
I did the factory reset from CWM i forgot to mentioned this on intial post, sorry about that. It went thru the whole process, i re rooted and everything but again after installing CWM aftv did not boot in CWM so i thought maybe i should wipe everything out and start over instale fresh stock firmware.
Maybe the fireware is corrupted or the partition. I tried to down grade and upgrade to stock version but AFTV wouldn't installed the updates.
For me go get in CWM using ALT+PRINT SYS+I option is really pain full, after trying if for a 3 days and spending at least 2 hours each day i was able to get in so i thought start from scratch would might work.
thank you
ashsha7877 said:
Hi,
I did the factory reset from CWM i forgot to mentioned this on intial post, sorry about that. It went thru the whole process, i re rooted and everything but again after installing CWM aftv did not boot in CWM so i thought maybe i should wipe everything out and start over instale fresh stock firmware.
Maybe the fireware is corrupted or the partition. I tried to down grade and upgrade to stock version but AFTV wouldn't installed the updates.
For me go get in CWM using ALT+PRINT SYS+I option is really pain full, after trying if for a 3 days and spending at least 2 hours each day i was able to get in so i thought start from scratch would might work.
thank you
Click to expand...
Click to collapse
If I'm hearing you correctly I think I know your problem. You can't flash stock firmware with cwm. Rbox has protections in place thatbwont letbthis happen and for good reason--doing so could brick your device. You need the preroot ROMs. Follow aftvnews starters guide because I only had to do this once and I'm not certain I remember exactly. I think there's a certain version you should start with and some users find its better to update incrementally.