Develop Bugs

What is that second vibration on startup about?

When I first got my phone like many others, it vibrated when the phone first turned on and that's it. After flashing a few radios, I now have and have for awhile, the second vibrate about five seconds after the first. I think I read somewhere what it was, but can't seem to find it now. Did we ever figure out definitively what causes that?
I know in between flashing radios it stopped for awhile, and then came back and has been with me ever since. Not worried about it, just curious. Thank you.
Sent from my HTC Vision using XDA Premium App

Same here. What is the second vibration on startup all about?

I noticed this after flashing the 04.30 radio over stock.

I know someone knows or at least has an idea!
Sent from my HTC Vision using XDA Premium App

I think it only shows up when you flash radios. I haven't flashed a radio on my past two devices and I have only one vibrate.
Sent from my HTC Vision using XDA App

Shameless bump. I want an answer to this.
Sent from my HTC Vision using XDA Premium App

I think first vibration is when you push button and phone is "okay, got it, I'm booting up" and then second when "I'm ready, you can enter your pin code". I had the same on Spica and there it was useful because it booted about 1 minute.
Sent from my HTC Vision using Tapatalk

ciaastek said:
I think first vibration is when you push button and phone is "okay, got it, I'm booting up" and then second when "I'm ready, you can enter your pin code". I had the same on Spica and there it was useful because it booted about 1 minute.
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
That makes sense but none of our phones ever did that until we started changing radios. So it's obviously not part of the "normal" boot up process.

I have not changed radios on my phone yet. It is rooted. I get the second vibration also. I have been wondering why it does this also. It did not start doing this until I rooted my phone.

Bumpity..... I'm curious as to why myself
Sent from my shiny metal G2 w/ meXdroid V3

I know i saw an answer to this once. Damnit if i can find it again!!!

Not that im gonna try it lol, but i wonder if installing a pc10img that unroots, S-ON, and all that would make it go away?

xsteven77x said:
Not that im gonna try it lol, but i wonder if installing a pc10img that unroots, S-ON, and all that would make it go away?
Click to expand...
Click to collapse
I don't know what causes it but if you want to make it go away try this. Go to ROM Manager and select to download rom > virtuous > virtuous sense 1.0.2. Let it download all the way and then hit cancel, don't flash it. Then do a nandroid from within ROM Manager and it will be gone....back to just a single vibration at boot.

Ext3 vs ext4 ?
Ive Had This Issue A Few Times And After Trying To Fix It I Believe It Could Be Due To CWM Formatting The Devices Partitions As EXT3 When It Should Be EXT4.
Can Anyone With This Issue Please Confirm This By Posting The Result Of Typing "mount" In A Terminal.
Their Should Be A Line Which Says "/dev/block/mmcblk0p25 on /system type" And Then The Filesystem Type.
I Hope That This Is The Cause As If I Am Correct It Will Be An Easy Fix

EdKeys said:
I don't know what causes it but if you want to make it go away try this. Go to ROM Manager and select to download rom > virtuous > virtuous sense 1.0.2. Let it download all the way and then hit cancel, don't flash it. Then do a nandroid from within ROM Manager and it will be gone....back to just a single vibration at boot.
Click to expand...
Click to collapse
+1
Sent from my XDA premium App

That is seriously the craziest thing i ever heard Edkeys lmfao but going to try now! Will report back in the morning. Ty for the heads up. How the hell did you figure that out!?
And yes ollied there is, and it says ext4.

xsteven77x said:
That is seriously the craziest thing i ever heard Edkeys lmfao but going to try now! Will report back in the morning. Ty for the heads up. How the hell did you figure that out!?
And yes ollied there is, and it says ext4.
Click to expand...
Click to collapse
I noticed a few months ago that after I took virtuous froyo for a test run that my second vibration was gone. Since then I flashed a new radio and the second vibration came back. I thought I'd test what had happened before and low and behold just downloading it with rom manager and creating a backup got rid of the damned thing. One of those wtf moments...lol. It must have something to do with the old vs. new ext. as OllieD suggests.
Sent from my HTC Vision using XDA Premium App

OllieD said:
Ive Had This Issue A Few Times And After Trying To Fix It I Believe It Could Be Due To CWM Formatting The Devices Partitions As EXT3 When It Should Be EXT4.
Can Anyone With This Issue Please Confirm This By Posting The Result Of Typing "mount" In A Terminal.
Their Should Be A Line Which Says "/dev/block/mmcblk0p25 on /system type" And Then The Filesystem Type.
I Hope That This Is The Cause As If I Am Correct It Will Be An Easy Fix
Click to expand...
Click to collapse
Just ran that in an ADB shell. Here's what I got:
/dev/block/mmcblk0p25 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
Click to expand...
Click to collapse
So it's not the formatting. There's another reason why there's a second vibration, but that's really a minor bug.

Misc Partition?
Can Someone With The Bug Please Dump Their Misc Partition?
Run "dd if=/dev/block/mmcblk0p17 of=/sdcard/Misc.img" In A Terminal And Upload The "Misc.img" File From Their SD Card Somewhere ?
Based On The Previous Fix Mentioned I Believe It Could Be To Do With The Way Rom Manager Reboots Into Recovery.
A Command Is Stored Somewhere That Lets HBoot Know Which Mode To Reboot Into.
An Error With This Command Probably Causes The Second Vibrate And When Rom Manager Reboots Into Recovery It Clears This Flag. Although I Remember Flashing Various ROMs Via Rom Manager Without This Issue Being Fixed.

OllieD said:
Can Someone With The Bug Please Dump Their Misc Partition?
Run "dd if=/dev/block/mmcblk0p17 of=/sdcard/Misc.img" In A Terminal And Upload The "Misc.img" File From Their SD Card Somewhere ?
Based On The Previous Fix Mentioned I Believe It Could Be To Do With The Way Rom Manager Reboots Into Recovery.
A Command Is Stored Somewhere That Lets HBoot Know Which Mode To Reboot Into.
An Error With This Command Probably Causes The Second Vibrate And When Rom Manager Reboots Into Recovery It Clears This Flag. Although I Remember Flashing Various ROMs Via Rom Manager Without This Issue Being Fixed.
Click to expand...
Click to collapse
Gonna go take the dog for a walk and some other things, if someone has not done it by time i get back i will do it for us

Goodbye.

It would appear as though my phone has died. I can't install another rom because it says bad zip, I can't install another recovery because of bad zip, and the constant reboots make this phone crap.
I am probably going to stop using xda, because without a phone, there's no point being on here.
Sent from my SGH-I927 using Tapatalk

You really don't have access to a PC for a brief minute?
Sent from Google Nexus 4 @ CM10.2

LaizureBoy said:
It would appear as though my phone has died. I can't install another rom because it says bad zip, I can't install another recovery because of bad zip, and the constant reboots make this phone crap.
I am probably going to stop using xda, because without a phone, there's no point being on here.
Sent from my SGH-I927 using Tapatalk
Click to expand...
Click to collapse
If you're interested I would like to purchase your phone and send it to a dev, how much do you want for it ?

LaizureBoy said:
It would appear as though my phone has died. I can't install another rom because it says bad zip, I can't install another recovery because of bad zip, and the constant reboots make this phone crap.
I am probably going to stop using xda, because without a phone, there's no point being on here.
Sent from my SGH-I927 using Tapatalk
Click to expand...
Click to collapse
You can manual install, put zip contain to sdcard, and run
dd if=something.img of=device
where something.img is file name from zip
and device is:
recovery:/dev/block/mmcblk0p8
boot:/dev/block/mmcblk0p9
But please make dump of your recovery:
/dev/block/mmcblk0p8
And one of sdcard where you found the problem:
internal sdcard:/dev/block/mmcblk0p4
external_sd /dev/block/mmcblk1p1
PLease do, then I could fix issue with my TWRP.
I think you can use adb for dump
adb pull /dev/block/mmcblk1p1 dump-file.img

Wait, wait.
bubor said:
You can manual install, put zip contain to sdcard, and run
dd if=something.img of=device
where something.img is file name from zip
and device is:
recovery:/dev/block/mmcblk0p8
boot:/dev/block/mmcblk0p9
But please make dump of your recovery:
/dev/block/mmcblk0p8
And one of sdcard where you found the problem:
internal sdcard:/dev/block/mmcblk0p4
external_sd /dev/block/mmcblk1p1
PLease do, then I could fix issue with my TWRP.
I think you can use adb for dump
adb pull /dev/block/mmcblk1p1 dump-file.img
Click to expand...
Click to collapse
How exactly would I do all of this?
I got my phone functioning again, but I still cannot flash anything in TWRP, ROMs, mods, or anything.
Now, if all of the things listed above are things I have to do in ADB, then we will be waiting a while, until I gain access to a computer with my phone drivers installed. (Home.)
So please, if you could, write out EXACTLY what I need to do, then I can complete it when I get home, and post the results tomorrow.
Thank you in advance.

santimaster2000 said:
If you're interested I would like to purchase your phone and send it to a dev, how much do you want for it ?
Click to expand...
Click to collapse
If I cannot fix it, then sure, I guess I would be up for selling it.
I must warn though, I got it second-handed, and the original owner has a pretty bad (but not horrible) scratch in the middle of the screen.

LaizureBoy said:
If I cannot fix it, then sure, I guess I would be up for selling it.
I must warn though, I got it second-handed, and the original owner has a pretty bad (but not horrible) scratch in the middle of the screen.
Click to expand...
Click to collapse
Don't worry, it's a third hand, semi-bricked, 2 year old phone, it's not like you are going to get a lot of cash for it.

[FIX] Are You Stuck on a Boot Loop to Recovery and cant find a fix?

So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop. I tried all the methods I could find on xda but none worked. I then started reading all the way through threads and found the fix... wish they would update the original posts... so for those in this same predicament, here is how I fixed it so you don't have to read through everything.
so the FULL ADB method code looks like this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
exit
adb reboot
I of course take no responsibility if this doesn't work for you. I got the original and extra code in this thread http://forum.xda-developers.com/showthread.php?t=2451696 and all true credit goes to them. I'm simply putting ALL the information in the one original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.

I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.

DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.

DooLocsta said:
I ended up doing this as well and now have my phone back. My problem now is that I have the notification of that update and I can't get it to go away.
Click to expand...
Click to collapse
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.

kuwlij said:
You can get rid of the notification by freezing the "Software Updater" app in Titanium Backup.
Click to expand...
Click to collapse
tried this didn't work? even wiped the data still have the icon.... Any other suggestions?

vegasdavek said:
I personally switched to a ROM that was already based on the update. I haven't looked but I'm sure there is a way to turn them off.
Click to expand...
Click to collapse
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.

This is almost an exact repost of the other bootloop fix.

TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Yup. This is a repost only. I have seen couple of Guides here in G2's thread.
Sent from my LG-D802 using XDA Premium 4 mobile app

TheNetwork said:
This is almost an exact repost of the other bootloop fix.
Click to expand...
Click to collapse
Agreed, which is why I said that the other thread is where I found the fix... but the original post in that thread didn't actually offer a fix when I got stuck in the loop. As a result I spent a lot of time trying other attempts to fix as well as combing through threads before finally finding the extra line of code to make it work.
So I posted a new thread so that someone else doesn't have to waste their time like I did trying to find a fix.

DooLocsta said:
What ROM did you end up going with? Each time I try a ROM the WiFi calling does not work and in my area I have to use that more than I would like.
Click to expand...
Click to collapse
I'm using this rom currently: http://forum.xda-developers.com/showthread.php?t=2595586 as I too need the WiFi Calling feature.

If you are on a T-mobile based rom, the way to 'freeze' the update is different than the others.
T-mobile roms use 'Google Services Framework' for the update, and obviously you can't freeze that app.
So, what you do is d/l a program called 'Autorun Manager'. Then inside that program, scroll down to 'Google Services Framework' and disable 1 receiver.
The one you want to disable is called 'com.google.gsf.update.SytemUpdateService$Receiver' Just disable that (by unchecking it) and then reboot. You will not receive a notification to update ever again.
Also, go into the folder /cache and delete the FOTA d/l. You will need R/W permissions in the root directory to do this. So use whichever file manager you prefer for that.
The FOTA d/l is easy to spot, it's a 150mb approximately zip file with a bunch of chars and should be the only file in that directory. There are a few folders as well, but, ignore them and just delete the 1 file.

I'm in the same situation - reverted back to stock rooted with twrp recovery and now boot back to recovery. I haven's used adb much, but do know how to open the cmd window in the adb directory on my computer and it appears I'm connected to my d800. However, when I run the adb devices command I see the device code and recovery listed. When I type the first line of the code in the first post, adb shell, I get ~ # ←[6n and can't type in any additional commands.
Am I missing a step - or just not understanding the process??
UPDATE - Nevermind - I just typed in the command dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota using TWRP's Terminal Command and the phone booted right up to Clean Rom.
Thanks vegasdavek for your repost on this fix!

vegasdavek said:
So like many, I took a stupid OTA on one of the roms (CleanROM) and got stuck in recovery boot loop...
original post of this thread in hopes of saving someone else a lot of time trying to find that extra line of code burried in the other thread.
Click to expand...
Click to collapse
Thanks, found this now, only after I already fixed my issue, but this is useful. Perhaps you should also update it to reflect it can be done with the Terminal in TWRP..

wiped everything

I accidentally formatted everything from my phone. I was in CWM and I formatted everything, and now I basically do not have anything on my phone at all. After the LG boot up logo, the phone goes blank. I'm able to go into download mode. I tried following this method http://forum.xda-developers.com/showthread.php?t=2420219, I keep getting failed previousload() a few seconds after clicking the top left yellow icon in LG flash tool. Anyone have any idea whats going on or how to fix this? LG E988.

aisforadam said:
I accidentally formatted everything from my phone. I was in CWM and I formatted everything, and now I basically do not have anything on my phone at all. After the LG boot up logo, the phone goes blank. I'm able to go into download mode. I tried following this method http://forum.xda-developers.com/showthread.php?t=2420219, I keep getting failed previousload() a few seconds after clicking the top left yellow icon in LG flash tool. Anyone have any idea whats going on or how to fix this? LG E988.
Click to expand...
Click to collapse
Copy a compatible ROM to your memory card and start CWM to flash the ROM you have just copied.
Hope this helps.

Addicted2xda said:
Copy a compatible ROM to your memory card and start CWM to flash the ROM you have just copied.
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply, however i finally managed to solve the issue. I sideloaded a custom rom using adb. Phew!

aisforadam said:
Thanks for your reply, however i finally managed to solve the issue. I sideloaded a custom rom using adb. Phew!
Click to expand...
Click to collapse
What section did you find your fix in? My friend did the same thing to hers and I can't find the command line.
Sent from my VS980 4G using Tapatalk

cj2566 said:
What section did you find your fix in? My friend did the same thing to hers and I can't find the command line.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Hi I didn't find it in one particular section, I had to search everywhere, i spent a good 8 hours straight searching as I really needed my phone to work. I will try my best to start you off though.
I started here.
http://forum.xda-developers.com/showthread.php?t=2559200
Watched this.
http://www.youtube.com/watch?v=dWXHD7PlaQc
That's basically all you have to do. I did, however, run into plenty of issues along the way which is what took up all if not most of the 8 hours. What I did was google each and every issues that occured and I always found answers to it (with some added trial and error).
Here are some of the issues I faced while sideloading that you or your friend may come across.
''device not found''
''cannot read file''
Both of which can easily be solved by googling. I hope I guided you in the right path, feel free to pm me if you need anymore help.

aisforadam said:
Hi I didn't find it in one particular section, I had to search everywhere, i spent a good 8 hours straight searching as I really needed my phone to work. I will try my best to start you off though.
I started here.
http://forum.xda-developers.com/showthread.php?t=2559200
Watched this.
http://www.youtube.com/watch?v=dWXHD7PlaQc
That's basically all you have to do. I did, however, run into plenty of issues along the way which is what took up all if not most of the 8 hours. What I did was google each and every issues that occured and I always found answers to it (with some added trial and error).
Here are some of the issues I faced while sideloading that you or your friend may come across.
''device not found''
''cannot read file''
Both of which can easily be solved by googling. I hope I guided you in the right path, feel free to pm me if you need anymore help.
Click to expand...
Click to collapse
THANK YOU! This helps more than you know.
Sent from my VS980 4G using Tapatalk

Recovery?

Hey guys I want to get into twrp recovery but after staying on the 'entering recovery' screen it will reboot . It worked fine till today and I tried reflashing it to no avail. Any suggestions?
Sent from my HTC One_M8 using XDA Free mobile app

Boot into fastboot and type "fastboot erase cache" then flash the recovery.
Try it with both CWM and TWRP.

i4GS said:
Boot into fastboot and type "fastboot erase cache" then flash the recovery.
Try it with both CWM and TWRP.
Click to expand...
Click to collapse
Yup. Wipe cache and install recovery again, usually solves this.

redpoint73 said:
Yup. Wipe cache and install recovery again, usually solves this.
Click to expand...
Click to collapse
I tried this but it still wouldn't boot into recovery. I then tried installing an older version on TWRP and finally it booted properly. I was looking through it and something caught my eye. MY ENTIRE INTERNAL STORAGE WAS WIPED!!! I have no idea how this happened!! I tried restoring from my sd card but it couldnt mount /data. Would adb sideloading a ROM work do you think?

ILIVE4HEAD said:
I was looking through it and something caught my eye. MY ENTIRE INTERNAL STORAGE WAS WIPED!!! I have no idea how this happened!! I tried restoring from my sd card but it couldnt mount /data. Would adb sideloading a ROM work do you think?
Click to expand...
Click to collapse
It may or may not. Or if it flashes, you might not be able to mount any data partitions or cache.
Try connecting to a PC, and formatting the internal storage with Device Manager.

redpoint73 said:
Yup. Wipe cache and install recovery again, usually solves this.
Click to expand...
Click to collapse
redpoint73 said:
It may or may not. Or if it flashes, you might not be able to mount any data partitions or cache.
Try connecting to a PC, and formatting the internal storage with Device Manager.
Click to expand...
Click to collapse
Last time i couldn't mount /data i just rebooted into recovery and let it sit for a day then it was fine... when I'm about to try to reboot into recovery though it says "no OS installed, are you sure you want to reboot?" will it be safe to reboot?

I hope you get your issues sorted soon. Don't know what i can contribute to help you achieve that. You seem to have more issues than one, but i like to give you one tip and that is to stay in one thread only. I seen you around now in multiple threads and its getting confusing on your actual status. Please don't take this the wrong way, it's very well ment advice
Cheers.

ILIVE4HEAD said:
when I'm about to try to reboot into recovery though it says "no OS installed, are you sure you want to reboot?" will it be safe to reboot?
Click to expand...
Click to collapse
Should be safe. You won't have an OS, so it will just boot into bootloader.

redpoint73 said:
Should be safe. You won't have an OS, so it will just boot into bootloader.
Click to expand...
Click to collapse
Thanks for your help. You answered many of my questions and were very patient with my questions. I regret to say though that my phone is now bricked. Only bootloader will show up, recovery is a black screen and so is bootup. This wouldn't be so bad if my /data is still corrupted after everthing i tried and no computer will recognize my device. I will come back to xda when I actually know what I'm doing and when my phone isn't as valuable. Thanks again for all your help.

Not sure if this is a similar issue or not but I had some issues getting into recovery after doing Sunshine S-Off today. Had TWRP installed and working fine, but after doing the s-off exploit I would see the recovery screen for a split second before the phone would reboot normally again.
Even running fastboot boot recovery.img to run it directly wasn't working.
However, downloaded and installed CWM instead and all is fine again. Phew

ILIVE4HEAD said:
Thanks for your help. You answered many of my questions and were very patient with my questions. I regret to say though that my phone is now bricked.
Click to expand...
Click to collapse
Its not bricked if the screen comes on. I sincerely think we can get this thing back up and running. A phone that doesn't work isn't "valuable" so you might as well keep at it.
Delete all HTC drivers, and connect the phone to a PC. Go to Device Manager, select the option to manually select drivers, and select the generic Android MTP device.

redpoint73 said:
Its not bricked if the screen comes on. I sincerely think we can get this thing back up and running. A phone that doesn't work isn't "valuable" so you might as well keep at it.
Delete all HTC drivers, and connect the phone to a PC. Go to Device Manager, select the option to manually select drivers, and select the generic Android MTP device.
Click to expand...
Click to collapse
wait I was going to replace it but i succeeded re flashing recovery (don't ask). Where do i go into device manager to reformat my storage?
{EDIT} WTF i flashed cwm and now my phone is up and running again... this after TWRP said i had no OS... Im confused

ILIVE4HEAD said:
wait I was going to replace it but i succeeded re flashing recovery (don't ask).
Click to expand...
Click to collapse
Looks like you solved it. But did you mean you were going to replace the phone? That shouldn't ever be necessary just due to software mods you did, as long as the screen comes on. I've seen only one exception so far, where several users here helped the user exhaust every possible fix to the memory not being mountable and nothing worked, and it might have been a fried emmc chip or similar hardware fault. In your case, I still had plenty of hope, as there were still several options that were not tried.
ILIVE4HEAD said:
wait I was going to replace it but i succeeded re flashing recovery (don't ask). Where do i go into device manager to reformat my storage?
Click to expand...
Click to collapse
Control Panel, under Hardware. Also, if you click the Window button in the taskbar, you can just type Device Manager in the "Search Programs and files" area.
ILIVE4HEAD said:
{EDIT} WTF i flashed cwm and now my phone is up and running again... this after TWRP said i had no OS... Im confused
Click to expand...
Click to collapse
No OS is a known issue for some folks on TWRP. It is puzzling, since it only seem to affect some people. TWRP was pretty rock solid and reliable on my past device, so its a bit disheartening to see it appears to be considerably more buggy on the M8.
So is the phone fully up and running, no issues mounting memory?

redpoint73 said:
Looks like you solved it. But did you mean you were going to replace the phone? That shouldn't ever be necessary just due to software mods you did, as long as the screen comes on. I've seen only one exception so far, where several users here helped the user exhaust every possible fix to the memory not being mountable and nothing worked, and it might have been a fried emmc chip or similar hardware fault. In your case, I still had plenty of hope, as there were still several options that were not tried.
Control Panel, under Hardware. Also, if you click the Window button in the taskbar, you can just type Device Manager in the "Search Programs and files" area.
No OS is a known issue for some folks on TWRP. It is puzzling, since it only seem to affect some people. TWRP was pretty rock solid and reliable on my past device, so its a bit disheartening to see it appears to be considerably more buggy on the M8.
So is the phone fully up and running, no issues mounting memory?
Click to expand...
Click to collapse
I reflashed TWRP and restored one of my backups... i have no idea what happened these past few days but thanks for sticking with me. Thanks again!

ILIVE4HEAD said:
I reflashed TWRP and restored one of my backups... i have no idea what happened these past few days but thanks for sticking with me. Thanks again!
Click to expand...
Click to collapse
You're very welcome. Not sure how much I actually helped, as it sounds like you pretty much figured it out yourself. So nice job!