Q&A for [Recovery][D2SPR] TWRP for Boost/Virgin Mobile Phones
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery][D2SPR] TWRP for Boost/Virgin Mobile Phones. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
i tried flashing twrp-2.8.6.0-d2spr-virgin-boost.img.tar.md5 and my odin just crashes.
hellspawn3200 said:
i tried flashing twrp-2.8.6.0-d2spr-virgin-boost.img.tar.md5 and my odin just crashes.
Click to expand...
Click to collapse
The .md5 is a checksum file. Use the .tar file.
Sent from my SPH-L710 using XDA Free mobile app
hellspawn3200 said:
i tried flashing twrp-2.8.6.0-d2spr-virgin-boost.img.tar.md5 and my odin just crashes.
Click to expand...
Click to collapse
Does it just hang or does the window completely close on its own?
Luniz2k1 said:
The .md5 is a checksum file. Use the .tar file.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Actually in this case it is the actual recovery with the checksum added in. Just like samsungs stock files.
Lrs121 said:
Does it just hang or does the window completely close on its own?
Actually in this case it is the actual recovery with the checksum added in. Just like samsungs stock files.
Click to expand...
Click to collapse
Good to know. I am used to md5 files being checksum files only.
Sent from my SPH-L710 using XDA Free mobile app
Luniz2k1 said:
Good to know. I am used to md5 files being checksum files only.
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
I completely understand, took some getting used to when I had a samsung phone.
twrp not working
i need help I installed twrp via odin on my virgin mobile galaxy s3 nd when I go onto recovery to do a back up it shows my internal storage 0 nd I cant install roms cuz it wont read my sd card also when I turn it off it says I have no OS installe dbut I do. but works fine with cwm nd philz touch any idea what it can be???
nowayjose420 said:
i need help I installed twrp via odin on my virgin mobile galaxy s3 nd when I go onto recovery to do a back up it shows my internal storage 0 nd I cant install roms cuz it wont read my sd card also when I turn it off it says I have no OS installe dbut I do. but works fine with cwm nd philz touch any idea what it can be???
Click to expand...
Click to collapse
Which version of twrp did you install the one from this thread or from the offical twrp website. if you installed the on from this thread make sure youre running the latest version.
Lrs121 said:
Which version of twrp did you install the one from this thread or from the offical twrp website. if you installed the on from this thread make sure youre running the latest version.
Click to expand...
Click to collapse
It was the latest version nd i even tried an older version juss to see if that was what was wrong but still did the same thing nd yes i used the twrp from this thread nd also from the website every twrp ive tried kept doing the same thing
nowayjose420 said:
It was the latest version nd i even tried an older version juss to see if that was what was wrong but still did the same thing nd yes i used the twrp from this thread nd also from the website every twrp ive tried kept doing the same thing
Click to expand...
Click to collapse
Unfortunately beyond saying use the latest version, there's not much I can do without logs.
Lrs121 said:
Unfortunately beyond saying use the latest version, there's not much I can do without logs.
Click to expand...
Click to collapse
how would I be able to show yu the logs?? I get a lot of red words saying cant mount
nowayjose420 said:
how would I be able to show yu the logs?? I get a lot of red words saying cant mount
Click to expand...
Click to collapse
How to obtain the logs is covered in the op right under the FAQ's. upload it here as an attachment and ill look through it. However, usually when there are mount errors thats because the recovery isnt meant to run on your device.
Is it possible to enable device encryption while using this recovery?
Sent from my Samsung Galaxy S3 running AICP 9 using Tapatalk
I've been using the multi boot version of twrp basically since I've had the phone and out of nowhere when I go into recovery its a different version of twrp and isn't mounting anything all the sudden. And says no os but I do
How do I add a file to your post from your phone.trying to add the log
SuppliedRelic said:
Is it possible to enable device encryption while using this recovery?
Sent from my Samsung Galaxy S3 running AICP 9 using Tapatalk
Click to expand...
Click to collapse
It should work though I don't know if/what issues may come up because of the way I had to change some files around to just get the recovery to complile.
lilcourv said:
I've been using the multi boot version of twrp basically since I've had the phone and out of nowhere when I go into recovery its a different version of twrp and isn't mounting anything all the sudden. And says no os but I do
How do I add a file to your post from your phone.trying to add the log
Click to expand...
Click to collapse
I'm not really certain how to do it from a phone. I would try and use the web browser instead of any of the apps that can connect to xda. And if that has issues I'd upload it to dropbox or google drive and post a public share link.
Right now I have Gummified TWRP 2.8.0.0 on my Virgin Mobile d2spr. If I switch to this recovery, will I be able to restore nandroids made with the Gummified TWRP?
Powered_By_Linux said:
Right now I have Gummified TWRP 2.8.0.0 on my Virgin Mobile d2spr. If I switch to this recovery, will I be able to restore nandroids made with the Gummified TWRP?
Click to expand...
Click to collapse
you should, im not certain if there were enough major changes between 2.8.0.0 and 2.8.6.0 or if there was changes made to the Gummified twrp that would make the backups incompatable. i suggest reading the major changelogs on the twrp.me website and look for anything related to backup changes. otherwise most if not all twrp backups will work with each other.
So I am not sure if this is a TWRP issue or a phone issue, I have a boots S3. SPH-L710 and Installed TWRP 2.8.6.0 and i try to wipe something and I get the following errors:
wipe completed: failed and other errors, see screenshot
I get error unable to mount /cache and so on, I have included a screenshot of the error.
I flashed via Odin, I tried 3.04, 3.06, 3.07 and 3.09 of oden and it says it has been flashed sucessfully no errors on the flashing side of odin, just when I try to wipe or install a rom. I have TWRP on Note 4 and it works fine, I tried all the steps i did previously on my note 4 and it worked on that device, just not the s3. Perhaps this TWRP isn't compatible with this device? Or something I missing,
I did try flashing this twrp listed on this forum and odin crashes as well. included screenshot
nofroyo said:
So I am not sure if this is a TWRP issue or a phone issue, I have a boots S3. SPH-L710 and Installed TWRP 2.8.6.0 and i try to wipe something and I get the following errors:
wipe completed: failed and other errors, see screenshot
I get error unable to mount /cache and so on, I have included a screenshot of the error.
I flashed via Odin, I tried 3.04, 3.06, 3.07 and 3.09 of oden and it says it has been flashed sucessfully no errors on the flashing side of odin, just when I try to wipe or install a rom. I have TWRP on Note 4 and it works fine, I tried all the steps i did previously on my note 4 and it worked on that device, just not the s3. Perhaps this TWRP isn't compatible with this device? Or something I missing,
I did try flashing this twrp listed on this forum and odin crashes as well. included screenshot
Click to expand...
Click to collapse
You can download Flashify from the Google Play Store and then use that application to flash the latest version of the fixed recovery posted in the original thread.
Sent from my Samsung Galaxy Victory running stock (but rooted) 4.1.2 Jelly Bean using Tapatalk
SuppliedRelic said:
You can download Flashify from the Google Play Store and then use that application to flash the latest version of the fixed recovery posted in the original thread.
Sent from my Samsung Galaxy Victory running stock (but rooted) 4.1.2 Jelly Bean using Tapatalk
Click to expand...
Click to collapse
yea hopefully i can get it running so i can do that
Related
Just got my gs3 today and decided to root using this method http://forum.xda-developers.com/showthread.php?t=1746682
Not really so tech-savy with this yet and after the whole root process of odin3 i reboot into recovery, wipe/cache/dalvik then flash the new miui 2.10.19 http://miuiandroid.com/community/threads/2-10-19.18540/ one i hit flash it says installation failed blah blah blah (status 7) getprop. Yeah all that junk, so i searched up on the forums and the only solution i find is to update cwm and i have, to 6.0.1.4 and still same thing!! installation error, aborted. Can someone please help me out :crying: I'm sorry if im a noob, just trying to flash a rom here
Update CWM via ROM Manager.
Download again
Sent from my SGH-T999 using xda app-developers app
use twrp
theexel said:
Update CWM via ROM Manager.
Click to expand...
Click to collapse
i did, still no luck
mt3g said:
use twrp
Click to expand...
Click to collapse
and this was my last thing i tried before bed last night and still didnt work! should i just unroot then re-root all over again?
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Aerowinder said:
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Click to expand...
Click to collapse
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
How could cwm not be working if its updated to latest version? I dont think im downloading the wrong rom and its not a bad link. Even tried dragging it onto my internal sd wirh debugging off. Btw I have the 32 gb s3 with does not have an external sd.
The way I fix that was I rerootes my phone into latest clockwork recovery. I didn't remove the root I just rerootee it. Look for cwr 6 I think.
Sent from my SGH-T999 using xda app-developers app
From watching the video given for the toolkit, when in odin and have to open up pda then go to the toolkit files and then root all my files are in winRAR type and his are in tar archive type. Does that matter at all? And also when clicking on the pda then root you chose the file /boot-insecure-tmo-t99uvalem-cwm but when in odin and clicking this file on the little winrar icon to the left of the file name its the only one with a little like key lock, doesnt know if thats an issue or anything just something i noticed because when accessing the toolkit files on my c drive and going to the root folder, the key icon is no longer there.. Any ideas??
Reading about people flashing a kernal in recovery then flashing the rom and working but when you flash a rom isnt it flashing the kernal it comes with also? Or is this the problem
Well, I re ran the toolkit, re did the root and odin process same as i did the first time, downloaded rom straight from my phone flashed again still getting status 7 error/ installation aborted -______- ugh...
Brad4891 said:
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
Click to expand...
Click to collapse
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
I can't believe I didn't see this before....what is the exact file name of the rom you are flashing?
I looked and did not see our phone listed in the op. Looks like the international one is there (codename m0?). But no d2tmo, d2att, etc.
Unless I just missed it there, you do not want to even try flashing that anymore! If I'm right you just got very lucky dude!
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Brad4891 said:
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Click to expand...
Click to collapse
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
DocHoliday77 said:
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I was at first but then changed my mind, both werent working before hand though when i was getting the errors.
And im using hellfire and the rom is super smooth like butter. I have one problem though, its notifications. Whenever receiving texts i dont get a vibration or light pulse. Sometimes randomly i get a vibration. Anyone know how to fix?
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Hi there fellow note users. I am currently using CWM and running the ported ROM with MultiView on my AT&T i317 Note2. I can't seem to get TWRP to take at all. I've tried 4 methods... flashing over in recovery, Oden, terminal and Goo Manager. All getting errors without install. Help please
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
SysAdmNj said:
I used goo manager after going to this link http://teamw.in/project/twrp2 and selecting my device. Pretty easy install from the goomanager. Then from goomanager I "reboot into recovery".
Click to expand...
Click to collapse
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
U have to make sure u are rooted first.
Sent from the TermiNOTEr!
mr1080p said:
Yeah I did that that first time and it didn't work. I get that little Android guy laying down dead with his heart out. Are you using a different kernel? I'm running stock.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
SysAdmNj said:
Im not running any other kernel. All I've done so far is root and twrp.
I believe you installed cwm? and a ported rom as well?
Click to expand...
Click to collapse
Yes. CWM and ported ROM. Everything works well I just want TWRP. But I guess I'll do with CWM. If it aint broke then why fix it. It works I guess. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
Check your build prop for device name. Maybe its not correct because of the Rom you're on. Whats the error you're getting?
Did you ever get TWRP on your phone?
I've had goofy issues with TWRP but much prefer it to CWM. Originally rooted using CWM and SuperSu and switched to TWRP when I flashed CleanRom several times via Romtoolbox pro I've flashed updated Twrp it said it was successful but when it rebooted was soft bricked! Had to use Odin and original CWM to get back in and re-install everything (nandroids were twrp backups) found file downloaded to sdcard that worked fine! Odd...
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
wargear said:
How can you wipe out all installed recoveries and start fresh? Via adb? Like to wipe Everything n start fresh advice? Running TWRP 2.4X -==
Click to expand...
Click to collapse
If by "installed" you are referring to the recovery program itself (and not your backups), you can only have one recovery 'installed' at one time as there is only 1 "Recovery" partition on the device (/dev/block/mmcblk0p9). So if you want to install CWM instead of your current TWRP (or visa-versa), either flash the appropriate new recovery zip via your current recovery... or Odin3 flash your desired new recovery tar. Either way, it will write to the same recovery partition. If you are referring to your backups... these are stored in the designated path you selected (either internal sd or external sd)... in the TWRP/BACKUPS folder. In that folder, you will have a device id #... in that folder are your backups.
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
wargear said:
Gotcha! Thanks the way it acted I wondered if there were "leftovers" in recovery partition or corrupt data. When I reflashed CWM or TWRP via ODIN it didn't say "Passed" instead "RESET" and I had to unplug phone and manually boot recovery which sometimes took a couple tries... Only boxes checked in Odin are reset time and reboot.
Click to expand...
Click to collapse
Which version of Odin3 are you using? When I used Odin3 v1.85 I would get the "PASSED" but with Odin3 v3.07, I also only got "RESET" (on an WindowsXP box)... but both flashed it correctly (and auto rebooted after flash)
Galaxy Note2 TOOLKIT V3.0.0 ATT]
I tried the [Galaxy Note2 TOOLKIT V3.0.0 ATT] http://forum.xda-developers.com/showthread.php?t=2052779 out of curiosity sake. Worked for me installing TWRP 2.3.2.3 without a hitch. Great tool from what I can see, and that's just one of it's many features. Great for simplifying things for new Android users just entering the customizing scene and regulars alike. Big ups to mskip for making this available. I can foresee myself grabbing the donate version here real soon.
And to get yourself SIM unlocked, get yourself back to 4.1.1 and give this a whirl.http://forum.xda-developers.com/showthread.php?t=2014982 Bought my device used, was supposedly unlocked, wasn't. Even came with an unlock code that the previous owner purchased. Firstly it's a no go on 4.1.2, secondly still didn't work when I dropped back to 4.1.1. But this http://forum.xda-developers.com/showthread.php?t=2014982 will set you free. Big thanks owl74 for posting. Once again XDA forums saves my hair from being pulled out.
Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!
I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!
I have already rooted with Odin. And after that, all I've done is disabled knox.
I'd like to install CyanogenMod 11 on my SM-P600
I've downloaded "recovery-cm-11-20141114-UNOFFICIAL-lt03wifi.tar" and "cm-11-20141114-UNOFFICIAL-lt03wifi.zip" from (http://forum.xda-developers.com/gal...m-p600-cyanogenmod-11-note-10-1-2014-t2929908).
From what I've read, I need something called a "recovery" and Gapps.
Can I just use any recovery and Gapps I find on the internet? Or are there specific ones for each phone/tablet?
Thanks for your help.
lonelyastronaught said:
I have already rooted with Odin. And after that, all I've done is disabled knox.
I'd like to install CyanogenMod 11 on my SM-P600
I've downloaded "recovery-cm-11-20141114-UNOFFICIAL-lt03wifi.tar" and "cm-11-20141114-UNOFFICIAL-lt03wifi.zip" from (http://forum.xda-developers.com/gal...m-p600-cyanogenmod-11-note-10-1-2014-t2929908).
From what I've read, I need something called a "recovery" and Gapps.
Can I just use any recovery and Gapps I find on the internet? Or are there specific ones for each phone/tablet?
Thanks for your help.
Click to expand...
Click to collapse
Here check the last half of the first page and all the rest of the pages. http://forum.xda-developers.com/showthread.php?t=2948791
Sent from my SM-P600 using XDA Free mobile app
Orion116 said:
Here check the last half of the first page and all the rest of the pages. http://forum.xda-developers.com/showthread.php?t=2948791
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. I've read that thread and I downloaded Flashify. I got TWRP 2.7.x.x and tried to flash CyanogenMod 12 but people were having trouble so I went back to Flashify and flashed TWRP 2.6.3 instead. When I hit reboot, the tablet put itself in a loop. It goes to the Samsung GALAXY NOTE 10.1 2014 Edition screen then turns off, and cycles from there.
I guess I had to unflash 2.7.x before flashing 2.6.3 or something? I probably bricked my device at this point.
I can get into Odin but I'm not sure what to do from here.
EDIT: I went to the TWRP site and downloaded 2.7.1.0 onto my PC and Odin'd my tablet with it. I'm restoring to my StockRoot backup. I don't know why Flashifying TWRP 2.6.3 softbricked my tablet and at this point I don't think I know what I'm doing.
lonelyastronaught said:
Thank you. I've read that thread and I downloaded Flashify. I got TWRP 2.7.x.x and tried to flash CyanogenMod 12 but people were having trouble so I went back to Flashify and flashed TWRP 2.6.3 instead. When I hit reboot, the tablet put itself in a loop. It goes to the Samsung GALAXY NOTE 10.1 2014 Edition screen then turns off, and cycles from there.
I guess I had to unflash 2.7.x before flashing 2.6.3 or something? I probably bricked my device at this point.
I can get into Odin but I'm not sure what to do from here.
EDIT: I went to the TWRP site and downloaded 2.7.1.0 onto my PC and Odin'd my tablet with it. I'm restoring to my StockRoot backup. I don't know why Flashifying TWRP 2.6.3 softbricked my tablet and at this point I don't think I know what I'm doing.
Click to expand...
Click to collapse
Hmm. That happen to someone else too who tried to downgrade TWRP from 2.7.x.x. Did Obin TWRP 2.7.X.X. fix the bootloop? If so you are ok. Otherwise I would Obin Samsung stock and reroot. And flash 2.6.3 with Obin.
Sent from my SM-P600 using XDA Free mobile app
Orion116 said:
Hmm. That happen to someone else too who tried to downgrade TWRP from 2.7.x.x. Did Obin TWRP 2.7.X.X. fix the bootloop? If so you are ok. Otherwise I would Obin Samsung stock and reroot. And flash 2.6.3 with Obin.
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
Yes it worked, thank you for responding.
I was then able to flash CyanogenMod 12 with another attempt on TWRP 2.7.1.1
I'm having an issue with my original StockRoot backup though. When I restore to it, it tells me, "Unfortunately, com.android.keyguard has stopped" after booting. I believe this has caused my Home button and Notification Panel (drop-down menu) to stop working as they are non-responsive. It also shows me a black wallpaper. All my files seem to be fine though. I just have to press the back soft key button a couple times to get back to the home screen.
Is there a way to fix this or would I need to Odin Samsung stock and re-root?
My goal is to have a CyanogenMod 12 back-up and my Original StockRoot backup working if possible.
I just need to fix this keyguard problem then flash CyanogenMod12 with Gapps and I think I'll be set for a while.
Thanks for your help.
Looks like I'm going to need to go back to Stock and Re-Root. What's the best way of doing this?
lonelyastronaught said:
Looks like I'm going to need to go back to Stock and Re-Root. What's the best way of doing this?
Click to expand...
Click to collapse
Download the stock from Sammobile. Com and flash using Obin. From the sounds of things you seem to be doing OK for not having much experience?☺
Note: if it seems like I am ignoring you it is because I am in the middle of finals?
Sent from my SM-P600 using XDA Free mobile app
No worries, you've been a ton of help - really appreciate it. But just to update you I flashed and its all back to normal after flashing from Sammobile firmware. It fixed keyguard so im back to where I started.
Now im just gunna try different roms and see what I like.