My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
haimmalka said:
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
Click to expand...
Click to collapse
did you follow all instructions for the new rom install properly? its some problem with the rom. Try a new rom and make sure you follow all the instructions properly
rollerdyke44 said:
did you follow all instructions for the new rom install properly? its some problem with the rom. Try a new rom and make sure you follow all the instructions properly
Click to expand...
Click to collapse
I do it right
wipe
Then install rom
There rom works
Some do not work to restart always get stuck
I wonder why
haimmalka said:
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
Click to expand...
Click to collapse
If nothing else works flash a factory image ☺
sachin.parmar100 said:
If nothing else works flash a factory image
Click to expand...
Click to collapse
What you seem I do not understand?
haimmalka said:
What you seem I do not understand?
Click to expand...
Click to collapse
I meant if any other methods doesn't work then grab a factory image via Google server and flash it via fastboot
Link :
https://developers.google.com/android/nexus/images
sachin.parmar100 said:
I meant if any other methods doesn't work then grab a factory image via Google server and flash it via fastboot
Link :
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I understood but I ask why this is happening
Some of the works
And some do not work restart
I want to know what the problem is
Probably kernel issue.
Aerowinder said:
Probably kernel issue.
Click to expand...
Click to collapse
Explain what this means?
haimmalka said:
Explain what this means?
Click to expand...
Click to collapse
Google it
dicecuber said:
Google it
Click to expand...
Click to collapse
Hahaha
I looked it up on Google
I went back to the same state device always do a restart
Until it worked fine now again it came back to do it] =
I was looking google what he means I get here:
http://kernels.franco-lnx.net/Nexus5/5.0/
Then again it returned to constantly restart the device
Now there is a direction to know how it happens?
How to fix it?
I do not remember what I did that worked
Tip know at least that's how it happens:crying:
haimmalka said:
Explain what this means?
Click to expand...
Click to collapse
A kernel acts as a connection between the
hardware and the software.
so if you flash a wrong kernel, it will misbehave
sachin.parmar100 said:
A kernel acts as a connection between the
hardware and the software.
so if you flash a wrong kernel, it will misbehave
Click to expand...
Click to collapse
I think that's a problem for the solution of the fire makes it
I order the same day repair lab
Flash a factory image. If the restarts stop then you know it's a problem with the ROM/kernel. Not all phones are identical, what may work for some doesn't always work for others. Your phone simply may not like some custom kernels, simple as that. If the ones you are flashing are undervolted by default that could be the problem, as some phones respond better to undervolting than others.
_MetalHead_ said:
Flash a factory image. If the restarts stop then you know it's a problem with the ROM/kernel. Not all phones are identical, what may work for some doesn't always work for others. Your phone simply may not like some custom kernels, simple as that. If the ones you are flashing are undervolted by default that could be the problem, as some phones respond better to undervolting than others.
Click to expand...
Click to collapse
Happens all the time for my device
I also install this rom Original still to helping through Toolkit
I also put a device
Start-up Shutdown button repair
It did not help thinking maybe this is the problem
So what is the problem I can not figure] =
haimmalka said:
Happens all the time for my device
I also install this rom Original still to helping through Toolkit
I also put a device
Start-up Shutdown button repair
It did not help thinking maybe this is the problem
So what is the problem I can not figure] =
Click to expand...
Click to collapse
Don't use toolkits. Flash the system image with fastboot. If the problem is still there, it's your phone. If the problem disappears, it's the ROM/kernel. Again, use fastboot and not a toolkit.
_MetalHead_ said:
Don't use toolkits. Flash the system image with fastboot. If the problem is still there, it's your phone. If the problem disappears, it's the ROM/kernel. Again, use fastboot and not a toolkit.
Click to expand...
Click to collapse
I try many things to no avail
I put it back to the lab to solve this problem
I've had enough to deal with it without success..
I do not know if it's a software problem
Or issue with the device
I do not believe more than 5 Nexus device that happens to many people
haimmalka said:
I try many things to no avail
I put it back to the lab to solve this problem
I've had enough to deal with it without success..
I do not know if it's a software problem
Or issue with the device
I do not believe more than 5 Nexus device that happens to many people
Click to expand...
Click to collapse
But have you restored to 100% stock by flashing a factory image using fastboot?
_MetalHead_ said:
But have you restored to 100% stock by flashing a factory image using fastboot?
Click to expand...
Click to collapse
I do not understand exactly what you record
I can not understand English I use Google Translate
Thank you you try to help
You need to tell me what to do to try ..
I just try it
Guide me step by step what to do
If you ask yes I have fastboot
Files
flash-all
image-hammerhead-ktu84p
bootloader-hammerhead-hhz11k
radio-hammerhead-m8974a-2.0.50.2.22
image-hammerhead-krt16m
cache
boot
bootloader-hammerhead-HHZ11d
userdata
system
recovery
I press
flash-all
Command window opens install it
It does not help
I also make it a manual command that does not help
I try a lot of versions
This is repeated restart problem ]=
Related
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
pewtel said:
hello everyone,
i'm developing a game with unity and sometimes when i compile and inject the game on the phone it crashes and forces me to factory reset the phone through fastboot. i've done it like 3 times already with no problems.
but today it happened again and the phone just wouldnt recover, i've tried the fix that this video (youtube.com/watch?v=laU6NQ0LxR0) shows but it still does not boot.
I am able to enter fastboot and my computer recognizes the mobile phone so that's a great start :victory:
not sure what guide to follow since i'm not sure whether the problem is on the rom or something else.
can someone give me a tip on what fix should I try? cant really afford to lose my phone right now
it has (had) a stock rom 4.4.2 with stock bootloader, tho i tried to install the fix in the video i've said earlier and i'm not sure whether it changed the rom or not.
thanks
Click to expand...
Click to collapse
What about following this guide?
Landrea said:
What about following this guide?
Click to expand...
Click to collapse
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
pewtel said:
got stuck here :/
dropbox.com/s/d3s378e9pvxs0ab/Screenshot%202014-03-30%2023.17.12.png
Click to expand...
Click to collapse
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Landrea said:
Have you configured the drivers on your pc? The phone is recognized? It looks like the pc can't dialogate with it
Sent from my Commodore 64 using Videotel
Click to expand...
Click to collapse
the phone is recognized as motorola adb interface, i even re-installed the drivers. now trying a different rom but i'm pretty sure the ROM is not the issue
*edit: yep, still waiting for device even with different ROM
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
pewtel said:
modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
:victory: :victory: :victory:
this worked for me,
posting the link just in case someone encounters the same problem. thanks
Click to expand...
Click to collapse
Thank you for sharing
/Data gets corrupted
Even, I had the same issue. I tried flashing ROMs through recovery but it gave me error that/data/media/0/ can't be mounted. The only way to get out I found was to full format /data and /storage (philz recovery) and then to push ROM. zip to/sdcard through adb and then to flash it through recovery.
Hope it helps someone.:angel:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?
Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.
Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.
Hello, everyone. I've got a trouble with my at&t atrix 2. I've cm10 onboard and when I tried to flash another rom on it I found that nothing changes. Reading similar problem threads I realized that the problem is in NAND, which is in R/O mode. And every change in internal storage restores after the phone reboot. Does anyone have a solution for this ? Plz help.
Ramieres1 said:
Hello, everyone. I've got a trouble with my at&t atrix 2. I've cm10 onboard and when I tried to flash another rom on it I found that nothing changes. Reading similar problem threads I realized that the problem is in NAND, which is in R/O mode. And every change in internal storage restores after the phone reboot. Does anyone have a solution for this ? Plz help.
Click to expand...
Click to collapse
fxz back to stock and start again maybe the best solution for any kind of problem...
that what I will do if something goes wrong with my A2
Az-one786 said:
fxz back to stock and start again maybe the best solution for any kind of problem...
that what I will do if something goes wrong with my A2
Click to expand...
Click to collapse
Nope. Nothing changes yet.
Ramieres1 said:
Nope. Nothing changes yet.
Click to expand...
Click to collapse
What method you are using?
Use BMM only.....here is the link......http://forum.xda-developers.com/showthread.php?t=2602229
Atrix2dBeast said:
What method you are using?
Use BMM only.....here is the link......http://forum.xda-developers.com/showthread.php?t=2602229
Click to expand...
Click to collapse
The problem is probably in NAND-flash. It is in read-only mode because of an error, I guess. So I can noy boot into BMM recovery. Maybee it will be easier to replace mainboard from anoter A2 ?
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
Hey, I have got a problem with my OnePlus One for quiet some time..
It started about 2 months ago - Whenever I'm on a call, the other side can barely hear me unless I'm on speaker.
I did some reading and there are suggestions that this is because of some mis-written code or something, that makes the input of the microphone low, so that only a small precent of the sound is being transferred to the one I'm talking to.
this may or may not be the problem, but I wanted to ask you fellows if anyone has any suggestion on what's causing this and how to try & solve it.
I'm Running a Stock 5.0.2 Cm12s with the latest OTA update, and this problem started when I had Stock 4.4.4 CM11s.
Device isn't rooted & never was.
Locked Bootloader.
Please help if you can
Lidor167 said:
Hey, I have got a problem with my OnePlus One for quiet some time..
It started about 2 months ago - Whenever I'm on a call, the other side can barely hear me unless I'm on speaker.
I did some reading and there are suggestions that this is because of some mis-written code or something, that makes the input of the microphone low, so that only a small precent of the sound is being transferred to the one I'm talking to.
this may or may not be the problem, but I wanted to ask you fellows if anyone has any suggestion on what's causing this and how to try & solve it.
I'm Running a Stock 5.0.2 Cm12s with the latest OTA update, and this problem started when I had Stock 4.4.4 CM11s.
Device isn't rooted & never was.
Locked Bootloader.
Please help if you can
Click to expand...
Click to collapse
try to flash this http://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
I had the same problem and it fixed it.
The only thing is that i had to flash it after every rom change.
solokiller11 said:
try to flash this http://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
I had the same problem and it fixed it.
The only thing is that i had to flash it after every rom change.
Click to expand...
Click to collapse
Does it not require a root access?
Lidor167 said:
Does it not require a root access?
Click to expand...
Click to collapse
it requires a custom recovery but not sure about root, i guess its required but not sure
solokiller11 said:
it requires a custom recovery but not sure about root, i guess its required but to sure
Click to expand...
Click to collapse
I don't even know what costum recovery means..
Lidor167 said:
I don't even know what costum recovery means..
Click to expand...
Click to collapse
read this thread, its a great one and explains everything you need to know
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
you don't have to read everything (although recommended)
solokiller11 said:
read this thread, its a great one and explains everything you need to know
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
you don't have to read everything (although recommended)
Click to expand...
Click to collapse
So in order to install a custom recovery ( say TWRP ) I do not need root acess? do I only need to follow step no.2 at the guide you gave me?
Lidor167 said:
I don't even know what costum recovery means..
Click to expand...
Click to collapse
Lidor167 said:
So in order to install a custom recovery ( say TWRP ) I do not need root acess? do I only need to follow step no.2 at the guide you gave me?
Click to expand...
Click to collapse
Yes, But it is also recommended to root the phone. Root is a great thing to have