yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
Great thinking actually. That is the original thread or maybe the same forum where I saw the pull method. Never thought about how the pull method was just a work-around rather than actually fixing the problem. I will give it a shot when I get back home and report back. Kind of excited there may be a way to fix it. :D
[Droid Incredible Q&A, Help & Troubleshooting] thejdog55:
I actually had an issue like this on my last DINC. I was flashing a nightly and then rebooted the phone and got the five vibs and blinking green LED. Everything I read or looked up said it was a Qualcomm diagnostics code, stating that something was wrong with the hardware and no one at Qualcomm would tell anyone what it meant. The only way I could get it up and running was the USB pull as well. While I was able to get into the phone and use it normally, the SD Card would not mount. I tried flashing it to stock and it didn't fix the problem. H-BOOT read the SD Card, but Clockwork wasn't able to mount the SD Card at all. I'm also not sure if you had S-OFF, but I did and after I got the 5 vib, I noticed in H-BOOT that it said S-ON again. So pretty much everything I did I couldn't get it to boot or mount the SD Card properly. I eventually went through my warranty and got a replacement, come to find out the replacement was defective. I had a similar problem to the service and then reboot issue you have. I was able to get the phone to be stable when it was not activated, but as soon as I activated the phone, let it reboot, it would go into a boot cycle. Sometimes I could get it to unlock for a second and then it would reboot. I tried to flash the stock ROM and even the RUU, but none of that worked so I had to get Verizon to send another replacement. I think it either had something to do with the Radio, or the actual hardware causing issues when it was receiving cell signal. Not sure how much this helps, but my situation was similar to yours and I'm pretty sure it was all hardware related. Well I wish you luck in getting it up and running!
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
Okay so I wiped and reformatted everything just to triple make sure and then I flashed a recovery and loaded IncRom 4.x (or something like that) to the phone. For the first time I had a perfect start. No issues. Even went in and downloaded some of the programs I usually use just to make sure it wouldn't get all crazy on me. So its working so well that I decided I'll go ahead and activate it on my account. So I activate it OTA and then it does the normal "will reboot in 5 seconds" thing. So it reboots, and its looking good, till it reboots mid bootsplash. :/ So I am thinking it has something to do with the radio? but how would I fix that? I have tried flashing one or two other radios to it but nothing ever seems to fix it. I plan on flashing the 11.19 to see how that one fares as I haven't tried it yet.

I mean the device was obviously receiving a cell signal while it wasn't activated, but activating it would have been the first time it interacted with a tower (I am assuming) since the flawless start up. I went ahead and checked the MD5 just to make sure nothing was wrong and it was a match. It started up fine. I'm going to use it tonight and see how it fares. If so then formating the stuff is what fixed everything.

Update:

Nope. No good. It rebooted while in the middle of downloading stuff. :/ I dont mind it rebooting once or twice a day, but this happens every 10 minutes...

It then rebooted while in the middle of a text message.

Is there any way to see whats going on with the phone (such as processes/what its thinking) so that before I try doing anything drastic I can see if maybe it is a failed process or a heat issue or something. I believe I have seen people on here talking about a CAT file or something... Or I may be entirely mistaken.
[Droid Incredible Q&A, Help & Troubleshooting] Vernox701:
you can try "log collector" from the market or logcat those may help you
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
Alright, I'll see if I can get it to download... I am currently having constant reboots. Do you think a video would help? It just shows it rebooting to the white screen 5 times, fully rebooting. Making a call, rebooting. After the video ended it did a 5 vibe. But then rebooted normally once I pulled the battery.

Nvm. Can't get it to download. Just reboots. :/ I'll have to let it sit and try tomorrow.
[Droid Incredible Q&A, Help & Troubleshooting] Vernox701:
Not really sure where you are on this maybe try to reload the stock rom from hboot. wipe everything twice while in recovery. Looks like you are running a Z-rom you could also try a different kernal. Some phones are really picky about the kernal. These suggestion will probably only help with the reboots not the 5_vibrate thing

http://xdaforums.com/showpost.php?p=8207764&postcount=1
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
I have reloaded stock via hboot and it didnt help either, but thanks for the suggestion. Is it normal to have heat problems? I mean, I do live in Florida, but I dont think a phone would act like this, I mean its not deathly hot here. Though I just booted it up and it worked fine. No issues, nothing. Thus it was also cold as it had been sitting in the a/c for the past 24 hours.
[Droid Incredible Q&A, Help & Troubleshooting] rlacrossjr:
Stupid but did you check your battery volts. May have a bad battery that fixed mine. One test is plug you cell into computer then try to boot up and see if it starts up and runs good when connected to computer.
[Droid Incredible Q&A, Help & Troubleshooting] mauiblue:
What the OP posted is quite similar to what my original Incredible was going through with random reboots which started about 2 weeks ago. I notice that when the phone booted up, it could not read the SD card every so often. I also had the phone experience that "5 vibration, flashing green LED" and the phone would not boot up unless I pulled the battery. Finally I gave up on the phone and called Verizon CS. After a quick explanation of the problem, the CS rep said Verizon would send out a replacement phone. I received the phone a day ago and all is well now. My original phone was rooted and I was able to unroot it prior to sending it back. In fact, even after it was unrooted, the phone would still randomly reboot. The replacement phone is working fine after a day of reinstalling apps and setting up the home screens. I hope I won't have any more issues and if I do, I hope it is before my warranty is up.
[Droid Incredible Q&A, Help & Troubleshooting] dbrits:
I kid you not - three days of running Redemption ROM 2.4 without a single problem (I thought I was in the clear) and five minutes after reading your post via the xda app my phone goes into a bootloop. I was doing quite a bit of texting right before my phone started bootlooping. I still feel like something it wrong with the radio...but I have no basis for the theory.

ETA: I just had a horrible realization. While running Re-Engineered Z, I did a *228 update. Could that have caused a problem??

ETAx2: When the phone is bootlooping, it seems like the phone always reboots right as the phone is trying to connect to the network, which is why I have a feeling the issue is the radio. I've never flashed radios - and if I did, it was only once when I ran unRevoked for s-off.

Anyways, I did a *228 on Redemption 2.4. The phone then rebooted two times instead of once. We'll see if this does anything. My next course of action is to revert to the stock kernel, but I've never had any issues with Lou's kernels in the past. They've all been completely stable.

Can you tell I'm dragging my feet on returning this phone to Verizon??
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
I was just able to replicate this with the incredrom or whatever that I am using. I went to activate it via *228 and now Im doing endless boots as per usual where as just an hour ago my device was running just fine. Even downloaded some movies and what not via wifi. So it was working about 3 days ago or so whenever I was no longer activated, and it was working today when I was no longer activated. But as soon as I activated it the device goes all crazy. I guess I'll just try to get as stock as possible and then flash different radios to the device to see if it helps any.

Update:

Went S-On, flashed stock, hit reboot and the htc screen flashed twice and then a screen with 3 arrows popped up with a phone underneath them. It rebooted itself and then did the normal boot but got stuck at the screen with the droid eye or whatever. Booted up to the lock screen and then rebooted. -.-

I am honestly at a loss seeing as I am as stock as you can get. Does the stock image include the stock kernal? I would only assume so. :/ Also checked md5 checksums. Tried booted while connected to the computer but still no good. Reboots at lockscreen.
[Droid Incredible Q&A, Help & Troubleshooting] dbrits:
In my case, I think the problem was hardware related. Last night I unrooted the phone, switched s-off to s-on, and reverted to stock 2.2. My plan was to run the phone for a few days with the stock setup to determine if it was a hardware problem or software problem. As I was going through the Android setup screens immediately after I reverted to stock, the phone rebooted as I was connecting to my home wifi network. That was the last straw.

I went to Verizon this morning and explained my problem. The only caveat was that I was unable to reproduce the reboots because they are - by nature - random. The rep did a factory reset and told me to run my phone without downloading any third-party apps and to come back to the store a week later if the phone continued to do the same thing. I told the rep that I'll be traveling out of state the following week and that I needed to have the phone replaced immediately so I could test it for a few days to make sure that it worked because I can't be traveling without a reliable phone. His response was that the line is eligible for an upgrade and I could purchase a new phone. That answer was unacceptable. Thankfully between the time it took for him to fetch his manager, the phone started to reboot. I showed it to the rep and he processed the exchange. I'm still somewhat irritated that I had to pay $13 for expedited shipping, but I need to get my hands on the phone as soon as I can.

That being said, since my phone rebooted while it was running stock and unrooted, I think that eliminates software problems. I know you're not able to return it to Verizon since you purchased it on eBay, so hopefully the reboots on your phone are being caused by the software and not the hardware. Best of luck to you.
[Droid Incredible Q&A, Help & Troubleshooting] k_nivesout:
I had a d2 i bought from a friend with a bad camera, Verizon replaced it even though they didn't "have to".
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
I'm pretty sure I have narrowed the issue down. It has to do with the phone being activated. I went ahead and reactivated my old phone, rebooted the dinc, and it booted flawlessly. So apparently I just have a phone that cannot be activated. I'm going to try activating it via the web instead of using *228 and see how that goes.

And returning to Verizon isn't a viable option at all as I am not a customer, but thanks for the suggestion.
[Droid Incredible Q&A, Help & Troubleshooting] luke1987:
I know when I first got my incredible I used it for a week without activating. So I know activation isn't required to boot phone.
[Droid Incredible Q&A, Help & Troubleshooting] juicy.cook:
Yeah, it works fine without activating it, but as soon as I activate it the problems start.

Update:

So, I tried putting my Eris battery into the Incredible once it started doing loops again, and it booted up fine. I think I just have a faulty battery or something. The Eris battery seems to be doing just fine in the device. Put the Incredible battery back in and instant reboots. So I guess the problem is solved. I just wish I would have thought to use my Eris battery before I attempted doing everything. D:
[Droid Incredible Q&A, Help & Troubleshooting] swindelljd:
I got my daughter an Incredible for Xmas from Craigslist. It worked great for 6 months or so but in the last couple of weeks started the random reboots and then the 5 vibs thing. I have tried swapping battery with my Incredible, but that didn't work. I then tried a factory reset and also rooting and still get the issue. It happens whether or not it is plugged into a computer. It will usually boot up once and run for 10 minutes and then reboot. Sometimes it will go into a boot loop but most times it is the 5 vibrates. If I wait about 10 minutes it will boot again.

I just tried the GB RUU figuring if it were a corrupt partition that would wipe everything and fix the issue but no luck. Hoping someone has a magic fix so I don't have to buy her another Incredible :(
[General Topics] shuggee:
Hi, yesterday i was messing with overclocking that didnt work as i wanted, so i made a thread about my problem not being able to change the freq. a guy replied that i should insmod in chargemon instead of hw_config because it's executed at beginning of boot sequence. so i guessed that i should put the code

"insmod /system/lib/modules/x8oc.ko # x8 overclock"

in the chargemon file located in system/bin/ and so i did. and now my phone starts up, but as soon as i slide the unlock button there comes lots of errors saying that the processes need to be force closed and then the phone restarts, and Xrecovery doesnt work either:( so i really dont know how to fix this! so please help, thanks
[General Topics] shuggee:
nevermind! i got it working with seus, sorry for making a useless thread about it!
[General Topics] _Claney_:
No problem
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] denwaotoko:
Hello XDA forums,

Recently I installed Urukdroid 1.0RC2 on an A43 8GB model, and I noticed how my device only has up to 7GB of space. I was just wondering where the other 1GB is because I don't want to have wasted space sitting around doing nothing.

Thanks for your time.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Lenn:
This "problem" isnt a problem:D

its always the same: if they write 8 gb, there is formatted only 7-7.3 gb;)

look at your hdd on your computer;)
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] denwaotoko:
Hello and thanks for the quick reply.

Actually I do understand the deal with the 1024mb = 1gb, but are you sure that it is supposed to read 6.95 gb (that is what it says in Linux when connected)? I'm pretty sure it should more or less be around 7.4-7.7.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Lenn:
Okey thats pretty much:D

hm.. than its because urukdroid's formatting;)

what did you select in urukdroid installation progress?

EDIT: You said thanks, psst... push the "Thanks"-Button don't hurt ;)
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] fzelle:
@denwaotoko:

What do you think where the system itself is hostet?

Right it is on that 8GB internal memory.

It has 3 Partitions ( without Uruk ) which are for System, Data and Rest.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] chrulri:
@fzelle correct.

as far as I know, the kernel splits the 8GB in two "virtual" devices which of one is 512 MB large and the other one 7,5 GB.

The first virtual device is /dev/block/mmcblk0 which contains rawfs (boot), swap, system and /data partition while the second (big!) virtual device is /dev/block/mmcblk1 and contains only one fat32 partition (internal storage)

so you only get 7,5 GB which in the end is about 7,x GiB formatted storage that can be used (don't have my A101IT with me so I can't give exact numbers)
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] denwaotoko:
Yes I do realize that, so is the 1gb of "lost" space just hidden?
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Lenn:
Jap, exactly;)

We can be proud of the fact that android uses only little memory space,

Windows for example use 20 gb:mad::D
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] denwaotoko:
Alright, I was just expecting that it would show up in a partition manager when connected to a Computer.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] Lenn:
Nope,apparently not:D

Thank you for thanks;):):D
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] chrulri:
No, it doesn't because the device only shows /dev/block/mmcblk1 and mmcblk2 to the computer, where 1 is the internal flash (the last 7,5G of the internal mmc as I explained before) and 2 is the external microsd.
[EVO 4G General] JohnnyBeGood113:
Hi all,

Here's short history of the phone:

Friend of mine drop his on the concrete about June of last year and whole screen was cracked (not pretty). About month ago I found LCD Screen with Digitizer on ebay bought it and replaced it.

After turning it on everything was working except random reboots. Phone was not registered to any account so there was no internet only WI-FI.

So I started going into system updates and downloading HTC updates it did two of them and I think on the 3rd one it just starts to boot white HTC EVO 4G screen comes on and then it reboots.

Only pulling the battery will stop it.

This is all on stock HTC Sense ROM, rooting was never attempted!

I've searched thru the forums here but everything here relates to failed rooting process.

Can someone please make any suggestions?

Bellow is the pictures of boot loader.

Help is greatly appreciated!
[EVO 4G General] Fazulka:
These directions are for un-rooting, but should fix your phone:

http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
[EVO 4G General] JohnnyBeGood113:
Thank you!
[EVO 4G General] JohnnyBeGood113:
Followed the instruction, run RUU and it starts to check the phone after this I get error[170]: USB connection error.

I've tried over 10 times.

Step 4 says "Make sure USB debugging is enabled on your phone."

I can't even log into Sense?
[EVO 4G General] ffolkes:
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
[EVO 4G General] JohnnyBeGood113:
I've tried using this method found here

I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"

Any other suggestions?
[EVO 4G General] rhconcepts:
I had to unroot mine and I found that u have to have the right pc36img file. If you dont know what ver rom was running then you may need to try them all. But I had the same problem it just wouldent install the file. Keep trying and if you need help finding them Ill help ya.

I found this but its not the same place I got mine from. http://www.filecrop.com/htc-evo-4g-roms.html
[EVO 4G General] JohnnyBeGood113:
Thanks for the reply!

Somewhat of a progress. I tried countless times and it always gives me USB connection error: Then I downloaded HTC Sync and and I think I went to Hboot and I heard sound on windows it seemed like phone got recognized and I was able to finish the processes. It was flashed using RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed. Then when I went to again in recovery it was again red triangle over the phone.

After that I just let it try to boot and it finally booted into HTC sense!

Turned on WI-FI and wanted to check if there's any updates and it said no updates?

This is what recoveries I've tried so far:

Amon RA 2.1.1

Amon RA 2.2.1

Amon RA 2.3 (Added 02/09/2011)

Stock Recovery 3.26.651.6 (Added 01/18/2011)

Stock Recovery 3.29.651.5 (Added 01/18/2011)

Stock Recovery 3.30.651.3 (Added 01/18/2011)

Stock Recovery 3.70.651.1 (Added 01/18/2011)

One by one I tried each one renaming to PC36IMG.zip and none of them asked me if I want to do the update. It just checks it and goes back to bootloader.

Why do I get red triangle?

What should I do now?

Help is appreciated!
[HD2 Android Q&A, Help & Troubleshooting and Genera] mrhalfdeadman:
I got the HD2 from a friend a few days ago, read every instruction, put the hspl file on first then flashed MAGLDR and the original DFT leo stock rom, only problem is thatit will not let me sign into my gmail account or access the internet from the phone, everything else is good?

What did i do wrong?

or What do you think is wrong with it?
[HD2 Android Q&A, Help & Troubleshooting and Genera] nickyg008:
Best thing is to retry but this time do a task 29 first to wipe off all previous os files on nand.could really be that simple.search task 29. Shouldn't be hard to find
[HD2 Android Q&A, Help & Troubleshooting and Genera] nickyg008:
Rebooting sometimes helps too
[HD2 Android Q&A, Help & Troubleshooting and Genera] powerdedo:
WIFI or Data?
[HD2 Android Q&A, Help & Troubleshooting and Genera] T-Macgnolia:
If you do a Task 29 as mentioned above then you will have to reflash MAGLDR or CLK, which ever one you use as Task 29 will wipe it from your HD2. Just letting you know.

As far as not being able to sign in are you sure you are using the correct Gmail account name and password? Also you do have a data connection don't you?
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
@nicky

Never ceases to astound me how often "oh you should Task29 " comes up in post 2 as the fix. The best post in this thread,,,,, "data or wifi"?

I've never had an android rom whose data works right away yet, and here you are telling him to wipe everything and start over?

Maybe it will turn out to be a shady instal, but Blimey, do a little fault finding first, eh?

(I've also never seen any actual evidence that Task29 is of actual benefit, if something is broken and you Task29 and reinstall and it works, that doesn't mean the Task29 fixed it, chances are the reinstall fixed it and the Task29 was an unneeded step.

If you have a few loose slates on your house roof, you don't demolish the whole thing and build a new one!

Just for the record I gave up on Task29 and mtty twelve months ago, and I always try installing over the top of the current rom before doing all the cache wipes and stuff, surprising how often it works and your apps and data are still there, and no big deal to do the wipe if it doesn't work.
[HD2 Android Q&A, Help & Troubleshooting and Genera] T-Macgnolia:
Gee thanks Sam I did ask if they had a data connection as I know it sometimes take a little bit to get a data connection or sometimes you have to soft reset once or twice to get a data connection. It is all good though lol
[HD2 Android Q&A, Help & Troubleshooting and Genera] samsamuel:
:) It wasnt meant as an attack, (and i DID start it ''@nicky', not you,,)

((@nicky, again, not a personal attack, just making a point :) ))

I know i come across pretty blunt and heavy handed, I was just making the point that task29 is usually side stepping the problem, and that whilst task29 may have had possibly visible results with winmo roms, there is no reason why it would help with android, since flashing cwm again will rebuild the partitions anyway, and android will conform to using the partitions, without danger of it seeing any left over bits and bytes outside the partition structure, whereas winmo uses the whole thing as a single partition, and doesnt rebuild it with a new flash, so in that situation task29 does something a winmo flash doesnt, hence useful. In this situation, a cwm wipe, or cwm reflash would be just as likely to give teh same effect. (and what with all the worry about all the extra flashing causing bad blocks, every step you can miss out is a bonus, right?)

In the case of magldr or cwm not functioning correctly, then you are in to the territory where task29 and starting over would be a good option, but only as good as flashing back to winmo and starting over, since once you get to the cwm stage again, the partitions will be rebuilt.

So, yes task29 has a place, but not generally as the first option.

Again, sorry if i caused any offence, none intended.