KFFOWI Stuck at Fire boot animation - Which version to restore? - Fire Q&A, Help & Troubleshooting

Hello,
I have a KFFOWI which I rooted some months ago with Superjunky tool, and it worked great. Recently I lost root following Supersu messy update. I tried today to restore root with Superjunky tool : King root rooted succesfully, then when it was time to install supersu and delete Supersu something went wrong, script maybe didn't have root access, well I don't know.
My device is now stuck at the Fire boot animation. I'm ready to restore a stock version, but how can I be sure of the one which was installed, as I don't want to restore a different version and hard brick ? Is there a way from recovery or bootloader to identify firmware version ?
Any help will be appreciated.

Displaying logs under recovery, I think I identified version : 5.1.1

madxxcow said:
Hello,
I have a KFFOWI which I rooted some months ago with Superjunky tool, and it worked great. Recently I lost root following Supersu messy update. I tried today to restore root with Superjunky tool : King root rooted succesfully, then when it was time to install supersu and delete Supersu something went wrong, script maybe didn't have root access, well I don't know.
My device is now stuck at the Fire boot animation. I'm ready to restore a stock version, but how can I be sure of the one which was installed, as I don't want to restore a different version and hard brick ? Is there a way from recovery or bootloader to identify firmware version ?
Any help will be appreciated.
Click to expand...
Click to collapse
madxxcow said:
Displaying logs under recovery, I think I identified version : 5.1.1
Click to expand...
Click to collapse
5.1.1 likely references the underlying version of Android which FireOS and all custom ROMs for this device are built upon.
To be absolutely safe reload FireOS 5.3.1 which is the highest rootable build. Before doing that try a factory reset (clearing cache/data) from the recovery menu. Often does the trick.

Thanks. Installed 5.3.1.
Then several attempts to root it with Supertool/King root, around 6 or 7.
Everything works great now.

Related

[Q] issue rooting with mskip's toolkit

Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
It sounds like CWM hasn't reflected TWRP, have you tried using the tool kit again just to flash CWM? Or how about flashing CWM via Odin using the recovery in the below thread?
http://forum.xda-developers.com/showthread.php?t=2232856
Sent from my Nexus 7 using xda app-developers app
OCTAF1SH said:
Hi guys,
First post here, so am not allowed to post in toolkit forum.
Having wanted to root several android devices in the past, I have lurked here for quite a while, but finally got round to rooting my s iii mini two days ago. My firmware updated to amg3, but I followed the advice in the toolkit and used the closest match. Everything seems to be working fine.
When it came to flashing a new recovery through odin, I chose twrp, and superSU and it failed. When opening superSU it gave a message about no binaries being present. I decided to reinstall the toolkit, this time flashing CWM and superuser.
This worked perfectly! I disabled superSU, as superuser is functioning correctly, but now when I boot into recovery, TWRP comes up.
Excuse the newbie question, but does this mean that flashing CWM didn't work, or do I now have 2 recoveries installed? Could I have inadvertently caused myslef a problem that will manifest itself later? I did a search for CWM files through root explorer, which came up with nothing, but I am not sure if I searchex for the correct file names or in the right places.
I am only really concerned as I am currently deciding which ROM to flash, but obviously want to check I'm not about to brick my phone!
Thanks guys.
Click to expand...
Click to collapse
I think when you rebooted into system in CWM, you accidentally chose to revert to the old recovery
Thanks so much for the answers guys. I went ahead and flashed a rom anyway, figuri g that as long as A recovery was in place, it would be ok, and it seems to be so.
And it turns out I am happy with TWRP and as the old sayi g goes, if it aint broke....
I only chose CWM as the previous root had failed, so I tried with different variables, ot because of a burning preference for one over the other.
Thanks again for your help.
Wil.

Followed guide, bricked my N6

Hey guys,
Followed a guide (which I cannot post a link to because I'm too new to the forum) today and I get a message that says "Your device is corrupt. It cannot be trusted to work properly". After this message, it won't boot. At all. I had the latest version of Marshmallow when I attempted this. Never rooted before. New to this whole scene. Hoping for some guidance on how to fix this.
I tried wiping with the TWRP installed and rebooting, but I get the same message. I can still plug in to my Mac and use Android File Transfer.
Thanks!
guide: on androidrootz /2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
EDIT: Just needed newest supersu. Works fine now. Don't follow old guides, and make sure you have the newest software =]
You are not hard bricked, you will get out of this.
Sounds like you flashed the old root. You must use 2.60 or higher. 2.66 is current.
Flash it back to stock.
Flash twrp.
Copy over root 2.66 from Chainfire and install it with twrp.
When you exit twrp it will ask you if you want to root your phone. NO. Always answer no to that question from twrp.
The old way modifies the system. The new android does not like that.
And, just looking at your link, that guide is over a year old. Always try to look for fresh information. A lot happens to change things during a year...
TonikJDK said:
You are not hard bricked, you will get out of this.
Sounds like you flashed the old root. You must use 2.60 or higher. 2.66 is current.
Flash it back to stock.
Flash twrp.
Copy over root 2.66 from Chainfire and install it with twrp.
When you exit twrp it will ask you if you want to root your phone. NO. Always answer no to that question from twrp.
The old way modifies the system. The new android does not like that.
Click to expand...
Click to collapse
Resolved the issue. Got it. Thank you!!! Just needed to install the newest root (2.66)

Unable to root 800F under Lollipop 5.1.1

Hi guys,
I have successfuly updated my SM-G800F phone using G800FXXU1BOL4_G800FVFG1BOL1_G800FXXU1BOL3_HOME (Cyprus version) today. I also tried to root it using Odin3-v3.07.exe and CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5. Unfortunately, this leads into instant boot loop. I just reflashed phone to Lollipop again. Can you help me with rooting this version?
Rooting certainly is possible, even on that exact ROM.
Some notes:
- With stock ROMs you should generally not root before you have completed the setup wizard
- The only variant of root that works with the stock Lollipop ROM is "Systemless" root
- The Odin version you're using is outdated. It *might* make a difference to update.
When you ran AutoRoot, did it claim it was performing systemless root?
Thanks for your reply, got rooted. I found CF-Auto-Root-kminilte-kminiltexx-smg800f was outdated too.

Create rooted Backup for sideloading

Hi there,
after some attemps I succesfully rooted my fire7. More than one time it happend, that my modding and flashing attemps lead into a bootloop. There was no choice than sideloading 5.3.1 Firmware and going through the whole rooting process again. (Annoying)
In the End I decided to stay with a rooted FireOs since it was the only Rom where screenmirroring worked flawlessly. Now I was wandering if there was a way to create a prerooted and modded backup img, that I can safely sideload. I think it could be possible since I'm still on the 'original' rom whixh I initially sideloaded.
snoerme said:
Hi there,
after some attemps I succesfully rooted my fire7. More than one time it happend, that my modding and flashing attemps lead into a bootloop. There was no choice than sideloading 5.3.1 Firmware and going through the whole rooting process again. (Annoying)
In the End I decided to stay with a rooted FireOs since it was the only Rom where screenmirroring worked flawlessly. Now I was wandering if there was a way to create a prerooted and modded backup img, that I can safely sideload. I think it could be possible since I'm still on the 'original' rom whixh I initially sideloaded.
Click to expand...
Click to collapse
No ready-made tools as most require access to a custom recovery (eg: TWRP) for assured recovery. Next best option is the backup/recovery capability built into FlashFire. Note this requires a bootable/functional/rooted/stable ROM to pull off a comprehensive recovery. More of a checkpoint than full restore.
so it's not possible to sideload the backupfile that flashfire created?
It's kind of annoying to go through the kingroot procedure again and again.
snoerme said:
so it's not possible to sideload the backupfile that flashfire created?
It's kind of annoying to go through the kingroot procedure again and again.
Click to expand...
Click to collapse
Correct and agree. Lucky we can do anything with this device given bootloader state.

hey. i messed up an update to my fire and now i'm stuck...

hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
havikx said:
hi guys. I was running the Nexus fire Rom using flashfire. its was on 5.1.2. I tried to flash the new updated version from this year of nexus fire from a clean wipe and now I dont have play store or anything. i cant remember the intial root process...its been while. I'm a little fuzzy as to how everything work cuz of the locked bootloader.
I dont have play store. i tried to side load flashfire into my downloads from pc but it wont show. it say dowloads empty. i literally have clock, calculator, downloads, settings and SU. i dunno what to do at this point. why arent the apks showing in downloads? any help is apprecaited. sad to see there is no real root yet..
Click to expand...
Click to collapse
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Davey126 said:
There is "real" root on FireOS 5.1.2. Best option is to sideload (reinstall) that build of FireOS via stock recovery then use the SuperTool to root and prepare your device for installation of Nexus. Going through that process will refresh your memory. A few tips:
- be sure to get the 5.1.2 binary; no higher/lower
- don't register with Amazon on initial boot
- keep off WiFi to avoid forced OTA update to an unrootable FireOS build
- be sure to flash the version of Nexus ROM that includes GAaps; you likely used the ROM only variant on your last refresh attempt
Click to expand...
Click to collapse
now that you mention, thats probably exactly what i forgot to do. Also, i'm on 5.1.1. My bad. As far as i know, 5.1.1 system still has that locked bootloader preventing android upgrades. Though I havent kept up with development too much. Ill get started on returning to stock and rerooting. Hope this little tablet get a breakthru in the near future!
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
havikx said:
ok, so i sideloaded flashfire thru ADB and decided to switch over to lineage. thanks for your help. easier than returning to stock.
Click to expand...
Click to collapse
Agreed. The technique you used doesn't work for everyone; hence my generic 'return-to-stock and redo everything' guidance. Glad you are back in business with minimum fuss.

Categories

Resources