I'm hoping someone can help me, and I may need led thru steps.
I came from an x2, which I had managed to root, install recovery, and flashed and changed several ROMs, all successfully.
On my rezound however, I'm kinda stuck. I unlocked it, using the htc instructions and links, and rooted using zerg. I apparently don't have, and never have had recovery. Originally I just couldn't go any farther as far as gaining recovery or flashing roms, would get an error message and it would go to reboot. I don't know what I did 2 nights ago, but how whatever I do from the boot screen, I get an immediate haptic response, and it goes right to the white htc screen, where it is locked until I pull the battery. I've even tried to do factory resets, and it asks the prompt questions, but eventually it just reboots to the locked htc screen, until I pull the battery. Then it will reboot normally, but nothing was wiped.
I'm not totally inept, on the phone or the computer, but I'm definitely still a noob, but I really want to learn this stuff, the customization possibilities are the main reason I got the rezound.
I would appreciate some patient assistance from some of you knowledgeable folks!
Thanks in advance! Scott
Try using scott's cleanflash tool. It will flash recovery for you. It will also flash the boot.img (kernel) when you flash a custom ROM.
Sounds like you have fastboot checked in the settings.
If you really want to learn more about flashing, do yourself a huge favor and read up on ADB and fastboot. There's a few really good guides on them you can find by searching the forums, and knowing the basic commands will save you quite a bit of hassle vs. constantly doing battery pulls.
update..getting worse
thanks to the 3 of u who tried to help so far, i have tried some of your advice, but now my phone is basically non-functional, with constant reboots. it wont even allow me to do a hard reset. i tried it thru settings, when i could access them, and thru the "battery pull and buttons method". it confirms the reset, and goes thru the motions, but when i reboot it...everything is the same...including my problem. i need a functioning phone, does anyone know how i can go about putting my x2 back into service?
i know a lot of people on here probably figure i'm getting what i deserve, but if it comes down to it i will run over it with my car and get an insurance replacement. i really want to learn how to do this stuff, but without the background or any help, maybe i AM too "stoopid" Thanks Scott
Are you able to connect to your pc with it so you can use adb or RUU?
Not that I'm going to be the one with the answer to your problems, but maybe you can post exactly what you did that got you messed up in the first place because your post is a little confusing and it would help people who really know this stuff figure out what happened and how to fix it. Looks like you rooted and then did you ever flash a recovery?
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
i appreciate it!
pwnwolf117 said:
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Ty wolf...and I very likely will take you up on your kind offer very soon! I was away all afternoon and evening today.
I did get out of the bootlooping mess I had earlier, I found a related post on droid forums, posted by malkavian under the title "continuous rebooting". The fix involved removing the sim card and typing in a code, and it fixed my most pressing problem.
I still have big problems though, I can't do anything from the boot/recovery screen, it goes right to the white htc screen and locks until I pull the battery. Also, I have tried several times to do hard resets, and those don't work either. I hope to talk to you soon...and thanks in advance! Scott
Related
Ok well, I finally did it. Broke my brick cherry. Screen goes black after galaxy S logo pops up. Was running bionix 1.3 w/ KK. Voodoo does not run on my phone. Went back to stock rom to undo tayutama's lag fix. undid it. Rebooted, got a black screen. Went into recobvery and tried to put in Bionix w/ KK, does a half install reboots gets to galaxy s screen and thats it.
I am a bit of a noob, I've flashed a couple of roms gone back and forth with no problems. I am not adb savvy, just figuring out how to get into it and start it up.
Any help appreciated,... will absolutely paypal you for a case of beer for your time and patience. I am cool calm and collected about this, I know it happens, so I should be pretty easy to work with. will definitely take this as a learning experience.
Have you tried using odin to go back to stock. Also you are going to get flamed for posting this in the dev section.
Sent from my SGH-T959 using Tapatalk
what is odin, how do I get it and get it cranking
Did you wipe/factory reset? From what I've been told, if you can get to recovery, you are not bricked... so I'd try getting into recovery, and wiping everything clean.
When you reverted to stock did you use Odin or Clockwork recovery?
EDIT: Never mind
delete user data and cache?
i used clockwork
You could also try to flash the file from Eugene's froyo that wont brick. Read the instructions sombionix posted in his original 1.3 post
Sent from my SGH-T959 using XDA App
That's not a brick. Learn what brink means FCOL
P.S. WRONG FORUM
http://forum.xda-developers.com/showthread.php?t=739091
Read through this post it will explain odin and its fickity nature.
jrkart99 said:
what is odin, how do I get it and get it cranking
Click to expand...
Click to collapse
Sent from my SGH-T959 using Tapatalk
Download this. It contains everything you need to get back up and running.
1. Make sure phone is off and not plugged into anything.
2. Open Odin
3. Select PIT file
4. Select PDA file
5. Click "Re-Partition" box in Odin
6. Hold volume UP and volume Down while plugging into the computer.
7. Phone will now be in Download mode
8. Odin should show your phone on a COM port (in yellow). If it does not, unplug the phone and plug it back in.
9. Click "Start"
Guys, thank you for your patience and tolerance. I realize wrong forum, torch me. 3.5 seconds of your time to point me in the right direction is worth the hell i'll get. Any other suggestions are welcome, and i promise to post in a more diligent manner next time. Like I said, you guys do great work, I am interested in learning this stuff but its a pretty stiff learning curve.
It is a brick. Although he should have said "soft" brick.
Sent from my SGH-T959 using Tapatalk
Just wondering, what is the difference of brick and door stop?
jrkart99 said:
Guys, thank you for your patience and tolerance. I realize wrong forum, torch me. 3.5 seconds of your time to point me in the right direction is worth the hell i'll get. Any other suggestions are welcome, and i promise to post in a more diligent manner next time. Like I said, you guys do great work, I am interested in learning this stuff but its a pretty stiff learning curve.
Click to expand...
Click to collapse
The post directly above yours tells you step by step what to do. Your phone is fine you just gotta ODIN back to stock.
flipper2006 said:
Just wondering, what is the difference of brick and door stop?
Click to expand...
Click to collapse
They are the same thing. Both are intended to mean that the device is dead, absolutely useless, completely broken, might as well throw it in the garbage, etc.
Unfortunately people have mis-used the term "brick" to describe "won't boot", "almost bricked", and "I'm an idiot" so often that it makes me want to punch babies. Luckily there are no babies present.
had the same issue but fixed it... used odin with the stock but it didn't work... tryin every restore in the book... except the Froyo version... low and behold Eugenes Froyo did the trick... it allowed me to install it and then go back to the rom of my choice... in recovery I repeatly got the error with trying to wipe data... after boot the phone would get stuck on a blank screen with the soft key lit... but (ROM) Froyo ~~~That does not Brick! Downgrading Is Fine --eugene373 did the trick... I'm not a noob but I almost called tmo, to do an exchange... Bionix 1.3 is the only rom I have ever had this problem with... It happened when I attempted to change roms via clockwork...
see i'm already learning. One less possible stupid-ass noob post from me. Learned odin, and the difference between brick, soft brick, and a baby punching brick.
Edit: I realize that, hydro, but the sheer volume of genius here, including yours i'm sure, is a lot to sort through. I want to learn, but just looking at all this info there is no good place to start, that I can decipher. Maybe a thread somewhere and how to get started, a learning section that spells it out for idiots like me. Using Odin, adb, etc etc etc. Keeps the noobs off the dev section. Years from now I hope I can been more of a contributor than a leech. Again, very sorry to put you out.
jrkart99 said:
Ok well, I finally did it. Broke my brick cherry. Screen goes black after galaxy S logo pops up. Was running bionix 1.3 w/ KK. Voodoo does not run on my phone. Went back to stock rom to undo tayutama's lag fix. undid it. Rebooted, got a black screen. Went into recobvery and tried to put in Bionix w/ KK, does a half install reboots gets to galaxy s screen and thats it.
I am a bit of a noob, I've flashed a couple of roms gone back and forth with no problems. I am not adb savvy, just figuring out how to get into it and start it up.
Any help appreciated,... will absolutely paypal you for a case of beer for your time and patience. I am cool calm and collected about this, I know it happens, so I should be pretty easy to work with. will definitely take this as a learning experience.
Click to expand...
Click to collapse
Your file system has become corrupt. Using Odin, Flash Eugene's 2.2 froyo build then flash back to the stock build. This was the only thing that worked for me.
jrkart99 said:
see i'm already learning. One less possible stupid-ass noob post from me. Learned odin, and the difference between brick, soft brick, and a baby punching brick.
Edit: I realize that, hydro, but the sheer volume of genius here, including yours i'm sure, is a lot to sort through. I want to learn, but just looking at all this info there is no good place to start, that I can decipher. Maybe a thread somewhere and how to get started, a learning section that spells it out for idiots like me. Using Odin, adb, etc etc etc. Keeps the noobs off the dev section. Years from now I hope I can been more of a contributor than a leech. Again, very sorry to put you out.
Click to expand...
Click to collapse
did you even bother checking out the thread with "bible" in it at the top of the forum?
Also, you say you realize this isn't Q&A section.....you realize people would have helped you there without wasting other people's time right?
Posts like this also serve to clutter things up and make it even harder to find stuff as well
come on man, you knew better but you did it anyways
That being said, I'm not a total ****...hope you get it fixed
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Well I'm deeply sorry for your issues but I also believe that the issues your experiencing is not totally related to the "wire trick".
The effects of the wire tricks can't do much damage because the voltage going out of the pin#1 is not enough to cause massive effects with the small amount of time you make contact with ground.
Questions :
what kind of wire did you use?
How long did you place the wires in full contact?
I would say as well that disclaimers are posted and there are risks with following any prodcedures written in this site.
Try flashing a RUU and see what happens, perhaps that could be a way out?
Sent from my PG86100 using Tapatalk 2
Nametaken said:
So I was on SOS Rom with Chad's linux 3 kernel and did the wire trick. I got s off, yay!!!!
So, now my wifi stinks, 3g stinks, my touch screen was affected, I have slight dead areas. I can't flash kernels, but I can flash boot screens. Totally not worth the trade off, lol. I have tried CWM, 4Ext, fastboot and flash image GUI. None work
Anyone have any ideas WTF is going on? Or what I need to do? I was thinking about using google to find out how to get s on and try the wire trick again, or just stay s on.
Would I need to flash a firmware from Frieza to possibly fix the kernel issues? I have no idea how that would help at all, lol.
If anyone else has had issues like this,.what did you do?
XDA senior techs, any ideas?
Not saying the wire trick stinks, just saying I ran into an issue I cant figure out
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Oouch! I hope there is a fix for you, I'm sure you are going to try everything.
I don't know how to fix this but I do know a little bit about electronics. Actually quite a bit. Sounds like this trick shorted out or caused a voltage spike internally. Generally when an electronic component is damaged, there is no fix.
When you let out that factory installed smoke, you can't get the Genie back in the bottle.
I had a laptop once where the fan stopped working. I bought a new one. New one was not getting any voltage. A friend of mine was sitting at the bench with me. He decides lets just find another spot with same voltage and tap in there. Starts jumping wires around on the mother board and poof -- $1,000 dollar laptop on sale for parts on Ebay. Took me a long time to get over that one.
I was just looking around and found a problem similar to yours, in the "wire trick" thread. http://forum.xda-developers.com/showthread.php?p=26390751
Yeah... I totally noob bombed that dev thread so o started up a qna here lol
Sent from my PG86100 using XDA
Just a little more info. I can flash other kernels, but on sense Roms, it just shows up as the same name as the other stock kernel. I was able to fully flash other roms, like AOSP. Once I flash AOSP, I can see the other kernels I flash.
Flashing AOSP:
While I can flash it and other kernels, I get stuck on being able to activate my phone on the device. It gets stuck saying airplane mode is on. Totally sucks. Haven't tried activating online or by calling sprint. I have been busy with family stuff.
If anyone else has issues, post em up! Perhaps we can all help each other out
Sent from my PG86100 using XDA
So Here's what I ended up doing. After wire trick got me the S-Off, I had that ICS HBoot and thought hey, maybe this has something to do with my weird AOSP issues (for background please see my post in the CDMA developers section in the JBear thread), so I flashed my 2.17 RUU that I had handy. After that, I updated PRL and Profile (hoping this would do something). Then to my surprise, everything was stock again, bootloader read hboot 1.5.0 again instead of the 1.57 one, however no root because it's an RUU! Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had. From there, I restored the nandroid I had (Nocturnal ICS Xi36 r105) and it all booted up fine. Later I will try flashing back to CM9 and see what happens, perhaps I'll be able to get out of this "sort of Airplane mode" that isn't really airplane mode (where the phone htinks it's deactivated.)
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Well what i can say is that after trying the wire trick my device would randomly turn off and stop working. No charge, No light. Nada. Completely dead then it would randomly come back to life. Anyways. I took my phone to sprint today and ill be going back in two hours to see what the problem with my phone is.
I personally think its a hardware issue. Maybe i used a bad wire? Or i touched the wire during the process which is known to mess up your device.
Thinking about it . I don't see why people don't downgrade instead of the wire trick.
Update- Sprint told me my device had hardware issues and will send me a new phone within 4 days.
There is a possibility that, as someone else has pointed out, that we are indeed hurting our phones. Not so insulated wires, paperclip with tape etc, is the culprit. Too much static getting in and possibly hurting our phones. Something to think about.
To RUU Paul, lol,
I was thinking of uprooting using a similar method like you and gaining root again to ensure it isn't permanent. While it seems you could make it back, this could mean it is a software issue then, but it is too early to tell. Hopefully we cab get enough of the anomalies in to pin point this.
Sent from my PG86100 using XDA
cmbaughman said:
Anyway, I kept reading through the thread like some of these folks told me, however I didn't find much, I did see that most people with success were using the JBear GB version. So, I flashed the jb_hboot from the GB version (I actually took another guy's advices and simply renamed the jb_hboot.zip file to PG86IMG.zip, this worked! Got me the Jbead modified GB bootloader on 1.50. SO I guess since we're S-Off, I was able to go back to hboot 1.50 and then did a fastboot flash recovery recovery.img and flashed the Ext4 recovery image I had.
The key here is that while I was on GB RUU, I updated PRL and Profile, then went to the 1.5 hboot hoping that would be enough for the CM 9 rom and other AOSP ICS roms to activate upon install. I'll keep you posted.
Thanks for starting this thread man, we need a place to sort all this out. With all the info that floods the OPs of development threads, it's hard to really find what is even relevant. So, glad to see one in the Q and A that we can ask questions.
Click to expand...
Click to collapse
Thanks for pointing this all out! I can confirm that doing this allows us to flash back to AOSP with Airplane mode off and get it all up and going.
Once in there, you can change out your kernel and see that it is changed under About Phone! I loves you so much!
Now, if anyone has a way to verify if a kernel was changed or not, we can see if my idea was right about it flashing the kernel, just not showing the correct name of the kernel that was flashed
Thank you all the effort you guys have put into this. I too ran into this issue, and simply flashing the GB hboot resolved my issue. Just so everyone knows, that it is not necessary to revert to stock first. Just simply flash the other hboot, and you should be good to go.
I know someone will eventually tell me to do a search, but I have and can't make any sense of most of the so called guides. What I have been finding is for the international version, or some generic crap that don't really help me. My phone is stuck on the Samsung logo when you try and power it on. I really need to fix this!!! I did SIM unlock it, rooted it, and installed OnlyOne ICS because I got tired of waiting for slow a$$ ATT to get the ICS update out. Anyhow, the phone worked great for 2 months and now this morning it kept saying, blah blah has crashed, etc. So I rebooted the phone and lord behold, the stupid thing won't work anymore. The only thing I can do with it is hold the power button and down volume button to get to the "Odin Mode". Other then that, the phone is useless. I would love to find some guide that is more specific on fixing this problem? Maybe I over looked one, but I am at work and don't have the time to search thru hundreds of threads, etc. I will when I get home, but really need to fix the phone ASAP since I use it for work too. Any info would be awesome.
I think your talking about Download mode.
http://forum.xda-developers.com/showthread.php?p=2725944
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
kcraptor82 said:
I know someone will eventually tell me to do a search, but I have and can't make any sense of most of the so called guides. What I have been finding is for the international version, or some generic crap that don't really help me. My phone is stuck on the Samsung logo when you try and power it on. I really need to fix this!!! I did SIM unlock it, rooted it, and installed OnlyOne ICS because I got tired of waiting for slow a$$ ATT to get the ICS update out. Anyhow, the phone worked great for 2 months and now this morning it kept saying, blah blah has crashed, etc. So I rebooted the phone and lord behold, the stupid thing won't work anymore. The only thing I can do with it is hold the power button and down volume button to get to the "Odin Mode". Other then that, the phone is useless. I would love to find some guide that is more specific on fixing this problem? Maybe I over looked one, but I am at work and don't have the time to search thru hundreds of threads, etc. I will when I get home, but really need to fix the phone ASAP since I use it for work too. Any info would be awesome.
Click to expand...
Click to collapse
If you can get into download mode (odin mode) just flash the attstock Rom to unroot.
Go to rootgalaxynote.com and click the upper right hand corner where it says uroot and follow the directions. Works great for me used it multiple times.
Sent from my SAMSUNG-SGH-I717 using xda premium
I do appreciate the quick responses, but I'm about to head out and will try to re-flash it later. I am just concerned about the data / pictures, etc I have on the phone itself. I know I can pull the 16gb sd card I have and it will be safe, but if I use the ODIN way to re-flash to stock, will it erase all my content I have? I thank god I have a MyTouch 4g as a backup, but all my work related stuff is on my Note, so I am really up a creek right now without it.
kcraptor82 said:
I do appreciate the quick responses, but I'm about to head out and will try to re-flash it later. I am just concerned about the data / pictures, etc I have on the phone itself. I know I can pull the 16gb sd card I have and it will be safe, but if I use the ODIN way to re-flash to stock, will it erase all my content I have? I thank god I have a MyTouch 4g as a backup, but all my work related stuff is on my Note, so I am really up a creek right now without it.
Click to expand...
Click to collapse
If you unroot all of the data stays on your note. No worries. Good luck
Just one thing, when you unroot and it is finished the att logo will come up with the "rethink possible" after that just go into Samsung recovery and reboot from there.
It doesn't say that on the website.
Sent from my SAMSUNG-SGH-I717 using xda premium
I got it to work when I got some time. I used a Wi-Fi connection at MacDonalds and downloaded the onlyone beta 5 rom. Thank god I had my laptop with me also. I was on beta 4 but I also got into clockwork mod and fixed permissions & cleared cache. Then went and flashed the new rom, hoping my data and installed apps would still work. Well my phone is working great again. Thanks for the info and keep up the good work!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Can you put solved in the title please? : )
And quite happy for your success.
After scouring for two days I am just giving up and asking for help. Here is what happened. I have a At&t Galaxy Note. It was rooted but very glitchy. Kept shutting off, weird lines going through the screen, my camera didnt work. I know for that process I did TWRP and cyanogenmod. I went back to att stock from a forum found here. After I did that I had no google apps anywhere. SO my brother found some gapps.zip thing. He put it on my phone after I had restored back to a previous version that did have them. Now my phone wont stay on for longer than a minute. I cant get it to recognize on my computer. So I cant even try to get into it to see if I can fix anything. Everytime I conntect it, a message pops up that says that it cannot install MTP... Even if I restore again, as I have tried. It is still not letting me use it. Then my brother decided to re root it I guess. And that is all well and fine but i still cant use my phone. I saw something about a .zip that removes gapps but I havent been able to use that as my phone just wont install it in recovery mode. Can someone please please help me!!!!
luvpudds said:
After scouring for two days I am just giving up and asking for help. Here is what happened. I have a At&t Galaxy Note. It was rooted but very glitchy. Kept shutting off, weird lines going through the screen, my camera didnt work. I know for that process I did TWRP and cyanogenmod. I went back to att stock from a forum found here. After I did that I had no google apps anywhere. SO my brother found some gapps.zip thing. He put it on my phone after I had restored back to a previous version that did have them. Now my phone wont stay on for longer than a minute. I cant get it to recognize on my computer. So I cant even try to get into it to see if I can fix anything. Everytime I conntect it, a message pops up that says that it cannot install MTP... Even if I restore again, as I have tried. It is still not letting me use it. Then my brother decided to re root it I guess. And that is all well and fine but i still cant use my phone. I saw something about a .zip that removes gapps but I havent been able to use that as my phone just wont install it in recovery mode. Can someone please please help me!!!!
Click to expand...
Click to collapse
wow. the first few sentences were making sense, then you just lost it grammar wise and lost me. it would have helped knowing what ROM was on your phone. from symptoms it sounds as if t was a 4.2 ROM with no GAPPS and some serious OC/UV issues.
but you lost me with your English and the "TWRP and CYANOGENMOD thingy" i know what they are obviously, but what you did with them is a HUGE guessing game. one person not knowing what they are doing is bad enough, but two of you.......... cant do that man. kind of like masturbating with someone elses hand man. who cleans up the mess.
absolute clean slate is going to be you best option in my opinion. the "Super Everything Thread" is going to be your new best friend.
read it, live it, learn it......................understand it. put yourself in position to help yourself first.
tutorals on YOUTUBE can help too.
can you get DOWNLOAD MODE?
do you have ODIN?
do you have PDA/ TAR files you need?
you may need to re-install the DRIVERS for phone on computer
there is a glossary in Super thread, that is why i capped these words. key points and things you need to do. its a marathon not a sprint.
go slow, one step at time, understand what you are doing. even rehearse it, i did. be confident in what you are doing. make sure you have files for I717.
read the OP's for ROM's
some need GAPPS (4.2) and some don't (4.1.2) or Touchwiz
the new 4.3 will also need GAPPS and there are 4.2 and 4.3 GAPPS. again make sure you have right files. all the more reason to take your time.
and uh, don't just let someone flash whatever on your phone, that's how you get a BRICK.
good luck and let us know.
if i have stated anything wrong, someone else will be buy to correct.
nothing wrong with how i am telling, others just may have shortcuts.
what you do with it is up to you, i just like to understand what i am doing, cause i will have to fix it.
but keep us posted
captemo said:
wow. the first few sentences were making sense, then you just lost it grammar wise and lost me. it would have helped knowing what ROM was on your phone. from symptoms it sounds as if t was a 4.2 ROM with no GAPPS and some serious OC/UV issues.
but you lost me with your English and the "TWRP and CYANOGENMOD thingy" i know what they are obviously, but what you did with them is a HUGE guessing game. one person not knowing what they are doing is bad enough, but two of you.......... cant do that man. kind of like masturbating with someone elses hand man. who cleans up the mess.
absolute clean slate is going to be you best option in my opinion. the "Super Everything Thread" is going to be your new best friend.
read it, live it, learn it......................understand it. put yourself in position to help yourself first.
tutorals on YOUTUBE can help too.
can you get DOWNLOAD MODE?
do you have ODIN?
do you have PDA/ TAR files you need?
you may need to re-install the DRIVERS for phone on computer
there is a glossary in Super thread, that is why i capped these words. key points and things you need to do. its a marathon not a sprint.
go slow, one step at time, understand what you are doing. even rehearse it, i did. be confident in what you are doing. make sure you have files for I717.
read the OP's for ROM's
some need GAPPS (4.2) and some don't (4.1.2) or Touchwiz
the new 4.3 will also need GAPPS and there are 4.2 and 4.3 GAPPS. again make sure you have right files. all the more reason to take your time.
and uh, don't just let someone flash whatever on your phone, that's how you get a BRICK.
good luck and let us know.
if i have stated anything wrong, someone else will be buy to correct.
nothing wrong with how i am telling, others just may have shortcuts.
what you do with it is up to you, i just like to understand what i am doing, cause i will have to fix it.
but keep us posted
Click to expand...
Click to collapse
Im sorry, Im just really frustrated. My phone was working fine yesterday and now its a very expensive paperweight. And not only that but Im having problems with my laptop. Apparently the hard drive just went clonkers for no reason and now I have to put in a new one. Yes I can get into download mode. Yes I have Odin. Yes I have the PDA/TAR files. I made sure everything was for the sgh i717. I read each process ten times before I did it. I installed my drivers from the Samsung website. I think my problem is that the internal sd card isnt being recognized. When I go into recovery mode, which is CMW btw, it gives me an eemc 07 error message and says it cant mount. When I can get my phone to stay on long enough for thecpu to recognize it it doesnt say sd card just phone memory. I will be sure to read the super everything thread. As for a ROM there isnt one on here. If I try to put one one it wont install and keeps saying that eemc 07 error message. Thanks for responding. Im spiraling in self-pity right now but im determined to get my phone back.
If you get it back to stock, do a complete erase/format, and your still having all these glitches, there's a good chance there's hardware issues. Especially if your not able to see the external SD card etc.
If your the original owner (I.E. you got it from a dealer with a plan), and you can get your counter reset to 0 on stock with these issues still showing up, it might be easiest to take it in and get a replacement. That is, if you have a warranty option available.
Ragnarkov said:
If you get it back to stock, do a complete erase/format, and your still having all these glitches, there's a good chance there's hardware issues. Especially if your not able to see the external SD card etc.
If your the original owner (I.E. you got it from a dealer with a plan), and you can get your counter reset to 0 on stock with these issues still showing up, it might be easiest to take it in and get a replacement. That is, if you have a warranty option available.
Click to expand...
Click to collapse
Its not the external sd but the internal one. Its just gone... I know that this is the problem at this point. But I have no idea how to resolve that issue. I have no idea where it is or how to get it back. I have been on xda and droidforums for an extreme amount of time trying to find a solution but nothing going. The only way I have seen to reset my counter is to use triangle away. As I cannot even use my phone due to freezing and restarting I cannot even install that app. I am hoping that one person in the wide world has had this problem and fixed it and will read this and tell me how to fix it.
Status 7 means you need to update you recovery
Sent from my SGH-I717 using xda app-developers app
Thanks for all the help. Took it it AT&T. Now my phone is working properly if a slight bit laggy. But at least its working.
luvpudds said:
Thanks for all the help. Took it it AT&T. Now my phone is working properly if a slight bit laggy. But at least its working.
Click to expand...
Click to collapse
so where are you at then?
what does your phone show as running?
settings/about phone
are you just going to leave it or are you still going to pursue customizing?
captemo said:
so where are you at then?
what does your phone show as running?
settings/about phone
are you just going to leave it or are you still going to pursue customizing?
Click to expand...
Click to collapse
I'm running 4.1.2 now. I will not be customizing like that for some time. I might think about it later but I'm so glad to have it back I'm just going to enjoy it for awhile.
luvpudds said:
I'm running 4.1.2 now. I will not be customizing like that for some time. I might think about it later but I'm so glad to have it back I'm just going to enjoy it for awhile.
Click to expand...
Click to collapse
you know, something going wrong with mine was my biggest worry. when I decide to screw something up, I can really screw something up. so I was very hesitant. it probably took me 2-3 months to get the courage to flash. but that was most likely a good thing. it made me be very thorough in the process.
all I am saying is don't let it completely discourage you. you have time.
glad you got phone back, I know it can be a bit of a scary thing. I have come across an issue or two myself and actually surprised myself by fixing myself. actually a pretty good feeling.
anyway, stick around, there are some pretty amazing folks here.
captemo said:
one person not knowing what they are doing is bad enough, but two of you.......... cant do that man. kind of like masturbating with someone elses hand man. who cleans up the mess.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
Rofl. Now I have a completely different vision when I see captemo advise a full wipe to someone.
Sent from my SGH-I717 using Tapatalk 4
Bubbajoe40356 said:
Rofl. Now I have a completely different vision when I see captemo advise a full wipe to someone.
Sent from my SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=h5HJGuyBfx8
Well I think we just lost our "FamilyFriendly" label.
rangercaptain said:
Well I think we just lost our "FamilyFriendly" label.
Click to expand...
Click to collapse
Well at least our PG-13 rating anyway. Tell me it wasn't pretty funny though
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
rangercaptain said:
Well I think we just lost our "FamilyFriendly" label.
Click to expand...
Click to collapse
I don't know ... They looked like they were pretty friendly.....for family
Sent from my SGH-I717 using Tapatalk 4
So I finally HAVE to replace my Note 2 via warranty. Power button sticks and will not boot.
At the end of the call to place the warranty order she says "any physical damage, water damage, or software alterations will result in a charge of $290". So I'm rooted and ROM'd and would normally just return to stock. BUT since the phone will not boot, I cannot do this. I realize if it won't boot for me it likely won't boot for Verizon.
My worry is that somehow they will in get it to boot. Do they still check for root? If so is this something I should be worried about? I cannot for the life of me get this thing to turn on it seems like I will not be able to return this to stock with out powering the phone on. Any insight is greatly appreciated.
I have done the warranty replacement game for a long time. Typical the people checking the phone are stupid and dump for checking for root. I havent spoken to or talked to one smart person that would check. Plus the people they hired to make sure the devices comes in probably isn't tech savvy. Just a worker trying to get paid.
Sent from my SCH-I605 using Tapatalk 4
I agree with the above. I guarantee you the people who do the initial evaluation have a 'target' for the number of phones processed. But just the same return your phone to as stock looking as possible. Restore the launcher, use a stock wallpaper and/or boot-ani. Uninstall all apps you got from the store. And run your battery all the way down. It will continue to discharge even though it's off. This means it will need to charge for a few minutes before it will boot again.
And I've never noticed many posts (i can't recall even one) about phones being kicked back for being rooted/flashed.
But with that said isn't there some kind of flash 'counter' on the Note 2?
Sent from my Nexus 7 using XDA Premium 4 mobile app
When I had my DROID X I went into a Verizon store to upgrade to an s3 and the guy who just got done telling me how he "mods" his gnex looked at my X and it was running cm7 themed out the wazoo and he said how plain the stock os is on the Motorola. Haha. So I don't think that 98% of the people who are either in store or at the warranty place have a clue what rooted is let alone able to tell if it is or not.
Sent from my SCH-I605 using XDA Premium 4 mobile app
I think I read somewhere that you can make a powered usb jig the will boot it into download mode. I might be wrong, but you can search around for it.
Sent From My Sticky Note, Too?
Did you even read the op
Sent from my SCH-I605 using xda app-developers app
Yea I can't even get the phone to boot. Which I believe is due to the malfunctioning power button. But I'm still concerned verizon will find some way to get it booted. I'm going to see if I can boot via ADB this evening. Its been quite a while since messing around with ADB so I need to allow myself some time. Hopefully I can boot it and just Odin the factory image via ADB.
I should also try and clear the flash counter right? Does anyone have any tips or know-how on how to do that? I saw somewhere that there is an app. But should that be run before or after running the Odin stock image?
Thanks again guys and gals.
Hey gerg, the app is triangle away, and I would always try to return to stock if possible. I would use it before returning to stock as it needs root privileges. What a great learning experience (better to look at it that way then get angry trying to accomplish your goal). Keep us posted as we are all"rooting" for you....:thumbup:
"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
JeramyEggs said:
Hey gerg, the app is triangle away, and I would always try to return to stock if possible. I would use it before returning to stock as it needs root privileges. What a great learning experience (better to look at it that way then get angry trying to accomplish your goal). Keep us posted as we are all"rooting" for you....:thumbup:
"One small step for man, One giant leap for mankind" said anyone who has tried Moon Rom
Click to expand...
Click to collapse
Thanks man. Appreciate the positive vibes.
However it seems like I'm stuck. I can't for the life of me get this phone to boot, therefore I can restore the stock image via ADB, because ADB will not recognize the device since it is off. I've tried every trick out there, including the youtube video about pulling the charger and pulling/re-seating the battery as fast as possible. No dice.
I did however receive my warranty device today, and since I have ADB all set up and ready to go, I'll be rooting her and getting back to Trans-Neb ASAP, and of course I'll see you back in that thread.
Again, thanks for the help guys it is appreciated. I'm fairly sure I've tried harder and spent more time to get this phone to boot than Verizon will ( I hope at least). So if they can't get it to turn on, I don't see how they can tell its rooted
Mods can close this thread
Cheers!