Develop Bugs

[Q] Will Unroot return the One-Year Warranty?

I need help to know if I unroot will restore my Warranty because I have trouble with charging my Kindle Fire. The only warranty I have is the One-Year Limited Warranty from Amazon. I need to send my Kindle for Replacement and I need to know if I can erase EVERYTHING so that there is no trace that I ever rooted my kindle. If I can't, is there a way to un-void my warranty?

I've done this before, you will have no problems with getting your kindle returned as long as you unroot
follow these steps
http://forum.xda-developers.com/showpost.php?p=22663761&postcount=7

If your running anything else besides rooted stock include a system wipe to the other scheme of wipes for good measure.

when wiping the system, there is a chance to brick your kindle and need a factory cable tho. I've sent two kindles back to amazon for repair/replacement without system wipes and have never had a problem.
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
I believe it's happens when you get a bad flash from the amazon stock update. So if you are going to include a system wipe it'd probably be good to verify the md5 from amazon?

YES
I think that if you wipe it and unroot then youll be fine Amazons customer service is incredible hahaha, i have bricked mine when i tried to root it for my first time and they sent me a new one at no cost to me hahaha. So yeah i think your good

chris_m128 said:
when wiping the system, there is a chance to brick your kindle and need a factory cable tho. I've sent two kindles back to amazon for repair/replacement without system wipes and have never had a problem.
---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------
I believe it's happens when you get a bad flash from the amazon stock update. So if you are going to include a system wipe it'd probably be good to verify the md5 from amazon?
Click to expand...
Click to collapse
Not to argue but unless you incorrectly flash stock there is virtually no risk in wiping the system prior to flashing stock and it certainly won't soft brick it requiring a factory cable. That only happens when you fail to wipe correctly. Anyone who experienced soft brickage after wiping the system and flashing stock messed up somewhere else in the procedure.

when you wipe system and you mess something up in a flash (hence why I said a bad flash) , you cannot fix it without a factory cable(when reverting back to stock amazon because it wipes recovery) . i know this for a fact. Thats why i said to make sure you set up "update.zip" properly. And as 99 percent of guides on here for reverting back to stock don;t mention wiping system. I believe it to be an unnecessary step.
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
Will you not get the exec '/system/bin/sh; failed : no such file or directory error?

No the error you state will not occur that is the result of a corrupt or missing shell exactly what happens when you fail to wipe correctly. Let me add proper order of wipes helps as well factory reset, cache, dalvik then the system. Always front to back not back to front I'm sure that doesn't require further explanation.

Okay, then but do you know if I will receive another 2ND Gen. Kindle? I really like that Kindle 2 has 1GB of RAM and 1.2Ghz CPU but there isn't much development for it. Do you think the Kindle 2 is much better than the Kindle 1? I ask this question because I heard(or rather read) that some people who send the Kindle for Replacement receive a Kindle 2.
Another thing is that all I have to do is like flashing any ROM but rather the Kindle Update and my Kindle will be unrooted and that's it? Or is there something else because not all the info given is as helpful. But if you need more info about my kindle is as follows:
Current Kindle Fire 1st Gen.
ROM: SmoothRom 1.2
Recovery: Team Win Recovery Project (TWRP) 2.2.2.1
Bootloader : FFF v.1.4a
Previous Kindle Update: Kindle Fire ver.6.3.1
Root Status: Permanent Root
Sent from my Amazon Kindle Fire using xda app-developers app

chris_m128 said:
I've done this before, you will have no problems with getting your kindle returned as long as you unroot
follow these steps
http://forum.xda-developers.com/showpost.php?p=22663761&postcount=7
Click to expand...
Click to collapse
No, my Kindle doesn't have the same TWRP and Boot loader so I don't think that method will work for me.
Sent from my Amazon Kindle Fire

[Q] Steps for dual booting OS's with our dual partitions?

I searched thread titles for "dual" and found minor discussions but no explanations.
So I'm running with the assumption we can dual boot and I'm just now interested in this.
So what are the steps to dual boot?
I have TWRP RC1 and I flashed a ROM on A.
Then I rebooted to TWRP and still on slot A, I flashed another ROM and it should have installed on B.
I ended up trying it a few different ways.
But one ROM install always seemed to kill the other ROM install?
It takes so long to test that I said fuggit and decided to ask the forum for help. :good:

Any progress with this? I'm looking to dual boot also. I have heard that both ROMs must be of the same Android version, but looking for more details.
Please reply or post a link, Thanks.

davidbanks said:
Any progress with this? I'm looking to dual boot also. I have heard that both ROMs must be of the same Android version, but looking for more details.
Please reply or post a link, Thanks.
Click to expand...
Click to collapse
I have done this. Just about the only way to use it without problems is to run stock on both slots. One for root and exposed whatever.. The other for no root for android pay and other apps that require safety net and stock build prop. This is the only practical dual boot setup seeing as how both slots share data.

DR3W5K1 said:
I have done this. Just about the only way to use it without problems is to run stock on both slots. One for root and exposed whatever.. The other for no root for android pay and other apps that require safety net and stock build prop. This is the only practical dual boot setup seeing as how both slots share data.
Click to expand...
Click to collapse
IDK what you are talking about. Magisk works with everything. Netflix, Android pay and safetynet. I got it running. As far as dual boot. It will never happen. A/B partitions use the same system. They have the separation for updating and that's it. No way to dual boot two different roms. People confuse A/B partition scheme with dual boot. Yes there is two slots. But only for updating. Research it. If we had a cache partition scheme, yes you can. You allocate part of each partition into another partition that allows for the second rom. And depending on how big and what you use, you could even triple boot. Say the s8 I had could be dual boot. Pixel XL runs a A/B partition with no cache partition.

What?
S8rooted&tooted said:
IDK what you are talking about. Magisk works with everything. Netflix, Android pay and safetynet. I got it running. As far as dual boot. It will never happen. A/B partitions use the same system. They have the separation for updating and that's it. No way to dual boot two different roms. People confuse A/B partition scheme with dual boot. Yes there is two slots. But only for updating. Research it. If we had a cache partition scheme, yes you can. You allocate part of each partition into another partition that allows for the second rom. And depending on how big and what you use, you could even triple boot. Say the s8 I had could be dual boot. Pixel XL runs a A/B partition with no cache partition.
Click to expand...
Click to collapse
The topic is dual booting the Pixel, strange tangent to Magisk by yourself, but you got it running! Oh, wait up, you're still on that diverted tangent. So no way to boot 2 different ROMS. I did research it. You go on to say "If we had a cache pardition ...", which we do, or am I misunderstanding the "Wipe Cache Partition" command on the Pixel? So we can dual boot! Or triple boot even! Oh, hold on again, now we don't have a cache partition? Pixels do have A/B partition as you call it, but within those partitions, are all the partitions we are used to (tho I think a couple are shared between A & B). So, I'll just get Magisk, that works with everything!

No cache partition.
---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------
Go develop it. Dualbooting cannot happen for reasons I explained above. There is no cache partition and or image. Please show me. Dav cache isn't a cache partition. But hey new developments are discovered everyday. Maybe next you could reinvent the wheel. It has gone on long enough without you reinventing it. Lol.

Supernoobsammyson said:
No cache partition.
---------- Post added at 12:50 PM ---------- Previous post was at 12:47 PM ----------
Go develop it. Dualbooting cannot happen for reasons I explained above. There is no cache partition and or image. Please show me. Dav cache isn't a cache partition. But hey new developments are discovered everyday. Maybe next you could reinvent the wheel. It has gone on long enough without you reinventing it. Lol.
Click to expand...
Click to collapse
Hey air needs to be reinvented too. Not enough going to your brain.
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
Also tampons. Reinvent those too while you are using them.
---------- Post added at 01:08 PM ---------- Previous post was at 12:59 PM ----------
https://source.android.com/devices/tech/ota/ab
Go read yourself from Android. What an AB partition is. No cache partition by itself.

I think we can safely say this question has been answered. Let's move on, the gentleman was right. Dual booting isn't possible , at least not right now.

I am able to duel boot on my pixel xl (was accidental but messed up something during installing lineage 16 and now have 2 versions 1 new install and 1 upgrade install)

S8rooted&tooted said:
If we had a cache partition scheme, yes you can. You allocate part of each partition into another partition that allows for the second rom. And depending on how big and what you use, you could even triple boot. Say the s8 I had could be dual boot. Pixel XL runs a A/B partition with no cache partition.
Click to expand...
Click to collapse
Is there a way to do it?
(And if it is no possible maybe it is possible to simulate a partition like the modules of magisk?)

Mordechay said:
Is there a way to do it?
(And if it is no possible maybe it is possible to simulate a partition like the modules of magisk?)
Click to expand...
Click to collapse
ya sorry i reformatted my pixel xl gen 1 and installed it once. So not sure how I did it.

July Verizon Update running very hot!

Can I just flash the June update and go back?

No issues when I used the July update (non-Verizon), but yes you can go back

If you don't mind setting up your phone again you might want to try a factory reset before going back to June. Sometimes after an OTA update or an accumulation of OTA updates over time something in the phone gets corrupted (cache, old app data, code that isn't properly updated or erased in an update) and the best thing to do is a factory reset to start fresh.

rickysidhu_ said:
No issues when I used the July update (non-Verizon), but yes you can go back
Click to expand...
Click to collapse
Thank you for responding.

jhs39 said:
If you don't mind setting up your phone again you might want to try a factory reset before going back to June. Sometimes after an OTA update or an accumulation of OTA updates over time something in the phone gets corrupted (cache, old app data, code that isn't properly updated or erased in an update) and the best thing to do is a factory reset to start fresh.
Click to expand...
Click to collapse
That's a good suggestion. Thanks for responding.

STraver said:
Can I just flash the June update and go back?
Click to expand...
Click to collapse
Mine did as well, I suspected teh July update.
5 days in though it seems to have cooled off and is working at the temps I am accustomed to ~30c at idle.

parakleet said:
Mine did as well, I suspected teh July update.
5 days in though it seems to have cooled off and is working at the temps I am accustomed to ~30c at idle.
Click to expand...
Click to collapse
Okay thanks. That's good to know. For now I have flashed back to June. I may flash July and factory reset as was suggested above. For the past few months I have been updating by removing the "-w" from the flashall batch file and maybe it's caught up with me. I also tried wiping the davlik cache in twrp but that doesn't seem to work.

STraver said:
Okay thanks. That's good to know. For now I have flashed back to June. I may flash July and factory reset as was suggested above. For the past few months I have been updating by removing the "-w" from the flashall batch file and maybe it's caught up with me. I also tried wiping the davlik cache in twrp but that doesn't seem to work.
Click to expand...
Click to collapse
Try just clearing your cache partition from settings > storage. It may help in some cases too if cache is corrupted.
Factory reset will pretty much guarantee fix.

STraver said:
That's a good suggestion. Thanks for responding.
Click to expand...
Click to collapse
You're welcome.
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
milan187 said:
Try just clearing your cache partition from settings > storage. It may help in some cases too if cache is corrupted.
Factory reset will pretty much guarantee fix.
Click to expand...
Click to collapse
You might be right that adding -w caused your problem. There is always a possibility that some user data in an app that gets saved can cause problems after the phone is updated.

jhs39 said:
You're welcome.
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
You might be right that adding -w caused your problem. There is always a possibility that some user data in an app that gets saved can cause problems after the phone is updated.
Click to expand...
Click to collapse
Well I factory reset and installed the July update. The phone is fine now and not not hot but it seems a lot faster too. The only issue I ran into was that evidently my apps weren't being backed up to my google account, so I had to manually install them again. Thanks for your advice!

STraver said:
Well I factory reset and installed the July update. The phone is fine now and not not hot but it seems a lot faster too. The only issue I ran into was that evidently my apps weren't being backed up to my google account, so I had to manually install them again. Thanks for your advice!
Click to expand...
Click to collapse
I've had that happen after a factory reset or Rom flash in the past too even though I knew my apps were being backed up--they are by default unless you turn the feature off. I don't know why that happens but sometimes it does. I'm glad everything is working fine now. Sometimes giving your phone a fresh start by doing an occasional factory reset or completely clean flash is the best thing you can do. The fact that it seems to be running faster now is very likely true. Again, glad you got it sorted out. I'm actually running the beta of O and if you like how the Pixel runs on Nougat I think you will be even happier when O officially rolls out in August. The boot time on O is almost instant, battery life is slightly better and should improve more if more apps optimize their code for O, and the phone runs very snappy even though O is still in beta.

jhs39 said:
I've had that happen after a factory reset or Rom flash in the past too even though I knew my apps were being backed up--they are by default unless you turn the feature off. I don't know why that happens but sometimes it does. I'm glad everything is working fine now. Sometimes giving your phone a fresh start by doing an occasional factory reset or completely clean flash is the best thing you can do. The fact that it seems to be running faster now is very likely true. Again, glad you got it sorted out. I'm actually running the beta of O and if you like how the Pixel runs on Nougat I think you will be even happier when O officially rolls out in August. The boot time on O is almost instant, battery life is slightly better and should improve more if more apps optimize their code for O, and the phone runs very snappy even though O is still in beta.
Click to expand...
Click to collapse
Interesting. So O is supposed to become available in August. Will my older apps still work or will they all have to be updated by the developers? Also- for future updates would I be better off doing an OTA vs a complete flash (with the -w taken out)? In any case it sounds like at least every other month I should do a reset and reinstall anyway. What is the risk in just not updating every month? Thanks!

STraver said:
Interesting. So O is supposed to become available in August. Will my older apps still work or will they all have to be updated by the developers? Also- for future updates would I be better off doing an OTA vs a complete flash (with the -w taken out)? In any case it sounds like at least every other month I should do a reset and reinstall anyway. What is the risk in just not updating every month? Thanks!
Click to expand...
Click to collapse
I've encountered a handful of apps that don't work on O but they probably will by the official launch date. But an app being optimized to help provide better battery life is something that goes on in the background that you won't notice unless you are a programmer that can analyze code or knowledgeable tech writers shame app devs publicly who don't do it. Android O has the ability to limit an apps background processes so it uses less battery but my understanding is that it only happens if the app developers voluntarily write code that allows O to do that to the app and a lot of devs are probably not going to do that if it is voluntary.
I'm not sure what your setup is but if you are manually flashing updates presumably you have a custom recovery and possibly root. Some Pixel users have reported successfully flashing OTA updates anyway because of the dual partitions on the Pixel but it wipes out your custom recovery and root and returns you to full stock and I'm not sure doing that works reliably. I don't know that the Flashfire/Flashify (I don't remember which app goes with TWRP) works on the Pixel. I don't have any experience flashing OTA updates manually via bootloader rather than the full monthly update. Personally I was never a fan of removing -w from a full flash because it can always lead to potential problems that aren't necessarily completely obvious. I always prefer to clean flash to give the phone a clean start, but that's just my own preference. I didn't like to dirty flash custom Roms either --i would always do a clean flash every month and set up my phone from scratch.

jhs39 said:
I've encountered a handful of apps that don't work on O but they probably will by the official launch date. But an app being optimized to help provide better battery life is something that goes on in the background that you won't notice unless you are a programmer that can analyze code or knowledgeable tech writers shame app devs publicly who don't do it. Android O has the ability to limit an apps background processes so it uses less battery but my understanding is that it only happens if the app developers voluntarily write code that allows O to do that to the app and a lot of devs are probably not going to do that if it is voluntary.
I'm not sure what your setup is but if you are manually flashing updates presumably you have a custom recovery and possibly root. Some Pixel users have reported successfully flashing OTA updates anyway because of the dual partitions on the Pixel but it wipes out your custom recovery and root and returns you to full stock and I'm not sure doing that works reliably. I don't know that the Flashfire/Flashify (I don't remember which app goes with TWRP) works on the Pixel. I don't have any experience flashing OTA updates manually via bootloader rather than the full monthly update. Personally I was never a fan of removing -w from a full flash because it can always lead to potential problems that aren't necessarily completely obvious. I always prefer to clean flash to give the phone a clean start, but that's just my own preference. I didn't like to dirty flash custom Roms either --i would always do a clean flash every month and set up my phone from scratch.
Click to expand...
Click to collapse
Okay that's good to know thank you!

You're welcome.

Stuck at android is starting...

So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?

jlee08517 said:
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
Click to expand...
Click to collapse
I have the same problem on LineageOS. I even removed password before booting to TWRP, which usually caused the encryption message in twrp asking for a password.

jlee08517 said:
So, after feb OTA, my TWRP decided to not decrypt my partition anymore . So I went ahead and deleted Locksettings.db, locksettings.db-wal, and locksettings.db-shm in /data/system.
Now the problem begins. I rebooted my phone and now the phone is stuck at "android is starting" of course I did not backup what I deleted.
I flashed-all without wiping but it is still doing the same thing. Any idea out there that I could do something without wiping my phone?
Click to expand...
Click to collapse
Oh boy! Your the first I've seen with this one. I've used that method on the 6p many many times without issue. The P2XL is a different beast evidently. I'm sure the code master guys could figure it out, but that's not me. Did you make a backup before you started (S.O.P)?? I always do that before any update, and then move it to the pc before I begin. Been burned to many times with this stuff. I'm afraid the only advice I can give is to do a clean install of the latest update, then restore your data from a previous backup through twrp. Sorry my friend...been there...done that! ??
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Btw...this is a known issue with twrp now until it's updated. You have to remove all lock screen security in order to use TWRP effectively. Unfortunately, that does you no good I know. But, at least, now you know.

Badger50 said:
Oh boy! Your the first I've seen with this one. I've used that method on the 6p many many times without issue. The P2XL is a different beast evidently. I'm sure the code master guys could figure it out, but that's not me. Did you make a backup before you started (S.O.P)?? I always do that before any update, and then move it to the pc before I begin. Been burned to many times with this stuff. I'm afraid the only advice I can give is to do a clean install of the latest update, then restore your data from a previous backup through twrp. Sorry my friend...been there...done that! ??
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
Btw...this is a known issue with twrp now until it's updated. You have to remove all lock screen security in order to use TWRP effectively. Unfortunately, that does you no good I know. But, at least, now you know.
Click to expand...
Click to collapse
Well of course I made a twrp backup on the device before I did all this but I can't get to any of those since twrp can't decrypt...
Remember I deleted the locksettings since twrp won't take my pattern? Haha it was just unlucky on my part.

jlee08517 said:
Well of course I made a twrp backup on the device before I did all this but I can't get to any of those since twrp can't decrypt...
Remember I deleted the locksettings since twrp won't take my pattern? Haha it was just unlucky on my part.
Click to expand...
Click to collapse
Wasn't trying to criticize your method, but you'd be surprised how many don't do backups then flash away...then something goes wrong, and, well, you know the rest. Since you tried dirty flashing the factory image, I'm afraid all you can do is clean instal the factory image and wipe it clean. Stupid question, but if you fastboot twrp again, are you still in the same boat? Probably so, but thought I'd ask.

Badger50 said:
Wasn't trying to criticize your method, but you'd be surprised how many don't do backups then flash away...then something goes wrong, and, well, you know the rest. Since you tried dirty flashing the factory image, I'm afraid all you can do is clean instal the factory image and wipe it clean. Stupid question, but if you fastboot twrp again, are you still in the same boat? Probably so, but thought I'd ask.
Click to expand...
Click to collapse
Ah I didn't mean to come off that way. It's all good. Yeah I probably should write a PSA on twrp about this. So I went back to twrp and everything is gibberish since it's encrypted. I tried adb but it wasn't able to find the /sdcard path. I'm guessing that's also because the device was not being decrypted? And i tried to reboot into the safe mode. All kinds of mess. I just gave up and formatted the device. There goes all my /sdcard stuff.... I really need to start backing up titanium into the cloud..

jlee08517 said:
Ah I didn't mean to come off that way. It's all good. Yeah I probably should write a PSA on twrp about this. So I went back to twrp and everything is gibberish since it's encrypted. I tried adb but it wasn't able to find the /sdcard path. I'm guessing that's also because the device was not being decrypted? And i tried to reboot into the safe mode. All kinds of mess. I just gave up and formatted the device. There goes all my /sdcard stuff.... I really need to start backing up titanium into the cloud..
Click to expand...
Click to collapse
Sorry man, that sucks! I've done that more times than I can remember. Going forward, after I backup everything, including all my apps on TiBu, I save my TiBu file to my pc, then transfer it back after I'm back up and running. Best of luck to ya bro ?

A similar saga can be found here. For an encrypted data partition there is still no solution, as it seems, see my posting in that same thread.

VZW Note 8 doesn't run well on TracFone after updates

So my uncle's Verizon Note 8 running well on TracFone had not gotten an update since it was purchased new. It was running the software it originally shipped with.
I put my Verizon sim in it and was able to update it to current software.
After doing all this his phone will not run properly on TracFone. Data is very slow. I'm trying to figure out what happened and if it is fixable....? TIA

I would first try going into the System Recovery and wipe the cache. Reboot the phone and see if that helps. If not, there is a chance that you may have to do a factory reset. If you use Samsung SmartSwitch, you can back up practically everything to the SD card and be able to restore it.
---------- Post added at 01:31 ---------- Previous post was at 01:17 ----------
It's also possible that the APN settings may have been changed when you put your Verizon SIM card in it. Check the APN settings to make sure they are correct: https://bestmvno.com/apn-settings/page-plus-cellular-apn-settings/

mikeyk101 said:
I would first try going into the System Recovery and wipe the cache. Reboot the phone and see if that helps. If not, there is a chance that you may have to do a factory reset. If you use Samsung SmartSwitch, you can back up practically everything to the SD card and be able to restore it.
---------- Post added at 01:31 ---------- Previous post was at 01:17 ----------
It's also possible that the APN settings may have been changed when you put your Verizon SIM card in it. Check the APN settings to make sure they are correct: https://bestmvno.com/apn-settings/page-plus-cellular-apn-settings/
Click to expand...
Click to collapse
Thanks for responding. I've tried all these things and no luck at all.