The system/boot image is packed in an Odin-flashable .tar. However, since I apparently suck at making Odin-flashable modem .tars, I'm including pterry30's CWM-flashable modem .zip for completionists sake.
Files Available
NB: The system-boot.tar is zipped to save space. Please extract the .tar before flashing via Odin.
pda-odin-telus-stock-system-boot.tar - This .tar contains the stock system.img.ext4 and stock boot.img and can be used to assist in resetting your flash counter using braway's method. Flash it via Odin's pda option. Unfortunately, no one has provided me with the stock Telus recovery thus I obviously cannot provide it to anyone else. Sorry.
Telus-Modem-CWM.zip - This .zip is made by pterry30 and contains the stock Telus modem/radio files. Just flash via Clockworkmod recovery.
SkyDrive folder containing all Telus files - Public SkyDrive folder that contains the above Telus files since my public DropBox links keep being suspended due to excessive traffic.
Disclaimer
I am in no way responsible for any damages caused to your Note by anything you flashed. These files are provided as is to help Telus Note owners return to stock after whatever they've done to their phones.
Special Thanks
adv1sory for providing the Telus system.img.ext4.
braway for taking my constant questions and providing much needed guidance in my first developer-ish project as well as for the flash counter reset.
Da_G for providing the stock Telus boot.img (kernel), instructions on using Odin, and indirectly showing me how to use the Linux terminal.
pterry30 for packaging the stock modem/radio files into a CWM-flashable .zip.
Please post your experiences with these stock Telus files below and if you have any questions, I'll do my best to help. Enjoy!!
Posted in General as per Development Forum Rules.
Just flashed with odin and noticed the following:
1) the flash counter didnt reset, actually added 1 to the counter
2) after flashing, cwm was still on the phone. *flashed a stock telus recovery to fix that.
3) Does not automatically format internal sd
4) Does not restore to factory default settings
5) Boot up music doesnt play
Is it possible to fix these issues?
btw ... why is it such a huge image?
adv1sory said:
Just flashed with odin and noticed the following:
1) the flash counter didnt reset, actually added 1 to the counter
2) after flashing, cwm was still on the phone. *flashed a stock telus recovery to fix that.
3) Does not automatically format internal sd
4) Does not restore to factory default settings
5) Boot up music doesnt play
Is it possible to fix these issues?
btw ... why is it such a huge image?
Click to expand...
Click to collapse
Please read through the entire post. You didn't provide me with a recovery so I could not include it. Also, to use the flash-counter reset, you need CWM, which is why I don't typically include recovery in the Odin-flashable. See the link to braway's method in the OP. The way the flash-counter works, anything that you flash that isn't just a system image increases the flash counter. I had to include the kernel, thus the flash-counter goes up. Using braway's method that I linked to will allow you to completely restore your Note to stock using my files and the recovery you found. If you could provide me with a link to the recovery, I will gladly add it to the OP so others do not have to go looking for it.
No Odin-flashable .tar clears the internal sd or restores the phone to factory settings. It only changes the system image. Kind of like installing windows again on your computer doesn't overwrite all your data unless you format the hard drive.
Also, not owning a Telus Note, I didn't know there was supposed to be boot music. That I cannot explain. I used Da-G's kernel. Not sure if anyone else has experienced this issue.
As for file size, it's the same size as all the other ones. And the same size as the files you provided me. The system.img.ext4 on any Note is about 1 GB.
I hope this clears some of this up.
I have a stock Telus Note and can confirm that there is no boot up music. Just the Samsung animation
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
Does anyone know if the LTE bands for the Telus Note are different from that of Rogers?
i.e. now that my Telus Note is unlocked, should I expect to get LTE speeds with my Rogers wireless account?
help, cant get back to stock from ics custom rom.
tried flashing this with no success.
odin freezes and if it says it flashes successfully, phone wouldnt boot after the restart.
came from ics objection rom and wanting to go back to stock.
i cant get anything that i flash through odin working.
ics objection rom runs fine when i flash it back through cwm.
tried flashing stock rooted image from another thread and i get stuck at "the touch the android to begin screen".
any idea whats going on? i know im just doing something wrong because my phone works fine with the objection rom whenever i flash it but when i try to get back to stock, thats where everything gets messed up.
any kind of help would be appreciated.
I've found that the "touch the android to begin" problem occurs if you haven't factory reset when coming from ICS back to this stock ROM. Reboot into CWM and factory reset then reboot the phone,. You should now be able to touch the Android to begin.
josepuzon said:
tried flashing this with no success.
odin freezes and if it says it flashes successfully, phone wouldnt boot after the restart.
came from ics objection rom and wanting to go back to stock.
i cant get anything that i flash through odin working.
ics objection rom runs fine when i flash it back through cwm.
tried flashing stock rooted image from another thread and i get stuck at "the touch the android to begin screen".
any idea whats going on? i know im just doing something wrong because my phone works fine with the objection rom whenever i flash it but when i try to get back to stock, thats where everything gets messed up.
any kind of help would be appreciated.
Click to expand...
Click to collapse
Full Stock
I am good. Finally got the steps done so Kies liked my phone again.
W
------------------------
Hi,
I am trying to go back to full stock from a failed ICS update.
I flashed your pda-odin-telus-stock-system-boot.tar file and I
can get back into the phone but Kies won't allow me to do updates?
What is my next step? Do I need a Telus Stock Recovery file?
Is Kies looking at the flash counter and saying no to updating
my phone because it has gone up?
My phone is not rooted, never has been.
My understanding is Kies won't update if it is rooted and also
to reset the counter with Braway's method you need to be rooted....
I'm real new to all this and all I want is a stock Kies updateable
phone back. Maybe I should have just gave it back to Telus....
Thanks for any help...
W
MrJoran said:
The system/boot image is packed in an Odin-flashable .tar. However, since I apparently suck at making Odin-flashable modem .tars, I'm including pterry30's CWM-flashable modem .zip for completionists sake.
Files Available
NB: The system-boot.tar is zipped to save space. Please extract the .tar before flashing via Odin.
pda-odin-telus-stock-system-boot.tar This .tar contains the stock system.img.ext4 and stock boot.img and can be used to assist in resetting your flash counter using braway's method. Flash it via Odin's pda option. Unfortunately, no one has provided me with the stock Telus recovery thus I obviously cannot provide it to anyone else. Sorry.
Telus-Modem-CWM.zip This .zip is made by pterry30 and contains the stock Telus modem/radio files. Just flash via Clockworkmod recovery.
Disclaimer
I am in no way responsible for any damages caused to your Note by anything you flashed. These files are provided as is to help Telus Note owners return to stock after whatever they've done to their phones.
Special Thanks
adv1sory for providing the Telus system.img.ext4.
braway for taking my constant questions and providing much needed guidance in my first developer-ish project as well as for the flash counter reset.
Da_G for providing the stock Telus boot.img (kernel), instructions on using Odin, and indirectly showing me how to use the Linux terminal.
pterry30 for packaging the stock modem/radio files into a CWM-flashable .zip.
Please post your experiences with these stock Telus files below and if you have any questions, I'll do my best to help. Enjoy!!
Posted in General as per Development Forum Rules.
Click to expand...
Click to collapse
After installing the Telus-Modem-CWM.zip file, my phone found the system update and is currently downloading. I will post if this fixed the issue. In any case, Thanks!
My phone is not updating. I have flashed the CWM touch using odin but it won't boot into CWM mode.
Strangely, my baseband remains T989 KJ3 even though I have manually uploaded the files from the "stock" files via adb... it changed from VKL to KJ3...
Any ideas on how to troubleshoot why I can't reboot to CWM? I have flashed it several times now and all were successful. From what I can tell, I have the stock image since I no longer have root.
I have a Telus Note, which I flashed to Rogers ROM so I can get LTE on Rogers and it has now been upgraded to ICS.
But I hate the Rogers crap that comes installed with the ROM and was wondering if its possible to load the TELUS ROM (minus Radio) so I can continue using Rogers LTE?
MrJoran said:
The system/boot image is packed in an Odin-flashable .tar. However, since I apparently suck at making Odin-flashable modem .tars, I'm including pterry30's CWM-flashable modem .zip for completionists sake.
Files Available
NB: The system-boot.tar is zipped to save space. Please extract the .tar before flashing via Odin.
pda-odin-telus-stock-system-boot.tar - This .tar contains the stock system.img.ext4 and stock boot.img and can be used to assist in resetting your flash counter using braway's method. Flash it via Odin's pda option. Unfortunately, no one has provided me with the stock Telus recovery thus I obviously cannot provide it to anyone else. Sorry.
Telus-Modem-CWM.zip - This .zip is made by pterry30 and contains the stock Telus modem/radio files. Just flash via Clockworkmod recovery.
SkyDrive folder containing all Telus files - Public SkyDrive folder that contains the above Telus files since my public DropBox links keep being suspended due to excessive traffic.
Disclaimer
I am in no way responsible for any damages caused to your Note by anything you flashed. These files are provided as is to help Telus Note owners return to stock after whatever they've done to their phones.
Special Thanks
adv1sory for providing the Telus system.img.ext4.
braway for taking my constant questions and providing much needed guidance in my first developer-ish project as well as for the flash counter reset.
Da_G for providing the stock Telus boot.img (kernel), instructions on using Odin, and indirectly showing me how to use the Linux terminal.
pterry30 for packaging the stock modem/radio files into a CWM-flashable .zip.
Please post your experiences with these stock Telus files below and if you have any questions, I'll do my best to help. Enjoy!!
Posted in General as per Development Forum Rules.
Click to expand...
Click to collapse
I was able to download the radio file. but when I go to access the other one it asks me to log in to skydrive. Is this file still available?
Thanks!
I just want to say thank you for this. I know this is an old thread, but I just purchased a Rogers i717. I had it unlocked to use my TELUS account, and i kept getting strange errors.
I flashed the stock TELUS image, and modem. From 2.3.6 using Kies I was able to upgrade to 4.0.4.
I must say, TELUS does not put any bloatware on their device compared to the Rogers.
Thank you again
puleen said:
I have a stock Telus Note and can confirm that there is no boot up music. Just the Samsung animation
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
Does anyone know if the LTE bands for the Telus Note are different from that of Rogers?
i.e. now that my Telus Note is unlocked, should I expect to get LTE speeds with my Rogers wireless account?
Click to expand...
Click to collapse
I'm using a Rogers Note on Telus. Speeds are the same, exactly, coming from the Amaze and Xperia Play, you still get 4G/LTE in the same places.
bowserm said:
I just want to say thank you for this. I know this is an old thread, but I just purchased a Rogers i717. I had it unlocked to use my TELUS account, and i kept getting strange errors.
I flashed the stock TELUS image, and modem. From 2.3.6 using Kies I was able to upgrade to 4.0.4.
I must say, TELUS does not put any bloatware on their device compared to the Rogers.
Thank you again
Click to expand...
Click to collapse
Same here. I just want to say thank you for this awesome thread. I accidentally bricked my Telus i717 while trying to root/flash the kernel. Followed the instructions here to restore back to stock rom and now trying to root again.
Related
Well....I think I might have done something really stupid. It should be obvious at the moment that I didn't understand completely what I was doing.
I just picked up my SGSII today from AT&T. In reading around I had hopes of a new ROM as I was very happy with CM on my captivate....unfortunately while in the process I followed instructions from an (obviously) european version of the phone and installed the KG6 modem....now I have no data connection.
I'm feeling really foolish...is there any way that I can get the stock modem for the AT&T U.S. Galaxy S2? Any help would be greatly appreciated.
Anybody? My phone is completely non-functional at the moment.
I've learned my lesson; I'll leave the modding to the more adept, I just need to get my phone back.
Try the stock plus root rom for odin/heimdall and that should over write the modem you flashed
Sent from my SAMSUNG-SGH-I777 using xda premium
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Entropy512 said:
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Click to expand...
Click to collapse
What would be the easiest way, If possible, to install european ROMS on the ATT version? Maybe, install the ROM without their kernel and modem and replace them AT&T's ?
Entropy512 said:
FYI, you shouldn't expect rapid replies on a Monday morning.
The modem is currently missing from my "unbrick" packages, but this is an omission. I'll dump modem.bin tonight and post it up in my unbrick thread.
insaneturbo13 is not correct - as I said, my stock unbrick package is currently missing the modem.bin file. I will correct this tonight.
Click to expand...
Click to collapse
Thank you! Thank you! Thank you!
Donation coming your way.
Thank you!
daraj said:
What would be the easiest way, If possible, to install european ROMS on the ATT version? Maybe, install the ROM without their kernel and modem and replace them AT&T's ?
Click to expand...
Click to collapse
I believe that alone should work - I haven't had time to test yet.
cgrums said:
Well....I think I might have done something really stupid. It should be obvious at the moment that I didn't understand completely what I was doing.
I just picked up my SGSII today from AT&T. In reading around I had hopes of a new ROM as I was very happy with CM on my captivate....unfortunately while in the process I followed instructions from an (obviously) european version of the phone and installed the KG6 modem....now I have no data connection.
I'm feeling really foolish...is there any way that I can get the stock modem for the AT&T U.S. Galaxy S2? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Feeling kinda foolish... I did the same thing yesterday AFTER I flashed the wrong kernel. (european kernel without proper button support) then everything went to hell, now I am back to the proper kernel, and the deoxed att firmware from the guide here on the forum... i just need the modem up and running with the right firmware and Ill have a working phone again
jdip1978 said:
Feeling kinda foolish... I did the same thing yesterday AFTER I flashed the wrong kernel. (european kernel without proper button support) then everything went to hell, now I am back to the proper kernel, and the deoxed att firmware from the guide here on the forum... i just need the modem up and running with the right firmware and Ill have a working phone again
Click to expand...
Click to collapse
I got all excited when my brother got his gs2 and I flashed a euro rom before I realized what I had done. I used entropy's stock package to get him fixed. Then he calls me from home and starts *****ing about how he can't use data unless he's on wireless. I put 2+2 together.
I am, like the others here, super eager to get that modem file when you post it. It would be a huge help. If it's not too much work on your part entropy, could you post a cwm version of the modem as well? I'd rather not have to flash him back to stock again just to fix the modem.
He's an iphone expat so I'm trying to make his android life smooth as possible.
I'm going to get home around 6 PM Eastern.
Initially I'm going to post up a Heimdall (and hopefully also Odin) flashable image of just the modem binary for those in a hurry, then I'll work on a CWM zip (need to find a reference one to pick apart in case it's different from the Infuse), then I'll upload a new more complete "unbrick".
Thanks for the donation cgrums.
OK, here's an emergency flash package for modem recovery - http://www.multiupload.com/JTFK1K1FOA
It's just a little too large to be an XDA attachment, sorry if multiupload is a problem for you.
It contains both a raw modem.bin, and a .tar file containing modem.bin (yes, redundant!)
It is NOT a CWM-flashable ZIP. Repeat, do NOT try to flash this ZIP in CWM. Seriously, it won't work!
The following method for flashing the modem IS tested:
Unzip the attached package
Use Heimdall to flash from the command line
Code:
heimdall flash --modem modem.bin
The following method for flashing the modem should work but is NOT tested:
Use Odin to flash the contained .tar file, using the Phone slot for the .tar
Man, before I even leave work! Awesome! Thanks again!
I made an error above - I believe in Odin, modem has to be in the Phone slot not PDA.
As I said in the post above - Heimdall is tested, Odin is not.
As to CWM - the maintainer of the I9100 modem collection frowns upon CWM for modem flashing - http://forum.xda-developers.com/showthread.php?t=1131950&page=2 . It sounds like CWM-flashing of modems might have issues on our device, I haven't had time to investigate but right now I'm going to trust pulser_g2's judgement for until I have more time to figure out GS2-isms of modem flashing. I've got a ton of stuff to do and I'm going to drop CWM-flashing of modems in priority for now since it should rarely be needed.
Entropy512 said:
I made an error above - I believe in Odin, modem has to be in the Phone slot not PDA.
As I said in the post above - Heimdall is tested, Odin is not.
As to CWM - the maintainer of the I9100 modem collection frowns upon CWM for modem flashing - http://forum.xda-developers.com/showthread.php?t=1131950&page=2 . It sounds like CWM-flashing of modems might have issues on our device, I haven't had time to investigate but right now I'm going to trust pulser_g2's judgement for until I have more time to figure out GS2-isms of modem flashing. I've got a ton of stuff to do and I'm going to drop CWM-flashing of modems in priority for now since it should rarely be needed.
Click to expand...
Click to collapse
I flashed the tar in odin using phone, the phone rebooted, but it will only make calls. The phone cannot use the internet when the wifi is off. Do you have any suggestions? I am going to try flashing your entire recovery image when you update it tonight.
What does your baseband version say now? If it flashed properly it should say UCKH7.
If it doesn't, it didn't flash for some reason. I know it flashes properly with heimdall, odin is kind of untested.
Entropy512 said:
What does your baseband version say now? If it flashed properly it should say UCKH7.
If it doesn't, it didn't flash for some reason. I know it flashes properly with heimdall, odin is kind of untested.
Click to expand...
Click to collapse
I had my brother do the factory reset, wiping the user data. That seemed to fix it (although we did flash your modem prior). Thanks so much!
I am happy to report that I am on my way back to functionality!
I've noticed a difference in connectivity though. At times, typically out-of-doors, I get decent signal strength and HSPA+ connection. Call service is a bit spottier than I remember it before the hijinks.
Inisde buildings is a completely different story...I can't seem to maintain a data connection of any type.
My baseband shows I777UCKH7 so I believe the flash went well. I'm planning to flash back to stock to get a good starting point going forward.
Anybody else experiencing similar issues? Thoughts?
This community is awesome!
I think someone did indicate that things were funky until they wiped - not sure though.
One click + CWM ICScrewed = in call audio problem
Hi I used your on click root kernel and then used CWM to flash the ICScrewed ROM .zip file.
Now I am having a problem where when I make or receive a call there is no audio. I still have data and wifi connectivity though it seems.
Could it be a problem with my modem? If so how do I flash another and where can I find the appropriate one?
Thanks, and sorry I cannot post on the ICScrewed page as I do not have permission to post in development yet.
jgordo32 said:
Hi I used your on click root kernel and then used CWM to flash the ICScrewed ROM .zip file.
Now I am having a problem where when I make or receive a call there is no audio. I still have data and wifi connectivity though it seems.
Could it be a problem with my modem? If so how do I flash another and where can I find the appropriate one?
Thanks, and sorry I cannot post on the ICScrewed page as I do not have permission to post in development yet.
Click to expand...
Click to collapse
I have no "one click" kernel. Any "one clicks" are repackaged by someone else and I have no idea what they contain in many cases.
My apologies if this has been asked before, but I've spent hours searching and think I've done a better job of confusing myself, than answering my question.
I've rooted my wife's Samsung Fascinate, using Super One Click and removed all annoyances such as the Verizon bloat ware and got add blocker installed, etc. The point on doing so, was also to improve battery life, backup the ROM and some of the other associated advantages with rooting. One of my main goals was to also install a custom ROM on her phone, as the factory ROM is very flaky. It receives emails, then doesn't. It sends a text, then can't minutes later. It's been a great phone HW wise, but just junk as far as the OS.
Thus far, all attempts to backup the factory (modified) ROM has failed, which evidently is part of the limitation with the stock ROM. At this point, she's so frustrated (me too) with her phone, that it's time to get serious.
So, my confusion stems from varying reports regarding what the proper steps are to install a new ROM. On my Thunderbolt, I simply used CWM to install and backup/restore my ROMs as needed. This doesn't seem to be the case with the Fascinate and there's varying reports of whether this can even be done if Super One Click was used.
Has anyone had experience with flashing new ROMs after the phone was rooted and if so, by what method?
Her current ROM details are:
Firmware
2.2.2
Baseband
S:i500.04 V.ED05
Kernel
2.6.32.9
Build
SCH-I500.ED05
Thanks in advance.
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cm7 zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
droidstyle said:
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cwm zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
Click to expand...
Click to collapse
Okay, that makes a lot more sense now. Thanks for the quick reply.
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
ibsk8 said:
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
Click to expand...
Click to collapse
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
droidstyle said:
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
Click to expand...
Click to collapse
I never could get to the ROM flashing part. Every time I tried I got the same set of errors as when trying to backup the original ROM. I did manage to get the CWM 4 fix applied through ODIN and it said successful, but nothing really changed and my attempts to flash the new ROM still failed.
I searched around this forum and others and found another file to flash and things went very badly. The flash was moving super slow and I left the phone, so I wouldn't be tempted to do anything stupid and after an hour, it was at the same point. When I rebooted the phone, I got a sad face icon only. No Samsung logo or anything.
Luckily, I was able to re flash the stock rom, but after messing with it for 4 hours and getting nowhere, I decided the stock ROM was good enough for now. I have no idea why this phone is so pesky and read how some folks had to ref lash the stock ROM, before being able to flash a new ROM. I made one final attempt to do so and got the same error as the first time, so that was enough for that day. I don't recall exactly what the error said at this point, but I had blue text, followed by orange, which I think said something to the fact that is was unable to verify the package, followed by red text showing the failures.
Sorry there's no more detail than that for now. I may try this again in the future, but as mentioned this is the wife's phone, so I can't take nearly the liberties with it as I could my own.
If anyone has any ideas on what I may be able to try next, that would be great. If not, I may keep digging on this forum (a very helpful place indeed) and see what the options may be.
Thanks everyone for your help.
refer to section 3 of my guide and follow those steps. for some reason certain fascinates have trouble flashing mtd roms when starting from ed05. I have to start with dl09 eclair then flash cm7. look in page 2 of this section for my guide. all files needed can be found there aswell. good luck!
Hey guys
I rooted my Note and after few reboots my phone stocked on splash screen with logo Rogers. If i understood right I had a problem with new ROM.
Then I flashed my phone via Odin using pda-odin-rogers-stock-system-boot.tar. rebooted and I thought my phone works fine but I have new problem- phone doesnt see sim card. After I flashed modem via CWM using Rogers-Modem-CWM.zip but still have the same problem- NO SIM card...
I did it following this thread : http://forum.xda-developers.com/showthread.php?t=1630843
Maybe some of you know what to do or any ideas how to solve this problem?
Thank you
What sim? Did you have to flash the radio at some point? The rom usually doesnt touch the radio unless you used an exe like the ICS leaks.
Sent from a big ass phone
I have sim card from Koodo.
I tried to fix this problem with sim card and thought at some point it would help.
I reverted regular GB folowed all steps in thread http://forum.xda-developers.com/showthread.php?t=1630843
These are Odin-flashable .tars of the stock Rogers system, boot/kernel, and radios and can be used to revert to stock.
Files Available
NB: All files are zipped to save space. Please extract the .tar before flashing via Odin.
pda-odin-rogers-stock-system-boot.zip This .tar contains the stock system.img.ext4 and stock boot.img and can be used to assist in resetting your flash counter using braway's method. Flash it via Odin's pda option. The recovery.img has been removed to preserve CWM if you've already flashed it to your phone. Once your flash counter has been reset, you can then return recovery to stock via this method using just the recovery.img file in the archive here.
phone-odin-rogers-stock-radio.zip This .tar contains the stock Bell modem/radio and is flashed via Odin's phone option. Not working properly. Apparently I don't know how to make Odin flashable modem .tars, lol
Rogers-Modem-CWM.zip This is a CWM-flashable .zip of the modem files. Should work perfectly. Let me know if you run into any problems.
Have you rebooted into recovery and done a full factory wipe/reset ?
Take a look at this thread. These files work 100%.
http://forum.xda-developers.com/showthread.php?p=26232608#post26232608
Yes I did it twice.
I dont understand what can be wrong.
Thank you Agoattamer
I found these files few hours ago and flashed them. http://forum.xda-developers.com/showthread.php?p=26175261#post26175261
Phone looks like new but doesnt work with sim cards.
When I was flashing first time I had sim card inserted could it damage radio or modem during the flashing?
Now I have a pretty nice small tablet for 550$)))
I was wondering if in repair store someone can help me to fix it after all my actions)))) but I still dont give up.
It will be last time when I modify my devices))) Lol
Now I dont know have to live without phone. Yesterday, when bricked my phone, I even didnt have alarm clock so I seted up timer on my appliance on kitchen
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
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.