Related
So I was trying to root my phone. Kinda went through a quick crash course of it with Odin. For some reason it kept hanging up at boot.img but that's a different story. Long story short, after numerous tries, I forgot to unclick repartition. Why it clicks itself when you load up the PIT is beyond me. Personally, I think the developer got a kick out of people bricking their phones that way. **** him/her. Anyway, I can't get into download mode anymore, even with a JIG. Anybody got any ideas before I send it for JTAG?
crimsondragon said:
Personally, I think the developer got a kick out of people bricking their phones that way. **** him/her.
Click to expand...
Click to collapse
Talking like that will likely not get you any help here...
Please everyone refrain from posting the rule about searching and reading as this should resolve itself (should the OP actually search and read).
anactoraaron said:
Talking like that will likely not get you any help here...
Please everyone refrain from posting the rule about searching and reading as this should resolve itself (should the OP actually search and read).
Click to expand...
Click to collapse
I've searched through enough threads as it is with a combination of different keywords and all I've found is a bunch of people explaining how to get into download mode or others saying so and so can be fixed as long as you can get into download mode. With the latter, if you can't get into download mode, then what?
Just for the record, I've already tried reflashing it to stock with a .tar file. That failed miserably.
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kind of an improvement as before it would just hang at boot.img but now at least I can get a confirmation of whether it works or not. Currently the phone is still showing the "Firmware upgrade encountered blah blah" crap. But I tried it anyway as I read that it's supposedly a front.
Can't get into stock recovery either. Top left corner says Odin mode. Odd as the JIG puts it into Factory mode. I've uninstalled/installed the Samsung drivers several times. I've changed the USB cable to a Samsung one that I got like a month ago. I have Kies installed. Can't connect the phone to it either. I've tried flashing with Kies not installed and with it installed and shut down/not shut down. Don't think I missed anything else but if I did I'll add it.
crimsondragon said:
Just for the record, I've already tried reflashing it to stock with a .tar file. That failed miserably.
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Kind of an improvement as before it would just hang at boot.img but now at least I can get a confirmation of whether it works or not. Currently the phone is still showing the "Firmware upgrade encountered blah blah" crap. But I tried it anyway as I read that it's supposedly a front.
Can't get into stock recovery either. Top left corner says Odin mode. Odd as the JIG puts it into Factory mode. I've uninstalled/installed the Samsung drivers several times. I've changed the USB cable to a Samsung one that I got like a month ago. I have Kies installed. Can't connect the phone to it either. I've tried flashing with Kies not installed and with it installed and shut down/not shut down. Don't think I missed anything else but if I did I'll add it.
Click to expand...
Click to collapse
I believe that has been discussed also. Pull the battery, re-enter download mode and flash again. When it doesn't complete properly it won't let you Odin again until the battery is pulled.
Just curious but are you on ICS 4.0.4? If so the Odin root is exclusive to gingerbread... Odin cwm and a flash a rom or just Odin back to stock. Root through ICS is obtained by flashing supersu zip through cwm when on ICS.
I realize you are frustrated, but the devs here are awesome and deserve respect, especially since they just brought 4.3 to us.
Sent from my SGH-T769 using xda app-developers app
anactoraaron said:
I believe that has been discussed also. Pull the battery, re-enter download mode and flash again. When it doesn't complete properly it won't let you Odin again until the battery is pulled.
Just curious but are you on ICS 4.0.4? If so the Odin root is exclusive to gingerbread... Odin cwm and a flash a rom or just Odin back to stock. Root through ICS is obtained by flashing supersu zip through cwm when on ICS.
I realize you are frustrated, but the devs here are awesome and deserve respect, especially since they just brought 4.3 to us.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Got it figured out. I was surfing the other subforums and landed on the thread talking about Odin 3.07 and I figured why the hell not. The flash to stock was a success. Then I did the root and CWM Recovery. All is well. 3.07 is much better than 1.85. For the record, I am on GB. Thanks for the help. I apologize for earlier as it was indeed frustrating.
Here's my problem with my Galaxy Tab 2 10.1 GT-P5110.
I never had a problem in almost 3 years until now, but it has been used alot more than normal over the past few months due to ill health. I had used it in the evening with no issues. Next morning it wouldn't turn on. So id pressed the power button for 10 or so seconds and it started to boot. It got to the Galaxy Tab 2 screen and hung and wouldn't boot any further.
After googling I found loads of sites saying you could press the power button along with the volume up button ect to get it to boot or to get you into recovery mode, these didn't work but did take me to the download page. After googling again I found that you can flash the rom ect so I used Odin and the correct firmware file.
It worked, I used it for half hour or so then put it on charge !
After an hour charging I went to use it and it was dead again and wouldn't boot past the Galaxy Tab logo as before. I tried pressing the power and volume buttons again with no luck so as flashing it fixed it before I did the same again.
It didn't work this time, all that is now on screen is a message stating " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" it wont power off but just reboots to that screen.
I tired connecting to Kies but it isn't detected. Ive tried using older versions of Odin with the firmware that work previously and still the same issue. Also tried a different cable, different USB ports and a different PC. Only way it turns off is when the battery dies.
Im not too fused about loosing and data as I can reinstall apps ect but I really don't want to loose my Tab as its my lifeline at the mo as I'm recovering from a spinal injury and spend alot of time laid down. If anyone can help id really appreciate it, thanks in advance
I should add, when i try flashing it again it fails at, NAND Write Start!!
Here's my problem with my Galaxy Tab 2 10.1 GT-P5110.
I recently had the same problem of finding the correct Oden download because I wanted to root and install a different ROM. Factory firmware has to much clutter and junk I will never use. This is what I did and it works. Odin 3 v1.85, CF-Auto Root espresso 10 WiFi, Shakatu recovery clockwork unofficial 6.0.3.1 p5110.tar, and finally downloaded Cyanogen Mod (CM12). Try that Odin version and try again with the factory firmware.
I never had a problem in almost 3 years until now, but it has been used alot more than normal over the past few months due to ill health. I had used it in the evening with no issues. Next morning it wouldn't turn on. So id pressed the power button for 10 or so seconds and it started to boot. It got to the Galaxy Tab 2 screen and hung and wouldn't boot any further.
After googling I found loads of sites saying you could press the power button along with the volume up button ect to get it to boot or to get you into recovery mode, these didn't work but did take me to the download page. After googling again I found that you can flash the rom ect so I used Odin and the correct firmware file.
It worked, I used it for half hour or so then put it on charge !
After an hour charging I went to use it and it was dead again and wouldn't boot past the Galaxy Tab logo as before. I tried pressing the power and volume buttons again with no luck so as flashing it fixed it before I did the same again.
It didn't work this time, all that is now on screen is a message stating " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" it wont power off but just reboots to that screen.
I tired connecting to Kies but it isn't detected. Ive tried using older versions of Odin with the firmware that work previously and still the same issue. Also tried a different cable, different USB ports and a different PC. Only way it turns off is when the battery dies.
Im not too fused about loosing and data as I can reinstall apps ect but I really don't want to loose my Tab as its my lifeline at the mo as I'm recovering from a spinal injury and spend alot of time laid down. If anyone can help id really appreciate it, thanks in advance[/QUOTE]
Ive tried using Odin 3 v1.85 with the same rom that worked for me before, but it fails again, below is the log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDNH2_P5110OXADNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should i be looking at the PIT file and flashing that, if so please could someone help me locate it and advise how i should flash that, thanks
Same probs here
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
mryanmarkryan said:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
Click to expand...
Click to collapse
If you can't even mount it on Windows or get into recovery that's not good.
True Dat!
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
mryanmarkryan said:
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
Click to expand...
Click to collapse
I would suggest pushing the root kernel to it anyway just to see if it will go.. I do have an FRPbypass but it's an apk meaning you need to install it and if you cannot mount to push it and then try to do adb shell pm install FRPbypass.apk then there's no point in that either.. Can you even get into download mode? If not the last thing I could suggest is the PIT file to repartition it. Unless someone else has a better idea? I do have the PIT file for odin too.
Also I think you're past the point of losing your data and if you can hold the volume down button and power button at the same time until it shuts off and turns back on again you can select factory reset and that's going to ruin all data..
My god, this happened to me on my first Note 5 I had. I was trying to restore it to stock before selling it and like an asshole I forgot to check for "OEM Unlock" and ran into that exact message. It put the fear of god into me. Like you I didn't have the serial number written down and I couldn't get it from anywhere. T-Mobile tech reps tried to tell me the IMEI number acts as a serial number, cool, that doesn't help me. I gave up on Kies and just played around with Odin after I was FINALLY able to find a stock firmware. I can't believe how difficult that was to get. I managed to flash the stock firmware thru Odin and I got the phone back! Stock as it came out the box.
I can't remember how I was able to get it into download mode but whatever button order I kept trying I finally did because Odin recognized the mofo and I flashed that stock firmware as fast as I could. It rebooted and I saw that beautiful stock welcome screen once more. Try to do this, I didn't need to do anything else.
For this reason I now keep a copy of stock firmware along with screen shot of my phone's status screen showing the serial number and everything else. All that's backed up to one of my external drives. Alone with several nandroid backups of various stages of owning this second Note 5 I have now. I'm running V10 of Darthstalker but I haven't heard of other users running into FRP lock. That would mean something tripped their OEM unlock option but how would that happen without you doing it? Is there something inside the ROM (a bug) that's tripping the option in Developer Options?
Best of luck with this, I know how stressful this can be. As far as getting your data back, yeah that's likely a no go. At this point you should be hopeful of getting a working phone back, let alone recover any personal data. Hope you can sort this.
More Info
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Yeah if you can get it into download mode and you've got the stock firmware you should be good to go and flash tru Odin. That's key. If I were you I'd be like, "To hell with my personal data! Get me a working phone back!".
Good luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
MrMike2182 said:
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
Click to expand...
Click to collapse
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
Try downloading the newest odin version sometimes that can help.. Can you tell me how it's failing? Like what exactly happens when you try to do all the flashing? Did you try the adb commands that I suggested? You only need to install minimal adb and Fastboot on the windows pc and then connect your device and then open a terminal in the same exact folder where adb and Fastboot were installed and then type Fastboot devices or adb devices if it give you a bunch of numbers it means that it can see the device and we can then manually push and install the firmware. The other thing I suggest you try to do is flash the Lollipop 5.1 T-mobile firmware because I think it doesn't have frp on it yet and before flashing it go into the actual firmware you downloaded and delete cm.bin then rezip the firmware again and flash that one without the cm.bin but first try flashing the entire firmware as is with the md5 and all before resorting to deleting cm.bin.. Don't try flashing the Marshmallow 6 rom because that's where they started that frp bullcrap if you ask me. FRP stands for Factory Reset Protection... I understand the need for it and it's importance but Google could have been a lot more open about it and explaining to its customers what it's for and what it does not just do it and let most of us learn the hard way!!
When you try to flash in Odin tell me what file it fails on.
If none of this works this page is your last bet buddy
https://www.sammobile.com/forum/showthread.php?t=31136
I'm working on it now! Give you guys a summary of what happened as I as check off your suggestions..
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Progress!
mryanmarkryan said:
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Click to expand...
Click to collapse
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Advice?
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
mryanmarkryan said:
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
It stopped right while trying to flash the recovery part of it so here's what I suggest you try to do.. unzip the 5.1.1 firmware you downloaded and unzip it again until you can see all the files in it and then manually flash them 1 by 1 in the AP slot but don't allow the phone to auto reboot uncheck that option and after 1 files flashed hold the volume down button and power button until you can select shut down device or turn off whichever then again hold the buttons to get into download mode again and continue until they are all flashed and then finally again hold the volume down button and power button and when it comes back on then select factory reset.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
E-POUND said:
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
Click to expand...
Click to collapse
If he flashes the latest firmware with the security updates he can never go back to 5.1.1 so I don't suggest he do that yet
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
mryanmarkryan said:
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
Click to expand...
Click to collapse
You're not rooted at all right now but you should not have needed to turn the imgs back into md5s again you should have just flashed them the way they were they don't need md5 just to flash. Try holding the volume down button and power button until it shuts off and turns back on again then select factory reset if that doesn't work then go into download mode again and connect to a Windows pc and use Smart Switch to try and fix it.
The reason I converted them was because Odin wouldn't find the files.. I tried just running them by typing a *.img but it didn't work. I'll go read about smart switch.. I"m learning stuff here
Update,: On a hunch I went back and ran the firmware install again, but just in it's original format. It succeeded and I'm setting up the phone now.. Thanks for your help MrMike. I appreciate you putting the time in..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
You are using the wrong stock firmware. Download the DPG1 firmware since that is was darthstalker v.11 is on. If you backed up your ROM then you don't have any troubles at all. Just ODIN back to stock, root, twrp recovery data only and done. But not all at once. First get the firmware going and reboot your phone. Once you know it's working the try rooting. Once you are rooted download TWRP and recover your data only.
Btw - FRP is when you log into your google account in the beginning of the setup so don't do that if you want to flash other ROMs.
P.S. I'be been running Darthstalker v.11 since it came out with no problems.
I did a factory reset, clicked "Start", connected to a wi-fi network, agreed to the terms, etc... and then the phone got stuck in the "Checking network. Adding a few finishing touches. This may take a minute or two" phase. I waited hours, but it would always get stuck at that part, so I skipped connecting to a wi-fi network.
That helped, and got me further through the initial setup phase, but now, and no matter what I do, it'll just get to a point where it tells me "Not signed in. To use this phone you first have to sign in to an owner's Google account in use on this phone when it was last reset. Because you haven't done so, you have to set up the phone again".
The ****ed up part is that, during the setup stages that precede this message, I'm not asked to sign in to Google. I've tried doing a multitude of things but I cannot get past that.
I can't even go back through the recovery menu, now, as doing the power+volume+home button combination just starts the phone normally.
How did this happen and how do I fix it?
Bumping.
Bumping
Sounds like you need to do factory reset. I take it you've tried holding power+home+volume up while phone is off and keep it held down until recovery appears?
Alright, it just got more frustrating.
I tried doing the button combo to get to the recovery menu, but every time I'd try that it would just start the phone normally. Now, for some reason, it did get me to the recovery menu, so I did a Factory reset once again, and wiped the cache.
But the issue is STILL there. Same thing. It got stuck in "Checking Network", so I went with not having the wi-fi activated, I went through the menus, etc... I even set up a pin and a fingerprint, but right after the window where you select weather stuff and location stuff, I get the exact same error message: "Not signed in. To use this phone you first have to sign in to an owner's Google account in use on this phone when it was last reset. Because you haven't done so, you have to set up the phone again."
Why on earth is this happening??? Why would it even mention google accounts that were in use before the phone was reset IF I'VE WIPED ALL THE DATA??? Shouldn't it start fresh? Like, zero, nada?
When I purchased my phone the initial setup didn't have that message. What gives? I mean, I had rooted my phone before doing a factory reset, but that has nothing to do with this issue, right?
Can anyone help?
Please, can anyone help? What do I do? What solutions are there? I saw some dude with the same issue on a forum somewhere, and he said that he went to settings > apps > Google play services and enabled all permissions, but I can't even access the settings in the first place, since the phone's in the initial setup.
What can I do? Do I flash some sort of custom firmware into it or something? There's gotta be something... How on earth is this error not talked about more? Is it a rare thing? I never knew **** like this could happen. Just what is going on?
Please.
Anyone?
I tried flashing the S6's default firmware through Odin onto my S6 yesterday, but right after select the .md5 file and then click "Start" in Odin's interface, it'll run for a few seconds, but then "Failed" comes up at the top.
What specific firmware can fix this?
Just tried it again, and this time it took a bit longer before failing but it still failed. Here's the log in Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the phone's download mode screen I can see something in red saying: [CM] SW REV. CHECK FAIL. DEVICE: 5, BINARY: 3
What does that mean?
I would stick to odin part
be very careful
put your phone right under the usb port when flashing since it can lose connection very easly
use odin 3 07
i think flashing rom is the only thing that could help you here
(or maybe custom recovery flash over odin then wipe and try other rom)
SOLVED
??
Crystalline3 said:
SOLVED
Click to expand...
Click to collapse
Please tell me how you did this. I am also having this issue with more than 1 device...please help.
hung in checking network
This just happened to me. I had to do a factory reset, and it just kept hanging on setup. Eventually, I just powered it down and turned it back on a few minutes later. And then the setup magically proceeded normally.
Hello, i have recenently tried to root my samsung s8 (did not know it was a stupid idea at that time) after i succeeded i wanted to start installing some roms
So i went and booted TWRP installed the roms, but my phone wouldn't boot anymore.
So i reinstalled the original OS through Odin, and my phone was back and working again , but being the stupid idiot I am, I tried to root it, again only this time without succes.
The phone is stuck on the device info (the samsung text with "Samsung Galaxy S8+" and "powered by android") and wont boot further or into android
When i try to once again reinstall the original OS with Odin it gives me the following error msg:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I can't boot into recovery mode on my phone either, just download mode nothing else.
i've treid booting recovery mode on my phone from my pc but when i use "adb devices" it won't detect the device (while in download mode) I'm not sure if it should detect it as I am in download mode, it does however detect the device in device manager, maybe USB debugging is disabled as i installed a fresh copy of android, I however only have a year of android experience so I really don't know if adb should even be possible from download mode.
Anyhow after 3 days of internet troubleshooting, I'm really running out of options.
Hope someone can point me in the right direction.
FluitGeluid said:
Hello, i have recenently tried to root my samsung s8 (did not know it was a stupid idea at that time) after i succeeded i wanted to start installing some roms
So i went and booted TWRP installed the roms, but my phone wouldn't boot anymore.
So i reinstalled the original OS through Odin, and my phone was back and working again , but being the stupid idiot I am, I tried to root it, again only this time without succes.
The phone is stuck on the device info (the samsung text with "Samsung Galaxy S8+" and "powered by android") and wont boot further or into android
When i try to once again reinstall the original OS with Odin it gives me the following error msg:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I can't boot into recovery mode on my phone either, just download mode nothing else.
i've treid booting recovery mode on my phone from my pc but when i use "adb devices" it won't detect the device (while in download mode) I'm not sure if it should detect it as I am in download mode, it does however detect the device in device manager, maybe USB debugging is disabled as i installed a fresh copy of android, I however only have a year of android experience so I really don't know if adb should even be possible from download mode.
Anyhow after 3 days of internet troubleshooting, I'm really running out of options.
Hope someone can point me in the right direction.
Click to expand...
Click to collapse
There is a S8+ forum, you'll likely get more assistance from there.
I'm getting the same problem one by one. please help
Critical Detox said:
There is a S8+ forum, you'll likely get more assistance from there.
Click to expand...
Click to collapse
when device reboots on its own after failed error press bixby vol down and power button. let it boot into download mode again now flash rom or whater ever. it would work on 2nd attempt.
rehanraza said:
when device reboots on its own after failed error press bixby vol down and power button. let it boot into download mode again now flash rom or whater ever. it would work on 2nd attempt.
Click to expand...
Click to collapse
I have tried that also, but keep getting the error above
same problem here. i had stock dbt tw rom. root with magisk. then i wanted to flash new BL and modem from new dbt fw update. after this i only got working DL mode left. couldnt flash back to another fw no matter which source i tried. btu too. i also got the same error as described above. after whole night of odin flashing trys, for myself i thought sth of internal memory chip is broken so i ordered a new phone. but now i see the second thread describing my problems maybe i was wrong with my thoughts
I fixed it!
With the help of Nameless i managed to fix my problem, here is his post regarding this issue: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
I see other people are experiencing this issue as well, hope this helps!
here is the AQF7 bootloader I used: https://www.androidfilehost.com/?fid=889764386195911671,
For a full flash of the AQF7 version, I recommend you to use this website: http://updato.com/firmware-archive-select-model
Fill in the model of your S8 or S8+ select your country then look for the one that ends with XXU1AQF7 under the tab PDA
Best of luck!
FluitGeluid said:
With the help of Nameless i managed to fix my problem, here is his post regarding this issue: https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
I see other people are experiencing this issue as well, hope this helps!
here is the AQF7 bootloader I used: https://www.androidfilehost.com/?fid=889764386195911671,
For a full flash of the AQF7 version, I recommend you to use this website: http://updato.com/firmware-archive-select-model
Fill in the model of your S8 or S8+ select your country then look for the one that ends with XXU1AQF7 under the tab PDA
Best of luck!
Click to expand...
Click to collapse
Worked like a charm thanks FluitGeluid....
You save me :angel: