Develop Bugs

Fresh 0.3 Reboot

Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.

l3l2ad said:
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
Click to expand...
Click to collapse
what commands did you use...? nothing in customizing bootscreen should damage anything on your phone...?
Last resort = RUU back to stock re-root and reflash..

So why did you feel you needed to make a new thread about this instead of just posting in the thread itself which is already dedicated to the rom and issues...

... ?
Tenny said:
So why did you feel you needed to make a new thread about this instead of just posting in the thread itself which is already dedicated to the rom and issues...
Click to expand...
Click to collapse
because it would get buried and no one would read it for days... hes hoping this way to get a speedy answer... im sure if you felt like you screwed up your phone somehow you'd be clicking on new thread to get as much help, as soon as possible... ???
if you cant help or are willing to help stop cluttering the forums with your "forum police" attitude...

i'm not going to answer your question specifically BECAUSE you made a new thread instead of posting in the existing one.

l3l2ad said:
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
Click to expand...
Click to collapse
wipe everything then try to reflash.

wrx4memp said:
what commands did you use...? nothing in customizing bootscreen should damage anything on your phone...?
Last resort = RUU back to stock re-root and reflash..
Click to expand...
Click to collapse
I used the 'mount' command while in shell.
Thanks for the help even though I posted WRONG.
I got my issue fixed by using a nAndroid backup..retsored and th issue was gone. I'm thinking the problem happened because I didn't have the droid SDK on my PC..fixed that too!

haha. mount by itself only displays the current mounted volumes. there isn't anything you can do with mount alone in order to render your system unusable.
-------------------------------------
Sent via the XDA Tapatalk App

geekykid said:
haha. mount by itself only displays the current mounted volumes. there isn't anything you can do with mount alone in order to render your system unusable.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Thanks for the info...well im not sure what happened then LOL I'm tryin to teach myself so go easy on me

BIG Problem...NEED HELP

I have been using incredibly re-engineered z and downgraded to clockwork 3.0.0.7 as the instructions say to do to load nils business sense z . I downloaded the rom and used Rom Manager to install the new rom, as I always do, except for restoring sometimes in recovery. For some reason when the phone booted back there was a horizontal black line across the screen below the "HTC Incredible boot screen...then there are two vertical white lines at each end of the screen and the center is black.. The home,menu,back and search button still have haptic feedback, so i assumed the phone didnt quite make it into recovery...pulled the battery...tried regular reboot...same thing happens at the boot screen. Got phone into bootloader and when i hit fastboot, it shoots out a bunch of errors it seems real quickly. All is can read is SD checking...no image or wrong image...PB310IAG.zip (i think)...lack of heap. I tried to get the phone into recovery from the bootloader screen and the same thing keeps happening. I'm stuck and have no clue what kind of fix there is for this...am i bricked? I dont get this...have flashed roms 20 times or so and nothing like this has ever happened...please help!

Sense you can't get into recovery you are going to have to flash back to stock with an RUU..... if you want I will help you through the process..... first check and make sure your SD card is formatted fat32... and let me know and we will go from there
Sent from my ADR6300 using XDA App

i was able to format fat 32...also tried a factory reset and clear memory...appreciate any help...thanks!

actually just tried to make sure once again and it says SD FAT32 init OK
(red letter) 255: Not key-card!!!
Process done, reboot device?
(vol up) yes...i am at that screen now

jdaniels31 said:
i was able to format fat 32...also tried a factory reset and clear memory...appreciate any help...thanks!
Click to expand...
Click to collapse
Ok follow these steps exactly for step was formatting the SD so hboot can read the zip..... now download the zip I'm giving you and place it on the root of your SD card once you have it there rename the zip PB31IMG.zip exactly, then boot into hboot wait for for it to search for it if you did my steps correctly it will once it finds it it will ask you if you want to update press the button up to update let it do its thing till it says it done and asks you to reboot... don't panic and pull the battery because the process can take awhile just be patient... make sure you have a good charge
Here's the file let me know what happens....
http://db.tt/8YWjgVF
Sent from my ADR6300 using XDA App

hit volume up and rebooted...didnt reboot into hboot though and same thing happened at incredible screen...assume the sd card is still formatted correctly

i do not have a sd adaptor for my mac and not sure how to flash anything on the hboot screen. Also I have never used my computer for anything on the phone so know very little about how I would put something on the root of my sd card through a computer

thinking about going to verizon tomorrow and just telling them that I might have picked up some new malware that I hear is going around on the market...that it has caused this to my phone...???

jdaniels31 said:
thinking about going to verizon tomorrow and just telling them that I might have picked up some new malware that I hear is going around on the market...that it has caused this to my phone...???
Click to expand...
Click to collapse
Well I thought I could help but if you can't access your SD card then that wont work.... the root of the SD is the section where all the folders are located....
Sent from my ADR6300 using XDA App

just wierd...flashed many a rom and this has never happened before. No clue what I did wrong as I do the same thing every time I flash a new rom through rom manager...make a backup if I wish and wipe...then reboot and off we go...for some reason things went a bit different this time. no clue...?

Yea it sounds strange if you go to Verizon be carefull
Sent from my ADR6300 using XDA App

if i am able to get an adaptor, how easy would it be to do this. As mentioned, I ve never really done anything with the phone on my computer. I have seen the mass storage files and pulled pics from the sd card through a usb cord and thats about it. I can get an adaptor pretty easily. Just dont know if I can actually do this. I'm decent with computers, but far from an expert

what did i do to the phone so i can try not to do this again. Its like rom rom manager messed me up...sux

Its hard to tell what happened without skittles more info but I can help you I will we will Yakut step by step if you want to try I'm willing to help
Sent from my ADR6300 using XDA App

most definitely...pretty beat from a long week. Are you gonna be around tomorrow? Also, do you know about mac's? I also have a windows machine so i guess it doesnt matter, but know the mac a little better myself.

I use windows myself but all you need it for is to download the file and then copy it to your SD the rest is done on the phone its actually pretty easy ill just have to explain it in more detail for you.... so if you want to wait go ahead and download the file its about 180mb so you will have it and we will get you fixed
Sent from my ADR6300 using XDA App

dl'ing file now...let me know when you might be up and about so we can get this done. Really appreciate it!

I'm usually up by 9 I have a 5 month old no sleeping in here
Sent from my ADR6300 using XDA App

haha...a 4 year old here...she's still up though so I might make 9...gonna have to run to the store to get that adaptor and have other chores as well, but first things first...thanks again

No problem I know what its like
Sent from my ADR6300 using XDA App

Clockword Mod / Rom Manager Observation

I noticed something weird here, I backup up my system with rom manager, and flashed cyanogen 7. Cyanogen decided to loop its boot animation constantly. So I think ok restore, go into restore choose menu options and press power button. All I got was a logo from rom manager on screen and nothing else. So after panicing a little I realised something, it would seem in the current version of clockwork recovery that the button assignments have changed, the power button no longer selects menu options but the circular button in the centre of the bottom row of buttons does!
Just thought I'd mention this in case anyone else has similar worries as it doesn't seem to be documented anywhere I have looked.

bean12345 said:
So after panicing a little I realised something
Click to expand...
Click to collapse
I panicked too seeing there are still people using that pos software. Ditch rom manager for being responsible for more bricks than most of us these days can count.
Sent from my HTC Desire using Tapatalk 2

Which software are you referring to, rom manager, cyanogen or clockwork. Also what rom would you recommend, I could use one that will handle an ext partition to conpensate for lack of internal memory

bean12345 said:
Which software are you referring to, rom manager, cyanogen or clockwork. Also what rom would you recommend, I could use one that will handle an ext partition to conpensate for lack of internal memory
Click to expand...
Click to collapse
rom manager is known for f*****g up phones and CWM recovery has problems to when it comes to partitioning sdcards, ditch them both and go for 4ext recovery its better in everyway.
Oh and bout asking erklat about whats the best rom to use..... well... good luck with that lol
Sent from my HTC Desire

I think advising him to send me a pm asking that would have probably been a good joke
Sent from my HTC Desire using Tapatalk 2

erklat said:
I think advising him to send me a pm asking that would have probably been a good joke
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
hahaha that would of been funny... dam, why didnt i think of that
Sent from my HTC Desire

Erklat is right, there is no reason to use ROM Manager (i said it before countless times), and do yourself a favor and switch recovery to 4ext.

just looked at 4Ext recovery control, it ain't exactly user friendly is it. Damn thing says it needs updating then refuses to do so, and also insists on busybox which wants to take what little internal memory I have left. Thank god I kept a restore image!

[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..

[Q] Probably broke it...[Resolved]

So I was working on putting on a new ROM and when I went to install the PA G Apps zip it said in my recovery that I didn't have enough space in the system storage. Which was a little confusing since I had just wiped it like usual through the recovery before I do a ROM. However I was navigating the recovery since it had been a while and just check out some of the things I didn't notice that changed. Went to the Mounts and Storage area, then I guess I touched "Format /system" and when I realized that it moved to asking me if I wanted to format /system I tried to push NO but apparently I have fat fingers and still pushed yes...So now after having rebooted the phone it is stuck at the screen "Google *small unlocked Lock at the bottom*". And now I'm not sure what to do.
Any advice?

Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Well the issue is it is stuck...I let it sit for at least 5min or so and it just sat there at that same spot. Is that because I need to reflash it? I have the Galaxy Nexus Toolkit, but I haven't used it as of late since I haven't needed it. If you don't mind going into detail I would appreciate it .
Should also mention if I go into the bootloader, it hangs at "Downloading..." so effectively I can't do anything to reflash my ROM or anything. And I probably should be clear that this all happened AFTER I flashed the new ROM and then remembered I needed the PA G Apps. Should have refreshed my memory with doing this sort of thing since I'm not as experienced as I use to be long ways back.

Ysosrslawl said:
Should also mention if I go into the bootloader, it hangs at "Downloading..."
Click to expand...
Click to collapse
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11

AndyYan said:
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.

Ysosrslawl said:
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Click to expand...
Click to collapse
Yeah, make sure you hold BOTH volume keys for bootloader. Hold only VOLUME- for Download mode as you've seen before. If you indeed held both keys but still got to Download mode, chances are you have a broken volume key.
Sent from Google Nexus 4 @ CM11

Yep I'm dumb apparently and misjudged how the buttons were being pressed down...now on to step 2! Hmmm....

Seems like the zip for the ROM isnt in the storage anymore. How do I copy it back on from just being in fastboot mode or recovery? I'm not familiar with ADB at all. I may have figured out the problem so hold on...I think I derped and forgot that I removed the device drivers off my desktop because I wanted to fresh install them way back.
Edit2: Doing this the hard way.

OK SO I feel like a total noob, which I really am. I've never used ADB, never tried pushing files, or anything of the sort. I tried for a very long time to get the Galaxy Nexus toolkit to help me out but it REALLY didn't do ANYTHING for me. None of the options worked like I had hoped, the ONLY thing it did for me was to install the missing drivers I needed. Other than that it was utterly useless. You guys may find this funny, but I really had no idea on how to fix this even in the slightest. Even with the responses put here by some of the community.
However, with a little searching I was able to find the answers to my questions, not found here on XDA unfortunately. What I ended up doing was updating my SDK tools and learning how to open up ADB (had no idea why the adb.exe wasn't just opening for me like I assumed it would). From there I used the sideload option in my recovery to help me get my ROM flashed back on my phone. So now all is well and I can go back to being a noob who just likes to find good looking ROMS and play with them every couple months.
Thanks, my issue is now resolved.