Hey!
It's really hard to explain my issue, but I'll try my best.
So here it goes..
My Nexus 5 keeps telling me I have a system update to download and install, so I wait for it to download and then it tells me to install the update from CM-Hammerhead-46e2abd61c to 1f023a4eca-signed.
It shows the Install update option right below, and everything seems fine till now.
When I press this Install update button, it reboots the phone, shows me an android popped open and something indicating that there're being changes which are not shown in normal reboots ofc.
The phone reboots and start, tells me it;s optimizing apps since I use Android Run-time Cache instead of Dalvik.
Now the issue is, it's not updated at all.
It shows me the same Cyan and Android version, 4.4.2 and 46e2abd61c, and when I check for update, it shows me the same thing that I have to update from CM-Hammerhead-46e2abd61c to 1f023a4eca-signed.
I tried this like 10 times and it happens over and over again.
This is bugging me for like a day now.
Any solutions to this?
Thanks.
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
If you're using cwm I don't think it'll work
Lethargy said:
If you're using cwm I don't think it'll work
Click to expand...
Click to collapse
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
rootSU said:
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Dunno then, I guess OP can try a different recovery to the one he's using now
Lethargy said:
Dunno then, I guess OP can try a different recovery to the one he's using now
Click to expand...
Click to collapse
Maybe. Thats why I'm trying to find out which one he is using
Sent from my Nexus 5 using Tapatalk
HeyIamSmiley said:
Hey!
The phone reboots and start, tells me it;s optimizing apps since I use Android Run-time Cache instead of Dalvik.
Thanks.
Click to expand...
Click to collapse
Not that it matters, but I'm kind of curious which runtime you're using =P
I'm having the same problem as well.
californiamaki said:
I'm having the same problem as well.
Click to expand...
Click to collapse
Then can you answer my question also please?
Sent from my Nexus 5 using Tapatalk
Try to download the latest update on your PC and flash it on your phone and if that doesn't work change recoveries.
rootSU said:
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not even sure, really new to this rooting stuff.
How do I check?
ClockworkMod
rootSU said:
What recovery are you using?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm using ClockworkMod.
And if it doesn;t work with Cwm, then what should I do to install that update?
Lethargy said:
If you're using cwm I don't think it'll work
Click to expand...
Click to collapse
Yes, I'm using ClockworkMod, so what do I do now?
rootSU said:
I think it ONLY works with CWM :/
It's that whole, lazy /sdcard/0 thing.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://www.cyandelta.com/index2213.html?q=FAQ
HeyIamSmiley said:
Yes, I'm using ClockworkMod, so what do I do now?
Click to expand...
Click to collapse
Try flashing one of these two recoveries with fastboot in bootloader
TWRP: http://techerrata.com/browse/twrp2/hammerhead
PhilZ Touch: http://forum.xda-developers.com/goo...t/hammerhead-philz-touch-6-43-6-f2fs-t2565174
Read a couple threads in the first linked thread of my signature if you're not sure how.
Lethargy said:
http://www.cyandelta.com/index2213.html?q=FAQ
Try flashing one of these two recoveries with fastboot in bootloader
TWRP: http://techerrata.com/browse/twrp2/hammerhead
PhilZ Touch: http://forum.xda-developers.com/goo...t/hammerhead-philz-touch-6-43-6-f2fs-t2565174
Read a couple threads in the first linked thread of my signature if you're not sure how.
Click to expand...
Click to collapse
Guess they've updated it recently then. This certainly was not the case recently, because Phil threads often get asked why it doesn't work and teh answer is the /sdcard/0.
Who knows, Maybe CM finally saw the light, 12 months after everyone else? I wont hold my breath though. Until very recently, it only worked in CWM. It was written that way
rootSU said:
Guess they've updated it recently then. This certainly was not the case recently, because Phil threads often get asked why it doesn't work and teh answer is the /sdcard/0.
Who knows, Maybe CM finally saw the light, 12 months after everyone else? I wont hold my breath though. Until very recently, it only worked in CWM. It was written that way
Click to expand...
Click to collapse
Dunno. Omni says OpenDelta only works with TWRP: http://omnirom.org/general/opendelta-brings-incremental-system-updates-omni/
I've never used Delta since I build my ROMs myself
Edit: CyanDelta seems to be 3rd party, not CyanogenMod's version of OpenDelta. Does the same thing though, I guess using TWRP is most likely to work for this? But you say it only worked in CWM.. so I have no idea lol
Lethargy said:
Dunno. Omni says OpenDelta only works with TWRP: http://omnirom.org/general/opendelta-brings-incremental-system-updates-omni/
I've never used Delta since I build my ROMs myself
Edit: CyanDelta seems to be 3rd party, not CyanogenMod's version of OpenDelta. Does the same thing though, I guess using TWRP is most likely to work for this? But you say it only worked in CWM.. so I have no idea lol
Click to expand...
Click to collapse
The whole thing came about where when 4.2 came out, they moved /sdcard from /data/media/ to /data/media/0. CWM left it as /data/media - which even today, is why you cant see your nandroids taken with CWM in /sdcard
So what the updater app did was put in the updater-script /sdcard/0 as the path, leaving the /data/media mountpoint in CWM in tact... In Philz and TWRP, you would see the error in recovery log (cannot find /sdcard/0/whatever.zip) because on proper recoveries, that is actually /data/media/0/0/whatever.zip).
So Kudos if they changed it to support real recoveries instead of legacy, antiquated CWM builds.
rootSU said:
The whole thing came about where when 4.2 came out, they moved /sdcard from /data/media/ to /data/media/0. CWM left it as /data/media - which even today, is why you cant see your nandroids taken with CWM in /sdcard
So what the updater app did was put in the updater-script /sdcard/0 as the path, leaving the /data/media mountpoint in CWM in tact... In Philz and TWRP, you would see the error in recovery log (cannot find /sdcard/0/whatever.zip) because on proper recoveries, that is actually /data/media/0/0/whatever.zip).
So Kudos if they changed it to support real recoveries instead of legacy, antiquated CWM builds.
Click to expand...
Click to collapse
Yeah, it's probably something related to that.. Several people I know had related issues with certain recoveries and complained about it. Solution was using a different recovery lol
Anyways, if it doesn't work for the OP in one recovery he can try another.
Lethargy said:
Anyways, if it doesn't work for the OP in one recovery he can try another.
Click to expand...
Click to collapse
How many euros will you bet that we never find out the answer?
rootSU said:
How many euros will you bet that we never find out the answer?
Click to expand...
Click to collapse
Euros? Psh :silly:
Related
Hi all.
How can I wipe my Nexus 5 so it is a plain Kit Kat 4.4.2 (like the day I received it) and just root it? it's currently in 4.4.2 and rooted, but with a lot of stuf in it too. My main concern is how to wipe once it's rooted, and how to reroot.
For those who like to read, a little more info:
I have a Nexus 5 which received 2 days ago. I come from an iPhone 5S, so... pretty newbie...
I unlocked the bootloader and rooted the device after unboxing, and have been using it since. Problems are:
1. I just found out about CWM and its capabilities, and I intend to use the backups a lot.
2. I kind of ****ed up with a couple of apps I regret installing.
3. After a backup I just did today, it asked to whether or not fix the recovery (or something like that). Selected YES, nothing happened. It then asked to fix the root... said YES and screwed it completely. I had to put SuperSu in the phone as a ZIP and manually install it again to recover my root access. It kind of looks "dirty" now, lol.
Anyways, I'd like to make a whole device backup from CWM with Kit Kat out of the box, no extra apps installed. Just rooted. Then install all my stuff, sync contacts and so on, and make another backup.
That's why I want to erase the device and have it all clean (just rooted).
Thanks!
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
rwed said:
Thanks! Can link 2 be replaced with just running CF-Auto-Root? That's what I used the first time and worked great.
Click to expand...
Click to collapse
It can, but I'd recommend you do it per the link.
jd1639 said:
It can, but I'd recommend you do it per the link.
Click to expand...
Click to collapse
Mmm. OK. And why? (Just curious at this point)
rwed said:
Mmm. OK. And why? (Just curious at this point)
Click to expand...
Click to collapse
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
rootSU said:
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Click to expand...
Click to collapse
lol OK. Thanks guys.
I come from iOS after several years. Please bear that in mind.
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
rootSU said:
We're just offering you the benefit of our collective experience. Some of us have been doing this for years so please understand - we're not giving you grief. We have your best interests in mind
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh please, I know. I was just hiding my ignorance under the iOS carpet.
Will give a read to both links tomorrow. Will definitely do link1 on friday if I find the time, and will then consider either doing link2 or going the CF-Auto-Root way.
I'll let you know how this all ends.
Again, thanks!
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
jd1639 said:
Start here http://forum.xda-developers.com/showthread.php?p=47156064
Then go here
http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
rootSU said:
Because the 2nd method furnishes you with knowledge and experience to help you understand and learn things that cf auto root "automates" for you. Using our recommended method, you will have a head start in knowing how to do things you may need to do to recover your device from various scenarios.
...for example, had you used that method last time - applying logic and knowledge, you may not have created this thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
rwed said:
Update:
Followed steps in link1. Everything went fine.
Gave a deep read to link2. Found it understandable and easy to do and follow, but decided to go the CF-Auto-Root way just because I had done it before and worked nicely...
Everything OK. Something weird happened -again- though. After the clean restore and root, I installed CWM and proceeded to make a backup of the plain system. After it, it asked to fix root again. I had previously said YES, which lead to a broken root, so I said NO this time. Same thing happened!! I lost root and had to manually install SuperSu 1.93 from ZIP in CWM... Why does this happen?
Anyways, I have another question. If one day I decide to restore from this backup I just made, will it be exactly as doing a complete restore following link1?
Thanks!
Click to expand...
Click to collapse
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
rootSU said:
Stop using cwm... use twrp or philz which can turn the nag off.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
jd1639 said:
Flash this in cwm http://d-h.st/YpG. It'll put twrp on
Click to expand...
Click to collapse
rwed said:
Oh damn it... Really? OK, a couple of quick questions:
1. Did reinstalling SuperSu leave junk in the file system?
2. Will flashing TWRP leave anything either?
My OCD would probably make me restore again if the answer to any of those questions is yes.
Click to expand...
Click to collapse
No to both your questions.
jd1639 said:
No to both your questions.
Click to expand...
Click to collapse
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
Not for the nexus 5. I think you're looking at cwm.
jd1639 said:
Not for the nexus 5. I think you're looking at cwm.
Click to expand...
Click to collapse
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
rwed said:
I saw it here: https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Click to expand...
Click to collapse
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
jd1639 said:
I just looked at it. I'm not sure what that is. The file I linked you to is the latest image from goo.im which is the official twrp depository.
Click to expand...
Click to collapse
I'll just install your file, specially if you can't even tell what that thing I linked is. Thank you jd. :good:
rwed said:
Thank you very much!
I just saw that TWRP is in version 5.7.3 in the Play Store. Any reason why you linked to 2.6.3.4? I'm asking because I guess it'll update as soon as I boot. Right?
Click to expand...
Click to collapse
That's the twrp manager. Different things. One is an app and one is a recovery
Sent from my Nexus 5
I'm running Cyanogenmod 11 and about once a day I get the error "Unfortunately, the process com.android.systemui has stopped. Another one just started today too the error is com.android.incallui has stopped. I also get a problem with my camera where it wont open and i get the message unfortunately the camera has stopped. I've been googling around and haven't really found anything. How do I fix this? Thanks in advance!!
Usually wiping data...
Sent from my Nexus 5 using Tapatalk
rootSU said:
Usually wiping data...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
If I wipe my data what happens to my phone like does everything get deleted?
lilfil3 said:
If I wipe my data what happens to my phone like does everything get deleted?
Click to expand...
Click to collapse
Yes it does. Not the sdcard though, if you have a custom recovery.
These are the basics to be fair. You should know all this if you're rooted. Please have a read of the sticky threads here and in general. They cover things like wipes, backups etc
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes it does. Not the sdcard though, if you have a custom recovery.
These are the basics to be fair. You should know all this if you're rooted. Please have a read of the sticky threads here and in general. They cover things like wipes, backups etc
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks! I just have a question. When I wipe data/ factory reset. It doesn't delete the rom off my phone does it? It just deletes all my settings and apps and stuff right?
lilfil3 said:
Thanks! I just have a question. When I wipe data/ factory reset. It doesn't delete the rom off my phone does it? It just deletes all my settings and apps and stuff right?
Click to expand...
Click to collapse
Correct. ROM Is on /system partition. Wipe /data only wipes /data partition. This is all explained quite well in the sticky thread in q&a by @abaaaabbbb63
Sent from my Nexus 5 using Tapatalk
rootSU said:
Correct. ROM Is on /system partition. Wipe /data only wipes /data partition. This is all explained quite well in the sticky thread in q&a by @abaaaabbbb63
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks!! Just restored it. That thread was helpful!
Anytime I've tried themes on cm based ROMs with theme support.....9 times out of 10, I eventually get these errors.
kj2112 said:
Anytime I've tried themes on cm based ROMs with theme support.....9 times out of 10, I eventually get these errors.
Click to expand...
Click to collapse
Does it only happen when you download different themes? I just use the stock theme and I still get these errors.
lilfil3 said:
Does it only happen when you download different themes? I just use the stock theme and I still get these errors.
Click to expand...
Click to collapse
No, I only get it when running the themes. I don't use them anymore.
kj2112 said:
No, I only get it when running the themes. I don't use them anymore.
Click to expand...
Click to collapse
I wonder why I was then. That's weird...
so i was on cataclysm from the beginning and everything worked great. I flashed stock 4.4.4 cause i want to use just xposed with a nice vanilla rom. everything works great except i cant get or place calls. i have sprint lte full bars, can get data and everything send texts/mms, go on facebook, dl stuff, just no calls. wifi or not doesnt matter either. everytime i try to place one it just sits on dialing and i lose all bars and then says can t make call, no connection. once i hang up the bars and lte come back.
I have noticed my network ends up on global sometimes instead of LTE but even when i switch it to LTE it still doesnt work. i have updated prl and profile too. Any ideas? thanks
EDIT: yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/forum/#!topic/nexus/Or6_6zCtBwc
seems like it might be sprints fault
Did you wipe?
Sent from my Nexus 5 using Tapatalk
rootSU said:
Did you wipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
fergdizzle9090 said:
yep cache, dalvik, data. never had this problem with any other roms before? might it be a 4.4.4 issue? cataclysm was 4.4.2
Click to expand...
Click to collapse
did you update the bootloader and radio?
Zepius said:
did you update the bootloader and radio?
Click to expand...
Click to collapse
no i did not, just twrp. would that be the problem?
possibly. you should do it to be safe.
Zepius said:
possibly. you should do it to be safe.
Click to expand...
Click to collapse
do you have to do it when you upgrade android versions? is there any quick link you can post to help me out with it? im not all that familiar with updating those. Ill search around and see what I can find. thanks for the suggestion though
Im thinking about RMAing my nexus 5 though because the power button is very loose and rattles loudly when i tap the screen, dont want a crappy refurb in place of my mint pristine nexus though :/ lol
Rma is always new
Sent from my Nexus 5 using Tapatalk
rootSU said:
Rma is always new
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
oh i didnt know that. well great thanks. Ill give the updates a shot and consider the rma more now i know ill be getting a new phone. just dont want to be without it for a while lol
yeah i still cant seem to fix it. I was going to go back to a 4.4.2 rom but for some reason it fails in twrp everytime now... :/ but this is the exact problem i am having in this thread https://productforums.google.com/fo...ce=footer#!msg/nexus/Or6_6zCtBwc/j5CP8vy4jGAJ
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Lokke9191 said:
Install 4.4.4 using fastboot. And after make sure you are using the latest version of twrp.
Click to expand...
Click to collapse
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
fergdizzle9090 said:
ill have to look up some stuff on fastboot and recovery updates. been a while since ive done anything out of recovery
Click to expand...
Click to collapse
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Lethargy said:
Section 3 #1 and Section 4 #1
[Resource] All Guides and Info Threads
Click to expand...
Click to collapse
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
fergdizzle9090 said:
oh yeah ok thanks. so you are suggesting just completely restarting and rerooting from absolute stock?
Click to expand...
Click to collapse
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Lethargy said:
Personally I would flash the factory images again just to rule out software being the issue, if it still happens then I guess RMA or whatever.
Click to expand...
Click to collapse
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
fergdizzle9090 said:
yeah i'll give that a try. weird thing is this happened only after i flashed 4.4.4 from cataclysm 4.4.2. i am waiting to hear if an RMA fixes the issue since someone else is already going that route. it sounds to me like it might be sprint
Click to expand...
Click to collapse
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
thanks ill try it out when i got a spare moment. now that im thinking of it this all happened after i updated twrp, so could that be the root of all this you think? because i used the twrp app to update it instead of flashing, and i noticed it has been acting extremely weird lately.
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
hsas.69 said:
You might check your APN settings. I had issues with MMS after flashing 4.4.4.
Click to expand...
Click to collapse
ill look into it. people who have this problem said its not the apn though because i get data just fine and i can recieve calls. its only when i am placing a call it goes crazy and disconnects me
EDIT: so anyone know how to get to apn for sprint? its not under mobile networks. is it buried in a dialer menu or something?...
Lokke9191 said:
I doubt it is sprint causing this, or it would be all over these forums. I'd definitely install 4.4.4 via fastboot it'll give you the newest radio and the stock recovery. I'm betting this will fix your issue. Then just use fastboot or flashify to install the newest twrp, and flash su in recovery. If this doesn't fix it, it's a hardware issue.
Click to expand...
Click to collapse
well full reflash of 4.4.4 stock from google through fastboot didnt work :/ i noticed also that it hasnt been connecting during initial setup, i have to connect to wifi. think my phone might be borked :crying:
I flashed userdata, and it wiped everything as expected.
But I didn't have a ROM installed. So I'm OSless and there is no OS on the internal SD card anymore.
What do I do in this situation?
RaggleFraggles said:
I flashed userdata, and it wiped everything as expected.
But I didn't have a ROM installed. So I'm OSless and there is no OS on the internal SD card anymore.
What do I do in this situation?
Click to expand...
Click to collapse
Flash factory image or adb sideload a rom in TWRP recovery
GtrCraft said:
Flash factory image or adb sideload a rom in TWRP recovery
Click to expand...
Click to collapse
When I try to do that, the toolkit tries to boot to android and wait for ADB.
RaggleFraggles said:
When I try to do that, the toolkit tries to boot to android and wait for ADB.
Click to expand...
Click to collapse
Don't use toolkits! Download the factory image from 4.4.4 connect your phone to your pc when in fastboot. Then click on flash-all.bat from the extracted image file
GtrCraft said:
Don't use toolkits! Download the factory image from 4.4.4 connect your phone to your pc when in fastboot. Then click on flash-all.bat from the extracted image file
Click to expand...
Click to collapse
Okay, I have a Flash all with Android L on my computer here.
I need a tutorial because it says it's not a command.
RaggleFraggles said:
Okay, I have a Flash all with Android L on my computer here.
I need a tutorial because it says it's not a command.
Click to expand...
Click to collapse
That's because you've not got adb/fastboot in your System Path. You'll need to extract the image to your fastboot folder and then run the flash-all.bat file again
RaggleFraggles said:
Okay, I have a Flash all with Android L on my computer here.
I need a tutorial because it says it's not a command.
Click to expand...
Click to collapse
Sigh...if only XDA had something like that stickied in the general section or something...http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527 <- everything you need is in this thread. Please read it before using toolkits.
PsychDrummer said:
Sigh...if only XDA had something like that stickied in the general section or something...http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527 <- everything you need is in this thread. Please read it before using toolkits.
Click to expand...
Click to collapse
Not to mention a few of us have it in our signatures. Lol
Lethargy said:
Not to mention a few of us have it in our signatures. Lol
Click to expand...
Click to collapse
Wish it could be a banner at the forum. Or even a pop up
Sent from my Nexus 5 using Tapatalk
He may have used a toolkit but at least he gave us an informative thread title.
OP: if you had done your modding without toolkits, you'd know that this is a nothing issue, resolvable in minutes.
Wakamatsu said:
He may have used a toolkit but at least he gave us an informative thread title.
OP: if you had done your modding without toolkits, you'd know that this is a nothing issue, resolvable in minutes.
Click to expand...
Click to collapse
Unfortunately, toolkits and "soft-bricks" are the reason for 90% of threads in Q&A, and the occasional few placed in incorrect sections.
Lethargy said:
Unfortunately, toolkits and "soft-bricks" are the reason for 90% of threads in Q&A, and the occasional few placed in incorrect sections.
Click to expand...
Click to collapse
I think he know. He isn't advocating
Sent from my Nexus 5 using Tapatalk
I fixed the problem on my own guys. I fell asleep and forgot to lock the thread. But now I know toolkits are not bout it.
RaggleFraggles said:
I fixed the problem on my own guys. I fell asleep and forgot to lock the thread. But now I know toolkits are not bout it.
Click to expand...
Click to collapse
Always better to learn :silly:
Lethargy said:
Always better to learn :silly:
Click to expand...
Click to collapse
I am having trouble with SMS now. I been trying to text my girl for 2 days now. They say it's an APN problem, but I don't understand what's wrong with my APN or how to update it.
RaggleFraggles said:
I am having trouble with SMS now. I been trying to text my girl for 2 days now. They say it's an APN problem, but I don't understand what's wrong with my APN or how to update it.
Click to expand...
Click to collapse
Is it just to the one number, or no one is receiving your texts?
PsychDrummer said:
Is it just to the one number, or no one is receiving your texts?
Click to expand...
Click to collapse
It's just one number. I think it's her problem though.
Find a girl with a number you can text to. Whatever you do, the phone stays!
I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?
It's probably because your bootloader is unlocked.
Honestly though I haven't heard of this.
I'm assuming you have the latest version and that you are rooted correct?
Has it worked at all on your setup?
Have you tried factory resetting, installing, and trying?
Maybe this might help someone who is more capable of helping than I am.
Sent from my SM-G920V using Tapatalk
twiz0r said:
It's probably because your bootloader is unlocked.
Honestly though I haven't heard of this.
I'm assuming you have the latest version and that you are rooted correct?
Has it worked at all on your setup?
Have you tried factory resetting, installing, and trying?
Maybe this might help someone who is more capable of helping than I am.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Have the latest version and I'm rooted. I've tried multiple times. Ah, I guess I'll just continue trying.
No issue with stock rooted.
No good. I knew one of the last 3 updates had a force close issue on 64 bit fixed. Was hoping it was that easy. Hopefully someone else will pop in for ya
Sent from my SM-G920V using Tapatalk
twiz0r said:
No good. I knew one of the last 3 updates had a force close issue on 64 bit fixed. Was hoping it was that easy. Hopefully someone else will pop in for ya
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
Thanks
twiz0r said:
It's probably because your bootloader is unlocked.
Honestly though I haven't heard of this.
I'm assuming you have the latest version and that you are rooted correct?
Has it worked at all on your setup?
Have you tried factory resetting, installing, and trying?
Maybe this might help someone who is more capable of helping than I am.
Sent from my SM-G920V using Tapatalk
Click to expand...
Click to collapse
My supposed "unlocked bootloader." Ha! You got me laughing.
deliberate.dev said:
My supposed "unlocked bootloader." Ha! You got me laughing.
Click to expand...
Click to collapse
I had to throw that in there on ya. Sorry
I'm not always an @$$hole I swear
twiz0r said:
I had to throw that in there on ya. Sorry
I'm not always an @$$hole I swear
Click to expand...
Click to collapse
Good to know.
deliberate.dev said:
I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?
Click to expand...
Click to collapse
There is one thing you might try. Delete the app. Go to your root folder data/data and delete the eu.chainfire.flash folder. Download and install the app again and see if it works.
Tulsadiver said:
There is one thing you might try. Delete the app. Go to your root folder data/data and delete the eu.chainfire.flash folder. Download and install the app again and see if it works.
Click to expand...
Click to collapse
Tried your suggestion, still doesn't work. Oh well, I'll just have to wait til something else comes along that'll let me flash.
deliberate.dev said:
I downloaded the Flashfire apk in hopes I'd be able to flash from my phone without recovery and every time I try going into the app, it instantly force closes. Has this happened to anyone else?
Click to expand...
Click to collapse
Where did you download the apk from?
What version is it?
When you say it "force closes", are you getting an error message?
Sent from my NCC-1701 using Tapatalk.
Finally got it working... then I go and upgrade my phone last night. Can't even use it til a new root method comes out.
deliberate.dev said:
Finally got it working... then I go and upgrade my phone last night. Can't even use it til a new root method comes out.
Click to expand...
Click to collapse
how did you get it working?
jonthn41 said:
how did you get it working?
Click to expand...
Click to collapse
setting your time to the year 2013
cant be connected to the internet
AlphaDroidzer said:
setting your time to the year 2013
cant be connected to the internet
Click to expand...
Click to collapse
why 2013 ? because thats when the device had its last software update?.. im trying to figure out how to get flashfire working on my tablet
jonthn41 said:
why 2013 ? because thats when the device had its last software update?.. im trying to figure out how to get flashfire working on my tablet
Click to expand...
Click to collapse
from what I gathered on google....
Devs stop supporting free version
if you dont want it to crash then buy pro