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.
So folks.
Just reached home with my new phone, an Xperia Arc S LT18a, I believe.
I'm stuck with this firmware 4.0.2.A.0.62 which doesn't seem to have an easy way to get a custom ROM on it yet. Sucks that I didn't read about this before heading out to buy a phone.
I went through one of the guides here and had the bootloader unlocked via Sony's website. However, the rooting instructions didn't work. So searched further and realised the issue.
I've seen people say that they've done it by downgrading to a lower firmware, rooting it and then upgrading the firmware OTA again. Then I read that upgrading firmware OTA with an unlocked bootloader will brick my phone. So I'm not trying that.
Any help on how I could go about this? Simple step by step instructions would be very welcomed, since I don't really know much about flashing various bootloaders and ROMs considering I just bought the phone.
Thanks for reading!
there are many threads relating to this problem....plz read & search before posting....
Well i believe the answer to your questions lie in this Thread ...
'
Hope i was helpful ....
Flash the zip I attached to this post through CWM. That's it, you're rooted
Thanks!
I used the above zip file, but from a different thread and got it working. Cheers to both of you!
RamEsRock said:
Flash the zip I attached to this post through CWM. That's it, you're rooted
Click to expand...
Click to collapse
How can I have CWM on my phone? If I will flash phone I will do it with rooted ROM not stock. For me it's closed circle because I need root'ed device to load CWM on it, and I need CWM to make root.
Can someone explain me it?
szaebb said:
How can I have CWM on my phone? If I will flash phone I will do it with rooted ROM not stock. For me it's closed circle because I need root'ed device to load CWM on it, and I need CWM to make root.
Can someone explain me it?
Click to expand...
Click to collapse
With unlocked bootloader, one can easily flash a custom kernel with CWM, then flash the zip file.
Try reading this http://forum.xda-developers.com/showthread.php?t=1304634
jason statham said:
So folks.
Just reached home with my new phone, an Xperia Arc S LT18a, I believe.
I'm stuck with this firmware 4.0.2.A.0.62 which doesn't seem to have an easy way to get a custom ROM on it yet. Sucks that I didn't read about this before heading out to buy a phone.
I went through one of the guides here and had the bootloader unlocked via Sony's website. However, the rooting instructions didn't work. So searched further and realised the issue.
I've seen people say that they've done it by downgrading to a lower firmware, rooting it and then upgrading the firmware OTA again. Then I read that upgrading firmware OTA with an unlocked bootloader will brick my phone. So I'm not trying that.
Any help on how I could go about this? Simple step by step instructions would be very welcomed, since I don't really know much about flashing various bootloaders and ROMs considering I just bought the phone.
Thanks for reading!
Click to expand...
Click to collapse
I when I rooted my locked bootloader ARC S, I read "The Nutshell Arc Guide" at http://forum.xda-developers.com/showthread.php?t=1304634
Before you start messing with the phone, please see the entire guide first.
Hope I can helped.
Cheers
Hey guys, I am new to this forum here but before anyone flames me, I did read the faqs and tried to uninstall from there but it did not work out. Apparently I dont think you can get rid of CM11 since you cant install any stock firmware older than it? Before I installed CM11, I was on jellybean. I had tried to find the latest kitkat update for the s3 (att) and there is no file of it found online (tried sammobile). When I tried flashing an older firmware with ODIN, it just fails at "NAND!". Any help would be appreciated. I am COMPELETELY new at this so specific directions would be appreciated!
I really do love cyanogenmod but there are simply too many glitches and not enough guidance on how to fix em. I am, however, currently using it on my HP touchpad, if anyone remembers what it is . Maybe ill go back to using it in the future.
thanks!
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
DocHoliday77 said:
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
Click to expand...
Click to collapse
..
I am on "I747UCUEMJB"
and i am not sure what build i am on but according to my "build number"this is what it says: "cm_d2att-userbug 4.4.2 KOT49H"
The main issue is, I cannot find 4.3 update anywhere on the internet
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
DocHoliday77 said:
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
Click to expand...
Click to collapse
i have no idea what MJB means (i google'd it) and i just found out what my bootloader version is via download mode (its at the very bottom) and i have version 2.0?
ok downloading the giant file now. will report details. just follow instructions in the first link?
[sorry, like i said, im a noob so i really apologize for the lack of terms here]
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
DocHoliday77 said:
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
Click to expand...
Click to collapse
Cool! Got it. I think that was my main problem. I could only find 4.0 (or 4.1) and have been trying to use that on ODIN. Perhaps that was the main issue....
Oh already ran it and got "I747UCUEMJB", sorry if didnt say it properly.
Really appreciate the help! Ive at this for days and no solutions. Sometimes the hacking/custom firmware isnt for everybody
Ill update what happens. Download is taking forever.
EDIT: BTW, for the first link, which poster am I gonna have to follow? im assuming "garbage guy"?
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
DocHoliday77 said:
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
Click to expand...
Click to collapse
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
david12795 said:
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
Click to expand...
Click to collapse
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
DocHoliday77 said:
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
Click to expand...
Click to collapse
TIL that OTA arent as fast. Ill download KIES and give it a try.
Just installed KIES and it said my phone has the latest firmware?
david12795 said:
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
TIL that OTA arent as fast. Ill download KIES and give it a try.
Click to expand...
Click to collapse
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
david12795 said:
Just installed KIES and it said my phone has the latest firmware?
Click to expand...
Click to collapse
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
DocHoliday77 said:
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
Click to expand...
Click to collapse
No no! Its fine, I wasnt planning using it or anything, I just wanted to get rid of it since I have no use for it, no need to apologize. , I was fully aware that I would lose all files, other than SD ext drive. I just wanted to make sure that all files are in the right place and none of the unnecessary files are taking up space (e.g. files from cyanogenmod)
As for the update, I talked to a samsung representative and they said one can go to Best Buy and get it updated there through a technician, so Ill try that later since I am close to it ATM. If it back fires, Ill try your suggestions.
I really do appreciate for the help , I have been completely lost for days but it turns out I was just using the wrong firmware. Thanks for pointing it out. Good karma is coming your way . Hopefully one day, I will be here again and trying out a new custom firmware.
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
DocHoliday77 said:
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
Click to expand...
Click to collapse
Ill hope for the best and prepare for the worst.
Of course, if the worst happens, I can just use one of your links you mentioned. :good::good:
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.
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.