please help
You might have destroyed the boot img. See if you can reboot to stock recovery or not.
i have reflashed miui 11 rom but now a problem is when i install custom rom it make l
Azamsm said:
You might have destroyed the boot img. See if you can reboot to stock recovery or not.
Click to expand...
Click to collapse
i have reflashed miui 11 rom but now a problem is when i install custom rom it get stucked on boot screen
haider123 said:
i have reflashed miui 11 rom but now a problem is when i install custom rom it get stucked on boot screen
Click to expand...
Click to collapse
Looks like you have encryption issue. Try to FORMAT data partition then flash the rom again.
Related
After rooting my N7 a few weeks back, I have tried flashing at least 3 different grouper custom roms through TWRP 2.4.2.
After flashing the rom, when I reboot from TWRP, the N7 gets stuck on bootscreen logo of the respective rom. I have to use Nexus Toolkit 1.6.3 to reboot into TWRP and restore from nanroid backup of stock rom, and everything works fine.
Why are Custom ROMs not being able to boot past the bootscreen logo?
I would appreciate help.
Thanks in advance.
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Nico_60 said:
You should give us more info... What's your device, which rom you want to try, what steps did you do to flash the rom in recovery?
Click to expand...
Click to collapse
Nexus 7, I have tried flashing simbean 4.2.2, latest XenonHD and another which i have forgotten the name (all latest grouper versions).
I downloaded ROMs on my PC from XDA.
Copied zip file into nexus 7 via USB cable.
Rebooted into TWRP 2.4.2.0
Wipe System/ cache/ dalvic cache
flashed Rom (indicated flash was successful)
Rebooted from TWRP
bootloop (getting stuck at the bootanimation of the custom rom)
Used Nexus Toolkit 3.6.1 to reboot into TWRP
Restored my stock rom from backup.
Stock Rom working fine.
Ive tried flashing faux kernel and an aroma installer for boot animation change, which has worked fine both times.
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Maybe try flashing with a more recent version of TWRP, 2.4.4.0
http://forum.xda-developers.com/showthread.php?t=1779092
http://www.teamw.in/project/twrp2/103
--------
Fastboot flash the latest recovery image from here...
http://techerrata.com/browse/twrp2/grouper
...and then try again, flashing your preferred ROM in recovery.
--------
Don't know if it will work... but it's got to be worth a shot.
What is odd, is you seem to have no problem NANDROID restoring back to stock...
Anyway, hope you get it sorted.
Rgrds,
Ged.
Nico_60 said:
When you are in recovery, first go in wipe menu and do a factory reset, wipe system (optional), install the ROM and reboot and all should be fine.
Click to expand...
Click to collapse
thanks , problem solved
fslnwz101 said:
thanks , problem solved
Click to expand...
Click to collapse
I am using CM12 nightlies on my N900W8, and I haven't had any problems until I tried to flash a new nightly (while running 20150410-NIGHTLY-hltetmo) and instead of booting into recovery I got a black screen. After taking the battery out and back in and trying again, the same thing happened. When I started it back up again the internal memory was completely wiped, I have no idea how or why. It can boot into download mode but I cannot get into recovery and therefore can't flash a new ROM or recovery to fix it. What do I do?
Download mode flash stock rom through Odin .
pieguy213 said:
I am using CM12 nightlies on my N900W8, and I haven't had any problems until I tried to flash a new nightly (while running 20150410-NIGHTLY-hltetmo) and instead of booting into recovery I got a black screen. After taking the battery out and back in and trying again, the same thing happened. When I started it back up again the internal memory was completely wiped, I have no idea how or why. It can boot into download mode but I cannot get into recovery and therefore can't flash a new ROM or recovery to fix it. What do I do?
Click to expand...
Click to collapse
Flash egain witch recovery you prefer with Odin.
JJEgan said:
Download mode flash stock rom through Odin .
Click to expand...
Click to collapse
You sure downgrading won't cause any problems?
jemis1983 said:
Flash egain witch recovery you prefer with Odin.
Click to expand...
Click to collapse
Didn't work. I tried CWM and TWRP, both resulted in a black screen when booting in recovery mode.
I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated
I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.
Is there a workaround to this other than flashing factory images...?
hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos
I flashed CM ROM today to try and see what progress has been made. I decided to return to the stock ROM. Flashed the stock ROM and wiped everything except system partition. Rebooted the phone and it is resetting itself at the first logo now. The second stage of boot (animated logo) doesn't initiate.
Download and Recovery modes work. Flashing the stock firmware with both Odin and Smart Switch didn't fix the problem. I tried PIT file and NAND Erase with a no go. Any help would be appreciated.
Edit: After spending some time trying, I realized I can only boot CM. Maybe CM caused this problem or the Gapps package I have been using. I am not sure. I'll be happy if anyone can help me fix this problem.
just flash cm12.1 (clean install without gapps ) do not let device boot just flash and then flash any rom you like it (dirty flash )
sorry for bad english
osamaAlrogi said:
just flash cm12.1 (clean install without gapps ) do not let device boot just flash and then flash any rom you like it (dirty flash )
sorry for bad english
Click to expand...
Click to collapse
this doesnt work mate
I am currently using MIUI 8 and i hate it.
I want to go back to Resurrection Rom. But the problem is when installing, i think i used wrong command and flashed the boot image (fastboot flash boot).
Now if i install any ROM other than MIUI 8, it does not work. Goes into bootloop. I can boot into TWRP recovery using fastboot. But after successfully flashing my Resurrection Rom, the phone starts, MI logo appears and it reboots again after a screen flicker.
Please advise on how i can install Resurrection Rom again. Also i can only boot into recovery using TWRP 3.0.0, any other recovery like Stock, Philz (CWM) are not working. I can only boot into recovery using fastboot boot twrp3.0.0.img command.
Thanks
kishorer747 said:
I am currently using MIUI 8 and i hate it.
I want to go back to Resurrection Rom. But the problem is when installing, i think i used wrong command and flashed the boot image (fastboot flash boot).
Now if i install any ROM other than MIUI 8, it does not work. Goes into bootloop. I can boot into TWRP recovery using fastboot. But after successfully flashing my Resurrection Rom, the phone starts, MI logo appears and it reboots again after a screen flicker.
Please advise on how i can install Resurrection Rom again
Thanks
Click to expand...
Click to collapse
try to install with t.w.r.p 3.0.2.0
i-AM-BoReD said:
try to install with t.w.r.p 3.0.2.0
Click to expand...
Click to collapse
I edited the question. I can only boot into twrp 3.0.0, all other versions, other recoveries are not working.
kishorer747 said:
I edited the question. I can only boot into twrp 3.0.0, all other versions, other recoveries are not working.
Click to expand...
Click to collapse
If fastboot method is not working for 3.0.2.0 version then ,Just try to flash t.w.r.p 3.0.2.0.img (download from here)by flashify or rashr app.Then reboot in to recovery and flash any custom rom.
u can also flash recovery image file by your existing recovery.
And why using only fast boot command?U can boot to recovery by updater app or button combo.