Just a quick question about the boot-up time after the flashing of Gobstopper.
Atrix is rooted, unlocked, tenfars CWM on a stock 2.2.2
Used Rom manager to flash update.zip (after format data/cache/dalvik) and i didn't see any errors and it looked as though it went through. It has been on the boot animation for about ten minutes now.
50% Battery when I started
How long should this first boot take?
if it's looping.. Battery pull -> restore back-up through recovery?
Thanks
**UPDATE: White LED flashing?? Is the battery almost dead now?**
**Update: Booted finally after about a half hour but the digitizer is reversed.
Another update: shutdown -> battery pull -> turned it on.. waited 10 minutes on the boot animation -> F%^& It! -> restoring backup through recovery
Backup restored but the digitizer is still reversed(mirrored)... wtf?.. saw a post about this some where before.. I'll try to find it again
Thanks: http://forum.xda-developers.com/showthread.php?t=1182782&highlight=touch+screen+reversed
Update: on trying to get the fix working for the touch screen I ran into ADB returning "offline" for my phone.
Tried this post: http://forum.xda-developers.com/showthread.php?t=974824
but still getting offline device from ADB... frustrated much? I think so!
Update::
After a bunch of reboots, i tried booting into recovery to try another backup. It didn't start the recovery but went fully into the home screen. Touchscreen now works and I can connect with ADB. I have no idea why it started working. Can anyone shed some light on it?
Well, first of all, there was a fix for reversed touch screen on here somewhere.
Basically, you had to do "Fix Permissions" in CWM as far as I remember.
Second, seems like you had the reversed touchscreen problem because you flashed across different version of Android (2.2.2 <=> 2.3.4). At least that's when I had this problem.
To avoid this you either have to flash via fastboot and do a full wipe. Or do the "fix permissions" thing and also do a full wipe.
Well I thought it fixed itself.. I lost connectivity though and restarted. Once loaded the touch screen was reversed again.
I going to carry on with those fixes I have linked in the OP and hopefully that will fix it permanently.
Update: reinstalled cwm recovery -> boot to recovery -> wipe data/factory reset -> restore backup -> Booted up fast without a problem...
I'll try the 2.3.4 again using the fastboot method later
Related
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!
My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...
Hello,
I own an Android tablet KO PARA1 FULL and experiencing a strange problem. This is a chinese atm7029 quadcore tablet (16gb, 1gb ram, without bluetooth, only wifi, bu supports 3g dongle), running android 4.1.1 nad 3.4.0+ kernel, which came prerooted. After some time I've decided to install backup programs on in to make a full backup of the device for the case something would go wrong, and after some trying I descovered, that there is something like recovery for that purposes which seemed a good solution for me. I decided to install CWM, which I managed to install without problems and made some backups on my device. Everything was fine, I did some factory resets through the time, some restoring processes from my previously backup states of the device, was always able to activate CWM recovery menu through Reboot to recovery or through combination of Volume down a Power button...
Until last saturday. I was normaly surfing the internet, reading mails and afterwords I powered my tablet off (it is draining battery in sleep mode, but its another story..). After a while wanted again to write a mail, so I powered it on. In that momet seemed the screen too dirty for me and I tried to cleen it little bit throug the bootup process. Unfortunately I obvious confused the system with it and after boot it was not responding properly. I did not wait enough and after a while powered it off with power key pressed for a long time, to make a new boot.
But when I powered it on again, it stayed stuck in boot logo and did not boot at all. I've tried a copple of times to boot it again with no cuccess, stayed stuck in boot logo for more then 10 min...
Afterwards I decided to make it boot up with the help of computer. I downloaded adb and drivers and somehow managed to make it boot up. I thing I was too excited to see it boot up again, that during boot up process I desconected my device from computer...
My worries were reliesed and I thought it would be a good idea to make a restore from backup to prevent some strange behaviour, so wanted to boot into recovery, but nothing had happened. After some repeated clicks on Boot into recovery button, as well as app called rebooter with nothing happening, I decided to try it out through button combination. It has not worked as well Next try was to reset to factory settings. But when I go through the menu, I can click on reset to factory settings button, seeing warning that I will lost ma data, then I can push the button to make it happen, but nothing is happening. I see only the screen with the button, can touch it 100 times and the tablet stays on, fully funcional. making no factory reset as it done before.
I did a lot of reading and searching, but have not find answer for my problem. I flashed recovery images from my backups (using flashify, flash gordon, adb shell, terminal emulator), from all previously functional states of the device. I refleshed the CWM recovery downloaded from the internet for my chipset, which previously did the job just perfect, with no success...
I am still not able to reach recovery menu. For me it seems like the bootloader would be locked, but I did not find the answer how to unlock it without to be able to start in some recovery state to use fastboot command to unlock it.
Otherwise, my device is functional, still rooted, i can use it without any other problems. But not be able to do recovery from my backups, even do a factory reset.
How can I restore my access to recovery mode? Is it somehow possible?
Hopfully it is not too much information (tryied to follow the intructions and wrote everything I thought would be important to know about) and you will not be bothered to read all my story and pull me out of my darkness with helpfull suggestion.
Thanks a lot in advance
Steve
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys
Ok, so something seems to have gone very wrong with flashing my phone :S
I managed to get recovery working yesterday, and followed the steps in this thread, http://forum.xda-developers.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155 , to create a pre-rooted 5.0.2 image. I put it on the external SD card, booted into recovery and installed the flashable zip, then used flashtool to flash with the instructions (though I also cleared Appslog, Cache and Data to get a fresh install). This went fine and everything appeared to be ok. I then tried to get the Xposed Alpha installed, but after that whenever the phone was rebooting it just hung if trying to boot to Android. I tried re-flashing with Flashtool, but still got the same issue. Would boot fine the first time, but then any restart it would just hang and crash out. Tried clearing the cache from recovery, but no difference.
So today, I went into recovery, re-installed the flashable.zip, then powered off the phone and flashed using flashtool, just as I had yesterday. Now though, my phone wont boot. It shows the Sony logo, then a blank screen, then restarts. Even worse, it will no longer boot into recovery. I hold the volume down button when the LED shows, nothing. I try holding the volume down button all the way through several bootloops, nothing.
I've tried to re-flash using flashtool which goes through the process ok, I can hold the volume down button and connect the cable once its in the process of rebooting, and it goes through all the process fine. It then powers off as expected and I can just disconnect and power on the phone. But it's still stuck in the bootloop and I don't have TWRP recovery.
Is there anything I can do to get my Z2 working?
Update - Re ran flashtool, this time not excluding system, only Partition. It now gets a little further, going to "Powered by Android" and giving the purple wavy lines, but after a minute or so it just hangs and restarts again. And still no recovery sadly....
I think I've got it sorted...
Used Flashboot again to do a flash, excluding System and Partition. This time the phone does boot up normally. The downside being that my root was gone. Despite my flashing a pre-rooted image, it seemed to just put a stock image on. And my recovery is still mysteriously gone.
In the end, just to get things completely back to a stable/stock starting point for later on, I ran a repair from PC Companion. Seems I was in the none rooted position anyway so figured I'd get myself to a more certain position. At least this way I can wait for someone to come up with a root for 5.0.2 so I can root and get recovery back.