I finally decided to update my AT&T Galaxy Note this Sunday. I already had a root on GB, so I decided to update to a ROM with root. I chose bigfau's {ROM}{UCLF6} Official ICS Stock Odexed, Deodexed, Rooted, Zipaligned, CRT ROM for the Note. However, when I went to update via Odin, I found out that I needed CWM.
Therefore, I found a GB rom with CWM, and installed that via Odin.
Then the phone restarted. It started just as normal, and I placed the ICS ROM (see above) on the internal SD card. I then restarted to CWM (this was the first time I had started CWM on this phone). I went and installed the ICS ROM via CWM. Apparently it came out fine (according to the screen). So I went all the way up, back to the original menu.
I chose the reboot option.
It rebooted, and the Samsung logo appeared.
The logo disappeared. And reappeared with more brightness.
So far, still normal.
Then the screen went black. No buttons I pushed did anything, no matter how long they were held. Only a battery reset would let me do anything with the phone. I took out the battery and put it back in, and restarted it in download mode, then re-flashed it with GB. Nothing happened. I re-flashed GB w/ CWM. Then I went back to CWM and tried installing ICS again. Same thing happened.
I went around looking for some helpful post on AndroidAuthority and XDA. Nothing.
I've run out of ideas.
So today, I ask for help.
Any help leading to a solution is appreciated.
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
The file is zipped!
gregsarg said:
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
Click to expand...
Click to collapse
Thank you, however, the file from samfirmware.com is a zip file, which I believe I'd need CWM to install (Odin only accepts tar files, as far as I can tell). However, when I unzipped it, I found a .tar.md5 file and a dll. What should I do now?
For clarification, I can't access the internal SD without it functioning, and I don't have access to a microSD card.
Unzip the file you got. The .tar file is in there.
I already did that.
I already did that. Like I said in the previous post, it contains a .tar.md5 and a .dll. What should I do next?
(Thanks for the suggestion, anyways)
the .tar.md5 is called a tarball and has the pda file, csc file, and modem file. just put the tarball in the pda section of Odin3 and flash. Make sure Kies isn't running in the background. Reboot is checked but nothing else is.
Just getting back ...
Many thanks for jumping in ranger ....
It sounds like the OP has it now ??
Time will tell I suppose ....g
Related
Disclaimer: Ive searched and searched through the forums and archives and Ive hit a brick wall.
Ive read Vibrants are nearly impossible to brick, which is awesome, however I dont think thats the case here. I had originally went from my JI6 OTA update to Obsidian 4.2. and I wanted to try a new ROM. I remembered reading its a good idea to flash back to stock between ROM flashes, so thats what I was attempting to do. Well I just got a new computer, and reinstalled everything, but didnt even think to do the stuff for my phone for whatever reason, so I was without ODIN, the drivers, and my backups.
So I got to a point where I was going to just try it with ROM Manager. When I clicked the option to "Boot Into Recovery Mode/CWR", it went to the first boot screen (the one that says vibrant and samsung) and wouldnt do anything else. So I reflashed the firmware (the 513.pit) and it came back on (this happened a few times actually, but hey we learn from our mistakes, lol).
I recently reinstalled ODIN also, and I guess I used to have v1.3 and this was v1.7, and for some reason re-partition was pre-checked, and when I unchecked it, and hit start to reinstall the firmware, it checked itself, and it was to late, I didnt want to unplug it. After this it wouldnt do anything, but I managed to get it back into DL mode, and Im pretty sure I need to re-flash the stock software, so I found it, downloaded it, unzipped it and whenever I click the "PDA" button, the files 'kernal update, META-INF, and system' all show up, but its just the folders, no files.
Also, I did have the OCLF on there, but once I reflashed the firmware, and the phone booted back up the ext2 files were no longer installed, as it didnt give me the option to uninstall them, only to install them
So here I am now, with a phone that I can barely get into DL mode, and I cant get any ROM to come up in ODIN. Its always just the folders, no files.
Thanks in advance
If you dont feel like reading all that, heres the cliffs:
Phone went from 2.1/JI6 to Obsidian 4.2/JK2 with OCLF
Backups are gone
Accidentally re-partioned phone with ODIN while reinstalling firmware
Regardless of the ROM, only the folders show up, no actual files for the ROM.
Phone wont turn back on, right now.
Need help
Edit: Odin installs the pit file fine, the phone just wont boot. I guess if nothing else, I need to either know how to get the files to show up in the folder, or something. And before anyone mentions doing anything with adb, I have spent countless hours trying to get it to install and it never recognized the JDK and wants me to DL netbean, so thats kind of not a option right now
From what I can tell, you tried to load a ROM and it didn't take, then you tried ODIN and it didn't take.
I'm not 100% sure from your description of the exact steps you've taken. But you've only mentioned the 512.pit file for ODIN. There should also be an associated .tar file that you'll include in the PDA section. I'll see if I can find some detailed instructions on using ODIN and will edit my post once I find it.
EDIT: You can follow the instructions in this posting. http://forum.xda-developers.com/showthread.php?t=734475
EDIT2: The JI6 ROM you can get there (in .rar format) http://forum.xda-developers.com/showthread.php?p=8511186#post8511186
EDIT3: Youtube video showing the .pit and .tar files in ODIN. http://www.youtube.com/watch?v=AnY7P14JSWQ
Also, you can use any recent version of the stock files as long as they are .tar files. Some files (like in my second Edit) are compressed as .rar files, which will need to be uncompressed into a .tar file before you can use it with ODIN. I think WinRar, 7-Zip, PeaZip, and other tools will extract .rar files.
Most of the ROMs you'll find here on the forum are meant to be flashed through recovery, not through Odin. If you unzip a ROM and it has the META-INF, system, etc then it is meant to be flashed through recovery.
You need an Odin-flashable ROM. Get it here:
http://forum.xda-developers.com/showthread.php?t=734475
Then:
1. Open Odin
2. Select the .tar and .pit files from the above download
3. Make sure "Re-partition" is checked Use this only if you are flashing UVJFD from the link above
4. Plug in phone in Download mode
5. Flash it.
Thanks guys, its got JFD on there through ODIN and repartioned it, and were back to the goofy grass wall paper and the haptic feedback being turned all the way up!
I recently recovered my phone through ODIN and then upgraded to JI6 through Kies.....I wanted to re-root the phone and get it back to where it was before, but I'm having problems. I loaded the root file and put the update.zip in the root (not the avatar folder) and tried to update packages through recovery. I get an error message that says e:can't open /sdcard/update.zip no such file or directory. I checked the file type in both drives (avatar is on e: and everything else on g, the avatar folder shows a FAT file type, but the g: drive shows an unknown file type. I had received information to try a different update.zip file, but it won't change the error message I get when select update packages in recovery. What can I do? I've searched a lot of posts (and I risk a flaming on this one, I know), but I can't seem to find one that seems to follow my trail of getting to where I am at today. One last thing, when I was recovering through ODIN, i did not select repartition because i could not get the 512 pit file to populate in ODIN. Thanks to anybody who can help me (again).....
gtiryan said:
I recently recovered my phone through ODIN and then upgraded to JI6 through Kies.....I wanted to re-root the phone and get it back to where it was before, but I'm having problems. I loaded the root file and put the update.zip in the root (not the avatar folder) and tried to update packages through recovery. I get an error message that says e:can't open /sdcard/update.zip no such file or directory. I checked the file type in both drives (avatar is on e: and everything else on g, the avatar folder shows a FAT file type, but the g: drive shows an unknown file type. I had received information to try a different update.zip file, but it won't change the error message I get when select update packages in recovery. What can I do? I've searched a lot of posts (and I risk a flaming on this one, I know), but I can't seem to find one that seems to follow my trail of getting to where I am at today. One last thing, when I was recovering through ODIN, i did not select repartition because i could not get the 512 pit file to populate in ODIN. Thanks to anybody who can help me (again).....
Click to expand...
Click to collapse
ok....
are you SURE you are putting update.zip on the right sd card....it goes on the INTERNAL CARD ( the 16gb one )...
I'm pretty sure I am, this is the one where all of the apps and apk were stored previously?
ok then start over...
odin back to stock and re-root
ok, ODIN back to stock. No change for the update.zip. This time when I flashed I added the pit file, and also checked repartition. No change in anything regarding the message or anything from before. I have tried tyhe update before and after I went from JFD to JI6. I really have no basis to speak from, but it seems that the path from my e drive (avatar) to g drive (everything else), is where the problem is, or else I got a bad flash. They all look the same though. I assume I would need root to get anywhere other than JI6 anyway. Thanks again for your help with this. I do appreciate it.....
gtiryan said:
ok, ODIN back to stock. No change for the update.zip. This time when I flashed I added the pit file, and also checked repartition. No change in anything regarding the message or anything from before. I have tried tyhe update before and after I went from JFD to JI6. I really have no basis to speak from, but it seems that the path from my e drive (avatar) to g drive (everything else), is where the problem is, or else I got a bad flash. They all look the same though. I assume I would need root to get anywhere other than JI6 anyway. Thanks again for your help with this. I do appreciate it.....
Click to expand...
Click to collapse
ok....
1. when you Odin you are supposed to load both pit and tar files and not check repartition...
2.read that...http://forum.xda-developers.com/showthread.php?t=849028
3. are you trying to go to a stock JI6 ROM?? If so...why??
My suggestion:
Click on the Noob Guide (signature)
Download files
Load ODIN
Get phone in download mode
follow my instructions in the guide
You will then have a stock froyo leak + root
at that point I would backup, then flash something, maybe NeroV3 and then enable voodoo (if you like).
I don't see how the alt method could lead you wrong.
I apologize, I sincerely didn't notice anything that mentioned not to partition. Going forward, if I reflash through odin with the right pit and tar files WITHOUT checking partition, do you think I should be ok? As a note (if it even matters), all of my files and things were still in the internal sd card, although the new market is there from my old 2.1 rom. Not sure if it matters, just more information.
gtiryan said:
I apologize, I sincerely didn't notice anything that mentioned not to partition. Going forward, if I reflash through odin with the right pit and tar files WITHOUT checking partition, do you think I should be ok? As a note (if it even matters), all of my files and things were still in the internal sd card, although the new market is there from my old 2.1 rom. Not sure if it matters, just more information.
Click to expand...
Click to collapse
just follow s15274n's guide...he wrote a nice guide for noobs (no offense)...it'll walk u through going back to stock and you'll be ok...
Excellent information, but one question since I'm still learning. Not in the way I had hoped, but trial-by-fire.....If I download the leaked froyo with root, don't I need root access first. Also if I can flash this through ODIN, where does the update file go in the ODIN screen, do I need the 512 pit file, what about the pda, phone csc windows, what do i poopulate in those options, if any. I do bow to your experience and knowledge. I promise once I get back to where I was before I may never do this again! All this from trying to flash a new kernal that was supposed to be compatible with all bionix platforms (I was running 1.9 w/jac's ocuv). Thanks again....
gtiryan said:
Excellent information, but one question since I'm still learning. Not in the way I had hoped, but trial-by-fire.....If I download the leaked froyo with root, don't I need root access first. Also if I can flash this through ODIN, where does the update file go in the ODIN screen, do I need the 512 pit file, what about the pda, phone csc windows, what do i poopulate in those options, if any. I do bow to your experience and knowledge. I promise once I get back to where I was before I may never do this again! All this from trying to flash a new kernal that was supposed to be compatible with all bionix platforms (I was running 1.9 w/jac's ocuv). Thanks again....
Click to expand...
Click to collapse
(sigh)....
ok in Odin....as long as the phone is in Download mode...Odin has root access to the phone(technically) so just make sure you're in download mode...
Odin needs 2 files to flash a VIBRANT to stock...the pit and tar files...load the pit file in the PIT field and the tar goes in the PDA field..( i know its tricky) dont mess with any other settings...click start and WAIT
Odin is a flasher's best friend....learn to use it and you'll love it
In process now. I do like ODIN although yesterday afternoon, I would have rather taken a sharp instrument to the neck rather than use it. I preferred to use ROM manager or other methods. I know it means nothing to you guys that have experience, but this is a learning experience and one I am grateful for with all of the experience on these forums. I know you devs don't like these dumb questions, but sometimes kids just want to be professional football players but end up working in a supermarket instead....get back to you soon.
it said updating firmware then it's sitting on cache.rfs for about 5 minutes. no green loading symbol like when I flashed before. Not sure if I should unplug and retry....
waited about 20 minutes with it stuck at the cache.rfs line. Unplugged and retried. Same thing. I need to get a working phone at least for tonight. I tried one more time, but check repartition and it started loading completely. Maybe there's something wrong with one of the files? Not sure. Will update when I get home to my laptop.....
Use this version of ODIN (older versions are known to hang)
http://forum.xda-developers.com/showpost.php?p=8863820&postcount=138
The files you need to get the leaked froyo + root: CLICK HERE TO DOWNLOAD
(IGNORE THE OLD OLDN VERSION IN THIS .ZIP - USE THE ONE I POSTED ABOVE)
1 - download the files to your pc
2 - open ODIN on your pc
3 - connect USB to pc (not to the phone)
4 - power off phone
5 - go into download mode (hold both volume keys... then insert usb to the phone)
6 - ODIN should be connected, and you should be in download mode
7 - load pit file
8 - load tar file
9 - click start
10 - it will run it's course, once done the phone will reboot
11 - once rebooted, go to stock recovery and wipe data/cache (I made this bold below for emphasis since not in the video)
I gotta hand it you guys, you really bailed me out and for that I am eternally grateful. I will have to scrape the funds together for whomever needs a donation, but it is well worth it. I have one last remaining question. Now that I have Eugene's Rom, am I safe to flash another ROM by update.zip, or is ODIN the only reliable way for me to get one on the phone. I like the phone better now, but it seems like it is an out of the box ROM, which is fine. I didn't mind bionix 1.9 on 2.1 either. I just made a big mistake. Anyways, thanks again, and whomever can answer my last question I will extend my thanks in advance!!
Download rom manager
Flash cwr
Make backup in cwr
D nownload nero v3
Flash it in cwr
Enable voodoo if you desires
Enjoy your much improved phone that has a stable backup for an emergency.
I you need detailedsteps for this, read my sticky threads.
I dowloaded ROM manager last night and flashed recovery. I went to recovery and applied packages. I'm still getting this error that says the update.zip file is invalid through my e: drive (avatar folder). I just looked on both e and f. I can't seem to find any update.zip file on either card and I can't seem to flash any other ROM or even enter CW recovery. I looked at another post from someone and noticed that I never pulled my external sd card when I used ODIN to go back to stock or flash Eugene's ROM that I was suggested to use. Any formats I could try or tricks to suggest. I've looked around, but I'm not sure if this is a partition issue, an sd card (internal or external), or otherwise. Thanks again....
i noticed that there were a lot of additional file in places i didn't notice originally. I found in the CW file a recover-update and I thought that might be confusing things, I put it in a seperate folder and retried cw recovery, but that didn't work.
So I am not sure what happened. I started with a stock rom (and what I thought was) a rooted tab. I wanted to try the new ICS nightly so I downloaded the ROM and attempted to install it from ROM Manager (install from SD Card option). That didn't seem to do anything so I booted into recovery and tried to install it from there. That's what it all went wrong. After rebooting, my tab stays at the screen that says "Samsung Galaxy Tab 10.1" (picture). I've rebooted several times but it still comes back to this screen. I've left it for over 30 minutes just to be sure it wasn't stuck building the cache or something (I did try deleting the cache).
I am able to get into Download mode and connect with ODIN and have tried flashing several stock ROMs and others. The load successfully but after rebooting, it still gets stuck at this screen.
Any suggestions?
Well, simple enough, when you flash a stock ROM, you boot into the recovery, and do a factory reset, I know it sounds silly but there are some files that are in the tablet, since the tablet has no SD card slot, it will try to read the sectors that were replaced and not replaced. If the nightly build files are in the system, it ends up reading that since some files don't get replaced as they have roman's name on it, (You can confirm this by checking in Titanium Backup )
You can however flash with a PIT file if you feel lazy to do that and would want to start without the hassle of booting into several options, just flash the file to completely wipe and repartition the thing, that would be your best bet. Should be on the Overcome thread to grab the pit file. That should do the trick
Thanks for giving me hope! I just did some reading and I am afraid to download and attempt the wrong .pit file. Any chance you can give me a link to the correct .pit file for my tab (GT-P7510UWYB)?
Thanks again for the help!
Thanks again Misledz! I found this thread over on the Overcome site (link) that had all the files and very detailed instructions. Ran the PIT to bring it back to stock and it looks like it worked! You saved another tab!
! Yeah I don't really keep track of the websites But I do know where most of the files are, and Overcome thread seems to be doing a good job of hosting the files required to save every man, woman and child's tab
It's all good, Don't mention it , Glad it's alive
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.
I hope someone has some advice for me. I've been racking my brain for three days trying to figure out this problem.
Bought a g900t from ebay that only bootlooped to samsung screen. DL mode and recovery both booted fine.
Tried just wiping everything in recovery - nothing but bootloop.
Tried getting custom recovery on via heimdall - no dice. PIT failed to download. (This issue is not related to Kies - different machines to avoid interference.)
Tried KIES 'Firmware Upgrade and Initialization'. KIES said it was successful. Bootloop.
Odin-ed both ANCH and CNK2 firmware. Both were successful according to Odin. After each flash, the phone restarted in recovery and went directly to the android image with the blue sphere and a loading bar underneath. Started to load something, then rebooted directly back to recovery with android, and over and over and over.... (20-30 times before I pulled battery).
The phone now will not boot to recovery (only to above mentioned recovery loop). DL mode still comes up.
Tried Kies again, and it pretends like it is going to install but once I press start nothing happens.
I can't find a ROM with clearly labeled extractable partitions, and I can't find the proper partition name list, so I am not going to start trying to force-flash the partitions through heimdall (don't want to get the aboot and boot mixed up, e.g.) if I can even get heimdall to work.
You need to use Odin to go back to stock. I have no clue what firmware the phone is currently on but it's most likely lollipop. Here is a link for the 5.0 download http://forum.xda-developers.com/showthread.php?t=3034334
I use Odin 3.07 and have not had issues for years. Download the stock rom from the link mentioned and extract it somewhere easy to find. Once you extract it you will end up with a .tar file. Open Odin
Put phone in download mode and plug it in.
Make sure the COM tab lights up.
Click on pda and find the .tar file you extracted. Once found click open or double click it.
Odin will freeze while it loads the .tar file so be patient and don't freak out.
Wait til you see the file location load in the pda tab.
Once file loads up click start and profit.
Good luck!
Sent from my SM-G900T using XDA Free mobile app
Hi,
Thanks for the reply. As I mentioned above in the fifth paragraph, I tried two different firmwares through Odin.
I took the phone to BestBuy the other day and one of the Samsung Experience Center staff spent well over an hour reflashing the stock firmware using their setup and the phone still won't get past either a standard bootloop (first screen) or a recovery bootloop. He suggested sending it in under warranty (Knox still reads 0x0) and so it went out in the mail yesterday. Hopefully I get a functioning phone back.
On the bright side, the S.E.C. inside BestBuy seems to be a viable option for those who have a brick and don't have access to Odin/Heimdall.