Help: stuck in bootloop after trying to unroot - EVO 4G Q&A, Help & Troubleshooting

I have screen problems so have to take phone back.
I tried running the first file from here:
http://shipped-roms.com/shipped/Supersonic/
it ended with an error along the lines of "ROM manager cannot update your phone."
It then went into bootloop. I was able to get back into Clockwork recovery, re-flasjed a previous ROM, but it is still in boot loop.
I did clear user data and cache... help...

OK, *phew* I was able to boot by doing a fresh restore off a ROM image on the second try... now, before I do anything I will regret, what is the proper way to unroot, given my first effort led to such a shameful rout.

http://forum.xda-developers.com/showthread.php?t=715176&highlight=unroot
http://forum.xda-developers.com/showthread.php?t=721843&highlight=unroot
Check these out. I haven't had to undergo the process personally, but I scanned through these before, just in case. Hope it helps

Thank you for the reply, I will try the first method although I am a little gun shy right now so I will wait until Friday so as not risk lacking a working during a workday.

I actually unrooted before I did the OTA that came late last month. It's not that hard and it can be done with a simple executible file that ends in .RUU.
But yeah, the first link explains it well.

Related

[Q] Unable to re-root MT3GS

Hope that someone can shed some light on this for me...
Wednesday evening, I decided to root my brand new MyTouch 3G Slide. I had barely had it a week and I couldn't ignore the itch. So I did my research and finally settled on the instructions set on the Cyanogenmod Wiki page using the Exploid method. After a couple of blunders, I got it to work and installed CyanogenMod 6.1.1 for the Slide. It worked great for the most part. There were a couple of issues that I had that ended up being deal breakers (Unable to install Flash, dock at the bottom of screen randomly disappeared, etc.). I decided I'd had my fun and wanted to go back to a stock image. Stupid me, I didn't do a Nandroid back up first. Luckily, I found a near stock image in with Champion build. After 2 long hours, and thinking that I had bricked my phone, I got it back on and everything seems to be working normally. I found out this afternoon at work that this flashed the Champion build but actually put the radio version into a lower version than was current. So I started looking into doing the manual update, which led me to finding the 1.35.531 OTA ROM from CR. Since I was at work, I couldn't attempt the update.
I've now been at this over an hour again and cannot get it to reroot to install this image. I followed the exploid rooting instructions again and everything seemed to be working fine until I load into the bootloader. It looks for the ESPRIMG.zip but doesn't find it, though I've verified 3 times that it is there on the root of the SD Card. So I went into Android System Recovery and attempted the Update.zip, to which I received the "E:failed to verify whole-file signature" and the install aborts.
I've searched and searched and followed all sorts of directions to correct the issue. Maybe one of the experts can tell me what I'm doing wrong
Valorendk said:
Hope that someone can shed some light on this for me...
Wednesday evening, I decided to root my brand new MyTouch 3G Slide. I had barely had it a week and I couldn't ignore the itch. So I did my research and finally settled on the instructions set on the Cyanogenmod Wiki page using the Exploid method. After a couple of blunders, I got it to work and installed CyanogenMod 6.1.1 for the Slide. It worked great for the most part. There were a couple of issues that I had that ended up being deal breakers (Unable to install Flash, dock at the bottom of screen randomly disappeared, etc.). I decided I'd had my fun and wanted to go back to a stock image. Stupid me, I didn't do a Nandroid back up first. Luckily, I found a near stock image in with Champion build. After 2 long hours, and thinking that I had bricked my phone, I got it back on and everything seems to be working normally. I found out this afternoon at work that this flashed the Champion build but actually put the radio version into a lower version than was current. So I started looking into doing the manual update, which led me to finding the 1.35.531 OTA ROM from CR. Since I was at work, I couldn't attempt the update.
I've now been at this over an hour again and cannot get it to reroot to install this image. I followed the exploid rooting instructions again and everything seemed to be working fine until I load into the bootloader. It looks for the ESPRIMG.zip but doesn't find it, though I've verified 3 times that it is there on the root of the SD Card. So I went into Android System Recovery and attempted the Update.zip, to which I received the "E:failed to verify whole-file signature" and the install aborts.
I've searched and searched and followed all sorts of directions to correct the issue. Maybe one of the experts can tell me what I'm doing wrong
Click to expand...
Click to collapse
I can't think of why the bootloader wouldn't see the esprimg file unless it wasn't on the root of your sd card. But you should follow the new rooting guide in the android development section for this phone by nbetcher, supposed to be much easier to follow. Try that, although that ALSO requires esprimg.zip. So yeah is ESPRIMG.zip on the root of your sd card? It has to be there.
Sent from my T-Mobile myTouch 3G Slide
I never got around to doing this again. I was without my new smart phone for days while I wiped, rooted, installed, rinsed, repeated. I stuck with the Champion build and have moved on from the root. I know I had that esprimg.zip on the root of the drive but it wouldn't read so I just gave up. I'm pretty happy with the stock interface. Thanks for the help though MusicMan.

[Q] Well, I've bricked my Sprint OG. Could use some help...

So I did something I knew better than to do, but after weeks of dealing with it, got annoyed and accepted it. There was a system update that came through a few weeks ago, pops up every ten minutes or so. Rooted and Freegee'd so I figured it was not in my best interest to accept this update. I tried to freeze it with Titanium, but that program for some reason constantly failed to load things, froze up, etc., even after reinstalls. Well, today, I decided to be dumb and said hell, let's see what happens. Hit "install now", phone rebooted into CWM, CWM asks if I wanted to accept this update, I said yes, gave me the broken android with the red triangle with a ! in the middle and said it failed. I selected reboot system now, it will only boot into recovery. I have two backups, neither of which CWM will load...ridiculous. Says MD5 mismatch, no idea what that means. Regardless, backups don't work. So, my question now is can I simply do a data wipe/factory reset or must I do an LGNPST? Also, will a data wipe/factory reset remove root and CWM? Because currently I have no reason for my phone to be rooted and unlocked, and CWM doesn't seem to function correctly anyways for me. I need a quick response please!
Look in general, there is a thread on how to recover from such things.
Cool. I'll see if I can figure it out. Thanks Chad.
Unbricked. It removed root and unlock, which from what I was reading, I didn't think it would do. Is it safe to update now? lol.

What the What?!

Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )

[Q] Whats causing this problem?

Sup, so in my last post I was told to read some info, get a better idea of what to do and how to move forward.. Problem being is, Where do I start? There is no actual help for the situation I am stuck in.
Im on a unlocked M8, no carrier version. I rooted the device and installed TWRP. This restored my Kit Kat 4.4.4 to 4.4.2. This is the google play edition, I believe.
Here is the Situation.
followed a youtube guide by "unlockr" which seemed to cover every aspect. after the root and with TWRP, phone bugged me to do a update to 4.4.4, I did, went back to TWRP, booted to system and got stuck in a loop.
I was recommended to delete the OTA file to stop this.. I did. Didnt stop the loop, bizarre...
Along this process, In fast boot menu my phone had a *tampered* label up top- further research this is nothing to worry about.
but without the OTA file, and just entering fastboot>twrp>system, this is where the boot loop still persists. S-On is back, no longer S-Off.
I've done my research etc and aware what needs to be done, but unsure on the safe methodology to reach this point. A friend who is helping me has better knowledge for SSung Galaxies and struggling to help me along.
He detailed I need to get back to 4.4.4(to stop this pissing 'you need to update your phone' pop up) - create a back up of this, then root and then from this point I can install custom roms ETC.
How do I install this, set up phone to a point Im happy, make the back up without the boot loop stopping me from doing so, then continue with experimentation etc...?
Like I said, Ive read plenty, but it doesn't help the situation I am in, so please, please don't just tell me to go educate my self, when there's no resources to help me with my problem. I still dont know which OTA is safe for me to use, or how to inject this without the bootloop ruining my life.. again.
P.S in work, Will reply when possible.
Im on a unlocked M8, no carrier version. I rooted the device and installed TWRP. This restored my Kit Kat 4.4.4 to 4.4.2. This is the google play edition, I believe. As far as i know there is no way your android version would downgrade by flashing a recovery. Most likely is you were and still are 4.4.2
Here is the Situation.
followed a youtube guide by "unlockr" which seemed to cover every aspect. after the root and with TWRP, phone bugged me to do a update to 4.4.4, I did, went back to TWRP, booted to system and got stuck in a loop. Golden rule - Never Never Never take an OTA when running a custom recovery.
I was recommended to delete the OTA file to stop this.. I did. Didnt stop the loop, bizarre...
Along this process, In fast boot menu my phone had a *tampered* label up top- further research this is nothing to worry about.
but without the OTA file, and just entering fastboot>twrp>system, this is where the boot loop still persists. S-On is back, no longer S-Off. Also pretty sure flashing a recovery can't turn S-ON and you have to be 100% stock for that anyway (I believe) which you are not. How did you get S-OFF in the first place??
I've done my research etc and aware what needs to be done, but unsure on the safe methodology to reach this point. A friend who is helping me has better knowledge for SSung Galaxies and struggling to help me along. Samsung are completely different. I know as I've rooted my GF's and it was painful
He detailed I need to get back to 4.4.4(to stop this pissing 'you need to update your phone' pop up) - create a back up of this, then root and then from this point I can install custom roms ETC.
How do I install this, set up phone to a point Im happy, make the back up without the boot loop stopping me from doing so, then continue with experimentation etc...?
Like I said, Ive read plenty, but it doesn't help the situation I am in, so please, please don't just tell me to go educate my self, when there's no resources to help me with my problem. I still dont know which OTA is safe for me to use, or how to inject this without the bootloop ruining my life.. again No OTA's are safe to use with a custom recovery.
There are a couple of things I'm not sure on, I think you have done the following so far
1. Unlocked using HTC dev
2. Rooted using the tool kit
3. Tried to install the OTA
4. Got a boot Loop
Is that correct?
Can you get into TWRP recovery?
Also you have a thread about this open already. Either delete that thread or this one.
As far as i know there is no way your android version would downgrade by flashing a recovery. Most likely is you were and still are 4.4.2 - Nope, Upon taking out the box on day 1, there was an update required and did it straight away.. then a smaller one. Guessing thats 4.4.3 and 4.4.4.
Golden rule - Never Never Never take an OTA when running a custom recovery - hahah, Ive established this now >.< I originally saw rooting as a "inject" sort of methodology.. before the os booted.. Thats not the case!
Also pretty sure flashing a recovery can't turn S-ON and you have to be 100% stock for that anyway (I believe) which you are not. How did you get S-OFF in the first place?? - I rooted following "TheUnlockr" video guide, It did say S-OFF, Bootloop and **** up with the OTA removed this I think. This was using the Hasoon2000 AIO tool.
Samsung are completely different. I know as I've rooted my GF's and it was painful - Good to know, I wont take too much advice from him, he did highlight a tool called Odin. Would that be any benefit to myself?
1. Unlocked using HTC dev
2. Rooted using the tool kit
3. Tried to install the OTA
4. Got a boot Loop
Basically.. yes.
Yes I can get into TWRP, but as I say, when I boot to system, this is where the loop starts.. phone starts up normally.. gives me 1min before restarting over and over.
I am sorry, Im aware that another topic is open. I did try to close it, dont have permissions on account. havent used forums in a few years and its all over the shop now hahaha.
Sorry for late reply.. hectic couple of days.

[Q] Really need your expert help guys! SM-T800

Alright, I'll lay out what happened. My end goal is to just have a rooted tab, but at this point, I'd be willing to just have it back to how it was. Preferably without losing everything on it.
-Looked around on how to root it, and found the following, and use the files it suggested.
- Seemed easy enough, and I had rooted/installed android on my old HP Touchpad, so I dl'd the files, and gave it a shot.
- Couldn't get CWM recovery on it, so I ran verify root and it said it wasn't rooted, even though I has SuperSU. It would even ask to grant apps permission, and I'd grant it.
- I opened SuperSU, and it'd say it needed to update the binaries, but would fail on normal, so I dl'd the newest zip, booted into recovery, and tried to load it like that, but 2 lines would come up red. I think they were just verifying signatures, so I ignored it and let it reboot.
- I opened SuperSU again, and it still said it needed the binaries updated, failed on normal attempt. I decided to try again from scratch, unrooting it and all. So, I went into the SuperSU settings and did it's thing, but it still had the version of SuperSU that initially was on it (it wouldn't let me past the "update binaries" prompt).
- I found that I needed to use Odin to flash a stock firmware back on it, and dl'd both version here.
- I tried the first one, and then it wouldn't get past the "Samsung" screen (the 2nd one with just the word Samsung, if it matters).
- I can still boot into Odin and Recovery, thankfully, so I tried the 2nd stock firmware. Same issue.
- Finally, I tried the rooting process again, hoping to get it to boot, same thing. So, I tried the 2nd stock firmware again, praying something good would happen, and still stuck on the Samsung screen.
I can still boot into Odin and recovery, but I have no idea where to go from here. I still want it rooted if possible, and I'd prefer not to lose all my games and such. I just found "[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705" thread here, but I didn't want to try it just yet.
It's a SM-T800. I had Lollipop on it. Don't know much else to add, but please help!
Thanks all.
Cypher5235 said:
Alright, I'll lay out what happened. My end goal is to just have a rooted tab, but at this point, I'd be willing to just have it back to how it was. Preferably without losing everything on it.
-Looked around on how to root it, and found the following, and use the files it suggested.
- Seemed easy enough, and I had rooted/installed android on my old HP Touchpad, so I dl'd the files, and gave it a shot.
- Couldn't get CWM recovery on it, so I ran verify root and it said it wasn't rooted, even though I has SuperSU. It would even ask to grant apps permission, and I'd grant it.
- I opened SuperSU, and it'd say it needed to update the binaries, but would fail on normal, so I dl'd the newest zip, booted into recovery, and tried to load it like that, but 2 lines would come up red. I think they were just verifying signatures, so I ignored it and let it reboot.
- I opened SuperSU again, and it still said it needed the binaries updated, failed on normal attempt. I decided to try again from scratch, unrooting it and all. So, I went into the SuperSU settings and did it's thing, but it still had the version of SuperSU that initially was on it (it wouldn't let me past the "update binaries" prompt).
- I found that I needed to use Odin to flash a stock firmware back on it, and dl'd both version here.
- I tried the first one, and then it wouldn't get past the "Samsung" screen (the 2nd one with just the word Samsung, if it matters).
- I can still boot into Odin and Recovery, thankfully, so I tried the 2nd stock firmware. Same issue.
- Finally, I tried the rooting process again, hoping to get it to boot, same thing. So, I tried the 2nd stock firmware again, praying something good would happen, and still stuck on the Samsung screen.
I can still boot into Odin and recovery, but I have no idea where to go from here. I still want it rooted if possible, and I'd prefer not to lose all my games and such. I just found "[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705" thread here, but I didn't want to try it just yet.
It's a SM-T800. I had Lollipop on it. Don't know much else to add, but please help!
Thanks all.
Click to expand...
Click to collapse
Well... you said you just updated to lollipop, but in order to not stay stuck at splash screen, you have to factory reset. I saw that you don't want to lose your games and such so you probably only have one option. That option is to flash twrp and make a nandroid of your data. Simply boot into download mode, download the twrp .tar http://twrp.me/devices/samsunggalaxytabs105.html
And now go into Odin, untick autoreboot, now hit the pda/AP button and pick the twrp tar. Hit start and let it do its thing. Now after its done flashing, your gonna have to force reboot. Simply hold power+volume up and down+home button all at the same time. Wait a bit and when the screen turns black, quickly press power+volume up+ home buttons all at the same time and it should boot into twrp.
Now in twrp, hit backup and hit backup data. Hopefully that should save your apps installed. Now after its done, go into wipe and silde factory reset. It should remove installed apps from Google play store and it won't remove pictures and such. It just removes the apps you installed. Then now reboot and wait....
Hopefully this helped
-DUHA
As said you will have to factory reset, this will wipe data and cache.
You can use the link you posted above to install TWRP and root.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
Lollipop changes the data partition so even if you back it up and then restore it with twrp In kitkat it likely won't boot afterwards.
All you can do is wipe it and take the hit.
Alright, I have TWRP running. The size of my "data" is just over 16 gig, and my space on the sdcard is 14.9 gig, so I've been trying to delete data to knock it down. I still have 1.3 gig to go. Everything I'm deleting, in the data folder, is barely making an impact.
I see what you're saying that I probably won't be able to restore it and have it work, but I still will try. I can always factory reset it again later. Once I wipe it, though, and update back to lollipop, couldn't I restore that data backup?
I gotta take a break and knock out some real work, lol, then I'll continue, and update here. If nothing else, maybe it'll help some other poor soul like me in the future!
Once I have it booting all the way again, do I just use TWRP to install SuperSU and it's rooted? Thanks again. I appreciate it!
Not sure what youre trying to do here. Just wipe the data partition with twrp,
Sent from my SM-T805 using XDA Free mobile app
Ashyx, I was just trying to save my game data, while ending up with a rooted tab. And you were right, of course! I tried to restore the back up to no avail, haha....well, I wiped it again, and it booted up just fine, and it is rooted to boot. I can't believe it was that easy with TWRP to root it.
I'm betting this isn't going to work out, but is there anyway to extract my game data from that backup I made, and transfer just that back to my tablet? If it is possible, it'll probably be beyond my ability, I bet, but I'm just curious.
One other question. With TWRP, can I get Lollipop back on it? Or do I need something else on it first?
Now, it's off to figure out how to get my Impulse Controller to work with it so I can play my games with it!
Thanks for helping me out, regardless. I truly thought I had bricked my $600 tablet. My wife would've killed me for wasting that much money, lol!
There is an app called nandroid manager that will allow you to extract data from nandroids, you could extract your game data with that.
The better way would be to make a system and data backup of your current system, reflash lollipop then restore your lollipop data backup. Then back up your game data with titanium backup.
Restore your kitkat backup then restore your game data with tb.

Categories

Resources