Argh! Just as I thought everything was fine - Boot Loop - HD2 Android Q&A, Help & Troubleshooting and Genera

My apologies for what is (hopefully) a simple or obvious issue and shortcoming on my point. I've used xda to flash my very first custom ROM, and managed to get things sorted without having to resort to asking you, the assembled phone-modding-guru's but I'm at a loss and don't want to dig myself in any deeper and make more of an issue of this than it already is.
I've got a UK HD2 with a sandisk ultra 32gb micro sd (with a 2 gb partition) and the ROM, Android 4.0.4 On HTC HD 2 NexusHD2 HWA V2.7
All was good and I'd even managed to overcome the lack of internal memory by installing Link2SD and placing the new Apps on the SD card. All was good until this afternoon when I set up a recovery app (or whatever it was classed as) in Avast.
I kept getting a message saying that something had crashed then Avast started flagging issues and finally, things refused to connect to the WIFI - google chrome, the stock browser, google play store. I tried following some instructions on various forums (stop google from syncing) after typing out what the prompt was but then my broadband went down and I lost what I'd typed.
I tried to restart my HD2 but then it refused to boot up. I managed to find that this is called the Boot Loop and followed through this thread Please Help!!! HD2 Boot loop, making a recovery which I've stored on my pc (I took out the sd card and used an adapter to connect it) and used the zipped ROM that was on the sd card but alas, back to the boot loop.
I've checked the battery pins and non are bent, although the one on the right hand side does seem to be a tiny bit shorter than the other two (I'm talking fractions of a mm) and checked to see that I'd mounted the SD card.
So, I guess my question is, where to go from here?

Well I don't know if it was the ideal way to sort things but after following the instructions on another site, I managed to get rid of the boot loop but now can't access the apps through Link2SD...
For future reference, if anyone else is unfortunate enough to have this issue, have a go at following this...
pull the battery, put it back in, hold down call-end whilst booting to boot into to MAGLDR, launch AD recovery, clear the cache partition, clear the dalvik cache, clear the battery stats and fix permissions then restart, I have to at least clear the dalvik cache every single time I reboot ANY android nand rom on my hardware (LEO512-TELSTRA) otherwise mine boot loops or just gets stuck on the black background and green htc.
try also Fix Permissions under advanced and "wipe data/factory reset" options in the AD recovery menu's
I do NOT use EXT4 partition, there could be something screwy on your card though, try booting it up without your SD card in, if it boots then you know there's something crap on the card you need to clean up
I'm unsure about being able to post external links on here (this is my first post after all, and one borne out of panic!) so if that's a no-no then please accept my apologies once more but I thought that if this can help one person, it was worth me writing this last part!

check out the links below, it might help
steps in the procedure is important to follow

mengfei said:
check out the links below, it might help
steps in the procedure is important to follow
Click to expand...
Click to collapse
Thanks but non of those contained anything specific to my problem - I've looked through each one at different times.

Related

NC won't install CM7, format data, or boot anymore

Where to begin...
So I based my install off of this YouTube Video: youtube.com/watch?v=88qRbLLEAPQ and after I got done following everything to the T, I was not able to format /data. I feel this may be my problem. After doing all the steps minus that one I tried to install CM7 and it would boot the second time around in CM7 (Something I read was common). IT would get the the skateboard screen and then it would just stay there with the arrow continuously looping around and around. I let if sit for quite some time before I had to power it off.
I called up my buddy who told me I would more then likely have to install it manually with the Android Developer tools (Or whatever he called it). I did not have those tools so I kept poking around online. I found that sometimes the SD card caused problems so I bought a new 4Gb class 4 card. This was not the issue.
I poked around alittle more in CWR and I accidentally formatted /boot. The unit froze up so I restarted it. It booted into CWR just fine and after trying to wipe the /system, /data (Still not working) and /cache and rebooting, it has now just turned to a black screen that I can't even boot from a card.
Now before I just cash in on my protection plan, What can I do to get this running again? I hate having a paper weight sitting on my desk..
Thank you so much!
tl;dr, Tried to install CM7, can't format /data, tried new card and re installing, accidentally formatted /boot and now it won't boot at all.
Honestly, I can't watch Youtube at work so I am clueless what instructions you are following.
1. What version of your NC? 1.2? 1.1? 1.0?
2. What version of CwMR?
3. You tried to install CM7 in the eMMC or uSD?
I don't know which Nc it is... I just got it 2 weeks ago today.
I do believe that the cwr was 3.0.0.3 or something like that... it was supposedly the newest.
and it was the latest stable version of CM7.
My problem now is that my computer has totally crashed and it won't start in safe mode even. I am fairly sure it has something to do with having the files on my computer.. I just have to get that part figured out, then I can get the rest of it working..
Latest CW is 3.2.0.1 if I recall.
I know when I leave my imaged microsd card in my adapter on the laptop that the laptop won't boot. You don't have the card in an adapter on the system do you?
Also, I assume you are trying to install CM7 to internal memory?
You have to use CWR v. 3.2.0.1. Earlier versions will not wipe/clear everything. Do that and you should be ok....
If it has been around 2 weeks ago, then it most likely be v1.2 which you need CwMR v3.2.0.1, which reportedly fixes the format /data issue.
Give it a try again.
Ok, got the Nook to boot back to the Nook software. Won't get past the loading screen, but atleast it is booting..
I got my computer working finally after booting in Safe mode and deleting all the zip files and images from the computer. So now I am back to a clean slate.
Where do I get CWR 3.2.0.1? And then where do I get the CM7 latest release? I feel like I should be listening to you guys rather then listening to the YouTube video.. It was nice to see things happen on there, But it did not work for me.
Thank you guys SOOO much for having this forum and the "How to fix the black screen" tutorial! I would be lost without it!

[Q] I'm a mess, CM7 back to stock

Hi. Ok so I rooted my NC to CM7 sometime last year, and now with all the blah about markets not working and having to do more about it, not to mention the PIA it is to get books on, I decided to put it back to stock. Which apparently was a big mistake.
First I mounted an older version of clockwork to the SD card, then when I figured that out (having format data error) I did the newer 3.2.x.x one. So that went good, I went through the steps and reformated data and system, and then went to upload the zip from the choose zip part, but it says there are no files. So I backed out, took out the SD and put it in my computer(Macbook pro) to try to put it in again but it wont show up at all? I tried looking in Disk Utility too and its not there. Any ideas where my card is? What do I do next?? I have nook complete restore 1.0.1, 1.0.0 and nook color update 1.4.1 on my desktop, I thought I had 1.0.1 on the SD card.
I've been reading and googling all over, I can't find what could've made my SD card disappear?
Thanks, I know you must get these all the time and I really appreciate your help-
Ok I didn't do anything, but it just started up to the little silver N and is now sitting there? Is that a good thing?
Don't panic. The NC is very hard to permanently brick. From what you've described, it sounds like your SD card may have gone bad or been corrupted. I'd just try again.
The 'n' logo is a good thing, but if it hangs there, be sure you've followed all the steps carefully. That's typically a sign that /data wasn't formatted, though from your description, you got that step.
Sorry I can't offer up anything more specific. Do be aware that you can restore back to 1.3 if you don't want to go back to 1.01
It happened to me and what I did is plugged my sdcard into my android phone and format it and start over again.
I did that couple time during first attempt to install CM7 on my nook
Hope this helps ! Good luck!
Try plug it into different computer(s) along with using usb-adapter.
The Eausus Partition program works well to wipe/format cards too...

nook color bricked please help me

i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Don't get too upset. You can still boot from SD. At worst, you may have to (re)install some firmware. If you want the B&N firmware, you can reinstall B&N 1.3 and update, or stay at 1.3 if you prefer.
It's hard to totally brick a NC.
Take a look at the restoring to stock section of the guide in my sig
Sent from space
Listen to the two people above this post. They are right. It is nearly impossible to completely brick it. Trust me I've tried.:what:
Seems no matter what I do to it, short of kick boxing it, I've always been able to start from a brand new running nook. Just by reading many posts and the great help from everyone on this forum, who have usually, "been there, done that.", folks.
I'm sure this will work out and everything will be fine, but then you'll be able to help someone else too.
Sent from my GT-P7510 using Tapatalk
i just use this command "fdisk /dev/block/mmcblk0 -l"
i think it was to see the partitions and they dissapeared just chek the image ;(
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
bobtidey said:
I think what you are looking at there is the partitions on a booted SD card which look correct for an 8GB card.
Click to expand...
Click to collapse
Nope... you can see he's looking at /dev/block/mmcblk0... that is internal.
Need to find the thread about the nook color partitions and create partitions 5-8 then dd the images to them.
i already fixed ! its working again
i can´t believe,
i was thinking about doing a tutorial in how to soft unbrick your nook, i´m not an expert but is a lot of people with the same problem as mine
basically when i enter in recovery receive errors in logs and he dont let me mount or format any of mine partitions(except boot and sdcard), a lot of people are having the same issues and i was thinking about doing a tutorial in how to do it.
should i do it??
thanks everybody
More tutorials are always good. One thing to remember though, is that if someone is looking for a tutorial that means they are usually starting with a small knowledge base. You not only need to be clear, you need to be right.
All I am saying is an underinformed/incorrect tutorial is worse than no tutorial at all. The information is out there, but can be hard to find. If you know your stuff, and have a place to present it where it doesn't already exist, then sure, people will benifit from your knowledge.
Just a guess, but problems mounting within CWM tend to come from old and/or incompatible versions of Clockwork. Is that where you had your problem? I definitely wished that had been stressed on the tutorial I first followed. Would have saved me untold hours of pointless reflashing.
you are right but in my case and i think that is the same of a lot of people (who follow this tutorial http://www.youtube.com/watch?v=szlGSBtWbKY) i tried about 7 to eight diferent versions of clockworkmod and including change of sdcard, i also tried DD the images of the boot and system, when nothing of this works we start get in panic, with no necessity because its only a partition problem, i fixed my 4 partition and he started working
Yeah, I can see where you are coming from. I followed an older tutorial as well, and never saw anything to indicate the link to the CWM image might be outdated.
For sure, that info should be wider spread.
Good luck on your video (?)
hackerse7en said:
i dont know if im asking for help to the right person but if you can help me tank you very much.
today i tried to restore my nook color by pressing u button and power and he goes to the factory reset asks to press u button and i press then he asks again and i press and after the yellow bar moves too fast only last about 3 seconds and it should take some minutes and after reboots. i think my factory partition in damaged.
;(
Click to expand...
Click to collapse
I am not sure where to ask for help. I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install, I power off forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. Am I bricked my nook?? please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stacked at the cw recovery screen. Help...

How I recovered from the /data "Encryption Unsuccessful" problem

Yesterday, I decided to give CyanogenMod a try and installed cm9-rc2 in my Samsung Galaxy S (i9000). I all went fine at first, but then I had to reboot and after I inserted my SIM unlock PIN was greeted with the infamous "Encryption Unsuccessful" screen. I had never seen any mentions to it in CM's wiki, where I got my instruction on how to install cm9. Afterwards I saw lots of forum posts about the problem.
I tried to recover my phone by installing CM7 (via CWM) and Samsung's stock image (via odin). Nothing worked. All I got was endless boot loops, looking at the animations. I was convinced I had bricked my phone. I went though google and this forums. I found lots of solutions for preventing the problem, but none for solving it once it had happened.
In the end I came up with a simple solution which got my phone back to life. I'm posting this as I did not find it mentioned in the forums. Maybe it's not new and I simply didn't look hard enough. If this is so, I apologize.
As my internal memory was not recognized, I used the microSD card to host /data, just like mentioned in the many threads that explain how to prevent the problem. All I had to do was to create a second partition in my microSD card. I used gparted (I use GNU/Linux) to shrink my microSD partition and created a second one (with 4GB) formated using ext4. From then on, my microSD card filled the role of the internal memory when that is not detected.
I was latter able to install CM7 and CM9. Both worked. I'm currently running CM9 and have a very weird behavior. Every other time I boot the internal memory is recognized. As such one time I get all the apps that are installed in the internal memory, the other I get the ones that are installed in the second partition of the microSD card. In any of the cases, the boot costs me any setup I do of the homescreen; I always get back to the reset state.
Even though I love ICS, I think tomorrow I'm going back to CM7 for the meanwhile.
Hope this helps anyone.
streelamp said:
Yesterday, I decided to give CyanogenMod a try and installed cm9-rc2 in my Samsung Galaxy S (i9000). I all went fine at first, but then I had to reboot and after I inserted my SIM unlock PIN was greeted with the infamous "Encryption Unsuccessful" screen. I had never seen any mentions to it in CM's wiki, where I got my instruction on how to install cm9. Afterwards I saw lots of forum posts about the problem.
I tried to recover my phone by installing CM7 (via CWM) and Samsung's stock image (via odin). Nothing worked. All I got was endless boot loops, looking at the animations. I was convinced I had bricked my phone. I went though google and this forums. I found lots of solutions for preventing the problem, but none for solving it once it had happened.
In the end I came up with a simple solution which got my phone back to life. I'm posting this as I did not find it mentioned in the forums. Maybe it's not new and I simply didn't look hard enough. If this is so, I apologize.
As my internal memory was not recognized, I used the microSD card to host /data, just like mentioned in the many threads that explain how to prevent the problem. All I had to do was to create a second partition in my microSD card. I used gparted (I use GNU/Linux) to shrink my microSD partition and created a second one (with 4GB) formated using ext4. From then on, my microSD card filled the role of the internal memory when that is not detected.
I was latter able to install CM7 and CM9. Both worked. I'm currently running CM9 and have a very weird behavior. Every other time I boot the internal memory is recognized. As such one time I get all the apps that are installed in the internal memory, the other I get the ones that are installed in the second partition of the microSD card. In any of the cases, the boot costs me any setup I do of the homescreen; I always get back to the reset state.
Even though I love ICS, I think tomorrow I'm going back to CM7 for the meanwhile.
Hope this helps anyone.
Click to expand...
Click to collapse
I use odin to just flash stock rom and move forward from there. it also fixes datadata error and if you find the right file if your phone dont see odin, odin will fix that. If i can help you anymore let me know. I had problems also but now can flash roms and kernels
streelamp said:
but none for solving it once it had happened.
Click to expand...
Click to collapse
look in My Guides and Manuals

[Q] Nook Color won't boot after cm7 install and update

I see that there are other posts on this same subject and I have looked through them to try and fix my problem but I haven't found a proper solution yet. I rooted my NC (1.4.3) cm7 and it worked alright after that but apps weren't available for the version so I attempted an update then reboot. I powered down and pulled the micro sd then powered up and it gets to "Read Forever" then goes black. I have tried cm10 with manual nooter in order to try and re-do the partition on the device but it won't do anything once I put the card in and try to boot. I have had to dis-assemble it so that I can pull the battery and get it to power down completely. I have tried a factory reset boot, sd card boot with auto nooter, manual nooter, cm7, cm10, and other options on the sd card, I have also tried to boot directly from internal memory. I have tried the process of plugging it into the computer through the usb cable. I have charged the battery completely so that isn't a problem.
I have read that it is virtually impossible to brick this thing but I think I might have succeeded....any input on what I can try next would be helpful...
Fatguy86 said:
I see that there are other posts on this same subject and I have looked through them to try and fix my problem but I haven't found a proper solution yet. I rooted my NC (1.4.3) cm7 and it worked alright after that but apps weren't available for the version so I attempted an update then reboot. I powered down and pulled the micro sd then powered up and it gets to "Read Forever" then goes black. I have tried cm10 with manual nooter in order to try and re-do the partition on the device but it won't do anything once I put the card in and try to boot. I have had to dis-assemble it so that I can pull the battery and get it to power down completely. I have tried a factory reset boot, sd card boot with auto nooter, manual nooter, cm7, cm10, and other options on the sd card, I have also tried to boot directly from internal memory. I have tried the process of plugging it into the computer through the usb cable. I have charged the battery completely so that isn't a problem.
I have read that it is virtually impossible to brick this thing but I think I might have succeeded....any input on what I can try next would be helpful...
Click to expand...
Click to collapse
A good place to start with boot problems is here http://forum.xda-developers.com/showthread.php?t=949699
You should also probably read at least the first two post in this thread http://forum.xda-developers.com/showthread.php?t=1621301
You need to do a better job of describing your situation if you want help: how your NC was set up; exactly what you did that created the problem; what you want to end up with. At a guess, I will assume the you were running rooted stock on EMMC and CM7 on SD, decided to update CM7 to CM10, but used directions for updating CM that was installed to EMMC. I am not an expert on this, but sort of remember Leapinlar posting advice for someone (or maybe a few (?dozen?) someones) with this problem, you might want to search for those threads. If not, you have probably corrupted your boot records, recovery and/or possibly some partitions. Check out this thread by Leapinlar for help http://forum.xda-developers.com/showthread.php?t=1759558
If you decide to install CM on EMMC, see this thread http://forum.xda-developers.com/showthread.php?t=1030227
To install stock BN firmware to EMMC, see this thread http://forum.xda-developers.com/showthread.php?t=931720
To install CM on SD, see this http://forum.xda-developers.com/showthread.php?t=1941858
Good luck and don't forget to hit the thanks button in the posts you use
webyrd said:
A good place to start with boot problems is here http://forum.xda-developers.com/showthread.php?t=949699
You should also probably read at least the first two post in this thread http://forum.xda-developers.com/showthread.php?t=1621301
You need to do a better job of describing your situation if you want help: how your NC was set up; exactly what you did that created the problem; what you want to end up with
Good luck and don't forget to hit the thanks button in the posts you use
Click to expand...
Click to collapse
Here are the exact steps that I took to get to where I am:
I rooted the stock EMMC with the manual nooter to be able to get the Google Play Market, that worked well and I had access but the Android version was so old that I couldn't install the apps that I was after.
I then attempted to flash the EMMC to CM7, all status came up as pass and I rebooted. when it came up after the reboot all I got was the "Read Forever" screen.
since then I have read many different posts and tried to boot from the SD...that doesn't work, the screen just stays black
I have tried to boot to CWM to repair or rebuild the EMMC...same outcome
once I remove the SD all I get to is the "Read Forever" screen...
I have read and tried all the steps listed in every post you listed but they all have the same outcome
I have attached a pic of what the screen looks like when it tries to boot.
Fatguy86 said:
Here are the exact steps that I took to get to where I am:
I rooted the stock EMMC with the manual nooter to be able to get the Google Play Market, that worked well and I had access but the Android version was so old that I couldn't install the apps that I was after.
I then attempted to flash the EMMC to CM7, all status came up as pass and I rebooted. when it came up after the reboot all I got was the "Read Forever" screen.
since then I have read many different posts and tried to boot from the SD...that doesn't work, the screen just stays black
I have tried to boot to CWM to repair or rebuild the EMMC...same outcome
once I remove the SD all I get to is the "Read Forever" screen...
I have read and tried all the steps listed in every post you listed but they all have the same outcome
I have attached a pic of what the screen looks like when it tries to boot.
Click to expand...
Click to collapse
Hopefully someone more knowlegeable will look in, this is above my level. The fact that the Read Forever still displays shows that CM did not install correctly, if it's a newer version. You might want to try posting your problem in the same thread that you got the install instructions from.

Categories

Resources