So, I just flashed the latest CyanogenMod nightly. All went according to plan until the phone rebooted. Now I can't boot into anything. Neither the mod nor recovery. When I press "X" and Power to boot into recovery I just get stuck on the triangle screen and when I power up normally I get suck on the "M" logo.
I have no idea how to flash the SBF from here. Thoughts?
Same Problem!
I flashed the latest CM7 from the website. I can get to the standard recovery and to the bootloader, but have no idea how to get my phone back to a working condition. I already flashed the Droid bootstrap recovery, but can't seem to boot to it to install another ROM. Anyone help?
did you try wiping cache and data in android recovery?
edit: if that doesn't work, try
http://www.droidforums.net/forum/droid-2-global-hacks/184272-bootloop-help-tutorial.html
or the ABD boot to revovery in the FAQs
I did format the Data and Cache with the recovery tool. I ended up following the instructions at the CM7 Wiki to reinstall the factory image, now it's working OK.
I think the reason you were having trouble with the recovery was because its a different method on gingerbread. On froyo you just press the search key and it boots you into recovery, on gingerbread you have to hit both volume keys at the same time. I know this is a mute point to you know but maybe someone else has a similar issue.
no he said
I can get to the standard recovery... I did format the Data and Cache with the recovery too
Click to expand...
Click to collapse
and that didn't fix it, so he got into recovery ok
Related
Hello.
Just yesterday, I installed CM 7.1 on my Defy, which was on stock froyo. It started up normally, and was working perfectly, until I had to reboot it, in order to get the google apps, when it went into boot loop.
I've tried going into stock recovery and wiping the data/ factory reset and wiping the cache, but even then it's stuck on boot loop on the CM 7 logo. What should I do?
Ps. It's the Indian Defy, which is without Blur, if that makes any difference.
EDIT: Just got it to work, I flashed the stock Froyo SBF using RSD lite. I think my mistake was installing Clockworkmod on it, because it has it's own custom recovery. Can anyone tell me how to get into it?
Ya installing CWM on top of CM7 will screw up the pre-installed Custom recovery. While the phone is just starting to boot watch for a blue LED to flash at the top of the phone. Right when it flashes blue, press volume down. From here use your volume rocker to select recovery, use the power button to make your selection. Next choose custom recovery.
Thanks mate
Though sadly, after rebooting it, it keeps on showing the message - process com.android.phone has stopped working, and I get no network. What do I do?
Wipe data and install the zip again...
Sent from my MB525 using xda premium
First, I searched and read all relevant threads concerning this issue. The five threads that showed up in the search did not help me solve my issue.
So on to my problem. I can no longer flash any rom onto my device. I attempted to flash the first official CM10 nightly (which I recently found out was not flashing properly for others) and had no success. I simply got a black screen and nothing more. I eventually got back into TWRP (v2.2.1.4) to try and Nandroid restore, but I noticed that /data was not formatting and the restore failed. Every time I would slide the bar across to confirm the restore TWRP would reboot itself. I then flashed CWM (v6.0.1.0) and the same problems were there. After that I flashed an earlier version of TWRP and successfully restored the backup. I'm not 100% sure how it was successful. So I decided to try flashing another ROM and no go. Same problems. Anyone have any ideas? When I was using CWM I got the error message below.
Code:
E: unable to locate volume information
E: unable to open ums lunfile '/sys/devices/platform/usb_mass_storage/lun0/file'
E: unable to format data
I'm running Bugless Beast with Motley #219
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
aznxk3vi17 said:
I'm having similar, if not identical problems. After flashing TWRP 2.2.1.4, I tried flashing a rom and gapps; the tablet would boot endlessly into recovery. Nothing I did would do anything, so I flashed the stock image to start over. This time, I used CWM 6.0.1.0 touch to make sure that it wasn't the recovery that was causing the problem. However, now after flashing the rom and gapps, instead of booting into recovery, I got stuck at a black screen and had to hold the power button in order to get back to the bootloader.
Now, like you, it seems I can't flash any roms anymore. It's frustrating to say the least.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What rom did you attempt to flash?
elementur said:
What rom did you attempt to flash?
Click to expand...
Click to collapse
So do I.I attempted to flash the first official CM10 8.18 nightly and had no success. I just got a black screen.Even more I boot into bootloader and choose to boot into recover but just stay at google logo.I try to flash recover once more,but just can't boot into recover!!
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Shano56 said:
I have the same problem, i flashed the cm10 nightly which I learned would not boot. No I have no backup to boot to, and cannot even push a new rom to the storage to try to install.
Click to expand...
Click to collapse
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
phiracle said:
Can't boot into recover,does anyone know what is wrong?When it is in android I can use APM boot into recover or via ADB,but unusually when it is in the bootloader I choose to boot into recover,it just stay at google logo!!What it is going wrong?
Click to expand...
Click to collapse
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
android1234567 said:
There is a bug with the Nexus 7 where you cannot access the recovery through the bootloader. To fix this, boot up into the bootloader on your nexus 7 and, without doing anything, plug it into the computer you used for rooting it and then select the option Restart bootloader and press the power button. Once it gets you back into the bootloader again select Recovery mode and press the power button. It will now get you into the recovery and once you're in recovery you can unplug your tablet from the computer. Note that this fix is not permanent and you will have to do this every time you wish to access your recovery via the bootloader (and this problem is not relevant to the OP's problem).
Click to expand...
Click to collapse
Thank You Very Much!!!
I am having much the same problem as the OP. I finally rooted my Nexus 7 using WugFresh's Nexus Root Toolkit. It seemed all went well. I chose to use TWRP in a first attempt to install a ROM (I was on rooted stock), and following the instructions for installing my chosen ROM I went into it to wipe cache, Dalvic Cache and data. Both cache and dalvic cache wiped without issue, but when I attempted to wipe /data TWRP simply reported that it failed. With that failing, I did not attempt to install a rom. I was still able to boot out of recovery, but even with repeated attempts wiping data always failed. Is any one aware of any solution or have any suggestions. Thank you!
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.
I had Mint Jelly2.1 installed and everything was working fine.
it started when I had used the APK Hide It Pro. I was in the process of hiding videos and I noticed that my phone got rebooted and got stock in the Samsung boot up image with the Custom Lock image.
I tried nandroid restore, 2 images, but both also failed to restore / bootup.
I tried re-installing ROM and it was successful but during reboot, it will still get stock on the boot image.
Last step.
I used ODIN to restore the stock ROM and ODIN was able to install and reset. And my phone rebooted but still got stock on the Samsung Logo with CUstom Lock Screen.
What else can I do to fix this?
Thank you.
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
I had tried to restore/flash from recovery before ODIN and it all Failed.
Anyway, the last step ODIN restore and it was still stock at the Samsung Logo with Lock image.
I left the phone to charge the whole night and this morning when I turned it on, it was able to start properly with ODIN stock ROM.
I tried to go to recovery, and can only be done manually, and it was not the TWRP recovery but the stock one, with very small characters.
I tried to install Mint Jell2.1 right away but just reboots.
I realized that I might need to root it again and downloaded the Tool and re-loki'ed/rooted and installed TWRP.
Now, I am able to install Mint Jelly 2.1 and restoring all my apps.
I appreciate the comment.
Thank you.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
CZ Eddie said:
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
Click to expand...
Click to collapse
I can confirm this works happened to me yesterday.
leoj85 said:
I can confirm this works happened to me yesterday.
Click to expand...
Click to collapse
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
I got stuck to 1st boot image of Samsung with Lock Custom Icon.
I did format data/factory reset/clear cache/dalvik.. all of the wipe ootions.
I flashed a new ROM, successful, rebooted pass the logo and booted fine. I did not change any settings yet and I rebooted to check if it will get stuck again and sure after reboot, it got stuck again on the 1st image that shows up : Samsung Logo with the Lock Custom Icon.
qwer43 said:
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
Click to expand...
Click to collapse
IMPORTANTwhen using*twrp*recoverydo not choose "format data"(that option will ask you to type "yes")what if i did?rom will not boot past "padlock" boot screen orrom will not boot on second reboot*help!! I did, I did*1. sigh2. d/l odin3. d/l odin stock restore MDL4. let it do its thang5. after its complete it will be stuck at padlock6. should have "rtfm" huh?*7. pull battery8. hold home button, vol-up, power at same time9. when phone vibrates, release power, while still holdingvol-up, and home button10. you will now be in "stock recovery"11. wipe factory reset then wipe cache12. reboot*13. swear you will never "ignore instructions"
Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks
Parvarsingh said:
Hey folks I'm new here and I recently rooted my phone and flashed a z5 rom from the XDA rom thread. Link below
http://forum.xda-developers.com/len.../rom-xperia-z5-rom-lenovo-a6000-plus-t3393251
And flashed this nano pack of this gapps Link below
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
So it all went fine but now I'm incurring some problems.
Firstly I didn't notice that the Gapps is closed for updates I don't know if that affected the issue but the Google play is not working and some other Google stuff as well.
And I thought I'll flash new Gapps which are being kept up to date but my phone won't connect with the PC with the usb now so I don't know how do I flash the Gapps now.
I have re Rooted my phone using the Kingo app but it still won't reconnect.
So any help on these issues would be really helpful!
One last question that if I do find a way to flash the Gapps will I have to reflash the rom again?
Thanks
Click to expand...
Click to collapse
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!
sasukay said:
First dowload the gapps from opengapps.org. Go here choose ARM>>5.1.1>>nano/pico.
Then, boot into recovery, wipe system, data, cache, dalvik and then flash the ROM again and the gapps. All done...!!!
Click to expand...
Click to collapse
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help
Parvarsingh said:
That's the prob right. I cant reach the custom bootloader I don't know why. Do you think its because of the new rom ill have to use some different recovery? I am usin twrp right now and even I used it to flash this rom. Please help
Click to expand...
Click to collapse
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp
sasukay said:
""usin twrp right now"" -- can you boot into it..??
You press vol up + vol down along with power key and release the power key once the lenovo logo shows up, to boot into twrp
Click to expand...
Click to collapse
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
This method worked before like I used this way to flash the rom but now its not working.
Any help?
Parvarsingh said:
no cant boot into it.
I go into the fast boot mode enter recovery commands in the command window. Then try to boot into recovery but it doesn't go into recovery. The Lenovo screen stays there or it boots straight into the phone
Click to expand...
Click to collapse
Brother, you have made it really confusing for me. Earlier you said that you can't boot into bootloader, but now you can boot into fastboot..!!
Also, your phone, instead going to recovery, boots directly to system. That means your phone is in working condition(Is it..?), which you didn't told me earlier.
So, if you can boot into system (normal boot). Download Rashr from play store (or from any other source) and flash this TWRP 3.0.2. (First extract this zip and then choose recovery from storage option in Rashr to flash).