Hi guys,
I recently flashed the TerraSilent kernel successfully for the galaxy player 4.0 because I wanted to flash a ROM.
After flashing the kernel, the player rebooted itself and when I unlocked it, none of the apps were working except some of the stock apps... even Google Play wasn't working. The problem is, i can see the apps but when I try to open them, it says "application not installed on phone." After that, I went into CWM and factory resetted it, and after I unlocked it, the apps were STILL there and it still has the same problem. Any idea on how to fix this?
the playa! said:
Hi guys,
I recently flashed the TerraSilent kernel successfully for the galaxy player 4.0 because I wanted to flash a ROM.
After flashing the kernel, the player rebooted itself and when I unlocked it, none of the apps were working except some of the stock apps... even Google Play wasn't working. The problem is, i can see the apps but when I try to open them, it says "application not installed on phone." After that, I went into CWM and factory resetted it, and after I unlocked it, the apps were STILL there and it still has the same problem. Any idea on how to fix this?
Click to expand...
Click to collapse
You should flash back to stock. Which apps don't work are it the ones that you installed, or the default apps. That's honestly not suppose to happen when flashing a kernel. What GP 4.0 do you have (USA, Intl, Euro)
obscuresword said:
You should flash back to stock. Which apps don't work are it the ones that you installed, or the default apps. That's honestly not suppose to happen when flashing a kernel. What GP 4.0 do you have (USA, Intl, Euro)
Click to expand...
Click to collapse
How am I suppose to flash back to stock?
And I have the US version... and some of the stock apps dont work as well....
the playa! said:
How am I suppose to flash back to stock?
And I have the US version... and some of the stock apps dont work as well....
Click to expand...
Click to collapse
Egad man, you must be a new bloke!
Jokes aside, I can't vouch for you in your app situation but something went odd when I flashed my first rom on the SGP 4. Most said youtube HD would install but the one I flashed "Ethereal Rom" kinda didn't but later I found out it was because I played with the youtube app on the stck rom before shortly flashing. So I thought to just flash the rom again to maybe fix the app issue - instant brick. I used odin for crying out loud, I thought it was safer than cwm.
So like most people I tried to find a "Recovery thread" here in the forums. Found it in the Development portion of the forums inside the All in one thread that is stickied near the top. I decided to flash a pit file that was recommended to me and flash a tar that had "everything in it" to flash back to stock rom. No go, infinite loops in recovery and cache and blocks just wouldn't fix no matter how much I wiped. I thought to myself - holy crap, I'm going to either have a new paperweight again (Bricked two PSP's on my own) or I'm going to have to send it to Samsung and have to pay for them to fix because they will instantly know I rooted my device. But then I noticed something in the Recovery Forum... Something called Heindall.
So for now, I'll give you the two links that you must have before jumping into the flash guide.
1. First Download the Pit (US) here - http://www.mediafire.com/?kjzdabdkg2p6jth
2. Then Download the Full Recovery file for the SGP4 (US) here- http://www.mediafire.com/?c76jdkgkn7qf310
3. Extract the Recovery as a folder with winrar ( download and install from rarlab.com) or 7zip ( download and install from 7-zip.org)
You should have a Folder with 5 items in it now.
4. Now place your device into download mode (Hold Power and Volume down button until you see an android with a shovel)
Now run through these steps below (original link here - http://forum.xda-developers.com/showpost.php?p=23290275&postcount=2) :
1. Download heimdall from here: http://www.glassechidna.com.au/products/heimdall/
2. This is a first time installation only. Extract heimdall, go to your drivers folders and run zadig.exe Install anything samsung related. (do this when in while in download mode.)
3. If you receive errors concerning the drivers install them anyway. (THIS IS NORMAL.)
4. Open heimdall-frontend.exe.
5. Go at the flash tab and chose the .pit according to your device.
6. After add the following partitions in the following order:
(Press drop down menu on the left to change)
PARAM: param.lfs
[Press Add]
CACHE: cache.rfs
[Press Add]
DBDATA: dbdata.rfs
[Press Add]
FACTORYFS: factoryfs.rfs
[Press Add]
KERNEL: zImage
7. When that is done double-check (just to be sure you're not obligated) ensure that re-partition is CHECKED!
8. Flash!
9. You should not have any errors but if you do have errors concerning can't mount cache (or something like that) Just wipe data is necessary.
10. You should have a like new device!
This worked for me and if I run into any bricks, I always revert to this. Make sure Kies while installed in your computer, just close anything inside your Computers Taskmanager that has anything with the word kies in the name, it conflicts with both heindall and Odin for some odd reason - remeber this for future rom /kernal flashing as this could be the reason why you currently are having problems.
da1writer said:
Egad man, you must be a new bloke!
Jokes aside, I can't vouch for you in your app situation but something went odd when I flashed my first rom on the SGP 4. Most said youtube HD would install but the one I flashed "Ethereal Rom" kinda didn't but later I found out it was because I played with the youtube app on the stck rom before shortly flashing. So I thought to just flash the rom again to maybe fix the app issue - instant brick. I used odin for crying out loud, I thought it was safer than cwm.
So like most people I tried to find a "Recovery thread" here in the forums. Found it in the Development portion of the forums inside the All in one thread that is stickied near the top. I decided to flash a pit file that was recommended to me and flash a tar that had "everything in it" to flash back to stock rom. No go, infinite loops in recovery and cache and blocks just wouldn't fix no matter how much I wiped. I thought to myself - holy crap, I'm going to either have a new paperweight again (Bricked two PSP's on my own) or I'm going to have to send it to Samsung and have to pay for them to fix because they will instantly know I rooted my device. But then I noticed something in the Recovery Forum... Something called Heindall.
So for now, I'll give you the two links that you must have before jumping into the flash guide.
1. First Download the Pit (US) here - http://www.mediafire.com/?kjzdabdkg2p6jth
2. Then Download the Full Recovery file for the SGP4 (US) here- http://www.mediafire.com/?c76jdkgkn7qf310
3. Extract the Recovery as a folder with winrar ( download and install from rarlab.com) or 7zip ( download and install from 7-zip.org)
You should have a Folder with 5 items in it now.
4. Now place your device into download mode (Hold Power and Volume down button until you see an android with a shovel)
Now run through these steps below (original link here - http://forum.xda-developers.com/showpost.php?p=23290275&postcount=2) :
1. Download heimdall from here: http://www.glassechidna.com.au/products/heimdall/
2. This is a first time installation only. Extract heimdall, go to your drivers folders and run zadig.exe Install anything samsung related. (do this when in while in download mode.)
3. If you receive errors concerning the drivers install them anyway. (THIS IS NORMAL.)
4. Open heimdall-frontend.exe.
5. Go at the flash tab and chose the .pit according to your device.
6. After add the following partitions in the following order:
(Press drop down menu on the left to change)
PARAM: param.lfs
[Press Add]
CACHE: cache.rfs
[Press Add]
DBDATA: dbdata.rfs
[Press Add]
FACTORYFS: factoryfs.rfs
[Press Add]
KERNEL: zImage
7. When that is done double-check (just to be sure you're not obligated) ensure that re-partition is CHECKED!
8. Flash!
9. You should not have any errors but if you do have errors concerning can't mount cache (or something like that) Just wipe data is necessary.
10. You should have a like new device!
This worked for me and if I run into any bricks, I always revert to this. Make sure Kies while installed in your computer, just close anything inside your Computers Taskmanager that has anything with the word kies in the name, it conflicts with both heindall and Odin for some odd reason - remeber this for future rom /kernal flashing as this could be the reason why you currently are having problems.
Click to expand...
Click to collapse
THANKS MAN! but since I manually deleted all my apps... its better for me to go for a ROM now.. lol
I will download the ICS 4.0.4 ROM after it gets a bit more stable......
I have one question though.... when I put my player in download mode, it says "USB not recognized" do you know how to fix that? it ONLY happens when its in download mode.
the playa! said:
THANKS MAN! but since I manually deleted all my apps... its better for me to go for a ROM now.. lol
I will download the ICS 4.0.4 ROM after it gets a bit more stable......
I have one question though.... when I put my player in download mode, it says "USB not recognized" do you know how to fix that? it ONLY happens when its in download mode.
Click to expand...
Click to collapse
I usually run the kies troubleshoot to reset my samsung drivers. You can also switch usb ports to manually force the driver install, you may need to have odin open so that it can pop it up... I plan on jumping to the 4.04 too as well btw - when it's stable of course.
da1writer said:
I usually run the kies troubleshoot to reset my samsung drivers. You can also switch usb ports to manually force the driver install, you may need to have odin open so that it can pop it up... I plan on jumping to the 4.04 too as well btw - when it's stable of course.
Click to expand...
Click to collapse
the drivers get installed again after using kies troubleshoot?
da1writer said:
Egad man, you must be a new bloke!
Jokes aside, I can't vouch for you in your app situation but something went odd when I flashed my first rom on the SGP 4. Most said youtube HD would install but the one I flashed "Ethereal Rom" kinda didn't but later I found out it was because I played with the youtube app on the stck rom before shortly flashing. So I thought to just flash the rom again to maybe fix the app issue - instant brick. I used odin for crying out loud, I thought it was safer than cwm.
So like most people I tried to find a "Recovery thread" here in the forums. Found it in the Development portion of the forums inside the All in one thread that is stickied near the top. I decided to flash a pit file that was recommended to me and flash a tar that had "everything in it" to flash back to stock rom. No go, infinite loops in recovery and cache and blocks just wouldn't fix no matter how much I wiped. I thought to myself - holy crap, I'm going to either have a new paperweight again (Bricked two PSP's on my own) or I'm going to have to send it to Samsung and have to pay for them to fix because they will instantly know I rooted my device. But then I noticed something in the Recovery Forum... Something called Heindall.
So for now, I'll give you the two links that you must have before jumping into the flash guide.
1. First Download the Pit (US) here - http://www.mediafire.com/?kjzdabdkg2p6jth
2. Then Download the Full Recovery file for the SGP4 (US) here- http://www.mediafire.com/?c76jdkgkn7qf310
3. Extract the Recovery as a folder with winrar ( download and install from rarlab.com) or 7zip ( download and install from 7-zip.org)
You should have a Folder with 5 items in it now.
4. Now place your device into download mode (Hold Power and Volume down button until you see an android with a shovel)
Now run through these steps below (original link here - http://forum.xda-developers.com/showpost.php?p=23290275&postcount=2) :
1. Download heimdall from here: http://www.glassechidna.com.au/products/heimdall/
2. This is a first time installation only. Extract heimdall, go to your drivers folders and run zadig.exe Install anything samsung related. (do this when in while in download mode.)
3. If you receive errors concerning the drivers install them anyway. (THIS IS NORMAL.)
4. Open heimdall-frontend.exe.
5. Go at the flash tab and chose the .pit according to your device.
6. After add the following partitions in the following order:
(Press drop down menu on the left to change)
PARAM: param.lfs
[Press Add]
CACHE: cache.rfs
[Press Add]
DBDATA: dbdata.rfs
[Press Add]
FACTORYFS: factoryfs.rfs
[Press Add]
KERNEL: zImage
7. When that is done double-check (just to be sure you're not obligated) ensure that re-partition is CHECKED!
8. Flash!
9. You should not have any errors but if you do have errors concerning can't mount cache (or something like that) Just wipe data is necessary.
10. You should have a like new device!
This worked for me and if I run into any bricks, I always revert to this. Make sure Kies while installed in your computer, just close anything inside your Computers Taskmanager that has anything with the word kies in the name, it conflicts with both heindall and Odin for some odd reason - remeber this for future rom /kernal flashing as this could be the reason why you currently are having problems.
Click to expand...
Click to collapse
I am indeed a newbie at this stuff, so I will do this.
My device is currently bricked. (it shows a cellphone then a warning sign then a computer)
will it work for my bricked player? some people say its forced download mode.. but neither computer nor odin recognize it...
the playa! said:
I am indeed a newbie at this stuff, so I will do this.
My device is currently bricked. (it shows a cellphone then a warning sign then a computer)
will it work for my bricked player? some people say its forced download mode.. but neither computer nor odin recognize it...
Click to expand...
Click to collapse
My computer hasn't recognized my player (MTD) since rooting, so that's not the issue. One of my usb ports don't even recognize my player either through odin. I was in your state one time, that's why I'm consistently trying to help you.
Now to help you out, once you download heimdall, extract the file. You should now have a heimdall folder (or icons/programs), there will be a folder called "drivers" - zadig is in it. Now hook up your device to a usb port that hasn't been used recently to flash roms/kernals. Run zadig and select "options" in the top menu. Click on "list all devices". Now the drop down menu should have Samsung drivers now (it won't be android or the player, it'll just be generic Samsung drivers - install these, don't worry.)
Once that is done, close zadig and follow the rest of the guide above.
If the player is still not being recognized, go to the final tab of the Heimdall Frontend and select "Detect Device" , it looks like this:
http://www.google.com/imgres?q=heim...0&ndsp=15&ved=1t:429,r:3,s:0,i:82&tx=72&ty=58
da1writer said:
My computer hasn't recognized my player (MTD) since rooting, so that's not the issue. One of my usb ports don't even recognize my player either through odin. I was in your state one time, that's why I'm consistently trying to help you.
Now to help you out, once you download heimdall, extract the file. You should now have a heimdall folder (or icons/programs), there will be a folder called "drivers" - zadig is in it. Now hook up your device to a usb port that hasn't been used recently to flash roms/kernals. Run zadig and select "options" in the top menu. Click on "list all devices". Now the drop down menu should have Samsung drivers now (it won't be android or the player, it'll just be generic Samsung drivers - install these, don't worry.)
Once that is done, close zadig and follow the rest of the guide above.
If the player is still not being recognized, go to the final tab of the Heimdall Frontend and select "Detect Device" , it looks like this:
http://www.google.com/imgres?q=heim...0&ndsp=15&ved=1t:429,r:3,s:0,i:82&tx=72&ty=58
Click to expand...
Click to collapse
before I begin the process, the player has to plugged in to the computer right?
and thanks for ur constant help
the playa! said:
before I begin the process, the player has to plugged in to the computer right?
and thanks for ur constant help
Click to expand...
Click to collapse
Yes, the player must be plugged in for the drivers to be seen or at least for zadig/heimdall to read the [generic] device. I will be on every night to help you sir to the best of my ability. Have you tried close pc screen btw? I'll show you a screen shot of what I mean...
http://www.google.com/imgres?q=heim...w=145&start=0&ndsp=18&ved=1t:429,r:0,s:0,i:73
On a side ote, I will be flashing back to stock as well soon (if the ICS rom doesn't come to a state I like) as I believe I'm not getting any benefits to these custom roms besides maybe additional battery life and debloating - almost no games work on Ethereal or Icy Fusion and some apps are iffy in working. Ram improvement is almost non-existent on these custom roms...
I'll be keeping root and either use Klin's R3 or Terrasilent Kernal to keep Voodoo. I miss some of my games I use to play all the time like Mass Effect and Dead Space...
Will be going the route of uzi2.
http://forum.xda-developers.com/showthread.php?t=1878542
I thought the roms impressed me due to what I mentioned above but it really doesn't bother me [with stock], I'm actually at odds between launchers more than anything when it came between choosing the 4.0's current best [which were Icy Fusion Holo Launcher and Ethereal's Go Launcher].
Will decide by next weekend...
da1writer said:
yes, the player must be plugged in for the drivers to be seen or at least for zadig/heimdall to read the [generic] device. I will be on every night to help you sir to the best of my ability. Have you tried close pc screen btw? I'll show you a screen shot of what i mean...
http://www.google.com/imgres?q=heim...w=145&start=0&ndsp=18&ved=1t:429,r:0,s:0,i:73
on a side ote, i will be flashing back to stock as well soon (if the ics rom doesn't come to a state i like) as i believe i'm not getting any benefits to these custom roms besides maybe additional battery life and debloating - almost no games work on ethereal or icy fusion and some apps are iffy in working. Ram improvement is almost non-existent on these custom roms...
I'll be keeping root and either use klin's r3 or terrasilent kernal to keep voodoo. I miss some of my games i use to play all the time like mass effect and dead space...
Will be going the route of uzi2.
http://forum.xda-developers.com/showthread.php?t=1878542
i thought the roms impressed me due to what i mentioned above but it really doesn't bother me [with stock], i'm actually at odds between launchers more than anything when it came between choosing the 4.0's current best [which were icy fusion holo launcher and ethereal's go launcher].
Will decide by next weekend...
Click to expand...
Click to collapse
thank you very much! :d
it worked! My player works now! :d
Related
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.
Hi all, I've never bricked my vibrant, seen so many horror stories and today it seems the "fully operational" rom I flashed has screwed me over big time. So i've seen the "odin back to stock" suggestion many times, but what exactly is stock now, JI6? so it wouldn't be ok to go to stock 2.2 since it's official now? Can someone point me to the most helpful walkthrough you specifically have ever used? Thanks guys.
Edit: This is where I'm at:
Came from Trigger, disabled voodoo, booted into rfs. Rebooted into rfs. Rebooted into recovery, flashed explodingboys ROM, flashed fine. Had 0 application storage upon boot/sd wiped. Never used dead horse previously (probably never will again). Now I can mount my phone and load stuff onto my sd, and even flash things. tried flashing a voodoo kernel and it failed upon converting, linda even said "not enough space" got stuck on boot splash. Got back into recovery and flashed this cursed ROM again and it did get my phone on again, so at least I got something, but i cant install any apps, roms, and not really sure what kernel if any would help me.
If you have flashed 2.2 roms and you can get into recovery then, this will work for you:
You will need:
Odin 1.7 or higher
Pit512 file for mapping
JFD file (stock 2.1)
Eugenes Froyo that does not brick
Of course the Samsung drivers in the computer
PLEASE READ S15274N Sticky for Noobs in the Gen section it has all the methods better explained for you.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will everything back to normal and the phone will work just like it did right out of the box
hope that helps
Thanks very much man, I'll try this out tomorrow, I think its just too late and i'm too frustrated. Sometimes you just gotta go to bed. Thanks again!
Everything you need to do you can do with this http://forum.xda-developers.com/showthread.php?t=954509
I believe in you, I just bricked MY FRIENDS vibrant and fixed it after about 6 hrs of work. Save yourself the time and get the right drivers for odin and just use that. Good night, and good luck.
I've always wanted to say that
Can anyone point me in the direction of a place that would have links / downloads to all the up to date filess as far as drivers go? don't want to use anything outdated..
My AT&T Samsung Captivate i897 has gone bad so I just purchased a used Note i717 (i tis on the way). I like the larger format, dual cameras +flash, LTE speed.
The phone is already in stock ICS 4.04 (build UCLF6). I would like to 1) root, 2) add CWM, 3) flash to final CM9 stable (like I have on my Captivate). I have read and read threads and posts to the point that I am a little dizzy. My questions are:
1) what is the best way for ICS 4.04 stock to be rooted and injected with CWM (the posts all seem to be targeted at the original GB)?
2) if I get in trouble and brick it (always seems to happen on my root attempts), is there a SuperOneclick or Heimdall or Odin approach that will push stock software (or any) so that I can retry 1 - in the past Heimdall was the savior)?
Thank you and I look forward to participating in this forum :good:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
gregsarg said:
then by all means, visit the "note super everything thread" at the top of the general section.
Once there, scroll down to the big green arrow, and go from there..
And welcome to the I717 forums....g
Click to expand...
Click to collapse
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
tonyo123 said:
I do not see a big green arrow and am in graphics more. My apology. Am I blind or old or something?
I've seen the thread and slooked into the links seem to be stock GB specific in terms of rooting and adding CWM. Some talk of ICS 4.03 not 4.04 but still not rooting. Will one of the rooting tools (DA_G's) help me to get going?
At the bottom of the post I see the following but interestingly enough the CWM link assumes root. So, at a basic level I am looking to first root with ICS 4.04
Again, THANK YOU and sorry for feelign like an almost Noobie.
{ROOTING OFFICIAL ICS 4.0.4 I717UCLF6}
[Recovery] Clockwork-mod Based Touch Recovery - 04/14/12
or
[RECOVERY] TWRP2.2.2. TeamWin Recovery Project 7/17 Bugfixes
[ROOT] Superuser 3.0.7 for ICS 4.0.3 Leak
USB Driver for ATT I717Galaxy Note
Click to expand...
Click to collapse
Go to the last page in that thread. I posted an easy, fool-proof root method. It was simple enough that even I could do it.:laugh:
root for the ICS 4.0.4 is easy....
It consists of Odin pushing a CWM image, and flashing SU from your new found recovery.
But there are a few tips that will help you out...
follow teyshablue...and you'll be rooted in 10 minutes....g
THANKS
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
tonyo123 said:
I thanked you both. My new Note is in tomorrow overnight via USPS overnight. Cannot wait!!! Teyshablue, the post with step-by-step pictures is excellent. It removes the risk of doing parts of this incorrectly, which I always do in geting to root and CWM (usually because somehting is always different than the directions say). I will do first thing upon receipt tomorrow and report in tomorrow. Obviously, I will spend the rest of my holiday weekend reloading my apps (how fun...really) OUTSIDE.
Click to expand...
Click to collapse
Yeah, the video tutorial saved my bacon!:good:
Okay I'm planning on doing similar tonight with my newly arrived refurbed i717. It shipped with ICS.
I'm confused however...if I simply want to flash a custom ROM (versus running rooted stock ICS), I've seen threads stating that I don't need Root, but instead install TWRP2 via Odin from here:
http://forum.xda-developers.com/showthread.php?t=1584576
...then flash custom ROM via TWRP2 recovery.
Am I missing something? Searching on Q&A seems to indicate some worrying issues about attempting this method of root on these refurbed Note's running ICS:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
TIA
Root is your first step.....as you need the custom recovery to flash the roms...
ultimately.....pushing a recovery via Odin, is giving you root....g
You don't need to root to flash a ROM. You can flash cwm through Odin then flash the twrp zip if that's the recovery you desire. I'm not sure if all the bugs are worked out on the twrp Odin tar. Once you flash a recovery, you can make a backup of your stocker and then flash your ROM of choice. Again, you do not need to root. Flashing a custom recovery through Odin does not root your phone, and is the first step. If you wish to root , then you would flash the su binaries zip in a custom recovery. I just don't want there to be any confusion.
Gubment Cheeze
Oh boy...want to be sure here...
Froid, I think what you type is consistent with Teyshablue's process.
1) This process first adds CWM (the custom recovery) using ODIN with the file “odin_ni717_cwm_recovery_b4.tar" in PDS slot. I assumed it needed root first but here CWM is the first step.
See here:
http://rootgalaxynote.com/galaxy-no...y-note-sgh-i717-icsgingerbreadeasiest-method/
1A) Then, I think I should nandroid back up the Stock ICS ROM here with CWM? I think so but it's not in the guide.
2) The next step using CWM is to load "Superuser-3.0.7-efghi-signed.zip ". So this roots correct Froid?
3) After that, then I can nandroid back-up rooted ICS ROM again with CWM.
4) Then can clean cache, Dalvik, and flash CM9 with CWM (Do I need to do some factory reset full wipe before adding CM9 ROM)?
Am I missing anything?
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
---------- Post added at 08:36 PM ---------- Previous post was at 08:25 PM ----------
On a side note, make sure you do your homework on the available recovery options before diving in head first. I personally use TWRP and would highly recommend.
Gubment Cheeze
Froid said:
You are flashing cwm recovery through Odin with that file. That process does not root your phone. You don't have to install the superuser zip file through cwm if you don't want to root(this is what gives you root). You can skip that step if you desire. Once you put the cwm tar file in the PDA slot and hit run, Odin will flash the custom recovery and reboot your phone. From there you can 3 button into recovery, make a backup, then flash your ROM of choice.
Gubment Cheeze
Click to expand...
Click to collapse
Froid, mind checking me one more time? I edited my prior post (with numbered steps) as you were typing the reply. I am not sure about skipping the rooting step but I know you are probably right. I think I will run through the process as stated adding the stock backup then the rooted backup. Sound okay?
MUCH THANKS !!!! :good:
On the recovery program, I have only used CWM while I had my Captivate. TWRP is new to me. More options better program?
That will absolutely work. Not a bad idea to have both stock and rooted backed up. Always full wipe when flashing a new ROM. follow the OP of the ROM you're flashing. I don't use cwm so do some research on whether or not you need the latest version to flash a cm9 ROM. There was an issue in the past with using an older version of cwm. Not sure if that still exists. Good luck
Gubment Cheeze
Rooting Upgrading Anxiety
thanks all for the help, knowing that I just purchsed a close to $500 (shipping and accesories) used phone and knowing how many times I messed up my Captivate did not allow me to sleep well last night. I really want to do this right and not be panicked with a messed up Note to start with. I will sleep better knowing that I have a thought out and tested approach for when it arrives tomorrow.
And yes, TWRP has a few more options. I was always a fan of cwm, and its a great recovery. I just prefer TWRP for its UI, backup speeds, and being able to name the backup beforehand.
Gubment Cheeze
Let me know of progress
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
tonyo123 said:
Madtowndave, assuming there are no file problems (there should not be from what I see) I think the process by Teyshablue that I link to should work fine and appears low risk. As I mentioned, I would do a backup of the Sock ROM after the first ,ajor step of loading CWM.
For now, I will stick to CWM because I have used it and know it. Don't want too many variables or new learnings at the moment. The risk would be too high and I am unfamiliar with the Note (for example, I already see that recovery and download mode button combinations are different - little things like these have tripped me up in the past).
Madtowndave, let me know what process you used and how it went, and if any steps caused you problems.
Click to expand...
Click to collapse
Yes, naming backups is good as I have had to go back and just had many dated files which became almost hunt and peck in finding the exact one I needed. As for CWM, I also used the Devil Kernel, not sure if it is available for the Note, that beyond speed, also gave a few added optionsto CWM including a file manager which came in handy in swapping out system files (like CM9's Trebuchet launcher being replaced by a lighter version). But, a step at a time. I only used the added kernel because the Captivate with single core was a bit speed challenged (but CM9 made it like new).
Success!!
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Madtowndave said:
I'll try to be as detailed as possible.
1. Use stock USB cable and plug in on a back USB port that is on the motherboard.
2. Let Windows install the i717 USB drivers. Annoyingly, whenever I was in a different mode (specifically, USB mass storage or d/l mode), Win7 would install/update more drivers. After 3 total device driver installs from the different modes, I rebooted my pc.
3. I d/l Odin 1.85 and the Odin .tar link under 4-14-2012 from here: http://forum.xda-developers.com/showthread.php?t=1584576
I decided to use the CWM touch version...very similar to Cappy CWM to go back in the menu you use the back capacitive button.
4. I decided on a custom ROM...For me, I loved Mosiac on the Cappy back in the day, so I chose from the fine folks at The Collective here: http://forum.xda-developers.com/showthread.php?t=1773229
5. Pushed the ROM and GApps zip files via USB
6. Run Odin as Admin, click on PDA and selected the .tar from step 3.
7. Put phone in d/l mode and plug in to USB, Odin Com port lights up...Click Start
8. After the phone rebooted, (wait for the haptic feedback) I pulled the battery
9. 3 fingered into Recovery and now in good ol' CWM. The one trick here is that the .zips are under Internal Storage menu option, not SD Card (unless of course you file transferred them to an external sd card)
10. Followed installation steps in ROM OP and flashed zips from Step 5.
11. Enjoy!
I did not need Root, but am now rooted by virtue of the custom ROM. I also did not Nandroid backup the Stock ROM since if I ever need to go back to Stock, I'll just use Odin.
Click to expand...
Click to collapse
Awesome for you. I am awaiting dilivery from USPS. I hope they don't let me down after payong $40 for the overnight.
Two questions:
1) What did(do) your Win7 drivers in 'device manager' indicate? Was it something like “Samsung Mobile USB CDC Composite Device" or did it identify the phone by name. I have seen both types in my Win7 setup with my Captivate so want to make sure I get this right.
2) So, you did not specifically root (no need for the "Superuser-3.0.7-efghi-signed.zip" or something like it). So assuming adter I add CWMm I flash the CM9 (Cyanogenmod 9 stable) ROM will that root my phone? I guess the more general question is do these ROMS automatically come rooted?
I have a new stock Gingerbread Fascinate, and want to install the Geewiz Media 4.4/JB 4.2.2 ROM/Kernel on it (making it an ipod-like device). I really really hate having to ask, especially after spending the past week reading a couple of hundred pages of posts, including the dev's, droidstyle's guide, and others, learning as much as I can. I have rooted a Motorola Droid 2 before, but this is all new, and I am still unsure.
So Geewiz comes as Edify .zip files or Odin-compatible .tar files. Based on the dev's provided information, I choose to start with the Odin-compatible .tar file named "GeeWiz Media 4.4 ROM/Kernel/Modem/Recovery/Data Wipe Full Update". As I understand it this is includes everything I need to start: a rooted JB OS with modified EH03 kernel, plus CWM, data folders reformatted to ext4, and an EH03 recovery. I need to start on stock EH03, which I already am.
I have plenty of threads saved (& many printed), so I don't need help with the button-pushing. My confusion stems from the different file types (tar vs. zip) and software (Odin and Clockwork), and what I am supposed to do in what order.
So my questions:
1. Does the .tar file to be installed by Odin go on my SD card or stay on my computer?
2. Since the .tar contains everything at once, what process do I follow after installing it? (Reboot into recovery, download mode, etc.)
3. Should I expect a CWM .zip file on my SD card after installing the tar?
I seems like I should have been able to figure this out on my own, but the dev thread doesn't get into the basics, and I haven't found explicit instructions for the all-in-one Geewiz ROM, or other instructions that I am comfortably sure are completely relevant.
Thank you.
I'm by no means an expert, but I've flashed a lot of roms including Geewiz before so I'll try to help you out.
1) Odin pushes files to your device from the computer, so there's no need to have anything saved on your phone
2) Once everything completes simply reboot the phone and you should be good to go
3) I'm not sure, but I don't think so. I'm pretty sure Geewiz has it's own recovery included with the rom and there will be no need to separately install CWM recovery
If anything goes wrong, simply follow droidstyle's guide to go back to stock and start over again. The Fascinate is extremely hard to break (luckily).
Thank you, Crawshayi! :fingers-crossed:
Wow, after all that worry, it was a piece of cake. If its any use to someone, I installed with Odin, following this procedure:
1. Remove battery
2. Fire up Odin (I used 1.85)
3. Plug in the factory USB cable and hold the volume down button
4. Wait for download mode and yellow box in Odin
5. Put my Geewiz full-wipe / kernel / recovery .tar file in Odin's PDA box
6. Hit start.
7. Wait till Odin box turns green and says pass
8. Reboot phone. (I wasn't sure about clicking the "Auto-Reboot" box. Some say yes and some say no, in my readings. I clicked it, but it didn't auto reboot anyway. I also had "F. Reset Time" checked as instructed.
9. First there was a brief message about wiping phone & ext4. Then, a pretty long wait time, watching a big colored "X". Just when I was starting to worry a little bit, a message from Google popped up and I was "in".
This is the first time I've ever looked at Jelly Bean. It's beautiful and really different from Gingerbread (which is my only exposure to Android since moving from Blackberry)
Yeah Jelly Bean is really great, Google hit a home run with that one and we're lucky enough to have a lot of good Jelly Bean roms to choose from on the Fascinate
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.