Related
Sorry, I'm new to this so sorry if this seems dumb.
So i bought the phone from rogers and immediately updated to froyo 2.2 official release by rogers/samsung.
I read about all the hype online about rooting and custom roms so i decided to give it a shot.
I used the superoneclick method to root my phone and it was successful.
I then used "rom manager - clockworkmod" and created a restore file before i did any flashing to my phone.
after creating a backup, i went on and flashed to the cognition 3.04.
Now my question is. Am i ever able to get my phone back to its original rom, kernel, and modem? the reason i want to know is because i might need to get my phone replaced due to some technical issues with the phone.
Also, does the backup of my phone after rooting play a part in any of this? if so, how?
Im sorry if there is already a post like this one. Its just that i couldn't find the answer through all the hundreds of pages of threads and replies, so I thought it would be easier to post a here with my specific question. Thanks.
regards,
danny
dsu said:
Sorry, I'm new to this so sorry if this seems dumb.
So i bought the phone from rogers and immediately updated to froyo 2.2 official release by rogers/samsung.
I read about all the hype online about rooting and custom roms so i decided to give it a shot.
I used the superoneclick method to root my phone and it was successful.
I then used "rom manager - clockworkmod" and created a restore file before i did any flashing to my phone.
after creating a backup, i went on and flashed to the cognition 3.04.
Now my question is. Am i ever able to get my phone back to its original rom, kernel, and modem? the reason i want to know is because i might need to get my phone replaced due to some technical issues with the phone.
Also, does the backup of my phone after rooting play a part in any of this? if so, how?
Im sorry if there is already a post like this one. Its just that i couldn't find the answer through all the hundreds of pages of threads and replies, so I thought it would be easier to post a here with my specific question. Thanks.
regards,
danny
Click to expand...
Click to collapse
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Christo_69 said:
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Click to expand...
Click to collapse
Dont use that link because it is for att firmaware. I havent seen any prepackaged odin one click for rogers.
This is my captivate. There are many like it buy this one is mine.
Christo_69 said:
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Click to expand...
Click to collapse
Thanks for that. Do you think Odin is the only way to do it or do you think i can use clockworkmod
flashman2002 said:
Dont use that link because it is for att firmaware. I havent seen any prepackaged odin one click for rogers.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
Do I not use that link in general, or just not to use the firmware given at the bottom? the steps are correct though, no?
also from my searching.
i can put my phone back to my backup point (just after rooting) through clockworkmod. Woud this change my rom back to stock from? how about kernel and modem and all that? would that all get reversed back to my backup point? meaning it will basically be a stock phone. But I think also read somewhere that my kernel and modem does not get changed back to rogers original one. is there a way to do it?
I then found this link: http://forum.xda-developers.com/showthread.php?t=846501
that says i need the original rogers rom for the captivate by the links there no longer work for download. Also on that thread, it was mentioned that the AT&T logo will still come up on startup, which would not be a good idea if i had to send my phone in for warrenty.
I then looked at : http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Here it tells me to flash to a i9000 before i reflash to a rogers firmware in order to remove the at&t logo. it also provides me with a link for the " Official Rogers Stock ROM ", but according to somebody on the first link i posted here, it isnt the "official rom"
Any ideas?
This is where I got the stock 2.2 file from http://forum.xda-developers.com/showthread.php?t=905042.
Edit: I have flashed a bunch of times and have never got stuck with the AT&T startup after flashing back to stock with the odin file.
Akalon said:
This is where I got the stock 2.2 file from http://forum.xda-developers.com/showthread.php?t=905042.
Edit: I have flashed a bunch of times and have never got stuck with the AT&T startup after flashing back to stock with the odin file.
Click to expand...
Click to collapse
Thanks. Do you know if my kernel is going to go back to stock too or is it going to remain the same as the custom rom one?
dsu said:
Thanks. Do you know if my kernel is going to go back to stock too or is it going to remain the same as the custom rom one?
Click to expand...
Click to collapse
If you use the odin file the kernal and modem will revert back to stock.
Akalon said:
If you use the odin file the kernal and modem will revert back to stock.
Click to expand...
Click to collapse
Thanks. So im assuming now that the only time my kernel and modem wont go back to stock is when i flash with CWM. correct?
I haven't tried using the CWM file in that link so I'm not sure if it contains the kernel and modem. As far as custom roms go most if not all come packaged with the kernel and modem of choice.
So.. When I do a "master clear" from http://forum.xda-developers.com/showthread.php?t=731989...
Would everything be wiped? I read somewhere that when you do a "wipe" from your settings it only clears user settings or something. What would a "wipe"
from the recovery menu do?
I flashed to a different rom today thinking it will help my battery issue. When i am flashing from one rom to the next, i do a restore back to my backup before i flash to a new rom. Is this the correct method? or am i supposed to wipe beforehand? The reason i ask is because this is my 2nd rom and my battery issue still seems to be there. I tried other methods of fixing hte battery but nothign seems to work. When i looked into root explorer, i see that there are a lot more files now everywhere, than when i first started. would some of them be from my previous rom? if so how do i remove them?
Hey,
I'm trying to install the [ROM] Team Tiamat Xoom Rom 2.2.2 - Moray [9/10/11].
I've got CWM installed (version recovery-Tiamat-R4c-100611-1150-cwm.img but also tried latest version from ROM Manager).
Each time i try to install the .zip it get's to opening package and then just exits to the CWM menu?
It's probably a common thing, but couldn't find anything from a search? Anyone got any ideas?
This has been covered many times so take the time to do a search.
Muffycheeks said:
This has been covered many times so take the time to do a search.
Click to expand...
Click to collapse
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
kar200 said:
I had to thank you Muffycheeks for your excellent answer. I am not sure why you did not at least give an indication about where to find the answer or what the issue is? Lucky this was posted in Q&A and not in the dev thread!
I am new to Xoom (only got it since yesterday) and have managed to get the bootloader unlocked and custom recovery installed. For some reason when I reboot the device the recovery is flash back to 3e (I suppose this has been also debated millions of times but I cannot find it yet...)
I had been able to flash one of the custom roms but it gets stuck in bootscreen. I wiped everything I could think of and followed a couple of advices and still not working.
I am downloading the other rom (as far as I can tell there are only 2 customs with one of them based on the other one) and will see if that works.
Sorry Addicteddddd for highjacking your thread but I have been searching for a while until I found your thread and I thought my issues were over to find the standard helpful XDA answer. Some people might have had their device for years but some other are quite new to this.
K.
EDIT: It seems that one of the recoveries do not advise if a ZIP file is bad and therfore comes back with no message. I suppose this is why this is happening.
I downloaded 3 ZIP files and they are all corrput. Not sure what is happening here but anyway.
Click to expand...
Click to collapse
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
okantomi said:
I don't know if you used this guide but there is a bit of discussion of some issues regarding cwm recovery versions and some pitfalls while trying to flash.Check it out if you haven't
http://forum.xda-developers.com/showthread.php?t=1249798
Also, how are you downloading the file? Are you getting the right version? If you are using the R4c v3.2.0.0 it should be called solarnz, not tiamat. The guide has the correct link.
Click to expand...
Click to collapse
I just ralised tnat my sd card was screwed (very old 1gb i found lying around). The files on the pc were fine.
I used a different card and now typing from a custom rom! All good.
K.
Sent from my Xoom using xda premium
Okay,
I'm hoping that I'm posting this in the right place, since I'm new here, but here it goes.
I was wondering how to tell if I am able to use a rom. I know the obvious that it has to be for my phone, but what other important things (such as firmware) should I look at to make sure a rom is right for my phone. If there's a thread on this already, or if this is the wrong section please just point me in the right direction.
If the ROM is made for your phone, then it will work completely. If it was made for a phone in the same family of devices as yours, it may work fully or partially. For example, I have the LG P505. I can use any ROM made for the P505. I can use any ROM made for the P500 (which opens the doors to dozens of choices, from only a handful), but the screen driver is wrong, so the colors are messed up, and once the screen goes black, it doesn't come back (lol). To solve it, I have to flash a kernel made specifically for my phone (P505) after flashing the ROM.
If you have a flashable kernel .zip for your phone, you can use any ROM made for the whole family of devices of which your phone is a part.
Vinny Bacon said:
Okay,
I'm hoping that I'm posting this in the right place, since I'm new here, but here it goes.
I was wondering how to tell if I am able to use a rom. I know the obvious that it has to be for my phone, but what other important things (such as firmware) should I look at to make sure a rom is right for my phone. If there's a thread on this already, or if this is the wrong section please just point me in the right direction.
Click to expand...
Click to collapse
Just read the OP of the ROM thread (all of it; more than once). That's where you should find information on compatibility. If its in your device's section, its quite likely it will be compatible. But, you still need to read in case it requires a specific recovery, etc. to be flashed and work correctly.
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw
Theonew said:
Just read the OP of the ROM thread (all of it; more than once). That's where you should find information on compatibility. If its in your device's section, its quite likely it will be compatible. But, you still need to read in case it requires a specific recovery, etc. to be flashed and work correctly.
Click to expand...
Click to collapse
I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Vinny Bacon said:
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw
Click to expand...
Click to collapse
Vinny Bacon said:
I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Click to expand...
Click to collapse
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw. I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Vinny Bacon said:
Thanks for the replies! I've been having problems with boot loops and I was wondering if it was a compatibility issue. where would I get my hands on my phones kernel? I have an HTC sensation currently running sence-o-manic btw. I'm having trouble flashing ViperS. the op doesn't specify any procedures, but I get caught in a boot loop after going through the setup. not sure if I'm missing something or if i may have neglected to run a process that the op is assuming Ive completed. Needless to say, I'm completely lost lol.
Click to expand...
Click to collapse
If you go to sensation forum instead of posting in general there will be A LOT more people there to help you.
Once you get there, read stickied thread by malybru called something like "great starting point for new sensation users" in Sensation general, and if you still have questions after that, go to Sensation Q&A , find another stickied thread called "Help Thread" and ask there.
I'm sorry for posting the same question in two different places (at the OnePlus forum and here).
It's not that I am impatient, but it's just so hard to get any straight answers over there.
Maybe someone here can help with this...
Well my device arrived yesterday and so far it is working very well.
I did the first OTA before doing anything else to the device and it went without any problem.
The only thing that really bothers me is that a couple of people wrote that they bricked their device after the OTA, when the device was unlocked and had a custom recovery installed (and was rooted, eventhough I don't think that could cause any problems).
So the question is, and I think it is a really important one...
Do CM11s OTA updates work with a custom recovery installed (twrp in my case)?
Should people flash the original, stock recovery via fastboot if they want to use the CM11s OTA update service?
And if that is the case...It is recommended, for people who do not want the stock recovery, to just go ahead and flash the the CM11 nightly (regular CM), to not receive any OTA updates?
I would really appreciate an answer to these questions.
Thanks in advance.
Ps. The problem was already mentioned at the cyanogen forum (and a couple of other places), but didn't get an answer.
http://forum.cyanogenmod.org/topic/97186-hard-bricked-oneplus-one/
Click to expand...
Click to collapse
[armitage] said:
I'm sorry for posting the same question in two different places (at the OnePlus forum and here).
It's not that I am impatient, but it's just so hard to get any straight answers over there.
Maybe someone here can help with this...
Click to expand...
Click to collapse
As far as I know, you won't be able to get OTA's with a custom recovery.
kudos
I did ota with custom recovery.Just uncheck update cm recovery in developer options
Sent from my One using XDA Premium 4 mobile app
I am reading conflicting things trying to figure this out. Can someone who is absolutely sure please let me know? I can't afford to waste another entire day making educated guesses.
It doesn't seem like the TWRP version numbers correspond to the Android builds, but if they do please correct me.
Thank you
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
RokCruz said:
You don't need to figure it out, there's only 2 threads about working TWRP, One for Android 9 & 10 and One for 11 and in the OP of each thread are specified what are working and what doesn't and how to install/boot it properly.
Click to expand...
Click to collapse
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
didymus said:
Oh ****, thank you! I totally missed these searching. Believe it or not I really did look, quite a bit. Anyway, thanks again.
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly. I just kinda assumed since it doesnt work with 11 which I had to figure out the hard way. That 11 thread though is super helpful.
Click to expand...
Click to collapse
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
RokCruz said:
It's specified in the name of the twrp
And another thing, this type of question should go in the section Questions and answers
Click to expand...
Click to collapse
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I know I installed it correctly too because in the past week I've installed TWRP so many times I could practically do it blindfolded now.
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things. I just hope yall don't ban me before then, lol.
didymus said:
Yeah, I wasn't sure about where to post it since it was directly about recovery. Sorry about that. I won't make the same mistake again.
Also, I'm just now figuring out what is what, but I don't see how any of those files designate they are for 11 in that screenshot you posted. I've seen all those files actually. I've also spent time on the TWRP website and read mostly everything. The only thing I could find was a post that said it (11 support) was coming, but I tried the newest one there and it bricked the phone. I also read in an article that the lad(s) who wrote those is working officially with TWRP, so I thought the TWRP website would be "the horse's mouth".
I don't mean to take a bunch of your time, but where in that screenshot does it designate "11"? I know `Pie` is an older Android, but I thought `Q` was too. Maybe I'm just wrong and it's 11. I was just getting confused because the OOS version numbers are right there in the boot image file name for Magisk, so when I saw those numbers on the TWRP files I just thought they were all for much older Android years ago.
Anyway, thank you, sorry for the n00b post, but I definitely am reading and searching and not just posting immediately when I encounter a problem. I've actually learned a ****load in the past week struggling with all of this though so I can't really complain. Eventually I will get up to speed and be able to write some things.
Click to expand...
Click to collapse
That screenshot was for this
didymus said:
Edit: That 9&10 thread I've read, but I didn't know it was for "9 & 10" exactly.
Click to expand...
Click to collapse
If you're in android 11 forget the thread about android 9 & 10
RokCruz said:
That screenshot was for this
If you're in android 11 forget the thread about android 9 & 10
Click to expand...
Click to collapse
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
didymus said:
Yeah, so, this one for 11 I've tried before. Once I install it how the thread says then I can only boot into TWRP. I'm just unsure what to do now because all the threads just say "flash rom, flash magisk". I didn't even know you could flash Magisk via TWRP.
I have the OTA of the new update downloaded. I have the boot.img extracted. I just have no idea how to fix this. I've done this before and I thought I bricked it and that's why I thought this wasn't for 11. :/
Edit: I'm guessing that I `adb push` the OTA to the device and see if I can flash that in TWRP?? Then once I am in the OS use Magisk to patch the boot? I'm unsure because places use the term "Magisk Manager" like its different from Magisk and I've never seen an app called exactly "Magisk Manager". I'm just assuming that was like... the old name of the app, but I don't know that could just be me filling in the blanks incorrectly.
Edit:Edit: I'm attempting to sideload the OTA. I think I've read of people doing this. *crosses fingers*
Click to expand...
Click to collapse
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
RokCruz said:
Wait, what? Im not sure what are you trying to do.
I guess you're new in all of this right?
My work here was the twrp thing.
Click to expand...
Click to collapse
Im trying to install TWRP. I do it exactly how the thread says and then system never boots into OOS again and I just have fastboot and TWRP. Basically bricked. Then when I try to reboot to recovery which should be TWRP (right?) it just boots me into the regular "recovery".
Thats why I think this is broken and I resigned to just not updating into 11.
I've never had this much trouble doing this. Ever. Not even close.
Edit: Yeah, so I patched the 11 boot.img and now I have root again, but no TWRP. I don't know how to keep both in 11. When I was 9.5.3 I used the Magisk A/B retention script and kept it, but once it became 11 it bricked the phone and the TWRP logo just flashed. I had to reflash the OTA to boot again. Thats another reason why I thought it didn't work for OOS11.
Starting to think I have a learning disability, lmao. Wish I was joking.
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
caca12357 said:
I just try.
When I flashed official TWRP and used it to flash any ROM(including OOS), it will lose or replace it by ROM's recovery...
Click to expand...
Click to collapse
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
@caca12357 I'm going to try to do a local OTA upgrade then before I reboot run the A/B retention script and then Magisks option for OTA and see if that does anything. If TWRP works for 11 something like that should make it work, but who knows. Have you messed with A/B Retention at all?
If you want to PM me we can figure it out together.
Thread moved to proper section
didymus said:
Yeah, exactly what is happening with me. The closest I ever had it working was with using the A/B Retention script within Magisk Modules, but the second I hit OOS11 it **** the bed. I think "official TWRP" is different than what he linked up there for 11. I mean, I know they are, as it says "unofficial", but that's kind of why I'm confused because the images on TWRP.me use the similar numbering nomenclature and imply there are newer version for my device, so why would a newer version not work, but an older version work?
And if this particular TWRP does actually support 11 then why hasn't TWRP Official incorporated it into their releases? It's just little things like that which led me to believe it's not working. Also, I read a bunch of articles saying it wasn't working, but they could have been old. However, one of them was on Reddit and a few months old, but maybe they were wrong.
I feel like I went on a wild goose chase today, but I really hope didn't.
@RokCruz Just out of curiousity, do you actually have a OnePlus 7 Pro right now with OOS11 and working TWRP/root? I'm not saying you're just making this up or anything, but maybe something has changed since the last time you tried? If you currently have an OOS 11.0.11 device with TWRP/root atleast I'll know it's possible.
Click to expand...
Click to collapse
Yes, and do you know how I flash TWRP to my OP7P? First, I flashed Pixel Experience recovery by fastboot, and I used Pixel Experience recovery to sideload the official TWRP. (In other words, I never can temporarily or permanently flash TWRP directly). If I did not want to convert my /data to the f2fs file system I will not do this meaningless work...