Internal sdcard inaccessible to OS, but accessible to TRWP recovery - Android Q&A, Help & Troubleshooting

I can see the contents of the internal sdcard when using the file browser in TRWP recovery, but after a boot-up the /system/sdcard is not accessible to the Android OS. I noticed the problem after I flashed system.img and boot.img in order to get rid of Apps Ops X.
Is there an easy was to restore access for the operating system and keep the data?
Nexus 5 / 4.4.2

Bump!

A380 said:
I can see the contents of the internal sdcard when using the file browser in TRWP recovery, but after a boot-up the /system/sdcard is not accessible to the Android OS. I noticed the problem after I flashed system.img and boot.img in order to get rid of Apps Ops X.
Is there an easy was to restore access for the operating system and keep the data?
Nexus 5 / 4.4.2
Click to expand...
Click to collapse
I am also facing the same problem. is there any solution?
I am using Nexus 5 recently rooted and upgraded to lollipop 5.0.

No solutions to this problem? I have it too. Flashed a new recovery and rom, and now I can see all my files in TWRP, but when I boot up, sdcard shows no files, yet in storage I can see that there is space taken, and when I connect to a PC - no files are shown. Any help is appreciated.

A380 said:
I can see the contents of the internal sdcard when using the file browser in TRWP recovery, but after a boot-up the /system/sdcard is not accessible to the Android OS. I noticed the problem after I flashed system.img and boot.img in order to get rid of Apps Ops X.
Is there an easy was to restore access for the operating system and keep the data?
Nexus 5 / 4.4.2
Click to expand...
Click to collapse
Well check out this forum by Android Enthusiast osm0sis:
http://forum.xda-developers.com/showthread.php?t=2239421
And the zip which rectifies Android Internal /sdcard/ problems is here for download:
http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Hope It Helps! Be Sure To Thank Me... :fingers-crossed:

Related

ROM zip doesn't show up in recovery

I recently decided to explore custom ROMs. I installed ARHD for my one but recently decided to try out the GPe ROM. However after I downloaded the ROM and moved it to my phone, it wouldn't appear in CWM recovery. Is there any reason for it? I've copied it multiple times to multiple directories but it won't show up
Sent from my HTC One using xda premium
Try directory '0'
Sent from my HTC One using xda premium
I have the exact same issue? Rooted, twrp installed, the directories show up when I usb to my laptop but created Rom folder is non existent in recovery. Tried downloading Cleanrom straight from the device as well into the "downloads" directory. Downloads shows up in twrp but the Rom isn't there. But browsing "my files" on the device shows that it's there?
Reflash a 4.1.2 rom, copy all your stuff off the device to computer, delete all but rom zip on internal storage flash rom then copy back content
Keep it in the root of you memory. Should show up :thumbup:
Tried putting the .zip file in the root of the internal storage. To no avail. It is invisible. Nothing there at all. What gives?
I also have no such thing as a directory "0"?
Use a different SD?
TeeJay!! said:
Use a different SD?
Click to expand...
Click to collapse
a different SD? The one has internal storage only...am I missing something?
cadorette said:
a different SD? The one has internal storage only...am I missing something?
Click to expand...
Click to collapse
Opps sorry... my bad reflash your phone clean out everything and then try
TeeJay!! said:
Opps sorry... my bad reflash your phone clean out everything and then try
Click to expand...
Click to collapse
another post said that..im gonna re-flash my current rom (at&t stock rooted) and try again...kinda strange ive been flashing since the HTC HD2 through the Galaxy S4 and everything in between and have never seen this...I'll try a re-flash and check in tomorrow
TeeJay!! said:
Opps sorry... my bad reflash your phone clean out everything and then try
Click to expand...
Click to collapse
Sorry..been away from HTC for a while..as in reflash my current ROM?
Did that...went in, wiped EVERYTHING...re-flashed current ROM (just a stock rooted ATT deodex) and its the same thing...the current ROM I'm running shows in TWRP..
But any ROM I've transferred via PC into internal memory, or downloaded straight from the device, is completely non existent...
the "ROMs" folder I created on my PC to the external memory (where I store the ROMs for easy access) is not there either.
Should I search GooManager for an updated TWRP or something?
Update: Wiped again and reinstalled TWRP fresh. Still have exact same issue. everything shows on the phones memory when i connect to PC, but loading up TWRP recovery they are not there. In any directory i select. I'm lost. I want to ROM this thing like crazy but I can't lol!!
OK...fixed it!!!
After a lot of digging it seems when I connect to the PC and look at the storage I DO have a "0" directory (only through the PC though, not in recovery). I opened the "0" folder, moved my ROM to a directory in that via PC, and voila! Now the ROMs show up in wherever I saved them as long as I open the "0" area first through the PC..
Now I just navigate to wherever I saved them (anywhere after double clicking "0" when connected to PC) and the zips are there and present and I can flash. Not exactly sure why this is but it worked for me!
so...in a nutshell...
1. Connect your One to PC.
2. choose "open to view files" (or if youre on a mac like me, android file transfer)
3. find the "0" folder/directory and open it
4. copy the .zip file of your desired ROM there
5. reboot into recovery and it should be there.
6. flash and enjoy!
Keep in mind this is for TWRP based recovery. I am not sure about anyone using CWM that has this problem.
cadorette said:
Sorry..been away from HTC for a while..as in reflash my current ROM?
Did that...went in, wiped EVERYTHING...re-flashed current ROM (just a stock rooted ATT deodex) and its the same thing...the current ROM I'm running shows in TWRP..
But any ROM I've transferred via PC into internal memory, or downloaded straight from the device, is completely non existent...
the "ROMs" folder I created on my PC to the external memory (where I store the ROMs for easy access) is not there either.
Should I search GooManager for an updated TWRP or something?
Update: Wiped again and reinstalled TWRP fresh. Still have exact same issue. everything shows on the phones memory when i connect to PC, but loading up TWRP recovery they are not there. In any directory i select. I'm lost. I want to ROM this thing like crazy but I can't lol!!
Click to expand...
Click to collapse
I'm having the same issue. If you find a fix please PM me.

Wiped the already installed OS in Huawei Honor 7(PLK-UL00) and cannot reboot

I rooted my phone, and then i was trying to flash a Marshmallow Rom. For this, i wiped my system, boot, dalvik cache, internal memory. I forgot to take a nandroid backup. For some reasons, there was some error in flashing that zip file, so i tried to reboot my phone normally and it failed. When i reboot my phone, the company logo appears and it remain sticked there. For now, i could only access the recovery and fastboot. Please HELP me..... Thank you.....
You got exactly same problem with me but i have model: Honor7 Premium (PLK-L01)
Hi,
what did you expect? If you wipe de system partition then obviously the operating system is gone.
What you need to do is to download the full stock rom of your phone somewhere on the internet (needrom.com for instance if available).
You need to take the closest version of your old system and also the same technical name (PLK-UL00).
For instant if you were already on Android 6.0, you can no longer use a stock rom of Android 5.x.
When you have that full stock rom on your computer, you need to use multi-tools and use the unbrick option. Meaning you will be asked to extract the most important img files from the stock rom and to put them into a specified folder. The tool will then restore that rom on the partition file.
Kind reg,
I had android lollipop 5.0.2. Is it possible that i install the backup file of any other person's honor 7 PLK-UL00 running same android?
Hi,
please have a look there and use the stock rom that fits with your model and version.
https://yadi.sk/d/ZD8hXFjenRFHf
Kr,
how do i flash an UPDATE. APP file?
Create folder called dload on your SDCard and copy Update.app file to your SDCard inside that "dload" folder.
Then shutdown your device and use 3-Button method(Vol- & Vol+ & Power button) to boot that to recovery, that should start installing "recovery" file what is that Update.app inside dload folder.
Sent from my PLK-L01 using XDA-Developers mobile app
i don't know but the 3-button method is not working. When i do so, it boots to the recovery and nothing happens. Anyways, i have copied the dload folder with update.app file to the sdcard.
Use Multi-Tools available in the forum. There is a little app where you will be able to extract all required files from the file update.app.
Then in multi-tools use unbrick option and it will install the stock rom correctly. ++
http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Thank you!!!!! Sebastien_be and everyone to help me... It worked very well.. Thank u guys so much for the help...

Update Fota Lollipop 43 to MM 13.6.5.30 (WW)

I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos

Rollback to Android 5 and EMUI 3.1 (PLK-AL10)

Hi guys
The official OTA update (B380) with Andoid 6 and Emui 4.0.1 arrived on my PLK-AL10 around a week ago and I was very disappointed when I saw the "privacy protection" feature is not there anymore. This feature allowed me to create "visitor" account and the visitor could not see all the apps and albums.
Now I installed B395 hoping the feature included but it is still not.
I would like to revert to the previous system (as I remember it was B320) or any working version with Android 5 and EMUI 3.1.
I tried to install all the rollback files I found on the net but all stopped after a few percentages with the error message "software install failed".
Pls help me, what can I do?
You can root your device and add a couple of lines in /system/build.prop to get back the multiuser mode.
Sent from my PLK-L01 using Tapatalk
DigiGoon said:
You can root your device and add a couple of lines in /system/build.prop to get back the multiuser mode.
Sent from my PLK-L01 using Tapatalk
Click to expand...
Click to collapse
Really?
May I get a bit more detailed explanation what to modify?
tgergo said:
Really?
May I get a bit more detailed explanation what to modify?
Click to expand...
Click to collapse
http://forum.xda-developers.com/cro...ti-user-mode-guest-mode-simple-build-t3064829
This thread explains what you need to add to build.prop
Or do you need to know how to root your phone?
You can set how many users you want by editing max user line.
lionboy33 said:
http://forum.xda-developers.com/cro...ti-user-mode-guest-mode-simple-build-t3064829
This thread explains what you need to add to build.prop
Or do you need to know how to root your phone?
Click to expand...
Click to collapse
I can find in other topics how to root the phone, thank you. I think I can do it with these. Thanks a lot.
DigiGoon said:
You can set how many users you want by editing max user line.
Click to expand...
Click to collapse
Great.
I will come back if I get into trouble.
tgergo said:
Great.
I will come back if I get into trouble.
Click to expand...
Click to collapse
Always here to help buddy.
DigiGoon said:
Always here to help buddy.
Click to expand...
Click to collapse
Hi again,
Finally I managed to edit my build.prop and got "users" option. The problem is that is is not the same function as "Privacy protection" was in android 5. Privacy protection left the icon layout untouched, it was just possible to hide albums and applications.
Here when I create a guest and switch to it, it shows a completely empty system without any installed apps, pictures, etc..
Therefore I still want to go back to Android 5. How is it possible? I have TWRP installed. My current rom is B395 and phone is PLK-AL10.
To add to previous post, please unroot, flash stock boot.img and recovery.img BEFORE attempting to flash any ROM, including transitional package.
zinko_pt said:
To add to previous post, please unroot, flash stock boot.img and recovery.img BEFORE attempting to flash any ROM, including transitional package.
Click to expand...
Click to collapse
I don't think he was rooted, as the official update was missing a feature and he just wanted to get back to Lollipop.
Sent from my PLK-L01 using Tapatalk
pixelitect said:
You have to first flash the transition package to go back to Lollipop. For transition package to work you have to first flash STOCK recovery.img.
To do that execute the following command:
Code:
fastboot flash recovery recovery.img[/b]
Here [b]recovery.img[/b] is the name of your recovery file, and execute this command from the folder where you have saved the STOCK recovery.img. If you don't have STOCK recovery then you can extract it form the [b]UPDATE.APP[/b] using [URL="http://forum.xda-developers.com/showthread.php?t=2433454"]Huawei Update Extractor tool[/URL].[/QUOTE]
First I wanted to do so, but I could not find any transition package that worked with B380 stock rom (now I have 395). All I tried stopped with "software install failed" :(
Click to expand...
Click to collapse
pixelitect said:
Oh, then you can debrand your device using Multi-Tool to the one which has rollback package, and flash the Lollipop of that model.
Click to expand...
Click to collapse
Ok, I haven't heard about this yet but I'll try.
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
I managed to get back to Android 5 and EMUI 3.1 with a rollback file.
Here what I did:
1. Download Downgrade pack.
2. Download C185B130 ROM, which i want to install.
3. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
4. Copy update app from Downgrade pack to dload folder on mobile internal memory.
5. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
6. The system will be installed from mobile internal memory. I had no issues with the installation.
7. Copy update app from C185B130 ROM to dload folder on mobile internal memory.
8. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
9. The system will be installed from mobile internal memory. I had no issues with the installation.
10. Factory reset the mobile if the memory is showing 4gb.
11. The the native app icons look different than my previous lollipop system.
Thanks to tgergo and rest of everyone for the kind help.
Follow my guide at your own risk.
*WARNING* You are doing it at your own risk, I am not responsible for any damages due to bricked phones or broken ones

Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup

Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Can you tell me how you rooted the SM-T380 I tried rooting it using the 2018 guide but it's not working and I tried patching the Boot.img ( from Sammobile) with magisk but when i open the magisk app it says Installed: N\A Ramdisk: Yes A\B & Sars: no.
Or can you share the stock boot animation from the T830 since I'm not a big fan of the Marvel's avengers/iron man boot animation.
i just installed this and it works great, total life saver. i was about to toss my tablet in the trash
@xfk110, out of sheer desperation I want to try this. I understand why and how it should work, and I'm downloading your backup now. But a couple of questions first if I may:
1. Will Titanium Backup work with this rooted firmware? That's most important and my biggest frustration, after trying every other way described in the T380 threads, with both Oreo and Pie, TWRP or patched boot image. Nothing has worked well enough for me.
. . . My Tab A arrived with XAR 3CTH4 which meant I could downgrade it to the last Oreo update 3BSD1, and I've been back and forth between versions trying to make something work with TiBu. I'm a diehard Titanium user. I have tried 4-5 different root methods and every effort has failed somehow, if only that TiBu would not run. (Most efforts were even worse failures though.)
2. How important is the firmware version (and CSC) on my Tab A? . . . My T380 came with XAR firmware . . . Should I match the 3CSL2 version of your backup exactly, i.e., should I flash 3CSL2 first? Or if I'm on 3CSI5, would that be close enough? (I ask because I'm getting really really tired of changing firmware on this Tab lol, and I already have 3CSI5 downloaded and unpacked.)
3. You mention "all of those files" -- for a TWRP restore I would expect to select ONE FOLDER to restore from, so I'm a little confused about what you mean by "all of those files". Wouldn't it necessary to copy all of those files to one new folder under TWRP/BACKUPS/my-serial-number? Maybe named 2022-01-18, something short and simple.
I do truly truly hope this will work for me. Thanks in advance for however much you can help me understand everything I need to do to get a solid working root.
Just wanted to thank you for providing this guide. It worked first time for me and I'm very happy with the improved speed and space.
Thank you!
zfk110 said:
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Hello could you please make a video, the truth is that I do not understand anything.
Can this process be done using internal storage?
banistersmind said:
Can this process be done using internal storage?
Click to expand...
Click to collapse
No, unfortunately, this process can only be completed with a micro sd card and another computer with an sd card reader. the sd card must be at least 8gb to work.
Still works great as of 3rd May, 2023! Thanks mate.
@banistersmind @mehmeh.re I just did it without an SD card using internal storage. Works fine.

Categories

Resources