Hello folks,
I am a noob in playing around with Android, although I am a long time lurker here, never dared to post anything, just because I don't know even basics.
That said, my XT910 was driving me nuts and many a times I considered throwing it in trash, but having paid ~$400 hard cash, I did not. Lately, it crawled, rebooted randomly, hanging all of a sudden in the middle of the call was pretty commonplace. Factory reset did not help. The wi-fi connectivity issue has been there since day one. Where my another HTC One X connects like breeze and downloads whatever needed, XT910 still looks for any wi-fi connections.
I decided to root, hoping to tweak the device so that I can use it for at least another year or so. I followed the thread at http://forum.xda-developers.com/showthread.php?t=2257137 Very good thread, pretty easy to understand. I did encounter few issues and thats where this post comes in.
While this post shows screenshots for remote storage, I never got this option, but I added it in. I never got an option to enter the details of the location i.e. image 4 and 5 of the post. Still everything seemed to work as expected.
Majority of the on-screen prompts went as expected, they were not same. Considering this post, image 2, there is a good difference in what I saw and what the screenshot mentioned. My screenshot attached below.
So the questions I have, whats in the red boxes.
The first big red box is not in the original screenshot, but I got it.
The last line of USB disconnect, I never got, neither my phone vibrated in the whole process as mentioned in big red box.
Since I am noob, I can not decipher this, and with posts less than 10, I can not post in that thread. I will be really thankful if someone expert can flash some light on this.
Is my phone really rooted now?
(P.S. - Don't ask me for phone screenshots, they never work on my phone, with power and volume down button pressed together.)
Thanks a lot in advance.
fuzzychicken said:
Hello folks,
I am a noob in playing around with Android, although I am a long time lurker here, never dared to post anything, just because I don't know even basics.
That said, my XT910 was driving me nuts and many a times I considered throwing it in trash, but having paid ~$400 hard cash, I did not. Lately, it crawled, rebooted randomly, hanging all of a sudden in the middle of the call was pretty commonplace. Factory reset did not help. The wi-fi connectivity issue has been there since day one. Where my another HTC One X connects like breeze and downloads whatever needed, XT910 still looks for any wi-fi connections.
I decided to root, hoping to tweak the device so that I can use it for at least another year or so. I followed the thread at http://forum.xda-developers.com/showthread.php?t=2257137 Very good thread, pretty easy to understand. I did encounter few issues and thats where this post comes in.
While this post shows screenshots for remote storage, I never got this option, but I added it in. I never got an option to enter the details of the location i.e. image 4 and 5 of the post. Still everything seemed to work as expected.
Majority of the on-screen prompts went as expected, they were not same. Considering this post, image 2, there is a good difference in what I saw and what the screenshot mentioned. My screenshot attached below.
So the questions I have, whats in the red boxes.
The first big red box is not in the original screenshot, but I got it.
The last line of USB disconnect, I never got, neither my phone vibrated in the whole process as mentioned in big red box.
Since I am noob, I can not decipher this, and with posts less than 10, I can not post in that thread. I will be really thankful if someone expert can flash some light on this.
Is my phone really rooted now?
(P.S. - Don't ask me for phone screenshots, they never work on my phone, with power and volume down button pressed together.)
Thanks a lot in advance.
Click to expand...
Click to collapse
The large red box and the previous content are perfectly fine. There isn't no problem there. The exploits ran fine and the files were pushed to your device. Sometimes the phone doesn't vibrate and in that case my other phone didn't when the tool said it would. But it was rooted.
As you said your phone didn't vibrate but it did reboot right? I assume it did because you didn't mention it not being rebooted.
How do you know if your phones rooted? Go into your app drawer, and if you find an app called. "Superuser or SuperSU" its rooted. But just to be sure its working. Go to the play store, and install and app called "root checker" the icon has a hashtag in it from what I remember.
Run the app and check root. If it prompts you with a window saying vie permission. Grant the permission. And that's means you're rooted. Hopefully I helped. If I didn't answer your question properly please state.
Thanks
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
The large red box and the previous content are perfectly fine. There isn't no problem there. The exploits ran fine and the files were pushed to your device. Sometimes the phone doesn't vibrate and in that case my other phone didn't when the tool said it would. But it was rooted.
As you said your phone didn't vibrate but it did reboot right? I assume it did because you didn't mention it not being rebooted.
How do you know if your phones rooted? Go into your app drawer, and if you find an app called. "Superuser or SuperSU" its rooted. But just to be sure its working. Go to the play store, and install and app called "root checker" the icon has a hashtag in it from what I remember.
Run the app and check root. If it prompts you with a window saying vie permission. Grant the permission. And that's means you're rooted. Hopefully I helped. If I didn't answer your question properly please state.
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you for your quick answer.
Little clarification,
The phone did not vibrate, but the prompt said, to hit any key on laptop to proceed. So I hit the key after waiting for about 2 minutes. And then it rebooted.
There is no Superuser app in app drawer and root checker tells me it is not rooted.
fuzzychicken said:
Thank you for your quick answer.
Little clarification,
The phone did not vibrate, but the prompt said, to hit any key on laptop to proceed. So I hit the key after waiting for about 2 minutes. And then it rebooted.
There is no Superuser app in app drawer and root checker tells me it is not rooted.
Click to expand...
Click to collapse
Then assuming the phone is not rooted. Did your phone boot into bootloader mode when this process took place?
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Then assuming the phone is not rooted. Did your phone boot into bootloader mode when this process took place?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No, never, it just felt like phone was restarting. It took a while to restart compared to when I reboot otherwise, but there was no bootloader mode for sure.
Related
I can't change my Wifi Xoom's orientation. The sensor appears to work when I test it in Elixir 2, and I have the autorotate slide switched on. I've rebooted and turned it on and off many times... I contacted Moto via online chat, but it was like 20 minutes before chat hours ended and the guy Juc stood me up! Like he asked what version of the Xoom I have and I said "I have the wifi version". Then he didn't respond for 30 minutes even after I asked repeatedly if he was still there. Anyone else have any advice? I can't find this problem ANYWHERE ELSE!!!! It's driving me BONKERS! I already tried toggling the autorotation switch and rebooting (volume button and screen lock) and turning it off and on. I also uninstalled my recently updated apps... I'll post a reply for future reference of others if I fix it with a factory restore.
What ROM / Kernel are you using?
All stock. Never rooted. Would rooting work?
Rblacula said:
All stock. Never rooted. Would rooting work?
Click to expand...
Click to collapse
I think it might be worth a try. It's obviously a software problem, so there's got to be a software solution. Rooting and flashing a kernel or rom could do the trick, otherwise you could reinstall your stock images through ADB (as much trouble as rooting IMHO).
I'm just going to play it safe and mail it to them first. I just got finished chatting with them again and they said to mail it to them. I'll wait the 10 or so days if it fixes him...
EDIT: Well, I figured since my support guy made me factory reset it, what harm would an external factory reset do? For some reason, it worked. I just don't understand it! At least I don't have to send him in! I would miss Xoomy too much!
Rblacula said:
I'm just going to play it safe and mail it to them first. I just got finished chatting with them again and they said to mail it to them. I'll wait the 10 or so days if it fixes him...
EDIT: Well, I figured since my support guy made me factory reset it, what harm would an external factory reset do? For some reason, it worked. I just don't understand it! At least I don't have to send him in! I would miss Xoomy too much!
Click to expand...
Click to collapse
I know just what you mean!
I know; I tend to personify my objects such as Xoomy and Nexusy (my Nexus S)! My Xoom is MY LIFE!!!!!!!!!!
Very glad he's fixed, then.
Hi there, I hope you guys can help me out on this.
I just got my HOS a few days ago and it was all good.
Rooted it after 1 day, everything was fine.. at first.
Played a few games, installed themes and so on. After a few hours, my HOS began to vibrate out of nowhere and apps started here and there, menu opens on its own and all that stuff. It was out of control xD
I then saw that theres an update available. Flashed stock recovery and unrooted it. Afterwards, I installed 1.78. Still unrooted, downloading most of my Apps again, works flawless. Gaming(specially Temple Run xD) is smooth.
Yesterday, I decided to root it again. At first no problems at all.
Just now on the train, playing Temple Run again, my HOS started going crazy, vibrating all the time as if it is pressing buttons on its own and I see the phone doing all kinda stuff(opening new apps, browsing thru home screen etc xD).
Has anyone else expierenced something similar? I have no idea where its coming from and it really annoys the hell out of me.
Right now I'm on TrickDroid v3.1 (wiped system/data/dalvik/cache before flashing)
Kernel: 3.0.8-01136-g9d2ad32
Baseband: 0.16.31501S.17_2_10.23.31501S.10L
Build: 1.70.666.1 CL52668
That really is strange !!! Its as if root contains some sort of poltergeist
I would have imagined a factory reset would have cleared it up, But in your case it didnt....
Have you tried an alternative rooting method ?
Nope, I did not. Always used the All-In-One Toolkit, except for when I flashed Trickdroid, since it comes rooted.
Is it ok if I unroot the HOS with Rootkeeper(is this just temp. unroot?) and then root it again with Superboot?
Unbranded HOS bought in Germany, if that matters. Also, no other recovery works for me except Intermin, CWM just won't boot for me.
that is weird...
Unlocking the bootloader was successful right ?
I dont understand why your phone is rejecting software lol.. Oh and I didnt know root keeper can unroot ive never used it..
how i got root was by flashing paul obriens recovery and then the root package zip file.. I did this on day one and have never had any issues at all.. Ive tested every single ROM and every single recovery lol..
Make a nandroid in recovery and just test out different methods and try get this issue fixed. If you have any issues just restore the nandroid..
Check your phone for remote access apps, maybe you got hacked. Most of those require root to function. Also check your google account for which IPs logged in and check the password recovery options for weird emailadresses and phonenumbers...
Ars has a writeup on hardening your android device, not very technical but some good stuff there. http://arstechnica.com/security/201...-smartphone-against-stalkers-android-edition/
Forget whatever i wrote.
My HOS registers my thumb, even tho I'm not touching it at all. If I'm like 5mm away from the screen, it registers it as if I'd touched it. My gf also has a HOS and it acts only if I touch the screen.
I also noticed that the hotter my HOS gets, the distance increases at which it recognized my "touch".
The distant screen touch has happened on my uprooted tmo us HOS. I've also experienced some craziness out of the device. I've kept it stock, no unrooting/rooting going on.
I was thinking an exchange with HTC cause I also have excessive battery drain and wavy lines in the screen but now I also have an awesome cracked screen too :-\
Sent from my HTC VLE_U using XDA
i also dont need to touch my screen to select something
I just hover my finger over the app, real close to the screen and it selects it...
I guess we have special powers
i also dont need to touch my screen to select something
Click to expand...
Click to collapse
Same here.
lets keep this quiet, We dont want people to know we are superhuman...
I cant be arsed with the fan mail from the CIA,,, Nor do i have the time to fight crime and save the world....
Id rather just continue to flash a ROM.
Hello all,
I have an LG G2X P999. I got this phone two days ago, and tried to root it. After watching some videos, I realized the phone was already rooted- Because it had the superuser icon in the menu, as I saw in videos.
Moving along, I downloaded ROM Manager. I flashed CWM and then tried to install the latest stable version of Cyanogen Mod.
After restarting the phone from CWM, it gets stuck at the Second LG Bootscreen.
When I hold the power button + Vol Dwn button, I see the android and the arrow. I realize now, that means CWM isnt really installed.
However, that doesnt help with the issue at hand- I cannot bypass the Second boot screen.
No matter how long I leave it, or any of the methods I try.
I have downloaded the NvFlash package, which contains the program + the apx drivers. However, I am unable to install the drivers, as my laptop wont detect the phone.
I have removed the battery, held both volume buttons and plugged in the USB. Nothing happens.
The computer does not detect the device. Different ports, Different cables, even tried a different laptop. Nothing.
I have done as much research as I can, and all the tutorials have me confident that I know what to do AFTER the device is detected.
But I cannot find any resource, that advises me what to do if the device doesn't even get detected :crying::crying::crying:
Ive read link after link, that has led me back to links that I have already checked.
The only thing I have not done, is ask for help. This is why I am now here.
Please, may I have some assistance. I am at my wits end.
:crying:
:crying::crying::crying:
:crying:
So the only way the phone detects the device, is by putting the battery in - Then holding the power + volume down buttons till it reaches the second LG logo.
Which is where the device freezes. It doesnt pass this boot screen.
It detects it as Unknown Device. Not APX
Also, the phone can charge with the USB. The laptop doesnt detect it while charging.
So I got the phone to go into APX mode.
I did this by having the battery IN the phone.
Plugging the phone IN the laptop.
Holding the power + VOL down buttons. It reset the phone, then went to the second LG boot screen.
I then held the VOL buttons + Power button. Then the laptop detected the device, and APX showed up in Device Manager.
__________
After doing that, I opened NVFlash, and clicked "Flash CWM 5.0.2.0 Internal and Exernal ....."
The process ws successful and then the phone went to "S/W Upgrade Please wait."
I do not know WHO said the battery NEEDS to be out or WHY they said that, but those instructions are NOT ACCURATE.
The battery does not NEED to be taken out to do this process, I have now gotten my G2x into CWM using NVFLASH, WITH the battery IN the phone.
This little detail has caused heartache to many G2X owners, including myself.
I have the remedy, my friends!! Leave the battery IN the phone!! It WILL WORK!!
Someone please make this a sticky, OR add these instructions to the original NVFlash Method.
The public needs to know.
I hope my journey will help many others, peace and love to you all.
You are incorrect. But whatever...
Sent from my glorified LG pet rock™
justjackyl said:
You are incorrect. But whatever...
Sent from my glorified LG pet rock™
Click to expand...
Click to collapse
My friend, what I have posted are the steps I took to get my g2x working; That is what worked for me, fact.
I am now running weapon g2x 3.0_R1; flawlessly, might I add. Praise to the developers.
I'm sorry you felt your disapproving opinion was necessary.
itskingruss said:
I do not know WHO said the battery NEEDS to be out or WHY they said that, but those instructions are NOT ACCURATE.
Click to expand...
Click to collapse
This is what you said and is incorrect.
This has worked for me and countless others and a statement like this can throw off a new user. Occasionally, directions will need to be altered and most often when they do it is due to operator error resulting in straying away from said original directions.
You should not state that these directions are "not accurate" , but rather should state something along the lines of "I ran into problems and got it to work trying this way, just an idea if someone else gets stuck."
But the original directions work correctly.
But it's cool man, I've only been modding this phone for a year now. Your solid 3 days of ownership have far surpassed that.
Sent from my glorified LG pet rock™
I got stuck in that same boot loop following some video on YouTube just this past weekend! ha-ha...
Glad I'm not the only one
Nvflash worked flawless with for me with battery out
Sent from my LG-P999 using xda app-developers app
JA1983 said:
I got stuck in that same boot loop following some video on YouTube just this past weekend! ha-ha...
Glad I'm not the only one
Nvflash worked flawless with for me with battery out
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Sent from my glorified LG pet rock™
justjackyl said:
This is what you said and is incorrect.
This has worked for me and countless others and a statement like this can throw off a new user. Occasionally, directions will need to be altered and most often when they do it is due to operator error resulting in straying away from said original directions.
You should not state that these directions are "not accurate" , but rather should state something along the lines of "I ran into problems and got it to work trying this way, just an idea if someone else gets stuck."
But the original directions work correctly.
But it's cool man, I've only been modding this phone for a year now. Your solid 3 days of ownership have far surpassed that.
Sent from my glorified LG pet rock™
Click to expand...
Click to collapse
Lmao when I read this I died, I tried the OP's way to make sure I had something to back me up incase I ever felt like hating on him and strangely for me both the OP's and the original way works for my G2X
Lol who cares, happy you got your phone working op
Sent from my LG-P999 using xda app-developers app
Hello everyone!
I just got my Verizon HTC M8 and was wondering if anyone else is experiencing these (possible) issues:
On Firmware 1.55.605.2-1.12.605.11_R3 , when I press "Check new" under "Software update", it sits for about a minute at "Checking for new software..." and eventually says "We were not able to download this update....". Does this mean there is an update and it's failing to download, or is this just their (stupid) way of saying "Nothing to see here".
BoomSound causes hissing while on. To replicate, start a Youtube video, and pause it. In the short time between you pausing and the BoomSound notification icon disappearing, the speaker will have an amplifier hiss to it. If you have a good ear, you can hear this during playback in the background.
Occasional WiFi hiccups - I've had this on every android device so far, but every once in a while the WiFi just stops working and I have to toggle it off/on.
Constant "Youtube stopped working"... at least a couple times a day I'll get this warning. Seems this is the only app.
Also, is there any way to restore the things Verizon removed (http://forum.xda-developers.com/showthread.php?t=2729137) without root? Specifically HTC Backup?
Thanks! My 2 week return ends this coming Sunday, so I was just making sure I shouldn't try to get it replaced before that
I've had my m8 for a week now and the only issue I have Is a loose volume rocker. But with a case on it's fine. I'd get yours replaced personally.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Anthony825 said:
I've had my m8 for a week now and the only issue I have Is a loose volume rocker. But with a case on it's fine. I'd get yours replaced personally.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ya, I have the loose buttons too... just wiggles enough to be annoying, but the case resolved that for me as well. As much as I wanted to go caseless, I'm too clumsy
Does yours show the same thing when trying to software update?
I've noticed the hissing too. Happens in the ear phones too or especially in calls. For YouTube, uninstall updates an reinstall. Reboot device. I had those issues too.
Zero issues to report.
Sent from my HTC6525LVW
@jacob_s your question has been moved to the device Q&A section. Please be sure to post in the correct location, as this ensures the best responses:good:
Thank you,
TonyStark said:
@jacob_s your question has been moved to the device Q&A section. Please be sure to post in the correct location, as this ensures the best responses:good:
Thank you,
Click to expand...
Click to collapse
Thanks - sorry about that.
So, can anyone confirm the update issue? My biggest concern is that I tried weeksauce but it didn't do what I needed. I want to be sure that I can still get OTA.
jacob_s said:
Thanks - sorry about that.
So, can anyone confirm the update issue? My biggest concern is that I tried weeksauce but it didn't do what I needed. I want to be sure that I can still get OTA.
Click to expand...
Click to collapse
If the update continues to be a problem, you might need to do Weaksauce temporarily and download the official OTA and put it in the right place and manually update your phone. There were a few threads covering this. It is really simple to do.
There are a few options in the phone that cut connection to Wi-Fi, so go check these under Settings:
-Wi-Fi>Then hit the three dots in the top right corner and choose Advanced>and take a look at the "Keep Wi-Fi on during sleep" option.
-Power>and then check out your "Sleep mode" options and, if your phone has it, the "Power saver" options.
I haven't personally heard any issues with my speakers due to BoomSound, so I can't really help there. If none of this helps, I would say go and have your phone swapped out.
If you checked this all already, I'm sorry! Good luck man. This phone is a beast and I hope you get it working. :good:
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Ashleyware said:
Hello xda, I have a problem!
My Nexus 5 is only six months old and aside from typical Nexus 5 shenanigans (the camera seizing upon lock, requiring a reset) it has worked fine. (though I have been very discontent with this device) Last night I was using my Nexus 5 as usual and I was tired, but too lazy to plug it into the charge port. By morning my phone died as expected, so I plug the charger in and lo-and-behold, it's stuck in boot up.
So naturally I freak the f*** out; I wait. To no avail.
I wait some more. Nix.
It's still f***ing booting.
So I know something's wrong with my phone and I said "f*** it; I'm just going to factory reset it" because knowing my luck, my phone decided to say "f*** you" and kill itself the night prior. (My affinity with technology is poor.)
So I wipe the damn thing.
I boot it up.
Loop. You've got to be kidding me.
I wipe the cache (don't tell me I should have done this first); nada.
I get flustered, chuck the black pice of s*** down the stairs, get desperate, pick it back up, take it to work with me (while it was still booting), I left for work at 12:00PM, it's now 7:04PM, I'm home and it's STILL BOOTING.
So what's a girl to do?
And I'm going to answer the fusillade of questions I know I'm going to get in response to my peril, so before you all premeditate; here's what I've done to my phone:
I rooted it THREE WEEKS AGO with KingRoot to turn off my proximity sensor. Why? Because I Skype and like to use my device at the same time, and Microsoft thought it would be brilliant to have the screen shut off any time something crosses slightly in front of the Nexus 's two stupid sensors, so horizontal use of the device gets thrown out of the window. (if any muppets at Microsoft are reading this, you're f***ing idiots! If I really wanted to turn my screen off to conserve battery power, I would lock the f***ing screen! I don't need YOU nannying me!)
I wasn't able to shut off the proximity sensor with root permissions so I got cheesed and unrooted, then uninstalled the application.
Things have been working perfectly fine. (And yes, my phone has been rebooted in that three week span.)
Up until last night, my phone was working perfectly normal. I did what I usually did.
Listened to music, checked my work schedule, text, watched YouTube videos, played Gameboy games on an emulator, and that's it.
Someone please help me with this phone so I can at least fix it and sell the wretched thing to some muppet for some money to put towards a REAL phone.
Thanks.
~ Ashley
And it finally died, just as I finished writing this.
Click to expand...
Click to collapse
Since you've already wiped data, have you tried unlocking the bootloader and flashing the Google factory image
I haven't because I can't. I'm on a Macbook and the Nexus 5 drivers aren't compatible with Macs apparently =/
Wait okay, so I misread what I looked at this morning.
So it says I have to flash a new rom to my phone O.K. but every website says I have to turn on USB debugging--how am I supposed to turn on USB debugging to unlock the bootloader if my phone is bricked to begin with? This doesn't make any f***ing sense!
HELP.
Also, my Mac doesn't recognize my device in fastboot mode; what am I supposed to do?!
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
ldubs said:
Try this? It has Mac instructions too.
http://forum.xda-developers.com/showthread.php?t=2513701
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------
I was able to unlock my bootloader on my Mac with no problems...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Don't you understand? I can't enable USB debugging because I can't ACCESS my phone! It's stuck in bootloop! I can't unlock the bootloader to begin with! Unless you know how to unlock the bootloader from the fastboot menu, you saying that you unlocked your bootloader doesn't help me. I tried everything in that thread and nothing works, I tried the terminal bull**** and the only thing that happens as I can get into the folder where the factory rom is, but I can't get it to flash, I can't get anything to happen--I don't know what the hell I'm doing.
Is there a way to start over without all of this stupid bootloader crap?
As far as I know ADB is not active in fastboot, it is not recognized. In fact I just flashed TWRP again with ADB off. You do need the fastboot drivers on your Mac installed correctly but that's no big deal. If you have access to your phone in fastboot it is simply fastboot oem unlock to unlock your bootloader.
PROGRESS REPORT
So last night I stayed up trying to fix my issue, and I've had no success. I've managed to flash back to Kitkat 4.4.4 but as soon as the phone boots into set up, immediately I get the error messages "unfortunately Camera has stopped working", "unfortunately Gallery has stopped working", and "unfortunately Google Playstore has stopped working". After setting up, my phone has NO service! It doesn't even recognize if there's a SIM card even inserted, or if I remove it.
I cannot open Playstore, it immediately crashes and my phone believes that it has no storage now, even though I see 12GB of space free. I tried flashing multiple roms and nothing beyond Kitkat will work, otherwise I get caught in a bootloop.
I tried installing Cyanogen mod and although it worked, I had the same issue--no service, no Playstore no storage.
I tried clearing the cache, the Dalvik and factory resetting several times and nothing works. I just flashed 4.4 and I'm updating it to 4.4.3 as we speak.
Also I think it's worth mentioning that every time I got caught in bootloop after flashing a new rom (and I tried all of them, including Lolipop, which always hangs) that when I boot in Recovery mode it says something along the lines of:
Invalid arguement couldn't mount blahblahblahgeniusspeak
Invalid arguement blahblahblahgeniuspeak
and so on. Does this have something to do with my lack of service, camera not working, Playstore not working and storage not working? I'm desperate people.
Have you got an imei number?,settings/about phone
Usually you just flash factory ROM, extract the file and then the second archive and flash each individual file and it should boot, factory reset and wipe cache to fix storage
I do this on my mac
If you can't do this then you may have a hardware issue
How did you try to turn off proximity sensor. There would be another way to keep screen on while skyping (keep screen on wake lock)
Also it sounds like you flashed custom roms without flashing gapps...
Sent from my Nexus 5 using Tapatalk
Definitely sounds like no gapps.
What's gapps? And I have no IMEI number (unknown), it says my (with my SIM inserted) Network is: Unknown
Mobile Network Type: Unknown
Mobile State is disconnected
Out of Service
Phone number is unknown
IMEI SV is unknown
IMEI is unknown
Not roaming either
What's the second archive? Every guide I used said use the flash-all.script and that's all you have to do, what're all these extra steps? How do I flash gapps, I don't even know what that is; I don't see the file anywhere in the factory image folder.
=/
I flashed again (back to stock; 4.4) and did everything manually instead of using the script, I even flashed the cache.img, recovery.img etc . . . and it's still the same issue. No service. No external storage available. No Google Playstore.
=/
I didn't flash a custom rom, I only flashed the official factory image from Google. Why doesn't anything ****ing work.
Is gapps going to return my storage and service?
Gapps is only for custom ROM. Since your imei etc is unknown seems like you have bad efs partition. I am not 100% sure. May be others can help.
Sent from my Nexus 5 using XDA Free mobile app