Related
Problem resolved
Just swap it out from where you purchased it don't tell them what you did just say its not booting anymore they will swap it out
Sent from my LG-P925 using XDA App
Or see if you can boot into Recovery Mode, you may be able to do something there.
Yea see if you can boot into recovery and do a hard reset from there bud
Sent from my LG-P925 using Tapatalk
I did a factory reset from recovery but it didn't work.
Where did you get it? You should have 30 days to switch phones
1. To pick a different phone
2. Or to swap from a thrill 4 a thrill
I've alrealy used 2 different phones from bestbuy I'm not sure how many times they allow you to do so I think once so I may be stuck with the thrill which is okay I really want the galaxy 2 tho..
Sent from my LG-P925 using Tapatalk
dincdoes.me said:
Yea see if you can boot into recovery and do a hard reset from there bud
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
this didnt recover mine either.
No big deal. Swapped mine out today. I will hold on to the phone til the GS2 comes out, and then im switching.
ADB isn't recognizing the phone either. I believe I left it in USB Debugging mode before this all happened, but maybe that got reset when I did the factory reset and therefore it isn't enabled anymore.
Isn't the SG2 RELEASING ON SEP 16?
Sent from my LG-P925 using Tapatalk
manske90 said:
ADB isn't recognizing the phone either. I believe I left it in USB Debugging mode before this all happened, but maybe that got reset when I did the factory reset and therefore it isn't enabled anymore.
Click to expand...
Click to collapse
you are correct... any setting you may have altered in your phone is saved in the phone's data partition... the build.prop which im assuming you edited is saved in the system partition.. a factory reset only wipes the data partition, this means the setting you enabled for usb debug is set back to default and the build.prop you edited is left the way you edited it in the system partition completely unaffected... best chance is to wait for a manual CWM
dincdoes.me said:
Isn't the SG2 RELEASING ON SEP 16?
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
There are some rumors that it will be releasing that weekend. A friend at samsung claims that is impossible, the phone is in testing.. but some claim that retailers have told them it will release that weekend
How is it resolved?
Sent from my LG Thrill 4G
I have two bricked thrills and cannot get them in download mode.. I watched the video and am doing everything correct.. Just installs the darn texas instruments USB driver. This suuuucks.
what videos are you talking about. I bricked my thrill as well and it wont cut on at all. I have been looking for some sort of help and cant get any.
How was this solved?What were you doing to brick it?Would like to know incase I get there but it seemed easy enough to flash to few roms Ive tried so far.Thanks
Do you have any info on bricked thrills?
hey
manske90 said:
Problem resolved
Click to expand...
Click to collapse
How did you Brick it? what did you do to fix it? my thrill 4g is bricked, it happend to get bricked while trying to restore a stock rom..
Had some LeWa rom.. the CWM i had was supposed to do an automated Backup of the original OS, But it didn't, and i followed dixtra's flash and it bricked my cell phone.. so im out of a cell phone right now.. which annoys me,
the errors i got.. while trying to do a master reset. were
E; cannot open recovery/log cache,
E; cannot mount recovery/log cache,
i can get to the master recovery menu.. but it just gets a boot loop.
Anyone able to help? Either via Tviewer, or pointing me to a guide that will un brick the piece of crud?
Cyaneyed said:
How did you Brick it? what did you do to fix it? my thrill 4g is bricked, it happend to get bricked while trying to restore a stock rom..
Had some LeWa rom.. the CWM i had was supposed to do an automated Backup of the original OS, But it didn't, and i followed dixtra's flash and it bricked my cell phone.. so im out of a cell phone right now.. which annoys me,
the errors i got.. while trying to do a master reset. were
E; cannot open recovery/log cache,
E; cannot mount recovery/log cache,
i can get to the master recovery menu.. but it just gets a boot loop.
Anyone able to help? Either via Tviewer, or pointing me to a guide that will un brick the piece of crud?
Click to expand...
Click to collapse
Reflash kdz then do factory reset it will fix it
Sent from my LG-P925 using xda app-developers app
So I was trying to restore back to my stock ROM backup using the boot strap recovery. There weren't any errors during the process of restoring the image but when it was time to boot the phone up it would stay in a bootloop.
I have tried factory reset with the power button and volume buttons but it'd go straight back to the loop.
I am trying really hard to understand this whole adb thing with the sdk program but I have no idea how to use it.
Can anyone please help this noob?
Return to stock - Windows.
FAQ sticky in the Bionic Development forum.
Thanks for the reply. I'll try this out when I come home from work.
Also, I reactivated my droid x until then. Will I need to go to Verizon for a new sim card for my bionic once I can start it up again?
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
I believe you may have to go for a new SIM card. The way the Verizon explained it to me when I returned my Charge was when you deactivate from a 4G to 3G only phone, that SIM is lost. However, 4G to 4G is fine.
Wouldn't hurt to try, but a good possibility you will have to.
Sent from my DROID BIONIC using xda premium
idefiler6 said:
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
Click to expand...
Click to collapse
About 2 hours after I said this, I bootlooped. Good thing this FXZ method works!!
haha yeah with all the new roms u cant help but to explore.
btw after 5 FAILED flashes I tried one more time with rsdlite and it finally worked!
It took about 20-25 minutes for the whole process to fully boot up my phone but I am very happy and thankful for the people on this forum.
The weird thing is that when it booted up... it booted up to an old restore of UNL3ASH3D. confused but im happy its fully functioning.
You won't need a new SIM card. I did an FXZ restore after I rooted my phone, unrooted it (didn't need to have it rooted because there were no ROMs and no CWM yet) and it wouldn't let me root again so I flashed to stock and it rooted just fine. You will need to flash the radio again though (or at least I did after installing DroidTh3ory's ROM because it kept showing 3G in spots I know i had 4G, worked fine after I flashed).
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
patches0616 said:
Hi Guys,
I'm a noob so please send me in the right direction if I seem out of place. I have an Exhibit 4G that I managed to root. It was 2.3.6 I believe. All was great until I decided I wanted to change the operating system to a Peach Sunrise (I think) then it became stuck in a boot screen loop. I have tried resetting to factory but that doesn't help. I'm not too savvy with these phones so I'm stuck at a dead end. I'm looking for someone in the Atlanta area to fix it for me. I'm willing to pay. It was a brand new phone bought from an individual. It was only used about two week by me. Please let me know if you can help or have a relatively easy solution. Thanks in advance, Les
Click to expand...
Click to collapse
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
i bricked my phone
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
allenw420 said:
:i cant get in recovery mode i have bricked my phone i was puting a costum rom on my phone stuck in boot logo and odin is not working please help :crying
Click to expand...
Click to collapse
Do you have the right drivers? Just download Samsung kies and it should be fixed
Sent from my Nexus 7 using xda app-developers app
Dvarl said:
Is it the galaxy exhibit 4G T679? It the original exhibit? There are multiple phones with the same name. Also wiping cache/dalvik cache and fix permissions will usually fix a problem like this.
Sent from my SGH-T679 using xda app-developers app
Click to expand...
Click to collapse
Hi Dvarl,
I'm extremely sorry but I forgot to bookmark the sight and finally decided to search my laptop history to find the thread. The phone is the newer model SGH-T679 galaxy exhibit, not the exhibit II. I have tried wiping the cache but i'm not sure exactly how to proceed to do all the procedures that you are talking about. It does not have cwm installed. I did manage to root it before I got myself in this mess.
I can assure you I will be checking the replies frequently and any help is appreciated.
theAPANT said:
What do you mean by reset to factory? Wiping data does not change the operating system. However do you have cwm installed and yea is it even the t679
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
patches0616 said:
I would like to put it back to way it came out of the box or really I would like to have the newest OS on it. After that I think I could root it myself (after performing a backup). It does not have cwm installed on it. It is the newer 4G Exhibit not the exhibit II. Thanks for the reply and sorry I lost the forum and finally searched my history to find it.
Regards,
Les
Click to expand...
Click to collapse
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Wow that was a fast response! I have saved your link so I can try it. You are right, it is the renamed exhibit II. The startup screen used to say exhibit NOT exhibit II. I just wished I had backed it up before I made the big mistake. I have learned my lesson. I'll give it a shot tomorrow and let you know the results. Thanks again for your help, Les
I'm having the same problem. I tried odin but it's not working.. what am I missing?
What I do because it is much much faster IMHO, I would use Odin to put cwm back on the phone then download any ROM I want or the flash to stock, or even better if you followed the rules restore a nandroid
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
The t679 IS the exhibit 2 (although it was renamed the galaxy exhibit). The original exhibit aka just plain exhibit 4g t759 is the older model. It sounds like you have the t679 if that is correct, follow these instructions http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
Do not follow those instructions if you do not have that phone. Google if you are unsure about the phone you have because if done right for the right phone these steps are perfectly safe. If however you have the wrong phone you will ruin it pretty badly. On that cheerful note, good luck!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
patches0616 said:
I do have the renamed t679. I must be doing something wrong. First I put it into restore mode and clear the cache then restart in download mode. Then I start the Odin Multi Downloader (Ancora) and insert into the OPS field the Ancora.ops then insert into the One Package field the T679LG3.tar file then hit start until all automatically finishes.
I am still left with a phone in the boot logo loop. I noticed when I wiped the cache and restarted the phone script said something about " unable to mount \system .... I didn't take a snapshot so I'm not exactly sure of what it was but I know the phone will not start up if it can't mount the system partition, at least I think I saw that somewhere in a thread.
Any suggestions? I wish I knew someone around Atlanta that I could join up with and get this thing working. I loved this phone and only used it for about a week. I'm thinking before all this is over I will be a phone geek instead of a newbie. All the information that I have gotten here is super helpful, I just don't know enough to effectively utilize it.
Click to expand...
Click to collapse
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
theAPANT said:
OK now use the volume up and power to get to a screen with a box and then hit menu that will bring you to a recovery and just click wipe data factory reset and you should be fine.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
patches0616 said:
I've tried that more than ten times to no avail. I get the feeling that the original OS may be corrupt or missing or maybe that "unable to mount" message that I saw.
Click to expand...
Click to collapse
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Odon does the same thing to me, it says pass but still boot loops, that's why I recommend just doing cwm through Odin and flash the b2s or any ROM you desire
Sent from my SGH-T679 using xda app-developers app
theAPANT said:
OK well if it boots to the android icon with green fire or whatever then you have an os. My only advice is to make sure you check the right things when using Odin.
Edit: there is a very slim possibility that you have a fried emmc chip but I doubt it. Also make sure it says pass before you unplug
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:44 PM ---------- Previous post was at 09:20 PM ----------
How far do you boot to? How long does it take for Odin to finish?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
patches0616 said:
When I run the Odin Multi Downloader program it takes 5 mins and 38 secs to finish. The phone restore Odin is fairly fast when I reset to factory settings but I've never timed it. The phone boots to the t-mobile exhibit screen just beyond the plain white Samsung start up screen.
Click to expand...
Click to collapse
Hmm when I've done it it took about 10min, so perhaps the 300 sec reset option is not set. Try what tazmanion said by using Odin to flash cwm and then you can Mount system in revovery
If it doesn't get to boot animation then yea you have no os
Sent from my Nexus 7 using xda app-developers app
I'm also still having bootloop issues, I wiped cache/dalvik, fixed permissions, wiped battery stats, etc. but best it did was sit on the SAMSUNG for like 2 minutes then go back into a bootloop.
I'd like to keep the original rom/system in tact to not loose any data (didn't backup beforehand, I know...) anyone have suggestions?
Thanks in advance.
(yes this is crossposted, need answer asap, sorry)
You do not have a ROM if it sits in Samsung
Sent from my SGH-T679 using xda app-developers app
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Survivor058 said:
hey guys i tried searching for answers. but had no success. i have a note 3 that was rooted with kingo. AT&T automatically installed an OTA update and of course it un rooted my phone. i still get the custom boot screen as well as still have safestrap on my device. my question is how do i reroot my device? ive tried kingo again and it fails after rebootong the phone 5 or 6 times. im still running 4.3 build is JSS15J.N900AUCUBNB4
i know a little on some things but im not as technical as most of you. but any help would be greatly appreciated.
Click to expand...
Click to collapse
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
theorioles33 said:
What version of Kingo did you try? Use 1.1.5 or 1.1.8. People have had success with that. 1.1.8 worked for me. Just Google around and you will find the download on the net somewhere.
Click to expand...
Click to collapse
it was 1.2.0 ill try an older version
In case you have trouble finding a copy
https://mega.co.nz/#!AxdHUCCQ!86DzctSWlXK4VfbInPYBgC_4QYAM2wUR8cewrflAyk0
theorioles33 said:
In case you have trouble finding a copy
unfortunately that did not work. the root failed. that was version 1.1.5, last night i tried 1.1.8 failed and tried the latest 1.2.0 with no success. would you recommend something else? i did try theese root methods with the sd card inserted im not sure if that is a no no or not
Click to expand...
Click to collapse
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
I'm at a loss. I had my SD card in by the way. Maybe someone else will have some ideas.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
that sucks. factory reset? ill most likely still have the issue but maybe not. isnt there a way to completely wipe the phone from the boot screen? id rather not if i dont have to.
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
theorioles33 said:
You can try a factory reset and then root. If not there is a thread in the general section to go back to stock. Works great. I used it.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
but arent i technically back to stock? since i dont have root access? this is very confusing to me. if my carrier didnt push that update i wouldnt be in this boat
You are but we can't figure out why you can't root when others in your situation can. There is Kingo thread you can check out. Maybe you can find some answers there.
Sent from my SAMSUNG-SM-N900A using Tapatalk
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Survivor058 said:
anyone have any suggestions?? 139 views in less than an hour someone has got to know something lol
Click to expand...
Click to collapse
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
coolmingli said:
Factory Reset after the update to NB4, also go to recovery wipe cache, then try the 1.18, during the rooting process, look your phone screen, you need to click accept something twice,
Click to expand...
Click to collapse
ok yea this is all french to me. you want me to factory reset? im not sure what the NB4 is?. and i thing i know how to wipe the cache.
Gary3 said:
I don't know how it all works terribly well but you said you still have Safestrap? Can you still install ROMs and can they have root?
Also, for when you eventually do get it working again. I recommend freezing the ATT updater. It can be awful when it eventually FORCES an update.
I got a free app called App Quarantine and froze "AT&T Software Update".
Click to expand...
Click to collapse
safestrap is on my phone but it cant be removed and just says that the phone isnt properly rooted. so no i cannot install roms and i will make sure that once i resolve this ill freezr that app
sorry for the delay guys im back at this again. i do very much appreciate all who are trying to offer assistance
ok guys so ive wiped the cache. and have done the factory reset. kingo 1.1.5 and 1.1.8 both have failed...... what is going on here maybe someone can skype with me the steps to completely flash my phone to the day i got it i see the thread but im scared ****less to try it lol
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
You will just have to follow the restore to MJ5 thread. The instructions are simple and very easy to follow. Go slow and follow them to the T.
What they do not mention however is do not use a 3.0 USB port. Only 2.0 will work.
Just follow that.
It is literally impossible to brick this phone to the point of it being unrecoverable. There is a tutorial to restore from hard bricks without J-Tag.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
chrispyutec said:
Hey graydiggy, I did the restore back to MJ5, but can't seem to get the last step for rooting to work. I tried every way with putting the rdlv on internal...unzipped and zipped. I even tried doing the same on the external sd as well. When I reboot supersu doesn't do anything. Any suggestion on how to get the last step to work?
Thanks in advance for your help.
Click to expand...
Click to collapse
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
It has to be unzipped and on the internal. You have to reboot a few times for it to activate. After the first reboot, let the phone sit for a few minutes and then reboot again. You should be good to go after that.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wow that did the trick!!! Thanks for holding my hand lol. I hit your thanks and I appreciate your help.
Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?
you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app
From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device
Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app
I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?
jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk
Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk
Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048