Related
This thread contains the stock ROGERS firmware that comes with the GT-P1000R.
Andrew_Low has provided a copy of his stock FROYO backup, which I tested on my tab and confirm that it is working. The kernel is rooted, other than that it is a clean ROGERS rom. For further details on this refer to post 2.
He was also able to capture the GINGERBREAD update (which I have not tested as of yet, any testers please post your results).
This is the stock update available from KIES. For further details on this refer to post 2.
Many thanks to him for this, if it helps you, hit his thank you button. If you find this thread helpful as well, hit my thank you button.
Instructions on flashing are not provided. If you need these files it means you know how to flash your device, have flashed a custom ROM previously, and require this to return to a stock state.
As usual FLASH AT YOUR OWN RISK, don't blame ANYONE here for ANYTHING.
PLEASE NOTE: The FROYO stock ROM is currently unavailable, will be back up soon.
Downloads can be found here
Further more, I would like to thank kpetrie77 for setting up a wiki on the Samsung Galaxy Tab, the wiki is full of great links for all things Galaxy Tab. You can find it here, and if you have anything to contribute please do so as it helps everyone here at XDA.
Thanks to theREDlegion for putting this together. Happy to try to help others both on P1000 series.
The FROYO version was rooted with SuperOneClick 2.2 - if you use this utility and unroot it will remove the superuser.apk and after a reboot, adb won't connect as root. Before you do that reboot, you'll want to remove the busybox binaries /system/xbin to reach as 'near a stock state as possible'.
The GINGERBREAD version was snagged from Kies during the update process. It seems the Check Fus Donwloader doesn't know about Rogers (but it knows about Bell?!).
Real life gets in the way for hacking, but I'm motivated to make the Tab (mine included) as useful as possible beyond stock.
Thank you. This will come in handy.
SaHiLzZ said:
Thank you. This will come in handy.
Click to expand...
Click to collapse
Glad to help.
If possible can you post your results. It might be useful info for others.
Thanks,
RED
user8525 said:
Was hoping you could answer this question. I am currently running stock froyo on my Rogers Tab. If i update to Gingerbread is there any negatives with me wanting to upgrade in the future to other builds. Does it lock the bootloader? or is the bootloader already locked?
Thanks.
Click to expand...
Click to collapse
Sorry to respond almost a month later but I have not been checking my PM's regularly for the past little bit with so many other things on the go. It is better to post these kinds of questions in the thread itself, as this would help other members with similar questions. That is why I created the thread, and this is a good question to ask and answer in the thread. It is a REALLY GOOD QUESTION, that I'm sure others would be interested in and therefore I will post it in the thread. If you would like me to remove your username please contact me.
The Samsung Gingerbread release is not locked, it is signed. You CAN flash custom kernels and ROMs, DO NOT use the PATCH tool that Chainfire has provided, if that is why you ask, see that thread. That patch is an amazing tool provided by Chainfire, there is nothing wrong with the patch it just does not apply to us. If you use it, the tool will ask you to patch, DO NOT PATCH. You will screw things up with it and have to re-flash, re-stock and re-do everything just to fix it.
If you are uncertain if you should flash anything, than DON'T FLASH ANYTHING. Read, read than read some more before continuing any further.
These stock ROM's are not SamFirmware downloads, they are STOCK Rogers firmware from the device and from the update from KIES.
theREDlegion said:
Glad to help.
If possible can you post your results. It might be useful info for others.
Thanks,
RED
Click to expand...
Click to collapse
I haven't had the opportunity to restore a tab yet. One of these days someone will lend me one for testing and I will try test these files.
Looking at the files, these will need to be restored via heimdall correct?
Also looking for the Bell Froyo rom. Any suggestions?
SaHiLzZ said:
...heimdall correct?
Also looking for the Bell Froyo rom. Any suggestions?
Click to expand...
Click to collapse
Heimdall is correct.
Have not come across a stock BELL Froyo ROM (haven't even looked really). Will see what I come across and post back.
How to flash P1000R to stock Gingerbread
I wrote up how to take the Gingerbread firmware in the OP and flash it to your device.
http://lowtek.ca/roo/2012/restore-rogers-galaxy-p1000r-to-stock/
It's short and sweet. Ubuntu (Linux) as my desktop, heimdall as the flashing tool. Key is really mapping the files in the firmware to the heimdall partition names and getting through the boot sequence (flash, recovery and allow update, reboot).
Rogers CWM flashable modem UXJJ6
Following instructions found here http://androidforums.com/galaxy-s2-...t/540640-make-my-own-cwm-flashable-modem.html I created a CWM flashable modem of the Froyo Rogers ROM.
Why? Well, this modem didn't appear to be available in this form - so here it is as an attachment.
****Seems like we're getting alot of new users thanks to the price cut on our phones, and while we have an amazing amount of information available it seems that it's overwhelming for new users and they end up posting questions that are answered already in stickies, etc, just because they don't know where to start, hopefully this guide will cut down on that.... please feel free to suggest things that should be added or any changes I should make to make this better and more complete, or if you think this is redundant and a waste of time feel free to flame me, you won't hurt my feelings, just trying to give back to the community, make things easier for new users, and cut down on "how do i..." posts that have been answered elsewhere...thanks!****
Welcome To the Epic 4g Touch
As a new user its probably overwhelming trying to figure out where to start since this is a relativity mature device, most of the existing users are well versed in the more basic tasks, and we have SO MUCH info all over the boards here, this guide should help you get started....
1. The 1st thing you'll probably want to do is root. If you're coming from an HTC device or are new to android you're probably not familiar with Odin. Odin is Samsung's in house recovery tool that leaked a few years ago. It lets you flash rom's via usb connected to a PC. Odin is PC only, if you use linux or mac the easiest way to get root would be to use a PC, however there is a cross platform tool, Heimdall, that allows you to flash on OSX/Linux... Going forward in this guide though I will only be referring to using 1-click Odin's on PC's as i feel this is what the vast majority of people will be using...
- You'll want to first go to Sfhub's stickied thread in the dev section, Sfhub has been kind enough to make rooted 1 click Odin images for us, so especially if you're coming from a HTC device you'll be amazed how easy these phones are to root...(found here http://forum.xda-developers.com/showthread.php?t=1342728)
- As of today (07/09/12) if you buy an E4GT it'll come with the EL29 gingerbread system, this ( http://forum.xda-developers.com/showthread.php?t=1433101 ) is the appropriate Odin 1 Click for you to get root, again, thanks Sfhub
7/12/12 edit: Sprint is pushing the OTA to ICS as of today. It is build FF18, the rooted odin one click can be found in yet another thread by Sfhub here ( http://forum.xda-developers.com/showthread.php?t=1721229)... as the emmc bug seems not to have been addressed in the kernel I will leave the rest of the post unaltered for now until most roms have been updated to a kernel built from source with the code that triggers the bug removed. Until then, as stated later, some ICS recoveries are considered safe (Agats), but it never hurts to take a few extra minuets when flashing to totally avoid the risk of bricking
7/26/12 EDIT:
ICS flashing is now safe AS LONG AS YOU ARE ON ONE OF AGAT63 OR chris41g's SAFE KERNELS, these are built from source and have the offending mmc_cap_erase code removed/disabled. The kernel repo is found here (http://forum.xda-developers.com/showthread.php?t=1662295) you can mobileODIN the tar's or flash the zip's via cwm
- You can refer to Garwynn's Official ICS OTA update thread for more information on the update (http://forum.xda-developers.com/showthread.php?t=1765953)
-After running the 1 Click Odin for your device you'll want to go back to the main thread ( http://forum.xda-developers.com/showthread.php?t=1342728 ) and download the auto root tool and choose option C to install Clockworkmod recovery- a custom recovery that will allow you to flash roms and make nandroid backups- on your phone. Dev VeNuM has posted a very detailed guide explaining what clockworkmod is and how to use it, which is stickied and can be found here ( http://forum.xda-developers.com/showthread.php?t=1587607 )
- I'm not providing detailed instructions as those are included in the linked to threads... should you find the directions difficult to follow user qbking77 has made really great informative videos, linked to in the directions, detailing the aforementioned processes that should help clarify things further for you.
2. You now have a rooted gingerbread system with custom recovery. You can safely flash any Gingerbread roms from recovery, following the directions posted with the rom of your choice. If you want to flash ICS roms however, you have some more reading to do, as this phone can be bricked if you do not follow directions....
- The Epic 4g Touch has a bug in it's emmc controller that can cause the /data partition to become inaccessible/unrecoverable sometimes thanks to the wipe process when flashing from ICS recoveries... DO NOT FLASH FROM ICS RECOVERIES!!!! (7/26/12 edit: OLD, you can now flash from ICS as long as you are on a safe kernel, safe kernels can be found in the repo linked to earlier this post)
7/11/12 edit: In the FF18 source Garwynn has confirmed the presence of the offending code that triggers the emmc bug (http://forum.xda-developers.com/showpost.php?p=28609341&postcount=32) meaning that it will eventually be safe to flash from ICS as long as the offending code is removed by the dev of the kernel/rom...
- Please see this (http://forum.xda-developers.com/showthread.php?t=1525495) thread by xST4T1K which details how NOT to brick your device... It is slightly out of date but still very relevant... if you want a more technical understanding of what this emmc bug is and why this is happening you can see Sfhub's thread in general related to it (http://forum.xda-developers.com/showthread.php?t=1644364 ). The OP contains all of the information that our users have been able to figure out about this bug... Be sure to thank these people, as their hard work has made it exponentially safer for all of us to flash ICS roms on our phones...
-Every ICS rom will have a flashing guide in it's dev thread, its HIGHLY suggested you read and reread the guide for the rom you want to flash and follow it EXACTLY, taking the extra time upfront to fully understand what you're about to do will save you alot of trouble going forward.
-Put simply though you will always want to ODIN or Mobile ODIN (mobile Odin is an app made by the dev chainfire, available in the play store, that allows you to preform Odin flashes from your phone without using a PC) the el26 Gingerbread kernel/recovery and flash any ICS roms from that. NEVER FLASH FROM AN ICS RECOVERY, THAT IS HOW BRICKS ARE MADE!!!! Also do NOT use Rom Manager or Touch recovery!!!! (7/26/12 edit: also now outdated, as long as you are on a safe kernel you can just flash via cwm in ICS, no need to ODIN back to EL26)
3. Additional Information...
-modems, there are a variety of modems available for the E4GT, and all can be found in the modem repo ( http://forum.xda-developers.com/showthread.php?t=1764210 ). Every phone responds differently to different modems and you may want to try some new ones if you are dissatisfied with the current one you have.
- Jelly Bean... Please do not post asking "Is Jelly Bean available for this phone!1!!!!!" / "when i get jellybean!!!1!!11!!"... we have some awesome dev's for this and there are quite a few working on it currently. It is currently booting with some issues, but should be ready to use as a daily in the coming weeks. DO NOT post asking where to find current builds, dev's will post in the development section once they feel its ready for release, same goes for CM10
- qbking77 has posted videos of reviews and install guides for most of the roms around here. If you find the install directions confusing watch the appropriate video and see if that helps you at all, he does a very good job of walking you through it... Also his reviews are quite helpful as well if you're not sure if you want to flash or not... Please consult these as opposed to starting a thread asking "should i flash XXXX?? is it good?" these things are a matter of personal preference... Also pretty much everything around here these days is good enough to use as a daily driver, all roms will have a working/not working section... refer to that, if everything you use is marked as working and the rom is not labeled "alpha build HIGHLY unstable, etc..." chances are it'll work for you well day to day and does not warrant starting a thread asking if its good enough to use as a daily driver...
- Stock roms/stock leaks are labeled as EL29, FF18, etc... all this represents is the date Samsung compiled the rom... the 1st letter represents the year (E=2011 F=2012) and the second represents the month (January=A all the way through December=L) and the number is the date. Modems follow the same naming scheme. The modems available are not limited to the "matching" rom in any way, ANY modem can be used with ANY rom (thanks to kingdazy for clarification on how the Samsung naming scheme works!)
7/26/12 EDIT:
It's been brought to my attention that we have a lot of people posting asking how to return to stock GB for whatever reason... all that you need to do is ODIN EL29, sfhub's one-click can be found here, its all you need ( http://forum.xda-developers.com/showthread.php?t=1433101 )
Also if you took the OTA and want root you can just ODIN the FF18 rooted one-click, found here ( http://forum.xda-developers.com/showthread.php?t=1721229 )
IF you need to get rid of the yellow triangle on the bootscreen in order to return your phone to sprint/it annoys you or whatever you need to download chainfire's app "triangle away" from the play store, its requires ICS and its like $1.99, buy it even if you don't need it, dude deserves the money for his awesome work on android devices... If you're still on GB you'll need a usb jig
~I will be adding more info to this over the next few days, but I figured this was enough to get started on, again any suggestions or additions are welcome and encouraged! the easier we make it for new users to get started the fewer times we'll all have to answer the same questions over and over again... If i referred to your work without crediting it I assure you it was accidental and if you notify me of my mistake I will make sure to edit the post accordingly to credit you, again thanks for any input!~
will be editing this to bring it current and for style this weekend, overdue for an update
This is very nice.. I wish I read something like this when I first got my phone months back, I had to take pieces of information from "here and there" and put it all together.. It can be overwhelming but it's not impossible to the new users
MiguelHogue said:
This is very nice.. I wish I read something like this when I first got my phone months back, I had to take pieces of information from "here and there" and put it all together.. It can be overwhelming but it's not impossible to the new users
Click to expand...
Click to collapse
thanks for your input! i'd actually thank you but have used up my 8 already today! I thought this would be useful as I've been seeing a lot of the same questions all over the place recently which are already answered in various threads, and there are some really good highly detailed guides out there as well, but we're kind of lacking in something that brings them all together in a noob friendly manner, like if you've never had a Samsung phone before its not immediately obvious that you need to start with sfhub's Odin thread since you're all like WTF is a ODIN?!? same with is it safe to flash xxxx from xxxx... those of us that have been around know the drill by now, and i guess it is kind of elaborate vs flashing on most phones, but its bothersome to have to reply to the same question over and over again, so hopefully this helps make it easier... like i said i will continue to add to this and welcome suggestions, again thanks for your input!
Thank you for this excellent guide. I'm a dev coming from the 3D and was about as lost as one can be, and this was a massive help to me. I appreciate it. :good:
No problem man, that's why I took the time to write it, have fun with the phone, its awesome... jet life till the next life
Sent from my SPH-D710 using xda app-developers app
great post, OP!
perhaps you might consider a concise explanation of build designations/dates (fdxx ffxx, ect) vs modem, and how they are related but not exclusive?
i struggled with that my first few days...
kingdazy said:
great post, OP!
perhaps you might consider a concise explanation of build designations/dates (fdxx ffxx, ect) vs modem, and how they are related but not exclusive?
i struggled with that my first few days...
Click to expand...
Click to collapse
I will edit to add that in later today, thanks for the suggestion!
cp320703 said:
No problem man, that's why I took the time to write it, have fun with the phone, its awesome... jet life till the next life
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
You already know man.
Outstanding write up cp320703 !
Thanks to everyone on this site, all guides were done so well I didn't have any questions and I rooted my phone and installed a custom rom and modem very easily. Thanks to all who made this possible. I was tired of waiting for ICS from sprint, so thank you all very much.
Rafter_Man said:
Thanks to everyone on this site, all guides were done so well I didn't have any questions and I rooted my phone and installed a custom rom and modem very easily. Thanks to all who made this possible. I was tired of waiting for ICS from sprint, so thank you all very much.
Click to expand...
Click to collapse
Thanks op.
Thanks for this guide, it has been really helpful. I have had htc phones before, but this is my first Samsung. Just a little bit different.
Great guide, I'm coming over from my evo 4g and was a little worried about rooting my touch. This guide takes away the doubt I had.
Sent from my PC36100 using xda premium
thanks
BigSmoke53 said:
Great guide, I'm coming over from my evo 4g and was a little worried about rooting my touch. This guide takes away the doubt I had.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
thanks for your guide and information; already I do some of the tested Roms and every I test i love it
---------- Post added at 12:47 AM ---------- Previous post was at 12:42 AM ----------
thanks for your guide and information; already I do some of the tested Roms and every I test i love it
Thanks my friend sextape recommended me this place as soon as I got the Epic ..
labelexpired said:
Thanks my friend sextape recommended me this place as soon as I got the Epic ..
Click to expand...
Click to collapse
Ah I See You Finally Came Thru Here Glad To See Ya, People On This Forum Are Great Dude!
Okay, first off thanks for the guide. However for some of us senior posters coming from HTC phones there still could be a clearer clarifications.
You say dont flash from ICS recoveries. That is confusing some of us that are not rookies. I understand much different then HTC phones Samsung has the recovery in the kernal. So are you saying not to flash from the built in phone recovery to another ICS build?
From what I gather and please correct me if I am wrong. If you have a custom agat kernal from 2.1 up you can flash betweeen FF!8 official rom or from custom rom to rom as long as you use ODIN to do it? Or is is ODIN MOBILE only do do it as long as you dont attempt thru stock recovery?
How about if your on stock FF18 kernal. Can you still use ODIN safely to go from ICS rom to rom? Should you always use either SFHUBS or Caulikins format program first?
Sorry to sound stupid but the verbage is new to some of us from other phones.
Thanks a bunch!
iceshark said:
Okay, first off thanks for the guide. However for some of us senior posters coming from HTC phones there still could be a clearer clarifications.
You say dont flash from ICS recoveries. That is confusing some of us that are not rookies. I understand much different then HTC phones Samsung has the recovery in the kernal. So are you saying not to flash from the built in phone recovery to another ICS build?
From what I gather and please correct me if I am wrong. If you have a custom agat kernal from 2.1 up you can flash betweeen FF!8 official rom or from custom rom to rom as long as you use ODIN to do it? Or is is ODIN MOBILE only do do it as long as you dont attempt thru stock recovery?
How about if your on stock FF18 kernal. Can you still use ODIN safely to go from ICS rom to rom? Should you always use either SFHUBS or Caulikins format program first?
Sorry to sound stupid but the verbage is new to some of us from other phones.
Thanks a bunch!
Click to expand...
Click to collapse
sorry just saw this post, ODIN is always safe, and now that the emmc bug is understood most all of the kernels in the repo are safe as well, a bit of code just needed removed from stock to make them so. Odin and cwm are two means to the same end for the most part, however outside of official leaks you won't really be flashing roms via ODIN. Basically if you are on stock ff18 rooted you would want to ODIN a safe kernel, then you would be good to flash roms via cwm going forward
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
sorry just saw this post, ODIN is always safe, and now that the emmc bug is understood most all of the kernels in the repo are safe as well, a bit of code just needed removed from stock to make them so. Odin and cwm are two means to the same end for the most part, however outside of official leaks you won't really be flashing roms via ODIN. Basically if you are on stock ff18 rooted you would want to ODIN a safe kernel, then you would be good to flash roms via cwm going forward
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
That perfect! Thanks for clarification on this. I am sure others wondered the same.. Now if there was just a nice Vanilla stock type tweaked non theamed ICS rom I would jump in. I will however ODIN Agats 2.3 to be ready! You rock!
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
Click to expand...
Click to collapse
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
As I understand it, you should just be able to re-apply a stock GSM ROM to your Galaxy Nexus to get back to the original state of things. That's the whole point of a Nexus - it's stock with no customisations etc. It sounds like you'll have start from the very beginning and reinstall apps etc. but I guess you've already bitten that bullet, and presumably you're happy with your current ROM configuration?
It's not clear what recovery you have installed at the moment. You've made mention of CWM ... Clockwork Mod recovery possibly installed in that case? Again, as I understand it, Clockwork Mod recovery means you can't <s>receive</s> apply OTA updates. If you're on a stock ROM you should still receive notification about them though? If you are truly on stock, but have the Clockwork Mod recovery installed you can reinstall the stock boot recovery image. You should be able to find the stock images via a google search easily enough.
Once you've determined which recovery you currently have installed you'll have a better idea of how to get back to stock everything.
Above all, don't panic
PS I could add that busybox doesn't screw stuff up ... it just allows you to screw things up
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
real_becksaufex said:
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
Click to expand...
Click to collapse
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Syn3rgi3 said:
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Click to expand...
Click to collapse
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
I executed that successfully however CWM still exists =/
Syn3rgi3 said:
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Click to expand...
Click to collapse
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
Disable bootloader?
Pressed from my Maguro
efrant said:
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Syn3rgi3 said:
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Click to expand...
Click to collapse
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
LOL, Telstra
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
DO NOT GET YAKJUDV!!! Try and just get Yakju, Then you will get your updates from Google NOT Telstra. You don't need the Telstra stock rom, you can use Google's Yakju. I have a Telstra one and I get updates from google because I put Yakju. You will need to flash the ROM though your pc. I have been through what you have with the exact phone (Telstra one), If you need any help you can PM me
I agree with the post from Atifsh.
The guide offered by Efrant gives you, step by step, everything you need to reach your goal.
Contrary to your case I did not need to change the factory ROM but I applied the rest of the guide (for instance post 855 in Efrant thread shows what I did).
Since I want to learn I refuse, so far, to rely on a toolkit.
I deeply share Efrant philosophy of learning. And I agree on the purpose of the XDA forum. It is not a walking clinic, it is a hospital implementing new medecines:laugh:.
Finally, taking into account my age I am closer to the hospital than to the clinic.
Thanks to Efrant and few others I am doing "stuff" I did not know I could do.
And, yes I am over the time I used to want and get everything at once.
efrant said:
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
Click to expand...
Click to collapse
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
As you say, the problem is you need the stock recovery for the build that you are on. What build is the backup you restored? If it is ITL41F, then you are in luck. Go to this thread and download any one of the two yakjudv updates to /sdcard. Use CWM to flash it, and you will be all set -- it will wipe CWM and replace it with the correct stock recovery for that build.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And please change the title of this thread to "Return to stock yakjudv" as it is very confusing. Most people refer to stock as yakju or takju for GSM devices.
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
picton said:
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
Click to expand...
Click to collapse
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
efrant said:
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
Click to expand...
Click to collapse
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
picton said:
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
Click to expand...
Click to collapse
Ok, are you flashing it in CWM? The "red triangle with a robot" IS the stock recovery, it is not an error. What is the exact procedure you are using to flash it?
i have seen all the "once you change to the new 4.3 bootloader you can't go back" comments which i thought was no big deal. i don't plan on going back to an older version. anyways here's the story.... i flashed "Stock MOD ROM" by saranhai and the "MJB" bootloader as per the directions for that ROM. i just wasn't feeling that ROM after i used it for a couple weeks but i wanted something stock looking so i thought i would give the "i747z" ROM by agriff a try. so i flashed that rom and the "MJ2" bootloader for that per the directions. In my not so infinite wisdom they are both "4.3" based roms so shouldn't be a problem right???? well as soon as i rebooted the phone after flashing it shut off and has no response after that. soooooooooo did i just brick my phone???
lfaulkner29 said:
i have seen all the "once you change to the new 4.3 bootloader you can't go back" comments which i thought was no big deal. i don't plan on going back to an older version. anyways here's the story.... i flashed "Stock MOD ROM" by saranhai and the "MJB" bootloader as per the directions for that ROM. i just wasn't feeling that ROM after i used it for a couple weeks but i wanted something stock looking so i thought i would give the "i747z" ROM by agriff a try. so i flashed that rom and the "MJ2" bootloader for that per the directions. In my not so infinite wisdom they are both "4.3" based roms so shouldn't be a problem right???? well as soon as i rebooted the phone after flashing it shut off and has no response after that. soooooooooo did i just brick my phone???
Click to expand...
Click to collapse
Checked here when I saw this. http://forum.xda-developers.com/showthread.php?t=2576895 see the linked post in dntesinfrno's post #5.
Bottom line: MJ2 is the leaked firmware & its bootloader behaves similarly to MJB. dntesinfrno's link shows the special handling regarding asserts & the updater script that flashing over MJB demands.
ok.... i read all that and the links and other posts around dntesinfrno's links. still confused.... part of what you said is "they are similar" so to me that means "should be fine" and dntesinfrno talks about "special handling" which i did not do, so now what??? i can't get into download mode or recovery mode from the standard button pushing method so is there anyway to fix this?
lfaulkner29 said:
ok.... i read all that and the links and other posts around dntesinfrno's links. still confused.... part of what you said is "they are similar" so to me that means "should be fine" and dntesinfrno talks about "special handling" which i did not do, so now what??? i can't get into download mode or recovery mode from the standard button pushing method so is there anyway to fix this?
Click to expand...
Click to collapse
I apologize. I get how you saw the v4.3 similarity of MJ2 & MJB but what I am referring to is their similar restrictions limitations & exclusions. Even against each other.
"No Response" describes a hard brick condition. DIY fixes using the phone alone require Odin mode & / or custom recovery.
Odin (download mode) requires an OTA 4.3 flashable tar of UCUEMJB which is not yet available for i747.
That unavailable firmware or its bootloader component is the only safe odin flash for bringing back your phone.
custom recovery would add the safe alternative of reflashing Stock MOD so you could begin again.
I may have seen something helpful for the hard brick. I'll check back & post if I find it.
These are the threads I mentioned:
http://forum.xda-developers.com/showthread.php?t=2559684
http://forum.xda-developers.com/showthread.php?t=2549068
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
AWESOME.... thanks for the help. I think i will attempt to do the fix myself this weekend and if that doesn't work then i will try the ebay fix route. thanks again for your help and i will update as to my success, or lack there of, depending on the outcome.
pc103 said:
Checked here when I saw this. http://forum.xda-developers.com/showthread.php?t=2576895 see the linked post in dntesinfrno's post #5.
Bottom line: MJ2 is the leaked firmware & its bootloader behaves similarly to MJB. dntesinfrno's link shows the special handling regarding asserts & the updater script that flashing over MJB demands.
Click to expand...
Click to collapse
Just to clarify any confusion, my post was regarding installing a ROM that doesn't contain the MJB bootloader in the assert and the dangers involved in attempting to downgrade the bootloader. This will have no affect on recovering from a possible brick after downgrading MJB.
dntesinfrno said:
Just to clarify any confusion, my post was regarding installing a ROM that doesn't contain the MJB bootloader in the assert and the dangers involved in attempting to downgrade the bootloader. This will have no affect on recovering from a possible brick after downgrading MJB.
Click to expand...
Click to collapse
As such I believe your posts detail precisely why downflashingover the MJB, even with MJ2; bricks. Once that happens, the other thread I linked details a possible way out for flashers who missed out on the asserts & updater script due diligence you described. Thanks again for documenting that & for your clarification.
I would like to thank both of you and all the other great people that contributes to this awesome forum!!!
I followed the directions in the link about flashing a debrick image on a 16gb sd card and it worked flawlessly. was almost easier than flashing a Rom to begin with. although I have no intention of having to do that again.
but I have a question, now that I am on the MJB bootloader, when flashing other 4.3 roms from now on I shouldn't need to flash a new bootloader.... correct???
Sent from my SAMSUNG-SGH-I747 using Tapatalk
You're welcome sir. Congrats!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!
General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.
Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.