Related
I am by no means good at this. I installed Hero v.4 and it was working ok. I wanted Haykuro's Rosie UI build, but could never get past the waving little android HTC screen. It would sit at black screen. I finally got it fixed and here, exactly, is how I did it and what the problem was:
1. The SD card was appropriately formated into Fat32 and Ext-2 formats per this thread-http://forum.xda-developers.com/showthread.php?t=512873
2.I knew Rosie should run since Hero v.4 ran. The only difference, really, was the app2sd requirement. Following Haykuro's directions in this thread, the developer clearly states
"for those of you that don't know how to place app_s into sd card do this:
Code:
adb push app_s /system/sd/app_s
3. well, I did that just fine but Rosie would never boot. I got to looking at the ADB for dummies page found here http://forum.xda-developers.com/showthread.php?t=502010 and found out I could view the contents of my Ext partition with ADB. I used ADB shell command>> adb shell then #ls.
4. It showed me that the ADB push command (adb push app_s /system/sd/app_s) did indeed put the files inside the sd directory, but within another app_s folder. my structure looked like this (using exactly Haykuro's instructions).
adb shell
system/sd/apps_s/app_s =>then all the .apk files.
For those of you having the black screen issue, you might want to take a look
at your directory structure as described above.
To fix it, I followed Haykuro's directions exactly, but omitted the last parameter (which was app_s). Typed this
adb push app_s /system/sd
It deposited all the .apk files directly inside a app_s folder in the sd directory. I didn't know how to get rid of the extra folder called app_s, so I left it there.
Rosie booted fine......
i had the same problem. i formatted my sd card tho, repartitioned and fixed the extra folder problem. wish i had your guide back then it woulda saved me so much time
I get this code whenever I try to adb push
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Alex P>cd C:\android-sdk-windows-1.5_r2\tools
C:\android-sdk-windows-1.5_r2\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>adb shell
# cp app_s /system/sd
cp app_s /system/sd
cp: cannot stat 'app_s': No such file or directory
# exit
exit
C:\android-sdk-windows-1.5_r2\tools>ls /system/sd
'ls' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>
Keep getting that cannot stat.
it looks like you mounted your phone (remount command). I am by no means an expert at this stuff, but it was my understanding that your phone is supposed to be unmounted to use any adb commands. could be wrong though.
apfroggy0408 said:
I get this code whenever I try to adb push
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Alex P>cd C:\android-sdk-windows-1.5_r2\tools
C:\android-sdk-windows-1.5_r2\tools>adb remount
remount succeeded
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>adb shell
# cp app_s /system/sd
cp app_s /system/sd
cp: cannot stat 'app_s': No such file or directory
# exit
exit
C:\android-sdk-windows-1.5_r2\tools>ls /system/sd
'ls' is not recognized as an internal or external command,
operable program or batch file.
C:\android-sdk-windows-1.5_r2\tools>adb push app_s /system/sd
cannot stat 'app_s': No such file or directory
C:\android-sdk-windows-1.5_r2\tools>
Keep getting that cannot stat.
Click to expand...
Click to collapse
Make sure you "cd" to the correct forlder that your "app_s" is in. So for example if you have the app_s folder in c:\android (thats where i always work from) type cd c:\android then adb push app_s.......
If I cd to c:\android won't it take me out of adb?
nope.
adb simply tells the computer you are commanding the phone.
so cd to where the folder is, then run adb push
I keep getting this message
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Main> cd c:\android-sdk-windows-1.1_r1\tools
c:\android-sdk-windows-1.1_r1\tools>adb remount
remount succeeded
c:\android-sdk-windows-1.1_r1\tools>adb shell
# cd c:\arnold adb push app_s /system/sd
cd c:\arnold adb push app_s /system/sd
cd: bad substitution
# cp C:\arnold app_s /system/sd
cp C:\arnold app_s /system/sd
cp: cannot stat 'C:arnold': No such file or directory
cp: cannot stat 'app_s': No such file or directory
#
what im I doing wrong? plz help thanks. Im stuck at the boot loop screen.
pinetreehater said:
it looks like you mounted your phone (remount command). I am by no means an expert at this stuff, but it was my understanding that your phone is supposed to be unmounted to use any adb commands. could be wrong though.
Click to expand...
Click to collapse
Seems I couldn't run adb without mounting.
Edit: Finally got it working.
What I ended up just doing was using ubuntu and creating the app_s folder in the ex2 manually and to me seems like the easiest way to do it. Luckily I have my eee running crunchbang.
Can anyone help me with rooting U8800pro running the official 2.3.5 ?
I tried all the methods I was using for the U8800 but all of them doesn’t work... Any advice ?
i have the same problem, how to root???
linomaniac said:
i have the same problem, how to root???
Click to expand...
Click to collapse
i'm searching everywhere for 3 days now with nothing usefull
If automatic ways failed try this:
http://forum.xda-developers.com/showthread.php?t=1423422
dancer_69 said:
If automatic ways failed try this:
http://forum.xda-developers.com/showthread.php?t=1423422
Click to expand...
Click to collapse
i think its not that easy to me to do it manual
but thanks anyway for trying to help
Of course automatic ways are easier, but it' s not that difficult, just need a little more time and attention.
The other way is to find a prerooted boot.img and put it to .cust_backup/image folder(replacing the original). I haven't pro model, so my boot.img will not work
dancer_69 said:
Of course automatic ways are easier, but it' s not that difficult, just need a little more time and attention.
The other way is to find a prerooted boot.img and put it to .cust_backup/image folder(replacing the original). I haven't pro model, so my boot.img will not work
Click to expand...
Click to collapse
i tried this way but it didn't work too.. i found a prerooted boot.img.. replaced the original one but it didnt work
To just say didn't work doesn't help. Write where you get an error and which is. Then maybe I can help you(or someone with more knowledge).
dancer_69 said:
To just say didn't work doesn't help. Write where you get an error and which is. Then maybe I can help you(or someone with more knowledge).
Click to expand...
Click to collapse
i got the prerooted boot.img file for the U8800pro... replaced it with the original one.. But the phone is not booting.. It stuck on the huawie logo (the 1st logo before the one with the animation) so i had to put back the original one to make it work
I mean the error on manual rooting.
As fro prerooted boot.img file, are you sure that is compatible with ther rom you have? If is from a custom rom will not work. You need the boot.img of a phone with the same rom as yours, just rooted.
well, maybe it wasn't compatible with my stock rom.. do you have anywhere where i can find some prerooted imgs ?
and about the manual root.. i didnt got any errors coz i didnt know how to wirte those codes :s
Sorry I' don't know because I haven't a pro model and I don't know if there is a rooted boot.img uploaded fro pro mode. Maybe a member with pro read your thread and upload his img file.
-About manual rooting, you need to open DOS command prompt window. It' s in all progarms -> accessories
If you put the DoomLordRoot program in the root directory of your C drive and rename this folder to DoomLordRoot.v3(if have another name), you need to just put the commands one by one as given on the link I posted.
You just need to put first the command:
cd \DoomLordRoot.v3\files
to go to directory in which adb.exe is.
You can check if you are in the right path if you enter the command:
dir
afterwards. If you are in correct folder you'll see the files which are in c:\DoomLordRoot.v3\files directrory listed.
After that just start to follow the directions of the link. Just hit enter after every command you put. If you don' t see errors after every command you're ok. If you get an error on a command, write it here, for farther help. I don' t think that you' ll get an error, because I've done this proccess about 5 times and never get an error. But if you do, just put it here to see if we can help.
Thanks alot bro for the help.
well, i followed what u said but i think i got confused somewhere.. i'll type what i got.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>cd\
C:\>cd DoomLordRoot.v3
C:\DoomLordRoot.v3>cd files
C:\DoomLordRoot.v3\files>adb shell
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
$
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
$ ^C
C:\DoomLordRoot.v3\files>adb shell
$ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
$
$ /data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$
$ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
$
VaMpYMaSTeR said:
Thanks alot bro for the help.
well, i followed what u said but i think i got confused somewhere.. i'll type what i got.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>cd\
C:\>cd DoomLordRoot.v3
C:\DoomLordRoot.v3>cd files
C:\DoomLordRoot.v3\files>adb shell
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
$
$ ./data/local/tmp/zergRush
./data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
$
$ ^C
C:\DoomLordRoot.v3\files>adb shell
$ chmod 755 /data/local/tmp/busybox
chmod 755 /data/local/tmp/busybox
$
$ /data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mount -o remount,rw /system
mount: permission denied (are you root?)
$
$ dd if=/data/local/tmp/busybox of=/system/xbin/busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
/system/xbin/busybox: cannot open for write: Read-only file system
$
Click to expand...
Click to collapse
Put su or sudo before command. like this "su /data/local/tmp/busybox mount -o remount,rw /system"
Yes, seems that you didn' t give the su command before(I think I've include command su, on my tutorial but I' m not sure. I'll check it).
If you see the symbol $ this means that you haven't get root rights yet.
Seems that zergrush succeed, so everytime after adb shell command, first you need to give the command:
su
If device is rooted, you'll see that the symbol changes to #
I think that you' re in good way though.
when i put SU in the begining it give me this :
su: permission denied
if you rebooted the phone you must run zergrush again.
Zergrush is the hack that unlocks the root account temporary. If you didn' t success to put su program on the right place, rooting access loosed after rebooted. su makes root permanent, busybox is an advanced shell and superuser is the app which used to give or denied root rights to apps which asking for this.
First be sure that zergrush is copied to data/local/tmp and you give to it the right permissions(all commands are in tutorial)
These messages mean that zergrush running
[+] Found a GingerBread ! 0x00000118[*] Scooting ...
bugreport dir[/data/local/tmp] exist.[*] Sending 149 zerglings ...
bugreport dir[/data/local/tmp] exist.[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
Click to expand...
Click to collapse
after that check if root succeed by input su command. If you get the # sign you're good to go to continue(exit shell etc)
i'm so sorry, but what do you mean with "If you didn' t success to put su program on the right place" ???? what where is the right palce ?
Some of the commands on tutorial handle the su program.
Push it to /system/bin(this is the right place), change its ownership, permissions etc.
For these commands to succeed(and also the commands for busybox and superuser), first need to enter to root account, by command su:
adb shell (press enter)
su (press enter)
these give the # sign which means that you are root.
If you don' t do this all commands will fail with errors as:
permission denied or cannot write to...
now i'm getting this:
C:\DoomLordRoot.v3\files>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ chmod 777 /data/local/tmp/zergRush
chmod 777 /data/local/tmp/zergRush
Unable to chmod /data/local/tmp/zergRush: No such file or directory
$
i think i will give up
Have anyone figured out how to put twrp on version ATT D80010o
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
datechnerd said:
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
how do i do this
ralphie1267 said:
how do i do this
Click to expand...
Click to collapse
enable usb debugging, plug phone into pc, and you'll need adb in attachments
open the folder you extracted adb to, shift right click in the folder, open command window here, then follow the example in the previous post
datechnerd said:
enable usb debugging, plug phone into pc, and you'll need adb in attachments
open the folder you extracted adb to, shift right click in the folder, open command window here, then follow the example in the previous post
Click to expand...
Click to collapse
i have minumal adb and fastboot can i use this
datechnerd said:
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
sorry for the late response I was at work....
datechnerd said:
If you pull the aboot.img I'll patch twrp for the device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]roid:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
for some reason I cant run command I downloaded it to the desktop
antawnm26 said:
for some reason I cant run command I downloaded it to the desktop
Click to expand...
Click to collapse
put it in a folder, then open the folder, hold shift and right click in a blank spot of the fold and open command window
datechnerd said:
put it in a folder, then open the folder, hold shift and right click in a blank spot of the fold and open command window
Click to expand...
Click to collapse
sweet it came up...Im not that great at it so Im going to need you to walk me through it
[email protected]:~$ adb shell- this should be my user name?
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
antawnm26 said:
sweet it came up...Im not that great at it so Im going to need you to walk me through it
[email protected]:~$ adb shell- this should be my user name?
[email protected]:/ $ su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
[email protected]:/ $ exit
[email protected]:~$ adb pull /data/local/tmp/aboot.img
3293 KB/s (2097152 bytes in 0.621s)
Click to expand...
Click to collapse
the username is just from an example
datechnerd said:
the username is just from an example
Click to expand...
Click to collapse
ok im getting errors when I copy ~$ adb shell
C:\Users\Bull\Desktop\adb>~$ adb shell
'~$' is not recognized as an internal or external command,
operable program or batch file.
antawnm26 said:
ok im getting errors when I copy ~$ adb shell
C:\Users\Bull\Desktop\adb>~$ adb shell
'~$' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
just type
Code:
adb shell
don't type $ or #
C:\Users\Bull\Desktop\adb>:/ $ su
C:\Users\Bull\Desktop\adb>:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
C:\Users\Bull\Desktop\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/loc
al/tmp/aboot.img
dcc.1/by-name/aboot of=/data/local/tmp/aboot.img <
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.100 secs (10485760 bytes/sec)
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Bull\Desktop\adb>pull /data/local/tmp/aboot.img
'pull' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>~$ adb pull /data/local/tmp/aboot.img
'~$' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>
d80010o
Any success guys?
datechnerd said:
just type
Code:
adb shell
don't type $ or #
Click to expand...
Click to collapse
i have abb running .i have att d80010c i downloaded openrecovery twrp 2.6.3.3 g2att.img .what comand do i need to use thanks
ralphie1267 said:
i have abb running .i have att d80010c i downloaded openrecovery twrp 2.6.3.3 g2att.img .what comand do i need to use thanks
Click to expand...
Click to collapse
think i got it i had to use esfile explorer to get it from the data/local because i suck at adb, but i got all the way with but started getting errors..hold on let me put it in drive
Code:
[CODE]
[/CODE]
antawnm26 said:
C:\Users\Bull\Desktop\adb>:/ $ su
C:\Users\Bull\Desktop\adb>:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboo
t of=/data/local/tmp/aboot.img
C:\Users\Bull\Desktop\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/loc
al/tmp/aboot.img
dcc.1/by-name/aboot of=/data/local/tmp/aboot.img <
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.100 secs (10485760 bytes/sec)
[email protected]:/ # chmod 644 /data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Bull\Desktop\adb>pull /data/local/tmp/aboot.img
'pull' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>~$ adb pull /data/local/tmp/aboot.img
'~$' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Bull\Desktop\adb>
Click to expand...
Click to collapse
Code:
adb pull /data/local/tmp/aboot.img
datechnerd said:
Code:
[CODE]
[/CODE]
Code:
adb pull /data/local/tmp/aboot.img
Click to expand...
Click to collapse
https://www.dropbox.com/sh/xfv49im0n1s3uy3/l6dxsrpKy9
antawnm26 said:
https://www.dropbox.com/sh/xfv49im0n1s3uy3/l6dxsrpKy9
Click to expand...
Click to collapse
NON-flashablezips
flash with loki
if you don't know how rename the .lok to .img and put it on your phone and flash it with flashify instead
datechnerd said:
flash with loki
if you don't know how take the .img put it on your phone and flash it with flashify instead
Click to expand...
Click to collapse
I know its asking a lot but is there a guide on flashing with loki? also, do i just copy the image without the other files to my sdcard and flash with flashify?
I've been using on my I9505 since 2013 the very old (3.11.1) MIUI ROM by bmarko which was AOSP CM based and it supports MicroSD EXT4 out of the box..
Now I've swiched to a much newer version (Version: 5.7.24 and future) by Shiro (http://en.miui.com/download-110.html) which is a (non-TW based) 4.4.4 MIUI v6 very beautiful but ...
... but my big surprise is that it do not automount a MicroSD EXT4 formatted.
I had an old procedure that works for TW based 4.2.2 old MIUI but it doesn't work here.
It was:
Step1:
Code:
su
setprop service.adb.tcp.port 5555
adb kill-server
stop adbd
start adbd
HOME=/sdcard adb start-server
adb connect localhost
adb -s localhost:5555 shell
exit
stop adbd
cat /sdcard/.android/adbkey.pub >> /data/misc/adb/adb_keys
start adbd
step 2:
Code:
#making sure adbd is on port 5555:
setprop service.adb.tcp.port 5555
adb kill-server
stop adbd
start adbd
#starting server in a way where proper private key is used:
HOME=/sdcard adb start-server
# connecting server to localhost
adb connect localhost
sleep 2
#actually mounting sdcard and re-running vold :
adb -s localhost:5555 shell su -c /system/xbin/msd2.sh
#if we don't kill server it will drain power like crazy:
adb kill-server
Step 3:
Code:
mount -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard && sleep 5 && /system/bin/vold
Unfortunately it doesn't work here...
Ext4 is very much faster and safer than FAT based filesystems, and it is the standard for Android on any partition but MicroSD... :crying:
Now that we all use MTP protocol to share android disks there's no need for fat filesystem anymore ...
Do you have an idea on how to properly automount (even using a boot script) a MicroSD ext4 formatted on our amazing MIUI??
Kind regards.
These commands dont seem to work on my galaxy a5 2016. Can someone please help
[email protected]:/ $ sm list-disks
disk:179,32
[email protected]:/ $ sm partition disk:179,32 private
[email protected]:/ $ reboot
that would most probably require kernel support, just like Always On Display.
go here, it has all that is required......works great....http://forum.xda-developers.com/sam...oblem-to-configure-adoptable-storage-t3458536