Related
My rooted KF got bricked by the new OS update that was released last night. It boots as normal, gets to the locker screen, and whether you unlock it or not, reboots about 15 seconds later to a screen showing the Android guy and an exclamation point in a yellow triangle. Then, if you start touching the screen, 4 buttons will show up on the side, up/down, select, and back... but they do nothing. Reboot again and it takes me to TWRP.
I know how to wipe my KF and reinstall everything, but I was hoping that someone might know of a fix for this. Especially because I just got a new computer and am still in the process of getting my normal apps installed, let alone Android SDKs that I use once in a blue moon. Plus, I have a few games that I would rather not lose my progress on.
BTW, I rooted my dad's KF the exact same way as mine and his just lost root access with the update, everything else is fine. Kinda weird.
TIA
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S. You may also get lucky and be able to flash modaco if you`re on rooted stock or previously rooted stock 6.3.1 without wiping.
Thepooch said:
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S.
Click to expand...
Click to collapse
About 3am last night, I found my KF bricked after just using it about 30 minutes before (the wifi was on and it was hooked up to the charger). Today, I checked on my dad's KF and he has his wifi turned off. I turned it on and it instantly rebooted to just a "command line" screen saying that it was installing an update. Took about 10 minutes and then rebooted and worked fine, except that it was unrooted. I read somewhere in the Amazon Forums today that they did roll out an update and plan on spending 2 weeks doing it to keep from bogging down their network. Granted, their Software Update page doesn't say anything about it yet.
BTW, thanks for the other info, I'll have to check it out. Sounds like I'll have to wipe it (or at least restore from a 2-3 month old backup and see how the update goes again). But that's cool that I won't need to install the Android SDK.
Explains why some are instantly being unrooted or like in your case bricked strange thing is that it doesn`t change the system version it`s still 6.3.1 figures that Amazon would pull something like this.
Hey, I did manage to find a quick fix!
In the recovery mode, I decided to try using the Fix Permissions option. Still had the same problem.
I then just used the Clear Cache option and my KF was back up and running... and still rooted.
The only issue I have found so far is that I had to change the permission to allow changing the wallpaper, just uncheck the "write" permissions, (which was probably reset by the Fix Permissions option I ran). Other than that 2 second fix, everything is fine.
Granted, I'm waiting for Amazon to do an auto-check for some file that was in the cache that told it that it had installed the latest upgrade, and since I wiped that, it may install it again. If it does, I'll post it in this thread that my quick fix didn't work. But so far so good.
It turns out that my quick fix is only a temp fix.
Twice tonight I had to clear the cache again via the recovery menu. The first time it happened, I had just finished reading and hit the power button to put it in sleep mode, which caused it to instantly reboot and then do the same thing as I mentioned above. It boots up, and within 5 second of getting the locker screen, whether you unlock it or not, it starts shutting down and reboots ending up with the screen in the attached pic (those dots are just dust that appear super bright for some weird reason because you can't see them except in the pic).
So I cleared the cache again, everything was fine, and then about an hour later I found it sitting on that screen again. Clearing the cache fixed it again, but obvious this is a reoccurring problem.
Anyone have any ideas?
I'm reluctant to do a reinstall yet because I'm afraid I'll just end up with the same problem... along with none of my apps installed.
I have the same issue my temp solution is turn off wifi asap after lock-screen appear, wait abt 1-2 minutes then I can turn on wifi and use as normal.
Everything will fine for few hours. Any permanent solution plz? I remember that it occurred after i update something from Amazon app store, maybe : apps...
Sent from my Kindle Fire using xda premium
The permanent solution is to flash another rom preferably modaco if you want the stock experience. Full wipe, your apps can all be redownloaded that is the least of your worries at this point. probably a really good time to upgrade your bootloader and recovery if you haven`t flash both of these zips as zips in twrp if are behind the curve http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 and http://forum.xda-developers.com/showthread.php?t=1632375 only get them from where I`m directing you or use smirkit http://forum.xda-developers.com/showthread.php?t=1500935.
thanks for your help. This is done with the below solution
1) Copy the update bin file to the /sdcard as update.zip
Download stock ROM : https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.1_D01E_4107920.bin
copy update-kindle-6.3.1_D01E_4107920.bin into Kindle Fire and re-name to update.zip
2) From the main menu of CWM, "Wipe cache from partion" to remove the existing files in the data and cache partitions
3) From the main menu of CWM, press the "Install update.zip" button to flash the stock software onto your device.
no data/application lost accept FFF and CWM
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Thanks for the info guys.
Considering the post in the Amazon Forums said this update was being pushed out over a 2 week period, I'm just going to keep my WiFi off (unless needed) and wait until everyone should have received the update and then see how it plays out. Considering it doesn't change the software version number, I'm thinking that this update may be just targeting rooted Fires. And BTW, it appears that the post was removed, because I can't find it again. Maybe they remove any that mention rooting? I just stumbled upon it via a Google search... 99% of the question in their forum are just idiotic.
Directv used to pull this stunt all the time to bust people with hacked cards that allowed them to get all their channels for free (usually a few hours before some big PPV event). They finally completely stopped the ability to hack cards by rolling out parts of their code over a long period of time, a year or so. When the final piece was put in place, the previous parts of their code had already been integrated into the hacked card software, because it appeared safe, and along with upgrading the type of cards they used during that same period of time, pretty much eliminated the ability to cheat Directv. I'm not saying that Amazon is going to those lengths to stop people from rooting their KFs,.. but who knows? It may be costing them too much with people bricking their KFs by trying to root them. Plus, they may also be losing revenue by people getting their free apps (with ads) from the Playstore instead of Amazon. And considering they pretty much sell their Fires for cost, they definitely rely on revenue generated by buying and using things via a stock KF.
BTW, this whole issue had almost perfect timing... I was planning on wiping my KF because it definitely is slower than when I first got it (which was day 1 of its release). I've read that Gingerbread doesn't clean up after itself too well, especially not as good as ICS (kinda like a Windows registry just gets filled with junk over time, and no cleaner beats a fresh install). It also appears that the ICS roms are actually working reliably these days, compared to the last time I checked. So, in a couple weeks, I'll get to have some fun. I am a Windows/Cisco System Engineer, so this kinda stuff is fun for me.
F.Y.I.
It seems that Amazon did do a incremental update on the Original Kindle Fire version
6.3.1_user_4107720, April 30 build to 6.3.1_user_4107920, November 27 build.
I looked thru the update and the only things I found changed are to do with the
Wifi driver, launcher icons, boot animation, and boot.img; attached the changed file below.
I have not tried to update mine, will attempt this weekend.
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Thepooch said:
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Click to expand...
Click to collapse
It seems they increased the resolution of the images in the file, but for me I can not see the difference.
For me I wonder what they changed in the WiFi driver file, tiap_drv.ko.
Kindle Fire Reboot Problem Solved - Install MoDaCo Rom
Thepooch said:
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Click to expand...
Click to collapse
I took Thepooch's advice and installed MoDaCo rom on my KF. It was a snap. I had FireFireFire installed with TWRP. Just downloaded MoDaCo to PC copied to KF. Rebooted to FireFireFire Installed with Install Zip utility. Took a few minutes. Rebooted didn't loose any data , apps or functionality. Its still rooted. THANKS!
No problem you can find the entire uncomplicated method here http://forum.xda-developers.com/showthread.php?t=1923010 or at least a synopsis of the concept.
SOLVED
We have a Oneplus3 with root and LineageOS 14.1. Downloaded the LineageOS 15.1 and Googleapps and placed them on the root of the SD card. Turned off the phone, rebooted into TWRP, performed a backup and tried to Install the 15.1. It said something to the effect that we didn't have a Oneplus3 and didn't install. The error which is shown when trying to install the 15.1 is "E3004. This package is for device: OnePlus3, oneplus3, OnePlus3T, oneplus3t; this device is ."
Tried installing the backup but when it finishes "installing" and we reboot all we get is the "Your device is unlocked..." screen and then the "POWERED BY android" screen. It doesn't go beyond this screen.
What to do?
Have a great afternoon!
Well, don't know if we have success or not... i applied a solution from this forum to "boot into recovery and select 'fix contents' and reboot".
https://forum.xda-developers.com/oneplus-3/help/stuck-logo-flashing-rom-t3422304
i now have advanced to the blue curve with the moving circle, but it's been like this for some 10 minutes... - lol.
Have a great evening!
frazelle09 said:
Well, don't know if we have success or not... i applied a solution from this forum to "boot into recovery and select 'fix contents' and reboot".
https://forum.xda-developers.com/oneplus-3/help/stuck-logo-flashing-rom-t3422304
i now have advanced to the blue curve with the moving circle, but it's been like this for some 10 minutes... - lol.
Have a great evening!
Click to expand...
Click to collapse
Which version of TWRP do you have? Try eng.stk's (blu_spark)
tnsmani - i really appreciate your posting! i was under the impression that these threads were a little more "active" - lol. i'm at TWRP 9.8 and it's already the Blue spark...
i finally decided to bite the bullet and reinstall 14.1 from scratch since i couldn't get my backup to reinstall - grrr. So, with the help of ADB and my trusty PCLinuxOS the phone's back and running. Very disappointed my backup didn't work i have used it before - with a different backup - and didn't have any problems at all. i wonder what secret, unknown, black magic, undocumented step(s) i missed when i created it. It's not like it comes with a button you get to press after you create it which says: To Test Your Backup.
Again, thanks for offering to help. It seems like there are fewer of you around these days. And
have a wonderful day!
frazelle09 said:
tnsmani - i really appreciate your posting! i was under the impression that these threads were a little more "active" - lol. i'm at TWRP 9.8 and it's already the Blue spark...
i finally decided to bite the bullet and reinstall 14.1 from scratch since i couldn't get my backup to reinstall - grrr. So, with the help of ADB and my trusty PCLinuxOS the phone's back and running. Very disappointed my backup didn't work i have used it before - with a different backup - and didn't have any problems at all. i wonder what secret, unknown, black magic, undocumented step(s) i missed when i created it. It's not like it comes with a button you get to press after you create it which says: To Test Your Backup.
Again, thanks for offering to help. It seems like there are fewer of you around these days. And
have a wonderful day!
Click to expand...
Click to collapse
If your phone doesn't boot. Just wipe boot and system and flash the rom again or your old rom and it should work 90% of the time. These two partitions get overwrited when flashing a rom.
i tried doing that several times, but those must have been the other 10%...
Have a super evening!
frazelle09 said:
i tried doing that several times, but those must have been the other 10%...Have a super evening!
Click to expand...
Click to collapse
Please, tell us how did you solved your issue.
(You wrote"solve" in thé OP)
I extract the ROM and go to meta-inf/com/Google/android/ updater script and delete from first line start as assert to before ui print and save and compress and flash with out any problem.
Because all the roms had this problem even my Redmi note 4x, mi max2 had this same "E3004. This package is for device
problem in custom roms for past few months.
drmuruga said:
I extract the ROM and go to meta-inf/com/Google/android/ updater script and delete from first line start as assert to before ui print and save and compress and flash with out any problem.
Because all the roms had this problem even my Redmi note 4x, mi max2 had this same "E3004. This package is for device
problem in custom roms for past few months.
Click to expand...
Click to collapse
I have been using Vertex and PureFusion Nougat before without any issues. So all the ROMs (if at all any) don't have this issue. Plus everyone is not tech savvy and extracting, deleting and repacking are all a little above the average user.
---------- Post added at 05:16 PM ---------- Previous post was at 05:14 PM ----------
frazelle09 said:
tnsmani - i really appreciate your posting! i was under the impression that these threads were a little more "active" - lol. i'm at TWRP 9.8 and it's already the Blue spark...
i finally decided to bite the bullet and reinstall 14.1 from scratch since i couldn't get my backup to reinstall - grrr. So, with the help of ADB and my trusty PCLinuxOS the phone's back and running. Very disappointed my backup didn't work i have used it before - with a different backup - and didn't have any problems at all. i wonder what secret, unknown, black magic, undocumented step(s) i missed when i created it. It's not like it comes with a button you get to press after you create it which says: To Test Your Backup.
Again, thanks for offering to help. It seems like there are fewer of you around these days. And
have a wonderful day!
Click to expand...
Click to collapse
eng.stk's TWRP latest version is 8.61. I don't know where you got 9.8 and it is probably the culprit.
Donglip said:
Please, tell us how did you solved your issue.
(You wrote"solve" in thé OP)
Click to expand...
Click to collapse
Please see the fourth post of this thread.
Have a great morning and a beautiful day in Paris!
eng.stk's TWRP latest version is 8.61. I don't know where you got 9.8 and it is probably the culprit.
Click to expand...
Click to collapse
You are correct. My version is 9.8 - my bad. Who knows why it didn't work. Maybe it would be a good idea for me to wait till the next version before i try again. i don't know if you saw it or not, but i also mentioned that my Backup (that i made through TWRP) before trying to upgrade did not work, either. i wouldn't have been so freaked out if it had since i've had to use them before, but this time it wouldn't reinstall. i'm wondering if i missed some vital, hidden, secret sign or step before making the backup - deleting the /temp folder, upgrading to Windoze 11 - something. There seems like there's always - something - lol.
Have a super day! It looks like threads get more love after the issue has been solved than when the OP is in the process of trying to figure out what's happening... but it could just be me and my sample methodology - lol.
Hi all
I have been pointed towards xda following a conversation in another forum regarding my failing Tab S.
Before I registered today, I took a look around the forum and am left feeling a bit like a duck out of water.
I dont really understand much of the jargon being used, and so im not sure if I really belong here . I'm just trying to find a fix for my tablet that doesn't involve the expense of returning it to Samsung.
I bought my Tab S 10.5 back in 2014, and until last year I felt that it performed flawlessly. So last year a friend of mine dropped it onto my kitchen floor resulting in a shattered screen from the top left corner outwards. I did look into getting the screen replaced at the time but it turned out that it was going to cost me £250, which I believe is half the price of what I paid for the whole thing when it was new. So I decided to live with the damage, which isn't too visible when its switched on.
A year later and I have what I think is a more serious issue. While I was on Facebook my tablet decided to turn itself off at 50% battery, and when I turned turning it back on it appeared to be stuck in some kind of boot-loop, constantly switching from a slowly glowing Samsung logo to the smaller constructing logo (I hope that makes sense). I tried various button sequences to get the thing running but none made any difference.
Following a bit of Googling I tried a hard reset and clearing the cache. The process took mere seconds, leading me to believe that the hard reset functionality wasn't working either. And after the reset where it gave me to the option to restart, I was taken back to the boot-loop again.
Part of me wonders if the tablet has reached the end of its life, but another part of me thinks that I should expect more from a 4 year old £500 tablet, although yes it did get dropped that time.
Anyway, I have been directed here by someone who suggested that a custom rom might be the answer, but after taking a look at the Samsung Tab S Development page, I am completely stumped at what rom to choose and how to install it, and just when I thought id go for it, I didn't really understand the following instructions:
Download the latest build (download to what, my laptop?)
Download opengapps.org (I dont know what this is and where to download it to)
Make a nandroid backup (totally lost on this one)
Recommended - Full wipe system/data (first install) (I think I did that, although it took about 2 seconds)
Flash latest Twrp (T800/T805) & Firmware from sammobile.com (T800/T805) (No idea what that means)
Flash ROM (?)
Flash Gapps (?)
Reboot
Enjoy!
Thanks for taking the time to read my post. I'm hoping that there might be an idiots guide to fixing the Tab S
5hane said:
Download the latest build (download to what, my laptop?)
Download opengapps.org (I dont know what this is and where to download it to)
Make a nandroid backup (totally lost on this one)
Recommended - Full wipe system/data (first install) (I think I did that, although it took about 2 seconds)
Flash latest Twrp (T800/T805) & Firmware from sammobile.com (T800/T805) (No idea what that means)
Flash ROM (?)
Flash Gapps (?)
Reboot
Enjoy!
Click to expand...
Click to collapse
1) yes, to your laptop or pc or what ever computer you're using.
2) OpenGapps are the google apps that don't come with a generic Rom, such as GMail, the Google Play Store, etc etc. (and again, download it to the computer you are using (so when you flash the Rom, you can flash these google apps also).
3) Making a backup (nandroid is one type, there are others), is imho, optional. If you have pictures, pdf files, anything on the device you don't want to lose, back those up somehow. I never worry about making a nandroid backup personally.
4) If you haven't installed TWRP, then you probably haven't wiped system / data. It's after having installed twrp that you want to do that wipe (within twrp, there are directions in it to do that). You wipe those partitions so you can "start new", with your new Rom.
5) TWRP is a replacement recovery you flash (install) over the old (original) recovery. It allows you to flash roms etc etc etc. BUT, you have to use the specific version of TWRP for your specific device.
I'd suggest doing a lot of reading, search google for various topics related to this subject; like 'how to install twrp on the Samsung Tab S' or 'What version of twrp should I use for Samsung Tab S' or etc etc etc.
Then READ READ READ READ READ READ!! until you feel comfortable with what you are doing! It's those that do things they don't have any idea what it will do that end up buying a new device when they didn't have to.
Cheers
AsItLies said:
1) yes, to your laptop or pc or what ever computer you're using.
2) OpenGapps are the google apps that don't come with a generic Rom, such as GMail, the Google Play Store, etc etc. (and again, download it to the computer you are using (so when you flash the Rom, you can flash these google apps also).
3) Making a backup (nandroid is one type, there are others), is imho, optional. If you have pictures, pdf files, anything on the device you don't want to lose, back those up somehow. I never worry about making a nandroid backup personally.
4) If you haven't installed TWRP, then you probably haven't wiped system / data. It's after having installed twrp that you want to do that wipe (within twrp, there are directions in it to do that). You wipe those partitions so you can "start new", with your new Rom.
5) TWRP is a replacement recovery you flash (install) over the old (original) recovery. It allows you to flash roms etc etc etc. BUT, you have to use the specific version of TWRP for your specific device.
I'd suggest doing a lot of reading, search google for various topics related to this subject; like 'how to install twrp on the Samsung Tab S' or 'What version of twrp should I use for Samsung Tab S' or etc etc etc.
Then READ READ READ READ READ READ!! until you feel comfortable with what you are doing! It's those that do things they don't have any idea what it will do that end up buying a new device when they didn't have to.
Cheers
Click to expand...
Click to collapse
That's great, thank you for your detailed reply.
Luckily I back up my docs and media to an SD card as I go, so I dont believe I have lost anything.
I will get reading this afternoon and fingers crossed it will work!
Further. I registered today and so assumed this was my first post, but according to my profile I posted in 2015!
Reading back it looks like those posts were made by me, but I have just registered under a totally different user name and password today and yet I am somehow logged in to my obviously forgotten account.
5hane said:
Hi all
I have been pointed towards xda following a conversation in another forum regarding my failing Tab S.
Before I registered today, I took a look around the forum and am left feeling a bit like a duck out of water.
I dont really understand much of the jargon being used, and so im not sure if I really belong here . I'm just trying to find a fix for my tablet that doesn't involve the expense of returning it to Samsung.
I bought my Tab S 10.5 back in 2014, and until last year I felt that it performed flawlessly. So last year a friend of mine dropped it onto my kitchen floor resulting in a shattered screen from the top left corner outwards. I did look into getting the screen replaced at the time but it turned out that it was going to cost me £250, which I believe is half the price of what I paid for the whole thing when it was new. So I decided to live with the damage, which isn't too visible when its switched on.
A year later and I have what I think is a more serious issue. While I was on Facebook my tablet decided to turn itself off at 50% battery, and when I turned turning it back on it appeared to be stuck in some kind of boot-loop, constantly switching from a slowly glowing Samsung logo to the smaller constructing logo (I hope that makes sense). I tried various button sequences to get the thing running but none made any difference.
Following a bit of Googling I tried a hard reset and clearing the cache. The process took mere seconds, leading me to believe that the hard reset functionality wasn't working either. And after the reset where it gave me to the option to restart, I was taken back to the boot-loop again.
Part of me wonders if the tablet has reached the end of its life, but another part of me thinks that I should expect more from a 4 year old £500 tablet, although yes it did get dropped that time.
Anyway, I have been directed here by someone who suggested that a custom rom might be the answer, but after taking a look at the Samsung Tab S Development page, I am completely stumped at what rom to choose and how to install it, and just when I thought id go for it, I didn't really understand the following instructions:
Download the latest build (download to what, my laptop?)
Download opengapps.org (I dont know what this is and where to download it to)
Make a nandroid backup (totally lost on this one)
Recommended - Full wipe system/data (first install) (I think I did that, although it took about 2 seconds)
Flash latest Twrp (T800/T805) & Firmware from sammobile.com (T800/T805) (No idea what that means)
Flash ROM (?)
Flash Gapps (?)
Reboot
Enjoy!
Thanks for taking the time to read my post. I'm hoping that there might be an idiots guide to fixing the Tab S
Click to expand...
Click to collapse
4pda.ru
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
5hane said:
Hi all
I have been pointed towards xda following a conversation in another forum regarding my failing Tab S.
Before I registered today, I took a look around the forum and am left feeling a bit like a duck out of water.
I dont really understand much of the jargon being used, and so im not sure if I really belong here . I'm just trying to find a fix for my tablet that doesn't involve the expense of returning it to Samsung.
I bought my Tab S 10.5 back in 2014, and until last year I felt that it performed flawlessly. So last year a friend of mine dropped it onto my kitchen floor resulting in a shattered screen from the top left corner outwards. I did look into getting the screen replaced at the time but it turned out that it was going to cost me £250, which I believe is half the price of what I paid for the whole thing when it was new. So I decided to live with the damage, which isn't too visible when its switched on.
A year later and I have what I think is a more serious issue. While I was on Facebook my tablet decided to turn itself off at 50% battery, and when I turned turning it back on it appeared to be stuck in some kind of boot-loop, constantly switching from a slowly glowing Samsung logo to the smaller constructing logo (I hope that makes sense). I tried various button sequences to get the thing running but none made any difference.
Following a bit of Googling I tried a hard reset and clearing the cache. The process took mere seconds, leading me to believe that the hard reset functionality wasn't working either. And after the reset where it gave me to the option to restart, I was taken back to the boot-loop again.
Part of me wonders if the tablet has reached the end of its life, but another part of me thinks that I should expect more from a 4 year old £500 tablet, although yes it did get dropped that time.
Anyway, I have been directed here by someone who suggested that a custom rom might be the answer, but after taking a look at the Samsung Tab S Development page, I am completely stumped at what rom to choose and how to install it, and just when I thought id go for it, I didn't really understand the following instructions:
Download the latest build (download to what, my laptop?)
Download opengapps.org (I dont know what this is and where to download it to)
Make a nandroid backup (totally lost on this one)
Recommended - Full wipe system/data (first install) (I think I did that, although it took about 2 seconds)
Flash latest Twrp (T800/T805) & Firmware from sammobile.com (T800/T805) (No idea what that means)
Flash ROM (?)
Flash Gapps (?)
Reboot
Enjoy!
Thanks for taking the time to read my post. I'm hoping that there might be an idiots guide to fixing the Tab S
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=636846
http://4pda.ru/forum/index.php?showtopic=604194
genrih69 said:
4pda.ru
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
http://4pda.ru/forum/index.php?showtopic=636846
http://4pda.ru/forum/index.php?showtopic=604194
Click to expand...
Click to collapse
Warning coming up.
---------- Post added at 08:28 AM ---------- Previous post was at 08:22 AM ----------
5hane said:
That's great, thank you for your detailed reply.
Luckily I back up my docs and media to an SD card as I go, so I dont believe I have lost anything.
I will get reading this afternoon and fingers crossed it will work!
Click to expand...
Click to collapse
If you are having issues with your device then flashing custom firmware is not the answer.
If indeed it is software related then the best you can do is simply factory reset the device.
If that doesn't solve reinstall the stock firmware via Odin.
Don't put yourself under extra pressure by introducing unknown issues from flashing custom stuff.
Go to updato.com search your device, download the respective firmware for your device and flash it with Odin.
Google has countless guides how to flash with Odin .
If that doesn't fix it then it's likely hardware. The first thing you should look at for random shutdowns is replacing the battery.
ashyx said:
Warning coming up.
---------- Post added at 08:28 AM ---------- Previous post was at 08:22 AM ----------
If you are having issues with your device then flashing custom firmware is not the answer.
If indeed it is software related then the best you can do is simply factory reset the device.
If that doesn't solve reinstall the stock firmware via Odin.
Don't put yourself under extra pressure by introducing unknown issues from flashing custom stuff.
Go to updato.com search your device, download the respective firmware for your device and flash it with Odin.
Google has countless guides how to flash with Odin .
If that doesn't fix it then it's likely hardware. The first thing you should look at for random shutdowns is replacing the battery.
Click to expand...
Click to collapse
Thanks. Luckily I haven't tried a custom rom yet.
No the factory reset didn't work, in fact it doesn't appear to work at all. The android guy is lying on his back with some warning text below it that vanishes to soon to be read.
I daren't try replacing the battery, as the last time I tied removing the front of a tablet (a mates) the screen shattered. Plus my screen is already badly cracked and likely to get worse if I attempt to remove it.
So ill look into the Odin option. Thanks!
https://drive.google.com/file/d/1WUCR-mhu1hNejUYsdycA32NyRzX-cX12/view?usp=sharing
https://drive.google.com/file/d/1PQj2bSjV66pXFkhAqkAKt4cJp6zrt1Xk/view?usp=sharing
I see you have to install more USB drivers to your laptop. Is there anyway this whole process might mess up my laptop?
5hane said:
I see you have to install more USB drivers to your laptop. Is there anyway this whole process might mess up my laptop?
Click to expand...
Click to collapse
No. Just install the Samsung usb drivers.
Hello dear HTC10 community!
My HTC 10 is driving me crazy right now and I'm at the end of my humble Latin and hope for your help.
Facts:
HTC_0034
ROOT (Magisk)
S-OFF
Radio: [email protected]
OS: 3.16.401.2
CustomROM: Viper10 6.0.0
TWRP: twrp-3.5.0_9-0-pme.img (I also used the 4-5 versions before that in between)
About two weeks ago I installed a Magisk update. I think it was Magisk himself and not the manager. After the reboot, the device wanted a decryption key. However, I was only shown a text field, although I had deposited a pattern. Unfortunately, the way via the sample number code translation (point top-left = 1, top-middle = 2, top-right 3, middle-left = 4, middle-middle = 5 ... and so on) did not work. I couldn't get to my data. Regardless, I synchronized all important data with the PC every day via MyPhoneExplorer. So I thought to myself that I would put the smartphone back on. That started the madness ...
Part 1: Restore via TWRP
However, some later installed apps caused problems. Hence the ...
Part 2: ROM flash via TWRP
First I flashed the latest Viper10 6.0.0 ROM.
Since the developers of Viper10 are unfortunately no longer active and the Venom HUB server is down, the setup is no longer fun and my PRO license could no longer be restored - even after the selective restore of the entire Venom Viper- Modules via TitaniumBackup.
A little annoyed, I looked around for more CustomROMs.
Part 3: AICP, crDroid, CarbonROM & XenonHD
The first alternative surprised me with Android 10. WOW - I wouldn't have expected that with the old HTC10. I tried them all one by one. It's cool that some of my favorite functions (e.g. the 1px thick battery bar at the top) have made it into other ROMs.
Now I wanted to flash both candidates crDroid and CarbonROM again and examine them carefully,
From here on, sheer madness followed!
The home button on one of the two ROMs no longer responded. I suspected a hardware defect, but still wanted to test a different ROM. It didn't work either. Okay, back to the beginning.
Stock-3.16.401.2 installed. Both as Flash via TWRP and via 2PS6IMG.zip in download mode. The home button worked again both times. So NO hardware defect. In return, the mobile data no longer worked. WiFi but yes. I hadn't touched the SIM up to now and the smartphone didn't fall down either, which could have explained a wobble on the SIM. SIM removed, cleaned, slot blown out, SIM inserted, reboot: nothing. No funk.
One of the CustomROMs flashed, yeah, radio including LTE works again, home button too, but the GAPPS and the Google setup didn't work. Unfortunately, I need this because of some paid apps. The alternative with MicroG and the fake store unfortunately only worked for a few apps. So I wanted to let Google go directly to my device, because thanks to XPrivacyLua it had been fed with fake data for years and should continue to do so.
So a CustomROM flashed again. This time I couldn't enter a PIN on the first boot. The touchscreen did not respond to any touch. The softkeys responded, however. The hard keys too. With a 1-second press of power, the power menu even came up. But couldn't click anything.
Tried more ROM. Same problem.
With XenonHD the screen went on again. But again no home button.
From here on I just had to look at the device and I got in a bad mood.
Back to the beginning: Stock-3.16.401.2.
Everything worked! Great!
So now my CustomROM favorite carbon flashed clean.
No touch!
After the umpteenth attempt and once more stock ROM in between, the screen went off and was able to enter the PIN. So entered the PIN and bang, black screen. No reaction. 1 minute, 5 minutes, 20 minutes. The device got suspiciously hot. So off and let cool down.
Tried again. Same problem.
Back to the beginning: Stock-3.16.401.2.
Everything goes. But get a slight stomach ache using it without Magisk, XPrivacyLua and AFWall +.
And this has been going on for almost two weeks.
StockROM works (mostly), CustomROMs almost all hang completely in different places.
In the meantime I can hardly get beyond the bootloader (where the red warning is).
When it goes on, I see the boot animation and then a boot loop follows.
I also tried to re-flash the firmware every now and then, because there seems to be some driver problem here.
I found the only ZIP here:
[8.0] HTC 10 OREO FIRMWARE
HTC 10 OREO ~ Firmware Downloads ~ HOW TO FLASH FIRMWARE (Thanks to @Sneakyghost) __________ I had previously provided a few firmware zips for Oreo in the older firmware thread. Some users have/had a difficult time reading and...
forum.xda-developers.com
Post # 2 at the bottom WWE Full_3.16.401.2_NoBootImg_Twrp3.2.1-2_firmware.zip.
However, this always caused problems when flashing. I have no idea what kind of error was displayed. I think it was because of the unpacking. Then left it.
The latest stock ZIP (2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4_release_519849) contains the latest firmware anyway. So a clean basis should be created for a later CustomROM installation. Or do I have a mistake here?
What is going on here? Is there a limit to the number of flash operations?
Can't be that the device can only be operated with a stick.
In between the installation of the custom ROMs caused problems. But that always looked like errors when unzipping the images. After downloading the ZIP again, at least the installation went.
Basically I installed the ROMS from the external SD and previously deleted Dalvik, System, Cache, Data and Internal memory and formatted the data in order to really remove all remains of the previous installation.
I'm slowly getting fed up with the idea of buying the device new and setting it up based on its original condition.
Hi, I'd like to start off by saying I'm new here, and have went over all the newbie threads as best as I can. I appreciate how welcoming this forum is, I never took that much of a deep look at it besides looking at threads in the past for multiple things. Still very new to all this stuff in general. Due to being stuck rn, I cannot provide a proper signature, apologies.
Couple Days Ago- Unlocked bootloader on my Oneplus 7 Pro using adb, flashed TWRP for the then current version for the 7 Pro Guacamole referenced from the post here, then sideloaded Lineage through TWRP. Started using the device and it seemed to have went well and like a pretty average install as far as I can tell.
Note- I'm not sure if I installed TWRP properly, as I was able to boot into TWRP through power button and volume up, but I remember also accidentally booting into the Lineage Recovery at some point after my phone was already rooted after the next step, but idk honestly. I note this bc I seen that there might be another step to permanently install twrp once inside after flashing, but not sure, apologies. My lack of knowledge feels inexcusable with how abundant it is here.
I rooted the device soon after with magisk, which I installed the zip (which was simply placed in main directory) through TWRP, then finished the install in the OS and that seemed to be good. Mention I didn't actually know that the device was rooted after the first time, dumb ik, but I did this maybe 3 times before realizing that the device was indeed already rooted and I did it extra times.
Today I got the notification for a Lineage OS update in the OS. Because I know it's coming, yeah, ik how stupid this was to not make backups beforehand as I already have a good bit on there I don't wish to lose, although I have MEGA for all my super important stuff like my password database, etc. Needless to say, I have learned my lesson. Nonetheless, I downloaded the update and pressed the install button. It said installed and would need a reboot, so I did. Then it got stuck in the boot animation for 1.5+ hours.
Force shutting it off and into fastboot, I could boot into the updated lineage recovery, but no TWRP. I have tried reflashing the previous version of the lineage recovery and it did not make a difference. I also tried flashing the next newest version of TWRP for the 7 Pro running guacamole, but then I couldn't get any further than the bootloader.
I ended up reflashing the up to date version of the lineage recovery and it sat doing nothing for a while, so it's off now. I presume that Nebrassy and other devs for TWRP are working on a version for the new update, but idk how long that takes, not complaining though. (mad respect for all who make lineage, twrp and all this possible) (not to mention I don't even know the root of the problem)
Any thoughts or help would be much appreciated, and feel free to ask questions. I would preferably not have to wipe it all and restart, so I'm looking for solutions, although I'm willing to accept this might be for nothing and take the L. Lastly sorry if I have done anything "wrong" in this thread, lmk if I can do anything better, I appreciate it.