When I tried to root the phone earlier, it quit the odin transfer in the middle of the Cache write, and then rebooted to the soft-brick screen
of "Firmware Upgrade encountered an error, please select recovery mode in Kies"
At the bottom, in bright yellow letters on that screen it said "Set warranty bit: Cache"
Basically, the phone was soft-bricked, so I used Kies to put stock 4.3 back on the phone, but now that stock is on it again, whenever the
screen times out, I have to reboot to get the screen to turn on. And on top of it all, Knox wasn't triggered, neither was the Device status,
but it says that the binary status is modified. I'm honestly stumped as to what to do, guys.
That screen will still work in Odin
{
"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"
}
Download the .tar use a different sub cable and Sun port
sent from my ??????? note 3?
deeznutz1977 said:
That screen will still work in Odin
Download the .tar use a different sub cable and Sun port
sent from my ??????? note 3?
Click to expand...
Click to collapse
Will it trip Knox if I use Odin? And it's on stock currently via Kies, it just doesn't turn the screen back on if it's been locked for a few minutes
THANK YOU SO MUCH FOR THE PROMPT REPLY! I really do appreciate your help!
Daltonyx said:
Will it trip Knox if I use Odin? And it's on stock currently via Kies, it just doesn't turn the screen back on if it's been locked for a few minutes
THANK YOU SO MUCH FOR THE PROMPT REPLY! I really do appreciate your help!
Click to expand...
Click to collapse
No it won't trip knox
sent from my ??????? note 3?
Related
Hi guys, could use some help with my situation.
This is what happens when I boot up the N7105.
{
"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"
}
I was able to access the download mode however when I tried to flash philz recovery via Odin, it failed.
The error message is below.
As I am able to see the product name, I guess it is not the SDS issue that has been circulating.
Would appreciate any help from you guys.
Thanks a lot!
What bootloader are you on?
(What does it say whe you're in DL mode)
If you have Knox you cant just flash anything you like, you'll have to flash 4.3 stock rom with knox and follow instructions of how to disable knox and downgrade.
If not on knox bootloader DL a 4.1.2 rom and flash it through odin
(Your OS and Odin versions can sometimes cause the PIT not found issue)
Which odin should i use to flash 4.1.2? And how do I check if my friend's phone has knox?
Anywhere i can get a 4.1.2 stock? Cannot find it on Sammobile for Singapore's version.
Nope did not work. Tried flashing 4.3 stock failed. Tried with PIT, failed too. All attempts failed at unable to Repartition.
Note 2 unable to boot up
Hi, so what u did to get the phone back on service? My aunt's note 2 give the same white screen like the top pic.
bladez87 said:
Nope did not work. Tried flashing 4.3 stock failed. Tried with PIT, failed too. All attempts failed at unable to Repartition.
Click to expand...
Click to collapse
Like my title says I have a i317 Note II on AT&T. It was bricked a while back I tried factory reset which sent it into a boot loop until the battery drained now it is just a brick and wont start but past the Samsung logo.
I ran Odin v3.09 with a Pass but the phone is still doing the same thing. Not sure where to go after this. Do I need to run a new bootloader file? Any help would be great.
These are the files I ran with it:
i317.pit
I317-UCUBMK6.tar.md5
{
"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"
}
verapakill said:
Like my title says I have a i317 Note II on AT&T. It was bricked a while back I tried factory reset which sent it into a boot loop until the battery drained now it is just a brick and wont start but past the Samsung logo.
I ran Odin v3.09 with a Pass but the phone is still doing the same thing. Not sure where to go after this. Do I need to run a new bootloader file? Any help would be great.
These are the files I ran with it:
i317.pit
I317-UCUBMK6.tar.md5
View attachment 3062723
Click to expand...
Click to collapse
Is the phone still turning on? If so maybe try booting into recovery first and wiping all data before flashing stock rom again with odin?
I tried that. I have been able to get the phone to boot but as soon as it restarts it goes right back into a bootloop. Try wiping again and restarting with the same results. Stuck in a boot loop on the first Samsung screen.
Like my title says I have a i317 Note II on AT&T. It was bricked a while back I tried factory reset which sent it into a boot loop until the battery drained now it is just a brick and wont start but past the Samsung logo.
I ran Odin v3.09 with a Pass but the phone is still doing the same thing. Not sure where to go after this. Do I need to run a new bootloader file? Any help would be great.
These are the files I ran with it:
i317.pit
I317-UCUBMK6.tar.md5
{
"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"
}
Did you try using Odin 3.07? Not sure if it will make a difference but I have always had good luck with Odin 3.07.
Try flashing again but do not check auto reboot, only check F.reset time. Flash the ROM. When you see Reset in the status window, disconnect the USB cable, pull the battery, wait about 10 seconds, replace the battery, boot into recovery, do a factory wipe, and reboot.
verapakill said:
Like my title says I have a i317 Note II on AT&T. It was bricked a while back I tried factory reset which sent it into a boot loop until the battery drained now it is just a brick and wont start but past the Samsung logo.
I ran Odin v3.09 with a Pass but the phone is still doing the same thing. Not sure where to go after this. Do I need to run a new bootloader file? Any help would be great.
These are the files I ran with it:
i317.pit
I317-UCUBMK6.tar.md5
View attachment 3062724
Click to expand...
Click to collapse
Are you working ??
This should help. You already did part #1
http://forum.xda-developers.com/show....php?t=2618447
Flash recovery if phone won't boot to recovery
Tapatalked from my PACMAN 4.4.4 Note II
I have my cousin's phone right here - just yesterday he tried to update to Lollipop. He was on stock TouchWiz, no root or anything of the sort and installed the update.
Now, if I try to turn on the phone, all I get is this screen and it just stays there forever:
{
"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"
}
If I try to boot into the bootloader, all I get is this: https://goo.gl/photos/WBSAcHhALQ9Jmz2n9
I really don't know what I would do here - can you do anything once your bootloader is f*ed up?
If it helps, the phone's model is SM-N7505
Yes, the same issue happened with me today on Note3 Neo. I rebooted the phone and it stuck on the same place. Checked in local phone repairing shop unable to make hard reset. They are suspecting of hardware issue. What could be the coz of this?
vadsvads said:
I have my cousin's phone right here - just yesterday he tried to update to Lollipop. He was on stock TouchWiz, no root or anything of the sort and installed the update.
Now, if I try to turn on the phone, all I get is this screen and it just stays there forever:
If I try to boot into the bootloader, all I get is this: https://goo.gl/photos/WBSAcHhALQ9Jmz2n9
I really don't know what I would do here - can you do anything once your bootloader is f*ed up?
If it helps, the phone's model is SM-N7505
Click to expand...
Click to collapse
Try flashing the rom using odin
ismaadu78 said:
Try flashing the rom using odin
Click to expand...
Click to collapse
How would I do that without being able to access the bootloader? I haven't done much with Samsung devices yet, only with my HTC phones. I've heard of the name ODIN though... Are there any tutorials you can recommend?
You don't need bootloader to flash stock rom via Odin, you only need to access Download mode (vol. down+home+lock). You can look up tutorials on YT. Just type "How to flash stock Samsung rom using Odin". Hope that helps somehow
Hello together
I tried to root my Samsung Galaxy Tab S4 according to https://appuals.com/how-to-root-the-samsung-galaxy-tab-s4/
There I came up to step 10 (so I flashed the two files). Now the Tablet is kind of stuck in the boot screen showing this (the same for step 8 and 10 but at step 10 i lost the ability to get to the download mode):
{
"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"
}
The only thing possible is to gamble a bit with the keys power, volume up and down to get the yellow sign in the top left showing "kernel" instead of "recovery". Otherwise if I press all three buttons together the following screen comes:
I am a complete noob in that kind of things and got no idea what to do now. There is no possibility to open the download mode to revert something, neither TWRP is shown as it should according to the Description in Link above. If possible I dont want to get anything deleted. What can I do?
EDIT: If possible I still want to root the tablet because I only see advantages in it, even I never found a good (explanatory) tutorial on it.
kind regards
alhuwile
Ok as I was very impatient and tried a bit, the blue screen is actually the "ODIN Download Mode". I reinstalled the stock firmware (loosing all data) (and rooted the device with Magisk later on) so the sm-t830 works perfectly again.
alhuwile said:
Ok as I was very impatient and tried a bit, the blue screen is actually the "ODIN Download Mode". I reinstalled the stock firmware (loosing all data) (and rooted the device with Magisk later on) so the sm-t830 works perfectly again.
Click to expand...
Click to collapse
Which guide did you follow and what firmware are you using?