Related
RESOLVED SEE POST #6
Hey guys,
I am having trouble flashing a custom recovery (TWRP) to be specific on my brothers Note 2. I was able to easily do it with my phone but I didnt update OTA to the latest ATT software.
I have the latest samsung drivers installed too.
So in general.
1. My brother updated OTA
2. I use odin to try to flash TWRP via PDA
3. It says success but when I reboot into recovery it goes into the stock android recovery instead of the custom one
4. ??? perplexed
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
cortez.i said:
is your [brothers] phone rooted? (you didn't mention that in the post). if it is, the easiest way to install TWRP is to download GooManager from the Play Store and, once installed, choose Menu->Install OpenRecoveryScript.
Click to expand...
Click to collapse
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
mc704 said:
He is not rooted. He is stock from AT&T but he said he did an OTA update a week or two ago.
I actually tried the GooManager to install TWRP but it said it installed twrp but it goes into stock android recovery
I'm not sure if this helps or not but when I load into stock android recovery it keeps "manually loading CSC"
Click to expand...
Click to collapse
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
cortez.i said:
so i take it [your] phone is rooted, because you have a custom recovery installed. my understanding is that the device must be rooted before you can install a custom recovery. that's why installing TWRP via GooManager didn't work.
Click to expand...
Click to collapse
what about ODIN doesn't it root the phone when you flash a custom recovery?
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
mc704 said:
what about ODIN doesn't it root the phone when you flash a custom recovery?
Click to expand...
Click to collapse
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
mc704 said:
on my phone all I had to do was flash via twrp via odin and it did everything for me...
this isn't the case for my brother's phone so im a little confused
Click to expand...
Click to collapse
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
cortez.i said:
ODIN doesn't root your phone. it's the package/file that you flash with ODIN that roots your device. you didn't mention the method you used to root your phone.
flash what via TWRP? you need to reference the methods you used to flash your device, e.g., link to post. it's difficult to help without having more info. in my case i used the CF Root method which does root your phone by using ODIN to flash a package that installs SuperSU binary and APK (app that provides root) and a Stock recovery. This took less than 30 seconds. afterwards, i added my GMail account to my device, installed GooManager from the PlayStore and then used GooManager to install TWRP. hope this is helpful.
Click to expand...
Click to collapse
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
mc704 said:
I see. Sorry for not being specific
When I worked on my phone. I installed the latest samsung drivers on the main website, used Odin 3.07, flashed TWRP 2.3 by PDA, and it was rooted and the custom recovery worked awesome (I did it similar to this http://www.youtube.com/watch?v=NFHZ535L7is)
However this process does not work with my brothers note 2. Which is why im confused.... I assuming TWRP auto rooted for my phone but it didn't for my brother's phone?
I will definitely give your method a try and post back. Thanks for putting up with a newbie like me! :laugh:
Click to expand...
Click to collapse
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
cortez.i said:
no worries... i'd hate to see you fubar your brothers phone, lol. anyway, the method used in that video appears to be created by ChainFire for the N7100, which is the international version of the Note 2. the method i referenced - also developed by ChainFire - is specific to the AT&T and Canadian versions of the Note 2. if there's one thing I've learned in my years on xda, it's to make sure that you play with stuff that's compatible with your device. several of today's devices go by the same consumer friendly name (e.g.,Galaxy S 3, Note 2) but have different internals (e.g., chips). if you flash an incompatible ROM, you could end up with a nice paperweight. hope you and your brother enjoy your phones.
Click to expand...
Click to collapse
just a quick update.
I flashed CF-autoroot, TWRP, and a custom rom! Everything works great!
Thanks for the help!
I have had a problem, I want to install aokp for my GS3 Model Sgh-1747m but I have not seen a single tutorial on how to do so. I am new to the forums and I have some understanding of how Root and Android work(My phone is rooted). I would like someone to show me how to add the aokp rom without any worries. This would be greatly appreciated.
My phone: Samsung Galaxy S III (Android 4.3)
Model: Sgh-1747m
Carrier: Bell
Are you on stock 4.3 ROM? Do you have any warranty left on your phone?
If you still have warranty and you're running a stock 4.3 ROM, you will void your warranty by flashing a custom recovery or rooting your phone.
pfffff
audit13 said:
Are you on stock 4.3 ROM? Do you have any warranty left on your phone?
If you still have warranty and you're running a stock 4.3 ROM, you will void your warranty by flashing a custom recovery or rooting your phone.
Click to expand...
Click to collapse
you did better answer his question than to speak about warrantly,,,pffff
hichem jerbi said:
you did better answer his question than to speak about warrantly,,,pffff
Click to expand...
Click to collapse
Feel free to answer his question. Please tell him what to do
Ketros said:
I have had a problem, I want to install aokp for my GS3 Model Sgh-1747m but I have not seen a singe tutorial on how to do so. I am new to the forums and I have some understanding of how Root and Android work. I would like someone to show me how to add the aokp rom without any worries. This would be greatly appreciated.
My phone: Samsung Galaxy S III (Android 4.3)
Model: Sgh-1747m
Carrier: Bell
Click to expand...
Click to collapse
SEARCH engines are your friend. (WARNING: Some reading is required)
Sent from my awesome phone.
aybarrap1 said:
SEARCH engines are your friend. (WARNING: Some reading is required)
Sent from my awesome phone.
Click to expand...
Click to collapse
I have searched I have already rooted my phone but all I am being told is to change the build.prop from d2Can to d2att
I don't want to do that because if I do I won't have another phone to use so I want to see someone do it so I can do it as well
Ketros said:
I have searched I have already rooted my phone but all I am being told is to change the build.prop from d2Can to d2attl
Click to expand...
Click to collapse
I didn't manually change the build.prop but i installed the d2att version of TWRP 2.6.3.1 and that allowed me to install d2att ROMs (I chose Quantum ROM). When First I tried the d2can TWRP (which I got from Goo Manager) and I couldn't install the ROM. Updating to the d2att TWRP fixed that.
jmppe3 said:
I didn't manually change the build.prop but i installed the d2att version of TWRP 2.6.3.1 and that allowed me to install d2att ROMs (I chose Quantum ROM). When First I tried the d2can TWRP (which I got from Goo Manager) and I couldn't install the ROM. Updating to the d2att TWRP fixed that.
Click to expand...
Click to collapse
How do I get the d2att version of TWRP and install AOKP 4.4, will I need to unlock the bootloader or something? If so how do I do that?
Ketros said:
How do I get the d2att version of TWRP and install AOKP 4.4, will I need to unlock the bootloader or something? If so how do I do that?
Click to expand...
Click to collapse
I did the same with my d2can. I installed the d2att version of twrp and can now flash d2att roms with no issues. Download goomanager from play store, and instead of letting it detect your phone model (d2can), manually select d2att and install. That's what I did.
Sent from my SGH-I747 using xda app-developers app
This might help: http://forum.xda-developers.com/showthread.php?t=2538991.
I have never used this method but it may be worth a read.
Ketros said:
How do I get the d2att version of TWRP and install AOKP 4.4, will I need to unlock the bootloader or something? If so how do I do that?
Click to expand...
Click to collapse
Here, the TWRP website: http://techerrata.com/browse/twrp2/d2att
audit13 said:
This might help: http://forum.xda-developers.com xda-developers.com/showthread.php?t=2538991.
I have never od but it may be worth a read.
Click to expand...
Click to collapse
Thanks for the link but my phone is rooted already I need step by step instructions on how to get twrp d2att and install apk 4.4 on my phone
bdithug said:
I did the same with d2can. I installed the d2att version of twrp and can now flash d2att roms with no issues. Download goomanager from play store, and instead of letting it detect your phone model (d2can), manually select d2att and install. That's what I did.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Can you explain how to Install twrp(d2att) I've already rooted my phone now how do I get goomanager to install the d2att twrp
Ketros said:
Can you explain how to Install twrp(d2att) I've already rooted my phone now how do I get goomanager to install the d2att twrp
Click to expand...
Click to collapse
I just took a look at goomanager and the options look different than when I flashed twrp (d2att). It's either because I already have the recovery installed or maybe the app has updated. It's been so long since I did it myself. Try googling it or searching in twrp's thread here on xda. I'm sure you will be able to find step by step instructions.
Sent from my SGH-I747 using xda app-developers app
bdithug said:
I just took a look at goomanager and the options look different than when I flashed twrp (d2att). It's either because I already have the recovery installed or maybe the app has updated. It's been so long since I did it myself. Try googling it or searching in twrp's thread here on xda. I'm sure you will be able to find step by step instructions.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Use the link to TWRP I posted earlier and then flash with ODIN. I'm sure there's another way to do it via the recovery but I haven't looked into it as I don't need to. Must be something on the forum about it.
jmppe3 said:
Use the link to TWRP I posted earlier and then flash with ODIN. I'm sure there's another way to do it via the recovery but I haven't looked into it as I don't need to. Must be something on the forum about it.
Click to expand...
Click to collapse
I have downloaded the twrp for d2att now all I do is flash it on my phone? My phone is already rooted with the d2can twrp will it still work? Will I lose any of my files?
Ketros said:
I have downloaded the twrp for d2att now all I do is flash it on my phone? My phone is already rooted with the d2can twrp will it still work? Will I lose any of my files?
Click to expand...
Click to collapse
I don't know, try searching on the forums. I told you how I did it and that's all I can help you with, sorry. You should have a backup before trying any of this stuff, anyway.
jmppe3 said:
I don't know, try searching on the forums. I told you how I did it and that's all I can help you with, sorry. You should have a backup before trying any of this stuff, anyway.
Click to expand...
Click to collapse
When I rooted my phone I used this method http://forum.xda-developers.com/showthread.php?t=2538991 I installed the twrp for d2att, but this was a while ago so is there any way to check if it is the d2att version and not the d2can version
Ketros said:
When I rooted my phone I used this method http://forum.xda-developers.com/showthread.php?t=2538991 I installed the twrp for d2att, but this was a while ago so is there any way to check if it is the d2att version and not the d2can version
Click to expand...
Click to collapse
Using which method, #1 or #2? I did #1 and installed TWRP via Goo Manager (IIRC). But that gave me the d2can version. I don't think you need to bother checking, though, just use ODIN to flash the new recovery (TWRP 2.6.3.1) from the link I gave you earlier. After backing up etc etc.
I had the exact same problem as OP.
What the recovery is trying to do is install a D2ATT rom onto a D2ATT phone which the Canadian carriers change to D2CAN in their build.prop file.
1. Find your build.prop file in system/data and make a backup of it however you which. I made a copy and just called it something else. Go to your build.prop file and change any instance of "d2can" to d2att. When I did this there was two. One on build.product=d2can and one on build.device. I just checked and CM changed some of the settings around and now there is just one.
Save the file and it'll ask you to reboot.
Now anything you download will think it's an actual at&t device (which is good).
The standard method for getting TWRP on your device is through goomanager but samsungs knox gave me issues trying to install a custom recovery.
2. Get the app "Recovery Tools" Or, specifically [ROOT]Recovery Tools - Flasher by DSLNEXUS.
and download the recovery file here http://www.teamw.in/project/twrp2/104
Download the .img file via dd into the root folder of your phone.
Open up recovery tools and select flash recovery and select other from storage. You CAN select TWRP and have the app do it for you but sometimes it uses older versions. I chose "other from storage" then you select the twrp file you downloaded.
3. At this point you should be able to boot into twrp and flash from there. Don't forget your gapps.
I spent months on and off wracking my brain trying to figure out how to do this on my phone without bricking it. I did it this way and it worked without a hitch.
Here is my dilemma, I recently unlocked and rooted my HTC One M7 for Verizon. I may not have performed a backup but I am oblivious to what the problem may be. I am a newb to rooting and unlocking so please spare me any negative feedback. S-off was successful using firewater. Phone is unlocked in bootloader. Phone was rooted through TWRP v2.7.0.0 and SU. After root was successful I did a factory reset then flashed CM11 with TWRP. CM11 installation was successful except for one problem. My mobile network is not available and a message appears on the screen(You need to refer to the SIM card instruction that came with your phone.) The CM11 file that I installed is: cm-11-20140407-NIGHTLY-m7.zip and after reading that the "Nightly" roms are not the most stable, I then flashed this one: cm-11-20140405-SNAPSHOT-M5-m7.zip. Here is what the Installation looked like in Recovery:
Updating partition details...
Full SELinux support is present.
Formatting Cache using make_ext4fs function.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing ' /sdcard/Download/cm-11-20140405-SN
APSHOT-M5-m7.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details..
Successful.
Following the successful flash, I then installed gapps-kk-20131208. Please be detailed in how I can fix this issue. Thanks so much in advance.
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
KK firmware
cmlusco said:
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
Click to expand...
Click to collapse
I don't understand. What is KK firmware? This may seem like a stupid question but I really don't know.
kk
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Zacb01 said:
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Click to expand...
Click to collapse
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Mobile service
Crawshayi said:
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Click to expand...
Click to collapse
I installed this successfully but I still can't make or receive calls. I am wondering if the version of cyanogenmod that I flashed might not be compatible but I did not get a status 7 error when installing. I am also wondering why I got the sim card message when first installing cm11. The version that I installed is stated above on my first post but cyanogenmod has m7 and m7vzw, I can install m7, which I believe is for GSM but I have a Verizon HTC One. When I try to flash the m7vzw version I get the status 7 error code. I tried to do a fix for it but I may have done this incorrectly since I got a status 6 error code. Plz help. I need this phone for work.
You want the m7vzw, the regular m7 is gsm. Status 7 refers to an error in the update script or an incompatible update binary. Does it give a specific error with that status 7? You should also update your twrp to version 2.7.0.4b-santod. http://www.androidfilehost.com/?fid=23329332407584851
Last i heard cm11 is only in preview and data and calls do not work. That may have changed though.
Error
I updated the twrp to v2.7.0.4b-santod, did a factory reset and tried to flash cm11 for m7vzw and was given this mssg...E:Error executing updater binary in zip ' /sdcard/Download/cm-11-20140124-NIGHTLY-M7VZW.ZIP' Setting performance mode OFF. Error flashing zip....etc.....
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Compatible
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Recommendation
cmlusco said:
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Click to expand...
Click to collapse
I decided to go with cm 10.2.1. Thanks for everything!
Zacb01 said:
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Click to expand...
Click to collapse
Hmm thats strange, mabey cm11 just dosent like twrp or something. Glad you got something figured out.
Upgrading to lollipop
Someone should please help on how to upgrade to lollipop 5.0 on HTC m7 complaining of md5 file not found
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.
DocHoliday77 said:
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.
Click to expand...
Click to collapse
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.
getochkn said:
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.
Click to expand...
Click to collapse
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me
DocHoliday77 said:
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.
Click to expand...
Click to collapse
Ah. Maybe I was looking at the QualcomSecureboot or something
Either way, all is good. Not sure why TWRP gave problems or CWM did via Odin. I'm using likewise rom, which is based off your sprint so shouldn't have any more problems now anyways. Not a stranger to flashing Samsung phones, just my first newer samsung flash with this whole knox/selinus thing and all that. My old sammy S 4G was flashed hundreds of times while I worked on ROMs'. lol.
Rickyfk said:
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me
Click to expand...
Click to collapse
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.
yes i forgot that in my post i always back ups of everything before i do anything.
i have also fixed bricked devices befor also but ya you have to be carful tho.
DocHoliday77 said:
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.
Click to expand...
Click to collapse
i have the same problem
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:
welcome2you said:
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:
Click to expand...
Click to collapse
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.
DocHoliday77 said:
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.
Click to expand...
Click to collapse
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.
welcome2you said:
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.
Click to expand...
Click to collapse
How are you trying to install TWRP? There are several ways to do so. Odin, recovery, Goo.Im app..... You can get the twrp files from my sig if you want to try those. No guarantee you will be able to unlock when flashing the 4.1.1 modem, let us know if it works for you.
I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.
getochkn said:
I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.
Click to expand...
Click to collapse
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)
DocHoliday77 said:
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)
Click to expand...
Click to collapse
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working
getochkn said:
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working
Click to expand...
Click to collapse
Ill have to double check that later. Been a while since I've flashed recovery. I know I am using the one in my repo though, so it should work fine whether its d2tmo or d2lte
I recently decided to get back in the trying customized software after taking almost a year and half break from regularly doing it back on my Nexus S. Everything was going smoothly at first and I choose the latest version of liquidsmooth as first at bat and it worked like a charm until the cellular radio would not turn on. I tried everything I could find and even tried flashing the latest radio while on the rom, but no dice. I had to flash the stock image and it worked again, but when I tried flashing again same problem. I even tried slim rom after my second attempt with liquid and the radio just would not work. Wifi worked like a charm but no cellular at all. Can anyone help me with this. I really liked what I got to play around with on liquidsmooth, but I need my phone to actually function as phone. For now I am back to stock until I can find a solution.
Which stock image did you flash? I recommend
http://forum.xda-developers.com/showthread.php?p=53353625
Lemme guess...you were using twrp to flash 4.4 ROMs
jrebo said:
Which stock image did you flash? I recommend
http://forum.xda-developers.com/showthread.php?p=53353625
Click to expand...
Click to collapse
I did flash that one. It's what I'm running now until I can figure out how to get my custom flashes working.
Skripka said:
Lemme guess...you were using twrp to flash 4.4 ROMs
Click to expand...
Click to collapse
Yes. I read that as long as I used version 2.6.3.3 or higher, it would be fine.
Protoroll said:
Yes. I read that as long as I used version 2.6.3.3 or higher, it would be fine.
Click to expand...
Click to collapse
"would be fine" in the sense that it has been common knowledge since 4.4 CyanogenMod builds started in November 2013...that TWRP does not work on L900 for AOSP-base 4.4, and it never has. And by the looks of things never will, as there's been no progress on L900 TWRP working in months,
Use PhilZ to flash and odds are your radios will magically work.
Skripka said:
"would be fine" in the sense that it has been common knowledge since 4.4 CyanogenMod builds started in November 2013...that TWRP does not work on L900 for AOSP-base 4.4, and it never has. And by the looks of things never will, as there's been no progress on L900 TWRP working in months,
Use PhilZ to flash and odds are your radios will magically work.
Click to expand...
Click to collapse
Alright, thank you for the help. I will try PhilZ and see how it goes.