Hi all,
I need some help.
My wife have an Samsung i747 phone which she used to store there all the pictures of our boys from the past 2 years. She never backuped the pictures.
Starting two weeks ago the phone got stuck very often, and became very hot. Last week the phone didn't power on anymore.
I could enter to download mode, but didn't succeed to go Recovery mode except of few times (I know it sounds weird, but I try a lot.. most of the times the text "Recovery Booting" for one second, and than I got the "Samsung S III" logo and the device shut down..).
So if I understood right, the was soft brick.
The few times i succeeded enter recovery mode it always print errors of something like "e: mount /system | /data | /cache failed".
I saw this thread and decide to give it a chance.
I didn't know what is the version of the bootloader (or anything else... my wife neither) so I go on the 4.3 bootloader.
I flashed the twrp 2.6.3.0 recovery and I saw there in backup section that the data is about 12giga. I couldn't make any backup of anything. I tried to reset to factory settings (without wiping the user data) and it failed(I even tried to backup the recorvery and boot partition that weights 10 mb and it failed).
I tried to flash from my sd card the:
d2att_I747UCUEMJB_bootloader
d2att_I747UCUEMJB_modem
d2att_Kernel_Stock_init.d_4.3_MJB_v1.0
AT&T_I747UCUEMJB
and everything worked but the AT&T_I747UCUEMJB.zip .
I tried flash newer twrp version, at first 2.6.3.1 and lastly 2.8.7.0. In all the same result - I can't flash the AT&T_I747UCUEMJB.zip file. the error says something about the updater (I can't read the whole error, the screen cutting the line).
Still when I open the recovery it says it couldn't load /system /cache /data partitions. I tried to change the fs type, wiping the partition, formatting - but nothing worked.
Can any one help me get the pictures out? They mean a lot to us, except the pictures from the I747 we only have a few pictures from the last 2 years.
Thanks!
p.s
I thinks that this is the log from twrp when I tried to install the AT&T_ rom:
Code:
Installing '/external_sd/AT&T_I747UCUEMJB.zip'...
Checking for MD5 file...
I:Cannot find file /external_sd/AT&T_I747UCUEMJB.zip.md5
Skipping MD5 check: no MD5 file found.
I:Zip does not contain SELinux file_contexts file in its root.
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
Blocks: 384000
Block groups: 12
Reserved block group size: 95
Created filesystem with 11/96000 inodes and 12609/384000 blocks
error: file_write: write: I/O error
E:Error executing updater binary in zip '/external_sd/AT&T_I747UCUEMJB.zip'
Error flashing zip '/external_sd/AT&T_I747UCUEMJB.zip'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'flash_done'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'action_complete'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p14
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p14', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p17
E:Unable to mount '/cache'
I:Actual block device: '/dev/block/mmcblk0p17', current file system: 'ext4'
I:Set page: 'clear_vars'
I:Set page: 'flash_done'
I:Set page: 'rebootcheck'
I:Set page: 'confirm_action'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'wipe'
I:Set page: 'advancedwipe'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
audit13 said:
Did you try mounting that data partition in TWRP? I assume you did and that didn't work for you.
You mentioned that you tried chnaging the fs, wiping, formatting. Which partitions are you referring to?
Click to expand...
Click to collapse
I tried to mount the partitions. It didn't work. In the Mount section of twrp when I clicking the system and cache partition nothing happens. And in the backup section it shows that the size of system and cache partitions is 0MB.
I tried to change the /system /cache partitions. I didn't try the /data partition because I'm afraid losing all my data.
I forgot to mention that right now, the only way I can boot to recovery and download mode is by the sd card with the debrick image.
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
audit13 said:
Since you can boot with the debrick image, did you try reflashing a bootloader or modem to the phone?
Sounds like you have the same problem as this XDA member: http://forum.xda-developers.com/galaxy-s3-att/help/failed-to-mount-data-frozen-factory-t3181035
Click to expand...
Click to collapse
If I understand correctly, its not the same problem. He couldn't mount just the /data while I can't /data /system /system. Another differnce is that his problems occured after he flashed things, mine was with the original recovery, and I can't do a factory reset.
Please tell me if I'm wrong.
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
audit13 said:
The other user could only boot his phone using a debrick image in the phone. Will your phone boot without the sdcard?
The other user had to flash a bootloader in order to boot without the sdcard in the phone.
Click to expand...
Click to collapse
I can't boot when the sdcard isn't there.
Should I try to flash another bootloader? If so, can you tell me what bootloader should I install.
The most important thing to me right now is to get my pictures back, so currently I don't care booting with the sd card. After I get my pictures I would like to make the phone work without the sd card.
Thanks!
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
audit13 said:
Do you know which bootloader was on the phone before you started flashing bootloaders?
I am not sure if flashing a bootloader and recovery will get you access to the pictures. I have never experienced a bricked s3.
Click to expand...
Click to collapse
I don't know. But what I do know is that the first time I used the debrick sd card it shows in the download mode the "warranty bit: 0" that wasn't there before. The second time I powered on the device it shows that the warranty bit is 1.
If thats help somehow recognizing the bootloader version.
I flashed (via recovery) the bootloader maximum 2 time, and via Odin few times (every time I tried another version of the recovery..something like 5 times).
I've notice that if I trying to get into download mode and release the buttons fast, the next time the device booting its showing this screen:
And when I'm going into Recovery mode its showing this screen:
Before I did the debrick the screen I has is the first one.
I thinks the second one is the debrick, because it always shows the first image for 1-2 seconds and it is rebooting and shows the second picture.
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
audit13 said:
The screen without twrp is the first screen. The second screen is how the phone would look with twrp.
The fact that the warranty bit exists in download mode means the phone has at least a 4.3 bootloader.
If the phone had a kit kat bootloader before you flashed anything, flashing the mjb bootloader is probably what bricked the phone.
Are you able to confirm which rom version was on the phone before you flashed anything? This will help determine which bootloader and modem should be flashed to the phone.
Click to expand...
Click to collapse
I didn't have the warranty bit in download mode before I used the debrick image, and I didn't flash anything before, the warranty bit appears only after I used the debrick image. So I guess I had the 4.1.2 bootloader (I remmeber that we were updating the phone once using Kies..about 2 years ago or something like that..).
I never flashed anything to this phone before the twrp last week after the brick happened. And My wife was using the Stock rom.
But 2 days ago when I tried following this thread I do flash (using twrp install section) a bootloader.(when the sd card inserted). I took the bootloader he recommended:
Use this bootloader for the AT&T i747 ONLY https://www.dropbox.com/s/vbyeorrxapwrots/d2att_I747UCUEMJB_bootloader.zip the one in the tread where I got mine hasn't been working so use this bootloader it is the same one just hosted by a different person.
Click to expand...
Click to collapse
Thanks for trying helping!
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
audit13 said:
It's also possible that the internal memory in the phone is damaged. It does happen on occasion.
Sorry, but I am out of ideas at this point.
Click to expand...
Click to collapse
I thought damaged memory is the case at first, but if so the twrp 2.6.X version wouldn't recognize that my data is about 12 giga.
How can I assure this is the case?
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
dawgdoc said:
A couple of ideas that may be of some help.
If you can boot into TWRP again you can go to >> Advanced >> Terminal Command >> Select
and enter these commands to determine current installed bootloader and modem
Code:
getprop ro.bootloader
getprop | grep version.baseband
Also, IIRC, once you are booted into your recovery, TWRP, you should be able to remove the sdcard with the debrick image and replace it with a blank card. Then, from with the Advanced menu of TWRP can you use the File Manager to copy folders/directories.
Click to expand...
Click to collapse
getprop ro.bootloader returns I747UCUEMJB (I thinks this is because I flashed the bootloader in @theramsey3 thread when I tried to follow his instrucions.)
getprop | grep version.baseband returns nothing. I tried "getprop | grep baseband" and it returns 2 result :
[ro.baseband]: [msm]
[ro.boot.baseband]: [msm]
I already tried the File Manager option. There is nothing in /data and /sdcard directories.
Thanks!
Sorry I wasn't of more help.
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
logoster said:
i believe TWRP (at least in version 2.8.x.x and newer) it will connect to your pc as a media device, which (at least on my i747) includes both the internal sd card (including the part i imagine your worried about, pictures and videos) as well as the external storage
at which point you should be able to copy files from your phone to your pc
Click to expand...
Click to collapse
I thinks it called MTP. I don't have the internal sd card. I have the external sd card only, so I can't copy my files.
Do you have any other idea?
Added the log of twrp if it will help somehow.
reading the log, it complains about not being able to mount the data, system, and cache partition
which to me reads as the phones internal storage is dead or almost dead, or heavily corrupted.
while i'm no expert, you may have to go to an actual expert to get the data recovered, because if recovery can't mount it then i don't really know how you could get any consumer hardware to do so
Related
EDIT: please delete! http://forum.xda-developers.com/showthread.php?p=44013269 a "Format data" was what I needed and an install of SuperSU.
Here's what I did:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery ~/Downloads/openrecovery-twrp-2.6.0.0-flo.img
reboot, go into twrp, click reboot, yes to root. Now it's stuck at the splash screen (with the colorful logo, not the Google + open padlock)
If I go back into twrp and try to sideload SuperSU then I get "error: closed".
I can adb push UPDATE-SuperSU-v1.51.zip but trying to flash it fails.
On the mount screen it says: Storage: Internal Storage (0MB).
I do not see anything helpful in the recovery.log I pulled:
Code:
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Error flashing zip '/sdcard/UPDATE-SuperSU-v1.51.zip'
Updating partition details...
I:Unable to mount '/usb-otg'
Not quite sure how to continue.
Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
EDIT: Fixed, formatted data as ext2, ran e2fsck, then formatted as ext4 again, then flashed userdata.img, system.img, and boot.img in fastboot.
CraftedAndroid said:
Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
Click to expand...
Click to collapse
Try using the Nexus Root Toolkit by Wugfresh to unbrick.
It will automatically install the latest stock firmware, making your device as good as new.
Just boot into bootloader mode, plug the device into a computer, open up the program, click "flash Stock", and watch as the magic happens.
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
alexfone said:
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
Click to expand...
Click to collapse
I'm looking much better than you. I only cannot mount /data and anything under it, like /data/media. Yours looks a bit irreversible if I've ever seen irreversible.
Fixed, updating OP
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: DEB-Z00_2.44.0_0213
Serial Number........: 09e4b977
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7448 KB)...
Click to expand...
Click to collapse
some attempts from fastboot flash also ends up with failure
any ideas?
fr3ker said:
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
some attempts from fastboot flash also ends up with failure
any ideas?
Click to expand...
Click to collapse
Try doing fastboot flash userdata userdata.img, fastboot flash system system.img, and fastboot flash boot boot.img in that order.
i did that too, I tried flashing tru a lot of method ... it just wont boot at all
does it have anything to do with the partitions? i cant find how to repair a partition for Nexus devices ...
^ So what's it say when you flash each .img individually? You get the "OKAY"?
You say some end in failure which ones? Throw in a fastboot format cache for the hell of it. Your bootloader and baseband are correct?
If you're getting the okay on all images and wiped everything in stock recovery.. I don't know man I might be stuck.
If you figure it out let us know. We can erase and format the partitions, usually you don't even need to use those. Hmm.. I clean flashed flo with just boot system and userdata (bootloader stayed the same as 5.1.1). Worked perfect.
Seems that we're stuck ... I've flashed a custom ROM and works perfect but when I flash any stock firmware it'll stuck at the bootani ... Flashing process were cleared until end ... I get everything as expected. I did everything founded on google and it's still fcuked up ..
Sent from my Z1 using Tapatalk
after many attempts to return my htc one m8 to stock i think i have bricked it.
my device is s-off , CID: 11111111 , MID: 0P6B12000
i have downloaded the stock firmware of 4.16.1540.8 and i flashed successfully to my device using adb, after that, i looked up stock ruu with the same id (4.16.1540.8) and i flashed it too successfully using adb.
After turning on the device it gets me always to the bootloader. I tried opening the stock recovery to wipe data but it doesn't work, even if i flased a stock firmware.
I have installed a custom recovery (twrp) and when i try to wipe data,cache,dalvik i get this errors:
E:Could not mount /data and unable to find cry pto footer
Updating partition details...
E:Unable to mount '/data'
...done
E:unable to mount storage.
E:Unable to mount /data/media during GUI start up.
Full SELinux support is present
E:Unable to mount /data/media/TWRP/. twrps when trying to read settings file.
E:Unable to mount '/data'
MTP enabled
Formating Cache using make_ext4fs function.
E:Unable to mount '/data'
E:Unknown MTP message type: 1
wiping android secure
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount syorage
i spent 3 days trying to fix it. if someone have some experience please don't hesitate to help.
aiserr said:
after many attempts to return my htc one m8 to stock i think i have bricked it.
my device is s-off , CID: 11111111 , MID: 0P6B12000
i have downloaded the stock firmware of 4.16.1540.8 and i flashed successfully to my device using adb, after that, i looked up stock ruu with the same id (4.16.1540.8) and i flashed it too successfully using adb.
After turning on the device it gets me always to the bootloader. I tried opening the stock recovery to wipe data but it doesn't work, even if i flashed a stock firmware.
I have installed a custom recovery (twrp) and when i try to wipe data,cache,dalvik i get this errors:
E:Could not mount /data and unable to find cry pto footer
Updating partition details...
E:Unable to mount '/data'
...done
E:unable to mount storage.
E:Unable to mount /data/media during GUI start up.
Full SELinux support is present
E:Unable to mount /data/media/TWRP/. twrps when trying to read settings file.
E:Unable to mount '/data'
MTP enabled
Formating Cache using make_ext4fs function.
E:Unable to mount '/data'
E:Unknown MTP message type: 1
wiping android secure
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount syorage
i spent 3 days trying to fix it. if someone have some experience please don't hesitate to help.
Click to expand...
Click to collapse
if you can get to bootloader you can recover. Download the ruu.exe for you version from here
http://forum.xda-developers.com/showthread.php?t=2701376
scroll down to RUU - EXE and click more variants and you'll find the official HTC dev edition RUU of 4.xx.xxxx.xx and run the exe. as long as you are supercid and s-off, this should reflash all partitions to a factory state. the ruu zips for this version would not let me OTA to marshmallow, but the exe did, just to let you know, so something might be screwy with the zips. adb is not required for the exe of an RUU.
fyarf said:
if you can get to bootloader you can recover. Download the ruu.exe for you version from here
http://forum.xda-developers.com/showthread.php?t=2701376
scroll down to RUU - EXE and click more variants and you'll find the official HTC dev edition RUU of 4.xx.xxxx.xx and run the exe. as long as you are supercid and s-off, this should reflash all partitions to a factory state. the ruu zips for this version would not let me OTA to marshmallow, but the exe did, just to let you know, so something might be screwy with the zips. adb is not required for the exe of an RUU.
Click to expand...
Click to collapse
i downloaded the ruu exe from htc's website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe) but when i run the RUU, the htc logo appears on the devices screen, and after few seconds i got this error:
error 155: unknown error
The Rom update utility cannot update your android phone
please get the correct rom update utility and try again
Stop being in 2 threads at the same time !
http://forum.xda-developers.com/showthread.php?t=2897783
Mr Hofs said:
Stop being in 2 threads at the same time !
http://forum.xda-developers.com/showthread.php?t=2897783
Click to expand...
Click to collapse
should i remove this one?
aiserr said:
should i remove this one?
Click to expand...
Click to collapse
You can't remove it. But stop posting in either one of them. It's annoying and not good to follow at what point you are and what you are doing exactly.
Cheers
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?
Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.
SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.
For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…
I have tested 2 GSI's so far, phh's AOSP and AndyYan's LineageOS 19.1.
Everything works so far except:
MTP file transfer
Fingerprint reader
File encryption (GSIs don't boot if you dont disable encryption)
So, if you wanna install one, here's what I did:
Install Prove N's Unofficial TWRP and follow his guide. DONT INSTALL MAGISK, IT HAS THE IMEI PROBLEM AND ITS NOT TESTED WITH GSIs
Download your preferred GSI, I recommend lineage-19.1-20220320-UNOFFICIAL-arm64_bvS.img.xz, comes without GAPPS (Use bgS if you want em).
Extract it and rename the .img file to system.img
(Optional) Download this vendor.img, I made a treble overlay and added it to the image. The rom should be more stable and power management should be fixed with that. I still have to push the changes to github.
Download ChonDoe_Flasher.zip, it's a tool to flash dynamic partitions. It checks your storage for system.img and vendor.img.
Get a microSD card, and copy to the root of it the ChonDoe_Flasher.zip, system.img and vendor.img.
Boot to TWRP, and install the ChonDoe zip, wait till it finishes flashing.
Reboot to TWRP again, so it can mount the vendor partition again, go to the terminal and type multidisabler, so we remove encryption.
Format data, internal storage and reboot, you should be ready to go.
Settings in PHH Treble Settings
Go to Samsung features and check "Enable extended brightness range" and "Enable access to all cameras".
Go to Misc features and check "Use alternate way to detect headsets"
To get the display working at 90hzs go to "Force FPS" and check the option.
On camera check "Expose Aux cameras" and "Force Enable Camera2API HAL3" (In theory you should get better photos with that but I didn't go outside today lol)
For the lack of MTP file transfer, I'm using ADB instead of MTP with this tool for uploading and getting files from internal storage: Python ADB File Explorer. Suprisingly it's faster than MTP for some reason...
I know MTP can be fixed changing the kernel driver, I have compiled the kernel from @Prove N. , he had some USB fixes, but I don't know how to pack it for Samsung, It could be nice to have it for GSIs. If anyone wants to help me with these small issues it would be awesome.
Report bugs, workarounds and fixes here in this thread, let's try to make this phone usable!
I've recently bought this phone and installed LineageOS straight away. I used my alternative method without TWRP, by repacking super.img using my script, which I've modified to support SM-A325F. Too bad the fingerprint sensor does not work. Can anyone confirm it does not work regardless of on which Android version a GSI is based on?
I already have TWRP on my A32 and have Magisk. Followed the guide, unfortunately phone didn't boot up. Instead it reboots to recovery. The hereunder error appears while flashing.
Code:
PARTITIONS FLASHER
| Released at 2021, January 10
| Developed by ChonDoe
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/busybox-arm
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/e2fsck
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/installer.sh
Archive: /external_sd/ChonDoe_Flasher.zip
inflating: /tmp/resize2fs
ENVIRONMENT SETUP
| Unmount System
umount: can't unmount /system: Invalid argument
umount: can't unmount /system_root: Invalid argument
umount: can't unmount /system_ext: No such file or directory
umount: can't unmount /product: Invalid argument
umount: can't unmount /vendor: Invalid argument
| Detecting Partition Layout
| Dynamic partition detected
| System Block: /dev/block/dm-0
| Product Block: /dev/block/dm-2
| Vendor Block: /dev/block/dm-1
FLASHING SYSTEM IMAGE
Invalid sparse file format at header magic
Failed to read sparse file
703357+0 records in
703357+0 records out
2880950272 bytes (2.7GB) copied, 34.579540 seconds, 79.5MB/s
| System flashed as raw image
| Attempt to Resize Partition
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
/: 7386/7744 files (12.1% non-contiguous), 684040/692238 blocks
resize2fs 1.45.6 (20-Mar-2020)
Resizing the filesystem on /dev/block/dm-0 to 1217099 (4k) blocks.
The filesystem on /dev/block/dm-0 is now 1217099 (4k) blocks long.
| Done
FLASHING PRODUCT IMAGE
| Cant find product.img
FLASHING VENDOR IMAGE
| Vendor flashed as sparse image
| Attempt to Resize Partition
e2fsck 1.45.6 (20-Mar-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Padding at end of inode bitmap is not set. Fix? yes
/dev/block/dm-1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/dm-1: 1140/41760 files (0.0% non-contiguous), 124955/166988 blocks
resize2fs 1.45.6 (20-Mar-2020)
Resizing the filesystem on /dev/block/dm-1 to 185664 (4k) blocks.
The filesystem on /dev/block/dm-1 is now 185664 (4k) blocks long.
| Done
I:TWFunc::Set_Brightness: Setting brightness control to 5
| Enjoy
I:Updater process ended with RC=0
I:Install took 59 second(s).
E:Unable to unlock /dev/block/mmcblk0p42 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p14 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p18 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p8 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p11 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p4 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p15 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0boot0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p5 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p7 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p13 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p10 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p12 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p9 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0 for flashing: (null)
E:Unable to unlock /dev/block/mmcblk0p6 for flashing: (null)
Updating partition details...
I:checking for twrp app
I:Data backup size is 0MB, free: 108145MB.
...done
I:Set page: 'flash_done'
I:TWFunc::Set_Brightness: Setting brightness control to 200
I:operation_end - status=0
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
I:TWFunc::Set_Brightness: Setting brightness control to 200
I:Set overlay: ''
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'copylog'
I:Set page: 'action_page'
I:operation_start: 'Copy Log'
uluruman said:
I've recently bought this phone and installed LineageOS straight away. I used my alternative method without TWRP, by repacking super.img using my script, which I've modified to support SM-A325F. Too bad the fingerprint sensor does not work. Can anyone confirm it does not work regardless of on which Android version a GSI is based on?
Click to expand...
Click to collapse
upload firmware plz
jasurshoir said:
upload firmware plz
Click to expand...
Click to collapse
Ok, I'll try not to mess it all up this time...
Here is the link to download: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}. That is super.img I've created using my script, it is packed into a tar archive and zipped to reduce the size for file sharing. It is specifically for SM-A325F, based on the NPB (Nepal/Butan) version of the firmware and contains LiR v3.16. After unzipping it is ready to be flashed using Odin into the AP slot over the stock NPB firmware. That means, you have to download and flash it first, then flash the super.img. After each flashing go straight into the Recovery mode and do factory reset, only then boot the system.
But that's not all, additionally you have to extract and flash optics.img from your regional firmware. Here is how to do it. Changing optics.img to your regional one is not compulsory but with the Nepalese/Butanese one you'll only have a few major cellular providers working. You can do it at any time after flashing the system, it does not require factory reset.
I have chosen the NPB stock firmware as the basis because after analyzing contents of other regional firmware I've found that it is probably the most non-bloated and privacy-respecting of all (the worst were Russian and European).
uluruman said:
Ok, I'll try not to mess it all up this time...
Here is the link to download: .... That is super.img I've created using my script, it is packed into a tar archive and zipped to reduce the size for file sharing. It is specifically for SM-A325F, based on the NPB (Nepal/Butan) version of the firmware and contains LiR v3.16. After unzipping it is ready to be flashed using Odin into the AP slot over the stock NPB firmware. That means, you have to download and flash it first, then flash the super.img. After each flashing go straight into the Recovery mode and do factory reset, only then boot the system.
But that's not all, additionally you have to extract and flash optics.img from your regional firmware. Here is how to do it. Changing optics.img to your regional one is not compulsory but with the Nepalese/Butanese one you'll only have a few major cellular providers working. You can do it at any time after flashing the system, it does not require factory reset.
I have chosen the NPB stock firmware as the basis because after analyzing contents of other regional firmware I've found that it is probably the most non-bloated and privacy-respecting of all (the worst were Russian and European).
Click to expand...
Click to collapse
all good please create one ui firmware
jasurshoir said:
all good please create one ui firmware
Click to expand...
Click to collapse
Do you really need it? First, OneUI is not to be trusted as it's proprietary and not fully open-source, second, the only GSI version of it I can find (repacked by erfanoabdi) is very old (2019).
uluruman said:
Do you really need it? First, OneUI is not to be trusted as it's proprietary and not fully open-source, second, the only GSI version of it I can find (repacked by erfanoabdi) is very old (2019).
Click to expand...
Click to collapse
Yes, I really need this one, I saw on the Internet nippon gsi one oh 4.0 downloaded installed but did not start
add please play servise
my log after install nippon gsi one ui 4.0 keep reboot
jasurshoir said:
Yes, I really need this one, I saw on the Internet nippon gsi one oh 4.0 downloaded installed but did not start
add please play servise
Click to expand...
Click to collapse
Ok, here it is: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
It's the same Nippon GSI you mentioned, I've just repacked it into super.img. I don't know whether it's gonna work or not. Sometimes the system is just incompatible with the phone hardware or the kernel. All I can do is to repack it all, analyzing logs or tweaking the kernel is currently beyond my abilities.
Here is also the version of LiR with GApps (Google Play, etc.): {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
I've also updated my script, besides other improvements now it supports GZ-packed GSI images.
P.S.: I really don't recommend using any of the Google services. Don't let corporations gather your usage data. You bought the phone and from now on it should be all yours, with all of its data, like a PC in the good old days. You own your device, and nobody has the right to stick their nose into how you use your phone, gather any statistics and push you any ads. You always have a choice to turn down privacy-unfriendly stuff, the price of that "inconvenience" is actually ridiculous. From my point of view, there is simply no point in using non-stock systems if they are still littered with the privacy-unfriendly bloatware.
uluruman said:
Ok, here it is: ...
It's the same Nippon GSI you mentioned, I've just repacked it into super.img. I don't know whether it's gonna work or not. Sometimes the system is just incompatible with the phone hardware or the kernel. All I can do is to repack it all, analyzing logs or tweaking the kernel is currently beyond my abilities.
Here is also the version of LiR with GApps (Google Play, etc.): ...
I've also updated my script, besides other improvements now it supports GZ-packed GSI images.
P.S.: I really don't recommend using any of the Google services. Don't let corporations gather your usage data. You bought the phone and from now on it should be all yours, with all of its data, like a PC in the good old days. You own your device, and nobody has the right to stick their nose into how you use your phone, gather any statistics and push you any ads. You always have a choice to turn down privacy-unfriendly stuff, the price of that "inconvenience" is actually ridiculous. From my point of view, there is simply no point in using non-stock systems if they are still littered with the privacy-unfriendly bloatware.
Click to expand...
Click to collapse
thank you one ui not working play market worked youre new lineage firmware
does it also work with the PixelExpierence GSI?
Franzyy said:
does it also work with the PixelExpierence GSI?
Click to expand...
Click to collapse
Probably. Try it: {Mod edit: Link removed. ufile.io is not accepted as file host on XDA}
uluruman said:
Probably. Try it: ...
Click to expand...
Click to collapse
I have a question. Is this file linked above different than the PixelExpirence GSI from GitHub? Because the file is about 1GB larger than the "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz" from https://github.com/ponces/treble_build_pe/releases?page=1
Franzyy said:
I have a question. Is this file linked above different than the PixelExpirence GSI from GitHub? Because the file is about 1GB larger than the "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz" from https://github.com/ponces/treble_build_pe/releases?page=1
Click to expand...
Click to collapse
It is different, although based on it. It is the full Super partition, while "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img" is only the System dynamic sub-partition within it. Besides System there are also Vendor, Product and ODM dynamic partitions included (taken directly from the NPB U2 stock firmware). Basically that's all the work my script is doing: repacking all the dynamic partitions inside super.img altogether, after which it contains another GSI but is still directly flashable with Odin.
There is an alternative way of installing a GSI, although it is far less straightforward. See this and this post. The latter deals with dynamic partitions, without which you cannot flash a GSI.
uluruman said:
It is different, although based on it. It is the full Super partition, while "PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img" is only the System dynamic sub-partition within it. Besides System there are also Vendor, Product and ODM dynamic partitions included (taken directly from the NPB U2 stock firmware). Basically that's all the work my script is doing: repacking all the dynamic partitions inside super.img altogether, after which it contains another GSI but is still directly flashable with Odin.
Click to expand...
Click to collapse
Ok thx for explaining it
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Franzyy said:
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Click to expand...
Click to collapse
Open "Phh Treble Settings" from the settings, then "Misc features" and check "Use alternative way to detect headsets" in the Audio section.
Franzyy said:
I followed your guide so that i can get PixelExpirence on my A32 but my wired headphones doesnt work when plugged in, it just plays music on the speaker on the phone. Do you know a fix?
Click to expand...
Click to collapse
how it works PE? I saw it is still in beta, does it works with 2 sim? thank you