Related
February 4: Rom updated to include February security patches.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16643
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
January 14. Rom updated to include Google's January 2016 security patches. Also, selinux not only disabled, but completely removed: the rom compiled without selinux sources/binaries.
Kernel does NOT include recovery, so use TWRP for Fota/Recovery partition.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=16217
_________________________________________________________________________________
For those who prefer to stick to bugless kitkat: Rom updated to include all "shields up" features including cleaning creepy Ips and dns defaults. Compiled just a few days ago.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13001
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Here is Slimkat 10 unofficial built from sources on March 2. Built using JDK-7, which turned out to be beneficial for the rom. Slim, fast, smooth and stable. For those of you who have been using Lollipop for a while, you will see how much faster, smoother and more stable kitkat is. Everything works: no reboots, no freezing, no overheating, no screen light flickering, no video recording/play problems, great battery life and abundance of features. This taken together with improved security makes a pretty darn good rom. I tried it and got rid of Lollipop.
Changes:
1. New Iptables binaries which allow to stop kernel communicating (if used with Afwall) with Google home.
2. Changes in Vold to enable 256 bit AES encryption, as opposed to default 128 bit
3. Key length increased for multiple keys
3. Kernel with disabled Selinux and enabled Tomoyo together with all ciphers/hushes/digests/random number generation tools
4. Latest changes from Google code (I was surprised finding changes pushed for kitkat while synching Google source)
5. TWRP 2.8.x integrated in boot image
Install:
1. Be on Kitkat, rooted with recovery
2. Enter recovery and wipe Cache/System/Data
3. Flash the rom and reboot
4. Enjoy and say thank you or perhaps donate
Rom is in Download section above
Credit: Slimroms
Warning: I am not responsible for your device exploding and killing everybody around. You are on your own. :laugh:
Source: https://github.com/SlimRoms/platform_manifest/tree/kk4.4-caf
Source with changes: https://github.com/HonamiZ1
XDA:DevDB Information
Slimkat 10 Final Edition, ROM for the Sony Xperia Z1
Contributors
optimumpro
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: Slimroms
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2015-03-02
Created 2015-03-03
Last Updated 2016-02-04
Reserved
Believe me I have no interest in being in any of "your threads" {That's why I'm editing this post instead of posting a new one xD},
I'll leave this thread from any further discussion.... for now at least
Regards,
Omar.
OmarEinea said:
Cool, can you give us changelog of what's new between build 9.0 and build 10?
cuz latest kk build by Slim Team is 9.0 : https://github.com/SlimRoms/vendor_slim/blob/kk4.4/config/common.mk#L154
so you must have made some major changes to call it build 10, right?
Regards,
Omar.
Click to expand...
Click to collapse
Thanks. Reading the OP might help...
" you didn't get my point, did you!!"
Oh, I did get your point alright. :fingers-crossed:
Could you please do me a favor? Kindly stay away from my threads. If you feel that you need to continue to report me, that's your right, but again, stay away from my threads.
Best regards
Gonna give this a try as sounds like Kk on steroids well stable steroids.....LP still too buggy for me.
I tried it. But play store doesn't work. What is the problem...?
Rom Updated
See OP for description and download link...
thanks
the best option is in that forum for the Z1 now
First download
Thanks for all your awesome roms
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Xecu said:
I downgraded from CM12 because it feels like each LP-Rom needs more polishing.
The Rom installed successfully (did a system / data / cache Wipe) but now I am unable to get into recovery. It is stuck on the Sony Logo. Just starting the OS works fine though.
Edit:
I tried flashing TWRP 2.8.6.0 via Flashboot.
Flash was successfull, but I still get stuck on the Sony Logo when i try to get into recovery.
The Led also switches lights from purple to orange.
Click to expand...
Click to collapse
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
optimumpro said:
If you have recovery in Fota partition, it is known to collide with in boot image recovery resulting in no recovery at all. So, you need to get rid of Fota recovery to use internal one. For that do this in fastboot: fastboot erase recovery; then fastboot reboot...
Click to expand...
Click to collapse
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Xecu said:
Thank you! That did it.
But I still dont quite understand what happened here.
So i had 2 partitions, fota and recovery, each having a recovery installed. 'fastboot erase' does delete the one in the recovery partition, leaving only the one in fota.
That sounds kind of wrong for me, because I do want to use the recovery I install via fastboot.
Click to expand...
Click to collapse
Xperias don't have recovery partition. Fota is used by stock firmware only, so it is available in custom roms, hence recovery image could be installed there. However, the normal way for custom roms is to incorporate recovery into boot image, which is faster. This was until lollipop, when the not so smart folks at Cyanogen, gave up on CWM (which was always in boot image) and came up with their own recovery. CM recovery does not work, so TWRP guys figured out a way to install their recovery in Fota, instead of having users/developers decompiling boot image, replacing CM recovery with TWRP and recompiling the image again. That's what I do in CM based kernels, but Slimrom folks use TWRP in boot by default.
So, when you did fastboot erase recovery, you got rid of recovery in fota partition. Now, you have TWRP in boot image.
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Running this Rom, these issues are gone. I am again at 2 days runtime and I can finally write longer messages without beeing bothered by an unresponsive screen. The system feels reliable again.
Only issue i found so far, is that my headphones are sometimes not recognized. In these cases, I have to unplug and plug them in again until the system recognizes them. I had the same issue when I was on KitSlim_AMG, but not on stock. So this might be a bug in the SlimBean / CM Code-Base.
Xecu said:
Running it for 2 days now and I am highly satisfied.
I downgraded from Lollipop (tried CM, crDroid, another CM-Based Rom and Custom Stock) because each Rom caused 2 main issues: Runtime decreased from 2 days to 1 day and the infamous touch screen issues.
Click to expand...
Click to collapse
You are forgetting the heat issue, which requires RECALL. I am not a huge gamer, but CPU can easily get to 75-80 degrees after using Firefox/Fennec for about 10 minutes. Then flickering and other heat protection kick in. Note, that most users won't notice overheat, because glass is not a very good heat conduit. They just complain of backlight flickering. However, if you enable CPU stats in developer options, you can see the temperature on screen. This is a shame (overheating), especially that LP has been around for about 7 months to no avail. You can't blame the processor, since there is no heat issue on kitkat and jb.
Lollipop, in my view, is the worst ever android version: linux (which is great) + google poop (google does what it does best) = lollipop. Really, the name should be Lollipoop.
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Xecu said:
I got another question
Logcat seems to be disabled, because /dev/log/main is not created. Is there a way to activate it?
Click to expand...
Click to collapse
Logging is disabled in kernel for security. You can get a few apps on f-droid for logcat...
New build
Rom updated to include January 2016 security patches. See OP for download and description.
optimumpro said:
Rom updated to include January 2016 security patches. See OP for download and description.
Click to expand...
Click to collapse
Thank you for continuing to support KitKat I'll try the new build tomorrow
So the boot image doesn't have a kernel? Do I have to fastboot flash recovery recovery.img if I don't have the bootloader update?
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Try the flash all script again with latest firmware and let it boot up completely. It will take a while, once booted, flash TWRP and root if you want.
ntropia said:
Hi,
I'm writing here as a last hope, after I've tried every possible solution I could find online. Any help here will be very much appreciated.
Couple of days ago I received my fresh Nexus 5X, that I plan to use with Project Fi.
After unlocking the bootloader (with Google Support blessing!) and installing TWRP+SuperSU, I ran into problems, big problems.
Following the Android wizard setup, I connected to the wifi and the phone started downloading an update of ~79Mb.
When rebooted, though, it started TWRP, and it didn't go ahead.
To play safe, I decided to do a factory reset, using the official ROM from Google, replacing also TWRP with the original recovery (I basically did every step in the "flash-all.sh" script).
That didn't work either, and the phone now gets stuck at the boot animation.
I've tried also wiping partitions using both fastboot ("fastboot -w...") and TWRP, but nothing worked.
Another diagnostic symptom.
I've noticed that the recovery (TWRP for sure, the stock one not so much sure) had problems finding the sdcard partition ("unknown volume for path couldn't mount sdcard installation aborted").
Could that be a source of issues?
I thought that it would be possible to do a factory reset, but I'm probably missing something.
At this point, I'm completely lost and I don't know what to do.
Thanks in advance.
Click to expand...
Click to collapse
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I wonder if you need a modified boot.img or kernel since you are rooted .In my experience since Android 5.1.1 you need a custom kernel for root and sometimes a modified boot.img after flashing twrp
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That's an interesting perspective, actually.
I didn't know that you needed a special image for rooted devices.
Although, I would imagine that's always possible to 'un-root' it, and honestly I was hoping that 'fastboot flash -w...' would have removed any trace of the root.
Is that the case?
Either way, where could I find these modified images?
Thanks a bunch!
Solved
I found the solution which, as it happens when nothing seems to be wrong, was fairly trivial.
Basically, the scripts provided with the stock ROM from Google has problems, and this last command fails:
Code:
fastboot update image-bullhead-mmb29p.zip
saying that system.img is missing.
To fix that, you have to manually extract the content of the files and proceed to flash manually userdata, system, etc...
The problem is that if you don't flash also vendor.img, you're in trouble, and the device will not boot.
Some of the guides that I've found were suggesting that you need to do it for the Nexus 9, and I didn't notice when other guides were mentioning it.
Once you flash the vendor.img, the boot loop is gone.
I'll put it here, I hope it can be helpful to somebody.
Thanks to androidddaaron and k.s.deviate for the support!
(I've thanked also used the thank button near the posts, but if there's more to do, let me know)
Now, back to mess up the Project Fi SIM...
Hello all,
I recently tried to flash the latest LineageOS (lineage-14.1-20170717-nightly-crackling-signed), but without any luck (stuck in bootloader/recovery mode). I had no backup so I tried a bunch of old CM ROMs until I found a working one (an unofficial CM14 release found on cyanogenmods.org, can't post links yet).
Now I wonder why this particular ROM is the only one I can install.
So far the only difference I found is that it only targets armeabi-v7a and armeabi ABIs, and not arm64-v8a as the LOS ROM does.
So I checked with Droid Hardware Info and it tells me I have indeed an ARMv7 architecture.
But everything I read about the Swift tells me it's a 64 bits architecture.
Could someone tell me what I am missing here? Is it all normal or did I buy a fake Chinese copy of a Swift?
Thanks
Welcome. I doubt anyone would fake a swift. Most likely you didn't flashed a compatible fastboot image and baseband. Unlock your bootloader and fastboot flash https://www.androidfilehost.com/?fid=457095661767123627 then flash twrp 3.1.1.0. https://forum.xda-developers.com/wi...ent/recovery-unofficial-twrp-3-0-1-0-t3350351
Hello Dmitriy.WZR, thanks for the reply.
Indeed I don't really believe I have a bad phone It has to be something I did.
But so far I only flashed a recovery image (twrp-3.1.1-0-crackling), after unlocking the bootloader, as explained in the LineageOS wiki Install LineageOS on crackling. Then I installed LineageOS, GAPPS and the LineageOS addonsu. Then bootloop.
Not sure I know what is a "fastboot image and baseband".
thomas.gillet said:
Hello Dmitriy.WZR, thanks for the reply.
Indeed I don't really believe I have a bad phone It has to be something I did.
But so far I only flashed a recovery image (twrp-3.1.1-0-crackling), after unlocking the bootloader, as explained in the LineageOS wiki Install LineageOS on crackling. Then I installed LineageOS, GAPPS and the LineageOS addonsu. Then bootloop.
Not sure I know what is a "fastboot image and baseband".
Click to expand...
Click to collapse
Same happened to me a few months ago. The solution that worked for me was:
1. Remove the battery and reinsert it.
2.Go to recovery mode.
3.Wipe everything including internal storage.
4.Download a fresh copy of Lineage os and gapps and flash. Try avoiding su.
5.Reboot
Hello nsa02,
I did that several times and it didn't help. Did it again to be sure, but nothing new. Thanks anyway.
I hope I'll have better luck with @Dmitriy.WZR answer, I'll try to figure out what is this radio-20161215-crackling file and what I can do with it.
Ok, got it!
Seems I had an old bootloader (an ugly one with a terminal-like style and a big green START on the top), very different from the Cyanogen one.
Used radio-20161215-crackling file to flash my firmware (or bootloader, no sure what is what yet), as explain in the [RECOVERY][crackling] TWRP 3.1.1-0 [OFFICIAL] thread by @beroid.
Then latest LineageOS and GAPPS installed without problem (didn't try the su addon), and Droid Hardware Info tells me I have an arm64-v8a indeed!
Many thanks to @Dmitriy.WZR
thomas.gillet said:
Seems I had an old bootloader (an ugly one with a terminal-like style and a big green START on the top), very different from the Cyanogen one.
Click to expand...
Click to collapse
That's actually the newest one (the one, that come with Android 7-based firmwares). Sadly enough this one is incompatible with custom ROMs, so you need a cyanogen-besed bootloader, yes.
Glad you make it, wishing you a rock-stable working device
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
Code:
tar -xzf ********.tgz
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
viking777 said:
Interesting. I have certainly thought of jumping ship to a custom rom, but I would like to wait a little before I do so, ideally until someone fires up a Lineage rom for the A2 Lite. But if things continue as badly as they have done so far with stock roms then I might well join you on RR.
Click to expand...
Click to collapse
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
12:121390 said:
also because of the new ARB thing, custom is much safer, i think i bricked my last device rolling back from ota 9.0 software to ota 8.1. that's a non-issue with custom. just something to be wary of. the current RR pie gsi is near flawless for he so far. hope that helps a little
Click to expand...
Click to collapse
Anti roll back is disabled and not an issue if bootloader is unlocked
Nice thread. Tried it as well but no chance 10.0.3.00 + twrp + magisk. And you are right the problem is twrp.
Sent from my Phh-Treble vanilla using Tapatalk
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
12:121390 said:
i was having similar issues. replaced my mi a2 lite and followed the guide for the aosp 109 gsi here in the forum replacing the fstab and one other file i forgot they name but it's instructed. i have twrp zero the fixed one, magisk, and I'm running the RR PIE ROM with zero issues and I've been back and forth in and out of recovery no problem. I'm pretty sure it will work for you too.
Click to expand...
Click to collapse
brother i also want to install RR PIE Rom can you please give me the guide link?
hossman said:
Anti roll back is disabled and not an issue if bootloader is unlocked
Click to expand...
Click to collapse
correct it is not. what happened was.. lol. i thought i was crafty and did some file swapping and made miflash setups that would flash so the stock files as usual , but with gsi's like RR and/or bootleggers for the system image. and it works, up until i flashed from RR to bootleggers with those setups described previously . there is where my genius was flawed. lol. lesson learned
---------- Post added at 06:43 AM ---------- Previous post was at 06:38 AM ----------
marstonpear said:
Does RR Pie have any issues on Mi A2 Lite? Whichever GSI I'd tried, I had lags :/
Click to expand...
Click to collapse
for me, i have not come across anything caused by the GSI. any issues I've faced are purely self inflicted.
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Voodoojonny said:
I don´t get your problems... Just boot twrp, and install it as described in original thread.
After that flash back aboot from 9.6.11.0 and the message "your system got destroyed" will disappear!
Click to expand...
Click to collapse
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
viking777 said:
You might not get my problem, but likewise I don't get your solution. Firstly aboot has never been touched during the attempted twrp install so why flash it at all, it has not been changed, and secondly you suggest I flash it with something that is how many versions old 4?, 5?, I'm not sure, when just about every post you ever read stresses that you should not mix old and new partitions at the same time.
I hope you forgive my scepticism, but can you actually suggest the slightest reason why this might work?
Or is it all just voodoo johnny (sorry, couldn't resist that).
Click to expand...
Click to collapse
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Voodoojonny said:
Aboot is the bootloader. Since Pie the aboot was modified to check wheather there are modification on your boot.img. So everytime you modify something (like installing twrp), you get the message "your system got destroyed".
9.6.11.0 is the last version of Oreo. Here the bootloader didn´t check boot.img.
That´s why you need to flash 9.6.11.0 - maybe the older verstions will work too. Didn´t check. But I guess only 9.6.11.0 will work becouse it was the latest oreo version and it had to have a bootloader which can boot up pie (to have ota working).
Here you can find the aboot.img I use... and which works without any problem on pie - right now I´m running 10.0.3.0...
Just flash it via fastboot.
Click to expand...
Click to collapse
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
viking777 said:
OK that makes sense now - thank you for the explanation. I will probably give that a try sometime, but not right now as I have a stable working phone for the first time in ages and I don't want to jeopardise that.
Just one question though. When I had twrp installed on 10.0.2.0, it was fine at doing backups, but on the two occasions I tried to restore with them they failed, by which I don't mean that the restore didn't repair the phone, but that it was impossible to even carry out the restore, it started but did not complete - just ended with 'Restore Failed' message.
Have you tried any restores with twrp installed in the manner you suggest and if so did they work? No point in installing it otherwise.
Click to expand...
Click to collapse
There seems to be some bugs restoring system and vendor... Some users talked about... I usually only save and restore the data and boot partition and I never had any problems with that. For all other partitions you can use miflash or fastboot...
Yeah all my twrp full backups don't work after a fresh stock installment either, that's very annoying.
The twrp version for daisy is bugged. Backups are not working, the wifi with GSI Roms on pie stock is not working anymore as soon as twrp is installed as well.
Sent from my Phh-Treble vanilla using Tapatalk
Thanks for the replies above. @voodoojohnny
In my case it was the data partition that caused the restore to fail, vendor and system and boot all seemed to go through normally. @cd492
Based on what you say along with my own experiences and those of voovoojohnny, it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
viking777 said:
First, let me say I have been using rooted phones with twrp for several years and never had the slightest problem with them, so I generally know what I am doing, but the Mi A2 Lite is just a disaster area for me, not with Magisk, that works fine, but twrp seems impossible for me to install on 10.0.3.0 without soft bricking ( I had twrp installed on 10.0.2.0 and 10.0.1.0 so I am not unfamiliar with the method, but on 10.0.3.0 - no way). I have done so many factory resets now I have my own parking space at the factory! (That is humour btw).
So I wondered if a different approach to the problem might work. I am not a coder or phone guru, so what I propose might be nonsense, if it is I am sure somebody will tell me.
We are all used to the concept of the 'patched_boot.img' created by Magisk and if you don't want to produce your own version the forum usually has a link to it. Magisk though is not the problem, twrp is, so what I am proposing is that somebody provides a link to a 'double_patched_boot.img' ie a flashable boot image that contains both twrp and magisk and that can directly replace the stock boot via fastboot.
Apparently there are some folks that have managed to install both twrp and magisk on 10.0.3.0, so if one of them could extract the 'double_patched_boot.img' from their phone it might help out a lot. How do you achieve that? Well there is probably more than one way, but the way that I would choose (if I could manage to install them both in the first place) is to boot into twrp, connect to pc, take a miflash backup of the phone and then unzip it with the following command (this is a linux command I am sure someone can provide a windows equivalent):
where ********.tgz is the name of your miflash backup.
Then extract the boot.img from the resulting folder, rename it to something like 'double_patched_boot_10.0.3.0.img' and provide a link to it on the forum. Then some brave soul could try it out (probably not me as I am sick of doing factory resets and don't have any backups because I don't have any recovery to make them from).
OTOH this might just not be practical, I don't know enough to be sure.
Click to expand...
Click to collapse
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
InfinityXDA said:
THIS HAS NOT BEEN TESTED ON GSI'S YET
I'm currently in the process of RR with TWRP but having extreme Encryption errors
Grab these two files (Big Thanks to Zerovoid, Seryioo, and mac12m99)
Fixed SDCard Support TWRP Image File (Put this on your SDCard and Computer)-
https://forum.xda-developers.com/mi...unofficial-twrp-daisy-mount-sd-fixed-t3889390
Fixed SDCard Support TWRP Installer Zip (Put this on your SDCard)-
https://androidfilehost.com/?fid=11410963190603893418
But I got TWRP on 10.0.3.0 with magisk, and Justic Kernel.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA
Start with the phone being on with USB Debugging enabled correctly
Type adb reboot bootloader
So flash the 10.0.3.0 ROM through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
After it is done flashing it restarts, go ahead and hold power and volume down right back to the Bootloader
Type: fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP, if you see something about decryption hit cancel this may mean you haven't followed directions so far
Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
Hit the home button back to TWRP home screen and tap reboot >>> bootloader
Download this to your computer - https://androidfilehost.com/?fid=11410963190603884024
Type: fastboot flash aboot aboot_9.6.4.img
Then type: fastboot reboot
Afterwards your phone shall boot up to Android if it does hold power and volume up and release power and keep hold volume up when the screen turns back on to go-to recovery, if TWRP boots up you have successfully completed the task.
Now flash Magisk zip (optional)
Hopefully this helped kind of my first tutorial, this was my process.
Click to expand...
Click to collapse
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
it looks like twrp is more trouble than it is worth at the moment. I think I will make do without it for now and hope for a better version in the future.
Click to expand...
Click to collapse
I meant it, at least for now, but maybe your post will help somebody else.
viking777 said:
Thank you very much for posting this process in such detail, unfortunately I think you must have missed my last post where I said:
I meant it, at least for now, but maybe your post will help somebody else.
Click to expand...
Click to collapse
Yes I didn't see that post but understand I didn't give you links to the official TWRP, I gave you the unofficial fixed TWRP which actually features SD Card Support and trust me it works completely fine I haven't had a problem yet. This took me hours upon hours to figure out what I was doing wrong.
The only specific reason you are not successfully getting TWRP is because you didn't flash the aboot.img after installing the zip.
I hope this helps you in the future!
thanks InfinityXDA for the tutorial, you should create a post just for it~
I was trying to update the OS on my Nexus 7 2013. I was able to connect it to my PC and unlock it and erase user data using adb commands. But after that it will not go past the Google logo in Recovery or regular Start mode. When I run "adb devices" it does not show up, though my computer does see it since I can run the lock/unlock adb commands and they work. I have uninstalled/reinstalled different adb drivers for the devices. I've tried using 2 different PCs. I can not get adb to fully recognize the device. I tried the Skipsoft Android Toolkit, and it too reports "no device detected".
Have I completed bricked the device? Or is there some way out of this that I haven't though of/found on the internet yet?
I hope someone here can help me!
Thanks!
Assuming you're on stock, try flashing a factory image from Google themselves. This reflashes everything, like stock OS, recovery, bootloader, etc. I'd choose the latest version found here: https://developers.google.com/android/images#razor As long as you understand that this wipes data, then give this a shot and let us know the results!
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
adamwsh said:
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
Click to expand...
Click to collapse
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
NTGDeveloper said:
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
Click to expand...
Click to collapse
Thank you! I did manage to get 18.1 to flash and load, after using a repartiion tool I found. However, I can't get GAspps to load, saying there isn't enough room on the partition. Now, I'm trying to use NRT to get back to stock (like I was able to do earlier) but now it is getting stuck at the Android 6 startup animation (4 round icons). I'm wondering if it is because I ran the partition update and somehow have to put that back to get the stock ROM to work.
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
NTGDeveloper said:
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
Click to expand...
Click to collapse
I wound up flashing Stock Android 5.0 and it worked. Now I'm updating to 6 via the software upgrade in the OS itself. I feel like this thing is just too old and not large enough memory to handle a custom OS.