Develop Bugs

[Q] [HELP] Assert failed: getprop(ro.bootloader”)==i747

I am new to all this root and custom ROM, but I have spent hours searching forums and need help so thats why I am posting.
I have an AT&T Samsung Galaxy S3 I747. I am using Mac OSX 10.6.8. I managed to root my android using CASUAL (http://forum.xda-developers.com/showthread.php?t=2189536) and install Clockwordmod recovery v6.0.3.6
I then download and install #SuperUser. Followed by ROM Manager. (My internet research told me rom manager is the easiest to use for mac users)
I run rom manager, flash clockwork, then look to install the latest "stable" build for CM. I select install CM, format and erase, It downloads, downloads gapps, reboots looks to install CM, then I get the below error message:
Finding update package
Opening update package
Installing update
Assert failed: getprop(ro.bootloader”)==i747
(followed by many more lines of error/failed)
my phone then reboots into the stock AT&T. What am I doing wrong? What do I need to do to wipe my whole phone, factory reset, then install a custom ROM like CM using ROM Manager? or should I be doing something else?
Thank you in advance for your help.
Regards,
Tim

I was able (after many hours of reading posts) figure out my problem.
The new CM mods require a specific version of your phone's "bootloader." I switched it to: I747UCDLK3 then re-flashed CM 10.1.2-dtatt with Rom Manager and it worked!
You'll need to download and flash the appropriate bootlegger.
This thread was very helpful: http://forum.xda-developers.com/showthread.php?t=2321310
I have to say all in I invested a good 8 hours this weekend of reading posts, troubleshooting, and research as I rooted my phone for the first time, then installed my first custom rom. It wasn't easy rooting on a mac 10.6.8. Every step of the way I ran into obstacles and had to do a special workaround to root, get java 7, type commands in the terminal, install clockwork recovery, update bootloader, reflash cm rom.
Good luck!

tim1182 said:
I am new to all this root and custom ROM, but I have spent hours searching forums and need help so thats why I am posting.
I have an AT&T Samsung Galaxy S3 I747. I am using Mac OSX 10.6.8. I managed to root my android using CASUAL (http://forum.xda-developers.com/showthread.php?t=2189536) and install Clockwordmod recovery v6.0.3.6
I then download and install #SuperUser. Followed by ROM Manager. (My internet research told me rom manager is the easiest to use for mac users)
I run rom manager, flash clockwork, then look to install the latest "stable" build for CM. I select install CM, format and erase, It downloads, downloads gapps, reboots looks to install CM, then I get the below error message:
Finding update package
Opening update package
Installing update
Assert failed: getprop(ro.bootloader”)==i747
(followed by many more lines of error/failed)
my phone then reboots into the stock AT&T. What am I doing wrong? What do I need to do to wipe my whole phone, factory reset, then install a custom ROM like CM using ROM Manager? or should I be doing something else?
Thank you in advance for your help.
Regards,
Tim
Click to expand...
Click to collapse
**** IGNORE THIS POST AS FIX WAS INCLUDED IN PREVIOUS POST ********
Status 7 is from you having an outdated bootloader. follow this http://forum.xda-developers.com/showthread.php?t=2321310 and do as instructed

[Q] What am I risking by running KitKat with broken TWRP 2.6.3.1?

Background
I'm one of the lucky ones that has the data mount issues with the SELinux versions of TWRP. I've tried every method I can find in the forums here including:
Hashcode's original instructions for Kitkat using either "zip-otter-twrp-2.6.3.0-selinux-recovery.zip" or "openrecovery-twrp-2.6.3.1-otter.img"
Using Kindle Fire Utility to install either version of TWRP
this technique explained here: http://forum.xda-developers.com/showthread.php?t=2537579
And finally using Flashify
I end up with data mount error every time and I couldn't install any of the 3 KitKat versions found here http://forum.xda-developers.com/showthread.php?t=1859851 from within native TWRP (not the app) because I would get errors and the install would fail.
Convoluted Workaround
Here's what I finally did to get kitkat installed and fair warning, it's very convoluted. I installed TWRP 2.6.3.0 with KFU and used that to install CM 10.2 M1 snapshot with the appropriate "gapps-jb-20130813-signed.zip". Then I installed the Goo.im and Flashify apps. I ran both to make sure they had superuser rights. Closed them and rebooted. I then went into Goo.im and tried to upgrade to latest TWRP 2.6.3.1 which downloaded the file but failed to flash it. Close Goo.im and use file manager to find the downloaded file and when I clicked on it Flashify automatically asked if I wanted to install it. I said yes and let it do its thing and then rebooted.
Next I installed KitKat "CyanogenMod version 11-20131210-NIGHTLY-otter" by going into settings, about tablet, update cyanogenmod. Change search criteria so it sees the CM11 nightlies and then use it to download and install CM11
After rebooting, Kitkat installed and I had to run through the normal new ROM setup.
After that google play didn’t work so I uninstalled google play services & google play store with clean master app and reinstalled the gapps-kk-20131119.zip version. I think I used Flashify but I don’t remember to be honest. I also “might” have had to go back to TWRP 2.6.3.0 first to install gapps but again, I’m not sure. I know I sound like a ditz but I spent a day trying all kinds of things and should have taken notes.
Result is that my Kindle Fire 1st gen is running KitKat very well and so far this is the best version I have found and I’ve tried most of the 10.1 & 10.2 versions out there. The down side is the TWRP 2.6.3.1 backup is broken now. I’ve also tried going back to TWRP 2.6.3.0 (with & w/out SELinux) and none of them will complete a backup.
Sorry for the convoluted post. I wanted to recreate/clean up my process but since I can’t run a backup, I’m scared to hose my Kitkat install and not be able to get back. You are probably at extreme risk to try to follow my madness but maybe one of the smart people on here can use this to create a cleaner method for those of us stuck with the data mount issue related to the SELinux versions of TWRP.
Question
Is there any risk to my Kitkat installation by running a TWRP that has data mount issues as long as I don’t use TWRP? I read the KF guide here in the forum and I don’t believe there are any dependencies of the Android ROM (kitkat in my case) on TWRP. I do realize that any version of TWRP is basically useless for me unless I go back to version 2.6.3.0, wipe and start over.

No, no threat to your os
Sent from my air powered ceiling fan

Thank you
Sent from my Amazon Kindle Fire using Tapatalk

Have you tried the flashable zip version of TWRP? it works within twrp so that you can get the right one on your kindle

I think I've tried them all.
Laquox said:
Have you tried the flashable zip version of TWRP? it works within twrp so that you can get the right one on your kindle
Click to expand...
Click to collapse
Yes, both the zip and img versions with flashify, goo.im app, TWRP app and within TWRP native.

LineageOS on BLACKVIEW BV9900.

Hello.
I bought the BLACKVIEW BV9900 running Android 9.
I want to install the latest version of Lineageos with Android 10 on this phone, but first I want to know if my phone is compatible and if it works fine on it?
Is it also possible to root this phone?
Are there people on this forum who have already installed Lineageos and rooted this model?
Thanks for your feedback.

natouche said:
Hello.
I bought the BLACKVIEW BV9900 running Android 9.
I want to install the latest version of Lineageos with Android 10 on this phone, but first I want to know if my phone is compatible and if it works fine on it?
Is it also possible to root this phone?
Are there people on this forum who have already installed Lineageos and rooted this model?
Thanks for your feedback.
Click to expand...
Click to collapse
Never heard of lineageOS for that phone.

kurtn said:
Never heard of lineageOS for that phone.
Click to expand...
Click to collapse
When i search on google "lineageOS BV9900" there are sites that offer tutorials to install it. But having also seen on XDA a person who could not boot LineageOS installed on this model, it is for this reason that I would like to have the opinion of other people who have already installed it.

i may give it a try i recently got twrp working on it so its a good a time as any to look around.
(gotta find a way to backup my stuff first tough as its still encrypted and twrp doesnt wanna play with that)

annoyed
I had also a lot of problems ...
I had to reinstall the stock ROM over SP Flash Tool because of bootloop
I then managed to install twrp
- by activating oem in android setting
- activating usb debug mode
- fastboot flashing unlock
- fastboot flash recovery recovery.img (Took the bv9900 TWRP 331 found on the internet)
- Then tried to wipe, but I get an error that twrp is unable to mount partitions...
After searching I was able to get a workaround, a made a "Format Data"
- Install lineage img from twrp and reboot => got boot loop again !
- Then I reinstall only stock system partition through SP Flash Tool, and working again, but TWRP is away ???
Is the scatter File from the stock rom wrong ? How is it possible, that on flashing only the system partition, the recovery gets overwrited ???

Help for back to stock HD10 (7th gen)

hey! ive looked around the forums unsucessfully - ive got an HD10 7th gen fire tab and need to go abck to stock
im currently on 5.6.6.0 (654620620) and have rooted and removed lock screen ads etc etc
but I'd like to go abck to stock
if anyone can point me to a guide, id appreciate it!
BTW ive tried downloading the stock .bin from amazon but when i hit 'update' on the system update screen on the tab it says 'check for updated failed'
thanks!!
-Dan

I'm here for the very same reason. I found a thread yesterday which appeared to explain, I'll post here when I find it again

This is what I'm going to use to restore HD10 back to stock from Lineage 14.1. Looks like some people have semi bricked their devices so read the thread fully first. I'll give you an update as to how I get on.
Unbrick/Restore/Downgrade Stock Firmware [Amazon Fire HD 8 & HD 10]
Updated: The 7th Gen (2017) HD Fire(s) can now be bootloader unlocked and rooted. See https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639 And...
forum.xda-developers.com

The steps I ended up taking to go from Lineage 14.1 back to factory/stock FireOS successfully are:
1. Download stock firmware and changed the file extension to zip from bin. I downloaded 5.6.4, as I knew I originally had at least an earlier release, from https://forum.xda-developers.com/t/firmware-update-stock-fire-hd-10-7th-gen.3926806/
2. Installed the zip file in TWRP and then cleared cache and dalvic.
3. Followed the instructions under "Going Back to Stock" in this thread* - https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/
As I had used 5.6.4 I had to place arm64 binary from rapid temporary root in the amonet/bin directory https://forum.xda-developers.com/t/rapid-temporary-root-for-hd-8-hd-10.3904595/

B0oza said:
The steps I ended up taking to go from Lineage 14.1 back to factory/stock FireOS successfully are:
1. Download stock firmware and changed the file extension to zip from bin. I downloaded 5.6.4, as I knew I originally had at least an earlier release, from https://forum.xda-developers.com/t/firmware-update-stock-fire-hd-10-7th-gen.3926806/
2. Installed the zip file in TWRP and then cleared cache and dalvic.
3. Followed the instructions under "Going Back to Stock" in this thread* - https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/
As I had used 5.6.4 I had to place arm64 binary from rapid temporary root in the amonet/bin directory https://forum.xda-developers.com/t/rapid-temporary-root-for-hd-8-hd-10.3904595/
Click to expand...
Click to collapse
Thanks, returned to stock from CM12.1 successfully

Lineageos Updater failing

I have an SMt-700 and an SMT-800. The installations are essentially identical except for the obvious (or maybe not):
The T700 has Klimtwifi, TWRP 3.3.1-0
The T800 has Chagallwifi TWRP 3.1.0 and the Marshmallow bootloader, both installed via Odin per the Lineageos 14.1 support forum.
The T700 works as advertised, downloading and installing the updates goes off without a hitch.
The T800 has yet to successfully download and install and update without manual intervention. It's only a nuisance, but it's supposed to work and it doesn't. Any suggestions before I start over? Does the TWR version that came with Beans GApps make a big difference?

wellersl said:
Does the TWR version that came with Beans GApps make a big difference?
Click to expand...
Click to collapse
Yes, older versions of TWRP will fail the assert check. The assert check is to make sure you don't flash the rom on the wrong tablet. Older versions of TWRP don't know how to handle the assert and will say somethinig like error 7. Upgrade chagallwifi to at least TWRP 3.3.1.

retiredtab said:
Yes, older versions of TWRP will fail the assert check. The assert check is to make sure you don't flash the rom on the wrong tablet. Older versions of TWRP don't know how to handle the assert and will say somethinig like error 7. Upgrade chagallwifi to at least TWRP 3.3.1.
Click to expand...
Click to collapse
I'll be damned. I downloaded and installed TWRP 3.5.0_9-0, installed via Odin, rebooted, re-downloaded the update, it failed to install. I must be holding my mouth wrong because it installed manually just fine. (sigh) Tomorrow's another day.
Maybe I should start backing off TWRP versions until I find one that works?