Hi, i can't figure out how to boot a custom boot.img with fastboot on last bootloader.
I tried both
Code:
fastboot boot boot.img
and
Code:
fastboot -c "lge.kcal=0|0|0|x" boot boot.img
but it won't boot, stuck on Google logo. I'm on stock 4.3 and I tried to boot also the boot.img I extracted from the factory image, same result. Please note that I was able to boot clockworkmod.img using the 2nd command.
Anyone has a solution?
But if you were able to boot the clockworkmod.img, you could only boot into recovery of course? And that worked?
Which other boot images did you try?
Sent from my Nexus 4 running Android 4.3
mihahn said:
But if you were able to boot the clockworkmod.img, you could only boot into recovery of course? And that worked?
Which other boot images did you try?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Yes, using fastboot I was able to boot only clockworkmod.img (obviously only boot into recovery), nothing else. Clockworkmod worked perfectly and I was able to flash SuperSU.
First I thought my custom boot.img was broken, so I tried the boot.img that I extracted from official factory image, but no luck.
I can't figure out...
Try this:
http://forum.xda-developers.com/showthread.php?t=2347060
Sent from my Nexus 4 using xda app-developers app
failly said:
Try this:
http://forum.xda-developers.com/showthread.php?t=2347060
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Wait, my Nexus is not bricked It works very good. I only want to try the custom kernel I built and I always used the fastboot boot command to do that... but now it's not working anymore...
d3s3rt_eagle said:
Wait, my Nexus is not bricked It works very good. I only want to try the custom kernel I built and I always used the fastboot boot command to do that... but now it's not working anymore...
Click to expand...
Click to collapse
Oh damn sorry I overread your whole post!
Sent from my Nexus 4 using xda app-developers app
fastboot boot boot.img works for me. Kernel/ramdisk compatible with your ROM?
Sent from my phone. Please forgive typos and brevity.
Problem half-solved. I noticed that the phone is actually booting, but the screen is blank... the strange thing is that if I flash the boot.img the screen works! The problem only happens when I try to boot with fastboot... anyone experienced this strange thing??
Related
Anyone have any suggestions? Booting into recovery froze my device on the Google screen.
Sent from my Galaxy Nexus using xda app-developers app
Bump. Anyone have any suggestions?
joshtb86 said:
Bump. Anyone have any suggestions?
Click to expand...
Click to collapse
I suggest to install the Android ask and use the following fastboot commands.
fastboot oem unlock
fastboot flash recovery recovery.img
*change recovery.img to whatever filename the recovery is and put it in the same directory as your fastboot.
This way you'll learn what a "rootkit" does and be on your way to learning more .
Sent from my Nexus 7 using xda premium
mwalt2 said:
I suggest to install the Android ask and use the following fastboot commands.
fastboot oem unlock
fastboot flash recovery recovery.img
*change recovery.img to whatever filename the recovery is and put it in the same directory as your fastboot.
This way you'll learn what a "rootkit" does and be on your way to learning more .
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you know where i can get a version of CWM that works for the n7?
thanks!
joshtb86 said:
do you know where i can get a version of CWM that works for the n7?
thanks!
Click to expand...
Click to collapse
Here ya go.
before i do this, do i need to be booted or in bootloader. bootloader, because its using fastboot, right?
joshtb86 said:
before i do this, do i need to be booted or in bootloader. bootloader, because its using fastboot, right?
Click to expand...
Click to collapse
Fastboot mode within bootloader i believe.
So i recently accidently flashed the newest franco kernal onto cm10.1 without realizing it doesn't support 4.2. My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery and when i boot it normally i get a chain of FC from NFC services, com.android, and systemUI at the lockscreen. It doesn't seem to enable USB debug at the lock screen.
any ideas?
Grona said:
So i recently accidently flashed the newest franco kernal onto cm10.1 without realizing it doesn't support 4.2. My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery and when i boot it normally i get a chain of FC from NFC services, com.android, and systemUI at the lockscreen. It doesn't seem to enable USB debug at the lock screen.
any ideas?
Click to expand...
Click to collapse
Start over using Odin...can you get it into download mode...
Sent from my SGH-T999 using xda premium
phordych05 said:
Start over using Odin...can you get it into download mode...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I haven't tried that yet. I've never out it into download mode before. How do I reach that?
Sent from my One X using Tapatalk 2
Grona said:
I haven't tried that yet. I've never out it into download mode before. How do I reach that?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Odin won't get you anywhere since it's for Samsung devices.
Download a CM10.1 nightly for your device and extract the boot.img file from the zip.
Flash the boot.img from fastboot to restore the kernel
Code:
fastboot flash boot boot.img
reboot, and done.
comminus said:
Odin won't get you anywhere since it's for Samsung devices.
Download a CM10.1 nightly for your device and extract the boot.img file from the zip.
Flash the boot.img from fastboot to restore the kernel
Code:
fastboot flash boot boot.img
reboot, and done.
Click to expand...
Click to collapse
I don't think I can get it to fast boot, adb doesn't read my device since android debugging doesn't turn on. I'll give it a shot though when I get home.
Sent from my One X using Tapatalk 2
Grona said:
I don't think I can get it to fast boot, adb doesn't read my device since android debugging doesn't turn on. I'll give it a shot though when I get home.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In your OP you stated:
Grona said:
...My problem is now when i go to fast boot my N7 wouldn't read any of my button presses to go to recovery...
Click to expand...
Click to collapse
So, hopefully you can still get there.
Kernel problems won't affect fastboot. Generally speaking, the only way you wont be able to get to fastboot is with bootloader corruption or hardware failure, neither of which sounds like your issue.
so i have my tablet in fastboot, and i have ADB up and running, but when i type in ADB devices it comes up blank.
any ideas?
Grona said:
so i have my tablet in fastboot, and i have ADB up and running, but when i type in ADB devices it comes up blank.
any ideas?
Click to expand...
Click to collapse
Adb doesn't work in fastboot. You need to use fastboot. Run this:
Code:
fastboot devices
Then try what I previously posted.
Sent from my Nexus 4
comminus said:
Adb doesn't work in fastboot. You need to use fastboot. Run this:
Code:
fastboot devices
Then try what I previously posted.
Sent from my Nexus 4
Click to expand...
Click to collapse
So after flashing the boot.img from the cm10.1 nightly I'm getting a garbled screen after the CM boot screen, any thoughts?
Sent from my One X using Tapatalk 2
Boot to recovery and wipe cache/dalvik. Reboot and try again. If that fails to resolve the issue, try flashing the entire cm10.1 nightly from recovery.
Sent from my Nexus 4
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
RohMish said:
Hi, when android 4.3 launched, i went back to 4.2 complete stock with no custom recovery and locked the bootloader to receive the update OTA.
Now I have 4.3 with Z20i bootloader and when i flash cwm, phone gets stuck on the GOOGLE splashscreen and after 1/2 hour moves to the X screen and gets stuck there. Recovery does not works. I had to flash stock recovery and wipe all data to make it work. when trying
Code:
fastboot boot recovery.img (recovery-clockworkmod-6.0.3.6-mako.img)
, it shows a black screen after google and then reboots in safemode whenever any button is pushed.
Click to expand...
Click to collapse
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
Normally you have to execute
Code:
fastboot flash recovery recovery.img
Try it with the latest cwm image
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
flash installs the recovery but nothing works. i have to do a wipe and install the stock recovery to boot it. i wrote it on top
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Put your device on the bootloader menu and use this: https://developers.google.com/android/nexus/images#occamjwr66v
Always use the stock bootloader like pretty much everyone who owns the Nexus 4.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
RohMish said:
It is on the stock bootloader that comes with the nexus 4. The problem is after 4.3 update, i am not able to install cwm on my phone. using fastboot boot command gives black screen while fastboot flash boots a recovery whose none of functions work as it is unable to mount any partition, etc. and i have to install factory image of recovery and do a factory reset to boot the device again to android.
Click to expand...
Click to collapse
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Oh, I thought that was some custom bootloader, apologies.
Em yeah you will have to install the factory image.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
RohMish said:
Did that. it has made me more mad as it took 3 hours to download and when your phone is not working, even ever minute is like an day.
Click to expand...
Click to collapse
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Did you try installing an other recovery like either the latest version of CWM or TWRP?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
tried an older version of cwm, touch, everything. but all are having same issues
RohMish said:
tried an older version of cwm, touch, everything. but all are having same issues
Click to expand...
Click to collapse
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Older is worse!
Try TWRP 2.6.0.0.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
UPDATE: Tried twrp via fastboot boot command. nothing. just a blank screen after the reboot from bootloader (and after google boot screen) for a few seconds, andd then shuts down.
RohMish said:
trying it now.
any ways i can switch to cwm after that as i prefer cwm any day of week. will fastboot boot command word as i dont want to sit flashing the factory image and let the apps and all download again
Click to expand...
Click to collapse
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
spaceman860 said:
The issue is that fastboot boot recovery doesn't work on 4.3. The new command if fastboot - c lge.kcal=0|0|0|x boot recovery.img
BLACKED OUT LTE N4
Click to expand...
Click to collapse
not working. says 0 is a not a command. this is as | works as a batch separator in windows
Update: as i remembered modifier <"> will prevent | from kicking into next line, i tried that, and it works!
fastboot -c "lge.kcal=0|0|0|x" boot recoverycwm.img. but still no action. tried a backup, it starts to backup but files are corrupted. and nothing else work.
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
spaceman860 said:
This is from efrant guide
Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img Note: If you are running the latest bootloader (z20i), the command would be: fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img Thanks hwti & el_charlie
BLACKED OUT LTE N4
Click to expand...
Click to collapse
i loads up but is kind of broken.
any way i can copy the files to my pc to do some analysis. currently the folder which used to save the files has nothing. adb pull /mnt/shell/emulated/clockworkmod/backup/ /android/adbbackupfiles/nexus4 is yielding nothing.
OK. so now i tried using the touch version, and this time there are some files(Still copying). but those are very different than what it was on my older phones and my initial backup. Sorry, I had got away with this due to studies. now the files are .a and.b and the orignal file which is 0KB
Stuck on google logo screen and then after 3 resets goes to CWM
I have only 1 rom on it the cataclysm rom and it gives an error when I try to flash it
I have no backup and no other rom besides this
noway either to put a rom on the Nexus 4.
LOL I am so screwed
I am currently in CWM and the PC won't recognize the device and there is nothing to do.
Please help.
Use fastboot commands to flash stock image....
Boot into fastboot and then connect n4 to your PC...run adb and type fastboot devices....
It will give you n4 serial no. And then flash stock image(Google how to flash stock image using fastboot commands)
Sent from my Nexus 4 using xda app-developers app
Ankurcul said:
Use fastboot commands to flash stock image....
Boot into fastboot and then connect n4 to your PC...run adb and type fastboot devices....
It will give you n4 serial no. And then flash stock image(Google how to flash stock image using fastboot commands)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
YESSS it worked
OMFG thank you so much
So, one of my family members was mucking around on their tablet. I was sure that I has locked down the appropriate areas, but as of right now, I think I'm looking at a hard-brick. I'm not sure what kind of fastboot capabilities I have, turning it off, and on again boots to what looks like fastboot, but I have a Google splash screen. Using the vol up/down/pwr button does boot into fastboot, but I'm not sure what I have at my disposal for flashing. Any suggestions? I've just never seen anything like this before.
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Pirateghost said:
If you can boot into fastboot, it isn't a hard brick. A brick doesn't turn on.
Just try fastboot flashing the stock image on it from Google.
Sent from my Nexus 5
Click to expand...
Click to collapse
bsquare said:
Another alternative would be to boot into recovery, if you can.
I assume you had twrp or cwm? If so, you could reflash the rom you're using. If not, you could install twrp from fastboot and then sideload a rom of your choice.
Click to expand...
Click to collapse
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Verfassergeist said:
ADB push wasn't accepting anything. What I ended up doing, was using the Wug toolkit to force-flash a stock image. Still not sure what the hell happened, I'm just happy it works now.
Thanks for your help!
Click to expand...
Click to collapse
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Pirateghost said:
Fastboot and adb are not interchangeable.
Adb doesn't work in fastboot mode
Sent from my Nexus 5
Click to expand...
Click to collapse
I....*facepalm*