Related
DLed the flashrec-20090815.apk
the first time there was no install button using astro
I DLed it again and added it to the SD card and tried again
Installed fine
Backed up fine
I clicked to flash cyanogen recovery 1.4 and its been on the flashing "working do not interrupt screen for about 30 mins
I expected possible problems, just not right away with the auto flasher lol
Its a G1 with 1.5 if it matters
thanks for the help
well its been quite a while now, phone seems to work
Just the flasher is stuck on "flashing do not interrupt"
I guess ill leave it overnight and check back in the AM
I dont want to kill the app if it will screw something up
it probably got stuck doing something because it shouldn't take too long to flash a recovery image.
Thats what i figured
In searching even some of the videos showed how quick
Im just not sure how safe it is to try and close the app
figures
i haven't used the one click before so i honestly couldn't tell you, though you can always power off the phone and hold home and power to boot into recovery
and see if it worked then if it did i can give you the commands to mount your sdcard from recovery
I guess thats worth a shot. I wasnt sure if it would brick if i tried to reboot or anything
figured it was like flashing firmware in other devices
Ill try now
let me know how it works out
Ok, booted to the normal android screen
rebooted and noticed the SD card had the backup
so i guess it stopped half way. trying again now
did you try to boot into recovery? with home and power
Yes. and thats where i saw the normal android recovery screen not the cyanogen I've seen pix of
its been backing up for about 4-5 mins now
i didnt think anyone would be up this late lol
i am usually always on here till 4 or 5 am
Hmm, now it seems to be hanging on backup
If this doesn't work Ill just give up for the night maybe try again tomorrow
So when it got stuck on backup i recovery booted again, no changes so i removed the backup from the SD card (saved to pc just in case)
loaded the app again
now it backed up and flashed in 2 clicks
now for the rom
Also worth noting is this time the phone wasnt plugged in to the USB port
at first i didnt think it would matter since it wasnt mounted
not sure which fixed it.
Just passed the android screen. now i see a black screen.
so far its been booting for 12 mins. Ill give it a few more
Spoo76 said:
Also worth noting is this time the phone wasnt plugged in to the USB port
at first i didnt think it would matter since it wasnt mounted
not sure which fixed it.
Just passed the android screen. now i see a black screen.
so far its been booting for 12 mins. Ill give it a few more
Click to expand...
Click to collapse
if it won't go past the black screen, boot into recovery and wipe and reflash your rom. that fixed it for someone i was helping earlier.
Thats what i was just about to do lol
BTW your Guide is very clear and to the point
I looked around at the older methods and a few other guides just to be sure i knew what to expect
( was still caught off guard a bit lol )
Signing back into google, thanks a bunch!
Spoo76 said:
Signing back into google, thanks a bunch!
Click to expand...
Click to collapse
woot glad you got it to work. welcome to the world of a rooted g1 enjoy
Im already looking forward to trying to brag, then explaining why its cool and then seeing peoples eyes glaze over haha
i rooted my NC with 1.1.0 and everything was perfect. installed and backup with CWR v 3.0.0.5. I have been stuck in the two screens of cwr. I CANNOT TURN off the nc so 8 aborted on/off s do not work. I cannot restore from sd card since it boots back into cwr, so i have not been able to use any removal code. the Monster pack is not for 1.1. I think I may be bricked. How do I get out of this clockwork recovery program (i have tried all of the options in it too, including fixing permissions, recoveries and endless useless reboots. HELP!
Hold the power button and it will turn off.
i have done that but it turns itself right back on again. it will not stay off. when it does go back on, it goes right back into clockworkmod recover (orange menu screen, landscape only)
Try going here and see if that gets you out of trouble .. Hope it helps
I can't say for a fact that this will make a difference for you, but it certainly can't hurt. Make sure you plug in your Nook Color to the charger, then do the manual power off (as in hold the power button). That should force it to reboot.
Those were the instructions I was given when CWR froze up on me during a kernel flash and it worked. Good luck.
got any mortar-bricked!
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Boot CWR off monsterpack SDcard and restore stock system.img/boot.img. This saved me. This is definitely auto-nooter 3.0.0 related because pre-rooted BN 1.1.0 flashable does not have this problem.
ddd22 said:
got it tuned off. now totally dead.. does not respond to power switch at all now. beware of CWR!!!
Click to expand...
Click to collapse
no can do...cannot be turned on. stone dead
It is not. Trust me, I've has this thing twice today. boot partition on emmc is messed up I guess. You CAN boot from CWR on SD card.
ddd22 said:
no can do...cannot be turned on. stone dead
Click to expand...
Click to collapse
With all due respect, I dont understand how that can be. When I press, or press and hold the power key, nothing at all happens. no screen or light activity of any kind... like someone removed a battery.
After your reply, thinking perhaps my removed micro sd card might make a difference, i put it back in and tried again to power on the NC.. nothing happens still. Are you telling me that somehow if i change the content of my SD card to the Monster Pack that somehow that firmware code is going to turn on the Nook even though i cannot power cycle it at all without that magic? I dont understand how this could be and creating that card is a fairly steep search and discovery mission for me which i am willing to do if it has a chance of working.
btw, the battery is fully charged according to the green N on the usb cable.
Thank you so much for your response.
zdrifter said:
Try going here and see if that gets you out of trouble .. Hope it helps
Click to expand...
Click to collapse
What he/she said.. Happened to me once today. Remove the CWR and you should be good to go
how do i do that when no matter what i do the NC will not power on at all...zero. I can no longer even establish a usb connection to the computer.. it detects something and then tries and fails to install required drivers (which were previously installed and previously working). As much as I wish you all are right and I am missing something, I think I may be the first fool to brick the unbrickable!
You will need to make a bootable SD card and boot off that.
i made a bootable cwr sd from the monster rootpack. same nothing happens. will not power on in any way shape or form. will now remake the card with the full rootpack and pray that i can eat my words.
chomp chomp chomp
(the glorious sounds of words being eaten). you both were 100% correct and trust you i should have even more. I followed your advice despite my doubts and I wrote the rootpack image to the sd card and held the power button for about 15 seconds and alive she came! now i am at least back to my cwr that i cant get out of. i now could use a little more of your wisdom as to the best next steps. should i remove cwr then reflash with say 1.1.0R2 or should i figure out how to use cwr to do that flash, and remove it after the flash is completed. obviously a newbee to flashing this device (less than a week old), but have been following Energy on HTC flashes for long times. There is so much information here, it is almost too much when you first step in and your collective willingness to help this doubting thomas is extremely appreciated. my apologies and my deepest thanks. more reading coming up..
resolved!
i added the zip for 1.1.0 -r2 to the monster sd boot card and installed the rom from there. setting it up now. thanks to all for not listening to my doubt and telling me to continue as instructed. forever grateful
ddd-22 - did you install from CWR after rooting 1.1 using the modified Autonooter, or did you sideload the rooted 1.1?
I installed CWR from a 1.1 that was rooted using Autonooter (modified for 1.1) and ended up in a CWR reboot loop similar to what you had.
Yeah- I attempted to run the OC rom after autonootered to 1.1 and got into the loop. Has anyone had succes in loading the OC rom after autonootering to 1.1? Thanks
Thank you for this thread. The exact same thing happened to me after trying to flash a kernel using CWR and autonooter3.0. Thought I was bricked for sure!
I am back to business and glad not to have an expensive paper weight!
though i am on the way to recovery, not fully there yet. the r2 prerooted version was great except i could not log onto gmail... it kept seeing the NC as a phone and was looking for a cellular network, and gave me the message "a reliable connection with google servers could not be made" or some such verbage.. In the pre rooted 1.1. r2, i followed the directions going through youtube etc, but that did not work. so i decided to try to restore the backup i made when i first got caught in the doloop. which i did again, so it is back to monster to start over again and clear out the NC. I have been scouring other sites and many people have been having this problem. I wish i could remember how i installed cwr (method) but cant. however, what i found fairly consistently, and i believe i made the same mistake, was not restarting the NC before i made the backup. seems that is what got a lot of folks into this doloop crisis. if anyone has a plan of how i should get back to my previous state of bliss, let me know. I am remaking monster pack again and clearing out my machine.
Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.
MentalDragon said:
Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.
Click to expand...
Click to collapse
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.
BarryR1 said:
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.
Click to expand...
Click to collapse
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Is this going to help me. My original firmware was 1.0.1.
Just grab the CWR 1.1 Recovery image from the development forum. Burn that onto an SD Card and reboot. Wipe data boot system cache and flash. done.
Find rootpack in dev section, write that to sd card, add the flashable restore to stock zip from samuelhalffs restore to stock thread in the dev section to your sdcard, boot to sdcard with the rootpack on it, flash the restore to stock zip after formatting system and data. Wala, fixed! All info can be found in my dummies guide to my nook won't boot a few threads down.
Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.
MentalDragon said:
Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.
Click to expand...
Click to collapse
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?
khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Oops. My bad. Sorry for the misinformation.
MentalDragon said:
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=949699
Try this Thread, "Dummies Guide to Fixing 'My Nook Won't Boot'""
This should work and get you back to stock so you can start all over.
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
Bear with me while I try to explain (and remember) what happened to get me to this point.
--
Last night I was using WeUI and decided for a switch so I flashed AOKP Build 34 and the flash went well. I then tried to do a restore using MyBackup Pro with an older backup which it didnt work because it couldnt find the directory (even though I put it in the right one but that isnt important). After that I turned away from the phone for a minute or so and when I looked back, I saw that the screen had darken and the AOKP unicorn was on the screen. At which point I thought the phone had froze along the way somewhere and so I took out the battery and restarted the phone. I then started the phone back up and I got this screen saying there was an issue with the phone and I needed to reboot it.
I did but it brought me to CWM recovery, which I thought was odd but then figured I just needed to reinstall the rom, so I was going to but it only showed me my external sd card and I couldnt get access to my internal sd card and left it for the night. Then today (after getting into download mode) I tried using the odin3 1-click to JF6 which succeeded but once it completes it just throws the phone into bootloops.
So now I am at the point where I am out of ideas of what I need to do, but luckily I am still able to get into download mode and recovery mode so its not SO bad right guys? *fingers crossed*
Any help would be appreciated in this little pickle I am in.
You have suffered from the Encryption unsuccessful problem. Right now your phone is a paper weight. Gotta wait until there is fix found... Sorry
b-eock said:
You have suffered from the Encryption unsuccessful problem. Right now your phone is a paper weight. Gotta wait until there is fix found... Sorry
Click to expand...
Click to collapse
Damn. Really? I guess the only good thing I have going for me is that it isnt my main phone anymore so I guess I can afford to wait it out and hope that a fix can be found in the somewhat near future.
b-eock said:
You have suffered from the Encryption unsuccessful problem. Right now your phone is a paper weight. Gotta wait until there is fix found... Sorry
Click to expand...
Click to collapse
So wait, If you get that screen you cant use your phone at all 0.o
Correct :/
If you're interested, there's a thread in the Development section (look for "Encryption Unsuccessful") that talks in great length about this issue.
Some people (myself included) have dodged a bullet because the Android angels smiled and allowed them to flash a stock ROM before the device marked the Internal SD as encrypted. Most people, however, aren't as lucky and have an inaccessible Internal SD.
Not trying to contradict b-eock, just wanting to futher expand on the post.
not arguing, but he has already suffered so I didn't include that part
b-eock said:
not arguing, but he has already suffered so I didn't include that part
Click to expand...
Click to collapse
Good point.
jmtheiss said:
If you're interested, there's a thread in the Development section (look for "Encryption Unsuccessful") that talks in great length about this issue.
Some people (myself included) have dodged a bullet because the Android angels smiled and allowed them to flash a stock ROM before the device marked the Internal SD as encrypted. Most people, however, aren't as lucky and have an inaccessible Internal SD.
Not trying to contradict b-eock, just wanting to futher expand on the post.
Click to expand...
Click to collapse
Yea I found that thread just now, and I will probably give it a shot, good thing I bought a big microSD card to use with this phone. So if I do this method, that means that the internal sd card is completely shot then and no chance of it being used again?
jonnyg1097 said:
Yea I found that thread just now, and I will probably give it a shot, good thing I bought a big microSD card to use with this phone. So if I do this method, that means that the internal sd card is completely shot then and no chance of it being used again?
Click to expand...
Click to collapse
Correct, for now we know the cause and steps that lead to this issue but there is currently no solution to get the internal sd back.
This thread gave me another clue. I posted in the Encryption thread to stay centralized.