Database Develop

Nexus one Froze, Vibrates 7 Times, Wont Boot

So my nexus one froze today, and now whenever I pull the battery and put it back in, it will vibrate 7 times and wont boot. Is it bricked, or what can I do to fix this?
Thanks

What were u doin when this happened and what does the boot animation come up
Sent from my Nexus One using XDA App

I opened up the navigation app and it froze. Puller the battery and had that problem. I then decided to pull the battery, press the power button a few times to discharge the phone and it booted back up. So hopefully it wont happen again

Same thing happened to me. I was experimenting with an undervolted kernel which up until then had been behaving well. Received a bunch of texts and notifications simultaneously. By the time I got to my phone, it had gone to sleep. I was able to power on, but the screen was completely unresponsive. The powering on was also very delayed. I couldn't shutdown with the power button so I pulled the battery.
It could only do a 7-vibrate boot/freeze every single time I pulled the battery and replaced it. Finally, with the above advice, I left it out for several minutes, hit the power button a few times, then replaced the battery and got it to finally boot.

This happened to me today too, I took out my SD and it booted up just fine after that..not sure what happened. I checked my SD for errors but it didn't have any and had no problems after I put it back in.

hmm havent faced these errors yet, have u modded the rom at all?

mine just did it now when i changed the sd card.
taking the card out doesn't help.
i'm guessing it thinks the battery is flat or something similar, will try charging.
edit: just kept trying and it eventually worked.

I have the same problem, hitting the power button does nothing, I leave the battery out for ~ 5 minutes and eventually get a fastboot screen and 7 times vibrate, but no control, power button, volume and trackball not working. I have to pull the battery out, wait another 5 minutes or so and try again.
Does anyone have a clue about what that 7 times vibrate means? sounds like an error code.
If after have pulled out the battery for 5 minutes I keep pressed the volume down and the power, I eventually have a fastboot working screen, but choosing recovery from the menu takes me back to the fastboot screen with 7 times vibrate. Taking the card out or the sim does not make a difference.
How did I get here: Was using Cyanogen 2.2, rooted, screen froze one day, pulled the battery out and here I am.
Tried to do a reset with volume down and power, it freezed during the procedure and now it won't boot at all.

I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?

alexxed said:
I'm still able just to start in fastboot. Recovery and clear storage do nothing useful. Booting normally gives me the nexus logo for a while and then the screen blanks after a few seconds.
I can do fastboot flash boot, but I can't do fastboot flash system, it just says sending and that's it:
Code:
[[email protected] apps]# ./fastboot erase userdata
erasing 'userdata'... FAILED (remote: not allowed)
[[email protected] apps]# ./fastboot erase cache
erasing 'cache'... OKAY
[[email protected] apps]# ./fastboot flash boot Passion\ Google\ WWE\ 1.01.1700.1_ERD79/boot.img
sending 'boot' (2044 KB)... OKAY
writing 'boot'... OKAY
[[email protected] apps]# ./fastboot flash system Passion\ Google\ WWE\ 1.01.1700.1_ERD79/system.img
sending 'system' (116663 KB)...
Any ideas anyone ?
Click to expand...
Click to collapse
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.

edited.
sent back to HTC

There are a batch of n1 that has this problem. I had bought a new att 3g version in june and returned it for a new. I also had the booting problem. It would constantly reboot or be stuck at the nexus boot logo. Its a hardware issue. Call google and they will transfer you to htc and work out a exchange or repair for you.
Sent from my GT-I9000 using XDA App

Vakman said:
Since you said you were using CyanogenMod, I will assume you are using CM6 RC2 not that it matters now. So you are running a custom recovery right? Try to wipe everything, data, cache, and the dalvik cache. Then flash a different ROM, either stock or any other really to see if that helps.
Click to expand...
Click to collapse
I'm trying to flash the stock image following the instructions here: #614850
Flashing hangs in various steps of flashing system.img, so I tried repeatedly until I succeeded, but still no success in booting afterwards, so I suspect I need to match the radio with the system as I've read that the radio boots before system. Right now I have FRF50 (4.06.00.12_7).
The problem is that once I leave the phone off for a while with battery in, the phone does not start in any mode (power, power + volume down, power + trackball) until I leave it with battery out for 2-3 days after which I can boot in any of the three modes above, the power button shows the nexus logo for a few seconds than the image scrambles and the phone goes off. If I choose to go in recovery I see the nexus logo forever.
Fastboot works, but as said, it hangs when flashing about 90% of the time.
I'll keep trying as sending off the phone for repair is a tricky option considering that I'm not in US, I haven't bought the phone from US, and so on.

Ive had this problem for awhile. It first started when i updated to froyo. I called htc Tech support an they told me it was probably caused by an app but i dont know if thats true or not. Iam curious to know what the 7 vibrations mean

In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).

maxdadev said:
In case you can't/don't want to send it back for warranty repair, it seems that leaving the phone charging for 12-24 fixes the issue (though it might look dead during those hours).
Click to expand...
Click to collapse
Tried that and almost anything I could have imagine. Finally I sent the phone to HTC and they were kind enough to repair it free of charge, I only paid for the shipping to them, they paid the shipping back.
The interesting part is that I got the same phone (it has the same IMEI), but locked again, so I guess that means there is a way to lock the phone back.

I hate to revive an old thread, but it's probably better than making a new one about the same issue.
A friend of mine said this happened on his Nexus and now it won't boot past the "X" splash screen, and it vibrates 7 times. He gave it to me to try to fix, and I've done everything I can think of. When I try to use a PASSIMG.zip through Hboot the progress bar on the side fills, then it says "Checking PASSIMG.zip," but then it just returns to the Hboot screen.
I've tried using Fastboot to install Amon_Ra's recovery and Clockworkmod recovery, even a radio update, but any .img file I try tells me "FAILED (remote: signature verify fail)"
Has anyone found a fix for this, or have any suggestions?
If I have to call Google/htc can I still have it replaced, even if the bootloader has been unlocked, voiding the warranty?
Thanks.

You have to unlock the bootloader to use fastboot.

I have unlocked the bootloader. It says ***Unlocked*** at the top, it's still S-ON though.
I can't access recovery or ADB to tell if it's rooted or not, either.
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.33.0012
MICROP-0b15
RADIO-4.06.00.12_7

OK, that's weird then. I've never heard of fastboot failing before.

[Q] stuck in bootloop

OK I know I made a very noob move here but its done now.
So my friend gave me a sprint zio I didn't look into much about it , I tried autoroot and rooted it then like an idiot I downloaded rom manager and flashed cwm recovery, IDK how it flashed but it did and when I rebooted the phone it was just stuck in a bootloop .
Has this happened to anyone and or does anyone know how to fix this?
I found a factory img here.
http://forum.xda-developers.com/showthread.php?t=1022573
I tried to fastboot wipe everything and as I flashed everything after wiping it when I get to fastboot recovery recovery.img I get an error faild.
Any help would be great.

linsalata28 said:
OK I know I made a very noob move here but its done now.
So my friend gave me a sprint zio I didn't look into much about it , I tried autoroot and rooted it then like an idiot I downloaded rom manager and flashed cwm recovery, IDK how it flashed but it did and when I rebooted the phone it was just stuck in a bootloop .
Has this happened to anyone and or does anyone know how to fix this?
I found a factory img here.
http://forum.xda-developers.com/showthread.php?t=1022573
I tried to fastboot wipe everything and as I flashed everything after wiping it when I get to fastboot recovery recovery.img I get an error faild.
Any help would be great.
Click to expand...
Click to collapse
fastboot flash recovery recovery.img(whatever its called, easiest to just rename it recovery.img)
Those are the only stock imgs there are, so I'd re-erase everything and try reflashing each img again. I think you can leave out cache. I realize its not your first phone, or an important one, but it's a pretty noob thing to do, not reading and searching first. Hope you get it working. If you need drivers try Sprints website. Also make sure you erased recovery in fastboot. fastboot erase recovery.
Sent from my Sensation using xda premium

Have you tried booting up with just erasing the recovery? Flash system, userdata, boot etc, just leave out recovery and try. If I remember correctly we could erase recovery and not reflash it and still boot up, as the Cricket version had no recovery, just fastboot.
Sent from my CyanSensation
CM 4 Life!

sinisin said:
Have you tried booting up with just erasing the recovery? Flash system, userdata, boot etc, just leave out recovery and try. If I remember correctly we could erase recovery and not reflash it and still boot up, as the Cricket version had no recovery, just fastboot.
Sent from my CyanSensation
CM 4 Life!
Click to expand...
Click to collapse
yeah I did try and boot without recovery but I got to the little android guy with the box and then it just started looping again.
I had to go out so I couldn't mess with it but I'll try the above later thanks for the reply.
And yeah I know that was stupid but I really didn't think it would even flash the recovery but it was still stupid none the less.

I got it fixed thanks for the replys.

What did you do to fix it?

linsalata28 said:
I got it fixed thanks for the replys.
Click to expand...
Click to collapse
I just flashed this through fastboot again and it worked.
http://forum.xda-developers.com/showthread.php?t=1022573

I did the same thing and it is still stuck in boot loop. Weird thing is it will load up until the slide to unlock screen and then reboots.

wthigon said:
I did the same thing and it is still stuck in boot loop. Weird thing is it will load up until the slide to unlock screen and then reboots.
Click to expand...
Click to collapse
Maybe just try and wipe from fast boot then try to boot up.
Don't wipe system , boot or recovery though.

HELP! Now im stuck in bootloop on my CRICKET zio. I have NO idea what im doing, im trying everything i read, all the fastboot recovery img binary things or whatever their called but honestly, im probly just making things worse. Can somebody please help me out, point me in the right direction, maybe even walk me through it, PLEASE? Thanks in advance and upon any help.

hey i think i have the same problem
well my zio is stuck at the kyocera screen, all i did was try to reset it using this method, dial ##4557*, select view, scroll to bottom and select reset, enter 6 digit code (000000) and select ok, it should then shut off then reboot and when its on dial *228, but when i did this it never came back on only got stuck at kyocera screen, ive tried usb fastboot reset and still nothing. any ideas?

crnorman said:
well my zio is stuck at the kyocera screen, all i did was try to reset it using this method, dial ##4557*, select view, scroll to bottom and select reset, enter 6 digit code (000000) and select ok, it should then shut off then reboot and when its on dial *228, but when i did this it never came back on only got stuck at kyocera screen, ive tried usb fastboot reset and still nothing. any ideas?
Click to expand...
Click to collapse
Im also still stuck at the kyocera screen and too noob to know what to try. Can we please get a lil hand up, please?

Follow the fast boot stock flash or openzio guide and you should be gold. If you can hit fastboot your only soft bricked.
Sent from my HTC EVO 3D using XDA App

Dang, I must be dumb and/or lazy cause I was hoping we'd get like a " R U USING, DO U GOT, 1ST U GOTA, THEN GO TO, NOW THIS N THAT" but just got another GO TO THIS PAGE/PART and under the bus I go. EVERY method I've tried only gets me to a certain point till something doesn't do anything or it says blah blah then stuck midway thru without a clue what to do. Dang I'm......I don't know. Thanks
Now I'm soo broke I cant even pay attention!

itrustno1 said:
Dang, I must be dumb and/or lazy cause I was hoping we'd get like a " R U USING, DO U GOT, 1ST U GOTA, THEN GO TO, NOW THIS N THAT" but just got another GO TO THIS PAGE/PART and under the bus I go. EVERY method I've tried only gets me to a certain point till something doesn't do anything or it says blah blah then stuck midway thru without a clue what to do. Dang I'm......I don't know. Thanks
Now I'm soo broke I cant even pay attention!
Click to expand...
Click to collapse
I'll make you a quick hand holding guide.
Save the following rom on your SD card.
http://forum.xda-developers.com/showthread.php?t=1073889
Follow the guide at this link to boot into clockwork via fastboot.
http://forum.xda-developers.com/showthread.php?t=968602
Once you are in clockwork.
1.Factory reset 3x
2.wipe cache 3x
3.wipe delvik cache 3x
4.select install from .zip and choose openzio.
5.after openzio install completes reboot.
If this fails follow this guide.
http://forum.xda-developers.com/showthread.php?t=973369
If it still fails throw your phone away smash your computer and go by an apple product.

Ok, ill give aaaaaaaall of the above a try and if that still don't work, yes I will smash it with a hammer, probly wont smash my computer, BUT I WILL NEVER BUY AN APPLE PRODUCT, NO WAY, EVER! But thanks, ill give it a shot, even tho I already went and bought the A2 id still go back to my Zio and toss this low-rez phone to someone else.
Now I'm soo broke I cant even pay attention!

Yup, this is how "newbie" i am, I CAN NOT FIGURE OUT HOW TO OPEN A BLANK COMAND PROMPT! Everywhere i read, comand prompt c:\ , but i always get c:\users\itrustno1> What am I doing wrong, how do i get a blank comand prompt? Please school me someone. Thanks in advance.

Type in: cd \
Then hit enter
Sent from my SCH-R915 using xda premium

THANK U! Now I finally might be able to get my zio back up n running and toss this Ascend 2 in the trash! Id root this thing but nah, I can't get the detailed feedback that I need to convince myself to do it. Anyways, thanks again!
Now I'm soo broke I cant even pay attention!

itrustno1 said:
THANK U! Now I finally might be able to get my zio back up n running and toss this Ascend 2 in the trash! Id root this thing but nah, I can't get the detailed feedback that I need to convince myself to do it. Anyways, thanks again!
Now I'm soo broke I cant even pay attention!
Click to expand...
Click to collapse
So did it fix it?

A bizarre series of events and my desperate recovery attempt [cliffhanger!]

So I started having trouble after flashing a rom. The old infinite htc boot logo. The troubling part was when I tried to reboot to recovery and TWRP blackscreened and device turned off.
I tried re-flashing recovery.img with identical results.
Now my phone locked while attempting a fastboot flash boot.img with a known working boot.img just in case the rom I flashed had a corrupt boot image.
I left the cmd window open and its been "sending boot.img" for about forty-five minutes now. I am terrified to ctrl+c the command or restart my device.
So boned or no boned?
On a scale of one to boned how boned where do I fall on the bonage spectrum?
Any ideas on what to do next, or if rebooting to fastboot is safe?

You have to wait the final of the sending.
Probably your USB cable is *****d up, and i'm advising you because i had the same issue.
A flash of a boot.img was of 15 mins.

Tried fastboot erase cache to get back into twrp?
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 9.1.0
Bulletproof 4.3

Afraid to stop the current fastboot operation to try to clear cache. Tried running from another window and it just sits there, cursor blinking, like its waiting for the other operation to complete.
Waiting for it to complete seems fruitless as its been almost two hours now for a 5836kb flash.
-update-
Okay so I took a couple valium and quickly switched out the usb cable. The cmd window running the flash operation crashed, but fastboot on the device became responsive again. I feel like this is a fact that might be useful to others in the future.
Fastboot stalls out--don't panic, just disconnect the usb cable...
I'm still scared to reboot it, even to reboot to fastboot. Is fastboot part of boot.img? If this botched op boned up my boot.img is it possible that fastboot might not work after a reset?
Gonna give cache erase a shot and report results.

Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?

hypocritelecteur said:
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
Click to expand...
Click to collapse
After the cache's erase you can boot in recovery.

Guich said:
After the cache's erase you can boot in recovery.
Click to expand...
Click to collapse
Phone still reboots right after TWRP logo is displayed!

hypocritelecteur said:
Phone still reboots right after TWRP logo is displayed!
Click to expand...
Click to collapse
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.

Yeah, I tried that before posting but for sake of thoroughness I did it again.
erased cache
reflashed m7 twrp
erased cache
Going to try CWM now.
Really appreciate the guidance and support in a problem you have no personal stake in. Being on the receiving end of the goodwill of strangers makes me all warm and tingly.
Also switched USB cables and did a fastboot reboot to make sure commands were being passed on... nothing wrong on that front.

Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Aaaand CWM worked for whatever reason.
Odd, since I've never had a problem with TWRP before but plenty with CWM... Every duck has its day I guess.
---
Well... CWM loads properly but executing any command that touches phone data causes a reboot.
Factory reset -> reboot
Install zip from sdcard -> reboot
Trying sideload next... it goes into sideload mode fine. I'm guessing that as soon as it tries to write something it will reboot, but I'll have to wait till I've re-downloaded and double checked md5s like a paranoid bastard first.
adb sideload ohdeargod.zip
---
Hmm, wiping cache partition alone works.
--
Noticed that on booting into CWM it displays the message:
Warning: No file contexts.
--
formating /system alone works
formatting dalvik causes reboot
formatting data causes reboot
--
sideload seems to have worked although its taking a long time to boot. I'll give it another 15 minutes.

Which firmware are you running?

Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Guich said:
Which firmware are you running?
Click to expand...
Click to collapse
Aaaand bingo gringo. It's booted.
Its a tmo m7. I haven't touched firmware afaik.
Resolved just in time for me to take it sailing today and drop it into lake Huron.

hypocritelecteur said:
[snip]....drop it into lake Huron.
Click to expand...
Click to collapse
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4

altimax98 said:
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Okay so I have a brand new HTC TMO One I got last week and its waterlogged. I drilled a hole in the back of the case to drain it and then left it on the radiator to make sure all that moisture is gone. I can't get it to post to TWRP.
Please help.
Deciding after recent events that XDA can be a dangerous place for sarcasm. So--thanks all, problem solved, no, no phone was damaged during the making of this thread. It was just my business partner, Lloyd, who fell in and became waterlogged. No amount of drilling or radiator baking could revive him.
Please help.

Sprint HTC One M8 (S-ON): erasing 'userdata'... FAILED (remote: not allowed)

Well, I have been trying for a while to SIM unlock the sprint HTC One M8 but with no luck. Yesterday I was giving it a try and used the SIM Unlock helper app, but it seems like it screwed up my phone. By mistake I pressed on Lock option, it restarted my device, wiping out all data, and leaving the phone with only a lock scree with a password that I didn't set. I googled and found that someone said it is 1866 but that didn't work. I relocked the bootloader., then tried to perform a factory reset, using the bootloader menu, but it keeps giving me message Security warning.
I tried it using fastboot, but it gives "erasing 'userdata'... FAILED (remote: not allowed)", I tried installing the stock ROM, but it keeps giving me error that battery is less than 30% while it is fully charged with the green led on.
I just want the phone to work now, even if SIM locked, doesn't matter!
Please help

Unlocked bootloader
Alshoabi90 said:
Well, I have been trying for a while to SIM unlock the sprint HTC One M8 but with no luck. Yesterday I was giving it a try and used the SIM Unlock helper app, but it seems like it screwed up my phone. By mistake I pressed on Lock option, it restarted my device, wiping out all data, and leaving the phone with only a lock scree with a password that I didn't set. I googled and found that someone said it is 1866 but that didn't work. I relocked the bootloader., then tried to perform a factory reset, using the bootloader menu, but it keeps giving me message Security warning.
I tried it using fastboot, but it gives "erasing 'userdata'... FAILED (remote: not allowed)", I tried installing the stock ROM, but it keeps giving me error that battery is less than 30% while it is fully charged with the green led on.
I just want the phone to work now, even if SIM locked, doesn't matter!
Please help
Click to expand...
Click to collapse
This is driving me crazy, I unlocked bootloader, factory resetted using winteam recovery project, but password stll there, please help!!!

Have you tried the latest RUU?
Make sure you are using a USB2 port.

Sloth said:
Have you tried the latest RUU?
Make sure you are using a USB2 port.
Click to expand...
Click to collapse
I am using the one I was able to find online and that matches Radio version, I used TWRP to wipe everything, went to wipe, advanced, and selected everything to delete it, now phone has no system, but TWRP is still there, and when every I try excuting the RUU on my laptop, it will tell me phone battery is less than 30%, I tried draining it out last night, and recharge again until phone said 53% and same issue persisted!

Nexus 6 stuck in boot loop after factory restore

Hey everyone,
I've rooted my Nexus 6 device and tried to modify some of the partitions on the device (logo, aboot, boot).
The device has gone bricked but as that's not the first time it is done I guessed it's a soft brick and can easily be fixed downloading a factory ROM for the Nexus.
I did that, and both Marshmallow and Lollipop were stuck on boot (the colored circles which eventually form the "Android" title).
I also tried custom ROMs, but nothing helped (got to the same point were the colored circles jump infinitely).
I tried to flash the ROM both via fastboot and via the recovery menu.
The bootloader is accessible and unlocked. However, it still doesn't work.
Before I rush to JTAG experiments, does anyone have any idea how to solve this? (or at least, some ideas which aren't mentioned above).
Needless to say, I was wiping the cache everytime I flashed the ROMs.
Sincerely,
Adam.

doadam said:
Hey everyone,
I've rooted my Nexus 6 device and tried to modify some of the partitions on the device (logo, aboot, boot).
The device has gone bricked but as that's not the first time it is done I guessed it's a soft brick and can easily be fixed downloading a factory ROM for the Nexus.
I did that, and both Marshmallow and Lollipop were stuck on boot (the colored circles which eventually form the "Android" title).
I also tried custom ROMs, but nothing helped (got to the same point were the colored circles jump infinitely).
I tried to flash the ROM both via fastboot and via the recovery menu.
The bootloader is accessible and unlocked. However, it still doesn't work.
Before I rush to JTAG experiments, does anyone have any idea how to solve this? (or at least, some ideas which aren't mentioned above).
Needless to say, I was wiping the cache everytime I flashed the ROMs.
Sincerely,
Adam.
Click to expand...
Click to collapse
Did you also first reflash the bootloader when flashing stock firmware? Also fastboot ersae system and fastboot format cache before flashing anything.

gee2012 said:
Did you also first reflash the bootloader when flashing stock firmware? Also fastboot ersae system and fastboot format cache before flashing anything.
Click to expand...
Click to collapse
Yes, I also reflashed the bootloader. The room itself comes with a "flash-all.sh" script which did not work as well.
I also tried to fastboo erase system and fastboot format cache (both with the recovery feature and the fastboot feature) but it did not work....
Same outcome - waiting on the colored circles.

doadam said:
Yes, I also reflashed the bootloader. The room itself comes with a "flash-all.sh" script which did not work as well.
I also tried to fastboo erase system and fastboot format cache (both with the recovery feature and the fastboot feature) but it did not work....
Same outcome - waiting on the colored circles.
Click to expand...
Click to collapse
Did you flash the following img`s manualy in fastboot:
system
userdata
boot
recovery
cache
Flash-all.batt isn`t working for a longer time now allready.

gee2012 said:
Did you flash the following img`s manualy in fastboot:
system
userdata
boot
recovery
cache
Flash-all.batt isn`t working for a longer time now allready.
Click to expand...
Click to collapse
Just tried this order. I've been waiting up for 40+ minutes for the phone to boot, however it still loops on these circles.
If it matters - I just tried the 6.0.1 ROM (I've been working on 6.0.0 previously).

doadam said:
Just tried this order. I've been waiting up for 40+ minutes for the phone to boot, however it still loops on these circles.
If it matters - I just tried the 6.0.1 ROM (I've been working on 6.0.0 previously).
Click to expand...
Click to collapse
Your best bet is to run a logcat as it is booting to see where it is hanging. Your issue was messing with the partitions. Not a wise thing to do.

zelendel said:
Your best bet is to run a logcat as it is booting to see where it is hanging. Your issue was messing with the partitions. Not a wise thing to do.
Click to expand...
Click to collapse
Already thought about that - however adb keeps waiting for a device and shows nothing...
Code:
*adamdo**~**shamu-mmb29k**adb logcat
- waiting for device -