Related
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
jimmydafish said:
this has been answered in more than one thread,
You don't have a valid recovery on your phone, you need to fastboot flash --> system, boot, recovery. This will get you out of the bootloop and let your phone update normally.
Click to expand...
Click to collapse
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
minitele said:
Thanks for the reply man. I will be honest, I did try to search within the forums and there were so many articles I literally was slightly overwhelmed.
Would you be able to point to a specific thread which would provide some steps, I am sure I can follow it. I am a little gunshy since I ended up bricking my phone when I updated. I performed the root process no problem and was happy I could still actually do this stuff. I just dont want to make things worse than they already are.
Thanks again!
Click to expand...
Click to collapse
you should join the G+ community for much better and more pointed help. The forums get cluttered.
1) download correct 4.2.2 (57-1) FXZ file
2) extract boot, system, recovery from the file
3) fastboot flash each of the partitions to your phone
(fastboot flash boot boot.img)
(fastboot flash recovery recovery.img)
(fastboot flash system system.img)
Doing this will put your phone in a state where it is ready to update.
minitele said:
Hi,
I recently have fallen victim to this reboot loop issue and yes it is my own fault - all I wanted was to be able to get control of my permissions and installed Pwnmymoto - What I read later on a different thread was that the OTA update would brick my phone.
Now, I could careless since I can get a new phone.
I just have one simple question - Is there anyway to connect to my phone and extract all the data out via adb or any other manner since I know my encryption password?
Here is the breakdown to make things simple.
1. OTA updated keeps phone in infinite reboot loop.
2. Phone is encrypted.
3. I want to be able to retrive my data and just do not know how to connect to my phone because it is encrypted.
I truly would appreciate any help regarding this matter!!
Sincerely,
Tony
Click to expand...
Click to collapse
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
jayboyyyy said:
what the above poster said is all accurate. but you can get your phone out of the bootloop by connecting it to fastboot mode and running fastboot erase cache. after you do that the phone will boot normally. Then you can take whatever data you want off it. then do what the above poster said to take the ota.
What happened was the ota downloaded to the phone and is forcing it to try and update the phone every time it boots. You need to erase that download which is located in /cache and then it wont force reboot thhe phone. this has also been answered many places. basically every thread titled brick or bootloop or whatever.
Click to expand...
Click to collapse
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
jimmydafish said:
erasing cache will cause the following to happen,
You reboot your device, it downloads the update, you bootloop again, you wipe cache, your reboot your device, you download the update, your bootloop again.
@jayboyyyy why not just have him fix the problem that is causing the update and then he will update correctly to KitKat, isn't that the best possible outcome?
Click to expand...
Click to collapse
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
jayboyyyy said:
well for starters, it seems he is trying to go from original stock FW to 4.2.2 (he said he is using pwnmymoto so he isn't on 4.2.2 yet).
He also said he wants to keep root so he isn't trying to take 4.4 because he won't have root on that FW.
While flashing that stuff will fix his problem and allow him to take the ota, I always like to make backups of everything before doing that. he won't be able to make a tibu backup of his current set-up by doing what you said because it will remove root once he flashes that stuff. So when he then gets root on 4.2.2 he will not have a back up to work with. (I believe you were thinking he was trying to take 4.4, which he may be, but i didn't read it that way).
If he is trying to take 4.4 he should know that he won't have root and he might never have root on 4.4. So if it is essential to him, he should only be taking the 4.2.2 update.
And once he erases cache. he can freeze otas from popping up on his phone. Also, he won't keep getting stuck in a BL because it prompts you and asks if you want to download the latest ota. it doesn't auto download it, so if he doesn't click yes then it won't download or cause a Bbootloop.
Finally, if he doesn't want to try and root with rockmymoto to save time, he can just install pwnmymoto without running it, then take the ota, then it will automatically root the phone for him. This is why i said what i did.
Click to expand...
Click to collapse
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
minitele said:
Guys, Thank you for your input, it is really appreciated. ( I am glad the forums are still alive and just as helpful as when they started! )
I see that I may not have been as clear as I could have and for that I apologize.
My only goal at this time is to recover my data, since I have activated my old phone ( couldnt wait since it happened on sunday and this is my only phone).
Would the flashboot erase cache method fulfill my only goal which is to recover the data?
If so, are there any different steps that need to be taken to accomplish this?
Thank you again both for your input. If only the world would be discussing two SOLUTIONS to any problem, or worked as this thread , man would it be a much better place!!
Click to expand...
Click to collapse
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
jayboyyyy said:
if you know how to use fastboot then no other steps are necessary. If you had root explorer on your phone, then you could just go to the cache directory and erase it before the phone bootloops again. most people have like 30 to 40 secs before it loops. Just another option. But all you need to do is remove the file from cache.
Click to expand...
Click to collapse
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
minitele said:
Just a quick question - Will it matter if my device is encrypted? I only ask because it seems most tutorials never cover encrypted phones.
At least the 10 or so I have read, even youtube videos .
Thanks!
Click to expand...
Click to collapse
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
jayboyyyy said:
doubt it matters. I think encryption just encrypts user data and other stuff, not all of the phones files. but i could be wrong. I jsut think thats probably the case. i think encryption can cause problems when people are trying to write to certain directories that might be encrypted. I don't think you should run into an issue with the cache though. Not like it wills crew anything up trying.
Click to expand...
Click to collapse
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
minitele said:
Cool, I have taken a look at a youtube video regarding fastboot.
I will give it a shot and report, thanks again!
Click to expand...
Click to collapse
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
tracyde said:
My Moto X is encrypted and can confirm that it will be fine after you fastboot flash boot, system, recovery. My phone was doing something similar when I tried to install OTA without returning the recovery partition to stock. One thing that I learned was that if you are trying to run fastboot command from an Ubuntu machine make sure you run it via sudo, otherwise your regular user will most likely not have permission and the fastboot command will fail.
Click to expand...
Click to collapse
To all,
The forums and people in our arena never fail, fastboot erase cache worked perfect. I have recovered all my data and now I will definitely continue to performing a full recovery with stock image.
Thank you again all for all of your help, I am glad to see at least this corner in the internet still is alive and kicking!
When I got my phone I chose to decrypt it, mostly because I was afraid of TWRP not being able to read the encrypted partition (at the time) and fears of bad performance (which plagued the N6 when it came out).
Every time I update my phone I have to wait until a noencrypt boot partition for my version is released and it makes the whole process clunkier.
I was wondering how many people still have their phone decrypted. Are there any downsides to encrypting my phone now? I've also seen some talks about kernels that support decrypted phones - I thought this was something that was decided at the boot partition level? What does the kernel have to do with it?
Thanks in advance for any information that will help me decide how to move forward.
Slartibartfast_ said:
When I got my phone I chose to decrypt it, mostly because I was afraid of TWRP not being able to read the encrypted partition (at the time) and fears of bad performance (which plagued the N6 when it came out).
Every time I update my phone I have to wait until a noencrypt boot partition for my version is released and it makes the whole process clunkier.
I was wondering how many people still have their phone decrypted. Are there any downsides to encrypting my phone now? I've also seen some talks about kernels that support decrypted phones - I thought this was something that was decided at the boot partition level? What does the kernel have to do with it?
Thanks in advance for any information that will help me decide how to move forward.
Click to expand...
Click to collapse
I would say it all depends on the user. If you use your phone for sensitive material such as work-related Communications or financial transactions, it might be a good idea to do so. If on the other hand, you use your phone to Simply play games and communicate on social media, it may not matter so much depending on what type of information you have on your phone
Just speaking for myself, my phone is encrypted, and I have no problem reading it with TWRP. I can apply over-the-air patches without a problem granted I take steps to return to. Full stock beforehand
Sent from my Nexus 6P using Tapatalk
Having the phone decrypted doesn't really give any benefit, on paper there's a performance gain but in real world usage it isn't noticeable. Just encrypt it and then you don't have to worry about all this mess.
Thank you both for your replies!
Heisenberg said:
Having the phone decrypted doesn't really give any benefit, on paper there's a performance gain but in real world usage it isn't noticeable. Just encrypt it and then you don't have to worry about all this mess.
Click to expand...
Click to collapse
What will I see different if I allow it to encrypt my data now? Basically to my understanding if I update to the latest version, if I overwrite the boot image and the kernel, it will encrypt my data the first time I boot into Android, right? Will I then have to enter my Google password every time I boot the phone? or my phone unlock PIN?
Slartibartfast_ said:
Thank you both for your replies!
What will I see different if I allow it to encrypt my data now? Basically to my understanding if I update to the latest version, if I overwrite the boot image and the kernel, it will encrypt my data the first time I boot into Android, right? Will I then have to enter my Google password every time I boot the phone? or my phone unlock PIN?
Click to expand...
Click to collapse
You can encrypt your data at any time. It will encrypt on the first boot after removing the kernel that doesn't force encryption. You only need to enter a pin/pattern if you choose to have lockscreen security, you can choose not to have any lockscreen security at all.
Honestly I would say do it. I always had it un-encrypted and it was just a pain in the arse waiting for someone to post a boot.img that doesn't force encryption or flashing a custom kernel to keep it without encryption. With this there is no worrying before updates, I have not noticed any changes in performance, and if you do want to use a custom kernel they all work great with it.
Yes, and yes!
Sent from my Nexus 6P using Tapatalk
My 6P arrived yesterday and I was pondering this same question. I have read a number of resources that show slower read/write speeds with encryption in play; however I use this phone for work and a backup to our kids' tablets dying (car rides, rainy day, etc. lol).
I was about to ask you @Heisenberg about decryption in your How-To thread in the General forum as I was confused on how to do this now? I recall from Nexus 6 days it was always a custom boot.img and you were decrypted...our instructions read more like TWRP (after a certain version) drives this process now instead?
Regardless, I am debating whether to bother with decryption at this point since it will be used for work.
3's&7's said:
My 6P arrived yesterday and I was pondering this same question. I have read a number of resources that show slower read/write speeds with encryption in play; however I use this phone for work and a backup to our kids' tablets dying (car rides, rainy day, etc. lol).
I was about to ask you @Heisenberg about decryption in your How-To thread in the General forum as I was confused on how to do this now? I recall from Nexus 6 days it was always a custom boot.img and you were decrypted...our instructions read more like TWRP (after a certain version) drives this process now instead?
Regardless, I am debating whether to bother with decryption at this point since it will be used for work.
Click to expand...
Click to collapse
TWRP isn't involved in the process of decryption, it was that TWRP wasn't able to decrypt so deception was necessary to use TWRP. To decrypt you need a kernel that doesn't force encryption, and to issue the "fastboot format userdata" fastboot command. This will erase your data so back it up first.
Heisenberg said:
TWRP isn't involved in the process of decryption, it was that TWRP wasn't able to decrypt so deception was necessary to use TWRP. To decrypt you need a kernel that doesn't force encryption, and to issue the "fastboot format userdata" fastboot command. This will erase your data so back it up first.
Click to expand...
Click to collapse
@Heisenberg ...lol, I honestly thought deception was a typo for decryption!
How dare I question the typing capability of the keeper of knowledge for the Nexus community! Did some more research and get "Deception" now (how often do you read those words in a sentence together in life as an adult?!).
Thank you as always you are always a benefit to the community! Ill go hunting for a kernel and test both security modes for fun (its a Nexus, right?!)...probably wont bother long term as I have a few exchange accounts, shared files, etc. on my devices.
Hi, bought this phone yesterday, and flashed the rom of the dev adition, and lost my radio, was lucky enough to get best buy to take it back. I got another one though, and I was wondering if there is an official marshmallow downloadible rom for this phone. Don't just want to flash the ota, want to get the entire rom, and I am bootloader unlocked. Also, is there a cfautoroot for this phone on marshmallow.
Thanks in advance
FYI this is a good way to get raged on.
please search before you ask questions that are and have been answered in other threads.
Have a blessed day
1. do you have custom recovery if so see http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
2. if you want to start over with a clean slate see http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
This is what I am using after not being able to get OTA http://forum.xda-developers.com/showpost.php?p=65965064&postcount=2
Honestly you should not be flashing anything. Ever.
I'm totally blind and these forms are super hard to navigate through the cludder with
Hi, I am a very technical person, who has a masters in computer programming, I work with linux and just about anything, but I ask questions that may have already been asked, because if you have ever used a screen reader, with the banners and so much cludder, some times I can find the answer, and sometimes I go through pages and pages, and can't find it, and you guys find it easily, so what am I missing. I just want to be on the latest rom, be rooted, and have a custome recovery. Can this be done with cfautoroot on the xt1575, because beeing blind I have to do everything through fastboot as much as possible because my wife will help me some times but usually she gets very frustrated when she has to work twrp and install things for me, so sorry for the ramble, but that's why I some times ask questions that have already been asked.
Thanks
Isaac
orvon.freeman said:
FYI this is a good way to get raged on.
please search before you ask questions that are and have been answered in other threads.
Have a blessed day
1. do you have custom recovery if so see http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
2. if you want to start over with a clean slate see http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
This is what I am using after not being able to get OTA http://forum.xda-developers.com/showpost.php?p=65965064&postcount=2
Click to expand...
Click to collapse
Fastboot flash twrp and download the newest rooted w security update and flash, what I did was flash the non rooted to get everything, then flashed rooted to get root. I can understand that there is a lot of clutter. Wish I could do it for you I deff would
so no problem, what wipe should I do before the flash of the rom, cache, dalvik, and data? Also, does the rooted deodexed use a different baseband or modem, and is there any advantage to deodexing in this day and time, I heard that most of these roms these days were actually not odexed anyway, just asking and learning
Do not do not use fastboot to wipe anything. Download the regular from the link above and the rooted and put on SD card. Flash recovery in fastboot use bootloader to get into recovery(otherwise phone will overwrite) wipe everything accept external in recovery and flash the ROM with February security patch
https://www.androidfilehost.com/fid=24459283995299100
Then after it flashes completely flash https://www.androidfilehost.com/fid=24459283995302251
Then let reboot. I did this with no issues.
Hey guys, I am having a huge problem with my PIN. I've been using the same pin for a very long time so I know for a fact that it's right. Now I cannot boot the phone, or get into TWRP.
When I boot the phone it's asking me for the PIN and it just keep saying that it's wrong which I know it's not. When I try to do a hard recovery into TWRP it's asking me for the PIN and then just sits at "trying decryption".
Anyone have any thoughts with where I should go from here? There's nothing on the phone that I need in terms of data so if it needs to be completely wiped out I don't care.. just looking for some guidance.
Thanks in advance.
Seems like you had your phone set up to require a pin even before it starts, which is why you can't even get into TWRP. It's a problem with the 6P, I'll link the thread in a bit if I can find it but basically when you back up a ROM, always remove ALL pins and passwords to unlock the phone first.. There's an issue that if you back up a ROM and keep it password protected, it won't let you get back into it even if the pin is correct, UNLESS you go in your file explorer (in TWRP) and delete a specific file that pertains to the the security features AFTER you restore it, but BEFORE you reboot the phone.
In your case it's worse because you had the device set up to not boot unless a code is entered. Don't ever do that, especially when flashing ROMS. The standard security on the lock screen when you boot the phone up regularly is enough. Had you not did that you'd still be able to boot into TWRP, delete that file, to get access to your back up.
There's nothing you can do now. I had to learn this the hard way too just like you. Load up your laptop and completely restore the phone using Nexus Root Toolkit or something similar, you'll most likely lose all data too. Sorry pal.
Edit- found the thread
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Hey it's no problem I don't mind losing all the data on the phone I everything backed up elsewhere.. as long as I can get it back running again it's all that really matters to me.
I'll give Nexus Root Toolkit a shot right now and let you know how it goes.. I appreciate the input.
Where would I go to be able to have the toolkit recognize the phone?
Got it all squared away.. I was able to get the phone recognized by just booting it and letting it sit at the PIN screen. Again I appreciate all your input it was very helpful.
I installed TWRP and tried to flash SuperSU according to the guide by ashyx here: https://forum.xda-developers.com/showthread.php?t=3475381
So, from what I can tell by reading this thread: https://forum.xda-developers.com/galaxy-tab-a/help/samsung-galaxy-tab-10-1-mount-data-t3544561, the problem is that my device was encrypted. I tried restoring the full image that I made using TWRP, before trying to flash the boot. Stuck on Samsung logo now. I should have seen this coming when I was getting "failed to mount /data" errors.
So I suppose I need to flash that zip https://www.androidfilehost.com/?fid=24591000424951049, but I thought I better ask specifically about my device and situation before blindly flashing yet another zip.
What steps do I need to take now?
thanx
update :: it sounds like my last resort option is to flash the stock ROM (can I do this in Odin?)
BUT I noticed that SuperSU saved a "stock_boot_*.img.gz" file, which I copied to SD root and also to my PC. Now I imagine that if I flash this, I might be able to regain access to the OS... that would be the best at this time. Then I can do more research and try root again later.
Is this true, and how should I flash the stock_root file?
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
trefrog said:
I absolutely love doing research and answering my own questions! no sarcasm. after reading a whole bunch of general info about the Android system, partitions, boot process, TWRP... I forged ahead with 90% confidence, unpacking the "stock_boot_*.img.gz" and feeling for a way to flash it with TWRP... and more importantly, with 99.9% confidence that it won't wreck anything if I try.
So next time, I will first decrypt the system before trying to root, and pay attention to the log output, and only proceed when confident that I know what's happening next... this is all basic IT procedure. I should know this! Guess I was in a rush to get root. Still in a rush in a way tho.... want to recover deleted photos and can't do it without root. Anybody know if Android device encryption is proper full-disk? Like if the empty space will be decrypted just the same?
Click to expand...
Click to collapse
It doesn't really decrypt it, it does a full format using either no encryption or new encryption. I'm sorry, but the files are gone. To answer your question though, I believe the encryption is full-disk.
Going forward, check out TitaniumMediaSync. You can mirror your internal storage to a computer via FTP, so when these things happen (and they do happen), you won't lose anything. I'm sorry you lost your files in this.
actually I didn't lose my files! I was able to restore the backed up boot partition that twrp made and tucked into a folder.
happy af :laugh:
... so are you saying that the decrypt function in the Android settings just wipes everything? Then why is it even there, if it's basically a factory reset?
hmm associated with Titanium Backup? I have a license for that, and as soon as I root this, I'll be installing it. Currently, all my important stuff (just photos), are backed up to my PC via QuicPic's cloud backup feature.
I think i have found myself in the same situation as you. I dont have any files or data to lose. managed to do first step in using odin to install twrp. tried to follow additional steps of installing super su, then padded boot. now the tablet wont load past the first screen. I can still get into twrp. how can i get this fixed, rooted and a custom image installed? any help in the right direction would be appreciated.
find that "stock_boot_*.img.gz" using the twrp file browser thing. copy it to the root of your SD for safe keeping (even if the SD is encrypted, it seems that it does so only at the file level, rather than partition/disk level, so it will be written unencrypted). if ur plugged to PC, you can copy it across for even safer keeping
then... I don't recall how I found it, but it's in twrp. a way to flash that file. worked for me, because as far as I made it, only the boot partition was affected