Database Develop

[ROM-STOCK] Amazon OS 8.4.3 (Flash .zip for TWRP) [07/11 - Version 8.4.3]

Amazon Stock OS for Kindle Fire HD 8.9 - Version 8.4.3
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
This flash .zip file contains the Amazon OS 8.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
NOTE FOR LTE USERS: This does *NOT* contain the wankit update for LTE modem firmware.
Download Information for OS 8.4.3:
Mirror 1: http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.4.3.zip
md5sum: d67ab5cd944dbf9d9509b44aa1d4a7e3
Download Information for OS 8.4.1:
http://d-h.st/VnR
md5sum: a39c815becf8517729c2baec2ad13582
OLDER VERSIONS:
Download Information for OS 8.3.1:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.3.1.zip
md5sum: 6a2584c9a52d9d57dc13e64e05558985
Download Information for OS 8.3.0:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.3.0.zip
md5sum: 9394219ae608bb73b292fcbb84d48aa2
Download Information for OS 8.1.4:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.1.4.zip
md5sum: c9e87973e42d6b34f8269469f9fb479a
INSTALLATION (TO REVERT TO AMAZON OS):
Place flash .zip file onto your SD card
Reboot into recovery
Wipe system
Use "INSTALL" and find the .zip file (NOTE: CM10.1 may create a "0" directory under /data/media so you may need to navigation up to /data/media and back down to find .zip)
Make sure to WIPE CACHE if you're currently on stock (and do a full FACTORY RESET for wiping data/cache if you're on CM10.1 going to this).
Reboot
Go back through the stock Amazon setup process

Works flawlessly thank you Hashcode!!

Works great - but not without a 'heart attack moment' first time around.
I pushed the kfhd8-amazon...zip to the /sdcard/download folder from a Windows box. It was put into /sdcard/0/download.
Once in TWRP, I naviguessed to the /download folder to install the old software - and the folder was blank (apparently TWRP defaulted to the /sdcard/download folder). Ok...Hashcode warned us about the duplicate folders in JellyBean, so I backed out of 'install' and used to file manager to find the kfhd8-ama...zip in the /sdcard/0/download folder. It was an easy click to select it to copy, then navigate to the 'other' download folder, then press paste. FAILED I tried again and that copy failed as well.
Navigating back to the 'install' menu refreshed the screen and the update software zip was magically there. Maybe the failed copy didn't really fail? Maybe the initial read of the /download folder failed and needed to be refreshed? Dunno.
But the flash worked perfectly. And it's apparently resilient enough to catch newb errors - I was so happy that the software appeared that I forgot to wipe the system again after installation. Pressing reboot to the system resulted in an attempted boot and a return to TWRP where I could give the system a good wipe. The next boot was normal.
Whew.

Does TWRP backup of CM10 work as other normal phones or we also need to take care of the "stack" file? because I saw these lines in the update-script. Will a backup/restore of CM10 overwrite this?
---------
run_program("/sbin/sh", "-c", "rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\\x00\\x50\\x7c\\x80' >>/tmp/stack ; done");
run_program("/sbin/dd", "if=/tmp/stack", "of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "bs=6519488", "seek=1", "conv=notrunc");
---------

thanks, will try this later...

stock room problem
Hello I opened this post: http://forum.xda-developers.com/showthread.php?p=38337627#post38337627
What can I do to solve. Thank you

Re: [ROM-STOCK] Amazon OS 8.1.4 (Flash .zip for TWRP)
field3d said:
Hello I opened this post: http://forum.xda-developers.com/showthread.php?p=38337627#post38337627
What can I do to solve. Thank you
Click to expand...
Click to collapse
You can start by following the instructions given to you in that thread and directing all non-development related questions to the Q&A forum.
Sent from my KFJWI using Tapatalk 2

I just flashed back to this until the CM built has working sound. I'm not sure if this is already known, but if you flash a ICS based gapps package on top of this you have all the gapps =D

vln004 said:
I just flashed back to this until the CM built has working sound. I'm not sure if this is already known, but if you flash a ICS based gapps package on top of this you have all the gapps =D
Click to expand...
Click to collapse
Seriously? And everything works? I already have everything installed but if this is true that would make going back and forth between cm and Amazon really easy

wojo797 said:
Seriously? And everything works? I already have everything installed but if this is true that would make going back and forth between cm and Amazon really easy
Click to expand...
Click to collapse
Only had about 30 minutes to play with it before going to bed. But everything that i tested worked fine. Google play installs apps fine, youtube works as expected, installed a couple other apps and everything works as it should.

vln004 said:
Only had about 30 minutes to play with it before going to bed. But everything that i tested worked fine. Google play installs apps fine, youtube works as expected, installed a couple other apps and everything works as it should.
Click to expand...
Click to collapse
So I bought a demo unit Kindle Fire HD 8.9 (you know, the ones in the store with just a demo OS installed) and I should have it by next week. When I root it I can install this ROM and everything works (sound, camera, HDMI etc.) just like a full one bought in the store?

OP updated for a new 8.3.0 stock ROM .zip file to flash in TWRP.
It includes the new kernel + stock ROM, but NOT the wankit update for LTE users.

Hashcode said:
OP updated for a new 8.3.0 stock ROM .zip file to flash in TWRP.
It includes the new kernel + stock ROM, but NOT the wankit update for LTE users.
Click to expand...
Click to collapse
Just install? Or wipe cache and dalvik? Thanks for doing all this work.. Very much appreciated

If you are on stock, then you can just install this over the top of 8.1.4. If you've been playtesting CM10.1 you will need to wipe data/cache.

Re: [ROM-STOCK] Amazon OS 8.3.0 (Flash .zip for TWRP) [04/02 - Version 8.3.0]
Hi,
Is it possible install flash plugin to use with DolphinHD? I ask this because i use Kindle to see NBA games from Game Time.
Sent from my Incredible S using xda premium

Running stock rooted so I simply installed this update over top..no cache or dalvik wipe. After reboot the play store kept force closing.went back into recovery and wiped cache and dalvik. Play store no longer force closing.maybe just isolated to me but I would wipe caches

wojo797 said:
Running stock rooted so I simply installed this update over top..no cache or dalvik wipe. After reboot the play store kept force closing.went back into recovery and wiped cache and dalvik. Play store no longer force closing.maybe just isolated to me but I would wipe caches
Click to expand...
Click to collapse
Good point. Adding wipe cache to the OP.

Wow, this is great, with 8.3.0!!
But I never succeeded downloading the file as everytime it stopped at 30%-70%. Anyone can help?

Finally I managed to download it through a proxy.

I am new to rooting and tablets. I cannot understand how to load "flash in TWRP". I try running adb commands in CMD but it says it is a unrecognized command. Can someone make this idiot proof? I am doing something wrong and I don't want to brick my kindle hd 8.9

[Q] CyanogenMod gets stuck at boot animation after update to 10.2

Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy

@Tomy_Delmar
Tomy, CyanogenMod is already custom ROM, there is always root access on it
Try it this way:
download Gapps for CM10.2x (Android 4.3.x) and paste them on your external SD card
put the card in your phone
run it in recovery mode
wipe cache and dalvik cache
flash Gapps for 4.3
wipe again cache and dalvik cache.
reboot
Post if it worked.

Tomy_Delmar said:
Hello
I have the problem that I cannot update my i9000 from CyanogenMod 10.1.3 to 10.2.0. After the update, Cyanogenmod doesn’t start anymore. It gets stuck at the boot animation: The blue CyanogenMod-mascot within the round rotating arrow. I waited 15min for it to start, then I left the phone for 2h and it still didn’t start.
I did the update as follows:
First, I tried to update with the automatic updater from CyanogenMod, but that didn’t work. It aborted and restarted CyanogenMod 10.1.3.
So I tried it manually with ClockworkMod (v6.0.3.6):
- wipe data / factory reset
- wipe cache partition
- advanced -> wipe dalvik cache
This message was shown: E:unknown volume for path [/sd-ext]
Dalvik cache wiped.
- install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
It aborted and the following message was shown:
This ROM uses an incompatible partition layout
Your /data will be wiped upon installation
Run this update.zip again to confirm install
- Did it again: install zip -> choose zip from sdcard -> cm-10.2.0-RC1-galaxysmtd.zip
Now the zip-file was installed completely.
- reboot system now
The result was that the phone got stuck at the boot animation.
Remarks:
- I didn’t do a backup of apps and data, because I didn’t have important data on the phone.
- I didn’t have root-rights in CM 10.1.3.
I tried it again with the stable version of CM 10.2.0. I didn’t have to install the zip twice anymore, but the phone still gets stuck at the boot animation. Wiping cache and dalvik cache again didn’t make it start.
I can still boot into ClockworkMod and it was also possible to go back to CM 10.1.3. Just CM 10.2 doesn’t start up.
What do I have to do to make CM 10.2 start up?
Thank you very much for your help.
Best regards
Tomy
Click to expand...
Click to collapse
As the partition layout is different in cm10.2, you should flash it at least 2 times and wait for system to be stable for about 15-20 minutes

Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy

Tomy_Delmar said:
Tetakpatak and Rohitdahiya, thanks for the reply and advice!
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
I tried again the update from CM 10.1.3 to 10.2:
- I downloaded cm-10.2.0-galaxysmtd.zip again and copied it to the internal SD-card of the phone.
- Restarted the phone into ClockworkMod recovery.
- wipe data / factory reset
- wipe cache partition
- wipe dalvik cache
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
- install zip -> choose zip from sdcard -> cm-10.2.0-galaxysmtd.zip
(Did it twice. Don’t know if necessary.)
Didn’t install Gapps.
- wipe cache partition
- wipe dalvik cache
- reboot system now
Unfortunately CM still gets stuck at the boot animation. The arrow has been rotating for over an hour now.
To my knowledge the Gapps are not mandatorily required to install CM. I could install CM 10.1.3 without the Gapps without any problems.
Could a full-wipe solve my problem?
ClockworkMod -> mounts and storage -> format /system …?
I have never done this before.
Or is there something else I can do?
Regards
Tomy
Click to expand...
Click to collapse
First of all, don't forget to quote the user whom you want to contact, because he don't get any notification until you quote. I was just checking around the questions and thus I saw this.
Sometimes, there is requirement of g-apps for the core system to be working ( Not sure in case of cm10.2). Try with g-apps (you may choose light package).
In my opinion, it should work. If not, try from the start ( flashing gingerbread with Odin with repartition ticked, then its root and finally cm10.2 from recovery)
Also make sure your handset is i9000 and you are using cm10.2 for the same.
And finally, All the best

CM doesn't neccesarily need Gapps to boot up. In fact most custom roms don't - they are still usable, just that everything Google-related doesn't work.
Its a bit odd seeing as how you've pretty much done what I would have done if I was installing CM to a Galaxy S. I can't think of any reason why it wouldn't work.
As far as I know as well, formatting /system is more of a last-resort method, not something you'd immediately do.
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Sent from my GT-P7510 using Tapatalk

Tomy_Delmar said:
In my previous post, I forgot to mention that I installed CyanogenMod without the Gapps. I’d like to try if an android-phone without the Gapps is still useful. Somehow I don’t like the data-collecting-mania of Google.
Click to expand...
Click to collapse
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.

Soryuu said:
However, I had a similar problem installing a rom onto my tablet - different device, I know, but try this anyway and see if you get anywhere:
1.) Go back into recovery if its still bootlooping
2.) Wipe data, cache, Dalvik (and this is after you've flashed the CM10.2 zip twice like you did)
3.) Reboot device without flashing Gapps - this is to see if it boots up.
Let us know what happens.
Click to expand...
Click to collapse
Unfortunately, Wiping data, cache and Dalvik cache again after I had flashed CM 10.2 didn’t make it start.

tetakpatak said:
Tomy, now it is getting clear- of course, I tought you already had Gapps on your CM10.1.3 installed so in such case they would definitely need to be updated to 4.3
Yes, the ROM shouold work perfectly fine also without Gapps
Your workflow sounds correct, but just to make sure: after first attempt to flash CM10.2 build, there should be a warning that all your data will be wiped, right? After that you must again choose the option "install zip" and install CM10.2. It will work this time.
If it doesn't work, download again the CM10.2 zip as it may be corrupted file. BTW, I didn't like that build for several reasons and returned to RC version.
If nothing helps, flash back your CM10.1.3 and restore your nandroid backup if important files were there. If the downgrade won't work for different partition of the /system, use my unbricking guide and revert to stock, then to CM10.1.3, then to CM10.2.
Keep step by step on the guide if you use it, it has important points to control before flashing. Flashing with re-partition needs always a PIT file, or with other words: without that file re-partition option mustn't be checked. Doing it simply by clicking the re-partition (like @Rohitdahiya adviced you to) without a PIT file checked under "PIT" would brick your i9000.
Click to expand...
Click to collapse
When I tried to flash CM 10.2 the first time – at that time RC1 was the newest version – I was asked to flash it a second time, which I did. To be precise, the following message was shown:
This ROM uses an incompatible partition layout
You /data will be wiped upon installation
Run this update.zip again to confirm install
This message hasn’t been shown again since then. I flashed CM 10.1.3 again and tried to flash 10.2 a second time, but the message wasn’t shown again.
Going back to CM 10.1.3 worked without any problem.
------------------------------------------
Now I have CM 10.2 on my phone and it starts normally
I flashed Stock-Android 2.3.6 with Odin (v1.82). Tetakpatak, thank you for the excellent guide and the video! As written in the guide, I used "s1_odin_20100512.pit" as PIT-file.
(I executed Odin on an old computer with Windows XP 32bit, as the guide says Odin 1.82 works better with Win XP.)
Then I installed CM 10.2 over Stock-Android 2.3.6. I followed the official instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd?setlang=en
(I executed Heimdall on my new computer with Windows 7. Heimdall 1.4RC2 doesn’t work on Win XP. If one executes Odin and Heimdall on the same PC, I could imagine this could lead to confusion, because Odin needs the Samsung-USB-drivers and Heimdall needs WinUSB. I’m not sure if this really leads to problems. But one should keep that in mind.)
I didn’t flash CM 10.1.3 before 10.2, because I didn’t need to restore a nandroid backup previously made with CM 10.1.3. There were no important data on the phone.
Many thanks to all who gave me advice and helped my solving the problem!
Tomy

HELP MEEE
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!

Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
This is the forum for the original Galaxy S, not the Nexus 5, sorry mate
However I think your problem can be fixed by doing a full data/cache wipe so it might be worth a shot

Flash Boot.Img. This might solve the bootloop!
I think, You just need to flash the boot.img (available in the Cynogen Bundle Zip Folder) after installing Cynogen Mod. Me too got stuck on the animation part for a long time. Then I found out this:
CyanogenMod builds for endeavoru currently do NOT support any bootloader version number below: HBOOT 1.28. As the device is S-ON (security-on bootloader), for a working installation you must extract the boot.img from the installer zip and run fastboot flash boot boot.img from fastboot mode.
Source: Cynogen Mod Wiki

Pure_Android said:
I put on TWRP 2.6.3.0 on my Nexus 5 (I used towerlroot succesfully) and i tried wiping as you should, i noticed i loaded an old twrp so i quickly powerd off my Nexus5. When i loaded, every app had a "Google play services has stopped" error and some would force close. I reloaded TWRP and tried to flash cyanogenmod and gapps, succelfully they installed. Now cyanogenmod is stuck in the boot animation and i dont know to update TWRP, HELPP PLEASSE!!!!
Click to expand...
Click to collapse
Which version of CyanogenMod are you using?

[Q] What's NOT getting wiped when I flash?

I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?

jran0880 said:
I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?
Click to expand...
Click to collapse
Sounds like /data isn't getting wiped or formatted.

jran0880 said:
I have successfully flashed @shinobisoft's latest CM11 build and it runs fine. However, I wanted to do a "clean" install. I used philz recovery to install the new ROM. Prior to install, i used the clean up for new ROM install option and let it run through. To be sure everyhthing was "clean", I also wiped dalvik, cache, and even user media. I also formatted everything EXCEPT external SD, as that is where the .zips are located for install.
I installed ROM and gapps "modular" as well a chrome add-on, and rebooted phone.
When ROM loaded, I was greeted by the "choose language" screen, which is what i expected to see. I let it "settle" (Galaxy S2 experience) for about 15 minutes or so before I touched anything. When I went to complete setup, my wifi was already connected and the phone was linked to my account. It was using Apex launcher and the settings I used prior to updating.
What am I NOT wiping/formatting prior to installation?
Click to expand...
Click to collapse
One other thing... Have you set up Google to track your installed apps/etc? If so, Google will automatically restore them.

Failbringer60 said:
I did a full wipe for the initial install. But for the newest build i wiped system only and flashed on top of the previous build. I can do a full wipe again and reinstall the newest build to see if it corrects my issues. But i can assure you i wiped everything when i installed the previous build.
Click to expand...
Click to collapse
shinobisoft said:
Umm... I'm seen a bunch of references in your posted log that refer to the old sdcard path ( as in stock, /storage/external_SD. New path is : /storage/sdcard1 ). This is telling me that you did NOT format your /system and or /data partition when you installed CM for the first time. Obviously the only way to remedy this is to do a fresh installation following the instructions I posted in the OP.
Click to expand...
Click to collapse
shinobisoft said:
One other thing... Have you set up Google to track your installed apps/etc? If so, Google will automatically restore them.
Click to expand...
Click to collapse
I changed the "auto restore" setting so it won't automatically install my apps and tried another "clean" install with the same results. It's almost like I'm restoring from a previous back up! I made sure to wipe and format everything twice just to be certain. Installed only CM and gapps zips, wiping dalvik and cache before booting system. My result was the same as previous..... Choose language.... WiFi connects, and my settings restore.... I am NEVER asked to login to my Google or Cyanogen account(s)......
I'm about to back up and wipe everything, use fastboot to format the partitions? Ideas? Thoughts? Suggestions?
Perhaps restore my "rooted factory ROM" from TWRP back up and start from there? Or restore from .kdz?

Maybe try a factory reset from Settings after installing? Kind of a long shot but that's what I had to do after flashing back to stock when nothing seemed to have changed ...

5.1.2 - Custom Rom (SlimRom) - Flashfire Problem

Hey everyone,
I recently got my Amazon Fire on the Prime Day. I did a lot of mistakes on my way to rooting it etc, but figured everything out by browsing the forums so far.
Unlike with my earlier issues, I am not getting a problem that I have no found a solution via the forums yet.
The problem is that I am getting stuck in a boot-loop (Amazon restarts soon after the logo (amazon) shows up) - I am assuming it has something to do with the fact that when I try to flash via FlashFire, I get the message that I have modified my /ota etc.
This I find confusing because my process doesn't seem to be any different than the rest.
Files I am using: Amazon Fire 5.1.2 (Sideload) - RootJunky's Supertool - Google Playstore - Flashfire 0.51 - Slimrom 0.15 UNOFFICIAL + Slimrom Mini GApps BETA 5.1
Process:
Sideload 5.1.2 -> Delete Data -> Delete Cache -> Restart (STOCK 5.1.2)
Use RootJunky's SuperTool to install KingRoot, replace it with SuperSu.
RESTART
Use SuperTool to block Amazons OTA Updates
Since the SuperTool does not currently download the 0.51V of flashfire, I manually download FlashFire by INSTALLING GOOGLE PLAYSTORE VIA SUPERTOOL
RESTART
Install FlashFire -> in FlashFire (order from top to bottom) -> Wipe (System Data, 3rd Party Apps, Dalvik Cache, Cache Partition, Cache Partition Format) -> Flash ZIP or OTA (Auto-Mount + Mount /system read/write)
START FLASH
Flash proceeds and finishes wipe and installs flashfire zip, then moves on the to the google apps and then reboots into a bootloop.
EDIT: Clarification: I'm trying to flash SlimLP.

iNETglow said:
Hey everyone,
I recently got my Amazon Fire on the Prime Day. I did a lot of mistakes on my way to rooting it etc, but figured everything out by browsing the forums so far.
Unlike with my earlier issues, I am not getting a problem that I have no found a solution via the forums yet.
The problem is that I am getting stuck in a boot-loop (Amazon restarts soon after the logo (amazon) shows up) - I am assuming it has something to do with the fact that when I try to flash via FlashFire, I get the message that I have modified my /ota etc.
This I find confusing because my process doesn't seem to be any different than the rest.
Files I am using: Amazon Fire 5.1.2 (Sideload) - RootJunky's Supertool - Google Playstore - Flashfire 0.51 - Slimrom 0.15 UNOFFICIAL + Slimrom Mini GApps BETA 5.1
Process:
Sideload 5.1.2 -> Delete Data -> Delete Cache -> Restart (STOCK 5.1.2)
Use RootJunky's SuperTool to install KingRoot, replace it with SuperSu.
RESTART
Use SuperTool to block Amazons OTA Updates
Since the SuperTool does not currently download the 0.51V of flashfire, I manually download FlashFire by INSTALLING GOOGLE PLAYSTORE VIA SUPERTOOL
RESTART
Install FlashFire -> in FlashFire (order from top to bottom) -> Wipe (System Data, 3rd Party Apps, Dalvik Cache, Cache Partition, Cache Partition Format) -> Flash ZIP or OTA (Auto-Mount + Mount /system read/write)
START FLASH
Flash proceeds and finishes wipe and installs flashfire zip, then moves on the to the google apps and then reboots into a bootloop.
EDIT: Clarification: I'm trying to flash SlimLP.
Click to expand...
Click to collapse
Try simplifying initial ROM flash:
- reload 5.1.2 to begin with a clean slate
- don't register device with Amazon
- use SuperTool to root and subsequently transition to SuperSU
- don't install any Google components
- sideload FlashFire 0.51 from apkmirror
- reboot device; launch FlashFire
- wipe system/apps/dalvik/cache (first action)
- flash SlimLP using default options (second action)
- do NOT flash a GAaps package; do that later
- add a second wipe of dalvik/cache (last action)
Post observations and results.

Davey126 said:
Try simplifying initial ROM flash:
- reload 5.1.2 to begin with a clean slate
- don't register device with Amazon
- use SuperTool to root and subsequently transition to SuperSU
- don't install any Google components
- sideload FlashFire 0.51 from apkmirror
- reboot device; launch FlashFire
- wipe system/apps/dalvik/cache (first action)
- flash SlimLP using default options (second action)
- do NOT flash a GAaps package; do that later
- add a second wipe of dalvik/cache (last action)
Post observations and results.
Click to expand...
Click to collapse
Procedure Observations:
- Reload 5.1.2: Standard Procedure - no problems.
- Don't register device with Amazon: Standard Procedure - no problems.
- RootJunky SuperTool Root: Standard Procedure - no problems.
- Don't install Google Apps: Standard Procedure - no problems.
- Sideload Flashfire 0.51V from apkmirror: Standard Procedure - no problems.
- Reboot Device; Launch Flashfire: Standard Procedure - no problems.
- Wipe system/apps/dalvik/cache (first action): Standard Procedure - no problems.
- Flash SlimLP using default options (second action): Standard Procedure - no problems.
- Do NOT flash a GApps package; do that later: Standard Procedure - no problems.
- add a second wipe of dalvik/cache (last action): Standard Procedure - no problems.
Note: Still warns me about having a modified /system, /vendor, or /oem partition.
Went into boot-loop when trying to flash SlimLP - used auto mount and mount system/read write. Gonna try again without any option as that was what FlashFire showed me when first clicking the .ZIP in my SD Card

Tried again without checking any of the options like it is in default. Still getting the same notification regarding modified files and it still crashes in the middle of the SlimLP set-up.. :/
EDIT: Tried without Auto-Mount but with system read/write - no warning regarding OTA notifications this time. Still crashed when scrolling through the SlimLP flash text. - Gonna check md5 for good measure.
EDIT2: md5 is correct... :/
EDIT3: Still looking for a solution, if anyone has any idea - feel free to post it here, im trying out anything at this point.

I tried for an entire day to literally do exactly what you are trying. I finally gave up and went with the Nexus ROM.

iNETglow said:
Tried again without checking any of the options like it is in default. Still getting the same notification regarding modified files and it still crashes in the middle of the SlimLP set-up.. :/
EDIT: Tried without Auto-Mount but with system read/write - no warning regarding OTA notifications this time. Still crashed when scrolling through the SlimLP flash text. - Gonna check md5 for good measure.
EDIT2: md5 is correct... :/
EDIT3: Still looking for a solution, if anyone has any idea - feel free to post it here, im trying out anything at this point.
Click to expand...
Click to collapse
gooberedup said:
I tried for an entire day to literally do exactly what you are trying. I finally gave up and went with the Nexus ROM.
Click to expand...
Click to collapse
In the absence of further data points (ie: recent success stories) I'd say something is amiss with the most recent rom zip. Not much you can do until maintainer chimes

Magisk Installing OTA on Pixel XL 1

Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?

niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...

Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?

niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.

* DELETED *

Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.

niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...

Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.

niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.

Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?

niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.

Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.

system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse

automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.

Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?