Database Users

Help Needed: Recovery Issue SM-t230nu

The first issue I started to notice after rooting via Odin & TWRP was when trying to flash the iOS and WP ROMs from this thread, http://forum.xda-developers.com/android/software/3oss-project-samsung-galaxy-tab-4-7inch-t3081478 , it would fail. I was able to successfully flash the Google ROM from same post. I believe it was with one of the other ones that it even said successful yet when i went to reboot said no OS installed. So, I figured update my TWRP to newest version, maybe that was the problem. Well after updating, now when i go to wipe/factory reset it either says unable to mount or it doesnt even make it that far and reboots system. I tried flashing PIT file with Odin and issue persists. Everything still works smoothly but any help fixing this issue would be much appreciated as I do not want to dirty flash anything. Thanks in advance.

So now...after flashing stock firmware, it boots all the way to nook screen (right after samsung logo) and stops. I can boot into TWRP but it still says unable to mount data. Also, in TWRP when i click mount, the only one already checked is cache. I can manually select all others except data. When i go to install, the internal sd has absolutely nothing on it...really hope i didn's completely mess it up, sometimes my eagerness to learn gets the better of me. Thanks again for any help!

I have the same issue, im stuck

How can I revert to factory state in my Leeco Le s3 (x522 US variant)

Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!

Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!

Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?

Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?

system keeps flashing stock recovery?

My phone was rooted for the longest time without any problems, but some time ago (I'm assuming after the Treble update) apps would not detect root, although any app that was already using root could continue doing so.
I checked Magisk, which said root was not installed. I booted my phone into recovery, and somehow my phone had the stock recovery flashed on it. I tried flashing TWRP on it again, and it worked. Except, when I rebooted my phone into recovery later again, it went back to stock recovery.
I have no idea what's going on, and would really appreciate some help.
(PS: I do know how to update my phone without the phone reverting to stock recovery, I've done it many times before, so that can't be the problem)

update: I tried flashing TWRP again (through bootloader), and this time I jumped straight to recovery. It showed all the directories as if my phone had just been completely wiped. Internal memory 0M. No files anywhere. Didn't even have a downloads folder.
In a panic, I rebooted my phone, but my phone was actually untouched, no data wipe whatsoever. I'm even more confused about what the hell is happening now.

The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.

It's the version. If I use 3.2.3.0 or 3.2.2.0 I get no files. But 3.2.1.1 works for some reason. You can also install pie now. There is a link in the one plus 5 forums here to hydrogen os. It's Chinese version but that doesn't matter. It is in English. You will need to uninstall a few Chinese bloatware apps and flash gapps. But besides that I don't see much difference. If anything the hydrogen os looks nicer. I'll add some screenshots . Developer options was enabled from first boot, with the advanced reboot menu I noticed.

Also, if you have root the TWRP app can flash recovery from in the OS.

Fif_ said:
The stock OOS will automatically reflash the stock recovery if it detects it has changed to something else.
You have to boot into TWRP right after installing it and either let it mount /system read-write (likely to cause problems later) or install something like Magisk that will prevent overwriting the recovery.
TWRP was not able to read your data partition, which can happen depending on which kind of encryption you have. Try the BlueSpark TWRP, it supposedly supports encryption better than the official one.
Click to expand...
Click to collapse
It's frustrating for sure. Lol

calls have no speaker or mic

Everytime no matter what I do after flashing a ROM it eventually stops my calling ability. It calls out but no one. Can hear me and I can't hear them.

What OOS are you using? How are you exactly installing roms, step by step..? What rom installing?? Must have more details to help...
After i see that info ill know more. Possible its a hardware issue but i lean more towards software.. Let me know those things and i can help more.
How I install on OnePlus 6t global (or converted)
Boot twrp v3.5.0
Flash OOS 10.3.7 from repo or updater app
Flash rom (with gapps)
Flash twrp installer zip
Flash finalize
Format data (wipes it ALL)
Reboot recovery
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Without gapps rom install:
Boot twrp
Flash OOS 10.3.7
Flash rom (without gapps included)
Flash twrp installer
Flash finalize
Format data (wipes everything)
Reboot recovery
Flash gapps package
Flash magisk
Reboot system
*Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
Use NanoDroid Micro G and Fdroid instead of Gapps on a rom that has sig spoofing and NO Gapps included:
1st part of micro G install:
Boot twrp
Flash OOS 10.3.7
Flash rom
Flash twrp installer zip
Flash finalize
Format data
Reboot recovery
Flash magisk 21.4
Reboot system
Select magisk icon in app drawer and allow update, itll usually auto reboot in 5 secs after it updates..
2nd part of Micro G rom install:
Boot twrp
Install micro g (stable) zip from Nanolx xda thread
Install Fdroid from Nanolx xda
Reboot system
Can also use twrp mauronofrio's 3.4.0-9-11. Those are newest twrp. I've flashed everything made for 6t and never an issue like this. Link to micro g and fdroid installer and more in my signiture.
(Edit)

Hey thanks for the responce, so here we go....
How I flash my roms
Flash OOS 10.3.7/twrp
Reboot recovery
Flash other side of a/b with OOS/twrp
Reboot recovery
Flash rom/twrp installer
Reboot recovery
Flash additional as in my migrate/magisk
Format data
Boot
The Roms I've tried are resurrection remix latest build & msm extended & one other I can't remember which tho. & with stock kernel. I've tried flashing other kernels it doesn't do anything or I'm trying the wrong ones.
Im not new to flashing been doing this for a while now, there's always bugs but there's also ways to fix the bugs. Something interesting is just one time calling it worked fine then the next call... back to no audio feedback. There are 2 other Roms that did the same thing. It happens completely random, like I'll be done modding my phone to my likings go a month or a week & all the sudden no audio. I doubt it's hardware cuz if I format data calls work again but yay all my customizing is gone. I've tried all the suggestions from other forums asking similar question like editing build.prop & a few other things I can't remember nothing's worked. I love this phone to death but it's not easy to keep it stable unless I wanted to go with linegen ROM but ever since they left cyanogen their customizations are lame. Anyways I hope this is enough details I imagine not just let me know thanks I appreciate your help.

I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio

jessejamesd2i said:
I'm no noob but definitely not a master, i use micro g. It's something in the data partition so technically it should be fixable im just sick of re flashing every time it decides it's not a phone anymore just a mini computer that can't compute phone call audio
Click to expand...
Click to collapse
The only time i experienced similar on my 6t is when i used a sound mod, the zen 5 sound mod from asus phone ported.. It caused me to have this no sound issue but when i disable it via magisk it was fine and i had sound again.
Have you tried going back to OOS 10.3.7 only and see if sound is an issue?

If this is present on OOS i would think its a hardware issue.

I cleared dalvik cache

Well i was just flasing my new boot.img that was patched with magdisk dowloaded the correct version 11.0.4.4 - EU IN11BA -IN2023 package from oficial one plus sites after the flash evering worked kinda ok the device rebooted like 3 times it was already rooted before so magdisk was loading all modules i guess everything loaded ok after third reset i ve gone ahed tested it for some time then something happend i was all of sudden unable to launch any apps and the ones that launched crashed withni 10s well i said to myself i ve seen this before on my huawei p9 and what i did there to fix this was clearing dalvik cashe then reset (huawei was running RR from open kirin and android 8) on huawei the main cause for this was messing with the cahe with lucky patcher well it even has a clear dalvik cache funuction so i launched the app on one plus and cleared the dalvik cache and after restart i got into boot looping with no ending (well after that i went to internet to read that dalvik cache is not even a think) so i tried to flash back the stock boot well that didnt fix so if somebody could point me to how to restore the device with keeping the data it would be appreciated i tried some restores like flashing some system partitons and overall trying to flash stuff from this guide https://www.thecustomdroid.com/oneplus-8-pro-oxygenos-restoration-guide/ with the updated version 11.0.4.4 of the ota package well nothing really happed half of the partitions are renamed and i dindt find the names for them anywere so i gave up to find help here.
So yea just a simple reboot to fix the device isnt enough for me i always have to "fix" something diferently.
well i ve let the device boot loop for some time and well i got at least some error
Boot Reason : fs_mgr_mount_all
unable to parse kernel log. for more debug information.
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
So i maybeee destroyed the partitions i guess. (well my thinking is that the LP didnt find the partiton so it tried to format something that was similar to it maybe acros multiple partitons and did kinda nasty wipe.)

First try to boot into the device via safe mode.
If that works just reboot again then all your magisk modules will be disabled.. You absolutely should disable them all before you update/root.
I have a thread for this in the guides section.
If however the safe mode didn't work then you could boot (not flash) a patched boot.img, if it boots then you can go ahead and disable the magisk modules and then go to install and install directly within magisk to make root permanent.
Only if the above works should you attempt to turn any modules back on and only if they're rated to work on 4.4
I would recommend running the remove magisk modules adb command which can also be found in my guide, if the above doesn't work, instructions for running it in the thread.
If none of this works you could maybe go down the route of flashing partitions but personally I'd just MSM and bite the bullet.
Good luck

dladz said:
First try to boot into the device via safe mode.
If that works just reboot again then all your magisk modules will be disabled.. You absolutely should disable them all before you update/root.
I have a thread for this in the guides section.
If however the safe mode didn't work then you could boot (not flash) a patched boot.img, if it boots then you can go ahead and disable the magisk modules and then go to install and install directly within magisk to make root permanent.
Only if the above works should you attempt to turn any modules back on and only if they're rated to work on 4.4
I would recommend running the remove magisk modules adb command which can also be found in my guide, if the above doesn't work, instructions for running it in the thread.
If none of this works you could maybe go down the route of flashing partitions but personally I'd just MSM and bite the bullet.
Good luck
Click to expand...
Click to collapse
Well i would like to try booting it into safe mode but the pohone after i ve letted it to boot loop for like 10 mins desnt event try to boot again i changed nothing so i guess something got modified in the phone to prevent bootloops when i power it on it just reboots into recovery and it would be really nice if you could give me links to those guides i just cant find them thanks