Database Users

[Q] problem with device

I know this isnt the right place for this thread, but i lost my other login credentials and had to start fresh, so Im posting here....
Device: SM-T230NU
Problem: I used a website outside of XDA to root my device. I followed the instructions precisely too, I than unplugged the device hoping that replugging and restarting odin would fix the problem i have/had as displayed by the picture. I than tried rebooting the device, and got this error message: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Well I downloaded Kies 3, and much to my surpise I got an error message about the samsung galaxy tab 4 7.0 not being supported by Kies 3. I am now downloading Kies 2.6, so I can atleast get this device booting normally.

If you knew this was not the place to post, why did you post a question here? A play by play of your device root is not of much interest to anyone! I hope you got it fixed up anyway!

It's been fixed. I found an alternate DL site that had Odin in the package..I used ODIN to run cf_auto_root which created that firmware upgrade issue...I had to Odin firmware from the links I found on these forums...it's rooted now though

[Q]Samsung SM-N900 bricked

Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..

@bluws just download any stock firmware for your phone and flash it later with Odin. Use Odin 3.04 or 3.07 if 3.09 failed.
tetakpatalked from Nexus 7 flo

Make sure you are using correct Ver of root, make sure kies not running in bag round when you flash threw Odin, take care of antivirus
Sent from my SM-N9005

bluws said:
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
Click to expand...
Click to collapse
Try to connect your phone from the KIES program in a mode of emergency restoration of firmware by Model phone type and Serial Number of the phone. This may take several hours. To do this, you need a good internet.

bluws said:
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
Click to expand...
Click to collapse
Did you previously disable Knox? If you didn't, that can cause random problems, read about it in the newest Chainfire's thread in recent post:
http://forum.xda-developers.com/showthread.php?p=55325329
What kind of root process did you use Odin for?
tetakpatalked from Nexus 7 flo

Ty guys i got it working just by flashing a new stock rom. Tho now i am unable to call (no mobile services). Apparently it says that there are no sim card or something like that, does the region of the firmware i downloaded have something to do with it. Im living in indonesia (xse) but downloaded the russian stock i think.

bluws said:
Ty guys i got it working just by flashing a new stock rom. Tho now i am unable to call (no mobile services). Apparently it says that there are no sim card or something like that, does the region of the firmware i downloaded have something to do with it. Im living in indonesia (xse) but downloaded the russian stock i think.
Click to expand...
Click to collapse
Good it works again now!
Maybe it is just a baseband problem? I'm sure you will find an asian baseband only and be able to flash it.
Is your IMEI number still there? If yes, make sure to create backup of it now.
tetakpatalked from Nexus 7 flo

Reporting a Problem With a Firmware

Hi
I today tried to flash my S5 using this Firmware: -
http://click.xda-developers.com/api... | Samsung Galaxy S 5 | XDA Forums&txt=MegaNZ This is the firmware in the 2nd post on the "[SM-G900F] S5 Firmware Thread "
This is the Official Stock Rom for my device and was under the impression it was not country specific.
I had Lollipop installed already from when it was first released and as always used Odin (3.09 in this instance) to flash. It flashed without problem. I have just been away for 2 weeks and in the meantime, my wife flashed her S5 through Wifi after getting popups reminding her to do so. She had no difficulty upgrading from KitKat to Lollipop either.
However a massive PITA for me was that I could not mute the volume as easily as I could with KitKat and when my wife showed me she could do it, after her upgrade, I simply had to upgrade, her version being the same as the one quoted above.
So this morning I downloaded the file and proceeded to flash (again using Odin 3.09). It got all the way but at the end, just before writing, I got "Fail" - it had completely failed and I was stuck in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen." I had never seen this before and thought I'd bricked my phone.
After searching in vain for a solution on this forum, I got nowhere fast. However I wondered if I could take the battery out, replace it to a blank screen and try going into "download mode" once more.
I could indeed! So I then downloaded the same file (I presumed) from Sammobile, to see if I could start over. It worked!!!! And more importantly, I too can mute my phone's volume - Happy Days !!!
But it seems (and from Googling) some of your firmware files are corrupt. Not my PC as I checked the file before using it to ensure it was binary correct.
So I am reporting this officially because I can see no other threads on this subject - maybe in a specific post but not, that I can see, in a specific thread.
I have been a member here for some years and never had an issue like this - your firmwares have been always ok until now. They are faster to download which is why I use them. The Sammobile file took 2 hours to download on their free service but it was fine, unlike the one above.
Any thoughts ?
roz

Samsung Galaxy Note 4 SM-N910W8 (Canadian) Hard-Bricked; Any Solutions?

I have a hard-bricked Samsung galaxy note 4.
After I rooted my note 4, it started to display problems. It would randomly crash processes, reset, and freeze. One day, it turned off by itself despite the battery being at around 40%. I tried to turn it on but it wouldn't respond.
I replaced the battery thinking it was a battery problem. It didn't fix the problem. I also replaced the power button inside my phone. That didn't fix it, either.
My phone cannot enter download mode. It also doesn't respond when i plug it into an outlet.
When i connect the phone to my computer, my phone is recognized as this device:
Qualcomm HS-USB QDLoader 9008 (COM5) [Ports(COM&LPT)]
Manufacturer: Unavailable
Model: QHSUSB__BULK
Model Number: Unavailable
Categories: Unknown
Description: Unavailable
Does anyone have a solution/fix for de-bricking a hard bricked note 4 SM-N910W8 with these problems? I've searched everywhere w/ no success. Thanks.
Edit - GREAT NEWS, fellow N910W8 users! A user posted the N910W8 debrick image, today! I haven't used it to debrick my phone, yet (My phone is disassembled and i may need a new battery) but there's no harm in trying it.
Link to the user's post (User name - Valentinez on page 20)
Link to the n910w8 debrick.img

Please explain what exactly did you do before starting to have those issues. What did you use for rooting?
Sent from my SM-N910F using XDA-Developers mobile app

Ok. I'll explain step-by-step. Since i'm a new user, i can't post outside links in my messages. I'll try to explain how i did it w/o links. I'll PM you the links i used to give you a clearer message on how i did it. Hopefully, i can PM links.
1. My phone was initially running 5.1.1 lollipop (n910w8vlu1coi4) before I decided to root it. It didn't display any of the problems that it had after rooting it.
Unfortunately, i used a guide that doesn't seem to exist, anymore.
I downloaded these files
- CF-Auto-Root-tritecan-tritecan-smn910w8.tar
- SuperSU - v2.65-20151226141550
- Odin3 - v3.10.6
- twrp-3.0.2-0-tritecan.img.tar
I did all of the pre-req things i was supposed to do before rooting (turned on developer mode & turned on USB Debugging). I put the CF-Auto-Root file in the AP field of Odin & pressed start. It passed. Afterwards, i put my phone in DL mode again and installed TWRP via the AP section of Odin. It passed as well.
My phone didn't root initially from doing both of those things. I had to go into TWRP and root the phone from there.
2. After doing all of that, my phone started to crash processes. Contacts crashed first from what I can remember. Others crashed over and over again. I thought it was due to having a bunch of apps on my phone prior to rooting it that didn't react well to the custom firmware/root. I decided to factory reset the phone via the OS' settings. When it turned back on, it continued to crash processes.
3. I decided to install CM 12.1 to see if that'd make a difference. I installed it via TWRP.
When i first booted CM12.1 up, i found that processes didn't crash on it, anymore. Also, it was faster than it was before. Unfortunately, it started to display other problems. It would freeze, reset, and turn off on its own. I reverted back to what i had before when that happened.
4. I decided that the CF-Root Tar image i installed to Odin to root my phone was screwing it up. I decided to un-root my phone by going back to stock firmware. I used samfirm (Samsung Firmware Downloader) to download the latest stock firmware for my phone.
Android 6.0.1 was the only stock firmware i could download. This was the name of the file:
SM-N910W8_1_20160507131653_k12ydzqths.zip
I flashed it to my device via odin by putting it in the AP section of the program. It passed.
5. When i booted up my phone after that, it seemed fine. It had a battery drain problem but that was a widely reported problem w/ android 6.0.1. My phone also wasn't rooted, anymore.
Unfortunately, the problems my phone had before came back. It would freeze and reset here and there. The processes didn't crash like they did after i initially rooted the device, though.
6. About a week later, my phone turned off by itself & wouldn't turn on anymore. I hooked up the phone to my computer and it wouldn't recognize it as a note 4. It recognized my phone as "QHSUSB_BULK".

feez_22 said:
Ok. I'll explain step-by-step. Since i'm a new user, i can't post outside links in my messages. I'll try to explain how i did it w/o links. I'll PM you the links i used to give you a clearer message on how i did it. Hopefully, i can PM links.
1. My phone was initially running 5.1.1 lollipop (n910w8vlu1coi4) before I decided to root it. It didn't display any of the problems that it had after rooting it.
Unfortunately, i used a guide that doesn't seem to exist, anymore.
I downloaded these files
- CF-Auto-Root-tritecan-tritecan-smn910w8.tar
- SuperSU - v2.65-20151226141550
- Odin3 - v3.10.6
- twrp-3.0.2-0-tritecan.img.tar
I did all of the pre-req things i was supposed to do before rooting (turned on developer mode & turned on USB Debugging). I put the CF-Auto-Root file in the AP field of Odin & pressed start. It passed. Afterwards, i put my phone in DL mode again and installed TWRP via the AP section of Odin. It passed as well.
My phone didn't root initially from doing both of those things. I had to go into TWRP and root the phone from there.
2. After doing all of that, my phone started to crash processes. Contacts crashed first from what I can remember. Others crashed over and over again. I thought it was due to having a bunch of apps on my phone prior to rooting it that didn't react well to the custom firmware/root. I decided to factory reset the phone via the OS' settings. When it turned back on, it continued to crash processes.
3. I decided to install CM 12.1 to see if that'd make a difference. I installed it via TWRP.
When i first booted CM12.1 up, i found that processes didn't crash on it, anymore. Also, it was faster than it was before. Unfortunately, it started to display other problems. It would freeze, reset, and turn off on its own. I reverted back to what i had before when that happened.
4. I decided that the CF-Root Tar image i installed to Odin to root my phone was screwing it up. I decided to un-root my phone by going back to stock firmware. I used samfirm (Samsung Firmware Downloader) to download the latest stock firmware for my phone.
Android 6.0.1 was the only stock firmware i could download. This was the name of the file:
SM-N910W8_1_20160507131653_k12ydzqths.zip
I flashed it to my device via odin by putting it in the AP section of the program. It passed.
5. When i booted up my phone after that, it seemed fine. It had a battery drain problem but that was a widely reported problem w/ android 6.0.1. My phone also wasn't rooted, anymore.
Unfortunately, the problems my phone had before came back. It would freeze and reset here and there. The processes didn't crash like they did after i initially rooted the device, though.
6. About a week later, my phone turned off by itself & wouldn't turn on anymore. I hooked up the phone to my computer and it wouldn't recognize it as a note 4. It recognized my phone as "QHSUSB_BULK".
Click to expand...
Click to collapse
Were able to fix?
I have a Rogers n10w8 that FUBAR'd too
---------- Post added at 10:33 AM ---------- Previous post was at 10:19 AM ----------
CANNOT BELIEVE THAT I CANNOT FIND ANY WHERE!
Can someone please upload a debrick.img for this phone and post a link?
Please...
Thanks!

Is there a fix yet?

my note 4 phone is restarting and freezing
my note 4 phone is restarting and freezing every 10mins and i'm on the verge of smashing the thing off a brick wall.
if anyone thinks they can help, please get back to me asap.

kojam said:
Were able to fix?
I have a Rogers n10w8 that FUBAR'd too
---------- Post added at 10:33 AM ---------- Previous post was at 10:19 AM ----------
CANNOT BELIEVE THAT I CANNOT FIND ANY WHERE!
Can someone please upload a debrick.img for this phone and post a link?
Please...
Thanks!
Click to expand...
Click to collapse
Not yet.

pukarmhz said:
my note 4 phone is restarting and freezing every 10mins and i'm on the verge of smashing the thing off a brick wall.
if anyone thinks they can help, please get back to me asap.
Click to expand...
Click to collapse
You should restore it w/ odin. Type in "Galaxy Note 4 restore odin xda" on google and you'll find a few good threads.

Droidskii said:
Is there a fix yet?
Click to expand...
Click to collapse
Nope. Not yet. I've been searching and searching for months and haven't found anything.

Same here. I've been searching everywhere for a 910W8 debrick image everywhere but no luck. If anyone has one, please post.

thepez said:
Same here. I've been searching everywhere for a 910W8 debrick image everywhere but no luck. If anyone has one, please post.
Click to expand...
Click to collapse
Check the original post of this thread. I updated it with the n910w8 debrick.img.

kojam said:
Were able to fix?
I have a Rogers n10w8 that FUBAR'd too
---------- Post added at 10:33 AM ---------- Previous post was at 10:19 AM ----------
CANNOT BELIEVE THAT I CANNOT FIND ANY WHERE!
Can someone please upload a debrick.img for this phone and post a link?
Please...
Thanks!
Click to expand...
Click to collapse
Check the thread's initial comment. I updated it with the N910w8 debrick.img and where it was found. They have steps on how to fix your phone.

SM-G900F unusual brick

its a european 32gb version samsung galaxy s5 SM-G900F.
the device is just over 2 years old never used rooted, since it wasn't mine.
i once rooted the device and reverted it back to official half a year ago or more.
been using the exact same PDA numbers (since that didn't work also tried different) for the official rom etc.
now during normal use, to be specific in a viber call.
the device suddenly shut off and went into a bootloop mode.
there are times the device just shows a black screen and after holding the battery out for some time it opens up again.
prior to flashing another stock rom through odin i just managed to get it booting after a factory reset holding the vol down button (safe mode)
and that is not consistent at all.
same goes as for recovery, with a lot of inconsistency i got it to boot a couple of times in recovery and once in twrp flashed through odin, tried flashing lineageos.
as i left the phone and came back i found it in a bootloop wich is unusual because twrp doesnt automatically reboot after flashing.
tried:
-cf auto root
-the european 32gb pit file
-repartitioning
-flashing multiple stock through odin
-fastboot doesnt recognize the device
-adb used to recognize, doesnt anymore
-flashing recovery
-another battery
-flashing cyanogenmod through twrp with no success
-flashing bootloader (and all else AP/BL/CP/CSC)
-tried samsung kies
-wiping cache, dalvik cache/ data factory reset (when recovery did to happen work out of luck)
the only thing working quite consistent is the bootloader through odin (no fastboot console detection) right now thats about all
and even then sometimes the phones screen is black during boot but after having the battery out for some time it works.
if i plug the phone in the charger it boots up in android but with a black screen.
i can notice because the lower touch buttons on the screen get lightened up and once i've heard the screen reader through the speakers.
it doesnt happen to boot to android without being plugged in.
so in other words im stuck with a phone on which no matter what i tried only has a working bootloader after unpopping the battery for a bit.
forgot to mention also the device always acts as if its turning on so it vibrates, either that results in a visual bootloop/or black screen not even reaching the roms logo (in the beginning sometimes did).
lately if it shows something after holding the battery out its just the galaxy s5 first logo and no rom bootup.
so its not that i press the power button and its completely dead
according to all bootloop brick solutions none of them worked as it seems its more than just that in my rare case
advice would be extremely appreciated

here is a picture of the bootloader

There was a similar/same issue that was solved on the following thread.
http://forum.xda-developers.com/showthread.php?t=3505610
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Ibuprophen said:
There was a similar/same issue that was solved on the following thread.
http://forum.xda-developers.com/showthread.php?t=3505610
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I read this and many other threads before but most if not all were solved with one of the steps i mentioned, furthermore it has always used and worked with sm-g900f roms and also states its a 900f in the bootloader unlike the experience with this thread

thanas said:
I read this and many other threads before but most if not all were solved with one of the steps i mentioned, furthermore it has always used and worked with sm-g900f roms and also states its a 900f in the bootloader unlike the experience with this thread
Click to expand...
Click to collapse
Did you try posting your issue on the following thread?
http://forum.xda-developers.com/showthread.php?t=2700073
I have a G900V and this thread is very active for all the Variants.
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Ibuprophen said:
Did you try posting your issue on the following thread?
http://forum.xda-developers.com/showthread.php?t=2700073
I have a G900V and this thread is very active for all the Variants.
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
no since the only samsung i had was years ago an s2 im not familiar. thanks man i will right now!

did u try another batttery
could be bad hw such as memory

vincom said:
did u try another batttery
could be bad hw such as memory
Click to expand...
Click to collapse
yes i tried another battery, also popped out the sdcard and sim card.
the same happens with a battery which is functional in another SM-G900F most of the time it just shows a black screen unless i leave the phone without a power source for some minutes.
after it just goes into a bootloop. or if i just put the battery back in the bootloader is almost guaranteed to work.
of the so many times trying i just managed to get 4 times in recovery or so.
well it still boots within android i can hear the narrator etc. just not with screen on.
i dont know how i did it but 2 times i managed to get it fully functional into safe mode.. not until a reboot. wonder why

also tried within odin flashing after researching options: NAND erase all, Phone EFS clear, Phone bootloader update, Repartitioning.
all combined when flashing full BL,AP,CP,CSC plus pitfile although ive read the pitfile is in the CSC if its not HOME_CSC. just to be sure for avoiding a brick.
despite this still same.
there is no way to create a backup and create an odin flashable file from a workin g900f right? ive read samsung locks partitions such as bootloader etc.
im sure this complexity is just a samsung thing, ive debricked phones even worse than this and somehow nothing appears to work.
what im currently having is a working phone with a black screen.
i can only go to the bootloader with screen on. the phone boots normally with screen off.
ive done nand erase all and all the above options i named on the latest PHN update meant for this phone.
simple solutions dont work since ive tried all, i feel i need to find a way to restore every partition to its original state with an older bootloader since ive read lots of people were experiencing this after lollipop or onto marshmallow.
can anyone help me a bit with ideas on this?