Ill get right to it, but I really need some help here. I was rooted and was attempting to go back into unrooted stock rom using odin on the computer. after numerous fails from odin, I then flashed the stock unrooted rom from my phone using Mobile Odin. Everything went fine until my phone booted back up. Now, about every 5 seconds I get the error "Unfortunately, Direct pen input has stopped working."
This literally makes my phone unusable - I couldnt even send my mom a text asking her to pick me up today...I am currently re-downloading the stock rom and will try again. I really don't know what to do here and need any help you guys can provide!! Thanks!!
[EDIT]
Also, I am following the instructions from http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/ to unroot
smsnodgrass said:
Ill get right to it, but I really need some help here. I was rooted and was attempting to go back into unrooted stock rom using odin on the computer. after numerous fails from odin, I then flashed the stock unrooted rom from my phone using Mobile Odin. Everything went fine until my phone booted back up. Now, about every 5 seconds I get the error "Unfortunately, Direct pen input has stopped working."
This literally makes my phone unusable - I couldnt even send my mom a text asking her to pick me up today...I am currently re-downloading the stock rom and will try again. I really don't know what to do here and need any help you guys can provide!! Thanks!!
[EDIT]
Also, I am following the instructions from http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/ to unroot
Click to expand...
Click to collapse
You haven't given enough info to help you. ... What tar file were you using ... What rom were you on etc .... Have you been on the leak
What USB cable are you using ....Have u tried other versions of Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Related
First off, I want to apologize if I ramble on. I am trying to be as thorough as possible.
Also, I am relatively knowledgeable about rooting and whatnot, so hopefully I will understand whatever help you guys can give me.
Here's my problem:
I originally had Bionix-V 1.3.1 (which is a 2.2 rom), and I wanted to upgrade to a Gingerbread rom. So I downloaded "Trigger Redux" (addictivetips.com/mobile/install-android-2-3-5-based-custom-rom-on-t-mobile-samsung-vibrant/) and followed the instructions completely. The instructions told me to do a nandroid (which I did and it went perfect), then factory wipe the phone and wipe the dalvik cache (which I did), and then run the Trigger Redux zip from the sd card (which I did). Everything worked fine, but when I started messing around with the new rom, I didn't like it as much as my old rom, so I decided to reboot the phone into recovery to perform the nandroid restore. When my phone rebooted, I noticed the clockwork recovery looked different from what had before (it was orange, when the old one I had was red). Anyways, I tried to do the nandroid restore, it gave me an error about not being able to perform the nandroid for whatever reason (I honestly don't remember what it said now). So did a factory wipe again, thinking that may allow the nandroid restore to perform properly, and I still got the same error. So I restarted my phone, and now I'm stuck on the Vibrant logo screen. I can get into download mode (by plugging in usb/pressing vol up and down/inserting battery), but not sure how to get my phone into recovery mode again. I know I can probably use Odin, but I'm not real familiar with that program and I wouldn't know where to start.
What's the first thing I should do? I know my phone is fixable, I just don't know where to start Any help is very greatly appreciated. You guys are awesome!
Odin to stock is simple but risky...if it fails due to any reason u will have a completely bricked phone....there's a guide on how to do that process BC u will need to download two files...one is .pit and other is .Tar file......here's a video link..http://www.youtube.com/watch?v=VIBeLG4frjM...and here is a link to download required files....http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/....good luck
Sent from my MB860 using XDA App
deziguy420 said:
Odin to stock is simple but risky...if it fails due to any reason u will have a completely bricked phone....there's a guide on how to do that process BC u will need to download two files...one is .pit and other is .Tar file......here's a video link..http://www.youtube.com/watch?v=VIBeLG4frjM...and here is a link to download required files....http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/....good luck
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes you need odin but you won't be bricked if it fails for any reason. I have odin fail a few times and you start it back up and try again. The only way you can brick with odin is during a bootloader flash
Sent from my GT-I9000 using XDA App
bfranklin1986 said:
Yes you need odin but you won't be bricked if it fails for any reason. I have odin fail a few times and you start it back up and try again. The only way you can brick with odin is during a bootloader flash
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
if it fails in the very beginning then it's ok but if it fails in the middle then definitely it will be bricked... if you record yourself pulling off usb in the middle of the process then send me that link...i would love to see the result...
Samsung Android T-Mobile SGH-T959 Vibrant Firmware
fallow guy and use from this roms
http://gsm-beyond.blogspot.com/2011/07/samsung-android-t-mobile-sgh-t959.html
bfranklin1986 said:
Yes you need odin but you won't be bricked if it fails for any reason. I have odin fail a few times and you start it back up and try again. The only way you can brick with odin is during a bootloader flash
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i hard bricked going to stock with odin, it froze at the very end so i unplugged to try again and it went off and wouldnt do anything after that
its froze afew times at the beginning aswell but just goes to the phone ! pc screen when unplugged
deziguy420 said:
if it fails in the very beginning then it's ok but if it fails in the middle then definitely it will be bricked... if you record yourself pulling off usb in the middle of the process then send me that link...i would love to see the result...
Click to expand...
Click to collapse
Why would you pull the cord? Never check auto reboot and if it fails just close odin and restart it. If you pull the cord and reboot with a half flashed phone then yes that would probably brick you
Sent from my GT-I9000 using XDA App
bfranklin1986 said:
Why would you pull the cord? Never check auto reboot and if it fails just close odin and restart it. If you pull the cord and reboot with a half flashed phone then yes that would probably brick you
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
that's exactly my point...according to other person he says odin to stock won't brick a phone...so i was just telling him to pull the plug out while it's running the procedure...and of course that will brick his phone and a prove that yes odin to stock can brick your phone... of course pulling a cable would be stupid...but what if your computer restarts all of the sudden or u lose electricity...stuff like that...can cause a dam hard brick....
Hers my dilema, i had 4.1.1 rooted and unlocked and decided to return to stock so I could update to 4.1.2. all went well downgrading to stock but when I got the OTA the phone bootlooped. I could not access the recovery menu to wipe cache (as suggested in a few other post) so I ended up having the download the newest image and flash it to my phone. That worked after using the 16Gb pit file that is here in the forum (it kept failing before trying the pit file). THE QUESTION I have is, how do I root with casual without bootlooping? I tried after getting 4.1.2 installed and it went back into the bootloop. Any help would be greatly appreciated.
big.daddy said:
Hers my dilema, i had 4.1.1 rooted and unlocked and decided to return to stock so I could update to 4.1.2. all went well downgrading to stock but when I got the OTA the phone bootlooped. I could not access the recovery menu to wipe cache (as suggested in a few other post) so I ended up having the download the newest image and flash it to my phone. That worked after using the 16Gb pit file that is here in the forum (it kept failing before trying the pit file). THE QUESTION I have is, how do I root with casual without bootlooping? I tried after getting 4.1.2 installed and it went back into the bootloop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
OK, how exactly did you get 4.1.2 on your phone? You say that using the very latest version of CASUAL still causes bootloops when trying to unlock?
The obvious thing here is YOU NEVER SHOULD HAVE WENT TO ACCEPT THE OTA.
As it is this is a question better answered by AdamOutler or Droidstyle.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
OK, how exactly did you get 4.1.2 on your phone? You say that using the very latest version of CASUAL still causes bootloops when trying to unlock?
The obvious thing here is YOU NEVER SHOULD HAVE WENT TO ACCEPT THE OTA.
As it is this is a question better answered by AdamOutler or Droidstyle.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
big.daddy said:
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
Click to expand...
Click to collapse
The more updates Verizon pushes the tighter they luck the phone down trying to deal up all the holes our exploits could use, in turn that makes the exploits more risky and more prone to cause potential trouble.
It is best to just leave everything alone once you get rooted and unlocked and just flash the updates via TWRP/CWM, there is no real reason or advantage to updating the normal way. It does nothing different than flashing the ROM in recovery and has no advantages and a huge amount of risk.
It may be that the Odin flashable ROM you got was missing something or was wonky in some way since it didn't come from XDA. It shouldn't have reacted that way if you were using the most up to date version of CASUAL.
Sent from my SCH-I605 using XDA Premium HD app
big.daddy said:
I flashed a stock image that I downloaded from stockimages(or something like that) with odin. That got the phone back up and running with 4.1.2. Once I did that, I figured I was back to stock (no root and no unlock) so I tried to run casual to re-root and unlock and ended up in a boot loop. Since then, I have gotten back to root and unlock but from now on I guess I have to update via the TWRP. Thanks for the obvious suggestion but I figured that since i had flashed back to stock it was ok to accept the ota.......I was assuming that I could get full access by running casual. From now on, I will leave well enough alone.
Click to expand...
Click to collapse
Big.daddy can I ask what you used to get back from the bootloop to where your at now? Sorry to bother you but I screwed up somewhere, once again
chiefsfan69 said:
Big.daddy can I ask what you used to get back from the bootloop to where your at now? Sorry to bother you but I screwed up somewhere, once again
Click to expand...
Click to collapse
I used Odin to get the phone back to stock (vramc3). I tried it on two computers and eventually got it to rum when using the 16 GB .pit file that can be found on this forum. That got me back to stock. I then used casual to re-root and unlock. The thing I have learned is that once twrp is intalled, I only need to download a ROM based on the Verizon stock (unless you want custom) and flash it through twrp. NOT WHAT I INITIALLY DID. I flashed back to stock and accepted an ota which didn't work out well. Took me 5 hours of downloading and trying to get the phone flashed. Good luck. The first thing I would try is downloading the beanstown vzw stock ROM and flash it with the .pit file.
big.daddy said:
I used Odin to get the phone back to stock (vramc3). I tried it on two computers and eventually got it to rum when using the 16 GB .pit file that can be found on this forum. That got me back to stock. I then used casual to re-root and unlock. The thing I have learned is that once twrp is intalled, I only need to download a ROM based on the Verizon stock (unless you want custom) and flash it through twrp. NOT WHAT I INITIALLY DID. I flashed back to stock and accepted an ota which didn't work out well. Took me 5 hours of downloading and trying to get the phone flashed. Good luck. The first thing I would try is downloading the beanstown vzw stock ROM and flash it with the .pit file.
Click to expand...
Click to collapse
Thanks man, **** I just went through all this bs and finally got mine last night but then I tried to do casual and something went wrong and now I am back in the loop and I don't know if i should just flash the same I did just last night to get it back or what? Thank you though I really appreciate your help
I would try casual agai if you can get into download mode (power + vol dn+ home). If that doesn't work I'd try reflashing. Good luck.
big.daddy said:
I would try casual agai if you can get into download mode (power + vol dn+ home). If that doesn't work I'd try reflashing. Good luck.
Click to expand...
Click to collapse
I can get in download mode but the problem seems to be the adb, and since i can't get in the phone to turn it on casual never picks up the device, for all I know?
chiefsfan69 said:
I can get in download mode but the problem seems to be the adb, and since i can't get in the phone to turn it on casual never picks up the device, for all I know?
Click to expand...
Click to collapse
Reflash with Odin
big.daddy said:
Reflash with Odin
Click to expand...
Click to collapse
Hold on, reflash casual in odin?
chiefsfan69 said:
Hold on, reflash casual in odin?
Click to expand...
Click to collapse
No, do what you did last time in Odin again.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
No, do what you did last time in Odin again.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I have been trying, this time around it hasnt passed a single flash, on anything?
chiefsfan69 said:
I have been trying, this time around it hasnt passed a single flash, on anything?
Click to expand...
Click to collapse
Check the drivers to make sure the CASUAL driver isn't the one in use.
Sent from my SCH-I605 using XDA Premium HD app
You may also want to try a different computer...... Different USB ports too. I will work it takes a little patience.
I installed a rom, got into a bootloop that wasn't working. I attempted to use odin to flash to factory, but now I get the "firmware upgrade issue" screen when powering on or recovery mode. I can get into download mode, but I keep getting fail when I try to get back to stock. If anyone can help me I would really appreciate it since I just got my note yesterday and want to get it working again (even on stock.)
note: I read for at least 2 hours and tried almost everything. My drivers are installed. New usb cord/port. Reboot computer etc.
hobokenshmo said:
I installed a rom, got into a bootloop that wasn't working. I attempted to use odin to flash to factory, but now I get the "firmware upgrade issue" screen when powering on or recovery mode. I can get into download mode, but I keep getting fail when I try to get back to stock. If anyone can help me I would really appreciate it since I just got my note yesterday and want to get it working again (even on stock.)
note: I read for at least 2 hours and tried almost everything. My drivers are installed. New usb cord/port. Reboot computer etc.
Click to expand...
Click to collapse
Need more info to be able to help....what firmware were you are before you flashed via Odin? We you rooted? Did you have custom recovery installed? What firmware version did you attempt to flash with Odin?
I was on the stock 4.3 firmware, rooted the phone via odin, everything went smoothly. Then I downloaded a rom for sprint note 3, when I rebooted (cleared cache and factory wipe) the samsung logo just kept popping up and rebooting. I was using clockworkmod, but now when I try to access it I just get the "firmware upgrade encountered an issue." ODIN just keeps failing no matter what I try. I am trying the latest N900P stock firmware.
is it time to throw in the towel and see if Asurion can get it replaced? or at this point is it fixable?
hobokenshmo said:
is it time to throw in the towel and see if Asurion can get it replaced? or at this point is it fixable?
Click to expand...
Click to collapse
What exactly is the file name of that which you are flashing in Odin?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
What exactly is the file name of that which you are flashing in Odin?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I realized that I am an idiot and was using a different model number and downloaded MJ4, worked like a charm. But now I want to get to the root of the issue (pun intended.) Why did the rom I used start the bootloop that was not fixed by clearing the cache and factory wipe? I found it right here on the sprint note 3 section of XDA. It was the MINIMUS rom.
I was rooted and all the fun stuff until I took the OTA. I used Odin and went back, used saferoot and just stayed rooted for a bit without putting a custom rom on. I didn't upload any roms. I was tired of getting the update notification and tried to get safestrap on to install a custom rom, but it wouldn't install. I then tried to use Odin to go back to stock and it will say "pass", but the phone is just the same it was before ODIN. I've tried even re-downloading all the programs, but it has no effect on the phone. No matter what I try, it doesn't effect the phone. It comes out the same way.
psalm462 said:
I was rooted and all the fun stuff until I took the OTA. I used Odin and went back, used saferoot and just stayed rooted for a bit without putting a custom rom on. I didn't upload any roms. I was tired of getting the update notification and tried to get safestrap on to install a custom rom, but it wouldn't install. I then tried to use Odin to go back to stock and it will say "pass", but the phone is just the same it was before ODIN. I've tried even re-downloading all the programs, but it has no effect on the phone. No matter what I try, it doesn't effect the phone. It comes out the same way.
Click to expand...
Click to collapse
Your question makes no sense. What are you trying to accomplish?
My goal was to install a custom Rom (Trents).
I was rooted (with saferoot), I went to install safestrap, and that's when it all went bad. I lost root, so I tried to use Odin to format back to stock, it (odin) says it passes, but when it reboots, I am not rooted and nothing was formatted. All my screens are the same, no data is missing. It's like Odin can't re-format the phone.
Sent from my SCH-I605 using XDA Free mobile app
Some how I got the 4.3 OTA. I don't remember accepting it, because I made the mistake of accepting the OTA a time or two before that one. That would explain why nothing is working.
Sent from my SCH-I605 using XDA Free mobile app
psalm462 said:
Some how I got the 4.3 OTA. I don't remember accepting it, because I made the mistake of accepting the OTA a time or two before that one. That would explain why nothing is working.
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using 4.3 to Odin back? If not that is the first mistake.
Let us know, bc If you are using 4.3 to Odin back it sounds like your partitions might be a little messed up if Odin says "pass" but does not wipe the phone completely..
Ok so i didn't want to start another thread but I've been searching all over here and google with no luck. About a week ago i noticed all the L.P. ported roms popping up so i wanted to see what they had to offer. After which i noticed that i wasn't receiving incoming txt. No big deal. New roms have small issues in the 1st version. We all know this. So i restore my rock go to never fails no issues Fre3 2.26. Still no incoming txt. I can receive incoming mms,emails,i get 4g,I can send txt and people get them i have even got storm warning and Sprint sent me a txt when i was on the phone with them just no incoming txt. Im currently using a 3rd party app for txt and running Fre3 2.26 4.4.4, OC5 Modem/Bootloader.
What i have tried:
Full wipes x100
PRL/Profile updates
Sent myself a txt
Ive had Sprint update from there end
I have Galaxy Tools installed but don't really know or wanna mess with it being i dint really know much in that department.
I believe The problem is with in the sim card BUT i dont really know what I'm looking for to fix the issue.
If anyone knows what i should be looking for and what to change it too. Maybe if a developer on here may see this and could shoot me in the right direction id be more then happy to buy them a beer or two. But any help would be great. Thanks in advance!
I was on stock OC5 rooted since it became available. About a week ago I lost MMS completely. I rebooted my device just because it had been a while.
They were working before the reboot and not after, I did same things as you. I also checked APN and none were selected and the list was greyed out.
So I decided to flash PAC 5.1.1 just to test, everything works now.
I use Textra; I tried stock messaging on OC5 with no luck. It is very peculiar.
at least all is good with PAC (for me any way)
I hope you get yours figured out.
Maybe odin to stock oc5 and then root and get custom recovery...just a thought...maybe it just needs fresh start.
Sent from my SM-N900P using XDA Free mobile app
bigpappags3 said:
Maybe odin to stock oc5 and then root and get custom recovery...just a thought...maybe it just needs fresh start.
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
I think I might take you up on that. Still without incoming sms. havent had time to do much with it. I will report back after I give that a shot.
No go as of site now. Flashed the OC5 stock tar in odin. But stuch on boot.
Goat1378 said:
No go as of site now. Flashed the OC5 stock tar in odin. But stuch on boot.
Click to expand...
Click to collapse
Make sure to factory reset in stock recovery, after you odin OC5
jdelano said:
Make sure to factory reset in stock recovery, after you odin OC5
Click to expand...
Click to collapse
ok I'll give that a shot. Thank you!