Database Info

Captivate (stock 2.2) stuck in kernel boot

Need help and I assume I am stuck in a ‘soft brick’ state.
My Captivate does not advance past a kernel flash screen.
Upon boot, I receive the AT&T logo boot animation, then black screen, then with 5 seconds receive the splash screen of the Kernel developer (“Trident”). The phone remains stuck on this screen.
I can, however, initiate download mode and recovery mode (signs of hope).
In download mode I cannot get the device recognized by the multiple PCs I used to access the device by (the USB drivers are on the PC…..as evidenced through its functionality before). Consequently, and SDK / adb and ODIN* is of no help to me as an option to recover the device.
In recovery mode, I can apply sd card zips and have a few available (had several updates, superuser, kernels, etc downloaded prior to this device bricking) to apply. Of the zips available are;
CWM Recovery v3.0.0.5
Voodoo Lagfix
recovery CWM 2.5.1.2
SuperOneClick 1.9.5
ROM Kitchen Froyo ROM
11-254 Trident (Kernel Manager – ytt3r7 )
Click to expand...
Click to collapse
Backup file on device was from the day that the kernel was installed
After applying any of these zips (except the ROM Kitchen file) I will get an abort with the
“E:no misc partition” message.
>>>>>>>>>>>>>>once ROM Kitchen setup is applied it says "successful" then reboot it does the exact same thing as before (sticks in kernel splash screen)
For what its worth, this occurs with no SIM card and no SD card in the device.
*I have successfully used Odin on this device (usb functioning, recognized the device in Odin) and flashed/reset the device prior to this kernel problem.
** the reason I am in this position was because after receiving a warranty replacement (in stock 2.2 Froyo) I received the signature verification error. No amount of sidestepping this worked (I’ve read every page of the guides for this issue and they did not work) so I figured the easiest way around it was simply to replace the kernel (it wasn’t the bootloaders giving me errors). The phone was rooted, had superuser permissions, just could not apply any ROMs because of the sig verification.
To get a kernel to load (ROM manager / recovery mode zips did not work), I figured I would use market apps for this. I downloaded “Kernel Manager” from the market and applied the only kernel available (“Trident”). Once it applied the kernel, it left me stuck in the current stat I’m in.
*** I have read all previous "stuck in boot" threads and none of them have ANY troubleshooting methods available.

Just for clarification before further troubleshooting, you are putting the phone in download mode unconnected from the computer, starting up Odin, then connecting, correct? The only reason I ask is that I had some trouble with the computer seeing my messed up phone when I connected it prior to opening Odin.

correct - though, I've tried it in every sequence....ODIN (PC itself) doesn't see any USB device.
If I could get ODIN to recognize the device, I could wipe the phone and start over.
I guess my question is two-fold.
FIRST - Is it a correct assumption that this device is recoverable (not complete brick)?
SECOND - is there any way to fix the kernel loop from recovery mode?

1. I would assume yes, as you have activity from the phone.
2. Possibly. Hopefully you backed up (or don't care about) your apps, because most solutions at this point have a good chance of losing them. Also, from recovery, the first thing I'd do is a nandroid backup.
If you haven't tried this already, see if you can get Odin to recognize your phone while it's at the boot loop.
Next step would be trying to flash a kernel like Onix. You can do this one from CWM, so there's a chance it could fix your phone.
If that doesn't work, you could to grab a custom rom with a full wipe package (Firefly, for example) and see if you can run that from CWM. As it contains a kernel as part of the package, there is a chance you would be able to get your phone functional again.
I can't guarantee any of these methods, but they might help.

so - likely recoverable IF ODIN can recognize the device
BECAUSE there would be no other way to put the other kernels on the device (if you can't get the OS to load {past the kernel loop}
IF ODIN can recognize the device;
1. wipe/clear the device
2. load a different kernel through ODIN.
or is there another to load a kernel without ODIN?

Actually, from CWM recovery you can flash kernels (like the Onix one). Use the method you used before to get back there (holding V+/V-/power, i'm guessing), and assuming you have a way to get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone.
To flash the kernel, from the recovery menu select the "install zip from sd card" option, then "choose zip from sd card", and then navigate to where you saved it.
Assuming all goes well, it will overwrite the Trident kernel, and since Onix claims to work with stock roms, you should be back up and running.

jmtheiss said:
get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone. .
Click to expand...
Click to collapse
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this

Ragin Caucasian said:
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this
Click to expand...
Click to collapse
No problem. We all have those forest-for-the-trees moments.
Just as a heads-up, the onix kernel will be an intermediate step to a more final solution. The reason I say this is that it's based on I9000 source, so you would either need to flash an I9000 modem, or flash back to stock (overwriting the onix kernel). Either way wouldn't be difficult, but just something to remember.

i thank you for the feedback/help. This should work, unfortunately, it doesn't.
When attempting to load zip from sd-ext I get
E:no misc partition
Click to expand...
Click to collapse
when mounting the "/sd-ext" from CWM, I get
"E:failed to mount /sd-ext (no such file or directory)
Error mountin /sd-ext!
Click to expand...
Click to collapse
even if I attempt to format the /sd-ext, I get
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmblk1p2
Error formatting /sd-ext!
Click to expand...
Click to collapse
So I'm stuck / dependent on ODIN (correct)?

Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?

jmtheiss said:
Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?
Click to expand...
Click to collapse
The sd/ext won't work unless you have an ext partition on your SD card.

Have you tried re installing your drivers?
If you can get to DL mode your comp. should recognize your phone.

I dunno.....
I've tried 2 different PCs (win7....32 and 64 bit environment) neither recognize the device. I keep getting the
E: no misc partition
Click to expand...
Click to collapse
anytime I doing anything with the sdcard (internal / external)
I've been using Odin3 (which is what I used to flash it originally)
Like I said, I can boot into Recovery Mode (get the internal menu) or boot into Download Mode (yellow sign 'downloading....do not turn off target!") but I don't think this really is doing anything because the PC never recognizes it and I can get into this mode whether I'm connected to a PC or not.
When I attempt to run Heimdall it runs and immediately crashes. This is what it displays
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heimdal Front end 1.1 used to work, but since the device isn't recognized, like ODIN nothing is presented to the application
I'm stumped. I just received this last Friday as a warranty replacement, I have 3 batteries and 2 usb cords, a rubber sleeve for the device willing to sell it all for $50 if anyone wants it.

Is the odin3 you're trying the one-click back to stock? Have you tried Heimdall? What version number shows up when you open it?
I used Odin3 v1.70 with my phone and had good luck. If you're using an earlier one, try using that one. If you're using v1.70, try an earlier version.
And to reiterate the earlier post, if you haven't tried uninstalling and reinstalling the drivers on your pc, that's worth a shot, too.

That dialog you're seeing with adb looks a lot like what happens if you run it without any arguments. Are you doing anything like "adb devices" or "adb reboot recovery"?

awesome!
Good news.....ODIN recognized the device
bad news......completely soft bricked the phone
I got the phone-<!>PC image and now the phone won't turn on again. great
I'll try the flux-capacitor jig fix sometime when I don't feel like strangling someone

Actually, you can use odin from the phone--!--pc screen. If you can get back there, try to flash the one click.

UPDATE
Bought the $10 jig (after my homemade resistor jig didn't work) - which works very well, btw.
* Uninstalled the USB drivers - reinstalled the USB drivers
* Used Odin3 1.8
* phone recognized by Odin.
* Flashed bootloader (what was originally wrong with the phone) and even a new ROM
Everything went FINE through Odin (first for me), even got a progress bar on my phone during the operation
now the phone is completely dead.
Will not give me the soft brick image.....can't go into download mode - nothing, completely unresponsive
$50....who wants it? This is a brand new phone just received as a warranty replacement....FOUR 1500m batteries, TWO USB cables, TV-OUT cable, and a rubber protective case

[Q] Noob needs help installing KatKiss ROM

Hi there!
I am a super noob in installing custom ROMs and desperately need some help!
I have an Asus Transformer tf101 (duh), I don't have the keyboard dock. I want to install the KKKK ROM, but I have no idea how to. I know I have to wipe, boot rom, flash kernel and reboot, but I really have no idea how to. I do not have an SD card (and I don't think my tablet can take one), but there is a folder on the tablet somewhere called sdcard. So... Can you help me? I have searched through the forums but I am not sure if descriptions for other devices go for mine as well...
Concluding: I have the TF101 without the keyboard dock. It runs stock android (updated as far as I could, just checked it: Android 4.0.3). And I want to run KatKiss' KitKat ROM.
Can you help this noob installing a ROM (and not bricking the device?)? It would be very much appreciated!
Michelle

Plug the tablet into the PC > USB
Turn off your tablet
Put the Tablet into APX Mode (Volume Up & Power button)
You won't see anything on the tablet screen, but the PC should recognise it, that is the only indication that you have successfully entered APX Mode
Install APX Drivers
http://forum.xda-developers.com/showthread.php?t=1514942
Run EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012
Depending on your tablet serial number you will need either SBK1 or SBK2 selection in EasyFlasher - easiest way to know if if your tablet serial starts with B4O > B6O it's SBK1, anything above that and it's SBK2 (Some B7Os are SBK1 but not many)
You need to select TWRP Recovery from EasyFlasher and flash that first
Once you have successfully flashed TWRP, you can flash any ROM you like from TWRP Recovery by booting into recovery
(Volume Down & Power until white text appears at the top of the screen, then release buttons and press volume up once)
Your TF101 does take Micro SD cards, it's a small slot on the lower right side of the tablet edge
Because you are coming from stock I would at this point suggest wiping everything from TWRP, but as you are not using a Micro SDCard, Im not 100% sure where you could store the ROM before wiping, so...
Copy the ROM & Gapps to your SDCard folder on your TF101 before wiping anything / before booting into recovery
Now boot into recovery and wipe only SYSTEM, CACHE & DALVIK CACHE
Now go to the INSTALL menu and find your KatKiss ROM & Gapps
Flash ROM then Gapps
Now back to the WIPE menu and wipe only CACHE & DALVIK CACHE
Now reboot
You should be booting into Kat Kiss now
My advice: Buy a MicroSD Card to make things much easier and have a way to recover your tablet if you accidentally wipe everything including your Custom ROM zip while you're inside recovery

Thanks so much!^^ I do have some questions still though.. (so afraid I'll brick the thing)
*Detection* said:
Install APX Drivers
http://forum.xda-developers.com/showthread.php?t=1514942
Click to expand...
Click to collapse
To install the APX drivers, I first wipe the drivers via device manager, and then install the new drivers via device manager? Which file should I click on? The zipped folder, the unzipped folder, or one of the files? (I use Windows 8.1, don't know if it matters).
*Detection* said:
Run EasyFlasher
http://forum.xda-developers.com/showthread.php?t=1688012
Click to expand...
Click to collapse
I do not need to follow the “instructions for unbricking/flashing ASUS stock firmware”, right?
*Detection* said:
Depending on your tablet serial number you will need either SBK1 or SBK2 selection in EasyFlasher - easiest way to know if if your tablet serial starts with B4O > B6O it's SBK1, anything above that and it's SBK2 (Some B7Os are SBK1 but not many)
Click to expand...
Click to collapse
Okay, so my serial number begins with BCO, so I need SBK2, right?
*Detection* said:
You need to select TWRP Recovery from EasyFlasher and flash that first
Once you have successfully flashed TWRP, you can flash any ROM you like from TWRP Recovery by booting into recovery
(Volume Down & Power until white text appears at the top of the screen, then release buttons and press volume up once)
Your TF101 does take Micro SD cards, it's a small slot on the lower right side of the tablet edge
Because you are coming from stock I would at this point suggest wiping everything from TWRP, but as you are not using a Micro SDCard, Im not 100% sure where you could store the ROM before wiping, so...
Copy the ROM & Gapps to your SDCard folder on your TF101 before wiping anything / before booting into recovery
Click to expand...
Click to collapse
Haha, that must have sounded so very dumb. I am so sorry. I use a cover for my tablet and there’s no opening for the SD in that cover, so never noticed it before, haha. Okay I have an Micro SDCard for it. So what exactly should I put on that SD? The KatKiss zips and the .zip.md5? Or the kernels? Or something else entirely? And what are/where can I find the Gapps? Are you talking about the ROM and Gapps already on the tablet or the new ones from KatKiss?
*Detection* said:
Now boot into recovery and wipe only SYSTEM, CACHE & DALVIK CACHE
Now go to the INSTALL menu and find your KatKiss ROM & Gapps
Flash ROM then Gapps
Now back to the WIPE menu and wipe only CACHE & DALVIK CACHE
Now reboot
You should be booting into Kat Kiss now
Click to expand...
Click to collapse
Okay, I think that will speak for itself when I arrive at that point.
Sorry for the million questions. Hope you can help me again! Thank you!!

MichelleChristiana92 said:
Thanks so much!^^ I do have some questions still though.. (so afraid I'll brick the thing)
To install the APX drivers, I first wipe the drivers via device manager, and then install the new drivers via device manager? Which file should I click on? The zipped folder, the unzipped folder, or one of the files? (I use Windows 8.1, don't know if it matters).
Click to expand...
Click to collapse
When you have the TF connected to the PC USB and enter APX mode, it should show up in Device Manager as ! unknown device or something similar, extract the zip of the Universal drivers and update the ! entry in device manager manually by pointing it to the drivers you extracted earlier - it should install the correct driver for you
MichelleChristiana92 said:
I do not need to follow the “instructions for unbricking/flashing ASUS stock firmware”, right?
Click to expand...
Click to collapse
No, just choose SBK2 and Flash TWRP recovery
Here is EasyFlasher with the latest version of TWRP recovery 2.3.2.3 included, it will save you having to update your TWRP later
http://www.putlocker.com/file/9A166042D0E31CE6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MichelleChristiana92 said:
Okay, so my serial number begins with BCO, so I need SBK2, right?
Click to expand...
Click to collapse
Yes, SBK2
MichelleChristiana92 said:
Haha, that must have sounded so very dumb. I am so sorry. I use a cover for my tablet and there’s no opening for the SD in that cover, so never noticed it before, haha. Okay I have an Micro SDCard for it. So what exactly should I put on that SD? The KatKiss zips and the .zip.md5? Or the kernels? Or something else entirely? And what are/where can I find the Gapps? Are you talking about the ROM and Gapps already on the tablet or the new ones from KatKiss?
Click to expand...
Click to collapse
Great, yes now you can copy the ROM & Gapps zip files to the Micro SD Card, and once you are inside of TWRP recovery you can now wipe SYSTEM, CACHE, DALVIK CACHE, DATA, INTERNAL STORAGE etc etc (Everything apart from External Storage which is your MicroSD Card) if you do not want to keep anything at all on the TF101 and just start a fresh with KatKiss
MichelleChristiana92 said:
Okay, I think that will speak for itself when I arrive at that point.
Sorry for the million questions. Hope you can help me again! Thank you!!
Click to expand...
Click to collapse

Hi,
I tried what you say and the ROM flashing failed with this error
Code:
-- Install /sdcard/KatKiss-4.4.2_2018.zip
Findind update package
Installing update
set_perm : some change failed
E:Error in /sdcard/KatKiss-4.4.2_2018.zip
(Status 7)
Could you tell me what this error means ?

Dalc said:
Hi,
I tried what you say and the ROM flashing failed with this error
Code:
-- Install /sdcard/KatKiss-4.4.2_2018.zip
Findind update package
Installing update
set_perm : some change failed
E:Error in /sdcard/KatKiss-4.4.2_2018.zip
(Status 7)
Could you tell me what this error means ?
Click to expand...
Click to collapse
Don't know where you got that ROM from, but it's not named the same as the actual ROM from the main page
This is the ROM you want
http://downloads.timduru.org/android/tf101/K.A.T/KatKiss/4.4/dev/KatKiss-4.4.2_018.zip
See how yours is called KatKiss-4.4.2_2018.zip
Actual ROM doesn't have that 2
KatKiss-4.4.2_018.zip

Another Guide for you
Hi
Frederuco also did quite a good guide HERE
It might help you too.

Okay, thanks. So I'm doing this, but can't seem to boot into TWRP... APX, EasyFlash all went great, but when I try to boot into TWRP (Vol Down+Power and when text comes vol up) it just boots into my tablet (you know, asus, android, but no TWRP).
Am I doing something wrong? Or should I press earlier or later on the vol up?

Detection: My bad that was a typo, i actually have downloaded the good version but it seems that the md5 is not correct.
I already wipe the system and havent a microSD card yet. So i can't change the file on the /sdcard. But i have a SD that the dock can read.And also 2 USB. But it is possible to use them in TWRP ? With a mount command or something ? Otherwise i will buy a microSD...
MichelleChristiana92: When the text come up, you have only 5s to press VOL_UP

MichelleChristiana92 said:
Okay, thanks. So I'm doing this, but can't seem to boot into TWRP... APX, EasyFlash all went great, but when I try to boot into TWRP (Vol Down+Power and when text comes vol up) it just boots into my tablet (you know, asus, android, but no TWRP).
Am I doing something wrong? Or should I press earlier or later on the vol up?
Click to expand...
Click to collapse
You have 5 seconds from the time the white text appears to press Vol Up or it will just boot to the ROM
---------- Post added at 06:04 PM ---------- Previous post was at 05:47 PM ----------
Dalc said:
Detection: My bad that was a typo, i actually have downloaded the good version but it seems that the md5 is not correct.
I already wipe the system and havent a microSD card yet. So i can't change the file on the /sdcard. But i have a SD that the dock can read.And also 2 USB. But it is possible to use them in TWRP ? With a mount command or something ? Otherwise i will buy a microSD...
Click to expand...
Click to collapse
You could use ADB in TWRP and push the new ROM to the TF via ADB commands
Put ROM in same folder as adb command is being run from on the PC
So if ROM is on C:\ROM, make sure Command Prompt is like this:
C:\ROM> adb push nameofROM.zip /sdcard/
Hit Enter
That should copy the ROM to the TF internal sdcard

Thank you for help.
But actually adb does not found my device :/
Is there something to configure ?

Dalc said:
Thank you for help.
But actually adb does not found my device :/
Is there something to configure ?
Click to expand...
Click to collapse
Check Device manager and install these drivers
http://forum.xda-developers.com/showthread.php?t=1514942
Or use Ubuntu, once you install the adb tools you should have no problems connecting to the TF using ADB - I use VMWare Ubuntu install for that

Hmm.. I press the vol up as fast as I can, but every time when I press it it goes to that second text screen with "OS will cold boot to stock linux, you have ten seconds to press vol up or vol down for..." or something like that.. I don't even think I have 5 seconds. When I press it it immediately goes to that second text screen, and then just boots.
Will try again tomorrow, if you know anything please let me know (but its probably just me though

MichelleChristiana92 said:
Hmm.. I press the vol up as fast as I can, but every time when I press it it goes to that second text screen with "OS will cold boot to stock linux, you have ten seconds to press vol up or vol down for..." or something like that.. I don't even think I have 5 seconds. When I press it it immediately goes to that second text screen, and then just boots.
Will try again tomorrow, if you know anything please let me know (but its probably just me though
Click to expand...
Click to collapse
Try using EasyFlasher to Root your TF, and then install this App, it will let you press it to reboot into recovery
https://play.google.com/store/apps/details?id=com.transformer.recovery&hl=en
It sounds like the TWRP install didn't work though, but could be wrong
Also, if you manage to root it, you could flash TWRP using GooManager
https://play.google.com/store/apps/details?id=com.s0up.goomanager&hl=en
GooManager > 3 dots menu button top right > "Install OpenRecoveryScript"
But you need to be rooted for either of those options to work

As you can see in the attachment below, i already have APX Driver installed.
But abd devices does not recognize my device when i boot my tablet in the APX mod.
When i boot in TWRP, the device appear as USB MTP device but adb still not find it...

Dalc said:
As you can see in the attachment below, i already have APX Driver installed.
But abd devices does not recognize my device when i boot my tablet in the APX mod.
When i boot in TWRP, the device appear as USB MTP device but adb still not find it...
Click to expand...
Click to collapse
Yea Windows & APX don't play nice together from my experience
Install Ubuntu somewhere and use that instead, I use VMWare, I guess VMPlayer will work too if it can see USB devices, and it's free
https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0
Or boot your PC on a Live Ubuntu DVD / Flashdrive and do it from that

Thank you! I am on KitKat now!
I downloaded and installed EasyFlasher again, from a few diffrent sources, and one of them worked and I rebooted into TWRP! Everything went smooth after that and am on KitKat now!
Thanks so much!
Cheers,
Michelle

MichelleChristiana92 said:
Thank you! I am on KitKat now!
I downloaded and installed EasyFlasher again, from a few diffrent sources, and one of them worked and I rebooted into TWRP! Everything went smooth after that and am on KitKat now!
Thanks so much!
Cheers,
Michelle
Click to expand...
Click to collapse
Great!
Remember to update your TWRP to 2.3.2.3 using Goo Manager from Google Play if it is an older version you managed to flash in the end
https://play.google.com/store/apps/d...omanager&hl=en
Open GooManager > 3 dots menu button top right > "Install OpenRecoveryScript"

Hi,
Finally i used a microSD card and its works.
Thank you Detection for your help !
Its really really smooth, pretty impressive for a TF101

:good: Pleased you got it working in the end
Yea KatKiss is very smooth indeed, brings new life to our old tablets

Ran "Fix Permissions" in TWRP - Everything is missing

I can see my SDcard in Recovery and I can copy stuff off via MTP from recovery...
But after I ran Fix Permissions I rebooted. The system hung on the boot animation so I force power off.
I figured the permissions got screwed up for some reason so I decided to just reflash the system.img from fastboot.
So, I did that and rebooted.
On boot it didn't hang but it acted like I was setting up a brand new phone. I finally got to the desktop and while all my apps are installed still, everything is missing. I can't see anything on the sdcard and stuff seems generally screwed up. If I go in to the settings and look at storage it still showes I have 20-something gb's used up.
Ugh... I don't know what to do... sort of panic'ing right now.
Anyone got any ideas?
edit: something is royally hosed up. Even if I boot up in and go to es file explorer and try and create a new folder on my new "blank" sdcard space it gives a failed to create folder error. I think the fix permissions option royally screwed things up. Not sure if there is any coming back from this one

Read the /sdcard sticky in general

Thanks rootSU.
Yeah, something is definitely funky between current recoveries and Lollipop.
What I found out last night:
-I cut my losses and decided to hard wipe everything. I was able to DOWNLOAD files off my phone from TWRP 2.8.1.0
-I wiped, reflashed, got the half storage issue, flashed stock recovery, factory reset, all better
-Booted Lollipop, signed in, it autoinstalled my ~130 apps (this took a long time)
-I still had all my "sdcard" files I'd downloaded. My phone wasn't recognizing in windows mtp while booted in Lollipop so I decided to copy files BACK over in TWRP
-Copied over my 16gb worth of files in TWRP (this took a very long time). Once copied over it looked good in recovery and windows mtp
-Rebooted back in to Lollipop
-All of the files I had copied over in Recovery to my phone were unreadable. Folders were showing up as "?" icons in ES File Explorer. So, all that time I'd spent copying files over from recovery was ****.
-Went back to recovery, could see files again in TWRP. Since Lollipop couldn't read them, I decided I had to just delete them from recovery and just copy them over WIFI
-Deleted in recovery, booted back to Lollipop, copied over via wifi (took >2 hours to copy over wifi)
So... in summary, TWRP + Lollipop are definitely NOT playing nice together.
It was DEFINITELY the "Fix Permission" function that totally screwed me.
And the kicker...
I was running it because on every boot I'd see the "Android is Upgrading" message flash up for a couple seconds. I googled it and someone had recommended the fix permission function.
And it's still doing it now. I now believe it is caused by the current root method from chainfire and will have to live with it until it is fixed I guess.
Sigh.... what an incredibly long night.

And just discovered that the current TWRP folder on my phone is in this messed up state.
TWRP created this folder and it can only be viewed in recovery.
Even a root shell can't get in to it from ADB in Lollipop:
Code:
[email protected]:/sdcard # cd TWRP
cd TWRP
tmp-mksh: cd: /sdcard/TWRP: Permission denied
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.

I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app

Redux90 said:
Yeah, I also have problems. Due to habit, I used "Fix Permissions" in TWRP - caused bootloop. Luckily i had just made a TWRP Backup, so I wiped the phone and restore it - worked fine again.
Guess I have to stay away from the feature until a fix.
Click to expand...
Click to collapse
Yup, something is broken. I found out the hard way
myliferockkss said:
I rooted my n5 lollipop.... But some rooted apps fail to get root access...like es file manager (root exp)...xmodgames...etc
In es it says failed test...and xmod shows device is not rooted
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.

GldRush98 said:
Yup, something is broken. I found out the hard way
This is completely unrelated to the topic of this thread. It's a known issue. Apps need to update how they're calling su.
Click to expand...
Click to collapse
Okay sorry boss *noob here*
Sent from my Nexus 5 using XDA Free mobile app

I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input

manny.m said:
I too am in the same boat, I was able to restore to a previous backup but there are issues with some apps and my storage is messed up.
GldRush98 - I was a bit confused by your post, may you please clarify
I am thinking of copying my files over to me desktop via MTP in windows. Wiping and re-flashing. Then, I plan on copying over the files - Is this what gave you issues? or was it just the TWRP folder.
or would this idea work: Wipe, re-flash then restore a backup (before i fixed permissions)?
Thank you for your input
Click to expand...
Click to collapse
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post

Thank you for the quick response! I have been away from these forums for a while now and I'm not able to located the said sticky under General. One more question, besides abd or TWRP MTP what other options would I have?
Thanks again!!

rootSU said:
If you copy files back in android it should be fine. Don't use adb or TWRP MTP. See my first post
Click to expand...
Click to collapse
Yup, this is correct.

In my haste I totally misread rootSU's post. I got all my stuff out with Windows MTP, flashed the factory images and now I'm good!
Thanks again!

Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?

mcgyver83 said:
Same issue on nexus4.
I wasn't able to create a file/folder on the phone.
Tried fix permission and bootloop happened.
I don't want to re-wipe everything, maybe a only rom flash from twrp will help me?
Click to expand...
Click to collapse
You can try the restorecon command from a terminal if you can get back in to Android.
Code:
su
restorecon -FR /data/media/0
reboot
I've seen others post that it is a potential fix.

Thank you man,I flashaed again the stock rom with data wipe.
I lost all my files but now all is working.
Many thanks

Hi guys, I have the same problem. Is there a solution to fix it, with full wipe? I can use just Odin because I can't get anywhere in the phone. I'm now trying stock room so hopefully it will work. If someone know the correct way to get working phone again let me know.
Thanks

Hello Everyone,
I fell victim to this issue and am a total noob when it comes to this. I was actually trying to remove the root and flash back to the stock software and accidentally ran the fix permissions expecting it to fix an issue that was arising. I have a ROM to restore but TWRP wont pick it up and I cannot seem to locate the proper directory folder. I already backed up all my data previously to starting and am ok with wiping everything but pretty much at this point I am at a loss.
If someone could help me out my email is [email protected]

I know it too late for you, but that is one feature I stay well away from. Never use it if you are reading this. Took me days to sort my phone out.

[Rom][Rooted_ALL_Carriers_Nougat_S8+BRB1_SafeStrap][SamFail][V5 Bootloaders]

My method is a little different than the actual SamFAIL method so please to tell me it says this in their thread. I feel my procedure is the best method for the S8+ and this method may not work on the other models so please follow there own set of directions. This method allows you to obtain root by simply flashing a modified system.img using only odin. These images include all carrier files and will work on all carriers. These roms should be stable and you can probably just use these as your daily rom. ​
What Is Safestrap
Safestrap is a Bootstrap / Recovery for locked bootloader phones. Safestrap is now based on TWRP Recovery (a touch based recovery) and you can perform .zip installs, backups and restores here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads V5 Bootloaders SamFail Method For Installation Using Odin
G955USQS5BRB1_ODIN_SAMFAIL_V5_Bootloader.7z Samsung Rom
G955USQS5BRB1_GOOGLE_ODIN_SAMFAIL_V5_Bootloader.7z Googgle Apps Rom
Directions Samfail Method Or If Coming From Stock Unrooted/Rooted Phone
This may wipe your phone
Unzip An Use Files From G955USQS5BRB1_ODIN_SAMFAIL_V5_Bootloader.7z Or G955USQS5BRB1_GOOGLE_ODIN_SAMFAIL_V5_Bootloader.7z
Reboot phone to download mode
Use the Odin3_v3.13 provide above or in above zips
1. In odin select BL_V5_PART_1_AND_3.tar.md5 and load in BL slot of odin do not change the options make sure Auto Reboot and F.Reset Time are checked Click Start
2. Phone will automatically reboot as soon as phone powers off hold buttons to reboot back to download
3. In odin make sure to click reset button then in AP slot in odin choose AP_SYSTEM_IMAGE_PART_2.tar.md5 make sure Auto Reboot and F.Reset Time are checked Click Start
4. When don flashing it will say fail in odin and phone will reboot. Reboot phone to download. If phone reboots to upload mode force it to reboot too download mode
5. In odin make sure to click reset button then in BL slot in odin choose BL_V5_PART_1_AND_3.tar.md5 make sure Auto Reboot and F.Reset Time are checked Click Start
6. When done flashing phone will reboot. If phone gets stuck on boot animation for more than 10 minutes force reboot to recovery and wipe cache if this dont work then you will have to wipe data
Downloads V5 Bootloaders Safestrap Method For Installation Using System Image Via Safestrap
G955USQS5BRB1_SAMSUNG_SAFESTRAP_SYS_IMAGE.7z Samsung Rom
G955USQS5BRB1_GOOGLE_SAFESTRAP_SYS_IMAGE.7z Google Apps Rom
Directions Safestrap Method Or If Coming From Rom That Already Has Safestrap Installed
This may wipe your phone
Unzip An Use Files From G955USQS5BRB1_GOOGLE_SAFESTRAP_SYS_IMAGE.7z Or G955USQS5BRB1_SAMSUNG_SAFESTRAP_SYS_IMAGE.7z
Copy System.img To Phone
Reboot Phone To Safestrap
1. In Safestrap choose install select install image and select System.img you copied to phone and flash to system
2. When finished reboot phone to bootloader
3. In BL slot in odin flash BL_V5_PART_1_AND_3.tar.md5
Older Downloads Version 2 Bootloaders
G955USQS2BQL1_ROOTED_ODEX_ODIN_FIRMWARE.zip
Odin3_v3.13.zip
Features
Pre Rooted With Latest SuperSu
SafeStrap Preinstalled
Patched Flashfire No More Having Too Set The Date Back
Xposed Framework Install
Wifi Passwords And Bluetooth Pairings Fixed
Wifi Hotspot Tethering Enable
Work on V5 Bootloaders
This thread is simply to get you rooted with a working rom.
This thread is not a rom request or features request.
If you dont like the rom that this method installs then install whatever you want.
Yes the 80 percent battery bug is still present in this method.
The screen gets a funny tint every once in awhile simple turn screen off and back on. This is not roms fault it is Eng Combo Firmware.
Sometimes FlashFire fails to achieve root or gets stuck acquiring root. A reboot usually fixes it sometimes it takes a couple reboots.
Kernel panics happen and will cause your phone to reboot to upload mode. If this happens simple hold the keys to reboot to download mode then from there reboot phone.
This is system root so safetynet apps will not work nor will samsung apps like Pay, Secure Folder, Pass. There is no work around
All Credit Goes To The SamFAIL Team their original thread can be found here
Any donations should directed to them​First and foremost, SHOUTOUTS!
- @partcyborg for finding the root method!
- @me2151 for testing on Note 8 and facilitating root on the Note 8!
- @elliwigy for being great help and original S8 root
- @Bsober for... Always testing my stuff
- @LiquidT for testing
- @Chainfire For opening the door to make this root useful. He will be missed! (no he is not dead, just retired.)
- @samsung for the amazing phone and leaving rediculous loopholes open for us to root!
Click to expand...
Click to collapse

How To Get SnapChat Working​Disable Xposed by toggling off in the Xposed installer reboot
Click on SuperSu app and goto settings and Uncheck Enable superuser
Now Install SnapChat and login
Now open SuperSu app it will say something su binary occupied just click on settings click on Check Enable superuser
Now it will say it was unsuccessful to reboot just ignore click on settings go to cleanup and click Reinstall
Now copy View attachment Superuser.apk to your phone install
Open Supersu app let it updated SU Binary choose normal
If All this fails or you want to skip these steps then just download latested SuperSU Systemode zip and install in safestrap
Create your own system.img.ext4 odin flashable image​
If you want to make a odin flashable system.img of your phones system image
Download
S8_Backup_System_Image.zip
MD5_TAR_TOOL.zip
FSTRIM Apk
Directions
Copy S8_Backup_System_Image.zip to phone
Unzip MD5_TAR_TOOL.zip on your computer
Install FSTRIM Apk on your phone
Run Fstrim and select system to trim
Once system trimmed use flashfire choose add zip and choose S8_Backup_System_Image.zip DO NOT MOUNT system when it ask
Click flash
This will take several minutes when phone reboots you should have a folder on your internal storage named System_Img_Backup and inside should be a system.img.ext4 file around 4.59 gig
Copy the system.img.ext4 file and place it in the MD5_TAR_TOOL. folder on your computer and place it in the Place_Files_Here folder
Run the ImgToTar.MD5.bat inside the MD5_TAR_TOOL. folder on your computer
This process will take 10 to 20 minutes to complete
Once done there will be a folder in the MD5_TAR_TOOL. folder on your computer called AP_SYSTEM_IMG_PART_1 and inside that folder will be a AP_SYSTEM_IMG_PART_1.tar.md5 which will contain your system.img from your phone
Just replace the Above AP..._PART_1 file with your newly created AP_SYSTEM_IMG_PART_1.tar.md5 and follow procedure in port 1 and now you can flash your system.img in odin its good if you bootloop your phone with a mod or something

I will try this tonight thanks for the guide
Update: I Just Tried It with the provided odex FW, Its Working For me On
S8+ Att Varriant

Mark805 said:
I will try this tonight thanks for the guide
Update: I Just Tried It with the provided odex FW, Its Working For me On
S8+ Att Varriant
Click to expand...
Click to collapse
I have confirmation from of course Verizon T-Mobile and Now AT&T. Just need someone from Sprint to try it. Does your volte, wifcalling , etc work ok on AT&T?

im allredy rooted can i flash with flashfire and can you make a full stock google rom flashable with flash fire im willing to test

robert ballard said:
im allredy rooted can i flash with flashfire and can you make a full stock google rom flashable with flash fire im willing to test
Click to expand...
Click to collapse
Since you didnt read the OP I will help you out on your request by posting what the OP says
jrkruse said:
This thread is simply to get you rooted with a working rom.
This thread is not a rom request or features request.
If you dont like the rom that this method installs then install whatever you want.
Yes the 80 percent battery bug is still present in this method.
The screen gets a funny tint every once in awhile simple turn screen off and back on. This is not roms fault it is Eng Combo Firmware.
Sometimes FlashFire fails to achieve root or gets stuck acquiring root. A reboot usually fixes it sometimes it takes a couple reboots.
Kernel panics happen and will cause your phone to reboot to upload mode. If this happens simple hold the keys to reboot to download mode then from there reboot phone.
This is system root so safetynet apps will not work nor will samsung apps like Pay, Secure Folder, Pass. There is no work around
Click to expand...
Click to collapse
check out my other threads I have what your asking for

Hey i have this fw with baseband l6
service provider used to say Xax/att/att but i got a security warning
from the device maintenance security window i clicked resolve now and it reset my phone it went to recovery for a brief moment I thought I was going to get a boot loop but it started up and my service provider is att/att/att now nd it booted with all the att bloat also i had knox dissabled thru the build prop but now it says 2.8. Did i get a ota or what happened?
Originally my phone is s8+ att unlocked

Mark805 said:
Hey i have this fw with baseband l6 modem used to say
Xxa/att/att but i got a security warning from the device maintenance security window i clicked resolve now and it reset my phone it went to recovery for a brief moment I thought I was going to get a boot loop but it started up and my modem is att/att/att and it booted with all the bloat
And knox says 2.8
Did i get a ota or what happened
Originally my phone is s8+ att unlocked
Click to expand...
Click to collapse
Wouldn't you want it that way. WiFi calling and all that volte won't work if your phone is XAA. Your rooted delete your bloat

jrkruse said:
Wouldn't you want it that way. WiFi calling and all that volte won't work if your phone is XAA. Your rooted delete your bloat
Click to expand...
Click to collapse
Yeah just found it to be wierd i went into the tri dump menu and im able to disable low battery dump i dont think i was able to in the other firmware

I just wanted confirmation that it's nothing wierd happening before I re flash my phone

Mark805 said:
I just wanted confirmation that it's nothing wierd happening before I re flash my phone
Click to expand...
Click to collapse
I have not heard of this happening later on your csc code is usually set on install. You can always change your csc back if you want

I tried this root method again, still SD issues

Hell-Razor said:
I tried this root method again, still SD issues
Click to expand...
Click to collapse
Your not trying to use encrypted storage are you? Other than that dont know what to tell you I have no problems with my 128 gig sd card

So i been running same fw no issues after the csc reset maybe I triggered it by going thru settings disabling apps

jrkruse said:
Your not trying to use encrypted storage are you? Other than that dont know what to tell you I have no problems with my 128 gig sd card
Click to expand...
Click to collapse
No. No encryption. I just wanted to state I'm not saying I don't appreciate your rom still please don't take it that way.
If your 128 works, can you link me which one you're using? I'll snag it off Amazon quick

Hell-Razor said:
No. No encryption. I just wanted to state I'm not saying I don't appreciate your rom still please don't take it that way.
If your 128 works, can you link me which one you're using? I'll snag it off Amazon quick
Click to expand...
Click to collapse
So what does it do? Reboot to upload mode when you insert It? Or just not read it?

jrkruse said:
So what does it do? Reboot to upload mode when you insert It? Or just not read it?
Click to expand...
Click to collapse
The phone will randomly read it. Like I can play a song for a minute or 30 seconds then it stops and I get the symbol at the top that says an SD card was inserted. The same when I'm trying to pull stuff off of or put stuff on... It will work for a little bit then unmount itself and remount. I saw that Google play may have something to do with it (other forums) but I've been trying to run traces on it to see and so far I don't see any error messages.

Hell-Razor said:
The phone will randomly read it. Like I can play a song for a minute or 30 seconds then it stops and I get the symbol at the top that says an SD card was inserted. The same when I'm trying to pull stuff off of or put stuff on... It will work for a little bit then unmount itself and remount. I saw that Google play may have something to do with it (other forums) but I've been trying to run traces on it to see and so far I don't see any error messages.
Click to expand...
Click to collapse
Have you tried reformatting it?

jrkruse said:
Have you tried reformatting it?
Click to expand...
Click to collapse
Yes. And checking it for errors and formatting it on other phones and formatting it on my computer. Everything else except this phone seems to accept it.

Hell-Razor said:
Yes. And checking it for errors and formatting it on other phones and formatting it on my computer. Everything else except this phone seems to accept it.
Click to expand...
Click to collapse
Try flashing some different combo firmware I have some listed in my rom thread

Development [RECOVERY][UNOFFICIAL][EXPERIMENTAL][ALPHA] TWRP for Galaxy A22 5G SM-A226B

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It took me sometime, but I can now share with you a TWRP with basic functionality. You of course flash at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device.
This Build of TWRP is based on:​
Firmware: A226BXXU4AVB1(Android 11) and A226BXXU4BVF7(Android 12)
TWRP-11 minimal manifest or TWRP-12.1 minimal manifest
Device Tree
Kernel source
Working:​
flash of zips
fastbootd
flashing of GSI images (via fastbootd)
MTP
Not working:​
Probably a lot of stuff ...
What you need:​
Unlocked bootloader.
Odin3 v3.13.1
android platform-tools and device driver.
adb and fastboot
Magisk or GSI depending on what you want to do.
Patience, the device can be very tricky to get to download mode.
How to flash:​Be advised that this build is a work in progress and is not ready as a daily driver. Only flash if you know what you are doing.
Spoiler
First read all points below, without doing anything. Warning, you will lose all your data!
If you are on Android 11 firmware download v1.01.2-alpha if you are on Android 12 firmware download the recovery.tar from here.
You start off in Odin, put recovery.tar in AP slot and the vbmeta_disabled_R.tar in the USERDATA slot, uncheck auto-reboot.
After the flash is completed hold down power + volume down, instantly after device goes Black screen press and hold power + vol up to boot to TWRP
if you didn't get to TWRP, you have to flash again.
In TWRP, go to Advanced → terminal.
Type multidisabler two times.
Now go to Wipe → Format Data (not wipe) → and type yes.
You can boot to system now.
Hot to install Magisk:​
Spoiler
Method 1, Micro-SDCard​
Download Magisk from here, rename the file from .apk to .zip
Save the file to a Mico-SDCard
Reboot the phone to TWRP.
Go to Install → Select Storage → Micro-SDCard. In the file system, choose Magisk-vXX.X.zip and swipe to confirm flash.
You can now Reboot to System
Method 2, sideload​
Download Magisk onto your PC from here, rename the file from .apk to .zip.
Reboot the Phone into TWRP. Go to Advanced → ADB Sideload → Swipe to start Sideload.
On your PC, type in a Terminal adb sideload Magisk-v24.3.zip
You can now Reboot to System. adb reboot system
How to install GSI:​
Spoiler
Go to Wipe → Format Data (not wipe) → and type yes.
Now reboot to fastboot.
Connect the phone to your pc and startup a terminal of your choice.
In the terminal type fastboot flash system name-of-your-gsi-iamge.img (it has to be a .img file, extract .img.xz files do not just rename them).
You should now be good to go and can reboot to system.
Thanks and credits to:
cheese-ass
akhil99
TeamWin

How to get TWRP log files:​recovery.log
adb pull /tmp/recovery.log
OR
Advanced -> Copy Log -> Swipe to copy log to default storage
dmesg
adb shell dmesg > dmesg.log
OR
Advanced -> Copy Log -> check "Include kernel log" -> Swipe to copy log to default storage
logcat
adb logcat -d > logcat.txt
OR
Advanced -> Copy Log -> check "Include Logcat" -> Swipe to copy log to default storage

Changelog​v2.00.1-alpha​
bump firmware and touchscreen drivers to A226BXXU4BVF7 and TWRP to TWRP-12.1
v1.02.2-alpha​
added drivers for himax touch screens.
v1.02.1-alpha​
added drivers for novatek touch screens.
v1.01.2-alpha​
added patch with improved multidisabler
v1.01.1-alpha​
update multidisabler
v1.01.0-alpha​
fix permission for mkbootimg
v1.00.0-alpha​
Initial Release

This has been tested, right? If it does work, I'll probably try it out when I have free time, which might be in a few days.

Yes, it runs on my A22 5G.

Could-Chaplain said:
Yes, it runs on my A22 5G.
Click to expand...
Click to collapse
It worked. But I didn't read your post carefully and now I have to format data :/
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.

Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Click to expand...
Click to collapse
It's the same for me, but no issues so far.
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Click to expand...
Click to collapse
That will be because you didn't format data. If I find sometime, I will try to reproduce that. Thank you, for testing.
Edit: Backups should work fine if you uncheck data?

Is the A226BZH3AUL1 suitable？

a0963655966 said:
Is the A226BZH3AUL1 suitable？
Click to expand...
Click to collapse
If your device is a SM-A226B you should be fine. But as always, flash at your own risk.

Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?

Thank you! Going to test asap.

lebigmac said:
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Click to expand...
Click to collapse
/data is most likely not mountable because you didn't run multidisabler twice and formatted data? ADB shell works fine for me, check in device manager that it shows up as ADB Interface.

Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?

koosman911 said:
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
Click to expand...
Click to collapse
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.

Could-Chaplain said:
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Click to expand...
Click to collapse
Are you using pixel experience on your device currently?

koosman911 said:
Are you using pixel experience on your device currently?
Click to expand...
Click to collapse
Yes and no, currently I am working on TWRP and there for flash the stock Rom quite frequently. But I do plan to use Pixel Experience. The only thing that does not work is NFC. But that seems to be the case with all the GSI I could find, as they are all based on phh.

Hey Guys, I did some work on the TWRP recovery. It's now more reliable, I highly recommend the update. You will find the download link and updated instructions at the top.

Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.

koosman911 said:
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
Click to expand...
Click to collapse
Thank you. What other phones despite the A22 5G are you using the recovery with?
Edit: Ahhh, you mean, you have nothing to test NFC with?

The model of a22 5G available in my country does not have nfc.