I was checking to see if everything is working ok with fastboot before upgrading to 4.4.4, I need to confirm with XDA whether everything is ok. I open a command prompt in my platform tools folder and I type in adb devices and it shows my Nexus 5. When I type in Fastboot it does nothing. If I type in fastboot fastboot devices it says "waiting for device." When I boot into the bootloader and type in the command, it shows the device serial. Am I ok to proceed first of all?
Second, I thought you could run fastboot devices inside the command prompt while the Nexus is not in the recovery? Is this incorrect?
Matthewlawson3 said:
I was checking to see if everything is working ok with fastboot before upgrading to 4.4.4, I need to confirm with XDA whether everything is ok. I open a command prompt in my platform tools folder and I type in adb devices and it shows my Nexus 5. When I type in Fastboot it does nothing. If I type in fastboot fastboot devices it says "waiting for device." When I boot into the bootloader and type in the command, it shows the device serial. Am I ok to proceed first of all?
Second, I thought you could run fastboot devices inside the command prompt while the Nexus is not in the recovery? Is this incorrect?
Click to expand...
Click to collapse
adb and fastboot are 2 completely different things, you cant fastboot in adb. fastboot is used ONLY while in the bootloader.
So if I'm seeing the serial when I type "abd devices" in devices and when I type "fastboot devices" in recovery, I should be fine?
Matthewlawson3 said:
So if I'm seeing the serial when I type "abd devices" in devices and when I type "fastboot devices" in recovery, I should be fine?
Click to expand...
Click to collapse
fastboot doesnt work in recovery.
Sorry I meant fastboot devices in the fastboot mode in the bootloader. I should be ok?
Matthewlawson3 said:
Sorry I meant fastboot devices in the fastboot mode in the bootloader. I should be ok?
Click to expand...
Click to collapse
yup
So here is my approach to upgrading to 4.4.4. I did this 4.4.3 and it worked fine for me without me losing data. I am going to extract from the factory .TGZ image.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Does this sound like an ok process for me to upgrade without losing data?
Matthewlawson3 said:
So here is my approach to upgrading to 4.4.4. I did this 4.4.3 and it worked fine for me without me losing data. I am going to extract from the factory .TGZ image.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Does this sound like an ok process for me to upgrade without losing data?
Click to expand...
Click to collapse
sure, should be fine. but im a bit lazier when it comes to these things. im assuming that you are running a stock rooted rom? all i would do, personally, would be to find a stock rooted rom in the n4 android development section, and dirty flash it over what i have, dirty meaning no wiping a thing. that way you upgrade and dont lose anything. i actually did that. i was running rastakat(a aosp rom) and dirty flashed stock 443 over it. later on, when it was ready, i dirty flashed rastakat 443 over stock(then 444). rastakat and stock are similar, so i had no issues dirty flashing
simms22 said:
sure, should be fine. but im a bit lazier when it comes to these things. im assuming that you are running a stock rooted rom? all i would do, personally, would be to find a stock rooted rom in the n4 android development section, and dirty flash it over what i have, dirty meaning no wiping a thing. that way you upgrade and dont lose anything. i actually did that. i was running rastakat(a aosp rom) and dirty flashed stock 443 over it. later on, when it was ready, i dirty flashed rastakat 443 over stock(then 444). rastakat and stock are similar, so i had no issues dirty flashing
Click to expand...
Click to collapse
n4 ROMs eh?
Just teasing. ??
KJ said:
n4 ROMs eh?
Just teasing. ??
Click to expand...
Click to collapse
n5 as well. except i skipped the stock step, as i was waiting to start development on the trinity 443/444 kernel(im part of trinity kernel). when we were ready to start development of it, rastakat updated the rom. so it was just a dirty custom rom flash over the same rom
I've never tried Trinity....its a performance leaning kernel right? I've seen your impressive benchmarks. Lol
Its the only one I'm ascared to try....cause I'm a mega battery life buff.
KJ said:
I've never tried Trinity....its a performance leaning kernel right? I've seen your impressive benchmarks. Lol
Its the only one I'm ascared to try....cause I'm a mega battery life buff.
Click to expand...
Click to collapse
its actually a pro user experience kernel, just happens that performance is part of it
simms22 said:
its actually a pro user experience kernel, just happens that performance is part of it
Click to expand...
Click to collapse
I'm not a pro. Lol
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
4 cores running. If I can't get 24 plus hours and 6 hours SoT....on out. Lol
Obviously a great choice for gamers and heavy multi taskers. ?
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Sorry for the off topic BTW. Lol. ?
KJ said:
I'm not a pro. Lol
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
4 cores running. If I can't get 24 plus hours and 6 hours SoT....on out. Lol
Obviously a great choice for gamers and heavy multi taskers. ?
Click to expand...
Click to collapse
pro as meaning for
i get 4.5-5.5 hours sot at 2265mhz/300mhz, and dont do anything to get better battery. granted, my signal quality here in nyc is exceptional(which plays a role in battery life). the using all 4 cores constantly is deceptive. really, the only difference is whether it hotplugs or not. normally it does, trinity doesnt. when hotplugging, the cores are constantly being turned off and on, constantly. trinity doesnt waste the time turning them on and off constantly. this saving time is also saving little bits of battery. everything else works the same, itll only use 2 cores if it wants to, like normally. it just wont turn off the other 2. this also has a side affect of added snappiness
simms22 said:
pro as meaning for
i get 4.5-5.5 hours sot at 2265mhz/300mhz, and dont do anything to get better battery. granted, my signal quality here in nyc is exceptional(which plays a role in battery life). the using all 4 cores constantly is deceptive. really, the only difference is whether it hotplugs or not. normally it does, trinity doesnt. when hotplugging, the cores are constantly being turned off and on, constantly. trinity doesnt waste the time turning them on and off constantly. this saving time is also saving little bits of battery. everything else works the same, itll only use 2 cores if it wants to, like normally. it just wont turn off the other 2. this also has a side affect of added snappiness
Click to expand...
Click to collapse
Well, I always say I'll get similar fantastic battery times on any rom or kernel out there. (When I hear "what's the best rom or kernel for battery" I cringe....Lol)
I'll give trinity a whack and see how it goes. Like I said, I've never tried it. And I like to try everything!
I'll give it a good few days, see how it feels.
Thanks my friend! ?
KJ said:
Well, I always say I'll get similar fantastic battery times on any rom or kernel out there. (When I hear "what's the best rom or kernel for battery" I cringe....Lol)
I'll give trinity a whack and see how it goes. Like I said, I've never tried it. And I like to try everything!
I'll give it a good few days, see how it feels.
Thanks my friend! ?
Click to expand...
Click to collapse
omg, me too. i get the exact same battery life on every kernel ive tried. and i tell people all the time, kernels make little difference, unless its a terribly coded kernel. but, as you know most of the average users dont know, and are on the constant search for the magic pill. i admit, once a bit back, i was one on the search as well(but learned). but it doesnt exist. most of the "magic pill" really depends on them themselves or the quality of the data/phone connection around them.
and on another part, i dont push trinity kernel onto people. i used to, not anymore. because it doesn't matter. people should always use whats they enjoy most and what their phones like best. thats whats important. trinity(like rastakat) is made for us and our friends to enjoy. just happens that we enjoy sharing it as well. if someone wants to use it, they are more than welcome. if not, that's cool as well
simms22 said:
omg, me too. i get the exact same battery life on every kernel ive tried. and i tell people all the time, kernels make little difference, unless its a terribly coded kernel. but, as you know most of the average users dont know, and are on the constant search for the magic pill. i admit, once a bit back, i was one on the search as well(but learned). but it doesnt exist. most of the "magic pill" really depends on them themselves or the quality of the data/phone connection around them.
and on another part, i dont push trinity kernel onto people. i used to, not anymore. because it doesn't matter. people should always use whats they enjoy most and what their phones like best. thats whats important. trinity(like rastakat) is made for us and our friends to enjoy. just happens that we enjoy sharing it as well. if someone wants to use it, they are more than welcome. if not, that's cool as well
Click to expand...
Click to collapse
Completely agree with first paragraph. Exactly!!
And if you get good battery life on anything, trinity included....then I've had the wrong idea about it. Gonna flash it when I get a chance.
Related
Hello
I was wondering if anyone has been using the Viewsonic VSD220 yet? It's the 22" tablet/screen running ICS.
I went to manufacturer's site to download drivers to use as part of Bin4ary's instructions on this thread: http://forum.xda-developers.com/showthread.php?t=1886460 in trying to root the device but there are no drivers available.
Anyone has any ideas on how to go about getting drivers or find other means of rooting the device? My intention is to overclock the OMAP4430 from 1Ghz to maybe as high as 1.2Ghz.
TY
garrek99 said:
Hello
I was wondering if anyone has been using the Viewsonic VSD220 yet? It's the 22" tablet/screen running ICS.
I went to manufacturer's site to download drivers to use as part of Bin4ary's instructions on this thread: http://forum.xda-developers.com/showthread.php?t=1886460 in trying to root the device but there are no drivers available.
Anyone has any ideas on how to go about getting drivers or find other means of rooting the device? My intention is to overclock the OMAP4430 from 1Ghz to maybe as high as 1.2Ghz.
TY
Click to expand...
Click to collapse
I would like to root the device as well in order to change LCD density as the default seems unappropriate for a screen of that size.
I'm looking for an answer here too ...
sagsg said:
I would like to root the device as well in order to change LCD density as the default seems unappropriate for a screen of that size.
I'm looking for an answer here too ...
Click to expand...
Click to collapse
What exactly do you mean by pixel density?
I had some issues with the screen as well but worked it out through configurations.
Video card drivers plus Windows text clarity tools improved things a lot.
I would also like to root it, as it seems not to support mass storage out the box... Other than that, I am quite pleased with it so far
garrek99 said:
What exactly do you mean by pixel density?
I had some issues with the screen as well but worked it out through configurations.
Video card drivers plus Windows text clarity tools improved things a lot.
Click to expand...
Click to collapse
With LCD Density I mean what most (windows) users would refer to display resolution. It has a native Full HD Display with 1920x1080.
Unfortunately, by default everything is scaled up in an 1:2 factor. This means that a webpage displayed in the browser that has actually a width of ~950pixel takes the full screen width on the VSD220. This may be good if a 10" screen with full HD does that, but not on a 22" screen.
Anyone found recovery mode yet as well - usually involved another button as well as power on a phone/tablet but there only is the power button!
This can root, just don't do the 1.1 OTA update!
http://forum.xda-developers.com/showthread.php?t=1886460
As long as you don't have the 1.1 update this will work to root the vsd220...
If any of you have the firmware or know how to recover to 1.0 I'd love to, I miss using titanium backup and droidmote amongst others...
The google generic adb drivers worked for me btw...
Ah, sorry just done the update. Took ages, messed up my config and stopped sleeping etc so had to fully reset! What a great update!!
Not really noticed any fixes - still very slow, can't use most apps on play etc etc.
Probably going to swap to a Minix Neo X5 and an old Acer T231HL Touchscreen that I picked up and have been messing with, works pretty well, much faster!
adrenalize_: Yeah update was a giant **** around :S You can get to recovery mode though, just have to use adb and send adb reboot recovery... can't access the recovery menu at all or anything like that though and there are no firmware images available for the vsd220 anywhere :S
OP and people trying to root the VSD220, I have accomplished root on both versions 1.0 and 1.1. Please go to my post http://forum.xda-developers.com/showthread.php?p=38438216#post38438216 and feel free to ask questions or if you need better instructions.
Thanks sk8tingusmc, although I had to use fastboot boot recovery.img instead of fastboot flash recovery recovery.img I finally managed to get my monitor rerooted (I'm not allowed to post on the topic you created though, sorry for the mislocated post) and now I've frozen system update so I shouldn't have to worry about that pile of stupid again Now if only they had actually released either the original firmware or a better update that fixed some problems (I hate having to restart my monitor just because it got froze in sleep or the touchscreen no longer works for windows or... ).
Yeah the locked in sleep is a real pain! Silly silly Viewsonic!
I'm onto customer support at the moment, trying to tease V1.0 out of them so I can restore it at home but they are saying it needs to be returned to their service center for it to be done. You'd kind of hope they would release a very quick update to fix it - I'm assuming it affect all units?
TJ_Hooka said:
Thanks sk8tingusmc, although I had to use fastboot boot recovery.img instead of fastboot flash recovery recovery.img I finally managed to get my monitor rerooted (I'm not allowed to post on the topic you created though, sorry for the mislocated post) and now I've frozen system update so I shouldn't have to worry about that pile of stupid again Now if only they had actually released either the original firmware or a better update that fixed some problems (I hate having to restart my monitor just because it got froze in sleep or the touchscreen no longer works for windows or... ).
Click to expand...
Click to collapse
Hey no problem, that is odd I could have sworn I used fastboot flash recovery recovery.img. Maybe the install-recovery.sh flashed the stock recovery before you had a chance to reboot into recovery. I will try to compile some custom roms but I have very little free time. Also I haven't used my monitor for long periods of time and have only had it for a few days so I have not had any of those symptoms yet. How long is it asleep before freezing?
---------- Post added at 11:49 AM ---------- Previous post was at 11:42 AM ----------
adrenalize_ said:
Yeah the locked in sleep is a real pain! Silly silly Viewsonic!
I'm onto customer support at the moment, trying to tease V1.0 out of them so I can restore it at home but they are saying it needs to be returned to their service center for it to be done. You'd kind of hope they would release a very quick update to fix it - I'm assuming it affect all units?
Click to expand...
Click to collapse
I made a nandroid and image.zip of version 1.0 if you are interested.
It seems that if the device sleeps itself - or if you quickly press the power button to sleep then when you press the power button to make it wake up it turns green for a few seconds then goes back to amber.
I've just found that if I leave an app open - like Tune in Radio the sleep works OK but if you go back to the home screen then sleep - well sleeps forever. I have turned off the sleep option to stop it happening then but we usually just sleep the screen when going out etc especially as it takes so long to boot.
Thanks for an offer of the image.zip I guess I might give it a go to save returning the hassle of returning the display! (I've used 4shared for things like that in the past)
Should the image be flashable using fastboot (after oem unlock and rebooting to the bootloader) or can it only be done from cwm?
adrenalize_ said:
It seems that if the device sleeps itself - or if you quickly press the power button to sleep then when you press the power button to make it wake up it turns green for a few seconds then goes back to amber.
I've just found that if I leave an app open - like Tune in Radio the sleep works OK but if you go back to the home screen then sleep - well sleeps forever. I have turned off the sleep option to stop it happening then but we usually just sleep the screen when going out etc especially as it takes so long to boot.
Thanks for an offer of the image.zip I guess I might give it a go to save returning the hassle of returning the display! (I've used 4shared for things like that in the past)
Should the image be flashable using fastboot (after oem unlock and rebooting to the bootloader) or can it only be done from cwm?
Click to expand...
Click to collapse
Actually the nandroid backup is the only way I can revert back to v1.0 is the Android, the boot loader/kernel does not allow modifications to just the system. The best thing we can do is try to do a safestrap. Since there is only one button flashing a kernel or bootloader would be to risky, if you can't boot in you can't adb reboot recovery. I have been able to boot a boot loader from an sdcard but I haven't found a bootloader/kernel combination that has worked yet.
I had to edit my last reply, I posted from smartphone and it auto corrected my words.
Any idea where i might find windows adb drivers for vsd220?
quadraxas said:
Any idea where i might find windows adb drivers for vsd220?
Click to expand...
Click to collapse
Either go here and follow the steps starting at the device manager step if SDK is already installed. If not start from beginning. Or set up an android environment on a Linux distro.
Got this rooted now. Any advice on best lcd density, tweaks, overclocking etc to make this thing more usable? What app can I use to hide the status bar?
Sent from my GT-N7105 using xda app-developers app
image.zip
I'm looking for firmware version 1.0 image.zip. After the update, the touch is totally f****** up. The touch is out of sync. Can anyone give me this version? I can give you a dropbox upload folder if needed.
Kind regards,
Pieter
---------- Post added at 10:05 AM ---------- Previous post was at 09:54 AM ----------
sk8tingusmc said:
Hey no problem, that is odd I could have sworn I used fastboot flash recovery recovery.img. Maybe the install-recovery.sh flashed the stock recovery before you had a chance to reboot into recovery. I will try to compile some custom roms but I have very little free time. Also I haven't used my monitor for long periods of time and have only had it for a few days so I have not had any of those symptoms yet. How long is it asleep before freezing?
---------- Post added at 11:49 AM ---------- Previous post was at 11:42 AM ----------
I made a nandroid and image.zip of version 1.0 if you are interested.
Click to expand...
Click to collapse
I'm looking for this firmware, after the update my screen is totally out of sync.
So I sold an unopened, sealed Nexus 5 to someone last night and he's having a problem activating the device.
Here is his description of what happened:
"I popped in the SIM card, the loading proceeded as normally. It said it was activating and then a box popped up saying that "android is upgrading system files" or something like that. It restarted and went back to the language selection screen. I pressed English, next and then it went to the connect to wifi screen, froze and then restarted before I could even connect. Now it just loads on the boot"
I had him boot into recovery and do a factory reset, but the result is the same. I had him do a 2nd factory reset just be sure, but again, same result.
My thought is the system upgrade didn't happen correctly and not is corrupted.
What's the best course of action? Can I use the WugFresh toolkit to flash stock and unroot, or would I have to do it through ADB since the phone can't boot into the system?
I don't want to leave the buyer hanging, he seems like a nice guy, but I'm just not sure how to proceed?
Use ADB and flash the factory image for him.
Synyster06Gates said:
Use ADB and flash the factory image for him.
Click to expand...
Click to collapse
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
SeanPlunk said:
That's what I figured. I'm not super familiar with ADB but can figure it out I'm sure.
Click to expand...
Click to collapse
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
switchfo0t said:
Easy walkthrough:
1) Install ADB drivers (You can do it with WUG Toolkit).
2) Reboot your device in Fastboot mode (Hold up/down volume and power)
3) Download the latest HAMMERHEAD image from google website.
4) Download the Google SDK (not needed, but you will need Fastboot.exe, so I would recommend downloading the whole thing)
5) Unzip the image (.tar or .tgz I think) to the location where Fastboot.exe is (all the files should be in the same directory, usually platform-tools)
6) Double-click on the flash-all.bat file from the unzipped .tar or .tgz folder, should install stock image on your phone (note that you might need the latest version of Java installed on your computer)
And you're done.
Hope it helped!
Click to expand...
Click to collapse
Hello, I am the buyer of this Nexus device. I was able to successfully do these steps above, and reload the stock image for the Nexus 5. However, I am still running into issues.
WITH SIM:
I was able to get to the home screen after the initial setup, sent a few test text messages to my Google Voice number successfully, and browse on Chrome for a little bit before the device froze and restarted. After it restarted, I let it load up again, tried setting up my Google account on the device, then it froze again. All of the freezing happens within 3-5 minutes of using the phone.
So I decided to go into the bootloader, and do a factory wipe/cache wipe, and proceed without having the sim card in. I was able to get to the wifi selection screen, select my router, but as soon as the keyboard was suppose to pop up, the device froze and restarted. I am now just stuck on the welcome screen.
Any ideas now?
---------- Post added 29th November 2013 at 12:45 AM ---------- Previous post was 28th November 2013 at 11:56 PM ----------
Update: So I'm not sure what happened, but I ended up locking the device through Wug's Nexus Toolkit, inserted my sim card, and proceeded to set up the phone normally. So far everything has been working perfectly fine. I can receive/send texts, make and receive calls, and do normal functions with the phone without it locking up and restarting. Fingers crossed it'll stay like this.
Any idea on why this would've happened in the first place with the device?
---------- Post added at 01:38 AM ---------- Previous post was at 12:45 AM ----------
Update 2: Well, I noticed that it will randomly reboot every half hour or so it seems. It's kind of random, but I'm not sure what else could be causing these random reboots. The phone itself is working fine, but I just started experiencing random restarts.
Are you still on the stock rom or custom?
neomorphix said:
Are you still on the stock rom or custom?
Click to expand...
Click to collapse
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
---------- Post added at 01:49 AM ---------- Previous post was at 01:48 AM ----------
Jaybot said:
Stock. I did the steps above and flashed the stock rom that I downloaded from Google's website.
Click to expand...
Click to collapse
It was working fine earlier. I put it on the charger and got it to about 50%, used it for a little bit, then bam. It froze, and restarted all over again. I can use the phone maybe 5 - 10 minutes before it starts to recharge. Sometimes It'll automatically reboot after even unlocking the device.
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Jaybot said:
I will try factory and cache wipe again, and see if that does anything with no apps or anything else installed, and go from there.
Click to expand...
Click to collapse
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
neomorphix said:
Sorry its happening. With everything stock and no third party apps or mods there to cause it at least to me things start looking like something bigger might be wrong here.
Click to expand...
Click to collapse
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Jaybot said:
I think so too. No go after another factory wipe/cache wipe. It reboots automatically after awhile. I haven't had this kind of issue before, so I'm not sure what is causing it.
Click to expand...
Click to collapse
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
neomorphix said:
Yeah im kindof at a loss here as well. I have had those issues before but they have always been due to something I have added thats messing things up. I am interested to see if anyone else has any ideas.
Click to expand...
Click to collapse
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Jaybot said:
I figured it would be a sim card issue since it was working for awhile without the sim, but I did the factory/cache thing without the sim card, signed on via wifi, but it still doesn't work. So I am seeing what my options are from here. Thanks for all the tips everyone.
Click to expand...
Click to collapse
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Jaybot said:
I was going to try and do that earlier. I will try and do that now, but I can't even get past the bootscreen animation at this point. The 4 dots will do the animation, freeze, and just reboot.
I'll keep trying. But, I really think this is just a defective one. I had a white Nexus 5 a few weeks ago and didn't have any of these issues :crying:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
Ok. This just sucks. But as with any mass produced product there is bound to be the ocasional issue.
neomorphix said:
For some reason I wasnt thinking of this earlier. Can you capture a logcat from the device after a reboot and post that here. Should help track down the problem.
Click to expand...
Click to collapse
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
theesotericone said:
Honestly it sounds like it's hardware related and time for RMA. OP If you do have ADB set up grab the last_kmsg right after the reboot.
Code:
adb pull /proc/last_kmsg
I doubt it will show any kernel panic but it's worth a shot.
Click to expand...
Click to collapse
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Jaybot said:
Edit: My last restart the phone kept vibrating like crazy before restarting.
Click to expand...
Click to collapse
neomorphix said:
From the sound of it he is now not even getting far enough to be able to pull it. I also think RMA is the best option here.
Click to expand...
Click to collapse
Just saw that. OP by your earlier symptoms I rules out a stuck power button. With the new info I'd look into it further. If the phone is just looping over and over it could be a stuck power button, Mash the power button repeatedly for a minute. Then try and reboot. A few other people have had this on the N5 already and it's a notorious issue on some Samsung phones.
neomorphix said:
I would do another factory reset and use it for a bit without any additional apps installed. If you are fully stock and locked with this happening I would think about possibly doing an RMA. Also just and FYI make sure you have the seller of your phone call and transfer the warrenty to you so if an RMA is needed you have the ability to do so.
Click to expand...
Click to collapse
If it comes to that, how do I go about transferring the warranty over?
I feel really bad, I just don't get it. I bought two of them, the other buyer hasn't had any problems. Both brand new, sealed, in the box. Go figure.
Every time I try to flash the OTA update, it first asks me if I want to install the untrusted zip, which doesn't make much sense, because why would an OTA be untrusted?
Then, during the installation, it aborts for some reason. After that it asks if I want to fix root.
I have no idea why any of this is happening, but I can't install the update because of it. What should I do?
Sent from my Nexus 5 using Tapatalk
There should be a reason in recovery why it failed. We'd need to know it before we can help
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
CarpeNivem said:
For me at least (I didn't start this thread), it fails because Roboto-Bold.ttf contains unexpected content.
I don't recall ever changing Roboto-Bold.ttf, so I have no idea what about it is unexpected.
Click to expand...
Click to collapse
It's a non standard font installed by something. If you have anything non standard on your phone the ota will fail
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
CarpeNivem said:
Thank you. I understood that.
What I meant to say is, how do I correct it? Where can I find a copy of Roboto-Bold.ttf that the update will be "expecting"?
And then, if/when it complains about another file being unexpected, where did I find THAT? etc, etc.
Click to expand...
Click to collapse
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
CarpeNivem said:
Those instructions include "attach phone to computer while phone is in fastboot mode".
However, when I do that, when I attach my phone to the computer while in fastboot mode, my Nexus 5 is NOT SHOWN when I type "adb devices" OR "fastboot devices".
When my phone is in recovery mode, and I type "adb devices", then it IS shown. Additionally, if my phone is fully booted up as normal, if I type "adb devices", it IS shown then too.
But if there are things which need to be done from the computer at the command prompt (and it seems that there are) while the phone is in fastboot mode, well, I cannot do those things, as my device doesn't seem to recognized at all while in that mode.
Click to expand...
Click to collapse
Google tool adb fastboot drivers xda. Use that to get the drivers working with fastboot
jd1639 said:
You need to read this http://forum.xda-developers.com/showthread.php?p=47369234. Basically you need to flash the stock system.img
Click to expand...
Click to collapse
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
kehlan said:
Will that do anything to root access?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
After taking the ota you'll have to re-root
I think it's finally happening. I think I'm finally done. I'm successfully running 4.4.2 on my rooted Nexus 5. Thank you so much for the help (especially since this isn't even my thread; it just had a title which aligned perfectly to my problem, so hopefully the OP was helped along the way also).
To recap, for future use other visitors to this thread...
1. I tried to apply the 4.4.2 update using an OTA.zip file I found elsewhere on the Internet. This is easy. You've probably already done this.
2. I was told "build.prop" contained unexpected content.
3. I remembered that I had changed the DPI, so I changed that back from my personal 420 to the default 480. This resolved the previous error message.
4. I tried again, but this time was told Roboto-Bold.ttf contained unexpected content. I have no idea why that was.
5. I followed SOME of the instructions on this page: http://forum.xda-developers.com/showthread.php?t=2513701
Specifically, from the "Method 2" section, I did the "fastboot flash system C:/image-hammerhead-krt16m/system.img" and "fastboot flash boot C:/image-hammerhead-krt16m/boot.img" commands. That's ALL I DID from the "type these commands" section of those instructions. Doing that, I did NOT lose data! (well, none that I've yet noticed, at least)
6. I tried AGAIN to flash the OTA.zip file from Clockworkmod Recovery. This time it finally worked!
7. I checked Settings > About Phone, and I'm running 4.4.2 now!
8. I'm having trouble changing the DPI back to 420. I'm probably not rooted anymore. I'll have to go do that again. No big deal. Everything else seems fine.
...along the way, I needed to install drivers, for which I tried so many things, I don't even remember anymore what was the best method. I think using "ADB Manager.exe" from within my ADB folder was best. I also, at one point, had to change my USB device type from MTP to PTP. That was done on the phone, by swiping down the notification area.
Ugh, I wish I remembered everything, so I could spell it out as directly and clearly as I would've appreciated it be this morning, but I've seriously done so much recently that I know I'm missing certain steps, and I feel really bad for anyone having problems. There are so many instructions on the Internet that say, "Do this, and then this will happen," but they never explain what to do if that DOESN'T happen. And now here I am, not being any better than any of them. Sorry. Good luck.
Glad you got it working
Q&A for CyanogenMod 11S
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Favor
I bought this oneplus from retail in mainland China, but it comes with colorOS and doesn't have google play. I want to change the OS to CyanogenMod. However it will be my first time flashing a ROM. So my question is, what do I need to prepare or do before doing the steps on the page one? do I need to root my oneplus one first?
Boyjour said:
I bought this oneplus from retail in mainland China, but it comes with colorOS and doesn't have google play. I want to change the OS to CyanogenMod. However it will be my first time flashing a ROM. So my question is, what do I need to prepare or do before doing the steps on the page one? do I need to root my oneplus one first?
Click to expand...
Click to collapse
Look in the help section if this forum, there is a guide to flashing cm on colorOS devices
Guys do you have a working kernel stock 38R?? Every kernel i find break my wifi! O___o
how do i build my own 11S? or is 11S closed source?
Just started having this issue in the last few days.
WiFi + LTE, no prob... Call is stable.
H/H+ (LTE turned off), no prob... Call is stable.
LTE without WiFi, phone switches to H/H+ and connects for about 2 seconds then hangs up while the signal icon goes blank, then back to LTE.
I tried reflashing stock 11S with a clean wipe, 38R.
I tried the latest nightly with a clean wipe.
I tried clean flashing back to 33R.
Really at a loss here.
jam90 said:
Guys do you have a working kernel stock 38R?? Every kernel i find break my wifi! O___o
Click to expand...
Click to collapse
You need to flash 38R again dirty flash system.img then flash the stock kernel. I assume you tried Franco now want to go back to stock kernel?
Sent from my Nexus 7 using Tapatalk
The ONLY time I've had some issues (random reboots) with CM 11S was when I played around with styles. Switched back to what I used to have before update @ early Oct and everything works fine NO ISSUES. Best ROM ever.
I guess oneplus staff are too busy running the company into the ground/oblivion.
Sent from my A0001 using Tapatalk
OnePlus One stuck on boot
Hi need help.
My new OnePlus one (64gb) stuck at bootloop or boot logo. I try to flash with the stock rom but not able to do it as the USB debugging isn't enabled...
When turning the phone On, it shows Android symbol and then get restarted. Tired the OnePlus One Toolkit for flash CM but nothing is working.. Need ur help as not even used the phone for more than 2 days...
Help with flashing
First time flashing CyanogenMod 11S on your device, or coming from another ROM (e.g. ColorOS)?
WARNING: This procedure will factory reset your device! Accounts, applications, settings, etc will be lost!
Download the file cm-11.0-XNPH33R-bacon-signed-fastboot.zip to your PC from the links below
Reboot your device into Fastboot mode by holding PWR+VOL-UP
Connect your device via USB to your PC
Unpack the downloaded zip
Open a command prompt (Windows) or terminal (Linux/Mac) and perform the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH33R-bacon-signed-fastboot.zip
Click to expand...
Click to collapse
I was following the instructions until I typed "fastboot flash modem NON-HLOS.bin" and got a reply <waiting for device>. Because of the long wait time, I closed the command prompt. I reopened it and typed "fastboot reboot" to reboot my device but it is still waiting> . I'm afraid that I might brick my OPO if I disconnect the device and turn it on. Help please! Thanks!
guys anyone of you has problems with touchscreen if activated double tap wake up and gestures shortcuts?i have no control in the middle of the screen...works only on border of the screen...what should i do?help here guys!i will post a video too
francis2co said:
I was following the instructions until I typed "fastboot flash modem NON-HLOS.bin" and got a reply <waiting for device>. Because of the long wait time, I closed the command prompt. I reopened it and typed "fastboot reboot" to reboot my device but it is still waiting> . I'm afraid that I might brick my OPO if I disconnect the device and turn it on. Help please! Thanks!
Click to expand...
Click to collapse
maybe you need admin rights to run fastboot? linux: sudo fastbook .... windows: open an administrative command prompt?
francis2co said:
I was following the instructions until I typed "fastboot flash modem NON-HLOS.bin" and got a reply <waiting for device>. Because of the long wait time, I closed the command prompt. I reopened it and typed "fastboot reboot" to reboot my device but it is still waiting> . I'm afraid that I might brick my OPO if I disconnect the device and turn it on. Help please! Thanks!
Click to expand...
Click to collapse
Disconnect and reconnect the cable, run all the commands again to be sure. Sounds like a USB problem.
can i flash 11s using twrp (OPO)
I'm currently rooted, have twrp and on Mahdi rom. Is there a zip file that i can use to flash 11s? I really dont want to have to go through all them steps to get back.
vince1228 said:
I'm currently rooted, have twrp and on Mahdi rom. Is there a zip file that i can use to flash 11s? I really dont want to have to go through all them steps to get back.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2906746
Transmitted via Bacon
Annoying problem with OnePlus One
So I have the latest build of bacon, unrooted, and I have this bug that's killing me; whenever I'm watching a video, on any app, whether Vine or Instagram, after the first playthrough, and when I replay it, the sound works but the video is stuck on frame until the video actually goes to the frame which sometimes would continue the video with workable video, or just continues being stuck at that frame. Scrolling away and returning to the video would play the video fine, but then when replaying the same issue reappears..
Is there a fix for this?
Thanks
Is anyONE facing distorted and very often choppy voice on calls??? It is more worse on loud speaker. Bit better changing to 2G only mode. This problem is killing me with shame as I gifted it to my wife.
I received this OPO a week ago in India and it is on stock 44S and not rooted yet. Does rooting and changing kernel helps me resolve these issues??
Quick question. I dont have the OnePlus One but Im wondering whether CyanogenMod 11S is Open or closed source? If I do get the OnePlus One, can I compile 11S myself or am I stuck with "regular" CM without the OPO specific features?
Untouchab1e said:
Quick question. I dont have the OnePlus One but Im wondering whether CyanogenMod 11S is Open or closed source? If I do get the OnePlus One, can I compile 11S myself or am I stuck with "regular" CM without the OPO specific features?
Click to expand...
Click to collapse
i believe 11S is closed source. it doesnt have root and has google. this is probably part of the agreement with goog.
i compile my own "regular" cm and i dont know what u mean by opo-specific, but i do have, for instance, gesture recognition with the screen off. other than themes and other crap, is there something specific u want me to test for you with my build?
the opo is the only non google free phone im aware of. all others at least aim to disable your warranty if u root or unlock bootloader.
do buy the opo, i switched from nexus 5 and im really likeing it.
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.