Hello guys,
I tried rooting my phone using the tutorial that is on this site.
then I flashed TWRP on it, the official version by beroid.
this went well and I tried to install crdroid and gapps for this I had to wipe the system, data and cache
after this android wouldn't boot up and now it is stuck in TWRP when I press reboot system.
fastboot doesn't work and I can only see the boot partition in twrp when flashing an image.
I really hope you guys can help me since I'm not really that advanced in rooting devices and this is my first go on it
I see this is marked as solved - is that correct? If so, could you post how you fixed the problem, as I think it's affecting me too. (My issue below.)
Does anyone have any advice on what to do here? I tried to update from:
lineage-14.1-20170320-nightly-crackling-signed.zip
(which was working fine) to:
lineage-14.1-20170328-nightly-crackling-signed.zip
When the updater rebooted into TWRP, it couldn't find the download, and I didn't know where it was either, so I just rebooted, and ended up back in TWRP!
TWRP has 4 reboot options, System, Power Off, Recovery, and Bootloader.
System - goes to TWRP again
Power Off - goes to Wileyfox logo, which stays on the screen forever
Recovery - goes to TWRP (as it should)
Bootloader - goes to fastboot mode
Nothing actually boots into LineageOS.
I tried flashing the previous nightly and the current one direct from the removable SD card, but same results.
TWRP appears to be able to flash anything I want, also fastboot is working when I connect it to my computer, so I assume the bootloader is somehow being prevented from loading LineageOS? Or I've somehow wiped the bootloader? (/boot is empty - is that correct?)
I'm now clueless as to what to do, so any help would be much appreciated.
---------- Post added at 12:15 PM ---------- Previous post was at 12:08 PM ----------
Just made some progress in the last few minutes, using the command:
Code:
fastboot reboot continue
gets it to the LineageOS boot animation.
Now waiting for a hopefully successful boot... :fingers-crossed:
edit: this worked, but I'm not sure I want to risk actually rebooting now
I have this exact same issue.
Related
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
After installing TWRP 2.6.3.2 (latest atm) I tried to flash the ROM CMB rc2 on my G pad. I am unable to post in that topic because of my low post count.
Everything went fine, though during the boot it just never stopped showing the boot screen/CMB logo (I am aware that the first time it is used to take a while). The thing I might have done wrong is before the new flash, is to erase everything at first. I didn't do that =(.
I am now unable to reach in through ADB. It just doesn't find the device. Any other way of booting in to recovery is unknown to me. I tried several times rebooting with a variety of button-combinations, but it just continues to the boot screen/logo. I dont even know if there even IS an button combination to boot into recovery.
Sadly when force-shutdown (holding the power button) it doesn't shut down. It restarts. I am now unable to shutdown my own tablet.
Help would be much appreciated. Thanks in advance!
Any additional info:
I have not flashed gApps right after, or any thing else for that matter.
I have installed TWRP from 2.6.3.0 => 2.6.3.1 => 2.6.3.2 in just about 3 minutes after each other. I was mistaken in the files, picked the #.1 in stead of the #.2 directly.
If there is any information I could provide extra that would help sort this out I would gladly do so.
jhjoosten said:
After installing TWRP 2.6.3.2 (latest atm) I tried to flash the ROM CMB rc2 on my G pad. I am unable to post in that topic because of my low post count.
Everything went fine, though during the boot it just never stopped showing the boot screen/CMB logo (I am aware that the first time it is used to take a while). The thing I might have done wrong is before the new flash, is to erase everything at first. I didn't do that =(.
I am now unable to reach in through ADB. It just doesn't find the device. Any other way of booting in to recovery is unknown to me. I tried several times rebooting with a variety of button-combinations, but it just continues to the boot screen/logo.
Sadly when force-shutdown (holding the power button) it doesn't shut down. It restarts. I am now unable to shutdown my own tablet.
Help would be much appreciated. Thanks in advance!
Any additional info:
I have not flashed gApps right after, or any thing else for that matter.
I have installed TWRP from 2.6.3.0 => 2.6.3.1 => 2.6.3.2 in just about 3 minutes after each other. I was mistaken in the files, picked the #.1 in stead of the #.2 directly.
If there is any information I could provide extra that would help sort this out I would gladly do so.
Click to expand...
Click to collapse
Your best bet would be to restore the factory firmware and start over. To do this, follow the instruction in this thread. The only change is that to enter Download Mode on the G Pad, you hold volume up and volume down while inserting the USB cable rather than just volume up.
Hi,
I had rooted my device with TWRP Recovery installed. I then updated my Cyanogen 12 version from cm-12-20150430-NIGHTLY to cm-12-20150502-NIGHTLY. Post that, I did a factory reset from CM12. Since then, my phone has been stuck in a constant TWRP Loop where the TWRP logo keeps flashing every few seconds. Unable to access the recovery. The phone buttons do not power off or restart the phone. However, I can access fastboot if i let the battery run out and then start the phone. Please help me.
AnirudhS89 said:
Hi,
I had rooted my device with TWRP Recovery installed. I then updated my Cyanogen 12 version from cm-12-20150430-NIGHTLY to cm-12-20150502-NIGHTLY. Post that, I did a factory reset from CM12. Since then, my phone has been stuck in a constant TWRP Loop where the TWRP logo keeps flashing every few seconds. Unable to access the recovery. The phone buttons do not power off or restart the phone. However, I can access fastboot if i let the battery run out and then start the phone. Please help me.
Click to expand...
Click to collapse
Got it done guys. Reinstalled twrp using fastboot. This stopped the loop.
Thanks !!
Hello,
after experiencing some problems with crashing Galery-app on Stock ROM Android 6.0.1 I decided to do a factory reset.
After factory reset, I got constant android.process.acore and HTC Sense crashed and could not use ANY app nor even see my starting-screen.
I managed to get into the settings and enable USB Debugging. But most of the time, my device did not boot up properly and just showing the HTC-bootscreen. When I pressed volume-up + Power I could reset the phone but was not able to manually power on again. Aso Volume-Down+ Power (To access recovery mode) did not worked anymore.
After getting on low batterie my device turned off and then I was able to access recovery mode again.
I started installing CWM Recovery (Philz touch) which ran fine.
After some unsuccessfull factory resets (same problem as above) I decided to install a custom rom. I choose cm-13.0-20160329-NIGHTLY-m8.zip (Android 6)
The installation process ran fine and I was able to boot normally. Only thing that was wierd: The phone did not recognize my sim-card and I was not able to play any sound. So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop). Naturally, there was the animated CM-Bootlogo showing and not the stock HTC Boot screen.
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power, instead I have to wait till my phone powers up on its own (Which will lead to a bootloop again)
Is there any way to get the device working again?
Thank you!
EDIT: Also it is running really hot while in bootloop.
EDIT2: my battery ran out of energy and I managed to get into recovery mode again. installing latest nightly (20160330) now
EDIT3: "Setup Assistent" crashes while startup. Can't get into recoverymode either. dont know why. phone just starts up normally...
Vendaar said:
Hello,
after experiencing some problems with crashing Galery-app on Stock ROM Android 6.0.1 I decided to do a factory reset.
After factory reset, I got constant android.process.acore and HTC Sense crashed and could not use ANY app nor even see my starting-screen.
I managed to get into the settings and enable USB Debugging. But most of the time, my device did not boot up properly and just showing the HTC-bootscreen. When I pressed volume-up + Power I could reset the phone but was not able to manually power on again. Aso Volume-Down+ Power (To access recovery mode) did not worked anymore.
After getting on low batterie my device turned off and then I was able to access recovery mode again.
I started installing CWM Recovery (Philz touch) which ran fine.
After some unsuccessfull factory resets (same problem as above) I decided to install a custom rom. I choose cm-13.0-20160329-NIGHTLY-m8.zip (Android 6)
The installation process ran fine and I was able to boot normally. Only thing that was wierd: The phone did not recognize my sim-card and I was not able to play any sound. So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop). Naturally, there was the animated CM-Bootlogo showing and not the stock HTC Boot screen.
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power, instead I have to wait till my phone powers up on its own (Which will lead to a bootloop again)
Is there any way to get the device working again?
Thank you!
EDIT: Also it is running really hot while in bootloop.
EDIT2: my battery ran out of energy and I managed to get into recovery mode again. installing latest nightly (20160330) now
EDIT3: "Setup Assistent" crashes while startup. Can't get into recoverymode either. dont know why. phone just starts up normally...
Click to expand...
Click to collapse
Yout could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Vendaar said:
EDIT: Also it is running really hot while in bootloop.
Click to expand...
Click to collapse
That's going to happen. The CPU is working hard during boot, and if its caught in a bootloop, the CPU is getting constantly worked, and heat is the inevitable result.
---------- Post added at 09:38 AM ---------- Previous post was at 09:34 AM ----------
Vendaar said:
When I power off via VolumeUp+Power I am NOT able to get into recovery menu via VolumeDown+Power,
Click to expand...
Click to collapse
Is the phone powering off with Power+vol up; or is it rebooting? It should be rebooting. If its rebooting, the moment the screen goes dark, and before any boot splash screen shows; hold only vol down to access bootloader (don't let go of vol down until you see bootloader).
Failure to get into bootloader this way is usually user error (often the result of not pressing vol down soon enough, or letting go of it too early)
---------- Post added at 09:40 AM ---------- Previous post was at 09:38 AM ----------
jkolner said:
Yout could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Click to expand...
Click to collapse
I agree to try TWRP. Philz hasn't been updated in a very long time, and is known to cause some issues due to that.
---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------
Vendaar said:
So i dediced to install the latest stable release which was cm-12.1-20151117-SNAPSHOT-YOG7DAO1K1-m8 (Android 5.1)
After installing via adb and rebooting, I had the same problem as mentioned above (bootloop).
Click to expand...
Click to collapse
Are you doing full wipe (data, Dalvik, cache) when installing new ROMs? This is recommended, and failure to do so will often lead to boot problems on the ROM.
Also, are you installing gapps (Google apps) with the CM ROMs? Failure to do so will also lead to boot issues, or setup assistant crashing (and a lot of other errors during startup). And the CM ROMs can be finicky with some gapps packages.
Thanks for your replies!
redpoint73 said:
Failure to get into bootloader this way is usually user error (often the result of not pressing vol down soon enough, or letting go of it too early)
Click to expand...
Click to collapse
I pressed both about 10+ seconds. Guess it was my error then.
redpoint73 said:
Are you doing full wipe (data, Dalvik, cache) when installing new ROMs? This is recommended, and failure to do so will often lead to boot problems on the ROM.
Click to expand...
Click to collapse
I did not do a full wipe then . Thought deleting cache will also delete dalvik cache. I did only delete data+cache
redpoint73 said:
Also, are you installing gapps (Google apps) with the CM ROMs? .
Click to expand...
Click to collapse
Yes, I booted to recovery, and used sideload to first push CM and afterwards gapps to the phone.
jkolner said:
Your could try and install TWRP 3.0 and do a factory reset or flas a new Sense Rom.
Click to expand...
Click to collapse
Okay. I will now install TWRP 3.0, do a full reset (data, dalvik, cache) and flash the latest CM. Thank you very much!
Android is now booting well. Thank you
Next problem i'm running into: can't play any audiofile. Ringtones dont work either. My phone isn't doing any beep. videos do not work and Gallery-app is crashing instantly. Also my equalizer AudioFX.
Errors, I get are:
Music-App
[CRASH] com.cyanogenmod.eleven threw java.lang.IllegalStateException
Gallery crash:
[CRASH] com.android.gallery3d threw java.lang.RuntimeException
Audiofx:
[CRASH] org.cyanogenmod.audiofx threw java.lang.IndexOutOfBoundsException
I researched some time but did not found anything useful here
EDIT: New problem:: SIM is not recognized by phone anymore. It worked on first boot..
Edit2: cant even hear sound over headphones.
updated to latest nightly. Did not resolve anything.
Bump.
Updated to latest nightly and cleared cache + dalvik before. didn't solve my problem either
Bump
Sent from my m8 using XDA-Developers mobile app
I was already using a custom rom and I wanted to update my Twrp from 2.8 to 3.0. So I booted to twrp, then I flashed twrp 3.0 using the Install menu and selecting the proper twrp image. But in the flash screen I ticked the boot partition and flashed. Immediately my phone turned off and now I can't enter recovery and my phone is on a bootloop without any system it seems (even though I actually have cyanogen 13 installed). The only thing it does is show the Asus logo and then reboot. I can't boot the bootloader or recovery.
I don't know what to do. It's the first time I actually brick a phone =/
Any help will be great!Thanks
EDIT: well... I installed intelSOC, connected my phone to my PC and after some bootloops it suddenly booted to twrp (I didnt do anything) , then I reinstalled my rom and it seems everything is normal now.
After many tries my TWRP wouldnt get past the blue logo screen. Then I decided to follow this tutorial http://techtrickz.com/how-to/unbrick-a-bricked-zenfone-2-ze550mlze551ml-restore-bootloader/
After doing every step, my ASUS LOGO is gone, replaced by something it seems a Flag with pink, yellow and purple horizontal lines, and nothing else. The phone boots, shows this flag and there is nothing else I can do.
Ideas?
Turns out I followed an incomplete tutorial. If you have the same issue as I did, just follow this one: http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
just follow my thread and you will be success in one try!
https://forum.xda-developers.com/showthread.php?t=3828667
---------- Post added at 09:46 AM ---------- Previous post was at 09:46 AM ----------
just follow my thread and you will be success in one try!
https://forum.xda-developers.com/showthread.php?t=3828667