So i manage to remover the boot failure on from fastboot mode since it has been there everytime it boots up and it didnt boot up fully but after using droid utility to downgrade to 4.1.2 it no more goes to fastboot but now its stuck on a bootloop and my device is unlocked. So my question is. Can i install a rom to get out of this bootloop or is there any other way to get of the boot loop? Please i really need help!!!!
You should follow this to go back to 4.1.2 I would try to rsd back to whatever firmware you were on or just kk... Do you have a custom recovery on there to try and flash the ROM... What update were you on prior to doing what you did
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
You should follow this to go back to 4.1.2 I would try to rsd back to whatever firmware you were on or just kk... Do you have a custom recovery on there to try and flash the ROM... What update were you on prior to doing what you did
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was running 4.4.2 kk but after ive tried to flash a image by using flasify to remove the boot loader unlocked message but it failed and it would start up on fastboot and thats it but after using droid utility to try to go back to 4.1.2 but after the reboot it stays in the bootloader message. but i do have a custom recovery im using twrp
I'm guessing you didn't make a backup before trying to flash the image... Or at all... I would say just restore your back up... If you want you could try to flash a ROM it would have to be comparable with whatever kernel you have and it may not work as you tried to use (I'm guessing) matt's utility... I would rsd the 4.4.2 firmware or use house of moto... If you want rid of the warning boot logo ATTACK just released some.... Always make a backup before attempting anything of that nature...and if you want to go back to 4.1.2 after the restore follow the method linked above
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
I'm guessing you didn't make a backup before trying to flash the image... Or at all... I would say just restore your back up... If you want you could try to flash a ROM it would have to be comparable with whatever kernel you have and it may not work as you tried to use (I'm guessing) matt's utility... I would rsd the 4.4.2 firmware or use house of moto... If you want rid of the warning boot logo ATTACK just released some.... Always make a backup before attempting anything of that nature...and if you want to go back to 4.1.2 after the restore follow the method linked above
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah well for now on ill try to make a backups more often but is there any stock roms availible for my device
Not recovery flashable....you should also search around for yourself more...
Sent from my XT907 using XDA Premium 4 mobile app
LIKEABEAST said:
Yeah well for now on ill try to make a backups more often but is there any stock roms availible for my device
Click to expand...
Click to collapse
I've managed to fix my phone with house of moto and its really useful also I want to thank you by trying to help me
Related
Hi all,
I'm freaking out here. I was trying to install a kernel on my N4 using the Toolkit and somehow it said it was done successfully but then my phone got stuck on the Google screen and was never able to start up again.
I do have a Nandroid back up but unfortunately it's on my computer and not on my phone.
I tried using the toolkit AND adb to push the files to my phone but I get the same message: "failed to copy to sdcard: No such file or directory".
I'm completely stuck now and am panicking. Somebody please help!
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Might also be helpful if you specified which kernel you flashed. As long as you didn't flash a kernel for a different device (e.g. nexus 7) you can definitely recover. To reiterate what others have mentioned, fastboot is your friend. There are numerous tutorials on his to install and use it. Check the stickies.
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Crisisx1 said:
Why would you use a toolkit to flash a kernel ...just download zip go to recovery cwm or twrp and flash...
Can you get into fast boot ??
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
My main problem is I need to get my Nandroid backup onto my phone. For some reason, because it's stuck on the Google screen, it's not able to write to the sdcard. Can someone please help me get my files from my computer to my phone?
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Unjustable said:
Flash stock first.
Follow Efrants guides.
http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for your help. I've successfully follows the instructions and got back to Android 4.2.2.
I still want to restore my previous Nandroid though. Although I have placed it in the Clockworkmod backup folder, it's not being seen by CWM recovery. I tried backing up a new nandroid just to test and CWM sees the one it backs up.
Anyone know how I can get CWM to recognize the Nandroid which was done through the toolkit?
Thanks!
darkwolf1789 said:
Yeah I can get into fast boot and even into CWM. I tried factory resetting in CWM but it still gets stuck on the Google screen.
The reason I used the toolkit and not CWM to flash the kernel is because CWM kept failing to flash the kernel, giving me some error and "(bad)" message. It is the kernel to improve Nexus 4 sensitivity directly from another thread.
Can someone please provide me with specific links or detailed instructions?
Click to expand...
Click to collapse
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Crisisx1 said:
If the kernel wasn't installing in the first place you probably shouldn't of flashed it via toolkit
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah I realize that now. But any idea how to get CWM to recognize my Nandroid that I did with the toolkit? Anyone?
joshnichols189 said:
And this is why we don't use toolkits.
Read up on how to use fastboot and how to boot into fastboot.
Then read up on where to find stock images and how to flash them in fastboot. Then do it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
skezza said:
There isn't really anything wrong with a toolkit for certain things, I just think it's a bit strange he tried to use it for something as trivial as this.
Click to expand...
Click to collapse
Ok well to solve the problem I did download the stock images and flash them according to Effrants guide:
http://forum.xda-developers.com/show...php?p=34552123
Then the reason that CWM wasn't recognizing my Nandroids was because I had them in /sdcard/clockworkmod/backups, but they should be in /data/media/clockworkmod/backup.
I recovered everything and I'm back! Thanks for your help everyone.
I flashed the clockworkmod touch zip from my recovery.
It didn't give me the touch recovery, I thought "whatever" and booted back into my rom.
It wouldn't boot.
I went back into recovery and flashed PA rom and gapps.
They weren't booting, I decided to give them a few minutes.
It finally booted.
It no longer connects to wifi or tmobile.
I can't transfer files over usb.
Wugfresh's toolkit couldnt return it to stock.
I thought the recovery might have gotten messed up when I tried to flash CWM touch, so I flashed TWRP from Wugfresh's toolkit.
I used adb sideload to flash a stock rooted rom.
It still took forever to boot, and is still not connecting to wifi/network.
TL;DR I can boot into fastboot and recovery and even the rom but I have no network connection... help guys :'(
It says BASEBAND VERSION - N/A... could that be the problem? If so, how do I fix it?
This is why we don't use toolkits. Return to stock using ADB and do it again...
Sent from my Nexus 4 using xda premium
When I try to fastboot flash the stock image it says "does not contain recovery.sig" "does not contain boot.sig" and only updates the bootloader.
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
ethan.r.besbris said:
Did you dl the image right from Google?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yup.. this one https://developers.google.com/android/nexus/images#occam
So I just flashed the radio by itself and its working fine now thanks for your help man.
No problem. Glad you're up and working.
Sent from my Nexus 4 using xda premium
*****
I've seen some people say its a good idea to update it and others say its not needed, and doesn't offer any improvements. I'm currently stock, rooted, and unlocked and trying to decide if I should revert to stock, take the ota and have everything update or just flash one of the 4.3 stock zip. I saw you can fastboot the updated bootloader but I have like no experience with fastboot and wouldn't want to screw anything up.
So its either revert to stock and accept the ota and gain the updated bootloader, or just leave the old one there and flash 4.3. I could try fastboot but weary of that method.
Sent from my SCH-I535 using xda app-developers app
Do not be afraid of using fastboot so long as the commands you typed are correct.
Leonhan said:
Do not be afraid of using fastboot so long as the commands you typed are correct.
Click to expand...
Click to collapse
Okay thanks...I'm actually in the middle of flashing clean ROM. First ROM on my nexus. I can still go back later and update the bootloader right?
Sent from my SCH-I535 using xda app-developers app
Great. So I flashed clean ROM 4, reboot system and now it keeps automatically booting up into recovery. It shows thr google splash screen, flashes and it shows again. Then boots into recovery. What's going on here?
Sent from my SCH-I535 using xda app-developers app
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
wrong advice, my mistake... thanks for the reminding simms22.
But I wanna stay rooted
Sent from my Nexus 4 using xda app-developers app
You don't have to unroot. Just download and flash TWRP 2.6.3.2. On that build, they fixed the issues of 4.4 ROMS incorrectly flashing. Using it myself with no problems. Its in Original Android Development if I'm not mistaken
Flashing 4.4 Factory Image issues
Currently on my Nexus 4.
Android 4.3 Unlocked and Rooted
Kernel Version: 3.4.0-perf-gf43c3d9
Build: JWR66Y
Baseband: M9614A-CEFWMAZM-2.0.1700.84
Using ClockWorkMod Recovery v6.0.4.3, when trying to flash the 4.4 factory image .zip file on the SD Card I keep getting an "Installation Aborted" error after "Installing update..." step and the red Triangle on the android figure.
When attempting to sideload using stock recovery, getting a "Signature Verification Failed"
Any Suggestions? Thanks
darkfire2040 said:
I'm on twrp 2.6.3.0 and anytime I try and flash a new 4.4 ROM the install fails.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
If you haven't already tried it, under Mount uncheck system, that solved the problem for me.
Yeah I wanna stay in twrp so I will try flashing the latest. The error I'm getting is. Error while trying to update binarys
Sent from my Nexus 4 using xda app-developers app
will_chrome said:
you've got to unroot and back to stock rwcovery 1st if I'm not mistake. the guide to flash stock rom can be found in http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
wtf??? never ever give advice on android ever again!
op, all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
simms22 said:
all you have to do is update your recovery to twrp latest(v.2.6.3.3). flash your rom, flash your 4.4 gapps, and flash the latest supersu then reboot.
Click to expand...
Click to collapse
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I will chime in on this one. I too have had constant failures with TWRP trying to flash ROMs lately. I'm running 2.6.3.3 and everything results in failure. I've tried the unchecking of system mount, multiple downloads with verified MD5s, sideloads, etc. Nothing is working.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
simms22 said:
next time you flash, after it fails, boot into the bootloader from the recovery. then, from the bootloader, go into the recovery again and flash.
Click to expand...
Click to collapse
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
Recognizing your knowledge and experience so asking you to explain why that works. Does something in the internals get reset?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
simms22 said:
ill be honest, i dont know why. but i do know that it has worked for many. the alternative, which works 100% of the time, would be to delete your recovery, then flash it again. btw, did it work for you?
Click to expand...
Click to collapse
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
ph37rd said:
I won't be able to experiment for a couple of weeks. I do know that I've wiped my phone four times or more in the last week with the 4.3 and 4.4 factory images and either manually or using one of the tool kits have added TWRP custom recovery and rooted the phone. Each time trying to flash a ROM it would result in a failure.
Next time I get the chance, I'll give your suggestion a shot and let you know. Are there logs I can capture that might prove useful?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
na. really the only 100% working fix is to delete the recovery, then reflash.
simms22 said:
na. really the only 100% working fix is to delete the recovery, then reflash.
Click to expand...
Click to collapse
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
ph37rd said:
So essentially I've done that with each factory image installed, correct? I'll have to read up on ADB and Fastboot to get the commands to remove the existing recovery. Will be a good way to kill some time (such the life I lead, being envious is not good for your soul)...
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
simms22 said:
no, you just flashed the next version of the recovery over the last. occasionally, something doesnt want to update in the partition, so clearing the previous recovery before flashing the new one will take car of it.
Click to expand...
Click to collapse
OK that confuses me. If using fastboot to place a new boot loader, radio, recovery and ROM are onto the phone and I have to 'fastboot flash recovery recovery.img' to replace the stock recovery that doesn't wipe out the stock recovery? Fabulous sentence structure.
Sent from my Nexus 4 using Tapatalk
I have been trying to change my custom ROM this entire week and I'm rooted and I unlocked my bootloader ,downloaded the ROM I want to use and gapps now the problem is the flash recovery everything I do it there is a problem the first time it said no command and showed the android guy with a caution sign now when I reboot to recovery it shows the bootloader warning sign and then it kinda like skip something then (I think the recovery) then just does a normally boot please help i have use ROM manager ROM installer and I just can't get it to work and I'm using a droid RAZR m version 4.4.2.
Sent from my XT907 using XDA Free mobile app
This has pretty much been covered... Check the linked thread...
Sent from my XT907 using xda app-developers app
Dr3loc said:
I have been trying to change my custom ROM this entire week and I'm rooted and I unlocked my bootloader ,downloaded the ROM I want to use and gapps now the problem is the flash recovery everything I do it there is a problem the first time it said no command and showed the android guy with a caution sign now when I reboot to recovery it shows the bootloader warning sign and then it kinda like skip something then (I think the recovery) then just does a normally boot please help i have use ROM manager ROM installer and I just can't get it to work and I'm using a droid RAZR m version 4.4.2.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
The recovery must be a bad flash try to flash one of the following recovery in fastboot mode with a computer if you know how to do it, if not then try to flash with rashr app from playstore, download the recovery manually from the link below and then flash it with rashr by going into choose from storage accept the warnings... Done.
Twrp
http://androidhosting.org/Devs/Dhacker29/msm8960/TWRP2710-RAZR_M-KITKAT.img
Cwm
http://androidhosting.org/Devs/Dhacker29/msm8960/CWM6049-RAZR-HD_M-KITKAT.img
These are only to flash kk bootloader compatible ROM's
Edit: also you can change the unlocked bootloader waring logo into previous M or Google logo see this post(don't try to flash it with the app mentioned above)
http://forum.xda-developers.com/showpost.php?p=53579570&postcount=87