Hey all,
Does anyone know if there is a loop module available for the stock Nexus 10 kernel? Specifically, I'm trying to get TrueCrypt volume mounting working with the latest updated binary: http://code.google.com/p/cryptonite/downloads/detail?name=truecrypt&can=2&q=
Thanks,
Ben
*EDIT*
Looks like while the issue being reported is about the loop device, that's not the actual problem TrueCrypt is having as I just mounted a vfat file. Hrm..
Related
Hi everyone
I just flashed my smoothrom 5.3 with franco kernel r75 , on my N7 (2012), and I have a "infinite loop of dead" com.android.phone crashed.
I saw somewhere in the forum, there is patched version of franco kernel, for people with this problem, but , I can't find for N7 2012, only N7 2013
Could someone help me please, I'm stuck at the boot screen...please
Same problem for me
Did you find a solution in the end?
Update: Nevermind, just found out Franco does not support CM derivatives.
android.phone.com error loop after franco kernel update r75
fred41 said:
Hi everyone
I just flashed my smoothrom 5.3 with franco kernel r75 , on my N7 (2012), and I have a "infinite loop of dead" com.android.phone crashed.
I saw somewhere in the forum, there is patched version of franco kernel, for people with this problem, but , I can't find for N7 2012, only N7 2013
Could someone help me please, I'm stuck at the boot screen...please
Click to expand...
Click to collapse
Dear fred41,
got the same error when i updated when i shouldn't have done so. anyways, only way i worked out of the loop was:
a) i assume you have clockworkmod installed (*BOOT into this: press volume - and power together till Recovery comes out)
b) choose from the menu: install from sdcard
c) i decided to re-install the latest cyanogenmod i downloaded.
d) once re-installed, the error disappears. i didn't have to re-install all my other apps, no data lost. (*N7 2012)
e) i had to re-root the N7 though... even if cyanogenmod has its own superuser options.
f) to do this, you will have to re-boot into CWMod again, and install your superuser .zip file (whatever version you may have in your sdcard)
all the best and good luck,
bod
I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
dude the error is written in plain English: the process expects one type of thing in your system, but it finds another, doesn't like that so quits. trying to find the exact source of the error would be futile. I received an error too, not sure if it was the same since I didn't bother reading it. I just downloaded the stock 4.4.4 firmware from Google and extracted system.img and flashed it with fastboot. I'd suggest you go that route. you can try flashing from twrp again after that, personally I went the adb sideload route: http://forum.xda-developers.com/nexus-7/general/lollipop-ota-update-via-adb-data-t2941175
arimaidana said:
I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
Click to expand...
Click to collapse
You are using OmniROM. Pretty obvious you can't upgrade a custom ROM with a stock OTA.
This has nothing to do with omnirom at all, it all has to do with twrp using a custom .prop with wrong preset values. It wasn't an issue until Google decided that the 5.0 update checks more things, hence this stupid error. Btw that's exactly the 1st thing the upgrade script checks!
twrp must change its way of providing props because it's so obviously a major bug and will prevent using it to install any future updates.
What I did is use the factory image to do a custom non-wiping upgrade (there's a topic about how to do that), got incredibly slow performance and then do a wipe to get performance back and start with a clean slate with Lollipop, like I did with Kitkat.
So I think if your Kitkat was starting to be slow, better start anew and anyway Lollipop lets you choose exactly what to reinstall.
Dear All,
I hope to find someone experienced the same problem. I was using the android updater-script to flashing some files(configurations) to the phone, this method works with my previous Nexus 5, but it never worked with this OnePlus 5. I am really confused. I already mounted the '/system' partition and uses the `package_extract_dir` to copy the files. then if I verify the results in the TWRP terminal, it seemed worked. But when I boot up into system, use `adb pull /system/etc/hosts`, the original hosts changed back. However this method works with Magisk patched ROM, I suppose the system files are in the boot image. This is really weird to me, I am really appreciated if anybody knows any details.
Thanks,
xeechou
Greetings to all,
Whilst following a guide to install LineageOS 17.1 on my nexus (I didn't relase mine is a 2012) I have inadvertantly deleted the Operating System so now it's caught in a "boot loop"
The options I still have are:
Start
Restart Bootloader
Recovery Mode
Power Off
Can anyone please advise how I re-install an Operating System from this point and which version of Android is the most recent/stable version suitable for the Nexus 7 (2012).
Many thanks in advance.
Scott
PS Why doesn't LineageOS 17.1 work on a 2012 Nexus?
Have you unlocked Bootloader?
Have you rooted it before attempting to install new OS?
Have you updated your recovery with TWRP 3.0.2.0 recovery?
Many thanks for the reply.
I'm now running TWRP 3.5.2-9.0 with Lineage 15.1 unfortunately
I'm getting an Error Code 70 preventing me from uploading Gapps.
I've tried resizing the system partition via TWRP without any joy.
Any advice please?
S&M Inc said:
Many thanks for the reply.
I'm now running TWRP 3.5.2-9.0 with Lineage 15.1 unfortunately
I'm getting an Error Code 70 preventing me from uploading Gapps.
I've tried resizing the system partition via TWRP without any joy.
Any advice please?
Click to expand...
Click to collapse
Unfortunately I never tried Lineage 15. I got 7.1 installed and I also had a problems with Gapps installation. The only package I was able to install was Pico with using config.txt file to limit number of apps to be installed. You can see post number 2 from the link bellow to get the idea what needs to be done. I guess you need to get or create similar config text file and include in same directory where your Gapps installation file is located. I also tried changing partition on my device, but it seems that this function does not work on Nexus 7.
[ROM][NZH54D][2023/04/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP
This thread is about installing and using AOSP 7.x (Nougat) ROM for the ASUS Nexus 7 Grouper / Tilapia devices. Asus - Model names Grouper = Asus Nexus 7 2012 WiFi Tilapia = Asus Nexus 7 2012 3G Initial Setup Installation Update Recovery to...
forum.xda-developers.com
Many thanks for all your advice.
So, I was trying to root a model of Samsung galaxy tab a sm-t380 2017 8" and I came across a boot loop and thought of a possible solution that is following, In TWRP I saw an option wipe/AdvancedWipe /RepairOrChangeFileSystem then finally I saw change file system and it then showed 6 options of formats to format the system to a different format rather than the default and to sum this up I wanted to know if changing one of the options would stop the supersu boot loop of the default device animation. PS: I said this because at the top of the final option it says in red "some roms or kernels may not support some file systems. proceed with caution!"
TheRealYiDa said:
So, I was trying to root a model of Samsung galaxy tab a sm-t380 2017 8" and I came across a boot loop and thought of a possible solution that is following, In TWRP I saw an option wipe/AdvancedWipe /RepairOrChangeFileSystem then finally I saw change file system and it then showed 6 options of formats to format the system to a different format rather than the default and to sum this up I wanted to know if changing one of the options would stop the supersu boot loop of the default device animation. PS: I said this because at the top of the final option it says in red "some roms or kernels may not support some file systems. proceed with caution!"
Click to expand...
Click to collapse
DON'T change the file system! I don't have a T380 but in general, when you get a bootloop on Samsung tablets it is because of kernel mismatch. IOW, the kernel version of TWRP doesn't match kernel version of the ROM you have installed. Also, instead of supersu, try using Magisk.