I've bent trying to update nut oneplus one from 33r to 38r but I seem to be missing this file and maybe others
http://i.imgur.com/PzTro2w.jpg
Could someone please upload that file from 33r?
Yeah you've removed/modified system files, OTA updates fail if you've done that. Get the recovery flashable version from here And flash it.
Transmitted via Bacon
Yeah I deleted a few 'indeed apps'
Will do a nandroid backup and try that update
Which do I download and flash? I don't wanna lose my data also? :/
You want the signed flashable 38R zip. You can try dirty flashing (only wiping cache and dalvik cache), but you might have problems, in which case you'll need to fully wipe (system/data/cache/dalvik cache) and clean flash.
Transmitted via Bacon
is there no way to do this without losing my data? With just the update file and not the full install like an ota update?
I just said you could try dirty flashing, that's flashing without losing data.
Transmitted via Bacon
But that'll be with the full install file and not the smaller update right?
Yeah, that's right, why does that matter?
Transmitted via Bacon
I don't want to do a full 'dirty' install I just want to apply the small update
It's essentially the same thing, do you not realise that? The only way you can use the OTA update is if you fully wipe and go back to stock first. If you want to keep your data you need to use the full ROM zip. Maybe it's time to do a bit of reading so you have a better idea of what you're doing.
Transmitted via Bacon
But I'm on stock? I'm just missing a few files can't I just replace them as I just wanna update via ota
If you think you know better and know what you're doing, go ahead. You came here looking for help, it's not much use trying to help you if you're just going to argue with the advice you're being given. It's not my fault you haven't properly researched all of this and don't have a firm grasp on what I'm talking about.
I know what I'm talking about here. The solution I'm giving you is the easiest solution for you, all it's going to do is flash the updated ROM over the top of your existing ROM, everything will be exactly the way it is now still, all of your apps, all of your settings, everything, the only difference being that you will have successfully updated. I can't comprehend why you'd just argue with someone who's attempting to help you.
Transmitted via Bacon
Wow why you you have such a problem with me? At what point am I arguing with you? All I'm doing is asking for help and making suggestions?
steve51184 said:
Wow why you you have such a problem with me? At what point am I arguing with you? All I'm doing is asking for help and making suggestions?
Click to expand...
Click to collapse
I don't have a problem with you, I only have a problem with giving time out of my day trying to help someone who is constantly questioning the good advice he's being given. You came here seeking assistance from someone with experience, because you don't really know what you're doing, it doesn't make sense that you're second guessing someone who has knowledge of all this. My advice is to take in what I'm saying because I'm offering you the easiest, most efficient, and effective solution for your needs.
Transmitted via Bacon
Not questioning just double checking and making other suggestions (hey we all start to lern somewhere right?)
I'm very sorry if it came over wrong and I really appreciate the help you've given you far
One last question so I don't make a mistake could you link me to the exact zip fileI need to fish please?
Thanks again and very for the confusion my friend
steve51184 said:
Not questioning just double checking and making other suggestions (hey we all start to lern somewhere right?)
I'm very sorry if it came over wrong and I really appreciate the help you've given you far
One last question so I don't make a mistake could you link me to the exact zip fileI need to fish please?
Thanks again and very for the confusion my friend
Click to expand...
Click to collapse
No problems, sorry that I misinterpreted your curiosity. We certainly do all need to start learning somewhere. The file you want is here:
https://www.androidfilehost.com/?fid=95747613655046955
Just download it and put it on your phone, boot into TWRP and hit the install button from the main menu, navigate to where you have the zip stored and select it, then swipe to install. Just wipe cache and dalvik cache after the install.
This is going to reinstall those apps that you removed previously, maybe instead of fully removing them again you could use Titanium Backup to freeze them instead, that way the next time there's an OTA all you need to do is temporarily unfreeze them to take the OTA without any hassle.
Transmitted via Bacon
Related
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Please be sure and thank the person who decides to do your homework for you.
:laugh:
FlynnErik said:
First off love the N00b video at sign up that was hysterical, nice work to whoever made it.
Ok on to what I need to know:
I understand HOW TO root/flash a rom, my issue is kind of different than most peoples. I have scoured the web and this site for the files I need to accomplish this with my GT-P3113 build ending in LG5 however I am confused to hell.
1 place will say that CWM 6.0.1 is not usable on my device, another will say that it works fine and another will say to use TWRP (which might I add looks cool to use). Some will say that I need the expresso_wifi file to root my device, others will say use update.zip, and others will say a totally different file all together.
I know what ROM to get, I understand the steps:
Download drivers
Boot to download
use odin to install CWM
back up everything with CWM (which goes to the MicroSD I am guessing? since I wipe the device in a later step)
wipe the device
wipe the cache
wipe the Dalvik cache
flash the rom
flash the root
is all that correct? (just to make sure I got it right) so my biggest question is, which files do I really use? There is a thread from back in June before the 4.0.4 update OTA came through) saying to use instead of that if you have LG3 or etc.
Help would be greatly appreciated, I am a smart guy, just want to have my facts straight before I make this happen.
PS sorry if this is in the wrong place, figured this was the best place for it.
Click to expand...
Click to collapse
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
ryphil said:
From someone relatively new to this as well, this is basically correct. Here are some tips from someone who has recently done it.
Make a backup.
Research the files you intend to flash, make sure they are right for your device
Verify the guide you are using has been tested and known to work.
This may seem elementary, but I didn't follow #3 and it cost me a lot of headache un-bricking my SGT 2.
Click to expand...
Click to collapse
Fully agreed! That's why I came to the experts. I have done my homework but the thing is my homework leads me to several different files from before the ICS update. There has only been 1 thread on 1 forum that has been post ICS update, and no real feedback on it. I think I even found one that uses ADB (I understand that concept, but would prefer not to use it since I don't know Linux well enough).
I would love to know what files to use, which ones to stay away from. As I said I have the concepts, I have the understanding, its the actual files that I want to verify, I can rattle off tons of files from tons of sites, but they may or may not be correct (and may have the same name as a correct one but still be incorrect, ie "update.zip" appears a few times on different threads from different time frames).
There is only post in the teamhacksung CM10 wiki that was last edited 8/12/2012, but that could have been anything that was updated, not the files/links to be used.
So I thank you in advance for your help, and you will certainly get a thank you in the forum for help you are providing, I always give credit where credit is due.
Well here goes nothing, going to reboot (to ensure the Kies drivers are installed and loaded into the system 100%), and try the instructions from this link http://forum.xda-developers.com/showthread.php?t=1788625
It seems to work for most, the only concern I have is that I have a different end to the build than most others do (and I am not sure why?)
Did I screw myself?
I rooted, and have CWM installed.
Is it to late to create a ROM backup of my device for when i go to install CM10 (I need a drink for now, so I might install it tomorrow night lol).
That link I posted in the last post is good to go if anyone else needs a safe bet set of directions.
Seriously though, I didn't do a backup, am I screwed now?
EDIT: I just did a back up and it said no sdcard/.android secure found, skipping of backup of apps
and
no sd-ext found skipping backup of that.
is that normal? Did it backup to my microSD?
Still hope I didn't screw myself by backing it up after rooting.
Hello,
I recently hopped over from stock to Paranoid Android 4 Beta (0).
This is my first experience messing around with the backend of Android, but I did jailbreak my iPhone a few times, I'd hope that helps my comprehension of all of this.
I currently have the Paranoid OTA installed, and it's telling me there are new versions,
I've downloaded the files and they are on the phone, but whenever I install it restarts and nothing happens. It stays on the current version, I'm doing the
I've been ticking to Backup, wipe the data, cache and dalvik but not the systen.
When it boots back up (it's instant, I'm still on beta(0).
Any help or guidance is appreciated, sorry if this is the wrong place!
phntem said:
Hello,
I recently hopped over from stock to Paranoid Android 4 Beta (0).
This is my first experience messing around with the backend of Android, but I did jailbreak my iPhone a few times, I'd hope that helps my comprehension of all of this.
I currently have the Paranoid OTA installed, and it's telling me there are new versions,
I've downloaded the files and they are on the phone, but whenever I install it restarts and nothing happens. It stays on the current version, I'm doing the
I've been ticking to Backup, wipe the data, cache and dalvik but not the systen.
When it boots back up (it's instant, I'm still on beta(0).
Any help or guidance is appreciated, sorry if this is the wrong place!
Click to expand...
Click to collapse
I´m guessing you have a custom recovery installed?.
Get the latest paranoid update from HERE and the latest gapps from HERE.
Boot into recovery and flash ROM GAPPS and if necessary SuperSU and then reboot. Should work.
lichti1901 said:
I´m guessing you have a custom recovery installed?.
Get the latest paranoid update from [removed] and the latest gapps from [removed]
Boot into recovery and flash ROM GAPPS and if necessary SuperSU and then reboot. Should work.
Click to expand...
Click to collapse
Hi there Litchi,
Thanks for posting.
I'm so bad at this stuff, I used the Nexus Root Toolkit by WugFresh. I really am a bit clueless on what custom recoveries have been installed. What I can tell you is that I have Paranoid Android 4 Beta with the corresponding GAPPS.
I tried doing Clockword Mod for backups but eventually just stopped trying, and used the backup provided in the toolkit (nandroid I think).
I installed the Paranoid OTA hoping that it would take care of me having to do it through my PC again since the drivers were such a mess last time.
Could you just provide a bit more detail as to the steps I'd need to take for that? I hate being so illiterate at this stuff.
Really appreciate any more help you can give! Thanks.
phntem said:
Hi there Litchi,
Thanks for posting.
I'm so bad at this stuff, I used the Nexus Root Toolkit by WugFresh. I really am a bit clueless on what custom recoveries have been installed. What I can tell you is that I have Paranoid Android 4 Beta with the corresponding GAPPS.
I tried doing Clockword Mod for backups but eventually just stopped trying, and used the backup provided in the toolkit (nandroid I think).
I installed the Paranoid OTA hoping that it would take care of me having to do it through my PC again since the drivers were such a mess last time.
Could you just provide a bit more detail as to the steps I'd need to take for that? I hate being so illiterate at this stuff.
Really appreciate any more help you can give! Thanks.
Click to expand...
Click to collapse
You really need to read the sticky at the top of this forum called [FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★
It gives you all the information you need to know. We pretty much all here advise against using toolkits for the exact reason in your post, it leaves you knowing nothing about your system, what you have got or the knowledge to use it. These toolkits are seen as a shortcut, but please be aware, there are NO shortcuts
Please read through that thread a few times. Don't flash anything else until you understand the process, what you have got and how to use it. Please don't take this the wrong way but you are not ready to flash things yet. Even if you have already flashed something, there are holes in yoru knowledge that can have disastrous consequences.
rootSU said:
You really need to read the sticky at the top of this forum called [FAQ] [REF]★ All you need to know about Android | Read this before you post/root ! ★
It gives you all the information you need to know. We pretty much all here advise against using toolkits for the exact reason in your post, it leaves you knowing nothing about your system, what you have got or the knowledge to use it. These toolkits are seen as a shortcut, but please be aware, there are NO shortcuts
Please read through that thread a few times. Don't flash anything else until you understand the process, what you have got and how to use it. Please don't take this the wrong way but you are not ready to flash things yet. Even if you have already flashed something, there are holes in yoru knowledge that can have disastrous consequences.
Click to expand...
Click to collapse
None taken,
Thanks for the help SU! I never really checked out this website, but I had seen the name around.
Appreciate the link.
Does anyone know why the Paranoid OTA application ITSELF isn't doing the work for me though?
phntem said:
None taken,
Thanks for the help SU! I never really checked out this website, but I had seen the name around.
Appreciate the link.
Does anyone know why the Paranoid OTA application ITSELF isn't doing the work for me though?
Click to expand...
Click to collapse
It may be an issue with the CWM recovery which is what I assume you have installed with the toolkit, as thats about standard...
In android, /sdcard on the nexus 5 isn't actually an /sdcard. /sdcard is actually /data/media/0 so whenever you are looking in what you think is in /sdcard, you're not... it's /data/media/0. It's been like this since 4.2 Jelly Bean, when multiuser support was added to android. The theory is there will be multiple /sdcards, for each user that logs in. The default user is use "0". With me so far?
Before multi-user support, /sdcard for devices with no physical sdcard, was simply /data/media. Now, CWM never bothered to update it's code to point to /data/media/0, so even today, basic CWM doesn't know the full location of your /sdcard. If the updater downloads the files to /sdcard (which it should), then tells CWM to look in /sdcard for the files to flash, the files cannot be seen because CWM is looking in the wrong place.
Essentially, you should look at ditching CWM and it's antiquated configuration in favour of Philz Recovery or TWRP. Both use /data/media/0 correctly as /sdcard
rootSU said:
It may be an issue with the CWM recovery which is what I assume you have installed with the toolkit, as thats about standard...
In android, /sdcard on the nexus 5 isn't actually an /sdcard. /sdcard is actually /data/media/0 so whenever you are looking in what you think is in /sdcard, you're not... it's /data/media/0. It's been like this since 4.2 Jelly Bean, when multiuser support was added to android. The theory is there will be multiple /sdcards, for each user that logs in. The default user is use "0". With me so far?
Before multi-user support, /sdcard for devices with no physical sdcard, was simply /data/media. Now, CWM never bothered to update it's code to point to /data/media/0, so even today, basic CWM doesn't know the full location of your /sdcard. If the updater downloads the files to /sdcard (which it should), then tells CWM to look in /sdcard for the files to flash, the files cannot be seen because CWM is looking in the wrong place.
Essentially, you should look at ditching CWM and it's antiquated configuration in favour of Philz Recovery or TWRP. Both use /data/media/0 correctly as /sdcard
Click to expand...
Click to collapse
Awesome thanks for the patience and information.
Should I unroot and go back to stock via the toolkit, essentially resetting it all?
That's about the last question I have for you,
Appreciate the help!
phntem said:
Awesome thanks for the patience and information.
Should I unroot and go back to stock via the toolkit, essentially resetting it all?
That's about the last question I have for you,
Appreciate the help!
Click to expand...
Click to collapse
Nope. I would read that thread to understand the process and then download one of the alternative recoveries and get yourself to the point where you can fastboot flash the recovery
phntem said:
Awesome thanks for the patience and information.
Should I unroot and go back to stock via the toolkit, essentially resetting it all?
That's about the last question I have for you,
Appreciate the help!
Click to expand...
Click to collapse
Please forget the toolkit!
The only thing you need is fastboot.
download TWRP or CWM recovery.img and flash it in fastboot. Boot into bootloader, connect the device with usb cable to PC, open cmd in windows and type following:
fastboot devices Enter ... that should give you a number, means your device is connected
fastboot flash recovery nameofrecovery.img Enter .... that will flash the recovery of your choice to your device. Then from bootloader you can select with volume up + down to boot to recovery. Do that - in recovery you can select what you want to do. Flash rom + gapps + supersu and you are ready to go.
Here is a good link for learning how to use fastboot. beginners-guide-on-how-to-setup-and-use-fastboot/
Learning fastboot is highly recommended - its the same what fastboot does, with 1 difference --> you know what you do
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Exactly which zip files are you trying to flash? What are the filenames?
Transmitted via Bacon
use a toolbox and an option to flash to stock
gfusion said:
Hi
I accidentally deleted with TWPR the system of my OnePlus One and it seems I cannot install a new rom.
I downloaded gapps and the original Oneplus One rom (zip) file and also the android stock. None of them works. It seems I need a
different format/special rom do recover from this. To make things more complicated I have a Mac and most instructions I've found are for windows.
Is there any rom I can transfer after mounting and flash via TWPR? I don't know much about android development so I appreciate technical details in replies.
Thanks!
Click to expand...
Click to collapse
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
playya said:
i assumed you fixed this since we have not heard back from you. Just an fyi - can you at least let people in your thread trying to help know you have been successful in doing what it is you were trying to do.
If not then simple download any rom transfer to your phone and flash it with TWRP and thats it. May I also suggest you dont use a toolkit since it will not give you the knowledge to fix your phone in the future
Click to expand...
Click to collapse
gfusion said:
Indeed, i fixed it last night. Thank you very much.
It was too late for me to be able to do the captcha (actually, even now it's difficult).
I was using the Mac OnePlus One toolkit which is a real life safer. I already learned quite a bit but I was grateful to have the support of the toolkit. There are quite some hoops to jump through and I needed to use fastboot. Due to some reason I wasn't able to just flash a rom.
Cheers
Gfusion
Click to expand...
Click to collapse
Here's a hint. Fastboot IS how you flash a new room for the first time had you not used the tool kit you would have seen this and done it that way lol
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!
Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon
conversation moved from LineageOS ROM thread.
bhishmar said:
I have a question to the experts here.
The official Lineage-OS-Wiki site has a page: "Manually Upgrading LineageOS" :
https://wiki.lineageos.org/upgrading.html
Can you explain whether this site is talking about:
a) "Updating" from an existing LOS-14.1-ROM to a new nightly-LOS-14.1 (Dirty-flashing)?
OR
b) "Upgrading" from an older (major) version like 13.1 (Cynagenmod) or a stock-ROM (5.1.1 / 6.0), to an LOS-14.1 for the first time (Clean-Flashing)?
Since the operational sequence listed in the site has no Factory-wipe (i.e dirty-flash), I tend to assume the answer of above is case(a) : "Updating" LOS-141.1: [ Old.Nightly --> New.Nightly].
But the title of the page is "Upgrading" & NOT "Updating". Hence my question!!
So what is the correct answer folks? Case-(a) or Case-(b).
Click to expand...
Click to collapse
KrisM22 said:
If you delete the "expert" word, I'll answer. - Yes, it's unclear. - that would be an update (dirty) on top of the same thing (14.1), imho. I suppose you could try it on top of 13 but I wouldn't want to vouch for the results and what you would wind up with, or whether it would even boot.
If I were to change it I would put a wipe of dalvik/ART, data, system, cache in front if that - then you've got a nice clean flash. Which is what I do several times a week. I use TitaniumBackupPro to backup (before) and restore (after) all my apps. Makes life so much easier.
Click to expand...
Click to collapse
bhishmar said:
@KrisM22, Thanks for ur response.
So essentially your answer for my above question is =
Case-(a) : Updating from [Old.nightly to New.Nightly]. OK?
- That is a factory-wipe, you are suggesting to add, before flash.
-I assume this needs a rooted system. And also w/o Titanium Backup, you are left with a totally wiped system, with all your settings/configurations, data & apps lost. Am I right?
Click to expand...
Click to collapse
KrisM22 said:
1) yes, "a"
2) I find in the parlance that when folks say "factory wipe" they often are NOT including "system". I do since it can allow a google problem (or many other problems) to be carried forward from build to build. I got caught by this a number of months back and wasted a lot of time. So I recommend "wipe", "advanced", dalvik/ART,data,system,cache.
3) yes, unfortunately TBPro does need root. I believe there is a backup out there, or used to be, that doesn't need root, but I don't know of it.
3b) yes, clean flash means all settings are gone. This is extremely useful as one of those settings may be causing a problem.
After all, this is running under the illusion of being a development thread, for a development ROM, in development status. Most casual people should NOT use it for a daily driver unless they are willing to put up with clean flashes, frequently, imho.
Click to expand...
Click to collapse
bhishmar said:
Incidentally how can i delete my own duplicate post?
Do the original poster has the privilege to do it?
It is not only what folks say, but also what "Factory-wipe" means, in official stock-recovery-parlance, & stock-recovery-menu. It does'nt wipe system as i know, so that u get a bootable system after factory-wipe ( & the intention is to get a bootable system).
But I understand what u r saying. You are essentially suggesting a conventional "Factory-wipe" + "system-wipe", so that we get a totally clean system devoid of any carried over errors. I also see that from ur experience u feel confident only with such a drastic step.
But to understand further, don't u think that some carried over system errors will get back from the Titanium backup also. Because all apps & system settings & configurations are put back from backup? I am only thinking aloud here, not sure about this....
Click to expand...
Click to collapse
KrisM22 said:
1) I replied above but click flag/report (triangle lower left of post) on those that you wish to delete and in the message just say it was an error, please delete. put low priority. Thank them profusely.
2) Whether something is bootable or not is determined by lots of things, but boot img and the stuff you flash in to /system, are critical. It is assumed you are flashing a bootable ROM in this case. Junk left in /system can be seen by the ROM you flash, if it does not overwrite it, and some things are intentionally not overwritten (watch the twrp lines as you are flashing something) and some gapps stuff is one of them.
3) EXCELLENT POINT! I have changed my habit recently as I have gotten lazy and have started restoring the apps with data, and you can indeed bring forward problems that way. If you don't know which app may be causing the problem, install them all without data (check box in TBP just before restore). Or if you only suspect a few, you could restore them all with data and then go to settings/apps/particular app/ storage, and clear cache and data.
As to why I do almost anything - it is to save time. I found years ago that I was wasting a ton of time dirty flashing and the resultant shooting bugs. So I changed.
Click to expand...
Click to collapse
bhishmar said:
@KrisM22 : Thanks for ur valuable inputs.
Now to another point, in my original post.
Now that we concluded that the official Lineage-OS-Wiki site "Manually Upgrading LineageOS" :
https://wiki.lineageos.org/upgrading.html
is really talking about "Updating from [Old.nightly to New.Nightly]", using dirty-flashing,
I have a further question.
The above site says that after dirty-flashing the latest Nightly-ROM, & before 1st Reboot, latest Gapps also need to be mandatorily flashed. (btw steps 8 & 9)
But in these forums, I have seen many contradictory recommendations regarding this topic, that either don't re-flash Gapps or don't need to be done.
(meaning don't do it OR does'nt hurt to do it)
I just want to inquire whether this (mandatory flashing) is a recent change in official position?
I just want to hear your opinion & others who regularly or frequently update nightly roms (14.1)
Click to expand...
Click to collapse
KrisM22 said:
1) yes.
2) Some people don't use gapps, so they wouldn't flash gapps. I don't know what they use or how they initialize their system.
2a) Obviously if you dirty flash the ROM you probably don't need to flash gapps. I guess. To me that's living on the edge. I would never not flash gapps, but then I would never dirty flash unless I'm testing for a dev.
2b) if you (your definition of) factory flash, then you "may not need to flash gapps, but I would never do that, nor would I tell someone to do that. It takes such a short time to flash something, and you might wind up spending hours shooting some problem that you then blame on the ROM even though it was fixed by a clean flash... well, I think you get the point.
2c) if you clean flash incl /system, you would need to flash gapps, if you use gapps, and almost all folks here and in the world use gapps.
Okay, if I didn't quite hit the nail on the head, fire away!
Actually, this is getting a bit Off Topic (LineageOS so we probably better end this or start it up in Q&A.
Click to expand...
Click to collapse
bhishmar said:
OK you gave ur point of view.
I also want to know more about what the official wiki site is saying.
Now the operational sequence listed in this site is a dirty flash. (No factory wipe, no data-wipe).
Yet they insist that, if you have used Gapps previously, you should mandatorily reflash latest Gapps.
Your views differ from these, especially the mandatory part. You say with a dirty flash you need not reflash Gapps. (Aside from ur reservations on dirty-flash).
From common sense I am also of the same view, since u can always go to playstore to update to update apps.
So I am confused why the official site say latest Gapps should be reflashed, mandatorily before 1st reboot after LOS nightly flashing.
It they say it is desirable or recommended it is understandable. I don't understand the mandatory part.
Am I right in my line of thought, and are you in agreement there?
Click to expand...
Click to collapse