i've searched high and lo, been reading up on this forum for awhile now, reading the tutorials, etc. i must now hang my head in shame. managed to root my phone, put android revolution ROM on it, yay go me. decided i wanted to restore back to previous ROM. couldn't boot into bootloader via vol - and power, so i used ROM manager. went into backup/restore and picked a previous version. rebooted phone and now it hangs on the white HTC screen. i can take my battery out and put it back in and it will charge my phone. i think this might be my mistake, the battery was yellow when i tried all this. but it's been charging for awhile now, and still nothing. when i try to turn it on or the vol- and power it gets stuck on the white screen and is no longer charging. i've looked and looked and seen some suggestions of booting into recovery, etc. but i can't for some reason boot into anything. i'm not sure if i'm doing something wrong or what. any help or suggestions would be greatly appreciated.
ok, when i take the sd card out, it boots just fine, so what would my next step be?
Haha....you didnt wipe your device clean before restoring from your backup!
Remove the battery and place it back in, hold the bottom volume button and lock button...you should boot into Hboot(white screen also)
give it like 20 seconds because it will search for a file and select the recovery option by scrolling using the volume keys.
factory reset phone and go into advanced-wipe dalvik-cache
now install any rom or any backup!
You must do this for every ROM and every restoring of a backup...
thank you for your response, but i corrected my mistake, and wiped everything, but the backups i was trying to go back too still didn't work. still got stuck on the screen. i was however able to flash the ROM i had, but it's very basic, and nothing like what i flashed from it originally.
Related
Alright. This is a 100% stock Nexus S- nothing "development" wise was done to the device, no system tools installed that could cause issues, basically nothing but basic apps loaded on the device.
It just started today. I was working on my bf's Vibrant (another, more successful story) and grabbed my Nexus and hit the power button and it did not turn the screen back on. Holding the power button down did not reboot the device, and none of the buttons would light up or function.
So, I pulled the battery. Now every time I try to boot, it hits the "Google" screen and stays put. I left it alone for 5 minuets hoping it would finish booting and nothing. The soft buttons will light up, and if I touch them they register the touch but it does not help the phone to boot.
I do know that the phone was basically dead right before this happened, and at first I thought it was just dead. However, its been on the charger for at least 30 minuets- which should have given it enough of a charge to boot up, and still nothing.
What could cause this issue?
I did install a couple of new applications today, and I know the market updated a bunch of them but they're all apps that I've had on several phones (minus the two new ones today) and have never had an issue with any of them. The two new ones I downloaded were OS Monitor, and a 2G/3G toggle for hopes of improving some battery life.
But those are the only two things I've done differently. I've only been using the phone for a week but I haven't had any problems at all, before this.
Now- if worst comes to worst I can seem to get into the bootloader, and through that, stock recovery. So I can try to do a factory reset and wipe cache but without a backup I really kinda hope thats a last resort.
Please help, and let me know if you need any more information.
Thank you!
I understand that you're fully stock which I assume means you have a locked bootloader (everything I say from here on out assumes as such)? First, I'm going to also assume that you didn't update to 2.3.3? If not, then follow the steps in this guide to boot into a custom recovery and from there go to backup and restore and do a NANDroid backup. Now go to mounts and storage and mount USB storage (or whatever its called, don't have my phone right here). Plug your phone into your comp and copy over whatever you'd rather not lose from your SDcard (just in case you have to wipe). Now download the 2.3.3 update from here and put it on the root of your SD card. Now go back and flash this. Reboot and see if you're golden. If so, great, if not try a factory reset.
If that doesn't work go through the steps again to boot into a custom recovery, you might have to unlock your bootloader and wipe all your data (again) and restore your backup and try doing a factory reset with that. Don't worry about unlocking the bootloader, it can be relocked with a simple command and it won't wipe anything to relock it.
Here is the command just in case:
Code:
fasboot oem lock
I got all the way to having clockwork recovery booted up on the phone, but nothing would mount. Everything gave me an error, and factory reset froze...
I don't think there is anything I can even do from here, is there?
Hey folks,
I could desperately use some help here...
I rooted my Droid Incredible using UnRevoked, which was painless and easy. After that, I downloaded Rom Manager, then backed up my current Rom.
Then I downloaded Titanium, and backed up all apps and system data.
Using Rom Manager, I downloaded Cyanogen mod 7.0.2, checked google apps, DID NOT check wipe data or cache, and then clicked OK to let it work it's magic.
The system turned on and off a bit, and then the CyanogenMod boot screen came on, ran the arrow around the droidbot a few times, then the droidbot dissapeared, came back across the screen, and the arrow resumed circling. This happened about 20 times, before I gave up and powered off by removing the battery.
Then I loaded Hboot, and attempted to access items in Clockworkmod, but even though I could click on an item, it would show the top hat with no change in status for many minutes. I eventually tried almost all options.
My Hboot screen shows:
HBOOT - 0.92.0000
Radio- 2.15.00.07.28
I am unable to click on Fastboot, Recovery leads me to busted Clockwork menu, Clear Storage causes restart into looped Cyanogen Mod screen, haven't tried Simlock, and Factory Reset also goes to broken Clockwork Menu.
I downloaded the RUU file from Doug, changed the title as directed, and put it on the SD Card. It gave me the option to Update, which when restarted afterwards continued to loop in Cyanogen Mod screen. Or, if I went to Clockwork Mod screen, the font was now Green instead of Orange. Also, when I click an item in the Clockwork Mod menu, it simply goes to a black screen until I hit the power button to bring me back to the menu,
I'd love to just get the phone to a factory state, so I can possibly use it for it's purpose of calling and sexting (just kidding.)
Please help, any advice would be greatly appreciated.
Oftentimes, ClockworkMod Recovery has an error at the bottom stating:
E:Invalid command argument
I have to go to bed for a bit, but will be back on around 10:30am EST. Thanks for any and all help!
In ClockworkMod, I can now access and start an operation by selecting it with the volume buttons, and then hitting the joystick button. This wasn't working previously. So, I've tried some of the obvious options such as Factory Reset but it's not doing anything. I've tried multiple solutions, which means I've probably messed it up on many levels. Is there any way I can just start from scratch or get a system restore done?
After utilizing that update from Doug, and then going into Clockwork Mod, clearing all caches and system data, and then trying to restore to a previous flash for the 7th time... I think it might be working!
Thanks to anyone who looked at this.
so today i went to unlock and flash CM 10.1 on my tablet.
unlocking went smoothly
installing clockwork recovery went fine
installing cm10.1 and gapps went fine
once i booted into cm successfully, i checked the internal storage to see if it was clear. it wasn't, so i went to settings, backup and reset, and done a factory reset. now i'm stuck on this one screen and i dont know what it is.
i've held the power button and volume down until the tablet restarts and that results in the same thing.
i've tried power and volume up. that seems to start the tablet but the screen stays blank. i connected it to the computer and my computer installed an APX or APTX or something like that driver.
i've tried holding power, volume up and down, and that does the same as the power and volume up.
i'm very new to installing custom recoveries and roms. can anyone give me an idea on whats happened
Once you have a custom recovery installed you should NEVER wipe from the system settings or the bootloader menu. You wipe from your recovery.
If you do that, the bootloader seems to write a command to the misc partition to reboot into recovery.
And that is the loop you seem to be stuck in.
You can try _that's method to clear the misc partition from here: http://forum.xda-developers.com/showthread.php?t=2528313
Read the whole thread, salvation may be found in post 7.
If that does not work, you could try this:
http://forum.xda-developers.com/showthread.php?t=2399698
buster99's method may be another way to enable you to boot into the bootloader and flash a working recovery.
Good luck!
Thanks for the tip. I'll remember to do that next time. As of now it is fixed. I found a post on the cyanogen forum of someone who done the same thing. And he said he had to wait a painful 6+ hours of that screen I posted. Lucky for me it was only a ~45 minute wait. So all is good. Cyanogen is running. Recovery is working. All the stress is gone.
So I haven't had any luck with my Oneplus One lately . I had rooted the phone and was running the CyanogenMod nightlies for a while, but recently for some reason when I updated it for Nov. 25 I have been suck in a reboot loop where the phone boots up and it starts updating apps, but then it continuously does this cycle of rebooting and updating apps. I have tried to enter recovery mode to try and remedy the situation as I have twrp, but for some reason it doesn't boot to recovery when I press down the power and vol down buttons. I have tried to adb to try and reboot into recovery mode but I haven't been able to get it to work. I'd really appreciate some help on this as I have no idea what to do at this point.
I should also mention that I would like to see if it is possible to recover my data as I foolishly did not make a back up.
Thanks in advance.
So just an update I was finally able to get into recovery mode. I backed up my data with twrp and I tried the method mentioned in the reddit link below.
http://https://www.reddit.com/r/AndroidQuestions/comments/1ly5b1/is_it_possible_to_restore_my_sms_from_a_twrp/
I installed the newest version of nightlies CM 13.0 2015 11/30 along with gapps 6.0, but now my phone just boots up and optimizes apps but when it restarts after that it just goes to a black screen.
I know I can wipe everything through twrp and install cm 13.0 probably eliminating the issues I am having, but I'm reluctant to do so as I would like to retrieve my sms messages. I have taken my photos off my phone so I have that.
If any one can advise me on if I can restore my sms from the twrp back up I have made then I'll wipe my phone and do a clean install.
Thanks in advance
i have the exact same problem. would be nice to have it fixed and working without losing all the data.
So I decided to go ahead and wipe my system as I have all of the data I could get out of my phone on my pc now. I get get cyanogen working nicely, until I go into twrp and try to restore the data files I had backed up. This goes well until the reboot then a message pops up saying something isn't working (too fast too read). I then get a blank screen.
Now I still have the same problem of how to put the data I had saved when I used twrp back on to my phone. I believe something in my data is corrupt which is why this is happening, but I'm not sure. Is there just a way to extract say the sms from the data I have saved, that's really all I need at this point. The backups made by twrp are in a format .WIN that I have never seen before and I would appreciate the help if someone can advise me what to do from here.
CM13.0 struck in Reboot loop
When I was browsing and doing some multitasking stuff..noticed that phone was lagging a bit .So i thought to reboot so that it would come out of that...But it completely struck in reboot loop forever.
please help me out of this issue.
Thanks in advance
Novius vi said:
So just an update I was finally able to get into recovery mode. I backed up my data with twrp and I tried the method mentioned in the reddit link below.
http://https://www.reddit.com/r/AndroidQuestions/comments/1ly5b1/is_it_possible_to_restore_my_sms_from_a_twrp/
Click to expand...
Click to collapse
How did you get into recovery ?
I'm not been able to boot into recovery even while pressing vol - and power. And system is also not booting up just stuck on oneplus logo. i can enter fastboot though
vindows18 said:
How did you get into recovery ?
I'm not been able to boot into recovery even while pressing vol - and power. And system is also not booting up just stuck on oneplus logo. i can enter fastboot though
Click to expand...
Click to collapse
Are you pressing the Vol down button and power button. Also I unscrewed the back of the phone to unhook the battery cable then I pressed the buttons. I found also, through trial and error on my phone, that you can hold down the buttons for too long so you have to watch and make sure on that. I found that you should hold the 2 button combo through the oneplus one boot logo and you'll see the lights dim then you let the buttons go and its worked so far at least on my phone.
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Jvers said:
Hi, it is an older device so you might have experienced everything possible.. so,
After a long time of trying to fix that phones mind, I wiped everything avaible in TWRP
multiple times(got mad). Last thing was data.
That way I went from a bootloop to an active nothing.
Phone does not react to any command, it does not react to USB charging or on PC.
That's the case a few months back, the phone halfway in the trash and I bought
myself a iphone (hate it).
I put the Galaxy S7 on a charger today and it starts immediatly in to TWRP.
From there I tried to install a ROM that's left on the SD card, which forced
a restart into TWRP. Into download mode I managed to install the stock Oreo ROM via Odin.
It went through like a charme, all green. PASS!
The phones screen is black and does not react to any command, nothing.
I had "auto-reboot" activated.
The phone is active it's warm and I'm waiting for the battery to die again, to restart.
..meanwhile,
Can you give some advice please?
Why would the phone have struggle with the boot with stock rom installed.(which has worked before,no updates installed)
When should I install TWRP?
When do I install what kernel?
Last thing running was the LightROM with moro kernel with nothing tweaked.
Also. The issue why i deaded the phone was a camera/flash thing, where I could only take pictures with flash activated.
Front and back camera. On all camera apps, I couldnt scan my ID for banking due to that.
Also on different kernels and different ROMs including the Samsung stock.
Why would that be
Could not accept...
Click to expand...
Click to collapse
OK so what you've done is correct flashing stock (which includes stock kernal). You have to make sure the stock ROM is correct for your device and region or it will not start.
It's not unusual to have to flash it twice with Odin.
Next up you don't need to wait for batt to die to restart. Press volume down+home+power and keep them pressed until phone restarts. Should now be in download mode, reflash correct ROM with Odin. TWRP is wiped off the phone when you flash a stock ROM.
If it doesn't go through the boot up/freezes/ does nothing etc. You need to "wipe cache" then reboot from the recovery menu.
Press and hold volume down+home+power. As soon as the screen goes black move your finger to volume up (it may take more than one attempt). Once your in recovery menu use volume up and down to move through options and power to execute. Wipe cache then reboot and allow the phone to go through all the reboot stuff. It can take a few minutes just leave it alone. It will also reboot a couple of times.
If it does nothing after 15 minutes then start again and repeat the process.
Thanks for reply.
The Phone was off for a day and after charging for 1h it still does not react to any command. Vol down + home + power does nothing. Same with vol up.
Is there a way to force a boot? Even if the PC does not recognize a device on usb?
I Tried the commands 30 secs each, plugged in and off. Also usb port is not broke since the phone is getting temperature after a while charging..