-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to mount /cache #17
Comments
i don't see the error you mentioned in the output. cache is blank by default so i'd just boot into fastboot and |
Hi,
I'm not able to access fastboot. The tablet are looping.
Please see the attached screenshot.
…On Wed, Aug 28, 2024, 22:26 tofurky ***@***.***> wrote:
i don't see the error you mentioned in the output. cache is blank by
default so i'd just boot into fastboot and fastboot format cache
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGZYKRAWC4SRMK35XOKQYWLZTYXANAVCNFSM6AAAAABNIC6TPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGE4TANJXGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
fastboot is on there as you wouldn't get to the recovery screen without it: Press and hold Volume Down, then press and hold Power. see if it enumerates in fastboot mode. i'd do it while it's connected to a linux system with if it does, try the but you say it's looping? so it goes to the exclamation mark screen then immediately reboots itself back to "E: failed to mount /cache" and then to the rescue screen again? |
flash.cfg.txt
Could it be that my partition tables got corrupt or do I need to format cache? I believe that my former rom was f2fs cache... |
Formating cache didnt help... Still same error.
|
I managed to flash twrp and it was access able (once). Then i formated the cache to ext3 and then back to etx4. Then I rebooted. It didnt work. Back to APX...
But suddenly it showed the google logo and now I see it in lsusb and adb devices.
|
ok, now I solved it. After the "cache wipe/format/(ext4->ext3->ext4)" using twrp I followed your guide once more and then I was able to access fastboot. From there I installed DivestOS. Thank you! |
Hi,
I have a Grouper 32gb that are looping with these two errors.
E: failed to mount /cache (invalid argument)
E: Cant mount /cache/recovery/last_locale
I have followed the guide but it still loops with the same error.
I got this error when I was flashing DivestOs from [ROM][NZH54D][2024/07/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP.
`Kalle@SLAPTOP:~/Downloads/tegra30_debrick-master$ sudo ./fusee-launcher/fusee-launcher.py ./payload/uart_payload_n7.bin -P 7330
2024-08-28 13:15:44,668 INFO:usb.core:find(): using backend "usb.backend.libusb1"
Important note: on desktop Linux systems, we currently require an XHCI host controller.
A good way to ensure you're likely using an XHCI backend is to plug your
device into a blue 'USB 3' port.
Identified a Linux system; setting up the appropriate backend.
intermezzo_size: 0x00000078
target_payload_size: 0x000005ee
Found a Tegra with Device ID: b'11fa47d43b485d01'
Stack snapshot: b'0000000000000000100000003c9f0040'
EndpointStatus_stack_addr: 0x40009f3c
ProcessSetupPacket SP: 0x40009f30
InnerMemcpy LR stack addr: 0x40009f20
overwrite_len: 0x00004f20
overwrite_payload_off: 0x00004de0
payload_first_length: 0x000005ee
overwrite_payload_off: 0x00004de0
payload_second_length: 0x00000000
b'00a0004000300040ee05000000000000'
Setting rcm msg size to 0x00030064
RCM payload (len_insecure): b'64000300'
Setting ourselves up to smash the stack...
Payload offset of intermezzo: 0x00000074
overwrite_payload_off: 0x00004de0
overwrite_len: 0x00004f20
payload_overwrite_len: 0x00004e5c
overwrite_payload_off: 0x00004de0
smash_padding: 0x000047f2
overwrite_payload_off: 0x00004de0
Uploading payload...
txing 20480 bytes total
txing 4096 bytes (0 already sent) to buf[0] 0x40003000
txing 4096 bytes (4096 already sent) to buf[1] 0x40005000
txing 4096 bytes (8192 already sent) to buf[0] 0x40003000
txing 4096 bytes (12288 already sent) to buf[1] 0x40005000
txing 4096 bytes (16384 already sent) to buf[0] 0x40003000
Smashing the stack...
sending status request with length 0x00004f20
The USB device stopped responding-- sure smells like we've smashed its stack. :)
Launch complete!
kalle@SLAPTOP:~/Downloads/tegra30_debrick-master$ sudo ./utils/nvflash_v1.13.87205_miniloader_patched --setbct --bct ./bct/nexus_7_grouper_bct.bin --configfile ./utils/flash.cfg --bl ./bootloader/bootloader-grouper-4.23.img --goNvflash v1.13.87205 started
chip uid from BR is: 0x0000000000000000015d483bd447fa11
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d483bd447fa11
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 3
device config strap: 2
device config fuse: 17
sdram config strap: 1
sending file: ./bct/nexus_7_grouper_bct.bin
./bct/nexus_7_grouper_bct.bin sent successfully
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: ./bootloader/bootloader-grouper-4.23.img
./bootloader/bootloader-grouper-4.23.img sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
kalle@SLAPTOP:~/Downloads/tegra30_debrick-master$ sudo ./utils/nvflash_v1.13.87205_miniloader_patched --resume --download EBT bootloader/bootloader-grouper-4.23.img --configfile ./utils/flash.cfg
Nvflash v1.13.87205 started
[resume mode]
sending file: bootloader/bootloader-grouper-4.23.img
bootloader/bootloader-grouper-4.23.img sent successfully
`
The text was updated successfully, but these errors were encountered: