What should we do? For myself at this moment, I do not need root or custom roms. I have read many people recommending staying on stock for OTAs updates right now. The only reason I want TWPR is for the nandroid backups of the stock rom. Is it even possible to update stock, the OTA updates and reapply the unlock bootloader and TWPR afterwards? I know TWPR is still being working on at this moment. Also, is there even a stock rom [for FRD-AL04???] without root available through TWPR right now?
I believe I have FRD-AL04 which is the US/32 gig phone, right? Is this the correct model? Here is the link to amazon page.
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
On whether to stay stock or not... it's up to you. I unlocked my phone, which wipes it, then installed TWRP and SuperSU for root. Kept the ROM stock. But then I realized I forgot to do OTA updates first. Doing a quick update failed because TWRP didn't know what to do. I then selected a "Full Update" in the menu of the Updater. This actually completely wiped out my unlocked bootloader, recovery and root in one swoop. So now I am back to stock it seems so I'll have to unlock and start over if I want to redo it. But I'm not sure I am going to. I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Stay on stock until company stops pushing out OTA updates. I do this on all my phones.
tekkitan said:
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
On whether to stay stock or not... it's up to you. I unlocked my phone, which wipes it, then installed TWRP and SuperSU for root. Kept the ROM stock. But then I realized I forgot to do OTA updates first. Doing a quick update failed because TWRP didn't know what to do. I then selected a "Full Update" in the menu of the Updater. This actually completely wiped out my unlocked bootloader, recovery and root in one swoop. So now I am back to stock it seems so I'll have to unlock and start over if I want to redo it. But I'm not sure I am going to. I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Click to expand...
Click to collapse
Few questions if you don't mind.
1. Are you saying that even with unlocked bootloader and custom recovery you're still able to accept the OTA?
2. How would you restore the apps&data after accepting the OTA and going throu the unlocking/rooting process over again? Does Helium handle this w/o problems?
Thanks.
well, your question is complicated... but it has many type of sollutions
1.if its the nandroid backup is the only thing you want, then try backing up via honorsuit app,,
2.you can unlock the bootloader( dont worry you still be getting updates after this)
install twrp
make a backup
and find if someone did a backup with stock recovery
grab it
restore..
now you have your backup and youl be elligable for ota
3. if theres no one done a backup of stock recovery, dont worry... you can do it
unlock bootloader
now type fastboot devices
fastboot boot recovery twrp.img
this will temperorily boot twrp and you can have your backup
and BTW, you better be on stock, because, there is no stable custom rom yet and you are nearly getting a nougat update..:good:
mimin0 said:
Few questions if you don't mind.
1. Are you saying that even with unlocked bootloader and custom recovery you're still able to accept the OTA?
2. How would you restore the apps&data after accepting the OTA and going throu the unlocking/rooting process over again? Does Helium handle this w/o problems?
Thanks.
Click to expand...
Click to collapse
1. Yes, but only if you select the FULL download update in the menu of the updater (which says it's around 1.6GB). This will wipe out your unlock, TWRP and root though. At least it did for me.
2. I don't know, I didn't re-unlock it because it was going to wipe my phone again. I decided to stay stock for now using Helium backup to backup my apps, SMS, etc.
tekkitan said:
Mine is the US 32gb black Honor 8 and model number is FRD-L04
Edit: Check your model number in the Settings > About Phone screen.
---------- Post added at 04:30 PM ---------- Previous post was at 04:22 PM ----------
I started using Helium made by the team that made ClockworkMod. It isnt able to back up ALL app data, but it does get a nice chunk of it which I think will be good enough for me for now.
Click to expand...
Click to collapse
I can't even get Helium to get past asking me for PTP mode on my H8. Even though I select PTP in the notifications and/or in the dev settings.
scoobydu said:
I can't even get Helium to get past asking me for PTP mode on my H8. Even though I select PTP in the notifications and/or in the dev settings.
Click to expand...
Click to collapse
I also had this problem at first. I ended up having to switch from using their chrome add-on to installing the client for my OS (OS X in my case). So if you're using the chrome add-on try installing one of the clients instead.
tekkitan said:
I also had this problem at first. I ended up having to switch from using their chrome add-on to installing the client for my OS (OS X in my case). So if you're using the chrome add-on try installing one of the clients instead.
Click to expand...
Click to collapse
Ok thanks, but I am already using the OSX app myself. Managed to get it to work just now, had to reboot and now can't get it to work again. Some say to select 'midi' instead of ptp to get it to work, but that doesn't work for me either. Seems its a timing thing and I have't worked it out yet.
Not having a cross platform backup mechanism certainly doesn't help people stay stock without root imho.
Related
Hi guys. I want to know how to do what the title says cause the new update sucks really bad. Games fps is lower, can't use SD card anymore, full screen is not really full screen anymore. Well yeah thanks
ALLEN2 said:
Hi guys. I want to know how to do what the title says cause the new update sucks really bad. Games fps is lower, can't use SD card anymore, full screen is not really full screen anymore. Well yeah thanks
Click to expand...
Click to collapse
GO here http://forum.xda-developers.com/showthread.php?t=2661067
Follow the instructions on getting the bootloader unlocked and getting rooted by flashing CWM.. after all those steps. re open the program and choose Flash BONE STOCK. You will be right back in Android 4.3 update 68 i think from Nvidia. which is right back to when you purchase it from Gamestop. Get it quick before the developer update it to The latest update which is the one your on, 4.4.2.
As long as you follow the instructions and get the Universal Ghost Driver installed properly. It works. I've tried this out already, I em back on Android 4.3..
DJFresh82 said:
GO here http://forum.xda-developers.com/showthread.php?t=2661067
Follow the instructions on getting the bootloader unlocked and getting rooted by flashing CWM.. after all those steps. re open the program and choose Flash BONE STOCK. You will be right back in Android 4.3 update 68 i think from Nvidia. which is right back to when you purchase it from Gamestop. Get it quick before the developer update it to The latest update which is the one your on, 4.4.2.
As long as you follow the instructions and get the Universal Ghost Driver installed properly. It works. I've tried this out already, I em back on Android 4.3..
Click to expand...
Click to collapse
Alright, do I loose all my data and is there I way I can update to the update before this 4.4.2 update?
Note CMW development its dead and dont know what happens if you install CMW recovery on kiktat,try to install another recovery.
ALLEN2 said:
Alright, do I loose all my data and is there I way I can update to the update before this 4.4.2 update?
Click to expand...
Click to collapse
unfortunately you will lose everything if you go through with this method unless most of your personal stuff is on the MicroSD Card, as it reflashes your original clean untouched recovery... Maybe in the near future there might be another simpler method.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
alexei_gp said:
Note CMW development its dead and dont know what happens if you install CMW recovery on kiktat,try to install another recovery.
Click to expand...
Click to collapse
It boots up to CWM and it seems to be working normal as far as doing a nandroid backup to MicroSD.. I haven't encountered any issues yet when i had KitKat.. I had the CWM running normal as far as I can tell. Well i'm still sort of a newbie, here you guys are the experts..... thanks for the great dev for another great device
DJFresh82 said:
unfortunately you will lose everything if you go through with this method unless most of your personal stuff is on the MicroSD Card, as it reflashes your original clean untouched recovery... Maybe in the near future there might be another simpler method.
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
It boots up to CWM and it seems to be working normal as far as doing a nandroid backup to MicroSD.. I haven't encountered any issues yet when i had KitKat.. I had the CWM running normal as far as I can tell. Well i'm still sort of a newbie, here you guys are the experts..... thanks for the great dev for another great device
Click to expand...
Click to collapse
I m not a dev xDDD when i install CMW recovery on my nvidia shield i have problems to update to 4.3 .Searching on the thread of CMW i realize the CMW recovery its dead , no update no oficial development nothing and the worse you cant download the recovery on that thread,
alexei_gp said:
I m not a dev xDDD when i install CMW recovery on my nvidia shield i have problems to update to 4.3 .Searching on the thread of CMW i realize the CMW recovery its dead , no update no oficial development nothing and the worse you cant download the recovery on that thread,
Click to expand...
Click to collapse
Even though CWM is dead. in order to root using the Shield 1.0 method, CWM is still needed to flash SuperSU.zip.. unless you another method to root, the CWM isn't nessessary to flash. as long as you boot loader is unlocked of course and your rooted. you can use the Bone Stock method, and it will restore the shield back to 4.3.... this is the only way i know of as of now... I'm sure in the near future there might be another simpler method...........
DJFresh82 said:
Even though CWM is dead. in order to root using the Shield 1.0 method, CWM is still needed to flash SuperSU.zip.. unless you another method to root, the CWM isn't nessessary to flash. as long as you boot loader is unlocked of course and your rooted. you can use the Bone Stock method, and it will restore the shield back to 4.3.... this is the only way i know of as of now... I'm sure in the near future there might be another simpler method...........
Click to expand...
Click to collapse
I dont need to use the script SHIELD 1.0, i used minimal adb fastboot to root it using a image root on github,CWM its not required to flash SuperSU.zip
Once you're on kitkat I dont think you can go back to jellybean. I could be totally wrong but I tried going back to 4.3 and it bricked my shield, wouldn't boot. I didn't spend much time on seeing why it happened, so like I said I Could be totally wrong. I could of had bad files for all I know.
alexei_gp said:
I dont need to use the script SHIELD 1.0, i used minimal adb fastboot to root it using a image root on github,CWM its not required to flash SuperSU.zip
Click to expand...
Click to collapse
I didn't say u had to use that SHield 1.0 method to root, I said only if your using that method. I know there are other methods to root. The point I was making is that once your rooted and bootloader unlocked. you can still use shield 1.0 to reflash the update 68 i beleive which is android 4.3.. out of the box state from gamestop.... It worked for me having the same latest kitkat OTA that you have......
---------- Post added at 08:43 PM ---------- Previous post was at 08:31 PM ----------
hexitnow said:
Once you're on kitkat I dont think you can go back to jellybean. I could be totally wrong but I tried going back to 4.3 and it bricked my shield, wouldn't boot. I didn't spend much time on seeing why it happened, so like I said I Could be totally wrong. I could of had bad files for all I know.
Click to expand...
Click to collapse
It does seem like that.. but using SHIELD 1.0.. it worked for me, I'm back on 4.3 update 68 from NVIDIA. Using this mainly for emulators.. I'm sure there will be some type of fix in the near future for kitkat though, when it is, i will update mines back to that...
DJFresh82 said:
I didn't say u had to use that SHield 1.0 method to root, I said only if your using that method. I know there are other methods to root. The point I was making is that once your rooted and bootloader unlocked. you can still use shield 1.0 to reflash the update 68 i beleive which is android 4.3.. out of the box state from gamestop.... It worked for me having the same latest kitkat OTA that you have......
---------- Post added at 08:43 PM ---------- Previous post was at 08:31 PM ----------
It does seem like that.. but using SHIELD 1.0.. it worked for me, I'm back on 4.3 update 68 from NVIDIA. Using this mainly for emulators.. I'm sure there will be some type of fix in the near future for kitkat though, when it is, i will update mines back to that...
Click to expand...
Click to collapse
Ok thats good to know i used fastboot to flash the update 68 files.
you are soo wrong, you arent briked
just set up the ghost drivers on your computer, get fastboot working, download kwonggers toolkit, follow the instructions on screen of your computer to set your shield back to 4.2.2 because the toolkit hasn't been updated and everthing shield is almost as dead as the ouya or worse, so I might just sell the shield from the lack of audience and support and get a bloody snapdragon 801 phone, if NVidia wants to keep this relevant, they need to work with the developer community more, unless shield will die, I have made my choice, now what's yours?
hexitnow said:
Ok thats good to know i used fastboot to flash the update 68 files.
Click to expand...
Click to collapse
That's Awesome.....
mudflap2.0 said:
just set up the ghost drivers on your computer, get fastboot working, download kwonggers toolkit, follow the instructions on screen of your computer to set your shield back to 4.2.2 because the toolkit hasn't been updated and everthing shield is almost as dead as the ouya or worse, so I might just sell the shield from the lack of audience and support and get a bloody snapdragon 801 phone, if NVidia wants to keep this relevant, they need to work with the developer community more, unless shield will die, I have made my choice, now what's yours?
Click to expand...
Click to collapse
I just got the Shield mainly for emulators, so will stick with 4.22 since that is what the device had out of box. Works great and no need to root or any other hassle for the intended use.
I am helping a person try and retrieve photos from a Samsung Galaxy S6 that is stock at the lock screen. The finger print scan is not working and they do not know there back up password. I researched two ways to get around this.
1. Entering in the google account user name and password
2. Signing into Find My Mobile with the samsung account information and unlocking the phone
If both of these options fail due to the owner not remembering there above credentials is there any other way to retrieve photos. How about putting the phone in dfu mode and using a program on a computer to copy photos from the internal storage. Is something like this possible? Appreciate any help on this issue.
Maybe flash a stock ROM with Odin?
That way all the data stays in tact and it may remove lock screen.
Sent from my SM-G920I using XDA Premium HD app
Thanks for the quick response. The lady is paranoid about losing her photos! Therefore flashing with Odin Stock Rom will not remove any data from the phone. Do you have instructions or a link on how to do this.
I also am able to sign into her google account through the web browser, but when I use those credentials to try and unlock the Galaxy S6 it says that the user name or email is wrong. Thanks
Obagleyfreer said:
Maybe flash a stock ROM with Odin?
That way all the data stays in tact and it may remove lock screen.
Sent from my SM-G920I using XDA Premium HD app
Click to expand...
Click to collapse
Sounds like she could be learning a hard lesson. Backup passwords, knowing what accounts you used to setup, photo backups all exist for a reason.
krelvinaz said:
Sounds like she could be learning a hard lesson. Backup passwords, knowing what accounts you used to setup, photo backups all exist for a reason.
Click to expand...
Click to collapse
I totally agree with your assessment! I don't understand how I can log into her Gmail account via the web and then when I enter the same information at the Galaxy S6 Unlock via Google it does not work. Could this have something to do with not being connected to the internet. It is saying that 4G LTE is connected. Doesn't seem to be a way to connect it to WiFi without unlocking home screen.
If this was my phone I would have no trouble trying to flash the Odin stock Rom, but do not want to lose her info incase someone else can retrieve it. Does flashing the Odin stock ROM wipe everything on the phone or does it retain photos and other information. Thanks
I'm in this same situation. Is there anyway to retrieve the pictures? Flashing with Odin does not wipe the phone?
Wasn't life easier when we had removable sd cards...?
Flashing the system partition does not touch the data partition.
Do you know how she managed to break the fingerprint reader, by the way?
My G920F stuck on bootloop because of fail on rooting and I was afraid of losing all my photos. First I flashed TWRP with Odin, booted to recovery mode and pulled photos and videos out with adb. Then I flashed stock firmware with Odin and made a factory reset (not mandatory). Everything is working fine now.
dsimpe said:
My G920F stuck on bootloop because of fail on rooting and I was afraid of losing all my photos. First I flashed TWRP with Odin, booted to recovery mode and pulled photos and videos out with adb. Then I flashed stock firmware with Odin and made a factory reset (not mandatory). Everything is working fine now.
Click to expand...
Click to collapse
I suppose doing this you had USB debugging ENABLED before the boot-fail? Or does it turn on USB debug when flashing TWRP?
---------- Post added at 01:49 PM ---------- Previous post was at 01:43 PM ----------
WahFai said:
Wasn't life easier when we had removable sd cards...?
Flashing the system partition does not touch the data partition.
Do you know how she managed to break the fingerprint reader, by the way?
Click to expand...
Click to collapse
Agree WahFai, much simpeler with SD-card! So you think flashing system partition will do the trick. I'll go read up on that, how to flash the system partition. In my case, afaik, the fingerprint reader did not break. The system failed accepting the unlock code from one day to another and she does not remember the backup code for the reader. Thanks for your reply!
All she wants are the pictures on the phone. She recently got a baby, all the pictures of the delivery are on the phone, so you sense the urgency to not loose the pictures. She'll still feel the effects 18 years from now.
By the way: does flashing the stock rom with odin void the warranty? Because the phone is still on warranty...
Flashing a stock rom via odin will not trip knox but flashing a custom recovery will.
Thanks for clearing that out for me.
WahFai said:
Flashing a stock rom via odin will not trip knox but flashing a custom recovery will.
Click to expand...
Click to collapse
---------- Post added at 03:32 PM ---------- Previous post was at 02:58 PM ----------
EDIT:
So I'm downloading the stock firmware right now. Still a question: I'm not sure which firmware is on the phone right now. Is it a problem if I flash a newer, say the newest available, stock firmware on the phone?
Go on samsung kies and back up the phone and the photos come up
Sent from my SM-N910V using XDA Free mobile app
madchainsawer said:
Go on samsung kies and back up the phone and the photos come up
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
The phone is locked out, it does not show up on Kies. Actually it does show, but says its locked.
Ok, I now flashed the stock ROM again. It still comes back on the locked screen. HELP!!
bronxboy1 said:
Ok, I now flashed the stock ROM again. It still comes back on the locked screen. HELP!!
Click to expand...
Click to collapse
At this point, it sounds like flashing a custom recovery (TWRP) is your only option.
dsimpe said:
My G920F stuck on bootloop because of fail on rooting and I was afraid of losing all my photos. First I flashed TWRP with Odin, booted to recovery mode and pulled photos and videos out with adb. Then I flashed stock firmware with Odin and made a factory reset (not mandatory). Everything is working fine now.
Click to expand...
Click to collapse
Hey dsimpe, I am willing to try this option, since I cannot acces de mediafiles after flashing the stock ROM. Can you confirm this will trip Knox? And I installed ADB Studio. I cannot find a simple explanation on how to pull de media with adb. Can you help me please?
---------- Post added at 03:22 PM ---------- Previous post was at 03:20 PM ----------
Sevael said:
At this point, it sounds like flashing a custom recovery (TWRP) is your only option.
Click to expand...
Click to collapse
I just saw your post Sevael. I recon this is my only option now. I need to figure this out to pull the media, after that I can do a factory reset or whatever, but I never used ADB before. Thanks for your reply.
bronxboy1 said:
Hey dsimpe, I am willing to try this option, since I cannot acces de mediafiles after flashing the stock ROM. Can you confirm this will trip Knox? And I installed ADB Studio. I cannot find a simple explanation on how to pull de media with adb. Can you help me please?
Click to expand...
Click to collapse
Check droidviews article of "How to Push and Pull Files on Android using the ADB commands".
I'm pretty sure that knox will be tripped.
Also go to my profile and check thread that I've started. I explain there how I did it.
If you've any problems post here or pm me.
I now found the instructions on how to pull files with ADB. I connected the phone to my pc and checked if the device was recognized. This was not the case. Does this mean, that the USB debugging was not enabled?
Edit: Thanks dsimpe. Saw the post too late again. Note to self: need to refresh page before making a reply... I'll go check out your posts. Thanks again.
bronxboy1 said:
I now found the instructions on how to pull files with ADB. I connected the phone to my pc and checked if the device was recognized. This was not the case. Does this mean, that the USB debugging was not enabled?
Edit: Thanks dsimpe. Saw the post too late again. Note to self: need to refresh page before making a reply... I'll go check out your posts. Thanks again.
Click to expand...
Click to collapse
My device wasn't recognized either before I flashed TWRP with Odin and I booted to recovery mode.
Ok, tnx dsimpe. I guess USB debugging must have been turned on before also on the phone? And can you confirm knox will be tripped?
Verstuurd vanaf mijn GT-N7100 met Tapatalk
Every guide I read about installing TWRP it tells me I have to format data or I will receive error about not being able to access internal data.
Is it possible to root the device without installing TWRP?
I don't want to format my phone, I have spent many many hours setting the device up. I just want to have root on it. Not experiment with different roms.
Please?
Forgot to mention. My bootloader is already unlocked. I had TWRP before but decided to completely restore my phone to update to latest C432B170 build so now it's completely stock again except for the unlocked bootloader.
Is there anyway to root mate 8 without losing/formatting data?
Can you provide me the C432 rom that you used for going back to stock please?
---------- Post added at 09:29 PM ---------- Previous post was at 09:23 PM ----------
its available for download in the huawei ota server link thread
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
Ah o.k. thanks. I own a NTX-AL10 Cinese version and I can't get it then. I like to go to European rom. For the moment I already made it International though ( More or less) ?. I still could use the proper image files. In fact the recovery of your phone would do?
I believe, if you make a backup (with provided program) to your sdcard you can restore all settings and homescreen icons. I made the backup already but as long it's not necessary I don't try to recover from it ?
Anyone?
I want to root but I don't want to lose the settings/apps on my phone. Please help
Samiii2 said:
Anyone?
I want to root but I don't want to lose the settings/apps on my phone. Please help
Click to expand...
Click to collapse
No way. Deal with it.
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...