ive been running the energy rom for like two months now everything has been fine. today my phone hangs a little bit so i restart it and it wont boot all they way up!!! what do i do to fix this please help!!!its stuck at the screen right after the screen of the color sparklers.
[email protected] said:
ive been running the energy rom for like two months now everything has been fine. today my phone hangs a little bit so i restart it and it wont boot all they way up!!! what do i do to fix this please help!!!its stuck at the screen right after the screen of the color sparklers.
Click to expand...
Click to collapse
use the proven process of elimination, have you installed something recently?
a Manila Mod, or tweak? I hope you have a backup of everything essential
on your device, as it may that you need to HR
maybe its only a dead sd card..
take out sdcard, sim card and battery for a few minutes and reinsert only the battery and try to boot up...
if this doesnt work, you'll need an hard reset..
so i kept resttiing until it booted up. then i saw these posts and decided to restart the phone and it doesnt work again. so i reset again an pressed the talk button then it went to the launching sense screen. me being a gambler i reset it again and it stalled again until i hit the talk button. now i reset it a couple of more times and its back to loading normal on its own. im only stating everything i did just in case someone else might come across this problem at some time. thanks for you guys quick response and help
Try a full reinstall using the flashaholic app that does a full OS ROM format, also backup any files on the SD card and reformat that too and see what happens.
I should add that the full "task 29" format thing probably wont work well unless you have HSPL installed (otherwise you have to first install a stock ROM, then SSPL install your custom ROM; kind of defeats the point of the full format!)
So I am unlocked and running MIUI
I was in CWM and my dog bumped my arm while I was trying to go to "wipe data"..
Instead I think I went to partition internal sd.
There was no backbutton only a few options
0MB
4MB
8MB
etc
or something like that.
Since there was no back button, I just chose "0Mb" hoping it would do nothing.
Then I rebooted recovery.. but this time instead of recovery it gave me a full white text boot screen, saying "choose and option 1 through 9. You have 5 secs to choose or it will go to "BP" by default". And it listed all the options you would see if you scrolled through them with vol down, all in one list.
I tried to vol down to recovery and choose it, but when I do, it just reloads this menu. I can choose fastboot and RSD and it will load those, but recovery seems to be gone.
I also see the internal storage doesn't show up when I boot the phone and connect to PC.. only my external SD does. So somehow I screwed the pooch. I guess my best bet would be to reflash the recovery through fastboot?
hmm now my PC isn't recognizing my phone in fastboot mode.
I tried rom manager and flashing recovery from within miui.. but it just does nothing.
OK on reboot I tried Rom manager again and it works. It still has that menu on boot, but recovery works now
Did this before. Only solution I came up with is flashing the SBF and starting from scratch. Hope this helps.
Sent from my MB855 using Tapatalk
i did this exact same thing the other day... I don't know what menu it is that i accidentally got into but it wiped something and my recovery was gone... flashed an sbf and got stuck in a boot loop and finally fixed it by wiping data
ugh
get into RSD mode and then flash the stock Rom..
After installing just wipe data in Stock Recovery mode..
Thats all.. You are good to go...
Make sure you have 5gb free in the drive you Run RSD Lite..
Yea I reflashed stock SBF and now it boots stock photon tho its stuck on "Contacting Network". reboot not helping.
The other day I was trying to back out of the advanced menu and ended up with multiple partitioning options with no back button. Selected one of the options. Lost all my photos
I could have tried to recover the data but decided it wasn't worth it.
I see a topic here with my problem:
http://forum.xda-developers.com/showthread.php?t=1284956
Tho I AM on the stock sbf so not sure why it is happening.. gonna try sbf again
sub2k1 said:
The other day I was trying to back out of the advanced menu and ended up with multiple partitioning options with no back button. Selected one of the options. Lost all my photos
I could have tried to recover the data but decided it wasn't worth it.
Click to expand...
Click to collapse
Why didn't you just pull the battery?
http://forum.xda-developers.com/showthread.php?t=1555948
Akilldema said:
Why didn't you just pull the battery?
Click to expand...
Click to collapse
I was being lazy. I figured that perhaps I accidentally hit a button combo that caused the back button to disappear. So I figured that a button combo might make it come back. Well I didn't find that button combo. I immediately pulled my battery when it said formatting SD Card but at that point it was too late.
sub2k1 said:
I was being lazy. I figured that perhaps I accidentally hit a button combo that caused the back button to disappear. So I figured that a button combo might make it come back. Well I didn't find that button combo. I immediately pulled my battery when it said formatting SD Card but at that point it was too late.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1496012
This happened to me because the back button too.........
Sadly, getting the menu to go away is not the main issue, you have actually erased your PDS partition which holds factory hardware information like MAC /bluetooth adr and stuff for the PRL/Data profile updates to recognize your phone.............Flashing the PDS partition from the Atrix Forums will create the partition but we need like a dev to help us figure out a solution for editing the files to work with Sprint software updates and getting all our hardware addresses on there correctly. No amount of flashing/SBF'ing stuff helped to get it working... some users suggest taking it to Sprint..
Oh so thats why I can't update my prl and profile. I had this happen a while ago and I just flashed a custom splash screen. Gonna go back tp stock and start it all over again. And if that menu happens to come up again i'll just pull the battery.
Plancy said:
This happened to me because the back button too.........
Sadly, getting the menu to go away is not the main issue, you have actually erased your PDS partition which holds factory hardware information like MAC /bluetooth adr and stuff for the PRL/Data profile updates to recognize your phone.............Flashing the PDS partition from the Atrix Forums will create the partition but we need like a dev to help us figure out a solution for editing the files to work with Sprint software updates and getting all our hardware addresses on there correctly. No amount of flashing/SBF'ing stuff helped to get it working... some users suggest taking it to Sprint..
Click to expand...
Click to collapse
It seems like it would be possible to dd a PDS partition image from a working phone and flash it to the phone with the bad PDS parition via fastboot as long as you knew the partition it needed to be flashed to, although it would have the data of the other phone (as far as bluetooth, MAC addresses). Not sure how to go about editing in the info you need though. Just tossing out ideas
-devx
This might help...hope it does.
I had formatted my internal SD which toasted my PDS partition.
I fixed it doing this...
http://forum.xda-developers.com/showthread.php?t=1575035:)
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD
Hello everyone, this is my first post here. I have an original nook tablet that I had rooted back in the day when I was quite a bit younger. If im correct I tried to factory reset it and it didn't quite work. I recently came across the tablet again and decided to fix it once and for all. I attached a photo of the issues I am having. I am honestly assuming I bricked the thing. Help would be appreciated! I'm looking to either get the nook back to factory state, or even root it and flash an android system onto it. Whatever is easier to be very honest. Looking forward to hearing from you all,
-Devin
devin.vorgang said:
Hello everyone, this is my first post here. I have an original nook tablet that I had rooted back in the day when I was quite a bit younger. If im correct I tried to factory reset it and it didn't quite work. I recently came across the tablet again and decided to fix it once and for all. I attached a photo of the issues I am having. I am honestly assuming I bricked the thing. Help would be appreciated! I'm looking to either get the nook back to factory state, or even root it and flash an android system onto it. Whatever is easier to be very honest. Looking forward to hearing from you all,
-Devin
Click to expand...
Click to collapse
Hi, try to download the firmware for your tablet and flash it to the tablet.
Jan Skokan said:
Hi, try to download the firmware for your tablet and flash it to the tablet.
Click to expand...
Click to collapse
Hello Jan!
That's what I was originally trying to do, but I couldn't find a tutorial on the whole process. Thoughts?
devin.vorgang said:
Hello Jan!
That's what I was originally trying to do, but I couldn't find a tutorial on the whole process. Thoughts?
Click to expand...
Click to collapse
If you think the tablet is truly "bricked" you may want to prepare a rescue card (https://www.mediafire.com/file/07fbs2usj7pk0pp/bn_142_factory_recovery.zip/file) to restore the factory partitions, etc. This will put you back at FW 1.42, but that doesn't matter if you're going to flash a custom ROM.
Once you're sure the device is functional you could flash a new ROM. If you have the 8 gb model, then the place to go is here: https://forum.xda-developers.com/t/...nd-for-the-8-gb-nook-tablet-bntv250a.3667555/
If you have the 16 gb model, then here: https://forum.xda-developers.com/t/...-internally-on-the-16-gb-nook-tablet.3578665/
nmyshkin said:
If you think the tablet is truly "bricked" you may want to prepare a rescue card (https://www.mediafire.com/file/07fbs2usj7pk0pp/bn_142_factory_recovery.zip/file) to restore the factory partitions, etc. This will put you back at FW 1.42, but that doesn't matter if you're going to flash a custom ROM.
Once you're sure the device is functional you could flash a new ROM. If you have the 8 gb model, then the place to go is here: https://forum.xda-developers.com/t/...nd-for-the-8-gb-nook-tablet-bntv250a.3667555/
If you have the 16 gb model, then here: https://forum.xda-developers.com/t/...-internally-on-the-16-gb-nook-tablet.3578665/
Click to expand...
Click to collapse
Thank you so much for the links. I will be sure and check them out as soon as I get the chance!
devin.vorgang said:
Thank you so much for the links. I will be sure and check them out as soon as I get the chance!
Click to expand...
Click to collapse
nmyshkin said:
If you think the tablet is truly "bricked" you may want to prepare a rescue card (https://www.mediafire.com/file/07fbs2usj7pk0pp/bn_142_factory_recovery.zip/file) to restore the factory partitions, etc. This will put you back at FW 1.42, but that doesn't matter if you're going to flash a custom ROM.
Once you're sure the device is functional you could flash a new ROM. If you have the 8 gb model, then the place to go is here: https://forum.xda-developers.com/t/...nd-for-the-8-gb-nook-tablet-bntv250a.3667555/
If you have the 16 gb model, then here: https://forum.xda-developers.com/t/...-internally-on-the-16-gb-nook-tablet.3578665/
Click to expand...
Click to collapse
sorry for the extremely late reply. I "burned" the recovery file to my micro SD card but the nook refuses to power on with the SD card inserted. I am so confused, any thoughts?
devin.vorgang said:
sorry for the extremely late reply. I "burned" the recovery file to my micro SD card but the nook refuses to power on with the SD card inserted. I am so confused, any thoughts?
Click to expand...
Click to collapse
That's the first time I've heard of something like that. Will it start up wth the card in place if you plug in a power cable?
Edit: FWIW, if you can get the tablet to boot with the card, here are the original instructions for restoring the device with the card: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Edit, Edit: And...if you still can't get the tablet to boot with a card in it, try this:
Perform Factory Reset of the Nook Tablet:
PWR off the Nook Tablet.
Hold "PWR" & "∩" buttons simultaneously to reboot.
After reboot, release the "PWR" & "∩" buttons after 2-3 seconds upon receiving the "∩ - Contains Reader® Mobile technology by Adobe Systems Incorporated." screen.
The screen may blink a couple seconds later and then you will be presented with the Factory Reset screen with the following options:
Do you want to reset your device to the factory default?
Press POWER key to exit
Press HOME key to continue
Are you sure?
This will delete all your content and restore the device to the factory default settings.
Press POWER key to exit
Press HOME key to continue