Help! Messed up my Note ... reacts VERY slow - AT&T Samsung Galaxy Note I717

Hi all,
I need help with my wife's Note i717.
I was on a custom ICS ROM, and I tried to flash CM10 ROM.
I've been flashing ROMs for a few years now on various phone, so this is no different ... flashing went smooth, but after flash CM10 I discovered the phone would freeze on certain screen ... like when I go to Task Manager, or when I hit certain menu's.
After a bit of searching, seems like a few others have the same problem ... I figure maybe ROM isn't very stable, so I did a NANDOID restore to my ICS ROM, and all is good.
Tried to flash again, this time I also wiped my internal SD, and flashed a new UCLF6 radio when I flashed a newer version of CM10.
This is when all hell breaks loose. I run into even more severe problems of freezing after flashing CM10, and I can't even make phone calls anymore as the phone I call would ring, but the Note would freeze to a point the other side can't hear me.
So again I did a NANDOID restore of my ICS ROM, but this time I'm not so lucky. After restore, my Note is VERY SLOW ... it'd take seconds going from one menu to the other, hitting "OK" buttons and the phone freezes for a few seconds before it goes to the next menu.
So I did a clean wipe, starting with a ODIN flashed the stock AT&T image. But rightaway after flashing the AT&T stock ODIN image, after the phone boots up again I knew I got the same problem. Even on the setup wizard by AT&T the phone reacts VERY SLOW like before, or downright freezes.
I followed up with rooting it, flashing CWM, then TWRP recovery, and tried to flash different ROMs ... all give me the same problem. I also tried NANDROID restore again, but same thing!
Any suggestion on what I can do next? I thought flashing AT&T ODIN is already the cleanest wipe I can do to restore my phone ... any help is appreciated!!!

did you make sure you wiped cache, davilik cache and did a factory reset? if you didnt do all 3 then flash again sounds like a dirty flash is what you have been doing

Yes always wipe cache, dalvik and factory reset 3 times before flashing any rom, not to mention I thought ODIN flashing stock rom would get me back to square 1 regardless of previous flashing?

Try using Kies recovery through your computer.
-Once you go NOTE, you'd say 4 inches a Joke
[Lady]: "How do you carry that huge phone in your pocket?"
[Note User]: "I'm used to having huge stuff in my pants"

Kies recovery eh? I can give it a try but how is that different from ODIN?

I had similar issues this past summer...I would try various roms and get crashing and instability, calling issues, etc.
Make absolutely sure that your modem is flashed...I had to do it via Odin. Get a stock one for your carrier. I assumed that when I flashed a new rom that the modem got updated as well but I was wrong. I went from FJs rom to CM10 and got the same issues as you. Went back to FJs rom and the issues persisted. Did a nandroid restore to stock GB and still had the same issues. Then I used the 'muglf4' version for my carrier (Bell), flashed the modem separately and all went well since.
Might not be your issue of course but its something to verify (that the modem and kernel are being flashed).

chriskwarren said:
I had similar issues this past summer...I would try various roms and get crashing and instability, calling issues, etc.
Make absolutely sure that your modem is flashed...I had to do it via Odin. Get a stock one for your carrier. I assumed that when I flashed a new rom that the modem got updated as well but I was wrong. I went from FJs rom to CM10 and got the same issues as you. Went back to FJs rom and the issues persisted. Did a nandroid restore to stock GB and still had the same issues. Then I used the 'muglf4' version for my carrier (Bell), flashed the modem separately and all went well since.
Might not be your issue of course but its something to verify (that the modem and kernel are being flashed).
Click to expand...
Click to collapse
Can you point me to where I can find the tar file for MGLF4 radio? mine is also a Bell unit and I want to ODIN flash the radio to see if it would fix my problems.
Thanks!

chriskwarren has the answer. Your LF6 radio download was corrupted. This happens frequently, so just redownload it and flash it again either with odin or CWM.
If the phone is at&t use LF6, if Bell use the Bell radio.

chriskwarren said:
I had similar issues this past summer...I would try various roms and get crashing and instability, calling issues, etc.
Make absolutely sure that your modem is flashed...I had to do it via Odin. Get a stock one for your carrier. I assumed that when I flashed a new rom that the modem got updated as well but I was wrong. I went from FJs rom to CM10 and got the same issues as you. Went back to FJs rom and the issues persisted. Did a nandroid restore to stock GB and still had the same issues. Then I used the 'muglf4' version for my carrier (Bell), flashed the modem separately and all went well since.
Might not be your issue of course but its something to verify (that the modem and kernel are being flashed).
Click to expand...
Click to collapse
It could be, but I can't seem to find the Bell radio for ODIN flashing, even with a lot of searching ... if someone can point me to it it'll be greatly appreciated.

BTW, having done some more tests I think the problems are caused by either a corrupted radio and/or corrupted kernel.
- If I run the phone in airplane mode, without turning on the radio, the phone works fine, for the most part
- What guarantees the phone to freeze and have all kinds of problems is if I try to make a phone call. The phone will either give me "Call cannot be sent" error message, or it will dial, the other number will ring, but can't hear a word at all, and the Note will freeze.
I have tried flashing different radio's I find, but most radios I find are CWM ZIPs, not ODIN TARs. I don't know if CWM can't do a 'complete overwrite' or something, but flashing different radio's don't help. I want to try to flash radio via ODIN, but can only find 1 appropriate ODIN file, and that tar file might be corrupted in itself because it fails trying to flash it through ODIN.
I suspect it may also be a corrupted kernel, because in trying to make CM10 work I flashed both a different radio and a different kernel, which causes all the problems I have.
I have a Bell Note i717M ... what is the safest radio and kernel I can use with ICS ROM? If someone can point me or send me the ODIN tar's it will be greatly appreciated. I searched and searched but can't find much for ODIN on xda!

Check the "note super everything thread "....
At the top of the general section ...
About half way down the page you will see the modem section .....and bell is there ....g

Try a stock kernel. If else fails, try a bell modem.
-Once you go NOTE, you'd say 4 inches a Joke
[Lady]: "How do you carry that huge phone in your pocket?"
[Note User]: "I'm used to having huge stuff in my pants"

SKyRocKeting727 said:
Try a stock kernel. If else fails, try a bell modem.
-Once you go NOTE, you'd say 4 inches a Joke
[Lady]: "How do you carry that huge phone in your pocket?"
[Note User]: "I'm used to having huge stuff in my pants"
Click to expand...
Click to collapse
Thanks for all the advices guys.
I have tried different radio's, all of them CWM zips. None of them seems to work ... the supposedly "stock" kernel makes it worse actually.
I wonder if ODIN would flash 'cleaner' ... but so far, can't find any ODIN modem.

As stated earlier, your modem you flashed was corrupted and you need the Bell modem.
If it is in CWM zip format, unzip the file on your pc, and use the mdm.bin or modem.bin file in the unzipped folder. That goes in the Phone slot of Odin3.

rangercaptain said:
As stated earlier, your modem you flashed was corrupted and you need the Bell modem.
If it is in CWM zip format, unzip the file on your pc, and use the mdm.bin or modem.bin file in the unzipped folder. That goes in the Phone slot of Odin3.
Click to expand...
Click to collapse
Ahhhh I see ... thanks a lot. I'll try that tonight.

Thanks a lot that did the trick!! As soon as I flashed modem.bin everything works.
How about amss.bin? Do I need to flash it too?

Noooo.

Similar issue - Note very sluggish
Hey guys, I'm having a similar issue as the OP. I've tried updating my Note to ICS without success and was working fine on stock ATT GB. I tried again today to update to ICS and failed, reverted to stock ATT GB from here: http://forum.xda-developers.com/showthread.php?t=1506330, and now my Note is sluggish as heck!
Right at the ATT setup flow, the touchscreen seems very unresponsive and screen taps take a few seconds to register. The soft keys are pretty much unusable - if I hit back or home, the whole thing freezes and randomly resets.
I made sure I wiped cache, wiped Dalvik cache and factory reset and then flashed the stock ROM again, but same thing. I found the stock ATT modem and flashed that as well by putting mdm.bin in the Phone field in Odin, but no luck...
Any idea what else could be wrong here?
Appreciate any help guys! I'm close to having a large ungainly paperweight here...

Related

[Q] Fascinate and new ROM

My apologies if this has been asked before, but I've spent hours searching and think I've done a better job of confusing myself, than answering my question.
I've rooted my wife's Samsung Fascinate, using Super One Click and removed all annoyances such as the Verizon bloat ware and got add blocker installed, etc. The point on doing so, was also to improve battery life, backup the ROM and some of the other associated advantages with rooting. One of my main goals was to also install a custom ROM on her phone, as the factory ROM is very flaky. It receives emails, then doesn't. It sends a text, then can't minutes later. It's been a great phone HW wise, but just junk as far as the OS.
Thus far, all attempts to backup the factory (modified) ROM has failed, which evidently is part of the limitation with the stock ROM. At this point, she's so frustrated (me too) with her phone, that it's time to get serious.
So, my confusion stems from varying reports regarding what the proper steps are to install a new ROM. On my Thunderbolt, I simply used CWM to install and backup/restore my ROMs as needed. This doesn't seem to be the case with the Fascinate and there's varying reports of whether this can even be done if Super One Click was used.
Has anyone had experience with flashing new ROMs after the phone was rooted and if so, by what method?
Her current ROM details are:
Firmware
2.2.2
Baseband
S:i500.04 V.ED05
Kernel
2.6.32.9
Build
SCH-I500.ED05
Thanks in advance.
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cm7 zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
droidstyle said:
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cwm zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
Click to expand...
Click to collapse
Okay, that makes a lot more sense now. Thanks for the quick reply.
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
ibsk8 said:
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
Click to expand...
Click to collapse
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
droidstyle said:
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
Click to expand...
Click to collapse
I never could get to the ROM flashing part. Every time I tried I got the same set of errors as when trying to backup the original ROM. I did manage to get the CWM 4 fix applied through ODIN and it said successful, but nothing really changed and my attempts to flash the new ROM still failed.
I searched around this forum and others and found another file to flash and things went very badly. The flash was moving super slow and I left the phone, so I wouldn't be tempted to do anything stupid and after an hour, it was at the same point. When I rebooted the phone, I got a sad face icon only. No Samsung logo or anything.
Luckily, I was able to re flash the stock rom, but after messing with it for 4 hours and getting nowhere, I decided the stock ROM was good enough for now. I have no idea why this phone is so pesky and read how some folks had to ref lash the stock ROM, before being able to flash a new ROM. I made one final attempt to do so and got the same error as the first time, so that was enough for that day. I don't recall exactly what the error said at this point, but I had blue text, followed by orange, which I think said something to the fact that is was unable to verify the package, followed by red text showing the failures.
Sorry there's no more detail than that for now. I may try this again in the future, but as mentioned this is the wife's phone, so I can't take nearly the liberties with it as I could my own.
If anyone has any ideas on what I may be able to try next, that would be great. If not, I may keep digging on this forum (a very helpful place indeed) and see what the options may be.
Thanks everyone for your help.
refer to section 3 of my guide and follow those steps. for some reason certain fascinates have trouble flashing mtd roms when starting from ed05. I have to start with dl09 eclair then flash cm7. look in page 2 of this section for my guide. all files needed can be found there aswell. good luck!

Stock odin flash and phone still broke

Can somebody please help me!! my att note was being very slow and i had been flashing all sorts of different kernels, roms and modems trying to get a 3g tmo signal going strong. i couldn't get anything to flash and work normal from recovery in cwm backup/recovery so i downloaded Da_G's stock odin tar and when i factory reset after completing it was the same deal. the starting screen i can't click anything and it is soooooooo slow to react. i tried odin'ing da_g's root also and i have CWM recovery too. now i am trying to transfer old recovery's from my computer to flash in CWM and hope one gets phone at least function properly so i can go from there.
I'm freeeakin' out man!
i think Alpha II might have saved me!! fingers crossed. so far i can do everything normal. time to investigate
Make sure u also reflash stock radio... that can interfere with a lot of stuff

Am I looking at a warranty return here? A quick look appreciated.

Hey guys this is where I am with this issue. Kind of new to Android so forgive me if something is obvious and left out.
Bell Galaxy Note, unlocked via unlock code.
Please note that before I ever flash a new rom, I do a factory wipe, wipe cache, wipe dalvik..3 times first, then I redownload and install from Play
1. Noticed that my phone on Flappjaxx's rom was acting flaky. (ie FCs more than usual). This rom worked fine for a few weeks.
2. Tried CM9 via Rom Manager. Phone still a bit flakey.
3. Used CWM Recovery to return to FJ's rom which I made a backup first.
4. Phone even more flakey (ie. noticed some apps could get the internet, others could not. Phone would FC as well every time).
5. Tried clearing cache, dalvik, and fixed permissions. FJs rom still flakey (at this point 2-3 attempts to fully boot). Factory reset and caches cleared again but still the same.
6. Used Odin to flash the Bell stock system, recovery, and boot from this thread: http://forum.xda-developers.com/showthread.php?t=1599127
Did a factory reset using the stock recovery after this was flashed as well.
7. Having the same issues on the stock rom as I had on FJs rom and CM9.
8. I was eventually able to get the phone to allow me to see the baseband version before it rebooted (took a few tries) and I see the baseband is still UCLF6. I thought the baseband would have been reset too but I guess not.
Is there something else I should do? Will popping CWM recovery on there again and flashing another modem fix this?
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
This happens sometimes. You just have to find and flash the stock modem through odin to get it 100 percent out of the box.
As far as the warranty return, no one would allow it because you have no way of proving that the problems with the phone are not directly related to your modifications to the device even if they are not.
However, I would suggest flashing the stock modem and then reformatting your device through kies as a last resort. If this does not still work, I would suggest (although never used) the flash counter reset zip once youre on stock and sending it in for repair.
Hope you get it up and working
welchertc said:
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Understood about warranty of course.
- not restoring anything...as mentioned, everything is always set up from scratch, including all apps from Play store.
- I'm trying to get back to stock, and everything looks stock except that my baseband reads UCLF6, which I assume is not stock GB. I have tried flashing the modems, kernals, and roms found here http://forum.xda-developers.com/showthread.php?t=1506330 and here http://forum.xda-developers.com/showthread.php?t=1599127
This is why I am asking if my hardware seems defective, or if there is something amiss in what I am trying to do (if I am seeing UCLF6 in my baseband, I am assuming I am missing something).
Last attempt to get rid of the UCLF6 baseband I downloaded this modem: http://forum.xda-developers.com/showthread.php?t=1506330 , did a reset, wiped caches, and still showing UCLF6.
Don't know what I did differently, but I tried pterry30's modem and flashed via CWM (I could not find an Odin modem tar) and my phone seems normal now (but very stock) and I got the 'mugla' version of the modem listed in my system settings.
Thanks for the suggestions...hopefully its really fixed. Since I went through all this trouble I'll try Bell's ICS update.
Problems like this are great learning tools...but a bit stressful lol
Happy all is well. Good luck.

Reverting to Stock Issue Inquiry

Hi am obviously new to these forums but not new to Android/Samsung development so I had custom roms installed on my I777 so I needed to revert back to stock in which I flashed a leak which apparently changed the pit so I was able to download all the stock files for Odin3 for my device in the Download Repository. My question is there any reason why my device just doesn't act as accurately as I though I remembered it being when it was stock. Is there any ultimately right process for flashing because most instructions including my own are all different, some say wipe cache and data first and battery pull then download mode Creepys says its not neccessary until after the flash as does ZedoMax. I've followed all of them and haven't understood why there is no ultimately right process if there is one at all using odin3 and one-click. And if this is the case what could possibly be going on with the force closes and hangups I'm getting? If someone is willing to take the time to help me with all these questions I'd greatly appreciate it.
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
Dunno if it'll help, but it won't hurt..
Boot into recovery and"fix permissions". *Should* help with the FC's - oh, and delete everything from your memory that you read on galaxys2root (zedomax). Whatever you've read from creepy, COMMIT to memory. The guy is ace!
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
GalaxyHackster85 said:
I don't see the option for fix permissions first of all is that a cwm option? Also I know creepy is one of the best but what's wrong with gs2root? And I appreciate the help but which process is the ultimate right way? Do you flash pit,PDA,modem all together or is that incorrect?
Click to expand...
Click to collapse
I don't remember for sure, but I don't think fix permissions in available in stock 3e recovery. It should be available in just about any custom recovery.
GalaxyS2Root, and it's owner who goes by the screen name zedomax, is a strictly commercial endeavour, designed to make money but not necessarily designed to help people. I think zedomax is a developer, but I'm not sure how good he is. Many of the offerings on that web site, and presumably on his dozens of other web sites for other phones, cause problems for folks, bricking phones, and other things. Further, he takes the work of developers here and posts their work on his sites without giving any attribution or remuneration. He's spread way too thin keeping up with all his various sites, and/or he just doesn't seem to care if his offerings cause problems. We've had so many people come to this forum with various problems due to GalaxyS2Root that when the name is mentioned, everyone is on it right away.
I would only use the pit to repartition on the I777 when everything else fails. It can be a help, but you should be sure that you are going to have a successful flash before you use it, since it repartitions the memory space of the phone.
Most firmware for the I777 has everything in one .tar file, which you put into the PDA slot. If you are flashing just a param.lfs or just a sbl.bin, then that goes into the PDA slot. You can also flash a modem at the same time as the rest of the firmware, using the Modem slot, but most firmware packages have the modem in them too.
So essentially the oneclicks are absolutely the only thing I need in order to ensure a 100% successful restocking? And if so am I always suppose to factory wipe/cache then battery pull (3e recovery doesn't have a power off option)? The reason why I ask so many questions is A. A lot of peoples data isn't accurate as you've stated and its better for me to have as much data as possible when potentially getting into these things. And B. I've been flashing my S2 like a madman with OCD because as soon as I'd get a force close or any sort of hiccup happened I assumed it was because I flashed it wrong when in fact I was just following some of the directions that I've aqquired from here or GS2Root and so far everything has flashed with the same results but as its been forever since my phone was purchased so I can recall if these are just the normal hiccups that come with the inconsistancy of android. So to me I'm just trying to.make sure that I'm doing things absolutely correct.
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
creepyncrawly said:
There is lots of material here to read. You can learn a lot about your phone by spending some time reading.
Click to expand...
Click to collapse
And you are absolutely correct and I have your guide bookmarked but with so many people having different takes on how to return to stock can you point me in a direction that's the completely right way of flashing your pit and attempt software. Or is your guide with one click the most surefire way to do it? Like I said before I'm a bit OCD when it comes to my phone so whenever I get a little hiccup I can't tell if those are just normal for I777 software or is it something I've done wrong which I probably haven't but it still worries me.
If you havn't done something absolutely ignorant, i.e. flash firmware for a different phone, then you should just use my guide with the linked one-click downloader. That package does not contain bootloaders or param.lfs. Those (the bootloaders and param) will always be good, and not needing replaced, if you only flash firmware from these forums and never flash leaked firmware (which usually contains bootloaders.) There should never, ever be a reason to use a pit file. As I said before, the phone has to be pretty seriously screwed before you need to repartition, and then it should be the absolutely last thing you try.
And inform yourself before you do any actual flashing. You should know exactly what you are doing to your phone, and also know what the remedy is before you do it. That way, you can avoid doing something stupid. If you really want to learn about your phone, read at least a little bit from the forums here every day for a few months, get involved in the discussions, and before you know it, you'll be one of the helpers.
Thank you so much for all of your prompt replies, I have been using the data from this site for quite some years now but never ran into any issues which required me to create an account (although I have wanted to), but for s**ts and giggles let me just say that due to the few hiccups I encountered and not knowing what would have caused them I have already flashed the pit and repartitioned as well as flashed the oneclick w/ bootloaders and param. Now asside from the few force closes that I ran into and the one time I bricked it and brought it back to fully functional is there any harm to the flashing of those tools that I've already done so far. Is there any negative side effects of what I've done that I may not be seeing or is it a case of well "there in the repository so theyre safe as long as I've flashed them correctly". And if so are these few force closes just everyday hiccups that every version of Android experiences and that I'm just overthinking it and it's just been a case of my ocd kicking me in the ass?
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
colorsharpkid said:
i did zedo then s2 unlock then aokp then siyah kernal change forgot to do triangle away then tryed a ota update messed up rom cwm messed up then i just did zedo again to get cwm again then i did aokp again then ran triangle away then i return to stock backup after root then odin flash for stock non root then i took stock and did ota update to 2.3.6 i dont think we will ever get 2.3.7 because google wallet is on 2.3.7 and we cant have it correctly .....on reboot it hangs so i did 3e wipe and cache delete reboot all has been good since batt has been outragously long on uckk7 but after ota update it shows as uckk6 i used a non rooted file maybe u used a rooted return to stock file ?anyway file i used was I777UCKH7-CL503881-No-BL as stated just used pda slot .....idk after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and do it all over again i honestly just miss the torch feature and the easy brightness slider on the pulldown
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Honestly, I have no idea what you just said, or what you're asking.
qwertyaas said:
Honestly, I have no idea what you just said, or what you're asking.
Click to expand...
Click to collapse
Me either, sometimes punctuation goes a long way
Sent from team Pirate! Using Tapatalk 2
colorsharpkid said:
i flashed zedo then used s2 unlock. then i flashed aokp and siyah kernel. I forgot to do triangle away (because I used zedo) and then tried an ota update. This messed up my rom because I couldn't access cwm. then i flashed zedo again to get cwm back. After that i flashed aokp again and ran triangle away.
I then did a return to stock backup after root and an odin flash for stock non root. While on stock i did an ota update to 2.3.6. (some nonsense about 2.3.7 and Google wallet)
.....on reboot it hangs so i did 3e recovery wipe and wiped cache. Reboot has been good since. My batt has been outragously long on uckk7!! But, after an ota update it shows as uckk6 i used a non rooted file, maybe I should have used a rooted return to stock file?
Anyway, the file i used was I777UCKH7-CL503881-No-BL as stated and i just used pda slot .....idk, after all the custom roms theres a distinct feeling in knowing your stock again but have the ability to go and flash custom ROMs all over again. i honestly just miss the torch feature and the easy brightness slider on the pulldown.
im getting h+ but it doesnt seem like true h+ speed and i also lose h+ while holding the phone. im waiting for this to change with tmobile and thier 1900mhz i hope it does or ill be looking into whats going on with the modem maybe
Click to expand...
Click to collapse
Fixed... I think. And "zedo" refers to the sh;t zedomax has on gs2root.
Clay
Team Pirate
Sent from my Buttery Pink SGH-i777
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
creepyncrawly said:
The danger in using those files is in the flashing. If a flash is inadvertantly interrupted or goes bad, then it can hard brick the phone. Once the flash is complete and successful, then you're fine. There are no side effects.
Force closes, and other anomalies can be caused by conflicting data is the system and data partitions. They can also be the result of bugs in the firmware distribution or in any of the various applications. To eliminate the first cause, following all the best proceedures when flashing such as wiping first, etc eliminates the possibility that the fc's are caused by improper proceedure.
With proper installation proceedure, and with a stable firmware, and with robust applications, you should experience little to no fc's.
Click to expand...
Click to collapse
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again. I also had on flash that was the 2.3.5 leak but flashed over that and it was fine. Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Sorry for double post but I wanted to make sure my questions are targeting creepy seeing as this thread is getting a bit off topic.
GalaxyHackster85 said:
Ok thats where I'm a bit concerned because I ran into an issue before where I was going to do a flash and it choked up on me (mind you it was a pit and tar flash repartition) and it bricked on me but I was able to reflash the same process again once the pc was ok again.
Click to expand...
Click to collapse
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I also had on flash that was the 2.3.5 leak but flashed over that and it was fine.
Click to expand...
Click to collapse
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
Now with that said the phone flashed well, and now it runs generally like it should have in the first place. But my question is did that fluke flash do anything negative to the device behind the scenes that will never be ok again?
Click to expand...
Click to collapse
I don't know how to look behind the scenes... but I would think your phone is fine.
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
OK great info and definitely a relief but just out.of curiousity what are the repercussions of a bad bootloader flash or an improper pit flash? And how would we know that whatever pit or bootloaders flashed weren't for our phone or are corrupted data?
creepyncrawly said:
As far as I know, that would be fine. Someone with dev experience could look into partition sizes on the phone, and see what actually happened. As long as the firmware is functioning correctly, then I would assume the partition sizes are correct.
I guess you didn't get a crippled bootloader. That was the main problem with some of the leaks.
I don't know how to look behind the scenes... but I would think your phone is fine.
Click to expand...
Click to collapse
And trust me I absolutely appreciate all the responses the answer to my last question is all I needed to know to truly understand how the i777 works and functions and I commend you for that. I felt that trying to find all these answers would have been trying to find a needle in a haystack.
Also regarding the repartioning I just wanted to make sure that everything is correct in terms of space. My device is showing only 1.89gb of "Device Memory" at the bout of the "Storage" screen is this normal I though it was higher before but I cant quite remember.

[Q] Can't get this thing running.

Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.

Categories

Resources