Related
Hi guys,
Tried to upgrade from Darchdroid 2.6.5 to 2.7 today and am now stuck with an unusable phone.
I get a boot loop OR I get stuck on the HTC boot screen for 20+ min. I'm not sure why I get stuck on either one.
This advice was given to me today in the 2.7 thread:
hold down menu+back+power and do a hard reset.
then wipe everything. [EVERYTHING ext4, ect.]
then flash DD2.7
then flash GoogleBits.
good luck.
edit: this has the newest kernel.
__________________
Click to expand...
Click to collapse
The problem is, in order to complete a hard reset, you have to reboot the phone!(right?) But when I reboot, I just get stuck on the HTC boot screen. Is there wiping instructions (i.e. do I need to do certain things from adb instead of the phone?) that I'm missing out on?
Thanks so much. Really loved 2.6.5. Don't know why I keep getting suckered into updating
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
HeroMeng said:
A hard reset is the same thing as doing a factory reset. So, go into recovery, go tinto the wipe list, and wipe everything on that list. Then, flash it and reboot.
Click to expand...
Click to collapse
Thx, Heromeng. Did exactly what you said - wiped everything possible in AmonRa 1.7 and now I'm back to a boot loop.
Some further info: When I was upgrading from 2.6.4 to 2.6.5, Darch said I should push the boot.img from 2.6.4 to make things work. That did the trick for the last update (although I don't know why!).
Is pushing the boot.img from 2.6.4 the way to get 2.7 to work on my phone?
Alright, I went ahead and pushed the boot.img from 2.6.4 and now it's working. I guess it's just like 2.6.5.
My question:
What am I sacrificing by using this boot.img instead of the one from 2.7? I'm not clear what the trade-off is.
Thanks again.
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Decad3nce said:
Back up your sd card, then repartition it.
Sometimes ramswapz corrupts the sd card, so you have to format it and repartition before being able to flash a new ROM.
---------------------------------------
There isn't enough of a difference between the kernel where your phone shouldn't boot.
Click to expand...
Click to collapse
Decad3nce: I've re-partitioned it 3 separate times and every time it's a boot loop! Would you tell me if I'm doing this all in the correct order?
-Wipe everything.
-Re-partition sd card
-Enable USB toggle
-Move 2.7 and Googleshits from computer to Phone
-Flash ROM
-Flash googleshits.
-Reboot.
note: I was able to boot into 2.7 with the (pushed) 2.6.4 boot.img but I wasn't able to start wi-fi. So I'm assuming the 2.6.4 boot.img had something to do with that and that's why I'm trying a "virgin" 2.7 flash again.
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
bohiti said:
All I can say is I'm in the same boat. It seemed to me, in my earlier tinkerings, that my phone needed a boot.img that was slightly less overclocked. The few DarchDroid successes I've had were from lower-clocked boot.img's. Without it, I just look at the HTC logo forever.
Click to expand...
Click to collapse
That's really helpful info, Bohiti. I thought I was alone here!
I am in 2.7 now with the 2.6.4 boot.img but I'm unable to start wi-fi.
This is a dealbreaker for me.
Why would the boot.img affect wi-fi??
Well sorry, kind of. While what I said was true, I just now tried the hard reset suggested to you. (Menu+Back+Power). And then I wiped everything and flashed 2.7 and GoogleShits. And it booted fine, quickly. Only on HTC screen for 10 seconds maybe.
So I'm not in the same boat, though in the past I've had the same symptom with my phone. I haven't rebooted again, maybe I just got lucky.
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Decad3nce said:
Darch made changes to his kernel(so it boots at a higher frequency); your phone probably can't handle it then.
Bug him, jus10o, or me(tomorrow) about making a 710mhz bootable.
Click to expand...
Click to collapse
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
sariamanascar said:
Thanks decad3nce. I will do just that! And thanks for the info, bohiti.
Finally some positive news!
Click to expand...
Click to collapse
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Decad3nce said:
I lied. it defaults at 710 on boot. But, try booting 2.6.7 with no sd card in your phone. (do a full wipe, I mean everything)
Click to expand...
Click to collapse
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
sariamanascar said:
OK, just tried this two different times.
No boot loop(!) but now it just hangs on the HTC logo.
Any other ideas?
Bout to go ask Darch and jus10o for ideas....Btw, should I PM them or create a thread?
Thanks again for your help.
Click to expand...
Click to collapse
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Decad3nce said:
already told jus10o, but feel free to pm him or Darcj anyways. one of us just needs to compile a kernel that defaults and limits itself under 710.
Click to expand...
Click to collapse
Just PM'd them myself. Thanks for the help, Dec.
Has this issue been addressed? I am having the exact same issue. I have flashed just about every rom on XDA and never had any issues, but I am having the same problem with 2.7 and Buffed2.0...both overclocked kernels. On 2.7 if I do a few battery pulls the phone somehow gets past the HTC logo but everytime I reboot i get the boot loop again.
I have never had any issues like this so I have never had to pull a log. If this would be helpful i would be glad to do it but would need directions on how to.
For all future visitors: Dec was kind enough to modify a kernel that got GPS and Wifi working for me - so thanks Dec. Problem was, GPS eventually started crapping out and I had a whole bunch of force closes over the past week. Including my phone app even crashing on me.
Today, I finally gave up on 2.7 and am on to PureHero which is largely AOSP and (for the non-OC'd version) a lot more stable. While I don't like the look as much, for those of us on weak phones, I think it's the best option.
I had the same issue, but flashed the uv kernel and it booted fine ever since. Couldn't run 2.7 till then.
stand corrected
I recently flashed the UV kernel and I have to say, everything works great. I stand corrected - no one told me the uv kernel was the same thing as "under clocking" a a kernel but I guess that's what it does. Thx.
Worked for me too
Hi just wanted to add that the UV kernel also solved my bootloop problems with DD 2.7.
A few times before the UV I was lucky, and after the 2nd or 3rd iteration of the bootloop it would get past the htc screen and boot. Happened enough times to get hooked on 2.7 haha But the last time I rebooted the phone it was very stubborn and stayed stuck no matter what I tried. That sent me searching back here. Glad I found your post, I assumed the UV kernel was only for those having battery issues, based on the main 2.7 thread.
So I got a new G1 ( after I bricked my old one )
Came with 1.6
downgraded, rooted, installed radion, danger, CM6
booting now, I get cyanogen waving android and spinning circle, but it's been doing this for over 30 min now
Tried rebooting, taking the battery out and powering again, same thing
Any idea what's causing it ? a fix ?
Moe29 said:
So I got a new G1 ( after I bricked my old one )
Came with 1.6
downgraded, rooted, installed radion, danger, CM6
booting now, I get cyanogen waving android and spinning circle, but it's been doing this for over 30 min now
Tried rebooting, taking the battery out and powering again, same thing
Any idea what's causing it ? a fix ?
Click to expand...
Click to collapse
This happened to me, so..
Restore your backup so it's back to what it was (You did a backup?)
Install Amon RA 1.7, do a nandroid, then do a factory reset wipe thingy, then a Dalvik cache wipe, then flash CM6 and Google Apps (The tiny one) and then bobs your aunties live in lover.
I didn't have any apps but there's a thread on CM's forum about how to get them back which I'm gonna try tonight. It's cos of the way that FroYo handles the AppsToSD thing, apparently its FroYoToFAT now..
HTH...
Did you partition your SD Card?
strange,
I remember posting a reply to this thread but can't see it now
a wipe, re-flashing CM6 and installing google apps got it working
Thanks for replying anyways
Ok, I might have bricked my phone. I had the cm7/Aosp gingerbread mod. But I didn't have apps2sd enabled. So I downloaded rom manager, flashed the newest version of clockwork recovery, and rebooted to recovery, where I partitioned for apps 2 sd with a size of 256 mb and 128mb swap-space . I then factory reset, and formatted Boot, cache, data, everything. After that I went to mount as Usb, and I copied the Rom, gapps, and a battery icon mod back to the phone. But the phone didn't recognize any installable packages on my sd after I un-mounted, so I shut my Hero off in hopes it would when I turned it back on p) . When I turned the Hero on, it went to a Usb-fastboot mode, and I couldn't get it to turn off so I removed the battery from the back of my phone, then put it back in. Now my phone won't turn on at all. Does anybody know what I did wrong and can I fix it?
http://androidcommunity.com/forums/f60/how-to-apps2sd-for-droid-34800/
http://forum.xda-developers.com/showthread.php?t=666420
not sure if this will help but maybe you can find some info there
Hopefully that squared you away. But for future question, please post it in the general or question section. This area is specifically for devs and their projects.
oohaylima said:
Hopefully that squared you away. But for future question, please post it in the general or question section. This area is specifically for devs and their projects.
Click to expand...
Click to collapse
Alright sorry, I think I meant to post it there but then kinda freaked out >.<
spleef said:
http://androidcommunity.com/forums/f60/how-to-apps2sd-for-droid-34800/
http://forum.xda-developers.com/showthread.php?t=666420
not sure if this will help but maybe you can find some info there
Click to expand...
Click to collapse
Thanks Spleef, but I was wondering how to get my phone to turn on again as it seems to have just quit on me
Whenever a ROM doesn't boot up properly, boot loop, freeze, etc, I usually have to pull the battery out. Then when I restart it, I hold down the Volume Down and Power buttons at the same time to boot into recovery. Try doing this while the phone is plugged into your wall charger and see if that helps.
Also, I'm not 100% on how to get the apps2sd working, but I had a question about which version of Clockwork you were using. I thought with CM7 Gingerbread we were supposed to use version 3.0.0.5 of Clockwork. I know there is a new version, 2.5.1.7 I think, that shows up in ROM Manager. Unless something has changed, I don't think it will work with CM7.
I'm still pretty new to this, so hopefully someone else will chime in here for you.
Good luck.
i did the same thing one time you gota wipe everything again i mean even the sd card and extthen take ur sd card adapter and put rom gapps any extras on ur sd card then put it back into ur phone then flash it in the order of rom,gapps,extras,and kernel last if u are using one hope this helps
p.s this was using CWM 2.5.0.1
This just happened to me the other day, except I was trying to use firerats partition mod. See if it will boot by holding volume down or up while powering on. It worked for me, but I had to ruu back to stock and had reroot with z4root.apk
Sent from my HTC Hero CDMA using XDA App
Ok anytime you do a factory reset from the phone you most likely will loose root. And leave your phone charged over night it should come back on. And your swap is to big IMO. For apps to sd try a 28 or 32 swap and 512 partition. Then upgrade you ext from ext2 to ext3. And you were supposed to wipe everything before you flashed the apps to sd file. As in wipe everything data,cache,dev-cache and ext. Then flash your rom,google-apps,and kernel last. Boot up sign into your account and let it sync. Then boot to recovery and flash the apps2sd zip. After that you should install your apps. And I think you should ruu and reroot. Sounds like you lost root when you did factory reset from with in the phone. Just my opinion. Hope it helps good luck.
Something.About.Me.U.Dont.Like.
Its.Cool.I.Understand.AWAH
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
aposva said:
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
Click to expand...
Click to collapse
I am searching the forums to find an answer to the same problem. I am running stock eclair that has been autonootered. I don't have clockwork installed. I can always boot with the sdcard to Honeycomb.. sometimes I can then reboot back into Eclair.
i had this one time, i try the 8 failed boot's to restore, didn't restore but rebooted to eclair!
arf, i'm having the same problem after all..
I had the same thing happen to me had to reformat cache if I wanted to boot into froyo,its a great system but that one problem did me in went back to stock and rooted the NC and plan on staying this way I just give up flash.Looked all over for fix or someone to explain why but never did get an answer sorry i couldnt help you but if i find answer will let you know
ok will look forward when i have time
At this point i can boot by pressing power + n for 30s, it boot to recovery, then i choose "reboot"
Yes that's right, this is the only way I can boot too (power but. + n).
when rebooted i lower setcpu to 1ghz max. it seems to help to boot ..
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
I have the same problem too. Just remove the SD card on power on (reboot with software is OK)
Looking for better fix.
Taeseong said:
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
Click to expand...
Click to collapse
Thx, I'll take a look at that if I ever have booting issues.
Think this is caused by the recovery image. Upgrade your recovery to the latest version 3.0.1.0 and see if that fixes it.
http://forum.xda-developers.com/showthread.php?t=971197
Going to try that today ..I just looked and i do have an older recovery file so maybe that is the problem will report back later on it.
Did the update, I will shut it off for the night and will check it in the morning.
Sent from my Nook Color
I also read CWR does not get along with 1.1..I just updated CWR and it still did the same thing what Im going to do now is clean restore then custom froyo then after setup go to market get rom manager install reboot into recovery and then install the remove crw with root file.
I downloaded the restore to stock zip file. Put it on the sd card. Then used the power and "n" to get to the butloader. Chose install from sd card and it installed. Back to operational!
OK i got a nook, rooted using AN3.0 (it is 1.1.0) and then put cm7 Tab tweaks on the eMMC using cwm and flashed GAPPS and The latest OC kernel with I/O fix. my nook runs GREAT!
however a buddy of mine liked what he saw so he went out and got one, we used AN3 to root it, then flashed cm7TT, gapps, and the kernel and his acts funny. on the first boot after the flash we got an error saying something like "bad install, please contact B&N" so i powered down, back up, and it worked. Funny thing is when we boot it still has the nook splash screen "harness the power of reading" or whatever it says. also he frequently gets boot loops and it just runs really buggy. we tried re downloading the ROM and re-flashing (with the stock cm7 kernel this time) and have the same issues. also i can OC mine to 1190 easy, if he does anything over 1000 he gets freezes and boot loops....any ideas...the weirdest part is the "enjoy the power of reading" splash screen.....help?
Sounds like something didn't get cleaned up. So if I were you, I would get CWM on a sd card, then I would get the stock 1.1.0 image and reflash it. Don't nooter or anything like that, there's no point.
Then I would wipe the following... /system, /data, /cache and dalvik cache. Then after all that is done, go ahead and reflash the newest nightly (it has the tablet tweaks), also you're running Madkat's OC, grab the newest Daligrin one as it's more stable and may work better with his nook.