Related
I had my at&t s4 rooted last night, i delete a lot of bloat on reqbull's list...my mms wasnt working next morning, did a factory reset..now at the setup screen & after the last screen (the one where i name the device) a popup comes saying settings has stopped, and takes me back to the setup screen. how can i get around this? i am on mac by the way..
Have to Odin the firmware back in
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Dallenn said:
I had my at&t s4 rooted last night, i delete a lot of bloat on reqbull's list...my mms wasnt working next morning, did a factory reset..now at the setup screen & after the last screen (the one where i name the device) a popup comes saying settings has stopped, and takes me back to the setup screen. how can i get around this? i am on mac by the way..
Click to expand...
Click to collapse
You'll need to ruu back to complete stock to fix your issue it's the only fix
Sent from my One V
i dont mind having to go back to stock, but is there anyway i can do it from my mac?
Dallenn said:
i dont mind having to go back to stock, but is there anyway i can do it from my mac?
Click to expand...
Click to collapse
Might be a more elegant way of doing this, but maybe try dual booting windows? Or google search heimdall which is a mac Odin equivalent. I'm not sure if the stock firmware works with it or not. You should definitely confirm that before attempting to use heimdall.
lessthanzach said:
Might be a more elegant way of doing this, but maybe try dual booting windows? Or google search heimdall which is a mac Odin equivalent. I'm not sure if the stock firmware works with it or not. You should definitely confirm that before attempting to use heimdall.
Click to expand...
Click to collapse
He's right, try to dual boot windows or ask a buddy to let you use their pc for now just download your ruu and load onto a flashdrive so it can be ready
Sent from my One V
Obeezy562 said:
He's right, try to dual boot windows or ask a buddy to let you use their pc for now just download your ruu and load onto a flashdrive so it can be ready
Sent from my One V
Click to expand...
Click to collapse
Samsung does not have RUU files thats HTC...
i have the stock firmware file from the (return to stock) odin method...
Dallenn said:
i have the stock firmware file from the (return to stock) odin method...
Click to expand...
Click to collapse
Cool. SO now either try heimdall for mac http://www.glassechidna.com.au/products/heimdall/, using a friends computer, or dual booting windows to use the appropriate odin method.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
i have heimdall but am unsure how to load the zip into it to flash
Dallenn said:
i have heimdall but am unsure how to load the zip into it to flash
Click to expand...
Click to collapse
I fairly certain heimdall is not confirmed to work with our stock rom yet. I would highly advise against it if at all possible, try to borrow a pc to do it via odin.
TwistedMexi said:
I fairly certain heimdall is not confirmed to work with our stock rom yet. I would highly advise against it if at all possible, try to borrow a pc to do it via odin.
Click to expand...
Click to collapse
prob what im gonna do, sucks cause i downlaoded the huge firmware from samsung that took forever..maybe can just file share it from mac to pc..
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
tr10 said:
Hello,
I've been reading as much regarding this issue before I've posted this thread. Please don't attack me because of my lack of knowledge, I'm trying. Thanks.
I recently rooted and installed a custom rom on my SGH-I337, Slimrom was the name of the rom. It worked perfectly, until I decided to upgrade the rom version. I downloaded the update on my phone, rebooted to recovery and flashed the zip. Rebooted my phone, and I'm stuck in a boot loop. No Logo, No recovery, I do have download mode.
I had read that odin flashing the stock rom would fix my issue, so I had done that. I flashed I337UCUAMDL_I337ATTAMDL_ATT successfully. Odin auto-rebooted....to a boot loop. No recovery, No image on my screen while charging, etc.
I had also read that odin flashing TWRP might fix the soft brick I'm experiencing, I downloaded the latest .img from TWRP and converted it to a tar using Cygwin. Attempted to flash it to have Odin tell me it failed.
Does anyone have any idea's or advice how I could get back to a working environment recovery?
Thank you for your time reading this.
Click to expand...
Click to collapse
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
xBeerdroiDx said:
when you flashed the rom update, did you do any sort of wipe as well?
when you flash the stock firmware via odin, you have to boot into the stock recovery afterwards and wipe data/factory reset to complete the process or you will be unable to continue. you may want to try that process again.
Click to expand...
Click to collapse
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
tr10 said:
Thank you for the speedy response.
When I originally flashed the rom update, I did NOT wipe anything.
When I flashed stock firmware, I could not get into stock recovery via three buttons.
Thank you.
Click to expand...
Click to collapse
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Pull the battery, put it back in and try recovery again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the advice, I have done that countless times. I'm hoping that it changes one of these times though.
I took your advice regarding re-flashing the image and ticking the bootloader update option, odin stated it was successful and auto-rebooted. I pulled the battery and tried to enter recovery, no cigar.
Perhaps try the Heimdall route: http://forum.xda-developers.com/showthread.php?t=2374441
When attempting to flash TWRP recovery, my phone says in the top right hand corner:
Odin Mode
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
CSB-OEM_CONFIG_LSB: 0x30
WRITE PROTECTION: Enabled
START [224, 1440]
SECURE CHECK FAIL: recovery
Don't know what that means.
I haven't tried the heimdall method yet, not sure if I wanna give it a shot because it seems a lot more complex only to accomplish the same thing odin would. I can imagine something is stopping odin from putting a bootloader, or kernel. That same thing would stop heimdall. But, I have no idea what I'm talking about. Waiting to hear more advice before I make the hole I dug deeper.
Thank you for your time guys.
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Febby said:
Try flashing the loki patched recovery from this thread. Link is in OP.
http://forum.xda-developers.com/showthread.php?t=2322682
Just extract the img and make it a odin file.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
xBeerdroiDx said:
After flashing stock via Odin, when you use the 3 button combo to access recovery, are you releasing just the power button when the device vibrates?
Click to expand...
Click to collapse
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
tr10 said:
Thank you for the advice Febby, I have downloaded the file you suggested. This was actually the first recovery I had when I had tried to update my rom version. I converted it successfully to a tar and attempted to odin it over to my phone. I'm receiving the same error I had earlier, Secure Check Fail: Recovery.
Thank you for the suggestion though, as I think this is in the right direction of what I need to do, I don't know how to get past that secure check though.
Correct, I am.
I am receiving absolutely no image on my screen other than when I enter Download mode.
Thank you for the suggestion.
Click to expand...
Click to collapse
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Febby said:
damn im sorry it didn't work. Samsung is just making this device more and more unpleasant to own. I actually considered switching to a ONE today.
You can always try exchanging it via att warranty (free).
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Aou said:
Indeed the "easiest" way to correct this would be via a warranty claim... but would take a couple days.
Otherwise, when you said "updated the ROM" ... How did you go about updating it? I assume you downloaded a .zip from the forums here, and installed it through recovery. But if you somehow, by some miracle, managed to download the MF3 update OTA... that would explain many things.
Also, there's an MDL recovery located over in this post. It's odin-flashable, and works on my device pretty well. Maybe it will get you back to at least having a recovery?
Also, Odin will reject the installation of TWRP like that. Tried it myself once.
Click to expand...
Click to collapse
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Febby said:
I actually considered switching to a ONE today.
Click to expand...
Click to collapse
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
Either way. Also, if one fails, try the other of course.
Te3k said:
What I did is just google around for my stock kernel, which came in a .TAR file, and was immediately Odin-flashable. That might be even easier.
Click to expand...
Click to collapse
I converted the .img to a .tar and I sadly had the same results =( Thank you for the idea though, definitely helped.
Aou said:
Does kinda sound like a kernel problem, I think... Might try just flashing to Kernel to see if it gets any further. You could do that via Heimdall (if you have it setup), or by modifying a copy of the MDL Odin package (e.g. delete everythine but the "boot.img" kernel file, and remove the .md5 extension).
I hope your break is refreshing.
Click to expand...
Click to collapse
Thank you, I attempted to reflash the stock kernel included in the MDL package. No avail. Same problem. Good advice though!
Te3k said:
Hey, don't despair! Last time I was here I used Odin to reflash my stock firmware, and also the stock kernel. Did you try reflashing the stock kernel yet? That got me right out of it.
Strange that you can't get into any sort of recovery menu.
Click to expand...
Click to collapse
I just reflashed the stock kernel, no cigar =( It is very strange to me that I can't get the phone to respond to anything other than download mode. Especially considering that I odin'd to stock. I'm starting to think I made it worse by going back to stock after flashing slimbean's weekly update.
Thank you for your time guys, keep the ideas coming, I'm definitely trying to come up with my own ideas.
I have so far done the following:
Odin'd MDL, MDB, Stock Kernel, Stock Recovery (All through download mode, as I don't have access to recovery.)
I've also tried to odin TWRP but I fail in Odin since download mode blocks the illegal recovery.
Thank you again for your time.
tr10 said:
No no, no need to apologize, I have been looking in the ONE as well haha, but I'm already looped into two years, so its probably not going to happen. I have a tiny cracked screen so they won't allow me to exchange it. =( Thank you for your ideas though!
Correct, I did update my rom via a zip file, I'm pretty sure it wasn't a MF3 update as I am familiar with the problems that's been causing.
http://www.slimroms.net/index.php/d...mo/3774-slim-d2att-4-2-2-build-7-5-weekly-596
That would be the link to the exact download I tried to update too.
I'll give that a shot with your link and let you know.
Thanks again guys.
EDIT: Tried the MDL Recovery, No Cigar. Though that thread is pretty interesting, gonna give it a read when I have the time. I need to get out of the house, this problem is driving me bonkers. Thank you guys very much for your advice and support, I would have went crazy hours ago if it wasn't for the intelligence provided by this forum.
Click to expand...
Click to collapse
Im not so sure how everyone just over looked this but the rom in that link is for the att S3. So you flashed an S3 rom to your S4.
D2att is the s3 for att.
Jflteatt is the att variant.
http://www.slimroms.net/index.php/downloads/all/viewcategory/620-jflteatt
Thats the correct link to weekly roms for slim rom for our device. your partitions might just be corrupted in case maybe having a jtag or using the pit file for MDL would fix? :/ im not an expert haha just observations.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
---------- Post added at 06:01 PM ---------- Previous post was at 05:57 PM ----------
xBeerdroiDx said:
that would be the worst mistake of your life. my wife has a One. stock, its like an iphone. rooted, there isnt 10% of the activity/development in the One boards that there are here so that makes life with a rooted htc device even more boring than a regular day with an htc device.
Click to expand...
Click to collapse
You sure? On the att one majority of devs dont post on the att htc one section but eather "HtC one" section since all roms work vice versa on that phone international roms > works on all models of the one.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I accidentally bricked my phone. All was well, Rooted, Cyanogenmod 10, twrp through goomanager. But when i tried to Flash a ktoonsez kernel for this device 4.2.2 aosp, it said failed and would not boot back up. All i can get is to the "Downloading... Do not turn off target!!" screen. Basically im screwed anybody know how to unbrick her? shes only a day old. ;(
Odin the stock firmware.
old tylivequ
jd1639 said:
Odin the stock firmware.[/QUOTE
Do you have a link to jflteatt odin? All i can find is the ecan version? Im sorry but im kind of a noobie.
Click to expand...
Click to collapse
2 questions: you're certain you can't boot into recovery? Can you tell me any specifics about the kernel (name/date/etc)?
hayden55 said:
jd1639 said:
Odin the stock firmware.[/QUOTE
Do you have a link to jflteatt odin? All i can find is the ecan version? Im sorry but im kind of a noobie.
Click to expand...
Click to collapse
Go to sammobile.com. you can find stock firmware there. You have to register but it's free. You'll download a zip file, use 7-zip to extract the .tar.md5 file from it. Use that in Odin.
Click to expand...
Click to collapse
xBeerdroiDx said:
2 questions: you're certain you can't boot into recovery? Can you tell me any specifics about the kernel (name/date/etc)?
Click to expand...
Click to collapse
ktoonsez kt747. AOSP JELLYBEAN 4.2 Linux 3.4 VERSIONS from the att version galaxy s4 forum. I checked and i was running 3.4 linux and cyanogenmod. Its the most recent as i downloaded an hour ago. Also, i had twrp 2.6 through goo manager. Cannot get to boot to it. Anything but the android download screen all i get is a little haptic feedback and a black screen
jd1639 said:
hayden55 said:
Go to sammobile.com. you can find stock firmware there. You have to register but it's free. You'll download a zip file, use 7-zip to extract the .tar.md5 file from it. Use that in Odin.
Click to expand...
Click to collapse
Which would i be? ucuamdb or ucuamdl? And i can flash this with the odin for canada only? Where is the odin for usa att?
Click to expand...
Click to collapse
hayden55 said:
jd1639 said:
Which would i be? ucuamdb or ucuamdl? And i can flash this with the odin for canada only? Where is the odin for usa att?
Click to expand...
Click to collapse
*correction. I found odin3
Click to expand...
Click to collapse
hayden55 said:
jd1639 said:
Which would i be? ucuamdb or ucuamdl? And i can flash this with the odin for canada only? Where is the odin for usa att?
Click to expand...
Click to collapse
Use mdl. Odin is a separate program and is not us or Canada. Read this guide and use the tar.md5 for your device http://forum.xda-developers.com/showthread.php?p=26056924
Take your time and read the guide more than once. You can permanently brick your device.
Click to expand...
Click to collapse
jd1639 said:
hayden55 said:
Use mdl. Odin is a separate program and is not us or Canada. Read this guide and use the tar.md5 for your device http://forum.xda-developers.com/showthread.php?p=26056924
Take your time and read the guide more than once. You can permanently brick your device.
Click to expand...
Click to collapse
hey thanks for all the help guys! Nice forum. I always read through but have never joined until now. In an hour from now i will have the download Hopefully...
Click to expand...
Click to collapse
hayden55 said:
jd1639 said:
hey thanks for all the help guys! Nice forum. I always read through but have never joined until now. In an hour from now i will have the download Hopefully...
Click to expand...
Click to collapse
When you use Odin, let it do its thing. It'll take 10 to 20 minutes. Don't panic in the middle and unplug the usb. Be patient. And make sure you use the file you're downloading from sammobile. Don't use any of the links in the guide, except Odin. The other files are not for your device and they will brick you.
Click to expand...
Click to collapse
culating humpSno
jd1639 said:
hayden55 said:
When you use Odin, let it do its thing. It'll take 10 to 20 minutes. Don't panic in the middle and unplug the usb. Be patient. And make sure you use the file you're downloading from sammobile. Don't use any of the links in the guide, except Odin. The other files are not for your device and they will brick you.
Click to expand...
Click to collapse
yeah. I read through the GS2 guide and noted some of the similar stuff for when i do mine
Click to expand...
Click to collapse
jd1639 said:
hayden55 said:
When you use Odin, let it do its thing. It'll take 10 to 20 minutes. Don't panic in the middle and unplug the usb. Be patient. And make sure you use the file you're downloading from sammobile. Don't use any of the links in the guide, except Odin. The other files are not for your device and they will brick you.
Click to expand...
Click to collapse
I downloaded the file and flashed it with odin. It said passed and the screen had finished the download, but whenever i try and boot the phone i still dont have a boot. Only a black screen with a little vibration every 5~10 seconds? PLEASE... i need help now. I dont need to hear a "I told you so" from my dad. he is anti-root
Click to expand...
Click to collapse
hayden55 said:
jd1639 said:
I downloaded the file and flashed it with odin. It said passed and the screen had finished the download, but whenever i try and boot the phone i still dont have a boot. Only a black screen with a little vibration every 5~10 seconds? PLEASE... i need help now. I dont need to hear a "I told you so" from my dad. he is anti-root
Click to expand...
Click to collapse
Did you have "repartition" checked in ODIN? Because if you did, you shouldn't have.
If not, try to get into recovery (if you can) and try a factory reset.
Click to expand...
Click to collapse
scott14719 said:
hayden55 said:
Did you have "repartition" checked in ODIN? Because if you did, you shouldn't have.
If not, try to get into recovery (if you can) and try a factory reset.
Click to expand...
Click to collapse
For some reason my recovery wont work? maybe thats it? all i know is my recovery wont boot, and i flashed a bad kernel. I have my twrp backup on my external sd
Also... all i had checked was auto reboot and f. reset time. I flashed the reset file with pda box checked.
forgot to add. i flashed the file with those two boxes checked and it said pass. I think it must be the kernel or the recovery? how do you flash these in odin? I bet if i can track down the stock kernel and get twrp again it may boot.
Click to expand...
Click to collapse
hayden55 said:
scott14719 said:
For some reason my recovery wont work? maybe thats it? all i know is my recovery wont boot, and i flashed a bad kernel. I have my twrp backup on my external sd
Also... all i had checked was auto reboot and f. reset time. I flashed the reset file with pda box checked. How do i flash a new recovery, maybe that would boot it? If i can get into twrp i have my stock rom backed up and maybe the kernel with it.
Click to expand...
Click to collapse
If you are positive you can not get into 3e recovery, you might want to go to the OUDHS CWM thread in the development section and look at the OP for a method to install that recovery via ADB shell. If you can get it installed, you can then flash another ROM to get up and running. Then, if you desire, you can use GooManager to put TWRP back on your phone and restore a working Nandroid you might have. Or you can just set things up from scratch. But all of this is only if you can get into recovery or get a recovery installed back onto your phone.
If you tried to install the wrong Kernel for your phone, you might be hard bricked, in which case Jtag might be your only hope.
Click to expand...
Click to collapse
scott14719 said:
hayden55 said:
If you are positive you can not get into 3e recovery, you might want to go to the OUDHS CWM thread in the development section and look at the OP for a method to install that recovery via ADB shell. If you can get it installed, you can then flash another ROM to get up and running. Then, if you desire, you can use GooManager to put TWRP back on your phone and restore a working Nandroid you might have. Or you can just set things up from scratch. But all of this is only if you can get into recovery or get a recovery installed back onto your phone.
If you tried to install the wrong Kernel for your phone, you might be hard bricked, in which case Jtag might be your only hope.
Click to expand...
Click to collapse
WHAT! I was hoping it wouldnt come to JTAG. I've heard you can make a jig and then just download their software and do it yourself? But yes, I will go to that thread and check it out. also thanks for the help. this forum is MUCH better than others I have used for various products and what not.
Click to expand...
Click to collapse
I hope you get it figured out. But let me tell you what I DID and had the same outcome with NO RECOVERY at all, black screen with vibrate only. So what your describing sounds EXACTLY what happened to mine.
So I was "TRYING" to make a custom splash screen as I had for my SGS3. (Which messed with the kernel). When I went to boot up after the flash it did the black screen with vibrate.
I COULD get into DOWNOIAD mode but not recovery at all. I tried for a few days. I was worried my battery would be getting low after trying for a few hours. I tried to plug it in and the battery came up but it acted like it was stuck and nothing would happen.
Next I tried to use Odin to flash back to MDL stock firmware. It would flash and said completed. But upon reboot same half/vibrate screen.
Next I tried MDB firmware. STILL a NO GO. I had to send it in for JTAG. I think they had some issues getting it working as well. It arrived on a Thursday, and they did not finish getting it to where their site showed it was completed for 8 days. Then it didn't get sent out for another day. It finally arrived at my house 10 days after they received it. But GLADLY they were able to fix it. So good luck to you. If you do have to resort to JTAG it cost me a total of $90, Almost $30 dollars for me to TWO DAY it to them. $60 for JTAG and rush delivery.
Sent from My Spiderman Themed I337
Sorry to hear Odin didn't work. Odin does put the stock recovery on your phone in the correct partition if every thing goes correctly. But if your hard bricked Odin won't recovery the phone.
Try what Scott suggested but it's looking like jtag may be your best option at this point.
jd1639 said:
Sorry to hear Odin didn't work. Odin does put the stock recovery on your phone in the correct partition if every thing goes correctly. But if your hard bricked Odin won't recovery the phone.
Try what Scott suggested but it's looking like jtag may be your best option at this point.
Click to expand...
Click to collapse
hell yeah this phone is hard bricked. But att was cool and let me return for a new one. Really no questions asked as long as you didnt damage it or get it wet. Rip to my first gs4. But the good thing is is that it should only take like 2 days to get a new one, because the first one shipped pretty quick. Thanks for all the help guys
I've been searching around on how to root my device and I thought I had found the right way to do it, but after trying my phone will stay on the boot screen while saying all the recovery stuff. I can also get it into download mode again, but it won't fully start. Can anyone tell me how to get my phone back to stock ROM so that I can just use my phone again? Thanks.
Whicf root u r using? Cfautoroot? Did u use the correct root file for 4.3?
Sent from somewhere under the sky, at the corner of this rounded earth.
antique_sonic said:
Whicf root u r using? Cfautoroot? Did u use the correct root file for 4.3?
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
It was cfautoroot. I thought I was using the right version, but evidently it might not have been. I also used Odin 3.7 instead of 3.9 on accident so I don't know if that changes anything.
So, to sum it all up, you were trying to root your device with your eyes closed ?
It's clearly written on the cfroot site what to use and how to do it.
Sent from my N9005
No... I used the file that it told me to use, and did all the steps. Anyone know how I can fix it?
Could I just do the same process over again with a different file using ODIN or do I need to put the stock back on it again in order to correctly root it? I've been looking at more guides and it seems like I did all the right things, but I guess the .tar file I had may have been old even though I thought it was for my T-Mobile Note 3 using 4.3. Any suggestions because I would prefer to get it right this time, and not mess my phone up anymore than I have.
JollyGreen527 said:
Could I just do the same process over again with a different file using ODIN or do I need to put the stock back on it again in order to correctly root it? I've been looking at more guides and it seems like I did all the right things, but I guess the .tar file I had may have been old even though I thought it was for my T-Mobile Note 3 using 4.3. Any suggestions because I would prefer to get it right this time, and not mess my phone up anymore than I have.
Click to expand...
Click to collapse
Did you try to flash Kit Kat? Therefor you would need the new bootloader as well. I never got a bootloop with just rooting the device and that's been a lot of times. Try to flash stock rom in Odin again (7 or 9 doesn't matter) and then look for the correct file again.
JollyGreen527 said:
Could I just do the same process over again with a different file using ODIN or do I need to put the stock back on it again in order to correctly root it? I've been looking at more guides and it seems like I did all the right things, but I guess the .tar file I had may have been old even though I thought it was for my T-Mobile Note 3 using 4.3. Any suggestions because I would prefer to get it right this time, and not mess my phone up anymore than I have.
Click to expand...
Click to collapse
U better get from someone with tmob who have it earlier. I guess the file there work on 4.4.2. U never mentioned earlier on ur 1st post that u r on tmob.
Or, easier way, upgrade to KK and then root.
Sent from somewhere under the sky, at the corner of this rounded earth.
So would http://stockroms.net/file/GalaxyNote3/SM-N900T/N900TUVUCNB4_N900TTMBCNB4_TMB.zip work? I just put the .tar file into the AP part of Odin 3.09 and start it in download mode, and it should work right? My girlfriend has the exact same phone not rooted also, would I be able to use hers at all to get it back to stock?
Thanks for the help. I was able to flash the stock ROM back on my phone and everything is back to normal. Now all I need to do is find the right file to correctly root it. (Still 4.3)
After trying again, with what I made sure was the right file for 4.3, which was the one I used before, it still won't get past the recovery and boot screen after the root process on ODIN. While looking at the guide it said to uncheck auto reboot if it is not installing then just put it into recovery mode myself and it should work. Should I do that to make it work?
Tried that, and it didn't work also. Not sure how to make it work. I put the .tar file in the AP spot. Do I need a different file in one of the other slots? Thanks.
JollyGreen527 said:
Thanks for the help. I was able to flash the stock ROM back on my phone and everything is back to normal. Now all I need to do is find the right file to correctly root it. (Still 4.3)
After trying again, with what I made sure was the right file for 4.3, which was the one I used before, it still won't get past the recovery and boot screen after the root process on ODIN. While looking at the guide it said to uncheck auto reboot if it is not installing then just put it into recovery mode myself and it should work. Should I do that to make it work?
Tried that, and it didn't work also. Not sure how to make it work. I put the .tar file in the AP spot. Do I need a different file in one of the other slots? Thanks.
Click to expand...
Click to collapse
No you don't need any other file.
Check your reactivation lock make sure it is off, usb debugging is on.
And sometimes, it needs 2 times to flash to success. Don't worry.
The only thing you have to make sure is : the root file you are using to flash, must be for 4.3 JB. Not 4.4.2
I have no idea the one inside CF-autoroot post is for Tmob 4.4.2 or for 4.3
You should find out this one, because if you are using root file for KK on JB, your phone will bootloop (and vice versa).
USB debugging on but still didn't work. Flashed it twice but didn't work. The reactivation lock option isn't showing up in my security so not sure about that one. How big should the file be that I use to root with? I found another guide that shows to use a file that's over a gigabyte big but also using the csc part of ODIN. The file I'm using now from cfautoroot is only about 20 megabytes.
I saw a post that said to use Kingo Root or Vroot but as I've been searching I've heard bad things about Kingo. Is Vroot any good?
Any more help before this gets buried?
JollyGreen527 said:
USB debugging on but still didn't work. Flashed it twice but didn't work. The reactivation lock option isn't showing up in my security so not sure about that one. How big should the file be that I use to root with? I found another guide that shows to use a file that's over a gigabyte big but also using the csc part of ODIN. The file I'm using now from cfautoroot is only about 20 megabytes.
I saw a post that said to use Kingo Root or Vroot but as I've been searching I've heard bad things about Kingo. Is Vroot any good?
Click to expand...
Click to collapse
I have no idea again. Sorry.
If u want to learn, find some other sources of knowledge and try on ur own risk.
But if u just want to get root a.s.a.p, I would suggest u upgrade to 4.4.2 and use cfautoroot. I believe the file posted on cf thread is for 4.4.2.
Good luck
JollyGreen527 said:
Any more help before this gets buried?
Click to expand...
Click to collapse
Sent from somewhere under the sky, at the corner of this rounded earth.
"Root my phone" she says, "It will be great" she says...That is what my girlfriend asked me but now I have her phone bricked and can't get it running again. Have rooted multiple android devices before but this one has stumped me. Tried to get old 4.4.4 OS on it using Odin and now I cannot get any OS on it. Even the original stock OS I cannot get loaded on, which I would happily take.
Things you should know:
-Samsung Galaxy S5 Verizon edition
-Using Odin v 3.10.06
-Using md5 and .tar SM-G900V
-Phone can go into Recovery/Download Mode
-Odin sees phone and recognizes it, but when trying to load on OS it gives error failed.
Ask me for any other info, I would be happy to get it rooted, not rooted, custom ROM, just anything to get it running again.
Thank you very much.
TUTRider said:
"Root my phone" she says, "It will be great" she says...That is what my girlfriend asked me but now I have her phone bricked and can't get it running again. Have rooted multiple android devices before but this one has stumped me. Tried to get old 4.4.4 OS on it using Odin and now I cannot get any OS on it. Even the original stock OS I cannot get loaded on, which I would happily take.
Things you should know:
-Samsung Galaxy S5 Verizon edition
-Using Odin v 3.10.06
-Using md5 and .tar SM-G900V
-Phone can go into Recovery/Download Mode
-Odin sees phone and recognizes it, but when trying to load on OS it gives error failed.
Ask me for any other info, I would be happy to get it rooted, not rooted, custom ROM, just anything to get it running again.
Thank you very much.
Click to expand...
Click to collapse
Which build was the phone running? OG5 and the one before it can't be rooted/downgraded to my knowledge...
I also only stick w odin 3.09...been using it for years with no problems..
roadblock217 said:
Which build was the phone running? OG5 and the one before it can't be rooted/downgraded to my knowledge...
I also only stick w odin 3.09...been using it for years with no problems..
Click to expand...
Click to collapse
it was on 5.0 I believe, and now am using 3.09. Thanks for the info.
Anything else you would recommend?
TUTRider said:
it was on 5.0 I believe, and now am using 3.09. Thanks for the info.
Anything else you would recommend?
Click to expand...
Click to collapse
Need to know exactly which build the phone was on...its in settings
roadblock217 said:
Need to know exactly which build the phone was on...its in settings
Click to expand...
Click to collapse
I do not know, I know that is super unhelpful. But all it can do at this point is go into download mode and recovery mode.
TUTRider said:
I do not know, I know that is super unhelpful. But all it can do at this point is go into download mode and recovery mode.
Click to expand...
Click to collapse
lol no worries. To me, it seems like the phone was on OG5 (latest) or the one before that, which disables going BACK to an older build to be able to root...Are you using ODIN properly (sorry, I have to ask)
ALL files I've flashed go in the AP slot...so try downloading the top file of the two (seeing as it prob. isnt rootable anyway) http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
download, unzip if needed, and try flashing that in the AP slot when in ODIN...see what that does..
roadblock217 said:
lol no worries. To me, it seems like the phone was on OG5 (latest) or the one before that, which disables going BACK to an older build to be able to root...Are you using ODIN properly (sorry, I have to ask)
ALL files I've flashed go in the AP slot...so try downloading the top file of the two (seeing as it prob. isnt rootable anyway) http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
download, unzip if needed, and try flashing that in the AP slot when in ODIN...see what that does..
Click to expand...
Click to collapse
I will try it and keep you posted. I believe I am using it correctly, phone is connecting and it will start things but then the fail message comes up.
TUTRider said:
I will try it and keep you posted. I believe I am using it correctly, phone is connecting and it will start things but then the fail message comes up.
Click to expand...
Click to collapse
I know, just figured I'd make sure. I've messed up with it alot myself, trial and error.
Yeah if the error message pops up I'm pretty sure it's one of the 2 new updates...it kills root and backwards flashing
roadblock217 said:
I know, just figured I'd make sure. I've messed up with it alot myself, trial and error.
Yeah if the error message pops up I'm pretty sure it's one of the 2 new updates...it kills root and backwards flashing
Click to expand...
Click to collapse
It worked. Thanks you so so so much! Now I know I just got myself out of a hole but...any chance I can get this thing rooted? or am I better off just leaving it as is?
TUTRider said:
It worked. Thanks you so so so much! Now I know I just got myself out of a hole but...any chance I can get this thing rooted? or am I better off just leaving it as is?
Click to expand...
Click to collapse
As he said in his first response to you, the OE1 and OG5 builds cannot be rooted, and likely will never be able to be rooted.
TUTRider said:
It worked. Thanks you so so so much! Now I know I just got myself out of a hole but...any chance I can get this thing rooted? or am I better off just leaving it as is?
Click to expand...
Click to collapse
Glad that worked at least...but yeah you won't be able to root or anything until (if) they find an exploit..only time will tell I guess at this point....BUT you have a phone that works at least...
landshark68 said:
As he said in his first response to you, the OE1 and OG5 builds cannot be rooted, and likely will never be able to be rooted.
Click to expand...
Click to collapse
OK. Thank you very much!
I happily did exactly what TUTRider did, from trying to root, to bricking, then using roadblock's 6.0.1 files to unbrick, but I'm still getting stuck on the Galaxy splash screen. Odin 3.09 gave the load a PASS, and I 100% had 6.0.1 on it before trying to root. Is there something I could be doing horribly wrong, I'm fairly new to Android rooting, though I have a lot of experience with iOS jailbreaking.
fabledlight said:
I happily did exactly what TUTRider did, from trying to root, to bricking, then using roadblock's 6.0.1 files to unbrick, but I'm still getting stuck on the Galaxy splash screen. Odin 3.09 gave the load a PASS, and I 100% had 6.0.1 on it before trying to root. Is there something I could be doing horribly wrong, I'm fairly new to Android rooting, though I have a lot of experience with iOS jailbreaking.
Click to expand...
Click to collapse
If you're trying to root, you have to be on Lollipop. Can't root MM, but it IS possible to get on a pre-rooted ROM.
Go back to Lollipop, and follow this: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Once you're on Lollipop and rooted, if you can get your bootloader unlocked, then you can upgrade to a pre-rooted 6.0.1 ROM.
Go here to see if you can unlock. (Some phones can, some can't. Cross your fingers!) Read the "Warnings" section carefully, and look to see if your cid # starts with 15.
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
If you can unlock, follow the instructions on that page carefully to do it, and then follow these instructions for going to 6.0.1 on unlocked bootloader:
http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
TUTRider said:
it was on 5.0 I believe, and now am using 3.09. Thanks for the info.
Anything else you would recommend?
Click to expand...
Click to collapse
Yes. We would need to know which 5.0/LP you were on. Such as 0A8, OC4, OD5, etc...as the person posted before me. You cannotODIN back to KK(4 4.2/4.4.4) if you were on OE1 and above...if you know exactly what version you were on, I'd suggest you grab that tar and odin. Best of luck bud and let us know the Version you were on before you attemptedto root.