HI Fellow XDA Members
I've literally finished the 4 hour update marathon thanks to a failed update to 1.20.
Why did it fail? I was rooted and had a custom keyboard installed. After I got the keyboard back to stock, the screen kept pulsing on and off. (long story)
If you want to save your self the anxiety I went through of having to do EVERY trick in the hacking book to get my device back to stock.
Basically you MUST follow the 8 failed boots to get the nook to recover itself. If that didn't work then move onto booting Froyo from an SD card and recover using CWM.
So yeah just over 4 hours later and nearly having a panic attack becuase I thought my nook was dead, it's on 1.20
Related
it was working fine with both restoring and backing up my roms before (jm5), but once I've flashed over to jg8 it's stopped working.
one thing that's different is that I applied RyanZA's lag fix that makes use of ext2.
to be honest I don't even think that's the cause but I'm just putting putting it there for information's sake.
any help is appreciated, thanks.
had this on my phone right today as well...was trying to do a backup after a flash -
it's not that it stopped but it just really takes an awful long wait to finish that part of it
really? I guess I'm not a man of patience but the first backup went by faster! I shall give it another try when I'm not using the phone, thanks.
Yeah,i did this last night. Was worried it wasn't going to complete however just left it to it a bit and it does get through it.
Sent from my GT-I9000 using XDA App
Yeah my EXT2 doesn't play nice with backup programs. Someone could make a new backup program that supports it, I guess, but that's probably not going to happen. It should be just temporary until either samsung gives us a better update, or someone cooks up a custom rom that won't need it.
well then, I'd rather have no lag than anything! damned samsung...
I can confirm this
I have a Bell Vibrant. I first applied the OCLF. Pressed Volume up, plus center button, plus power and booted into recovery.
Applied update.
Rebooted.
Went back into OCLF and played with all the other optimizations.
Installed Rom Manager.
Tried going straight to backup - rebooted into recovery and failed.
Installed nandroid recovery. Rebooted into nandroid recovery -> Great Success!
Clicked backup and everything seemed to be going well till it got to the file
linux.ex2
Then it seemed to be stuck for 3-5 minutes. I was reading this forum page when it got going again.
Great Success!
Thank you all!
For me, it stopped for about 5-7mins. It went again after I had a cigi.
So I was trying to restore back to my stock ROM backup using the boot strap recovery. There weren't any errors during the process of restoring the image but when it was time to boot the phone up it would stay in a bootloop.
I have tried factory reset with the power button and volume buttons but it'd go straight back to the loop.
I am trying really hard to understand this whole adb thing with the sdk program but I have no idea how to use it.
Can anyone please help this noob?
Return to stock - Windows.
FAQ sticky in the Bionic Development forum.
Thanks for the reply. I'll try this out when I come home from work.
Also, I reactivated my droid x until then. Will I need to go to Verizon for a new sim card for my bionic once I can start it up again?
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
I believe you may have to go for a new SIM card. The way the Verizon explained it to me when I returned my Charge was when you deactivate from a 4G to 3G only phone, that SIM is lost. However, 4G to 4G is fine.
Wouldn't hurt to try, but a good possibility you will have to.
Sent from my DROID BIONIC using xda premium
idefiler6 said:
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
Click to expand...
Click to collapse
About 2 hours after I said this, I bootlooped. Good thing this FXZ method works!!
haha yeah with all the new roms u cant help but to explore.
btw after 5 FAILED flashes I tried one more time with rsdlite and it finally worked!
It took about 20-25 minutes for the whole process to fully boot up my phone but I am very happy and thankful for the people on this forum.
The weird thing is that when it booted up... it booted up to an old restore of UNL3ASH3D. confused but im happy its fully functioning.
You won't need a new SIM card. I did an FXZ restore after I rooted my phone, unrooted it (didn't need to have it rooted because there were no ROMs and no CWM yet) and it wouldn't let me root again so I flashed to stock and it rooted just fine. You will need to flash the radio again though (or at least I did after installing DroidTh3ory's ROM because it kept showing 3G in spots I know i had 4G, worked fine after I flashed).
Hey guy's Im hoping you can help me.
Last night while browsing my phone froze, so i performed a battery pull and on putting it back in the phone refuses to boot.
If i plug thr charger in alone, the LED's blink orange/green
If i place a battery in the charging light turns on. I have two batteries so I tried them both. Still nothing.
I was able to boot into recovery and tried to clear the clash and do a full reset. upon reboot the phone stuck on the boot screen.
I tried a battery pull once again, and since that I have only been able to get the phone to boot once after numerous tries only to get 7 vibrations.
The power button still works, if i try turning it on while on charge the orange light goes out, but nothing.
Ive tried the battery trick while on the charger alone the green light goes on but again nothing, I've tried different chargers, I'm now at a loss.
While typing this IVe been able to get it to boot once again, but again i get 7 vibrations and nothing.
Any help would be appreciated, I have no phone, while my GNEX is being repaired under warranty
A noob question... you said that you do a full reset... Did you flash the rom again? (give more details.. rooted phone...hboot.. rom...)
Obsy said:
A noob question... you said that you do a full reset... Did you flash the rom again? (give more details.. rooted phone...hboot.. rom...)
Click to expand...
Click to collapse
full reset as in going into recovery and wiping everything, unfortunately, I have note been able to get back in since to try and reflash a new rom.
I'm currently running a stock hboot, with the last stable release of MIUI before MIUI4 cant remember the exact version number. The phone is rooted and locked.
Thanks for the swift response
poseoff said:
full reset as in going into recovery and wiping everything, unfortunately, I have note been able to get back in since to try and reflash a new rom.
I'm currently running a stock hboot, with the last stable release of MIUI before MIUI4 cant remember the exact version number. The phone is rooted and locked.
Thanks for the swift response
Click to expand...
Click to collapse
Why don't you copy the miui zip onto your SD card, and flash it back from recovery? If you are running GB MIUI, the last version for that would be 2.3.30.
Sent from my Nexus One using xda app-developers app
sphinxcs898 said:
Why don't you copy the miui zip onto your SD card, and flash it back from recovery? If you are running GB MIUI, the last version for that would be 2.3.30.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Agreed, I've preped my SDcard with a Passimg.zip. however I'm at a point where I cant get the phone to turn on constantly. since posting this morning. I've had no success - c'est la vie. I'm reluctantly thinking of moving on, however I really loved my N1 believe it or not it was much more reliable than my GNEX which is in under warranty repair for the 3rd time already!
Let me tell you a story. I once brought a Galaxy Note form Flipkart.com . When it arrived, it had features rivalling that of the iPhone 5, but had half the price and a larger screen size at that. I was over the moon. It seemed like nothing could go wrong.
I rooted it the day after it came. Almost miraculously, you had features like dual-boot animation. I, of course, in my inimitable stupidity, forgot to make a Nandroid backup. But who cared ? The device was up and running.
That's when the nightmare started. It just started out as minor blips - Google Play saying that authentication required or sevrver error or offline mode ( whatever the hell that means ) ; Google Talk forever on offline mode ; Gmail not being able to sync. These and more warning signs appeared, but I brushed them aside, thinking that they would be fixed with the passage of time. In retrospect, this was a very stupid thought.
Then the hell started. Galaxy offered a Jelly Bean Update. In my steadfast optimism, I downloaded it and installed it. Nothing changed. Absolutely ****ing NOTHING. My mother's sister, who was Android Development Head, informed me that it was due to some conflict between TouchWiz not being compatible with Android Jelly Bean. Then apparently, since the update was downloaded and not installed, it kept informing me that your update is due, and kept asking me whether I would install it. I, obviously kept saying NO. Some stupid person on androidforums told me to freeze Samsung Updater using Titanium Backup. But, my friends, the worse was yet to start.
As soon as I froze Updater it crashed. I had to force start using Recovery. Then the device wouldn't give any signal and even WiFi stopped working.
I then unfroze Updater, since that was the natural action one would take. It crashed again and on force start it said - " Android Updating, Start Applications... ". There was no signal whatsoever.
Then it seemed like Satan had reserved a special place in the depths of Hell for the Note. Every thirty seconds the Note would crash and give the same message which I listed above. Some person on some random forum suggested moving all the apps from the SD Card to Internal Memory. Well, great suggestion, because whenever I tried to open settings, Note would, very conveniently, crash again.
I tried backing up using ADB. Crash. Factory Reset attempt. Crash. Crossing my fingers. Crash. Just isolating it and keeping it on a bookcase. Crash.Crash all the way.
I've run out of ideas, so from my long post, if you have figured anything that might be of use, don't hesitate to reply
Regards And Thanks
Sid
Just download ROM of your choice, stock or custom. Use pc odin to flash stock rom or cwm to flash custom rom.. Head over to dr ketans thread for list of stock roms be it jb, ics or gb. If you still can access custom recovery (dont wipe on stock recovery) do all the wipes like /system /preload /data /cache(ofcourse if u dont want to backup anything important ) and the flash the stock or custom rom
Sent from my GT-N7000 using xda app-developers app
try Cursed4eva on youtube...this guy's videos would definately help u....btw u did tried flashing an official rom right?
Usually a factory reset and stock rom solves evrything
Sent from my GT-N7000 [better than gtn2] using xda app-developers app
Several months ago I wanted to sideload apps (mainly for humblebundle) on my Nook HD so I followed the dummies guide instructions and got it all working, I remember the whole CWM thing coming up first time and it all going swimmingly. I put the little boot sd card away and then somewhere along the line either lost it, or someone in the house swiped it for themselves. So anyway I don't have it now. All was going well and then everything started crashing ALL THE TIME on my Nook HD, so I decided to wipe it as I wanted to put everything on a bigger sd card anyway. I thought wiping it would unroot it, because I don't know anything, but now I realise it didn't, it still comes up with Cyanoboot when booting up, but it has forgotten the side load app stuff I could do, it won't let me install them anymore. But it's definitely rooted, I just have no idea to what version (must be 10 something) because I am able to use link2sd no problem. So I have been trying to recreate the boot sd, so I can flash the sideload app thing and it is not working. I have followed all the steps carefully again and again, and tried on 3 different sd cards, and it will not boot from that little card at all, just boots normally every single time. Is there any other way I can get this one little setting to work? I'm not all that interested in putting 11 on there, just want this one thing to work. Is there a way to unroot the whole lot so I can just try and start over? Frustrating.
Have you tried to boot to internal CWM? If you followed the dummies guide you should have it installed internally. Look at the latest version of the dummies guide for how to set it up to boot to internal CWM.
Sent from my BN NookHD+ using XDA Premium HD app
"but it has forgotten the side load app stuff I could do, it won't let me install them anymore."
Can't really figure out what your talking about from all your confusion.
Put cm on there and its one little check box from within android @ device settings -> security -> unknown sources. Everything you did would be non-valid.
If your talking about the offical bn rom, then I have no idea how the rooting effects sideloading.
leapinlar said:
Have you tried to boot to internal CWM? If you followed the dummies guide you should have it installed internally. Look at the latest version of the dummies guide for how to set it up to boot to internal CWM.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Ok, I have tried to do this, and it won't. Every time I try it just comes up with a factory wipe question. I even tried downloading an app to boot into recovery, and it just rebooted normally.
Is there a way to just completely unroot easily and start over? Or is there something else I can try? Seems like getting this thing to sideload apps should be fairly simple, but it's not turning out that way.
sandsofmyst said:
"but it has forgotten the side load app stuff I could do, it won't let me install them anymore."
Can't really figure out what your talking about from all your confusion.
Put cm on there and its one little check box from within android @ device settings -> security -> unknown sources. Everything you did would be non-valid.
If your talking about the offical bn rom, then I have no idea how the rooting effects sideloading.
Click to expand...
Click to collapse
Sorry for the confusion, I'm confused and frustrated with this.
Basically, my nook hd is rooted. I flashed it so it would sideload apps. All was well. Then all was not well, and I factory wiped it. It is still rooted apparently, but it no longer lets me sideload apps. I no longer have the sd card that I originally rooted it with. I want it to sideload apps. I can't figure out how to make that happen.
ladyynara said:
Ok, I have tried to do this, and it won't. Every time I try it just comes up with a factory wipe question. I even tried downloading an app to boot into recovery, and it just rebooted normally.
Is there a way to just completely unroot easily and start over? Or is there something else I can try? Seems like getting this thing to sideload apps should be fairly simple, but it's not turning out that way.
Click to expand...
Click to collapse
That message means you still have stock recovery installed. To easily start over, just interrupt the boot 8 times in a row by hard powering off the device before the boot completes. Hard power off means holding the power key for several seconds until it turns off. On the 9th boot, let the boot continue and it will reset itself to stock the way it came in the box. Then you can start over using the dummies guide.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
That message means you still have stock recovery installed. To easily start over, just interrupt the boot 8 times in a row by hard powering off the device before the boot completes. Hard power off means holding the power key for several seconds until it turns off. On the 9th boot, let the boot continue and it will reset itself to stock the way it came in the box. Then you can start over using the dummies guide.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks so much, I think that worked, after a few attempts it did a different kind of loading while saying nook and didn't say cyanoboot, and has reset itself. Now to try again!