Related
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
ScottDB said:
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
Click to expand...
Click to collapse
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
aekel87 said:
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
Click to expand...
Click to collapse
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Deleted.
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Thank you!!!! I just had the same problem. However even when using cwm i get errors in the recovery. Unable to mount anything or do anything besides reboot. Any ideas?
need stock Firmware
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
iamwaynes said:
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
Click to expand...
Click to collapse
This is the h1 stock you need. type this in google you should find the download if not I have it.
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV0
Dont use e-z recovery. I had the same problem neither cwm or twrp from ez recovery worked and then cwm said no os on my phine so I flashed that file from download mode and was back to stock.
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
iamwaynes said:
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1771398
In that thread go down to method 2 of getting a custom recovery. I downloaded cwm touch from the link there and then installed it with android terminal emulator using the codes that it says to type in. I tried to look up that stock rom but I didnt find it. Its on the forum somewhere in a thread about how to root the straight talk s3 and how first you need to download and flash the h1 baseband stock rom
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
iamwaynes said:
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
iamwaynes said:
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Have you gotten recovery installed and straightened out yet?
Let me know if you need some help, tell me where you're at and what you've got going on with what you have.
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
iamwaynes said:
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Droidriven said:
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Click to expand...
Click to collapse
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
---------- Post added at 07:42 AM ---------- Previous post was at 07:23 AM ----------
sazendrak said:
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
Click to expand...
Click to collapse
Finally found it here
https://forum.xda-developers.com/showthread.php?t=2516498&page=28
I've been scouring over this website (SO much great information!), but am overwhelmed. I'm wondering if anyone would be so kind as to give me sort of the idiot's guide to root/rom my phone.
I have the straight talk galaxy SCH-S968C. It is running 4.1.2, is there anyway that I can get this to update to 4.4? After my research I'm pretty sure I can figure out how to root it (haven't done this yet, because I'm a little terrified).
Then is it possible to some how update it to 4.4. If this is possible, how do I do it?
Thanks for any help. I really do appreciate it!
I bit the bullet and rooted the phone. Wow could that have been any easier?!
I guess now what do I do?
Thank you so much for any help!
MrsELF said:
I bit the bullet and rooted the phone. Wow could that have been any easier?!
I guess now what do I do?
Thank you so much for any help!
Click to expand...
Click to collapse
Unsure about the straight talk version of the S3 and I'm not even sure what version it's currently on. I know the VZW S3 ended up being on 4.4.2 but the ST version may of been different
From my Wicked S3 on SOKP
MrsELF said:
I bit the bullet and rooted the phone. Wow could that have been any easier?!
I guess now what do I do?
Thank you so much for any help!
Click to expand...
Click to collapse
ShapesBlue said:
Unsure about the straight talk version of the S3 and I'm not even sure what version it's currently on. I know the VZW S3 ended up being on 4.4.2 but the ST version may of been different
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
here you guys go
http://forum.xda-developers.com/showthread.php?t=2516498&page=30
Sent from my SCH-S968C using Tapatalk
Dummies Guide?
N_psycho_PD_uh? said:
here you guys go
http://forum.xda-developers.com/showthread.php?t=2516498&page=30
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Thanks! That wasn't the thread I was following to figure out how to upgrade, I had read that previously but didn't realize it had derailed to roms. I'm still making my way through it (only on page 33). I'm wondering is there a newb guide to this, like a Dummies Guide To Flashing Roms? I'm a somewhat technical person, but I've never worked on phones before. I'm stuck at this 4.1.2 version, and I would REALLY love to be at anything other than this. I just am beyond terrified of bricking my phone.
I have my phone rooted. I took a backup, I have terminal emulater, EZ - recovery, Clockwordl Mod, and superuser installed. I downloaded google apps (gapps-kk-20140105-signed) and cm-11-20140916-SNAPSHOT-M10-d2lte. I'm just unsure of my next steps. I just want re-assurance before I continue, I really don't want to brick my phone. Thanks again!
I would truly appreciate any and all help. Thanks!
MrsELF said:
Thanks! That wasn't the thread I was following to figure out how to upgrade, I had read that previously but didn't realize it had derailed to roms. I'm still making my way through it (only on page 33). I'm wondering is there a newb guide to this, like a Dummies Guide To Flashing Roms? I'm a somewhat technical person, but I've never worked on phones before. I'm stuck at this 4.1.2 version, and I would REALLY love to be at anything other than this. I just am beyond terrified of bricking my phone.
I have my phone rooted. I took a backup, I have terminal emulater, EZ - recovery, Clockwordl Mod, and superuser installed. I downloaded google apps (gapps-kk-20140105-signed) and cm-11-20140916-SNAPSHOT-M10-d2lte. I'm just unsure of my next steps. I just want re-assurance before I continue, I really don't want to brick my phone. Thanks again!
I would truly appreciate any and all help. Thanks!
Click to expand...
Click to collapse
if you are rooted, have custom recovery installed and made your backup of your stock firmware in recovery(MAKE SURE YOU DO THIS SO YOU DONT HAVE PROBLEMS) , then all you have to do is put your CM ROM and your Gapps on your extsd card where you can find it, if you put it in a folder then remember which folder it is so you can find it, when you have it there then make sure your battery is fully charged, when its charged then boot to recovery, in recovery select install zip, then select install zip from sd card, then find your ROM and select it, then yes-install zip, it will then flash your ROM, whe its done do the same to flash your Gapps, when its done go back to main menu in recovery and select wipe data/factory rest, when its done select wipe cache, when done select advanced, then select wipe dalvik cache, when done go back to main menu and select reboot, let it load, it will be slow at first because it has to load everything you just flashed, just give it a minute, if it takes to long then just power it down and reboot, when it does boot you'll have to do your setup wiz like you did whe you first got the phone, finish setup, ENJOY your new ROM.
**now that you have custom recovery then anytime you find a rom for your phone that you want to try all you have to do is download your ROM and Gapps, place them on extsd like I instructed, then boot recovery and repeat what you just did but remember to make a backup of what you are running at the time BEFORE you flash the new, that way if you have problems with the new or if it won't boot then all you gotta do is boot to recovery select restore then restore the backup you nade and you'll be good again, I told you this just in case you have problems in future or want a new ROM. Good luck!
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
MrsELF said:
Thanks! That wasn't the thread I was following to figure out how to upgrade, I had read that previously but didn't realize it had derailed to roms. I'm still making my way through it (only on page 33). I'm wondering is there a newb guide to this, like a Dummies Guide To Flashing Roms? I'm a somewhat technical person, but I've never worked on phones before. I'm stuck at this 4.1.2 version, and I would REALLY love to be at anything other than this. I just am beyond terrified of bricking my phone.
I have my phone rooted. I took a backup, I have terminal emulater, EZ - recovery, Clockwordl Mod, and superuser installed. I downloaded google apps (gapps-kk-20140105-signed) and cm-11-20140916-SNAPSHOT-M10-d2lte. I'm just unsure of my next steps. I just want re-assurance before I continue, I really don't want to brick my phone. Thanks again!
I would truly appreciate any and all help. Thanks!
Click to expand...
Click to collapse
the rom you will be using will need to be worked with our simple fixes, make sure you have a dead sim, you might try the d2lte ROMs if you can deal with 3rd party apps instead of stock, just follow what the guys are doing in the thread
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:53 PM ---------- Previous post was at 04:39 PM ----------
by the way, I didn't send you to the thread for the ROMs themselves I sent you there to pick through the members posts about what was working, what wasn't and how to straighten the issues out so you could decide which ROM you were comfortable with.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:56 PM ---------- Previous post was at 04:53 PM ----------
if you are still unsure then the thread where you got your ROM should have a walthrough in the Original Post, all threads with ROMS should have walkthroughs with the links for your resources.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 05:37 PM ---------- Previous post was at 04:56 PM ----------
so are you good yet? just checking in on you
Sent from my SCH-S968C using Tapatalk
thanks!
N_psycho_PD_uh? said:
if you are rooted, have custom recovery installed and made your backup of your stock firmware in recovery(MAKE SURE YOU DO THIS SO YOU DONT HAVE PROBLEMS) , then all you have to do is put your CM ROM and your Gapps on your extsd card where you can find it, if you put it in a folder then remember which folder it is so you can find it, when you have it there then make sure your battery is fully charged, when its charged then boot to recovery, in recovery select install zip, then select install zip from sd card, then find your ROM and select it, then yes-install zip, it will then flash your ROM, whe its done do the same to flash your Gapps, when its done go back to main menu in recovery and select wipe data/factory rest, when its done select wipe cache, when done select advanced, then select wipe dalvik cache, when done go back to main menu and select reboot, let it load, it will be slow at first because it has to load everything you just flashed, just give it a minute, if it takes to long then just power it down and reboot, when it does boot you'll have to do your setup wiz like you did whe you first got the phone, finish setup, ENJOY your new ROM.
**now that you have custom recovery then anytime you find a rom for your phone that you want to try all you have to do is download your ROM and Gapps, place them on extsd like I instructed, then boot recovery and repeat what you just did but remember to make a backup of what you are running at the time BEFORE you flash the new, that way if you have problems with the new or if it won't boot then all you gotta do is boot to recovery select restore then restore the backup you nade and you'll be good again, I told you this just in case you have problems in future or want a new ROM. Good luck!
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
the rom you will be using will need to be worked with our simple fixes, make sure you have a dead sim, you might try the d2lte ROMs if you can deal with 3rd party apps instead of stock, just follow what the guys are doing in the thread
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:53 PM ---------- Previous post was at 04:39 PM ----------
by the way, I didn't send you to the thread for the ROMs themselves I sent you there to pick through the members posts about what was working, what wasn't and how to straighten the issues out so you could decide which ROM you were comfortable with
Sent from my SCH-S968C using Tapatalk
---------- Post added at 04:56 PM ---------- Previous post was at 04:53 PM ----------
if you are still unsure then the thread where you got your ROM should have a walthrough in the Original Post, all threads with ROMS should have walkthroughs with the links for your resources.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 05:37 PM ---------- Previous post was at 04:56 PM ----------
so are you good yet? just checking in on you
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Thanks. I haven't had a chance try to put the rom on yet. I was working on this in early october and hadn't recieved any response back (that's why the rom and gapps are probably old - I'm assuming I'll need newer versions). I saw that there was a newer gapps in that thread posted. So thanks for that. Again I was not following that one earlier. I had read it but that was when I was trying to root not upgrade. I'll need to go through that thread again to see what roms people are using. I'm okay with using 3rd party apps (as long as everything works). And I need to find myself an old sim card. I think I've got an old phone laying around somewhere.
To the bolded, no there was no walk through (at least that I saw). It was chunks here and there but nothing really step by step. I know I'm a newb, but I'm pretty technical person I just like having instructions before I do things (unless I had a phone that i didn't care about wrecking!).
Thanks again for the help. I'm still nervous about doing this though!
@MrsELF you are rooted and have recovery so the hard and risky part is over, all you need now is your rom and gapps then put them on extsd like I said, then I literaly gave the instructions step by step word for word leaving nothing out or skipping anything, would you like me to give you a link for detailed instructions of what your recovery is, the funtions and features it has and how they are used? Do you want me to find you a tutorial on flashing a rom? Honestly, you are passed the dangerous part so relax. Your risk comes involved if you have a problem in the process before you get recovery installed, you have recovery so you have nothing to worry about now because you have your nandroid backup so even on the off chance that you have a problem your backup ccan be easily restored and you will be fine, that's why its called "RECOVERY" its a safety net, so even if you flash the wrong thing don't panic, its very simple, boot to recovery and restore your backup and threat eliminated. The CM11 and the CM12 are good roms but the CM12 is still buggy but getting better, CM11 2/17 nightly (I think) is stable with the third party apps. I think we are close to getting the stock MMS working, but we are still missing something, anyway, all the d2lte roms are supposed to be fine with the apps and sim, you can actually download as many as you like and try each one, flash one then test drive it, if you don't like it select another and flash it, test drive it and so on till you find the one you like, reading isn't going to find it for you, you'll just have to see how they each "feel".Actually your rom might work as it is because the older d2vzw roms work fine, the problem didn't start til the d2lte roms because that's when they merged all the builds for all the different S3s into one, that's why we have bugs because the devices are not all the same, if you'd like you can get on another device so we can comm back and forth through your flashing. You really do have no reason to be nervous now.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 09:40 AM ---------- Previous post was at 09:29 AM ----------
[/COLOR @MrsELF, the tapatalk app makes navigating these forums a lot easier, it also gives you acces to every forum site for android devices, there are many, XDA is the top of the game in my opinion but you CAN sometimes find things on other sites that you won't find here
Sent from my SCH-S968C using Tapatalk
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Rom manager makes it easier to find and download roms for your device because it will only give you a list of roms that work for your device so you don't have to pick through the crowd of other ROMs for other devices.
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
@MrsELF you are rooted and have recovery so the hard and risky part is over, all you need now is your rom and gapps then put them on extsd like I said, then I literaly gave the instructions step by step word for word leaving nothing out or skipping anything, would you like me to give you a link for detailed instructions of what your recovery is, the funtions and features it has and how they are used? Do you want me to find you a tutorial on flashing a rom? Honestly, you are passed the dangerous part so relax. Your risk comes involved if you have a problem in the process before you get recovery installed, you have recovery so you have nothing to worry about now because you have your nandroid backup so even on the off chance that you have a problem your backup ccan be easily restored and you will be fine, that's why its called "RECOVERY" its a safety net, so even if you flash the wrong thing don't panic, its very simple, boot to recovery and restore your backup and threat eliminated. The CM11 and the CM12 are good roms but the CM12 is still buggy but getting better, CM11 2/17 nightly (I think) is stable with the third party apps. I think we are close to getting the stock MMS working, but we are still missing something, anyway, all the d2lte roms are supposed to be fine with the apps and sim, you can actually download as many as you like and try each one, flash one then test drive it, if you don't like it select another and flash it, test drive it and so on till you find the one you like, reading isn't going to find it for you, you'll just have to see how they each "feel".Actually your rom might work as it is because the older d2vzw roms work fine, the problem didn't start til the d2lte roms because that's when they merged all the builds for all the different S3s into one, that's why we have bugs because the devices are not all the same, if you'd like you can get on another device so we can comm back and forth through your flashing. You really do have no reason to be nervous now.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 09:40 AM ---------- Previous post was at 09:29 AM ----------
[/COLOR @MrsELF, the tapatalk app makes navigating these forums a lot easier, it also gives you acces to every forum site for android devices, there are many, XDA is the top of the game in my opinion but you CAN sometimes find things on other sites that you won't find here
Sent from my SCH-S968C using Tapatalk
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Rom manager makes it easier to find and download roms for your device because it will only give you a list of roms that work for your device so you don't have to pick through the crowd of other ROMs for other devices.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
I truly appreciate the help! I just need to find the rom that I know want to use. You say the riskiest part is over.... Well that happened to be the EASIEST part! It seriuosly took like two seconds to root the phone. I just am nervous that I'm not finding the "correct" rom for my phone. And it's like I need to find a half an hour of my time to attempt to do this once i find an old sim card.
Random question for you, I read in that thread you linked, that you haven't rooted/flashed your phone. Is there a reason why?
my pc is fritzed, everything else I have is rooted and tweaked out to the max not just custom flashed, I'm getting impatient though, I'm ready to get on a ROM and do some tests and work some bugs out, why? I would also love to get my hands on the stock firmware for my device first because I have the H2 device and since there is no root for H2 without downgrading to H1, if I downgrade I will lose the stock H2 with no way to get it back, ill be on H1, it would be nice to have the H2 stuff to work with because it has upgrades over the H1, modem and things like that plus my device has 2Gb RAM where yours has 1Gb
Sent from my SCH-S968C using Tapatalk
---------- Post added at 10:30 AM ---------- Previous post was at 10:19 AM ----------
if you would like to ask the other guys questions that are actually on the roms then you can type thier name in with a mention and they will get a notification telling them that you mentioned them and they'll check and they'll probably be more than glad to answer you, you do that by adding the @ to their name like this: @MrsELF, give it a try if you'd like to ask one of them wgat they are running, you can be sure that they are running the best and easiest choice, so you might want what they have
Sent from my SCH-S968C using Tapatalk
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
you actual flashing will only take like five minutes maybe ten, it will take you longer to get your download than it will to flash, once you boot to recovery it only takes a minute or two to flash each zip so its not a long process
Sent from my SCH-S968C using Tapatalk
@N_psycho_PD_uh? Thanks for the help. I think I'll stick with the ones i've got downloaded then, and use the third party apps. Until the newer ones become more stable. Do you happen to know with the ROM I've got downloaded if I need the extra sd card? Just wondering because if I don't then I can try doing this shortly.
Also it's been awhile since I've looked at all this, so I was just making sure I had everything on my phone that i needed and the unbrick image. I ran this dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick.img bs=4096 count=50000 to make a backup (from terminal emulator). Where on earth did the unbrick.img go? I can't seem to find it anywhere on my sdcard. But it actually looked like it did run the command. I'm slightly confused.
MrsELF said:
I truly appreciate the help! I just need to find the rom that I know want to use. You say the riskiest part is over.... Well that happened to be the EASIEST part! It seriuosly took like two seconds to root the phone. I just am nervous that I'm not finding the "correct" rom for my phone. And it's like I need to find a half an hour of my time to attempt to do this once i find an old sim card.
Random question for you, I read in that thread you linked, that you haven't rooted/flashed your phone. Is there a reason why?
Click to expand...
Click to collapse
rooting and recovery on your device just happens to be easy, don't be fooled its not so easy on a lot of devices, you just got lucky and got an easy one, actually this device can be rooted, recovery and rommed all without using a pc even once, therez an app called towelroot that is just a 1 click and its rooted, EZ recovery is a 1 click for recovery and ROM Manager is an app that lets you find a ROM, download it and boot straight from ROM Manager into recovery without having to use the buttons to boot there then it flashes whst you selected, easy as pie, plus no risk because the apps won't dont even make it possible to choose or do wrong, just a few clicks and a few minutes and your full custom all without touching a pc but I'm not so fortunate because I have the H2
Sent from my SCH-S968C using Tapatalk
One last thing
@N_psycho_PD_uh? A couple of questions:
1. I ran this to get the unbrick image (this is the backup that I would need to restore it right?) dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick.img bs=4096 count=50000
Or is there a different backup I need to take? I saw on some other video or someplace, that if you boot into recovery mode, you can take a backup from there. I don't see that option.
2. When I go into recovery mode, it doesn't look like the video I watched or what you described. I would think i should see a "install from zip" option but there isn't. Here is what I have:
reboot system now
apply update from ADB
apply update from external storage - I'm assuming I'd pick this one, and when I do I can then navigate to the place where I have my ROM stored.
wipe data/factory reset
wipe cache partition
apply update from cache.
Sorry for the dumb questions and hand holding
ETA: I have ROM Manager installed, but I don't think i actually have clockwork mod installed.... Looks like I need to figure out how to install that.
ETA: I know how to install it, but I have to figure out what phone model to use.
MrsELF said:
@N_psycho_PD_uh? A couple of questions:
1. I ran this to get the unbrick image (this is the backup that I would need to restore it right?) dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick.img bs=4096 count=50000
Or is there a different backup I need to take? I saw on some other video or someplace, that if you boot into recovery mode, you can take a backup from there. I don't see that option.
2. When I go into recovery mode, it doesn't look like the video I watched or what you described. I would think i should see a "install from zip" option but there isn't. Here is what I have:
reboot system now
apply update from ADB
apply update from external storage - I'm assuming I'd pick this one, and when I do I can then navigate to the place where I have my ROM stored.
wipe data/factory reset
wipe cache partition
apply update from cache.
Sorry for the dumb questions and hand holding
ETA: I have ROM Manager installed, but I don't think i actually have clockwork mod installed.... Looks like I need to figure out how to install that.
ETA: I know how to install it, but I have to figure out what phone model to use.
Click to expand...
Click to collapse
the unbrick img was a good idea, if you want to be sure you did it right then go to the XDA home page and click the xda search box and type How to unbrick sch-i535, that will take you to a post with detailed instructions on how to make and use the unbrick.img
you have your stock recovery still so use either Rom manager or EZ recovery apps to find your CWM (clockworkmod) you are looking for the one for the verizon s3
Sent from my SCH-S968C using Tapatalk
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
go in your terminal emulator and type command "adb reboot nvdata backup" that will nake a backup of your imei for restoring data connectivity if something happens, you shouldn't need the unbrick and the nvdata backup though, but they are nice to have, you can do a search on each for more instructions on how to make and use them, what gave you the idea to make your backups? I saw that you've been to AA51, did you read my OP there or something?
Sent from my SCH-S968C using Tapatalk
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
I deleted that OP because with the fixes that we found the dangers that I had listed in my OP are no longer a problem.
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
the unbrick img was a good idea, if you want to be sure you did it right then go to the XDA home page and click the xda search box and type How to unbrick sch-i535, that will take you to a post with detailed instructions on how to make and use the unbrick.img
you have your stock recovery still so use either Rom manager or EZ recovery apps to find your CWM (clockworkmod) you are looking for the one for the verizon s3
Sent from my SCH-S968C using Tapatalk
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
go in your terminal emulator and type command "adb reboot nvdata backup" that will nake a backup of your imei for restoring data connectivity if something happens, you shouldn't need the unbrick and the nvdata backup though, but they are nice to have, you can do a search on each for more instructions on how to make and use them, what gave you the idea to make your backups? I saw that you've been to AA51, did you read my OP there or something?
Sent from my SCH-S968C using Tapatalk
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
I deleted that OP because with the fixes that we found the dangers that I had listed in my OP are no longer a problem.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Thank you SO much!
MrsELF said:
Thank you SO much!
Click to expand...
Click to collapse
I'm not sure about the older roms and the sim card. Did you find your unbrick.img?
Sent from my SCH-S968C using Tapatalk
Yes I did somehow it was on my phone and not the sdcard.
N_psycho_PD_uh? said:
I'm not sure about the older roms and the sim card. Did you find your unbrick.img?
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
I gotta give it to ya, you're being thorough and doing your reasearch and not only looking to flash but also preparing solutions for any problems you may have and how to get it back, that's good, that's what I did when I did the research for this device, there are three completely different versions of the sch-s968c and the differences matter when flashing, H1 is fine but with the H2 there is one with a qcom chipset and one with a Exynos chipset and that matters, so I gathered all my pieces before going any further, the only thing you don't have that I do are the camera files from the thread and the modem file, those are tricky to use but I think you can handle it, btw there is a link in the thread that takes you to detailed unbrick instructions.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
MrsELF said:
Yes I did somehow it was on my phone and not the sdcard.
Click to expand...
Click to collapse
yes operations like that are written to internal sd from terminal emulator, you can actually use an app called Titanium Backup to nake your emulator a system app instead of a user app
Sent from my SCH-S968C using Tapatalk
N_psycho_PD_uh? said:
the unbrick img was a good idea, if you want to be sure you did it right then go to the XDA home page and click the xda search box and type How to unbrick sch-i535, that will take you to a post with detailed instructions on how to make and use the unbrick.img
you have your stock recovery still so use either Rom manager or EZ recovery apps to find your CWM (clockworkmod) you are looking for the one for the verizon s3
Sent from my SCH-S968C using Tapatalk
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
go in your terminal emulator and type command "adb reboot nvdata backup" that will nake a backup of your imei for restoring data connectivity if something happens, you shouldn't need the unbrick and the nvdata backup though, but they are nice to have, you can do a search on each for more instructions on how to make and use them, what gave you the idea to make your backups? I saw that you've been to AA51, did you read my OP there or something?
Sent from my SCH-S968C using Tapatalk
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
I deleted that OP because with the fixes that we found the dangers that I had listed in my OP are no longer a problem.
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
One last thing @N_psycho_PD_uh? I started searching for adb reboot nvdata backup. I can't find much about it. What exactly does this do? How do I restore if I need it? Where is the file stored? I was able to get CWM installed, and i took a backup from the recovery mode. Should I still backup the IMEI? I'm assuming so, but just figured that the backup I took from the recovery should be fine if I need to restore, right?
N_psycho_PD_uh? said:
I gotta give it to ya, you're being thorough and doing your reasearch and not only looking to flash but also preparing solutions for any problems you may have and how to get it back, that's good, that's what I did when I did the research for this device, there are three completely different versions of the sch-s968c and the differences matter when flashing, H1 is fine but with the H2 there is one with a qcom chipset and one with a Exynos chipset and that matters, so I gathered all my pieces before going any further, the only thing you don't have that I do are the camera files from the thread and the modem file, those are tricky to use but I think you can handle it, btw there is a link in the thread that takes you to detailed unbrick instructions.
Sent from my SCH-S968C using Tapatalk
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
yes operations like that are written to internal sd from terminal emulator, you can actually use an app called Titanium Backup to nake your emulator a system app instead of a user app
Sent from my SCH-S968C using Tapatalk
Click to expand...
Click to collapse
Like I said I work in a tech field, I've had to restore in the past (not phones but other systems), and not having the proper backups make restoring a nightmare. So I have found (from past experience) it is SO much easier to be prepared for the worst to happen, and be happy when you don't need to use those files
Thanks again for all your help and guidance I really do appreciate it.
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Edit:
HEY, YOU. YEAH YOU. READ THIS BEFORE YOU POST:
We figured out the solution quite a while back, but I know no one wants to read the entire thread, so here's a summary c/p'd from the end:
But to summarize, we've been able to get root by flashing CF auto root, letting it fail, then immediately flashing TWRP. To fix any issues encountered with xposed framework (stock sms not working, lagginess, installations taking forever, etc.), freeze with titanium/delete data for shealth, health services, and private mode, install securestorage module in xposed or use the equivalent option in Wanam, reboot, and unfreeze.
Click to expand...
Click to collapse
Now if you've tried this and you're still having issues, then post ahead. If you haven't tried this, or need help with specifics, read the thread. There's a post by me halfway through or so with 4 XDA links in it. If you want more info on the problem with xposed, check out those links.
jooniloh said:
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Click to expand...
Click to collapse
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Does TWRP fully support the note edge yet? Some of those steps (disabling screen timeout) make it seem otherwise. I'm usually hesitant to go for workarounds rather than actual fixes... :/ tell me if you do try it out though.
Next1776 said:
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Click to expand...
Click to collapse
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Next1776 said:
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Click to expand...
Click to collapse
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
z31k said:
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
Click to expand...
Click to collapse
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
jooniloh said:
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
Click to expand...
Click to collapse
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
z31k said:
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
Click to expand...
Click to collapse
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
jooniloh said:
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
Click to expand...
Click to collapse
Lmfao!!
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
jooniloh said:
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
Click to expand...
Click to collapse
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
beejmeister said:
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
Click to expand...
Click to collapse
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
EDIT: See my post here : http://forum.xda-developers.com/note-edge/general/info-galaxy-note-edge-sm-n915-t2945942 for more details on what worked for me
jooniloh said:
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
Click to expand...
Click to collapse
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
beejmeister said:
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Click to expand...
Click to collapse
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
jooniloh said:
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
Click to expand...
Click to collapse
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Next1776 said:
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Click to expand...
Click to collapse
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
BUt just to confirm, jooniloh.... you do have confirmable root? Guess my clue should be that you are using xposed.... but just wanted to confirm before I went down the rabbit hole....
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
Awesome. Glad you are able to join the party!
I'm not having any issues right now. I have installed Xposed and Wanam without any issues so far. I did disable Knox and Secure storage with Wanam (under security hacks) as another poster suggested. Maybe also try wiping Cache and dalvik in recovery ? Hopefully we will have a stable custom recovery available soon. I say stable, but I guess this one is "stable" - its just not real pretty...
I have a oneplus one that I just returned to stock using the method in this thread: http://forum.xda-developers.com/onep...stock-t2826541
Problem is that at some point, while it was rooted, I used this method to make my phone microphone work (changing the build.prop file): https://forums.oneplus.net/threads/f...-issue.284449/
If I had remembered that I'd done that, I might have just left the phone alone. So, now that I'm back to stock and unrooted, my microphone doesn't work and I can't use the above method to make it so. Is there a solution out there I can use without going back to root?
My exact problem with the mic is that when I talk into the phone, the person on the other end can't hear me but I can hear myself (echo) in my earpiece. I can hear the person on the other end fine. If I switch to speaker phone I still have the same issue. Any help would be appreciated.
You'll need to go root again. Lucky this isn't too hard especially if you maintained a custom recovery. If not, then you will have to use adb. Or bacon root toolkit (the easy way).
Sent from my A0001 using Tapatalk
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
You can use KingRoot to root without custom recovery. After changing the values you can then unroot it to get future OTA updates
anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk
Elius2676 said:
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I got Cyanogen Recovery. Options are "reboot system now", "Apply update", "factory reset", and "advanced".
So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.
anonymous93 said:
So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.
Click to expand...
Click to collapse
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk
Elius2676 said:
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?
anonymous93 said:
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?
Click to expand...
Click to collapse
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk
Elius2676 said:
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yes and no. Turns out I was actually able to boot my phone into fastboot mode. So I did that, used the baconroot toolkit option of "flash stock + unroot" and I was back to the start. My device now has an unlocked bootloader, but I think I have issues with the tamper bit. When I get my device info the "Device tampered" is set to "false" and the "device unlocked" is set to "true". I know they should both be true, but I can't for the life of me figure out how to use the zip file to change the tamper bit. I did it before, but I'm just not figuring it out this time. I hate doing this stuff.
I think once the tamper bit is correct I should be able to go back to baconroot to root and reinstall the custom recovery.
Update: I finally figured this out, now rooting with bacon root, hoping it works.
I'm all set, now to make the adjustments so my microphone works. Thanks to everyone that helped!
So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.
anonymous93 said:
So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.
Click to expand...
Click to collapse
So sounds like you just wiped everything and your phone is back to stock now, but I'm getting the impression you still have a custom recovery or modified system partition and the OTA updates don't like that. So yes, you'll need to flash updates in your recovery. It's not as bad as it sounds.
And about Android versions available to you, the stock COS (which might actually say "CM..." when you check your Android version in "about phone" in settings - confusing, I know) can normally receive the OTA updates (except in the cases mentioned above) or you can get the official updates online in zip form and flash them yourself (even with the stock recovery -which I'm pretty sure you have still, unless one of your methods to fix the phone installed a custom one like TWRP or CWM). The other ROM/OS options you have are about as plentiful as the stars in the heavens (since android is open source). I personally like to stick with CM especially since they do what they do very well and they have a particular interest in there OnePlus One. They just released CM 14 nightlies (which basically means it's the latest version of the OS, bugs and all, built every day). Though, to be honest, this CM 14 nightly is ridiculously stable for a freshly released nightly. At this point, though, cyanogen hasn't implemented a fair number of their customizations that are in their previous versions. So if you want the best complete CM experience right now, go with CM 13.
And to answer your question, updates like the ones that are OTA, don't wipe your data or storage. However, if you switch from COS to CM, you'll have to clean install and that will lose your data at the least (your internal storage can usually be kept between ROMs if you've got a custom recovery).
Sorry, in throwing a lot at you right now. Probably just created more questions than answers...
Sent from my A0001 using Tapatalk
Thanks for your help and the explanations. When you talk about COS vs. CM is that Cyanogen OS vs. Cyanogen Mod?
I was able to root and I have TWRP installed. In about phone it says "Cyanogen OS version" is "12.1-yog4pas1n0". That's the Cyanogen OS correct?
Where do I go to download the update for 13 (whatever matches what I already have) and is there a guide for doing that? I'm reading about updating to 13 and everything I see (so far) states that the update has to happen with stock recovery. Is there an option to run the update with TWRP?
Wait a minute... If I unroot but keep the bootloader unlocked then it won't wipe my phone and I'll be able to take the ota updates right? What about the change I made to the build.prop file for my phones microphone? Will that get wiped if I unroot? That's the big question.
Nevermind about unrooting. After some searches it seems that a full unroot would require a rest which would delete the mod I made for the microphone. I found that supersu can "unroot", but it's not actually a fill unroot which means that I still probably wouldn't be able to do the ota updates.
Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk
Elius2676 said:
Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?
anonymous93 said:
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?
Click to expand...
Click to collapse
A backup in TWRP (or nandroid backup) is like a perfect picture of what you phone was running just before you booted it into recovery. So when you restore one of them, it is like the phone steps back in time to when you made the backup, restoring the system (read: OS), data (read: apps), and cache.
In other words, you do a backup so that you always have something you can restore if you break your phone/have boot loops or what have you when flashing new ROMs.
If you go from COS to CM, it will require a clean install which means you will need to setup your phone the way you like it again. That being said, there is an app called Titanium backup that doesn't work the same as a nandroid, but can backup your apps and data and is capable of restoring them from one ROM to the next. It's not always perfect, but it can do a lot.
I personally have just chosen to embrace the chance of needing to start fresh every once in a while. I use Nova launcher and I have a Kustom LWP, both of which I made backups of in their respective app settings. I save those backups and whatever else I want to internal storage and I just don't wipe that partition in TWRP. To be safe, I also keep backups in the cloud. Everything else I just download again from the play store and setup the way I like.
Sent from my A0001 using Tapatalk
Well, its looking more and more like I might go to cm. Once I do that will I still have to wipe my phone to flash updates? Or will I still have to do that for updates every once in a while?
Hi all,
Apologies for such a simple question, but there are a bunch of different threads over the last few months that have slightly differing techniques for rooting and adding TWRP to the J7, but there seem to be a ton of different versions compared to the J3 and I need to make sure I'm following the right directions for a Boost Mobile j700p. I don't want to waste time and risk softbricking this brand new device, so does anyone know or can link me to the most up-to-date reliable method? I just upgraded from a j3 and it seems like the method is very similar if not identical (odin twrp on, flash chainfire supersu, flash xposed) but I just to make sure I am following the right directions and using the right files. This is for a brand new Boost Mobile j700p.
I have attached a screenshot of my phone info, in case firmware version or baseband etc info is relevant.
Thanks in advance for all your help!
slvmecha said:
Hi all,
Apologies for such a simple question, but there are a bunch of different threads over the last few months that have slightly differing techniques for rooting and adding TWRP to the J7, but there seem to be a ton of different versions compared to the J3 and I need to make sure I'm following the right directions for a Boost Mobile j700p. I don't want to waste time and risk softbricking this brand new device, so does anyone know or can link me to the most up-to-date reliable method? I just upgraded from a j3 and it seems like the method is very similar if not identical (odin twrp on, flash chainfire supersu, flash xposed) but I just to make sure I am following the right directions and using the right files. This is for a brand new Boost Mobile j700p.
I have attached a screenshot of my phone info, in case firmware version or baseband etc info is relevant.
Thanks in advance for all your help!
Click to expand...
Click to collapse
bump
This is the way i was able to root my version of the J700P. MY phone is the same as the screen shot provided. The only issue that i had was once i flashed TWRP and did a backup, the phone would constantly boot into TWRP Recovery. So i had to reflash stock rom and root again oh and i unchecked OEM unlock to off, didnt realize i needed to leave it on so i wouldnt get the FRP Lock lol. Still waiting on someone to let me know how i can install TWRP Recovery and it work and not soft brick.
https://forum.xda-developers.com/galaxy-j7/how-to/root-samsung-galaxy-j7-sm-j700p-t3430185
Nas8 said:
This is the way i was able to root my version of the J700P. MY phone is the same as the screen shot provided. The only issue that i had was once i flashed TWRP and did a backup, the phone would constantly boot into TWRP Recovery. So i had to reflash stock rom and root again oh and i unchecked OEM unlock to off, didnt realize i needed to leave it on so i wouldnt get the FRP Lock lol. Still waiting on someone to let me know how i can install TWRP Recovery and it work and not soft brick.
https://forum.xda-developers.com/galaxy-j7/how-to/root-samsung-galaxy-j7-sm-j700p-t3430185
Click to expand...
Click to collapse
i have twrp, the most current version on the sm j700p. All you gotta do is use odin to install it. Just make sure u use the most recent odin and twrp file for j700p. Then when u place it in AP with odin make sure auto reboot option is turned off so it fully installs it. If u have auto reboot on it will not complete the process.
Ok I will give that a try, tyvm. I cant uncheck auto reboot. Here is a screenshot.
Sent from my SM-J700P using Tapatalk
---------- Post added at 08:08 PM ---------- Previous post was at 07:19 PM ----------
Ok so i re-downloaded Odin again and now its working fine. Just need to reboot and i will let you know.
Awesome! That worked. My Hero!!!! lol
---------- Post added at 08:32 PM ---------- Previous post was at 08:08 PM ----------
Ok sooo now i did a backup and now again, it just keeps rebooting back up into twrp. I have no idea whats going on with this. Gonna have to reflash stock rom again and then root again. This is frustrating to say the least.... Keeps saying Recovery is not seandroid enforcing, set warranty bit : recovery...... Thats whats it saying at the top...