Database Users

[Help] Flashing an .SBF [Solved]

Solved by myself. Turns out I had to find and download RSDLite v5.4.4 and it instantly found my Xoom.
Okay, so I've followed the steps to revert back to HRI66 and relock my bootloader (I've also tried to do it on the same version, but with the unlocked bootloader).
I am using RSDLite v5.0 and the latest drivers from Motorola for USB connectivity.
I'm trying to flash the .SBF file from here, but RSDLite keeps giving me errors.
I am on Windows 7 64-bit, but I have also tried to do it on my laptop that has Windows XP 32-bit.
This is what it says when I first start up RSDLite:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it says when I hit "Show Device":
This is what it says when I try to hit "Start":
Any solutions?
This is what my error log is telling me:
23:55:36, October 18, 2011
Line: 2201
ERROR: Device S Flash MZ600 is not supported.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashCharacteristics.cpp
Device ID: 0
23:55:36, October 18, 2011
Line: 1041
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
Click to expand...
Click to collapse

I've never used RSDLite. Can you give a bit more detail about your solution?

okantomi said:
I've never used RSDLite. Can you give a bit more detail about your solution?
Click to expand...
Click to collapse
Well, there's really not much else to how I fixed it.
I tried using RSDLite v5.0, and a few other versions below it, and none of them were correctly identifying my Xoom. Then I found v5.4.4 and it worked perfect.

software updates:signature verification failed

i have a sgs4 sprint rooted cwm recovery stock rom, and i am not able to install any software update i continue to receive this error:
E: invalid command argument
E: failed to verify whole file signature
E: signature verification failed
" / system/framework/ services.odex" has unexpected contents
E: error in/cache/e9fcadf8ac862c1b6c99b9fad69b16613a49a6a. user_L720_spt_NAE_csb_user_rp_to_ng2_csb_user_rp_update_fwd.zip status7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

reesemtk61 said:
i have a sgs4 sprint rooted cwm recovery stock rom, and i am not able to install any software update i continue to receive this error:
E: invalid command argument
E: failed to verify whole file signature
E: signature verification failed
" / system/framework/ services.odex" has unexpected contents
E: error in/cache/e9fcadf8ac862c1b6c99b9fad69b16613a49a6a. user_L720_spt_NAE_csb_user_rp_to_ng2_csb_user_rp_update_fwd.zip status7
View attachment 2916698
View attachment 2916699
Click to expand...
Click to collapse
The reason you can't install a software update is because you have to be bone stock. With no mods or custom recovery.
Sent from my SPH-L720

ROMANTiC KiD said:
The reason you can't install a software update is because you have to be bone stock. With no mods or custom recovery.
Sent from my SPH-L720
Click to expand...
Click to collapse
question is there a bone stock file i can flash or odin

reesemtk61 said:
question is there a bone stock file i can flash or odin
Click to expand...
Click to collapse
Look in development.

how to fix " updating partition details... ... unmounting of / system" (ZC550KL)

how to fix " updating partition details... ... unmounting of / system" (ZC550KL)
firstly, i’m looking for all the resuilts on web and xda. but i can't fix it. i need your help because I had a problem with my phone so i can’t use it now (zenphone max ZC550KL - MSM8916) . I took a rom on here -MIUI 8 : goo.gl/hB9Rzh
Quote:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
. In TWRP , I wipe everything: include Dalvik, System, Data and cacher.
and installed Rom by TWRP 3.2.0- 0
And i saw a error: unmounting of/ system....
now. my phone hangs at the boot screen.
i tryed:
- installed SU before install Rom
- in screen WIpe -> advaned wipe -> repair or change file system - > REpaier
- > resize
- > chage file system -> FAT
- > exfat
- > ext4
- > F2Fs
i don't know what to do
screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Download Asus Flash Tool and flash a raw file

Formatted storage to f2fs and now can't mount anything

So i messed up badly...
Really badly...
I finally unbricked my Nexus 7 with the help of nvflash.
Had trouble with mounting /system.
Fixed it.
Locked Bootloader in process of fixing.
Didn't find a solution.
Tried to flash a new ROM.
Formated data, cache and system as f2fs.
Installed ROM from TWRP.
Got message it succeeded.
Rebooted.
No ROM.
So back into recovery.
New problem:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't load any partition at all.
Can't fix them.
Can't wipe them.
Can't format them.
Tried to reset everything by flashing the blob files again with nvflash.
Finally unlocked the bootloader with this.
But still no storage.
Even internal storage is shown as 0mb.
I fixed the system problem before by using this:
Code:
cat /etc /fstab
make_ext4fs /dev/block/<insert id of system block from fstab here>
But I don't have any of those blocks remaining. So I can't reference anything here.
I guess I have to format the whole drive somehow and repartition it. But I don't know how to do that.
I would really appreciate the help.
I got so far and always do something dumb to create a new problem
EDIT:
Also I just had a look into the filesystem with twrp and I guess I really need to build everything from the ground up. There should be a few more blocks and partitions :/
EDIT 2:
If anyone can run the following 2 commands on a 16GB Nexus 7 and post the output I can try to create the partitions with parted. Would really appreciate it
Code:
cat /proc/partitions
cat /etc/fstab
and if you have parted then
Code:
/parted block/mmcblk0
(parted) p

Latest TWRP 3.5.2 BROKEN With LineageOS 18.1 - Galaxy S10+ Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This's my error message in TWRP:
It appears everywhere, while flashing, wiping or trying to backup/restore.
OS: LineageOS 18.1
Recovery; TWRP 3.5.2 (Latest)
Rooted with Magisk and flashed pre-rooted TWRP image
-----------------------------------------------------
Error reason:
LineageOS 18.1 encrypts /data in a way that prevents TWRP from decrypting it.
Even when choosing no locking mechanism (Pin, Swipe etc.) decryption still fails.
Error symptoms:
Backup/Restore via TWRP is not working due to /data error
Constant warning message "could not open /data permission denied"
Lineage Recovery has the exact same problem, it actually doesn't even display the internal storage due to its inability to decrypt it.
-------------------------------------------------------
How I've "fixed" it:
Formatting /data stops the error messages, but that's just because the encryption is removed by wiping the entire drive.
This also messes up the ability to create backups in TWRP.
-------------------------------------------------------
For comparison, this is what the log is supposed to look like when /data decryption has been successful:

Just found out that can't backup rom...
OS: LineageOS 18.1
Recovery; TWRP 3.5.2 (Latest)
Rooted with Magisk and flashed pre-rooted TWRP image
...setup is just like yours.
If you have found out some better solution than format, please share link.
Thank you!