Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.
coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2
Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.
Related
Like the title says, my Nexus 5 won't boot unless I manually plug it in, hold down volume buttons and power, then wait 15 seconds for fast boot to appear, and then select "start."
Thats the problem. Now for some more information:
1. Nexus 5 32 gb
2. ROM: CM 11 Dec 13s Nightly
3. Kernel: Bricked 3.4.0
4. The phone is totally functional. The only thing wrong with it is that it can't reboot. From the system, TWRP recover, or anything, it simply will not reboot. Every time I must go into fast boot then press the power button when it says "start." After this, the phone works just as I would expect it to. I can still flash kernels and backups through recovery, it just must be restarted manually through the fast boot. This is a problem for me because I don't always want to have to plug it in when I want to reboot it.
When did it start:
Let me start off by saying that I thing the root of all my problems was the TouchControl app that allows the knock to wake function to work. I downloaded the app and was told to install the developers custom kernel. I did and not only did the app not work, it also seemed to brick my phone. I was scared, but, after doing some research, I found the method of plugging it in and holding down all buttons for about 15 seconds and my phone was saved. Ever since then there has been the problem. I must always do this to reboot my phone. Since the app didn't work I decided to install the Bricked Kernel and everything went fine except that I wasn't prompted with the interactive installer. The kernel works fine and I am now using the Knock to wake feature built into the kernel and am very happy.
Seems to be caused by swipe2wake aka knock 2 wake aka knock knock (but not totally sure)
What I've Tried (don't assume I've tried something I haven't. I could have missed something obvious.):
1. Resetting permissions through TWRP (just thought I'd try)
2. Putting back CM 11 Kernel
3. Restoring to a time when my phone did restart
Any help would be greatly appreciated. I will try to keep the original post updated with everything I try.
FIXED with the help of jd1639 and meangreenie
------------------------------------------------------------------
1.Follow jd1639's link in 3rd comment to the page and
A. Install adb and flashboot drivers
B. Install your version of factory images from google (if you are running 4.4.2 get the image for 4.4.2)
2. Plug in phone to AC CHARGER and hold down power and volume buttons for up to 20 seconds. This should put it into fast boot mode
3. After getting phone in fast boot mode, plug it into your mac or pc.
4. Out of all the instructions in the "How to flash a factory image" thread go to method 2 and ONLY DO THE FIRST TWO LINES OF CODE. All that needs to be flashed is the bootloader.img
5. After it says complete and your phone restarts you should be able to push "start" on your phone and be good!
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
jd1639 said:
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
Click to expand...
Click to collapse
So that's essentially flashing the stock ROM?
benaside said:
So that's essentially flashing the stock ROM?
Click to expand...
Click to collapse
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
benaside said:
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
Click to expand...
Click to collapse
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
jd1639 said:
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
Click to expand...
Click to collapse
I downloaded the folder for 4.4.2 from the link developers.google .com/android/nexus/images#hammerhead
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
meangreenie said:
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
Click to expand...
Click to collapse
Will this'd elite all my files and unroot?
Btw thanks so much for the help
benaside said:
Will this'd elite all my files and unroot?
Btw thanks so much for the help
Click to expand...
Click to collapse
no it won't delete your data.. but please triple check your files and fastboot commands before executing
the last resort is to format data if all else fails
Thank you both so much. I have (with both of your help fixed it). I will post how in the original post. Thanks again.
Hello
I followed this guide http://forum.xda-developers.com/show....php?t=2507905 to root my new Nexus 5 and flashed this rom http://forum.xda-developers.com/show....php?t=2528265 onto it, when I tried to boot it up it got stuck in the boot animation so I rebooted into recovery and wiped the data, cache partition and the dalvik cache and tried to boot it up and encountered the same problem so I went to reboot and it wont boot back up not even to the bootloader and when I plug it into my pc its unrecognized and wont even show charging animations
Did I brick my new phone?
Smragnol said:
Hello
I followed this guide http://forum.xda-developers.com/show....php?t=2507905 to root my new Nexus 5 and flashed this rom http://forum.xda-developers.com/show....php?t=2528265 onto it, when I tried to boot it up it got stuck in the boot animation so I rebooted into recovery and wiped the data, cache partition and the dalvik cache and tried to boot it up and encountered the same problem so I went to reboot and it wont boot back up not even to the bootloader and when I plug it into my pc its unrecognized and wont even show charging animations
Did I brick my new phone?
Click to expand...
Click to collapse
Press and hold volume up then connect usb cable, what the result?
bitdomo said:
Press and hold volume up then connect usb cable, what the result?
Click to expand...
Click to collapse
same as above, nothin.
Smragnol said:
same as above, nothin.
Click to expand...
Click to collapse
Then it is bricked , but I don't really understand how could fromating data, cache and dalvik cache destroy the bootloader . There must be something wrong those recoveries, because you are not the only one
Did you ever check the md5 of the rom you flashed? It could have been a corrupted download
does your bootloader work? hold the vol up/down and power on boot. if u can get to the bootloader u can save it with wugs nexus tool.
malibu_23 said:
does your bootloader work? hold the vol up/down and power on boot. if u can get to the bootloader u can save it with wugs nexus tool.
Click to expand...
Click to collapse
If you can get into bootloader you can save it without a tool kit.
Do this if u can't go into recovery
http://forum.xda-developers.com/showthread.php?t=2513937
But if u are able to go into recover, just flash any other rom, make sure you before flashing u do a factory data reset, and after finished wipe cache/dalvik always so u dont go into bootloops.
Through some miracle I was able to get to the bootloader (sat there and held the vol and power buttons for like 3 minutes while my pc dinged and donged as it disconnected and reconnected) but I'm unsure of what to do now. Should I keep trying to load a custom rom on it or just go back to stock? and either or how am I going to get the rom on the internal storage as its still not being recognized by my pc (but I do have fast boot access)
Smragnol said:
Through some miracle I was able to get to the bootloader (sat there and held the vol and power buttons for like 3 minutes while my pc dinged and donged as it disconnected and reconnected) but I'm unsure of what to do now. Should I keep trying to load a custom rom on it or just go back to stock? and either or how am I going to get the rom on the internal storage as its still not being recognized by my pc (but I do have fast boot access)
Click to expand...
Click to collapse
I'd flash the factor image with fastboot and start all over
Do this if u can't go into recovery
http://forum.xda-developers.com/showthread.php?t=2513937
But if u are able to go into recover, just flash any other rom, make sure you before flashing u do a factory data reset, and after finished wipe cache/dalvik always so u dont go into bootloops.
Stay away from tool kits. You got enough problems on your hand
Alright so I got the stock os flashed on there and booted up and everything is looking goood, thanks guys for all your help I'll be sure to come back if I have any more problems
Smragnol said:
Alright so I got the stock os flashed on there and booted up and everything is looking goood, thanks guys for all your help I'll be sure to come back if I have any more problems
Click to expand...
Click to collapse
Glad to hear you're back up and running. Google md5 checksum and make sure the roms you download are good. I think that was your problem
Done this to my Nexus 7.. something went wrong when flashing the Rom and ended up somehow cocking up my drivers aswell.. Weird one.
Glad to hear your back up and running buddy.
So guys, i've done it. I bring my first device.
Yesterday i tried to downgrade via fastboot with this recovery images https://developer.nvidia.com/gameworksdownload (yes is choose the right ones)
flash boot, check
flash recovery, check
flash system, failes (insufficient memory)
erase sytem, check
flash system, failed (insufficient memory)
flash twrp, check, but no usb mouse so
flash cwm, check
factory reset, check
rom.zip and gapps on sd card, check
reboot, boot into bootloader, no chance
It boots everytime normal, so i cant enter the recovery.
Connect it to charger, check
charging led lights up, check
Go sleeping, check
doenst boot into bootloader :/
Back to charger
Now I wanted to try it again and i wont even boot.
Anyone has an Idea? Or is it really bricked?
Can you still see the device listed using fast boot?
No, because I can't enter the bootloader or the recovery. But it boots again
...
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
rafaelvelasquez2 said:
The same thing just happened to me. Unfortunately, I am still trying to figure it out. I flashed a "stock" recovery that I had found in order to be able to take the OTAs. Now when I boot, I just stay stuck on the NVIDIA splash screen.....been there for hours.
Click to expand...
Click to collapse
Same here.....
Mine is working again. Booting in the bootloader is a little bit tricky.
Have you tried to flash all? Boot.img, recovery.img and system.img?
...
I had the same issue. But after trying to get into the bootloader using POWER + VOLUME DOWN for about 15 minutes it finally went to the bootloader and I was able to re-flash it. I have a feeling it's the cludgy power button.
You do not need to flash the stock recovery to take the ota. I have taken 2 otas now on custom recovery without any issue and without loosing root. Just an FYI.
Sent from my SHIELD Tablet using XDA Free mobile app
I just did a factory reset under lollipop, locked boot-loader rooted and it rebooted to the green android screen then dropped into CWM and asked to fix root. I said no, then it went to the nvidia boot logo and it is stuck. Any suggestions? Thanks.
Edit: nevermind, I just powered it off after about 20 minuets and it hung again. When I plugged it into my pc, it finally poped into the setup/welcome screen. Pretty weird. Heart attack averted
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.
Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.
success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!
stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.
jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good:
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Fireflynj said:
Hello,
I am getting myself deeper into trouble working on this.
First I will explain what I did, I wanted marshmallow and read TWRP needs to be updated to load it and also that that I cannot restore from older backup, so I figured I update TWRP first then do a backup.
I did the TWRP update via app, verified the partition and when done and rebooted to recovery, TWRP was still v2.7 and the phone won't boot, the OS was gone.
so then I figured I flash Dottat M8firmwareandRecovery to get the new TWRP and backed up the Data partition.
then found out that I can't use that Data partition with a different OS. So I figured I flash KitKat back on.
did that, now I can not get back into recovery, holding the Vol down with power will not go to HBOOT.
now KitKat loads, had root, but the dang thing auto updated to 4.4.3 and now lost root. I thought it can't auto update with s-off
so it as asking for another update now and I turned it off. Waiting for someone to help , I keep making it worse.
my phone was unlocked and s-off, I hope it still is, can anything undo that?
Please help
Click to expand...
Click to collapse
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
andybones said:
I've personally never seen a device go back to S-ON without the user doing it with the cmd.
That isn't to say it's never happened before.
I'd assume you are still S-OFF.
What happens when you flash a ROM that has a power menu and you select to reboot to recovery or bootloader?
Or you can root and download an app that works the same way. curious what it does.
Also how long are you holding the buttons?
If everything else is working you should be able to get to hboot/recovery - but I honestly don't know.
My suggestion?
Get a more recent RUU .exe and run it on your PC and see what happens.
here is the link
https://www.androidfilehost.com/?fid=24052804347812372
Click to expand...
Click to collapse
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
Download the .exe and click open. Follow directions on the screen. It doesn't get easier, trust me you'll be fine. Wouldn't steer you wrong.
Fireflynj said:
I would, but I don't know how to flash without the HBOOT, I got some research to do to learn how to do it from the PC.
Click to expand...
Click to collapse
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
dottat said:
The only time I've seen a phone be a pita when trying to enter boot loader is when it's connected to USB.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Fireflynj said:
My Galaxy Tab2 did that. I tried the M8 again today with USB unplugged, did not get boot loader menu, but then while it was on, I did a Vol up and power (forced shutdown) then while still holding the power button switched to Vol down right when the screen blanked, then I got the boot loader! :victory:
Click to expand...
Click to collapse
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
dottat said:
and to correct myself.. one other condition. The older version of software included a "fastboot" option in settings->power that was more like a hibernate feature. That feature when enabled would prevent you from getting into bootloader.
Click to expand...
Click to collapse
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Fireflynj said:
That makes sense, 'fastboot' was on, its now off.
The bootloader works, KitKat OS is working, but not recovery. I get 'Entering Recovery . . .' on white htc screen and stuck there.
I used adb command prompt to flash recovery with fastboot then I tried HTC_fastboot and different versions of TWRP.
tried flashing with Flashify , no errors, it just doesn't load. I think something else is broke.
dottat, do you have an image of RUU rooted Kitkat with TWRP?
Thank you for the help.
Click to expand...
Click to collapse
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Your firmware is too old. That's why the newer recovery won't work. Do you want to update everything first and then RE-root?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yup , that was it, the older one worked.
So dumped the idea of getting KitKat back and I flashed the Marshmallow custom s-off RUU with TWRP that you provided. so far good now I just need to re-root it.
Thank you