Database Users

[Q] Killed my Tab 4 (SM-T230NU)

I was looking to factory reset my Tab 4 7.0 to sell, but since I've rooted it and installed TWRP, the process wasn't as simple as I'd have liked. I tried the standard Factory Reset function of TWRP, but it didn't do anything. I tried Wipe Data, still nothing. Then I did an Advanced Wipe and checked off everything, not realizing one of the options was to wipe /system. Now my Tab 4 keeps rebooting to TWRP, and the recovery also states "No OS is installed".
I'm currently downloading the new NH1 firmware from SamMobile and considering flashing it through Odin 3.09. Would this be the most effective method, considering I had no prior backup made to the tablet? Will this likely remove my root access and custom recovery? Is there a chance of tripping something like a Knox counter and bricking my device (happened once when I tried an old method to root my Note 3, Knox blocked part of the flash and left the system halfway between two OS images)

Sounds like you're on the right track with downloading the firmware off of SamMobile. I had a similar issue with my Galaxy Tab 2 and that got my tablet out of its funk.
Sent from my SM-T330NU using Tapatalk

At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to completely flash. Odin says it was fully successful, but when the tablet tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)

chuman72486 said:
At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to completely flash. Odin says it was fully successful, but when the tablet tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)
Click to expand...
Click to collapse
hi i have a tab 3 7.0. why dont you try using odin 3.07 if that fails try emergency firmware recovery in kies. odin flashing of official firmware does not increase binary counter as stated by sammy tech support. but you flashing twrp does increase binary count. hope i helped.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app

chuman72486 said:
At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to comCellular allsh. Odin says it was fully successful, but when the taalso tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)
Click to expand...
Click to collapse
I have successfully flashed ND9 and N2E firmwares with Odin 3.07. The NH1 firmware is corrupt when I download it. These are the Cellular South versions which I assume are the US firmwares. I did also flash the Canada versions and I couldn't tell them apart. Currently on ND9 firmware so I could get it rooted. I only have the WiFi 230NU.

chuman72486 said:
At this point I've tried all the ROMs listed on SamMobile for my tablet and all fail to completely flash. Odin says it was fully successful, but when the tablet tries to boot, I only hear half the boot sound and then the boot animation just sits there saying Samsung with the little blue dots popping out of it, and that's it.
Are there any other types of ROMs I can flash to this system? Does it matter what version of Odin I'm using? (Tried 3.06 and 3.09, both unsuccessful)
Click to expand...
Click to collapse
this question may sound silly but have you tried to wipe data/cache after full odin firmware install?
I believe i was able to keep all my apps and data after full firmware upgrade using odin, so it isnt doing full wipe after all.
.

I rooted and installed TWRP on this device and decided I wanted to get the SM-T330NU instead. I returned the T230 and the clerk tried to factory reset the device and it booted up into TWRP - the clerk made the comment "What in the world" but did not say anything. I had tried to factory reset it before returning and it would not work either.

rsktkr1 said:
I rooted and installed TWRP on this device and decided I wanted to get the SM-T330NU instead. I returned the T230 and the clerk tried to factory reset the device and it booted up into TWRP - the clerk made the comment "What in the world" but did not say anything. I had tried to factory reset it before returning and it would not work either.
Click to expand...
Click to collapse
If you power off the device and then boot up into download mode, connect the usb to your pc and run odin you can flash the factory stock image to the device using odin and that will reset the device to stock. Replacing TWRP with the factory recovery image and everything else. You can download the stock files for the device either by searching these forums or going to sammobile. Try starting with the oldest version available and update from there. I rooted and unrooted the SM-T230NU several times using this method and had no issues. Be patient. Allow the device 5 minutes to boot up after flashing the stock. Make sure the device has 80% charge or better before starting. Leave the device connected to the PC with odin open until you see a message in odin that reads, "passed".

chuman72486 said:
I was looking to factory reset my Tab 4 7.0 to sell, but since I've rooted it and installed TWRP, the process wasn't as simple as I'd have liked. I tried the standard Factory Reset function of TWRP, but it didn't do anything. I tried Wipe Data, still nothing. Then I did an Advanced Wipe and checked off everything, not realizing one of the options was to wipe /system. Now my Tab 4 keeps rebooting to TWRP, and the recovery also states "No OS is installed".
I'm currently downloading the new NH1 firmware from SamMobile and considering flashing it through Odin 3.09. Would this be the most effective method, considering I had no prior backup made to the tablet? Will this likely remove my root access and custom recovery? Is there a chance of tripping something like a Knox counter and bricking my device (happened once when I tried an old method to root my Note 3, Knox blocked part of the flash and left the system halfway between two OS images)
Click to expand...
Click to collapse
Just install deodexed rom from twrp

I don't think sm-t230's have Knox do they? You didn't kill your tablet just flash a stock ROM from sammobile. And you'll be a-OK
Sent from my SM-T230 using XDA Free mobile app

Downgraded my Note 3 to kitkat now I have a bootloop

Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!

peety25 said:
Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!
Click to expand...
Click to collapse
Try this:
1. Full wipe first (system, data, cache and dalvik)
2. Flash the VIA Kit Kat firmware via ODIN unticking "Autoreboot".
3. Take out the battery and pull in it again when the flashing process finish.
4. Boot in Recovery and make full wipe again.
5. Reboot your device and it should boot normally.
6. Tell me if it worked for ya

Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.

try flashing MODEM with NON-HLOS, I think you have corrupted the EFS.

peety25 said:
Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.
Click to expand...
Click to collapse
You can flash TWRP recovery if you don't care about KNOX and follow my steps above :highfive:

[Q] SM-G900I

Hi There
Im trying to fix another persons SM-N900I which is stuck in a bootloop.
WHAT HAPPENED TO THE PHONE
What I've been told is that the phone was receiving an OTA upgrade to Lollipop in which it crashed somewhere in the process, which caused the phone to become all glitchy (that's what she said). In addition this caused the KNOX flag to be tripped which meant that the carrier staff refused to honour the warranty saying it was caused by a custom flash.
So attempting to remedy this she tried to use odin to flash a stock rom which sent the phone into an indefinite bootloop. (Sorry no idea what rom she tried to flash or if she clicked something wrong).
WHAT I'VE TRIED
Using Kies to "Firmware Upgrade and Intialisation" with the model number and S/N. This completed successfully with no errors, however after a restart I still get a bootloop.
As in 1 but with factory reset and clearing cache in recovery before flash.
Using odin to flash stock rom from sammobile. Still bootlooped after flash.
Trying stock KITKAT rom from sammobile with odin. Still bootloops after flash.
Installing a custom recovery and installing a couple of custom roms (factory resetting and clearing dalvik cache before install). Still bootloops...
Flashing stock bootloader, and stock rom. Still bootloops...
I wanted to try and flash a PIT file however I get the "secure check fail : PIT" message with and without flashing it with stock rom. Im assuming this is because reactivation lock wasn't disabled.
Not really sure where to go from here?
Thank You

makeez said:
Hi There
Im trying to fix another persons SM-N900I which is stuck in a bootloop.
WHAT HAPPENED TO THE PHONE
What I've been told is that the phone was receiving an OTA upgrade to Lollipop in which it crashed somewhere in the process, which caused the phone to become all glitchy (that's what she said). In addition this caused the KNOX flag to be tripped which meant that the carrier staff refused to honour the warranty saying it was caused by a custom flash.
So attempting to remedy this she tried to use odin to flash a stock rom which sent the phone into an indefinite bootloop. (Sorry no idea what rom she tried to flash or if she clicked something wrong).
WHAT I'VE TRIED
Using Kies to "Firmware Upgrade and Intialisation" with the model number and S/N. This completed successfully with no errors, however after a restart I still get a bootloop.
As in 1 but with factory reset and clearing cache in recovery before flash.
Using odin to flash stock rom from sammobile. Still bootlooped after flash.
Trying stock KITKAT rom from sammobile with odin. Still bootloops after flash.
Installing a custom recovery and installing a couple of custom roms (factory resetting and clearing dalvik cache before install). Still bootloops...
Flashing stock bootloader, and stock rom. Still bootloops...
I wanted to try and flash a PIT file however I get the "secure check fail : PIT" message with and without flashing it with stock rom. Im assuming this is because reactivation lock wasn't disabled.
Not really sure where to go from here?
Thank You
Click to expand...
Click to collapse
If you are using Windows operating system, have you tried running Odin "As Administrator" ( using right click on the mouse when you open Odin ), then try partitioning with the PIT file.

Phone Stuck On Splashscreen

My phone is a verizon gs5 SM-G900V and I tried to root it but something (I honestly have no idea) went wrong and now it is stuck on the splash screen. I have tried everything i thought of, doing a factory reset, clearing the cache partition, I tried reinstalling the stock rom using odin but of course because there was no root and the bootloader is locked, I can't reinstall. I tried applying updates using SD no dice. I am able to access the bootloader and the and the android recovery menu if that will help at all. I don't know every acronym/term because i'm still fairly new to these terms so any help will be greatly appreciated.

I'm guessing you are on lollipop because you say you can't downgrade to KitKat aka stock
so what you should do is go to Sammobile and download either lollipop official firmware bok3 or Pb1.
then install via odin in either ap or pda slot
with the phone in download mode after that wait for the Phone to boot then set it up
then use ok3 root method by Jr Kruse on xda it's a sticky in the s5 verizon forum to get root

Might have Bricked S7 Edge SM-935FD. Need Help to recover

Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.

Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process

zzThrain is right -- I wouldn't risk flashing custom ROMs at this stage, especially because many contain new bootloaders or other stuff that might make this even worse for you. Just pick up the relevant Samsung stock ROM file (from, for example, SamMobile) and see if it boots normally again. Once it does, re-do the process *after checking all MD5s of the files you used* -- I, too, have had it happen before that a download went corrupted and I flashed it. If all is well, get into Download Mode and let Odin rip.

rixon.d9 said:
Hello guys
My phone is Galaxy S7 Edge Duos- SM935FD. I seem to have bricked the device.
Below are the actions I have performed.
1. Flashed TWRP using ODIN as described on https://www.the***********.com/root-samsung-galaxy-s7-edge/
2. Booted successfully into the OS. Found superuser app installed.
3. When I went to back to Flash ROM i erased multiple things such as internal storage/dalvik/cache/system after which device got stuck in bootloop. Showing NO OS.
4. I tried flasing Custom ROM Zip files through OTG. The process failed showing package corrupt and still stuck in bootloop.
I can enter recovery/download mode however cant seem to get the device booted. How can I get the device to work either Custom or stock ROM.
I will be going through some threads in the meantime, your guidance is very much appreciated.
Click to expand...
Click to collapse
Go to recovery mode & transfer rom to phone using pc. wipe cache, delvikcache, data only. No need to wipe internal sd. Install rom & reboot.
if you phone goes to recovery or download mode, no need to worry. If it doesn't go to neither recovery nor download mode, them your phone might have probably bricked.

It's my pleasure to help you if you still facing this problem

zzThrain said:
Flash stock rom with Odin: This shouldnt be posted on Development Forum but rayher questions and Answers.
Find what your Stock Firmware for your phone is using Sammobile and flash stock then re do rooting and TWRP Process
Click to expand...
Click to collapse
Hi
I tried flashing stock rom from sammobile. I could find for SM-935FD hence downloaded SM-935F.
It got stuck at 90% showing System in ODIN.
From the ZIP file which is the file that needs to be flashed among below ? I tried AP.
AP_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship_meta.tar
BL_G935FXXU2DRB6_CL12365438_QB16944063_REV00_user_low_ship.tar
CP_G935FXXU2DRAG_CL648265_QB8691891_SIGNED.tar
CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
HOME_CSC_OJV_G935FOJV2DRAG_CL12785220_QB16560277_REV00_user_low_ship.tar
Now when I try again it immediately shows FAIL. Am i Flashing the right stock rom ?

It Worked. Thanks to all who helped.
I wasn't running ODIN as Admin and also was using an slightly older version V3.10.7.