Please Help Me - T-Mobile Samsung Galaxy S6

Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,

Cummins4 said:
Was running looper just fine on my 920t when system started fc/ing . Flashed latest kt kernal. Still f/c . Wiped chash nothing. Odin back to stock, STILL system F/C! Wiped / Factory reset , retried odin stock , still F/Cing.. Is there ANYTHING else that I can try? I can get into Download ,
Click to expand...
Click to collapse
If it's still happening after two Odin flashes something is seriously wrong with your phone. It started force closing out of the blue? Your sure you weren't poking around in partitions other than system and data?

No, everything was working fine on looper. I flashed Alliance in the 925t thread. Let it boot, went back twrp then flashed latest kt kernel. That's when I started to get the fc. Figured I did something wrong, so Odin stock tar. Still getting the fc. Sorry for the miss post. Just frantic..

So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,

Cummins4 said:
So it turns out by dirty flashing a 925t rom with a 920t kernel over a 920t rom some how caused a system wide fc loop from hell. Completely wiped everything in Stock recovery, also tried twrp. Odin stock tar several times.... I finally threw in the flag and ordered a replacement.. Just thought I'd share,
Click to expand...
Click to collapse
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.

ThePagel said:
The weird part is odin *should* have fixed any problems a rom could cause. Good luck with your next phone, really sucks you had to replace it.
Click to expand...
Click to collapse
Thanks, lesson learned.. Been flash dozens of ROMS since my s2, first-time ever I couldn't save a device. Just so weird. Tried stock tar right from Sammy with everything wiped. Wish someone had an idea what would've caused it. Right Odin, right tar, Samsung cable, different computers... Just think I'll leave it alone from now on. Too expensive to mess around with this device, especially without a reliable fall back.

Just wondering if anyone had any idea on how to fix a force close loop after stock Odin flash? I bought a new device. Obviously my warranty is void. I didn't have insurance. I'm left with a really shiny paperweight. I'm willing to try anything, thanks in advance.

Related

Firmware flash will not unbrick phone?

I used 2.3.5 JVT (+root) for some weeks perfectly fine on my Galaxy S I9000, though a bit laggy due to too many apps.
Today I rebooted the phone and got stuck in a boot loop. Never had that before.
I went into CWM recovery, wiped cache and did factory reset. Did not resolve a thing.
Then I flashed the whole phone again with the 2.3.5 JVT and it did not help either.
What can I do? The phone goes into download and recovery mode perfectly fine, so guess it's OK. I see Odin has an Option "EFS Clear". Would that help?
I would not tick that option. What happened when you flashed stock JVT with Odin? Bootloop?
Yes I use the stock firmware, that is firmware from sammobile.com (samfirmware.com). No fancy mods.
Tried with and without root. Both give me boot loops.
If you properly used Odin with the 3 files, pit, and repartition ticked, and you get bootloops after that then it goes beyond my experience. Maybe corrupted stock rom download? Download again stock JVS or JVT (change the one that you used before).
ok tried too other firmwares. still bootloops.
then i tried stock 2.3.3 and it went past boot screen. but it said UIDs inconsistent, need to wipe data partition. so i wiped data partition. but still same error.
seems like something strange is going on here. i'm always using 512 pit file and flashing with repartition checked!
that happened to me ,i just plugged in my charger and voodoo lagfix spoke then phone turned on apps were transparent set launcher default went into bootloop tried nandroid restore didnt work .eventually flashed 10.2 resurrection xxjvq worked a treat
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
thers a video on tube by totallydubbedhd or puggerdug shows u how but u probably already know ,hope it helps u
try flashing 2.3.4 XXJVP. this ROM worked for me while I went into a similar bootloop like yours once...while in 2.3.5 XXJVS. Then I reflashed JVS and it worked just fine.
I had similar and had to flash a stock rom to get it to boot. Then just root again...Took a while to figure this out. Very frustrating at the time!
.
OK tried a couple of other roms with no success. I read in another thread that someone had exactly the same problem and had Samsung fix it.
Now I am having a problem wiping my SDcard. The CWM backups are on the SDcard, right? So why can I still select them if I wipe the SDcard in Recovery?
OK, Samsung replaced the motherboard of the phone (warranty).
It's working again now.
So to everybody that is having the same problem, it is a hardware problem, most likely. But you will need to have tried everything else that could fix it beforehand, of course.
cdbee said:
OK, Samsung replaced the motherboard of the phone (warranty).
It's working again now.
So to everybody that is having the same problem, it is a hardware problem, most likely. But you will need to have tried everything else that could fix it beforehand, of course.
Click to expand...
Click to collapse
but warranty doesn't cover rooted/hacked phones lol?
HelloThere1 said:
but warranty doesn't cover rooted/hacked phones lol?
Click to expand...
Click to collapse
Yes, I resetted everything to stock.

Phone won't boot

Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?
right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.
Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself
right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?
Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.
If you have tried also with the correct original pit, then it's time for the scanners to do its job
nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?
Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.
SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.
Ok. Try booting into recovery and performing a full wipe.
nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?
Yeah
nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.
right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?

[Q] HELP - Softbrick Galaxy Tab 8.9 Telstra p7320

Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
ragvaror said:
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
Click to expand...
Click to collapse
hey mate,
i was just caught out by this last night. all you need to do is re-flash on a stock rom with ether oden of heimdall and youre good to go. im sure there is a oden flashable rom on these forums
take it sleazy!
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
ragvaror said:
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
Click to expand...
Click to collapse
yeah, i think its becaute the cwm recovery doesnt know what to do with the update.
you need to have the stock recovery installed. dont take my word for it though.
just look up a tutorial for flashing a rom via oden. its really easy, just make sure the image you are flashing is of .tar.md5 extension.
You can get the stock rom at sammobile.com. down load the zip file then extract the .tar.md5 file out of it using 7-zip.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
how ?
ragvaror said:
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
Click to expand...
Click to collapse
i currently have the same problem as you did, how did you flash with odin if you're stuck in recovery mode ?
please help, I'm racking my brain trying to figure this out.

I9305t 4.3 wont boot

HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
spiderman07 said:
flash the original firmware from samsung.....the 4.3 since you updated it...
after it finishes and reboots it will enter a boot loop....IT'S NORMAL.....pull out the battery and start the phone in recovery mode(stock one) and do a wipe data - factory reset and wipe cache partition...it should work without a problem...did this many times...
after you updated to 4.3 you should have done a full wipe...
Click to expand...
Click to collapse
Yeah I have done that. I have tried it about 10 times. Im going to give it another bash today as I am stuck using my wife's old Iphone and its horrendous.
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
spiderman07 said:
try installing your firmware with a .PIT file and check repartition box...search for the pit file....
if this doesn't work i suggest going to local repair shop and let them have a look...
maybe something got broke when you flashed the unbranded firmware...
Click to expand...
Click to collapse
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Filipiak said:
Thanks for the info. Im unsure what a PIT file is. Are they phone specific or just model specific.
Cheers
Pat
Click to expand...
Click to collapse
Found the pit file and read up on it. Tried to use it but it fails as soon as it starts.
Best of luck
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Knox was tripped when the firmware install crashed. So knox tripping is no issue. Thanks for the information. I will have a go tommorrow.
I did manage to restore a cm9 backup but my IMEI is now gone and I cant get to the menu to restore my back up. Seems like Samsung has done a number on my phone. In all the years ive been fingering phones with custom firmware and modding I have never had anything stuff up this bad. Its rather amusing that it has happened flashing a stock rom that belongs to my phone.
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Filipiak said:
AMoizK you are the ****en man. Worked. The part that worked for me was the format everything. IMEI restored as well. Phone is perfect. Now i dont need to use my wifes crappy old iphone.
WOOT!!!!
Click to expand...
Click to collapse
Cheers
Filipiak said:
HI all,
Today I decide to update my i9305t to the 4.3 rom. I unrooted my phone and reset the custom counter and all was good. I flashed the telstra rom and all was good. Because of the locked dock Icons I thought I would flash a different unbranded rom. During the installation (via odin) it went skew if and froze. It sat there for ages but I ended up having to do a battery pull.
When I went to the download menu on the phone, knox had been tripped and there was 47 instances. Any way I reflashed the telstra firmware. It passed but now the phone gets stuck on the Samsung logo.
OK now I have already.....
Pulled the battery.
Removed all cards sim and sd.
Restored different firmwares.
factory reset, clear cahce etc.
Installed custom recovery and cleared devalk cache.
Googled for similar events.
Nothing I have read has worked.
I cant think of what else to do. When I restore a firmware via odin everything is OK, it passes but on the reboot it just stops at Samsung logo and goes no further.
I gather that because the phone can still get into recovery and download mode there must be something can sort this out.
Thanks in advance.
Click to expand...
Click to collapse
It happened to me once, i found that 4.3 won't boot if baseband and imei are unknown. when you were trying to flash with odin and your phone got stuck it probably has damaged or ( erased ) your imei partition. try flashing 4.1.1 ( the package file without bootloader files ) it will definitely work for you. the reason is simple , Samsung's stock 4.3 never boots if the imei is corrupt or unknown (baseband is then usually too ) so, flash 4.1.1 , root your phone and install Persus kernel +any modem / baseband file, this is the only solution as i dont know how but does repair your imei , but you will be stuck at 4.1.1.

Your phone is bootlooping after flashed firmware? Read this. [Tested on A6+ (A605GN)]

Hello everyone, I'm here to share with you guys a solution that saved my life last night.
Well, as a good user, I tried to root my phone and I got it, but the screenlock wasn't working as you guys should know, then I tried to go back to stock and wait 'til someone fix that problem, but when I flashed Stock through Odin, my phone began to bootlooping after Samsung's logo and apperently there was no reason for it to do that, but I got a lot of erros, like:
No data access (Argument invalid);
Modem error (auth), etc.
Well, what I did was just flash TWRP through odin, formatted /data and then I flashed the official recovery and firmware again.
Hope that helps!
iRomulls said:
Hello everyone, I'm here to share with you guys a solution that saved my life last night.
Well, as a good user, I tried to root my phone and I got it, but the screenlock wasn't working as you guys should know, then I tried to go back to stock and wait 'til someone fix that problem, but when I flashed Stock through Odin, my phone began to bootlooping after Samsung's logo and apperently there was no reason for it to do that, but I got a lot of erros, like:
No data access (Argument invalid);
Modem error (auth), etc.
Well, what I did was just flash TWRP through odin, formatted /data and then I flashed the official recovery and firmware again.
Hope that helps!
Click to expand...
Click to collapse
probably during flash with odin you chose Home_csc_omc..... and all phone's data still intact/untouch. that's why need to wipe data in TWRP.
if since the first place you chose csc_omc without HOME label... thats mean you do the clean flash and all will fine no need format data in TWRP.
just my thought..

Categories

Resources