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.
Related
hi all i have Samsung Galaxy Grand Prime form t-mobile i was using the phone with kingroot and it was working fine but for some reason i am getting this error now Custom binary blocked by FRP now i cant do anything with phone please help.
desiking911 said:
hi all i have Samsung Galaxy Grand Prime form t-mobile i was using the phone with kingroot and it was working fine but for some reason i am getting this error now Custom binary blocked by FRP now i cant do anything with phone please help.
Click to expand...
Click to collapse
OK i manged the get the phone working again using this method
Quote:
Originally Posted by zomgitsanoob
Your instructions were slightly off. Here's what worked.
1) install KIES 3. DO NOT PLUG IN PHONE
2) go to tools -> firmware upgrade and initialisation in KIES
3) device id = SM-G530AZ ; serial number is under battery
4) allow KIES to download the firmware
5) place phone in ODIN mode/Emergency Download Mode (hold VOL DWN and HOME while powering on ) then plug in phone to computer via USB
6) allow KIES to send image to phone. Have some ice cream and egg rolls and do not touch anything.
7) PROFIT! After the phone restarts, it will take you through initial set up (like when you bought it)
Click to expand...
Click to collapse
but under ODIN mode menu it still says FRP lock so now my question is how do i remove the fpr lock ?
Enable developer options then enable oem unlock
desiking911 said:
OK i manged the get the phone working again using this method
but under ODIN mode menu it still says FRP lock so now my question is how do i remove the fpr lock ?
Click to expand...
Click to collapse
Custom binary blocked by FRP Issue
desiking911 said:
hi all i have Samsung Galaxy Grand Prime form t-mobile i was using the phone with kingroot and it was working fine but for some reason i am getting this error now Custom binary blocked by FRP now i cant do anything with phone please help.
Click to expand...
Click to collapse
esummers91 said:
This what worked for me. Try this at your own risk .
I tried the stock rom listed here through Odin and I was not able to get back into my device because of the
FRP Lock. FRP Lock Binary Message , would not let any of the roms boot onto my device from Odin and I tried a lot of different solutions. This is the only thing that worked for me .
I downloaded Kies 3.
I installed it .
I put my device into download mode ( I did not connect it yet )
Kies wil tell you that your device is not compatible with the software .
Knowing that Tmobile software would be close enough I decided to give this a try. (Some people have bricked their phones trying to run t-mobile software through odin, this is running through kies is different, it worked for me.)
In Kies I then went to where it said Tools,
I selected the option that says "Firmware Upgrade and Initialization.
Its going to ask you for the model number and the serial number.
I won't go into details of how I got it but use the MN: SM-G530T1 - Serial Number: R28GA0EJ6FZ
Its a public serial number
Then from there it ask you to hook up your device,
Once you hook up your device you can continue with the install.
Make sure that you are taking the battery all the way out before putting the device in download mode. In my opinion this may be the best way to make sure it works.
Please let me know if this works for anyone. Thank all of you that helped me and gave me advice to get my phone restored . I hope that this helps everyone who has this issue.
One things for sure . This will make me never want to buy a metro device again especially if there devices aren't supported by samsung.
I'll try my best to answer any questions anyone might have. I'm really hoping that this will help all who have that nasty FRP LOCK
ISSUE
Click to expand...
Click to collapse
The phone will now boot with the Tmobile Stock and saw far everything is working Great !
Help
esummers91 said:
The phone will now boot with the Tmobile Stock and saw far everything is working Great !
Click to expand...
Click to collapse
It tells me that it cant install after i put the product name and the serial number
I setup my brothers phone with Kingroot like 2 weeks ago, then randomly yesterday this crap happens. This security feature is ridiculous. A warning, I can understand but this thing is borked.
Using the stock cable and connecting it to the laptop at the error screen, as well as at the bootloader. In both instances, the phone started charging, but wasn't detected by the PC.
Having the same issue. ..
esummers91 said:
The phone will now boot with the Tmobile Stock and saw far everything is working Great !
Click to expand...
Click to collapse
I'm having he same issue with my phone but in addition, kies will not allow me to use the S/N that is on the phone. I also tried using the one you have listed and that didn't work either. I'm kinda stuck at this point.
---------- Post added at 02:21 AM ---------- Previous post was at 02:15 AM ----------
johnnyboi808 said:
It tells me that it cant install after i put the product name and the serial number
Click to expand...
Click to collapse
The prog keeps saying the s/n isn't correct. Not sure what to do now. .
I did the same thing and everything works fine EXCEPT multimedia messages. From there as far as I've learned its just trial and error with access point names. Which in the grand scheme of things isn't that bad considering the run around I had to go thru before I found xda forums. Metro told me to file a claim and get a new phone, insurance provider said no and sent me to Samsung, Samsung said no sent me best buy, best buy was going to follow directions noted above except the serial number for the firmware was 1 digit off (I'm assuming they were skeptical about flashing tmobile firmware which I understand but they let me figure that one out on my own). Thank you XDA.
Sooo...how many and which ports have you tried on your PCs? Sammys are finnacky sometimes with USB ports. On my PC, only 1 port will detect ANY Samsung devices in Download Mode but the others work fine with every other device. Try all your ports, preferably USB 2.0 and on the back of your computer. Ones on the front don't usually have enough power for anything other than file transfers.
Just a suggestion from experience
So I bought my son a Galaxy Grand Prime and he said that he was playing some racing game on the phone. He then put the phone on the charger and now there is a message that says Custom Binary Block by FRP. I tried downloading Kies 3 but it is not allowing me to do anything with the phone. Nothing happened so I don't know if I did it correctly. I also took the phone to Samsung and they basically said that the phone is no good. like I am not understanding why this can't be fixed even by Samsung. Some one please help!!!
I do that but it says the S/N its incorrect when its not
Yeah, the kies repair works. You may have to try it a couple times. Just check out this video. Nothing will happen. When you connect your phone to PC until you put it in download mode
Just follow directions
https://m.youtube.com/watch?v=LqoX7wNhotk
---------- Post added at 01:47 AM ---------- Previous post was at 01:44 AM ----------
Directions here also
http://forum.xda-developers.com/grand-prime/help/custom-binary-blocked-frp-t3266961
I hope it fix is my samsungs
I have the Same problem I hope it can fix my Samsung's I rooted android lollipop and my phone is locked out
gorilla p said:
Yeah, the kies repair works. You may have to try it a couple times. Just check out this video. Nothing will happen. When you connect your phone to PC until you put it in download mode
Just follow directions
https://m.youtube.com/watch?v=LqoX7wNhotk
---------- Post added at 01:47 AM ---------- Previous post was at 01:44 AM ----------
Directions here also
http://forum.xda-developers.com/grand-prime/help/custom-binary-blocked-frp-t3266961
Click to expand...
Click to collapse
Thank you thats the video I needed this I'm gonna try this in the morning and try to fix bolth Samsungs galaxy
Oh also, after putting it in download mode it will give you a message saying something like "custom software can cause problems are you sure you want to proceed?". Click yes and proceed, then your phone will connect to the computer.
Just follow the directions and have Kies installed first.
Hi there I know how to fix this problem if you'd like to flash the stock lollipop ROM or simply by pass this frp lock PM me and I'll send you the link for the ROM or the stock boot IMG ☺ this is only for the G530AZ model
my samsung galaxy grand prime SM-G530H do not open after ODIN mode stuck, i disconnect cable while upgrade from kitkat to lollipop, then my mobile do not open and keys are not working also. HOME+POWER+VOLUME UP OR DOWN.
Please help me from this issue
Thanks Man for the help..
I also have a galaxy core prime and I turn my phone off and tried to turn it back on but it showed custom binary blocked and when I tried to fix it but I dont have a computer what do I do
Devante02 said:
I also have a galaxy core prime and I turn my phone off and tried to turn it back on but it showed custom binary blocked and when I tried to fix it but I dont have a computer what do I do
Click to expand...
Click to collapse
You need a computer to run keis or Odin so that you can reflash your firmware
Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?
which OS?
S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread
Hello everyone,
2 weeks ago I rooted my Galaxy Note 4 sm-n910f using root online with KINGO.After the root, I used the phone normally and nothing went wrong.After my battery was low, I I switched off the phone to charge the battery. Once the battery was 100%, I turned it on, and the problem started, it was a bootloop. I tried to do all kinds of reset in recovery, but nothing worked.My ROM was 5.1.1 and here in sammobile I downloded 6.0. 1 to flash with odin. After unzip I got errors saying that the file was corrupted but I ignored the errors and kept the file broken with WINRAR.after put the phone in download mode and flash with Odin when it reached in aboot .mbn he stopped for over 1 hour, i removed the phone and i was still having the errors. So, I tried to download other firmware from here and from other site, but I do not know why all the files for my phone model are corrected pted, and all gave the same error.With a version more recent odin, he stops at Nand write start for hours.I tried to download a file that did not give an error, but still the same problem.Thus, I tried to download 4 files to hide according to other site tutorials, but it is still stuck in aboot.mbn.After using the samsung tool (Z3X), and when blinks with this tool, everything starts okay, and then I get the boot.img error time So, in fact when I turn on my phone, I get the following message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again ".I tried with KIES and Smart Switch, but the phone is not even recognized, but my KIES is I have the latest version and I have the model drivers installed. So, my phone is dead or there is a way to fix this problem.
jochri3 said:
Hello everyone, 2 weeks ago I rooted my Galaxy Note 4 sm-n910f using root online with KINGO.After the root, I used the phone normally and nothing went wrong.After my battery was low, I I switched off the phone to charge the battery...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2866810
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hello, all!
I have a Samsung Galaxy S7 (SM-G930A). I originally used the PrinceComsy post (https://forum.xda-developers.com/att-galaxy-s7/how-to/root-s7-att-g930a-g935a-t3410538) to root my S7. This was back about 6 months ago. I ended up using an iPhone (for change of pace) and came across my S7 again and wanted to go back. It was working at the time, no problem. Since then, however, I must have done something within Odin to break it as now it is stuck at the Samsung logo boot screen with the "custom"/unlocked padlock icon on it. I cannot boot to recovery mode as when I do, it simply flashes "recovery booting..." indefinitely.
I think I need help to get this thing working again. I don't necessarily care if it has to get wiped. That said, I am willing to do what I need to do in order to get this damned thing fixed. I have tried flashing a few different G930A firmwares, but Odin either just says "failed" or "model dismatch." I have no idea what to do and all the threads I've read so far seem to be different than what I am going through.
Any ideas? Anything is much appreciated. Take care!
As it would turn out, the only firmware that I got to actually successfully flash to the S7 was the SM-930U firmware. I can now get into recovery mode and I can at least get passed the initial logon logo. When I start the phone, it takes me to the setup as if it is a new phone, however, after a certain amount of time, the phone will randomly reboot. Hmmm... going to continue to tinker with it.
Here is how I fixed my issue:
1. Downloaded and flashed the SM-G930U firmware using Odin3 v3.12 to my SM-G930A S7. This fixed the issue with not being able to get into Recovery Mode and with the phone stalling at the first boot-up Samsung logo screen.
2. Once I was able to get into recovery mode (verify this... my original issue was that it would simply flash "recovery booting..." and go nowhere.
3. I downloaded the Nougat QE1 firmware from this post: https://forum.xda-developers.com/at...mware-g930a-qe1-android-7-0-6-4-2017-t3617101
4. Flashed above firmware.
5. Rebooted a couple of times and I got into first time setup within Android (I could also tell that it worked because the ATT chime came back after rebooting).
Hope this helps someone out there! Been working on this for a couple days and it is nice that it is now working
DentMan06 said:
As it would turn out, the only firmware that I got to actually successfully flash to the S7 was the SM-930U firmware. I can now get into recovery mode and I can at least get passed the initial logon logo. When I start the phone, it takes me to the setup as if it is a new phone, however, after a certain amount of time, the phone will randomly reboot. Hmmm... going to continue to tinker with it.
Click to expand...
Click to collapse
I'm also facing the same issue...
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
DentMan06 said:
Here is how I fixed my issue:
1. Downloaded and flashed the SM-G930U firmware using Odin3 v3.12 to my SM-G930A S7. This fixed the issue with not being able to get into Recovery Mode and with the phone stalling at the first boot-up Samsung logo screen.
2. Once I was able to get into recovery mode (verify this... my original issue was that it would simply flash "recovery booting..." and go nowhere.
3. I downloaded the Nougat QE1 firmware from this post: https://forum.xda-developers.com/at...mware-g930a-qe1-android-7-0-6-4-2017-t3617101
4. Flashed above firmware.
5. Rebooted a couple of times and I got into first time setup within Android (I could also tell that it worked because the ATT chime came back after rebooting).
Hope this helps someone out there! Been working on this for a couple days and it is nice that it is now working
Click to expand...
Click to collapse
And now I'm going to try this...
Btw thanks for your post...
Sent from my [device_name] using XDA-Developers Legacy app
I want to put this Samsung SM-T567V Verizon tablet back to its original factory state, without the software the previous owner used for work, but I think I'm missing something. I've located the factory ROM and downloaded it. I boot the tablet up in odin mode. Start Odin in administrator mode on my laptop. Connect usb cable and recognize the tablet. Choose AP and locate the ROM file. Run the flash. Odin completes and says "PASS". Disconnect the tablet from my lappy and it reboots. Runs all of the normal setup screens as if new (language, email accounts, etc) and finally gets to a home screen. Then about 90 seconds later, it forces me to go through an install for some "Brookdale" program that I'm guessing the previous owner used for work. Once that is done, I see in the Apps section MobiControl and also Knox Mobile Enrollment Service (both mentioned during this last install), but nothing for Brookdale. Its really been driving me crazy! I've searched and searched but I cannot find any help or a solution anywhere. I don't want the previous owners company to think I'm trying to hack into them and I certainly don't want them accessing me either!
So I guess my questions are:
1. Are the MobiControl and Knox apps remnants of the previous user or are they actual factory programs?
2. If these are from the previous user, why wont they get wiped out when I flash the tablet? (I cannot uninstall them either)
Please help!!!
Thank you for any info you can share with me!
Mike
Hi ?
Hi,
I read your post and I have the exact tablet and have the same issues.. I was wondering if your ever got it resolved ?