Related
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...
So i flashed a p4 rom and apparently it was not intended for my p4vzw. i know its sad. anyways no worries, got it back on akop, but now i have a unknown baseband. I am searching and searching but i can't seem to find any files on this.
so questions are
1 anyone know if there are radio files.
2 or do i have to get it back to stock and then root again.
thanks in advanced
bensl84 said:
So i flashed a p4 rom and apparently it was not intended for my p4vzw. i know its sad. anyways no worries, got it back on akop, but now i have a unknown baseband. I am searching and searching but i can't seem to find any files on this.
so questions are
1 anyone know if there are radio files.
2 or do i have to get it back to stock and then root again.
thanks in advanced
Click to expand...
Click to collapse
The easy way would be going back to stock, the other way, i know that you can find modems on http://droidbasement.com/db-blog/?p=3008
One way to fix it
I've had similar issues lately playing around with installing CM10.1 and the modem getting messed up. I did use adb to make a modem.bin backup from stock ICS, but then could not figure out how to flash it. In the end what I did is flash the original stock ROM. Search for STOCK VZW Galaxy Tab 10.1 4G LTE Factory Firmware PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar
That will put it back to the original Gingerbread factory image. It will have to go through multiple OTA updates to get back to ICS. I know this is a pain to do, but my nandroid backup of the OTA updated stock ICS when restored did not restore the modem, and the modem.bin I created from instructions at mygalaxyway.blogspot.com/2012/09/how-to-share-your-nandroid-backup-and.html was kind of useless.
Aethera said:
I've had similar issues lately playing around with installing CM10.1 and the modem getting messed up. I did use adb to make a modem.bin backup from stock ICS, but then could not figure out how to flash it. In the end what I did is flash the original stock ROM. Search for STOCK VZW Galaxy Tab 10.1 4G LTE Factory Firmware PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708.tar
That will put it back to the original Gingerbread factory image. It will have to go through multiple OTA updates to get back to ICS. I know this is a pain to do, but my nandroid backup of the OTA updated stock ICS when restored did not restore the modem, and the modem.bin I created from instructions at mygalaxyway.blogspot.com/2012/09/how-to-share-your-nandroid-backup-and.html was kind of useless.
Click to expand...
Click to collapse
Thanks. But i did the factory image and I still get unknown radio. Odin flashed successfully yet no modem.
I'll flash again maybe it was a fluke
SCH-i905?
You have an SCH-i905?
Yea I do. No matter how many times I flash the factory stock in Odin. The radio doesn't stick
does that mean id be able to use the p4wifi rom? i dont care about the radio files i just want one of the p4wifi roms...
Id love to have the ics radio files to flash too. when I odin the stock image it fixes nothing for me.
So basically I found that my csc file is gone. The Lte factory image doesn't include it. I bet it's on purpose.
What ever the case if we get a csc file for the tab and flash it then flash radios or flash firmware then csc it should work.
That's my guess at least. What's weird is there is no factory Firmware to be found on the Samsung site for the i905. Not sure why.
bensl84 said:
So basically I found that my csc file is gone. The Lte factory image doesn't include it. I bet it's on purpose.
What ever the case if we get a csc file for the tab and flash it then flash radios or flash firmware then csc it should work.
That's my guess at least. What's weird is there is no factory Firmware to be found on the Samsung site for the i905. Not sure why.
Click to expand...
Click to collapse
Please let this happen please
So i am still researching this.
I am going to write Samsung mobile to see if they will release the firmware for the tab. I am sure it has to do with Verizon not wanting anyone to keep that i905 that rooted it or flashed the stock firmware.
I can't be the only one that is missing the CSC file after an odin stock firmware flash. and i think its very odd that samsung has every firmware i can think of except the i905.
Im just taking stabs here.
I am also assuming thats the problem, thats the one part of the /system that's missing.
it would be cool if anyone had a i905 with lte and posted their CSC file.
how would i go about requesting that? just post
"[request] CSC file for i905 galaxy tab 10.1"
i have never asked for a request before.
bensl84 said:
So i am still researching this.
I am going to write Samsung mobile to see if they will release the firmware for the tab. I am sure it has to do with Verizon not wanting anyone to keep that i905 that rooted it or flashed the stock firmware.
I can't be the only one that is missing the CSC file after an odin stock firmware flash. and i think its very odd that samsung has every firmware i can think of except the i905.
Im just taking stabs here.
I am also assuming thats the problem, thats the one part of the /system that's missing.
it would be cool if anyone had a i905 with lte and posted their CSC file.
how would i go about requesting that? just post
"[request] CSC file for i905 galaxy tab 10.1"
i have never asked for a request before.
Click to expand...
Click to collapse
this will get you sorted out:
http://forum.xda-developers.com/showpost.php?p=19275562&postcount=1
http://forum.xda-developers.com/showpost.php?p=31600421&postcount=1
pershoot said:
this will get you sorted out:
http://forum.xda-developers.com/showpost.php?p=19275562&postcount=1
http://forum.xda-developers.com/showpost.php?p=31600421&postcount=1
Click to expand...
Click to collapse
I have done that. When i flash the stock firmware i still don't have a baseband and i can't do any updates.
I have no problem rooting. I just don't any radios.
maybe i am missing something here but once i flash back to firmware stock the radios don't stick so when i when boot up i get unknown radio and no updates are ever found.
bensl84 said:
I have done that. When i flash the stock firmware i still don't have a baseband and i can't do any updates.
I have no problem rooting. I just don't any radios.
maybe i am missing something here but once i flash back to firmware stock the radios don't stick so when i when boot up i get unknown radio and no updates are ever found.
Click to expand...
Click to collapse
I have the same problem. I tried flashing modem it works fine but when I try flashing lte_modem.bin I get an error in red writing and it doesn't flash. I've tried this with every version of Odin. I used the modem files from the full Odin image. I think it was EG01. I download it multiple times nothing has worked.
k,
so if anyone is interested, i finnaly got around to digging and came up with a processes to get the modems back. its technical and i am sure i am doing something wrong cause i can't get it to get on the network. could be a lte chip at this point. anyways.ill try tomorrow
it must be rooted. go to dev settings and check debug and root accsess: apps and adb.
then download EFS professional. go to restore and restore. nothing will change.
flash original firmware with odin.
once it installs you can see your radios... this it where it stops. I can't get it to access LTE. it has correct time and knows its on the verizon network. but no lte.
I then rooted to see if i could carry my radio files to 4.2.2 and i can't. radio unknown. tomorrow i am going to go to VZW and ask them if its a bad sim. will update tomorrow or when i get around to it.
Update:
So it was a bad sim. once a new one was put in i got LTE but now it wont update. Ha one problem after another. So now i can't flash 4.2.2 cause i loose radio. I believe you have to be on ICS before you can flash to 4.2.2, anyways its been a few days and it still thinks its up to date.
So now i need to know how to force an update..... will update if anything else happens
I am at my wits end and hopefully one of you can help.
The phone in question is is the AT&T Galaxy S2 SGH i777. It was running a jellybean ROM and there were problems with the GPS and google maps not working at all about four months ago. Not sure what happened. I went through the usual process of putting a ROM on the SD card, wiping cache/davlik and installing, then installing the gapp.apk for that rom. Everything was fine. Except wireless. Wireless would not connect. Just wouldn't do it. Googled forever, found no real solution. Thinking it was the rom I reinstalled. Wash rinse repeat. Same issue. Thinking it was a bad rom I proceeded to go through about six more roms. Same issue. Four hours later I resolved to unroot, take it back to stock. Took it back to stop with no issues. Wireless worked just fine. Everything was great. Rooted it again with the stock gingerbread. Wireless worked fine. Made a backup of the rom and was feeling lucky so I installed the Carbon ROM from the Sept 29th post on galaxys2root.com (I don't know if you guys allow linking here) and the gapps from that post. I boot. Everything is looking fine....yet the wireless doesn't work. This has been consistent across every rom I installed. I am quitting for the night.
It is currently running android 4.3, kernel version 3.064-CM-gbc8f4c9 (if that helps). The phone service is fine and makes/receives calls/texts just fine. No other blaring issues. Worth pointing out: all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect.
I had this phone for years (girlfriend has it now) and Rom'd it many times with next to no issues, especially not with wireless. I don't understand why it was working fine on a JB rom and trying to change rom suddenly screwed the wireless.
I am literally at my wits end and it's probably the result of me being an idiot somehow and missing something. Can anyone suggest a fix?
God bless in advance.
fifthmanstanding said:
[...]all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect. [...]Can anyone suggest a fix?
God bless in advance.
Click to expand...
Click to collapse
My advice is to avoid downloading ROMS from galaxys2root.com
If you want the insider scoop, keep up at xda or at each group's G+ community.
if you want:
-Carbon; get it from: http://download.carbon-rom.com/?dir=./i777/nightly
-Cyanogenmod; get it from http://download.cyanogenmod.org/?device=i777
-Omni; get it from http://dl.omnirom.org/i777/
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
cyril279 said:
My advice is to avoid downloading ROMS from galaxys2root
If you want the insider scoop, keep up at xda or at each group's G+ community.
The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)
Happy Flashing
-Cyril
Click to expand...
Click to collapse
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
fifthmanstanding said:
So would you suggest I revert back to the rooted gingerbread image and go from there?
I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?
Click to expand...
Click to collapse
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
creepyncrawly said:
You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.
Click to expand...
Click to collapse
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
fifthmanstanding said:
Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.
Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.
Click to expand...
Click to collapse
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
creepyncrawly said:
There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.
Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.
And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.
Click to expand...
Click to collapse
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
fifthmanstanding said:
I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums
Click to expand...
Click to collapse
hint: http://forum.xda-developers.com/member.php?u=2916435
cyril279 said:
hint: http://forum.xda-developers.com/member.php?u=2916435
Click to expand...
Click to collapse
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
fifthmanstanding said:
Yeah I'm an idiot. I literally just saw that in the signature.
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
cyril279 said:
We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.
Click to expand...
Click to collapse
I agree.
Which links?
I read through the notes on the repository:
There is always some risk involved when flashing bootloaders and Param.lfs. Please don't flash this unless you absolutely need to.
"This is the complete stock UCMD8 Binaries downloaded from samfirmware at sammobile.com. Please note, this package contains boot.bin, sbl.bin and param.lfs, plus cache.img, factoryfs.img, hidden.img, modem.bin and zImage.I777UCMD8 Full Odin Flashable tar: I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z 427.02 MB (Contains I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5)
(MD5: 307cc8fcbb8f220d3ae75d387569da40)"
And I'm downloading the file now. I've used odin before so I assume that goes by the standard process ( download mode, open, pda, select file, hit start, wait, finish) and then I went here http://forum.xda-developers.com/showthread.php?t=2130276 and he says "Version 1.3: Add Aragorn and Legolas exploits" so I assume based on Creepy's previous statement that's the one I need. I would download the apk and run it.
What am I missing?
Yeah I just installed the tar file using odin and before I even get to rooting process, wireless isn't working. This time it sees the network, password goes in as usual, it attempts to obtain IP address and says that forever. Never connects. Then goes back to scanning. Then attempts to connect again. No dice. No other device in the home has this issue. I'm out of ideas.
Edit:
Yeah I just tried again, using odin, took it back to stock, wireless works, using odin took it to stock with root, wireless works, using the tar file located here http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 took it to I777UCMD8 Stock Binary. Wireless is not working.
Does anyone have any insight? I've got a pissed off girlfriend an a perment dent in my desk from my head.
update: took it back to i777 UCMD8 with odin, just for kicks I tethered it to my nexus 4. Works fine. Turned off data, disconnected the wireless just to be sure. Turned it back on. Working fine. Still will not connect to my router. This would imply there is a router issue and I have less knowledge of how/why that would work. Thoughts?
fifthmanstanding said:
So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here
http://forum.xda-developers.com/showthread.php?t=2130276
and run it?
Click to expand...
Click to collapse
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Edit: Failed to click on the latest page of the thread before I posted this. Yes, it sounds like an issue with your router, perhaps. So find other routers and test the wifi. If that's the issue, then the other roms will probably also work on a different router.
creepyncrawly said:
The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.
I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.
Click to expand...
Click to collapse
Yeah I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
EDITosted before I saw your edit
fifthmanstanding said:
Yeah as stated, I'm familiar with odin. I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.
This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.
The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?
At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.
Any thoughts?
Click to expand...
Click to collapse
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
creepyncrawly said:
Apparently you are moving too fast, with too little information.
On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.
To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.
Click to expand...
Click to collapse
Fair enough.
I've downloaded the AJK no swap from here http://forum.xda-developers.com/showthread.php?t=2110542
I've downloaded Mobile Odin lite and am going to work on that.
Assuming it all works out and I get to make a backup. Where to next? This rom is terrible. What do you recommend for a jellybean experience as stock nexus 4 as possible.
Yeah the ajk no swap 4.9 is giving me a consistent java error that kills the download. I attempted to move it to the sd card and open in odin lite but am not seeing it on the card. Am I doing something wrong?
Edit. I tried connecting the phone to the computer and opening in explorer, following directions from here http://forum.xda-developers.com/showthread.php?t=2197157 , created a folder and attempted to drop the zip in there and it's not letting me drop files to the phone. nor to the sd card.
Edit 2: suddenly file xfer is working again. I dropped the .zip to the new folder on the internal and also created a new folder with the boot, METAINF folder and system folder that shows when you unzip. It's not detecting the zip file so I assume you're supposed to select the Boot file. I select it. Nothing happens.
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
fifthmanstanding said:
Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?
Click to expand...
Click to collapse
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
creepyncrawly said:
Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.
If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.
Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.
Click to expand...
Click to collapse
Ok by the looks of it that worked. Thanks for that.
In terms of roms I'm looking for something stable, jelly bean and non-touchwiz. As close to possible as nexus 4's jelly bean. Nothing comes to mind?
Edit: apparently the home key now no longer works properly, hitt it brings up a selection box and selects whatever is the left most side whether it's 'apps' tab or an icon on the home screen. Also the search magnifying glass soft key doesn't work, same function as the home key it seems.
Edit 2: And the wireless is no longer working. Was working fine before flashing the kernel. Put the phone directly on top of the router. It shows the network, allows for password input, says 'connecting' and never ever connects. Then it drops and goes to 'out of range'...sitting directly on the router. Just for kicks, like last time, I enabled the hotspot on my N4 and it connected fine. I attempted to connect to the router again and it does the same...connecting and drops to out of range. Sigh.
Hi,
I got my hands on an i9300 that the previous owner had broken while trying to do a sim unlock.
I've tried flashing various ROMs and recoveries using Odin (1.85 and 3.07), and also from within the recovery.
I'm not able to determine if the EFS partition is completely intact, but I believe it is.
So far I have tried flashing the rescue firmware (http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6), various stock firmwares, resurrection remix, android revolution hd, and a few others.
I have philz recovery installed at the moment, and have tried the latest CWM as well.
I've even tried using kies to do an emergency recovery, but this also failed.
No matter what I do, I'm unable to make the phone boot up.
I do have adb access to it.. Anyone got any suggestions for what else I can try?
In odin mode it *does* display the model number, so from this I believe that it is safe to say that the emmc is still ok.
Any thoughts or suggestions?
Cheers!
Try the latest threepart stock firmware for the region (CSC) the phone originally comes from and flash firmware including PIT file (re-partition is ticked then). This solved my booting problems in such cases.
Edit: maybe also the bootloader is f***ed, does it start up to the Samsung logo or nothing at all?
If nothing at all it might be the bootloader, in this case there is SD-Bootloader-repair-files floating through the net, allowing you to repair bootloader just from your external SDcard - i9300 only.
Benko111 said:
Try the latest threepart stock firmware for the region (CSC) the phone originally comes from and flash firmware including PIT file (re-partition is ticked then). This solved my booting problems in such cases.
Edit: maybe also the bootloader is f***ed, does it start up to the Samsung logo or nothing at all?
If nothing at all it might be the bootloader, in this case there is SD-Bootloader-repair-files floating through the net, allowing you to repair bootloader just from your external SDcard - i9300 only.
Click to expand...
Click to collapse
I'll see about getting the latest 3 part stock, though that seems fairly similar to the rescue firmware I linked to - it includes a pit file.
Shall give it another go though
I do get the samsung logo/text, as from a standard boot, and then it launches straight into recovery.
Cheers,
EqUaTe
EqUaTe said:
I'll see about getting the latest 3 part stock, though that seems fairly similar to the rescue firmware I linked to - it includes a pit file.
Shall give it another go though
I do get the samsung logo/text, as from a standard boot, and then it launches straight into recovery.
Cheers,
EqUaTe
Click to expand...
Click to collapse
Ok, so bootloader is fine. This seems to be strange, how can you have ADB access if you can't boot up thus USB debugging's not enabled?
I had a similar disaster lately with Note 3, a real pain in the a** updating to KK. Also the 'firmware encountered blabla...' message, I got this fxed by flashing latest CWM right after the stock firmware flash, then it would finally boot.
Your case is different though since you even do get into recovery. Deep down I'm positive you just need to find the correct PIT resp. 3-part stock ROM.
Benko111 said:
Ok, so bootloader is fine. This seems to be strange, how can you have ADB access if you can't boot up thus USB debugging's not enabled?
I had a similar disaster lately with Note 3, a real pain in the a** updating to KK. Also the 'firmware encountered blabla...' message, I got this fxed by flashing latest CWM right after the stock firmware flash, then it would finally boot.
Your case is different though since you even do get into recovery. Deep down I'm positive you just need to find the correct PIT resp. 3-part stock ROM.
Click to expand...
Click to collapse
philz recovery has adb support built in, that's how I've accessed it. I believe CWM used to, but it doesn't seem to anymore.
Do you know which firmwares are likely to have the PIT file separately? I've got one downloading at the moment, but no guarantee it'll have the various files individually. Most of the ones I've come across are AIO files.
EqUaTe said:
philz recovery has adb support built in, that's how I've accessed it. I believe CWM used to, but it doesn't seem to anymore.
Do you know which firmwares are likely to have the PIT file separately? I've got one downloading at the moment, but no guarantee it'll have the various files individually. Most of the ones I've come across are AIO files.
Click to expand...
Click to collapse
Alright, never used philz 'cause I always loved TWRP, this could be a reason though
Well, they are hard to find indeed. On a quick random search I found this JB ROM:
http://uploaded.net/file/p8e4pasy
Though I must say I always had best results when repairing persistent devices with older firmwares, so I got used to finding the exact
version installed when factory delivered, when issues are fixed updating is no problem.
Have set that file downloading, and have also grabbed TWRP.
Will give it a shot when I get home from work tonight. Cheers for your help so far Sometimes it helps just to have another set of eyes on these things!
Balls.. That link is a passworded zip. Don't suppose you came across the password for it?
EqUaTe said:
Balls.. That link is a passworded zip. Don't suppose you came across the password for it?
Click to expand...
Click to collapse
Ok, found the password.. Extracting a bunch of zips atm, fingers crossed one will help!
Benko111 said:
Alright, never used philz 'cause I always loved TWRP, this could be a reason though
Well, they are hard to find indeed. On a quick random search I found this JB ROM:
http://uploaded.net/file/p8e4pasy
Though I must say I always had best results when repairing persistent devices with older firmwares, so I got used to finding the exact
version installed when factory delivered, when issues are fixed updating is no problem.
Click to expand...
Click to collapse
So, I've now flashed that 3-part ROM, sadly with no joy - it does the same.
It has made me go back and look at your earlier comments, and made me wonder if the logo we each refer to is the same one, so I'm attaching an image..
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
EqUaTe said:
So, I've now flashed that 3-part ROM, sadly with no joy - it does the same.
It has made me go back and look at your earlier comments, and made me wonder if the logo we each refer to is the same one, so I'm attaching an image..
Click to expand...
Click to collapse
It is indeed what I meant. If it was the bootloader it most likely wouldn't do a thing anymore.
But k-semler above this post is absolutely right, I forgot to pay attention to what model size you've got?
Of course PIT is different for 16 or 32GB model.
Just in any case, I attached two PIT from my collection, DBT region for 32GB model, you've got a 16GB one above (use his firmware with that), flash the size according to your model and try once again. Eventually it should work.
If your phone was branded originally, find the original branded firmware and try as well.
That's all I can think of right now.
Benko111 said:
It is indeed what I meant. If it was the bootloader it most likely wouldn't do a thing anymore.
But k-semler above this post is absolutely right, I forgot to pay attention to what model size you've got?
Of course PIT is different for 16 or 32GB model.
Just in any case, I attached two PIT from my collection, DBT region for 32GB model, you've got a 16GB one above (use his firmware with that), flash the size according to your model and try once again. Eventually it should work.
If your phone was branded originally, find the original branded firmware and try as well.
That's all I can think of right now.
Click to expand...
Click to collapse
It's the 16gig model, will have another go this evening
k-semler said:
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Click to expand...
Click to collapse
I'm curious, which version of Odin did you use when you fixed yours?
Interestingly, while I've had it available before, the bootloader update tickbox isn't available on 3.07/3.09 at the moment, stays grayed out..
Going to give 1.85 a whirl
So flashing with 1.85 has resulted in the same thing.. Wondering if it may actually be a 32gb one.. I don't think it is, but at this point I have no idea.. Are there any identifiers that distinguish it on the unit itself? FCC ID, SSN, etc.
Fairly sure it's not a 32gb as it hangs flashing if I use that pit.. Trying another flash at the moment.
So no joy with this so far.. Getting a bit annoying really, tried quite a few combinations now..
Fairly certain at this point it's a 16GB model, using the 16GB PIT I can flash other ROMs, but no joy on actual resurrection of the device.
Odin logs seem fine, with and without a bootloader update.. After the ROM flash, sometimes I get the Android with the spinning polygon for a while with a new progress bar, followed by a further reboot, and then the sick android (little red triangle coming out his chest).
All stock roms have the following text at the bottom (though the actual position varies from rom to rom as some of them have recoveries at much higher res than others):
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VOD
Successfully applied multi-CSC.
And yes, the typo is on the screen.. Appling.. Really?
Anyway, don't know if that is normal (while I've used other s3's, I can't remember what they showed with stock recovery as I rooted them pretty early on, and never really touched them again).
I can say I'm glad I still had the jig from my s2, as it makes getting into download mode much easier
I've tried several odin versions, different USB ports, different cables.
I can go through and provide details of the various ROMs I have downloaded, the majority of which are stock at the moment, and am happy to grab others if people think they may work..
Cheers,
EqUaTe
That's not nice, still busy with it... I must say, when I read the bit you wrote
After the ROM flash, sometimes I get the Android with the spinning polygon for a while with a new progress bar, followed by a further reboot
Click to expand...
Click to collapse
I thought yay, that sounds promising. That is exactly what happens after a successful stock flash. Also
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VOD
Successfully applied multi-CSC
Click to expand...
Click to collapse
is absolutely normal (incl. the spelling). The question is why does it not boot into system then? After a (what I consider) successful flash and then in stock recovery, have you tried a factory reset/wipe cache? Please try this urgently.
In my optinion you can stick to Odin 3.09, I could never confirm the reports of different versions working with certain devices, at least not with the new ones. Re-partition is forced and mostly greyed out when a PIT file is flahed with the ROM. Without PIT it should be not greyed out.
Benko111 said:
That's not nice, still busy with it... I must say, when I read the bit you wrote
I thought yay, that sounds promising. That is exactly what happens after a successful stock flash. Also
is absolutely normal (incl. the spelling). The question is why does it not boot into system then? After a (what I consider) successful flash and then in stock recovery, have you tried a factory reset/wipe cache? Please try this urgently.
In my optinion you can stick to Odin 3.09, I could never confirm the reports of different versions working with certain devices, at least not with the new ones. Re-partition is forced and mostly greyed out when a PIT file is flahed with the ROM. Without PIT it should be not greyed out.
Click to expand...
Click to collapse
I figured the spelling was normal, just a little disappointing Also thought it was normal that this appeared, but wasn't sure. Makes sense though.
I have tried a factory reset after pretty much every flash attempt, but will give it another go. Getting to the point where i'm tempted to try and do the sd card recovery, just to see if there is something fundamentally broken at that level.
I'm also downloading the latest ROM for the carrier (Vodafone UK) to see if flashing that here makes any difference..
Well, factory reset and wipe cache don't help. Other ROM won't be donwloaded for a bit, so will have to try it after work. grr.
so I eneded up installing crdroid successfully on an old S III i747 i had lying around following
https://forum.xda-developers.com/t/...-can-i747-m-compiled-by-alexenferman.4021787/ and about a hundred different threads on the internet but I got there and it worked but t-mobile wifi calling wouldnt so i put it aside. now att is offering a crazy deal to swap almost any samsung phone including the S III for an S22. so now i'm interested in returning it to stock rom. I thought it would be much easier , using odin and a factory rom but every time i use odin it starts to init the flash and they promptly stops. hard to tell whats wrong. i suspect some of the many things I had to do to get crdroid on there is making it sad. any thoughts on getting this back to factory would be appreciated.
right now i have both TWRP and CRDROID installed and its still working fine. i dont know if the newer kernel/filesystem crdroid is using is confusing odin version that is expecting much older kernel and layout. i THOUGHT odin would ignore all that but at this point I can't tell what odin is annoyed at. from what i can tell the error I'm getting can be caused by any number of things.
i can mount my phone in windows explorer so I think all the drivers and usb stuff is working.
some notes about my current state:
crdroidAndroid-7.1.2-20200102-d2att-v3.8.9, android 7.1.2, kernel 3.4.112
tried using odin 3.04 and 3.13.3, using I747UCDLK3_I747ATTDLK3_ATT
odin log shows
checking md5 successfully
firmware update start...
aboot.mbn
NAND Write Start!!
Complete(Write) operation failed.
and on the phone download interface
SW REV CHECK FAIL : FUSED 3 > BINAARY 0
i got this sorted. turns out i had version NJ1 last installed so thats what modem/bootloader etc were at.
since I had TWRP installed I found stock files with root here
Rooted UCUFNJ2 Stock ROM
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support. STOCK NJ2 Thread. http://forum.xda-developers.com/galaxy-s3-att/development/rom-d2att-ucufnj2-stock-rom-deodex-t3183267 Stock rooted...
forum.xda-developers.com
i was able to install the UCUFNJ1 file over the garbage i had. i then proceeded to wipe everything i could. i thought it was hanging on boot but i think i was just impatient. after 4 spins the att logo stops but its continuing to start fresh. not realizing this i ended up installing the stock recovery from TWRP so I could do a stock wipe. I was planning on doing this anyway. After that and after waiting long enough device booted to stock , i even tested it with my tmobile sim and confirmed i was talking to the network. after that wiped it again. the download boot still shows custom/warrenty bit 1. i started trying to good with triangle away but most posts still say it wont fix that in knox firmwares and I suspect att will be throwing this in the trash anyway. hopefully the drones that are paid to issue refunds for the new samsung which claims you can send in a galaxy SIII for wont care as long as it boots stock and works. guess we'll see. i know it was a long time ago but i cant thank enewman17 enough. all his work and files are still hosted here and enabled me to get this done. i hope whereever he is he's having a great day.