I have a Nexus 4, and my ultimate goal is to get a custom kernel running on it. After the first attempt failed (predictably), I tried to boot a stock boot.img - one pulled from my device's boot partition, and the other downloaded from the Google stock images.
I am using 'fastboot boot' to boot the image, on Windows 7 64-bit. The command outputs that the downloading and booting process went OKAY, and the phone continues booting, but after the Google logo disappears I just get a black screen. The phone does start though, since my computer then picks up the adb interface, and I set up an SSH server to start when the phone starts. So the phone still works, just I get a black screen with backlight on.
Obviously the first step is to get a stock image booting properly. After that I can attempt to get a custom-built kernel working, but that is a whole other problem. Is there any way to figure out what is going wrong during boot? I can get any log files from the device if needed. It is running stock Android, rooted, with CWMR v6.0.2.3.
Thanks!
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So for now just flash any ROM through recovery, do a full wipe then flash ROM of choice (maybe some thing known stable like a basic cm ROM) then flash gapps then reboot
Unless you need to have a stock ROM for your custom kernel which if this is the case I would recommend just building a kernel based of stock cm for starters, see if this boots for you, don't erase anything while testing just use the command like you did earlier
fastboot boot kernel.img
If you want some more info on fastboot look at my threads and there's one @ xda u for fastboot, but not one for building kernels... Anyway just have your first custom kernel be stock cm, it will be easier as you progress
Best of luck!
Click to expand...
Click to collapse
Well ideally I want to keep the stock ROM - while the N4 is supported by Google I don't want to mess with it too much. The kernel can be 'easily' tested without flashing, which is why I don't want to flash just yet. Are you saying though that the ROM could be to blame for this? Surely though, if the kernel, initrd and configuration are identical the boot should just work straight away? It works fine booting normally - just when fastboot is used graphics don't work.
So you are saying you are running a stock ROM and kernel and when you take the exact kernel from this ROM and use fastboot to boot that kernel you have no GUI?
Something is wrong here then as this should cause no issues. Well first step is to pull a logcat and see if it will show you why there's only a black screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
My exact procedure:
Get a boot.img by cat'ing the boot partition
Start adb logcat
Use fastboot boot boot.img to boot the image
Hopefully I got that right. Unfortunately since I'm under 10 posts I can't post links, but if you put this at the end of the Pastebin URL you can access the logcat: C2Q0eR4k
I'm not sure what cating the boot partition means and logcat hast to be started after booting the kernel, but here is what I would do
Take stock ROM source and take boot.img from it
Be sure I'm using the exact same stock ROM as this kernel
Boot to fastboot
fastboot boot boot.img
Now it will start booting and in the terminal/cmd I would then run adb logcat (probably define my logcat more but whatever)
And then see what happens
But again, there is no reason that an untouched stock kernel won't boot through fastboot or give you issues as its the exact same kernel you are currently using so with this I'm confused as there must be something else missing here, either using a different ROM that the kernel booting is not meant for (different versions or whatever) or really not to sure whatelse.
Try the above again and when I get near a PC I'll peek at your logcat
Sent from my Nexus 4 using XDA Premium 4 mobile app
I have already tried using a boot.img taken directly from the Google Nexus 4 stock, but with exactly the same results. I could post a logcat of that if you want, but I strongly suspect it will be exactly the same. It wouldn't be the recovery changing something, would it? CWMR asked me if I want to prevent Android from overwriting it - I answered 'yes', naturally, but I don't suppose it broke something?
I can rule out the software on my PC being a problem, since both Linux and Windows do the same thing. It could possibly be the USB cable, but I highly doubt it.
'cat' is a utility on Linux that reads files - that's why logcat is called what it is, since it reads the logs. By cat'ing the boot partition I literally read the boot partition, then saved the result into a file - boot.img. A form of copy, if you will.
Recovery should have no effect when booting a kernel through fastboot, I highly suspect the kernel you are trying to boot is for a different stock ROM than you are running right now. Feel free to post logcats and I can look when I'm near a pc
Sent from my Nexus 4 using XDA Premium 4 mobile app
It is the identical stock ROM to the one I'm using on my phone at the moment. For that reason, and based on the fact that the symptoms are exactly the same, I can guess that the logcats will be identical.
How is the logcat looking, by the way? I wish I knew more about Android...
Still haven't gotten near a PC, most of the time I'm mobile but hopefully tonight if I don't get back too late
Is your phone running properly when booting normally then? Or if you flash rather than boot the kernel.img with fastboot?
Sent from my Nexus 4 using XDA Premium 4 mobile app
The phone works perfectly normally - using the same boot.img that I have been unsuccessfully trying to fastboot. It is really strange, almost as if the phone is rejecting the fastboot. And I don't dare flash using fastboot, in case my phone boots without graphics and forces me to flash a new ROM. Although it wouldn't be disasterous, I don't have the time at the moment to go about fixing it if something does go wrong.
Just make a backup of ROM in recovery, then fastboot flash the kernel you've been trying to boot, if there is an issue then just wipe clean and install the nandroid
This whole process will take less than 10 min and will let you know if there is an issue with your kernel.img
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hmm, assuming fastboot isn't lying to me, it seems to have worked. I ran 'flashboot flash boot boot.img' (to which fastboot reported OK) and then continued with the boot in the bootloader. It booted, graphics work, along with all other basic functions like wireless and touch input. To confirm, that is with the boot.img that previously did not work with 'fastboot boot', and the one that I pulled from the device itself.
Any ideas why 'fastboot boot' isn't working properly, while 'fastboot flash boot' works? I guess I can test my custom kernel by seeing if the device boots without graphics, but ideally I would like to test the whole system, not just the kernel after booting. Besides, what happens if my kernel change does in fact break the graphics - I would assume that the fastboot broke the graphics, but when it comes to flashing it would still be broken.
I'm not marking this thread as solved until some kind of answer is to be had over this problem, but I will give 'thanks' to you for giving me the courage to properly mess with my phone and come out of the other side unscathed. Having that backup there will certainly give some reassurance in case something does go wrong!
This is indeed very strange and I can't attest to why flashing the boot works while booting it doesn't as I've never experienced this issue
Its possible you may need to update fastboot on PC but I doubt this
Maybe try to boot another kernel, a recovery would do
Grab a compatible recovery.img for your phone but different than the one you currently have installed and do the same procedure you did for the kernel
fastboot boot recoveryname.img
Now see if it boots you to a different recovery temporarily
Sent from my Nexus 4 using XDA Premium 4 mobile app
I just tried with TWRP 2.6.3.0. Same issue - it seems like the recovery has booted (Windows starts trying to install device drivers) but I just get a black screen.
Then this issue is baffling, never seen it before. I would update or reflash bootloader and update or reinstall fastboot.exe, the issue seems to lie in here but I can't say what it is off hand
Sent from my Nexus 4 using XDA Premium 4 mobile app
As mentioned earlier, I doubt it is the fastboot binary, since I get exactly the same problem on both Windows and Linux (different binaries, from different places). I don't really want to start messing around with the bootloader since as far as I'm aware if something goes wrong with that the only method of recovery is JTAG on the board.
True but it is hard to brick a nexus.
the phone side of fastboot resides within the bootloader so if your issue is here flashing a new one will be the only remedy I can think of, I will say I have flashed bootloader literally hundreds of times (used to buy and sell android phones) and never once bricked one. I used fastboot most every time for this purpose as it is the safest method and even though you seemed to be having an issue with fastboot I can't imagine flashing an appropriate bootloader through fastboot will cause you a brick but it also may not fix anything
But of course this choice is yours to do (I have flashed bootloaders many of times on my n4 without fail) and I can't think of anything else that would cause the problems you're having
Sent from my Nexus 4 using XDA Premium 4 mobile app
Where should I get the bootloader image from? Just from the Google stock ROMs, or is there a thread here on XDA?
In related news, by using the 'fudge' testing method (the kernel works if Windows starts installing drivers and the backlight fluctuates), I have managed to create a working custom kernel! At last I should be able to run LXC on it. Just need to work out why the display keeps tearing...
Great news!
Either extract the hboot from stock ROM (linked at Google dev) or look in the nexus 4 threads for someone who posted it ( they usually do) just be sure to check md5sum or sha1 first
Another note i see I never posted this
http://forum.xda-developers.com/showthread.php?t=2277112
May not help you much anymore but there will be a few tips for fastboot for ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
Related
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.
I have officially stressed myself to the brink. I try to be calm but nowhere do I find how to fix my problem. I have tried flash image gui, I have tried htc dumlock, and I have also tried flashing the .img manually through fastboot usb then flashing the entire zip with twrp 2.2.2.0. Almost every time, I must recover from my TWRP and then use bootimg flasher v1.1 to stop my evo from getting stuck at the boot screen.
Everytime I attempt, I wipe the system and cache, then flash the boot.img, then flash the zip, then the gapps and reboot and it gets stuck on the splashscreen. I must note also that when I had first rooted, and installed Rom toolbox pro, I picked out a boot animation and installed it, restarted the phone, and it didnt work. BUT NOW sometimes after i flash the CM10 that random boot animation appears. WTF? even after i wipe the memory and everything. So I turned off the boot animation, and even deleted them from the phone off the app and it still comes up. I believe this is part or maybe IS the problem. But either way, I do not know how to deal with it. I have had the Cyanogenmod 10 boot animation ONCE out of the many times I have tried flashing but it was stuck on that screen forever like I have read other users have had happen. I REALLY, REALLY would like to be able to use the rom, as it has the new google now voice and all the cool features that i would like to have now that I am rooted.
NOTES:
I am running my stock rom. I have not installed any other ROMS on my phone. The backup i created was after I installed the stupid boot animation. (In case thats another problem)
When i tested the "current" boot animation from within rom toolbox pro, the normal htc evo 4g lte Sprint one loaded but yet, the retarded one i chose for ****s and giggles is what keeps loading. FML (I shouldve chose at least a cool one.)
My backup works fine. I am damn glad i made it!!!
Sorry for any grammatical errors, lowercase i's and what not. im too lazy to press the shift key sometimes. (Caps lock is broken. FML.)
Also sorry for it being so long. I am trying to be thorough to give you experts what you need to help me out.
If you need anymore info as far as detail instructions i will be happy to write back on this forum.
PLEASE do not tell me that my answer is on another forum, because I believe that it is not due to the special situation I have. I have tried looking for days for an answer.
I will be periodically checking this forum for any replies and will reply ASAP, whenever i am available.
Thank you for your time and patience!
Here is my phone's specs. I tried to get as much as possible. Again, if there is more info that would be needed I will gladly get it and post it here.
I am running on booloader:
Tampered
Unlocked
Jewel PVT SHIP S-ON RL
HBOOT- 1.19.0000
Radio- 1.12.11.0009
OpenDSP-v29.1.0.45.0622
eMMc-boot
Aug 9, 2012, 15:14:25
About Phone:
Hardware Version 0003
Android Version 4.0.4
Sorftware 2.13.651.1 710RD
HTC Sense Version 4.1
HTC SDK API level 4.24
HTCExtension_403_1_GA_22
PRI Version 2.45_003
PRL Version 25006
Anyone?
Sent from my EVO using xda app-developers app
What happens when u fastboot the kernel? Does it say success?
Sent from my EVO using xda premium
Use fastboot to flash the kernel, if you still have trouble wipe the partion and try again
Fastboot flash boot boot.img extract it from the Rom and place in adb folder.
Fastboot erase boot to wipe partition
I had problems trying out CM10 also. This worked for me.
Edit:: I'm assuming you have TWRP recovery and are unlocked before you start this...
Buy Flash GUI from app store. Worth the 99 cents!
Open it and point it to the CM10 zip. It will extract the parts it needs and flash the kernel.
Once that is done have it reboot (it prompts you) into recovery and then wipe system, do factory reset, then flash the CM10 zip and gapps zip.
Reboot one last time
The CM10 animation went on for a couple/few minutes the first time, don't panic.
You should be good after that.
Make sure to install Flash GUI again though. You will need to use it to go back to a ICS/Sense ROM later (using same method). And my guess is you might want to.
CM10 is incredible on this phone but it's not quite ready. I have tons of data connection issues and NEVER get 4G in the places where I've always had good signal. Also, the camera is just about worthless. No disrespect to the devs working on it. I'd have no idea how to work the magic they are doing and I appreciate their time.
Good luck.
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
When I fast boot the kernel everything says success with no errors
Sent from my EVO using xda app-developers app
How do you partition? Do you think that is my problem?
Sent from my EVO using xda app-developers app
You don't need to partition anything, just flash kernel and reboot
Hey guys thanks to everyone replying! I'm currently at work as a delivery driver trying to write back.... Dangerous! Lol but also I have the 5 min limit to post so I will try and do some of these methods when I get home and report my findings to you all ASAP! But to anyone with more suggestions please keep bringing Em!
Thanks!
Sent from my EVO using xda app-developers app
Hey guys its me again. I just got home and I'm dead beat tired. I had to work later than I thought. Im gonna get some sleep but once again thank you everyone for giving me some answers that I can try tomorrow! I will, without a doubt, try some of them tomorrow after my classes. But first I would like to leave you all with a VERY important question that I did not think of. Is there a stable release of cm10 that has worked for you all that I can try? Perhaps that was the problem too? I was trying the nightly release that came out October 2. Once again thank you all for replying and i will try to do this ASAP after class. Sorry to leave you guys hanging so much!
Sent from my EVO using xda app-developers app
Thing is it's a nightly, some people have flashed back to earlier versions and others upgrade with out any issues. Ymmv
padrino121 said:
I did the very same thing earlier today. I flashed CM10 without paying attention tot he fact that I was unlocked but still had S-On so the phone would continually get stuck on the boot screen. I must have reflashed and formatted with TWRP 10 times before diving into it deeper.
In terms of workflow the only way I could make it work properly was to:
1. Use TWRP to flash CM10 and gapps (just add both zips)
2. Reboot into bootmanager using TWRP.
3. Use fastboot to flash boot.imgfrom the CM10 zip (fastboot flash boot /path/to/boot.img)
If I did the boot.img first it didn't seem to work, it should so maybe that wasn't the real issue but the above process worked and I'm now running CM10.
Click to expand...
Click to collapse
Which nightly did you use?
Hey guys so I used padrino121s suggestion for flashing. At first I tried flash gui again like you had suggested but it got stuck in the boot screen. So I decided to download a different nightly release (20121002) and it flashed perfectly and everything transferred over correctly! Thank you guys so much for all of your help! Now one more question... If I decide to get a new nightly build, do I have to flash everything all over again like I had to the first time? Or because I have flashed cyanogen mod already do I just do something else to update it?
Sent from my EVO using xda app-developers app
it all started when i installed a faulty launcher
my phone's in a boot loop
when i try to slide the key into the lock on the lockscreen, it reboots.
otherwise touch is working fine (emergency call, status bar etc)
but since i can't open the lock, i can't access the home screen and apps and stuff..
obviously i tried recovery, but it doesnt have a factory reset option (strange). the recovery mode only has some phone tests and calibrates
the other hard key combination opens up some black screen with "fastboot mode" written. and that's it.
my phone is gingerbread 2.3.5, unrooted. the company is a less popular and cheap one but it's not china.
long story short, i cant get outta boot loop coz recovery doesnt have factory reset option
plz help!
thanks
i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.
fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
deadbunny said:
thanks
i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.
fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
Click to expand...
Click to collapse
In recovery, try to wipe cache and dalvik cache. If still, then you need to flash stock ROM
deadbunny said:
thanks
i did as you said. but when i erased everything and booted the phone. it's stuck on the manufacturer's logo. it doesnt even reach lock screen now.
fastboot commands are working. i flashed a new recovery, but its not accessing. what should i do?
Click to expand...
Click to collapse
That is because when you ran those commands you wiped the rom on your phone completely so now when it tries to boot it has nothing to boot into. Please give the name of the phone so we can help you more.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
Erasing the user data and cache was good, but erasing boot erases your kernel, just find the one that came with your ROM and as long as its in .img format use fastboot to flash it and all should work great
Sent from my Nexus 4 using xda premium
yo, the prob is, it's a recent phone, but from qmobile
it's qmobile bolt a2 lite. i cant find the stock rom (it was released in 3 july 2013, i believe)
so, can't i install some other ROM that all gingerbread phones support? it has 1 ghz processor, 256 mb ram, and 200 mb internal storage
thanks
i have a 2gb micro sd card as well
Then you have an issue, right now it sounds as you have no kernel maybe if your lucky the manufacture will respond to a request to release the kernel source or have a copy of factory firmware you can download.
Otherwise try to find someone with the same phone and see if they can get you a copy of the kernel
Sent from my Nexus 4 using xda premium
since i can't find the exact stock ROM for this lesser known brand, isn't there some universal gingerbread 2.3.5 stock rom? the manufactureres obviously use a modified version of google's stock gingerbread 2.3.5
It won't work, you can't just flash some generic aosp ROM to your phone, if it were that easy every phone would have tons of ROMs
You need a device tree that contains all the proprietary drivers etc to build from source and just flashing a random kernel or ROM won't do you any good (possibly make things worse)
You need to contact the maker of your phone and request this or find someone who can get you a ROM dump
Sent from my Nexus 4 using xda premium
okay thanks
Simple just claim ur warranty man!!
Sent from my A2 using xda app-developers app
im not in pakistan dude. i moved to canada. that's the prob
deadbunny said:
im not in pakistan dude. i moved to canada. that's the prob
Click to expand...
Click to collapse
That's sad
Sent from my A2 using xda app-developers app
I recently rooted my HTC sensation and i have now achieved S-off and unlocked my phone.
The main problem is that now if my phone turns off to reboot it I need to go into the recovery and to the command Fastboot boot boot.img. i really need a solution to this because its really annoying to have to use my computer every time I need to reboot my phone especially because im using a CWM and i have a nightly CM rom currently installed
HELP PLEASE
Sounds like something is wrong with the kernel, try to do a full wipe and flash the ROM again
Sent from my Nexus 4 using xda premium
thankswill try that im going on holiday so i will do it when i get back hopefully my phone won't die
ive tried that now and its still not working, i also tried flashing a custom ROM and its still not working.
Maybe try to reflash your bootloader?
Sent from my Nexus 4 using xda premium
I've tried flashing the bootloader and the problems still occurring.
any other ideas?
I don't own a sensation so I don't know this is a common issue, but you can always try reverting to stock and restoring radio secure flags, this can tell you if its firmware/software or a hardware fault
Sent from my Nexus 4 using Tapatalk 2
is their possibly a link you could provide to help me with restoring radio secure flags or is that restored when reverting back to stock.
plz and thank you
anything?
asianminime said:
anything?
Click to expand...
Click to collapse
Hi,
Try running a RUU.
Look HERE
Are you supercid?
hello I fixed the problem I didn't use the RUU however because I was really confused doing it.
the way In which I had done it was by factory resetting my phone and completely wiping the data and the cache so I didn't have any rom installed it was just the phone and the bootloader. then I went and re-installed the ROM I had chosen with the CWM recovery. although after I had installed the rom and the G-apps I wen and I opened a command prompt window and used the following instruction:
Fastboot Flash boot boot.img
after this I had rebooted my phone using the code:
Fastboot boot boot.img because I didn't know I had fixed the problem but I had to reset my phone and It just worked so thank you all so much for your help I really appreciate all the help and support given :good::victory:
So I've tried researching this slight issue and I have seen a lot of different solutions but none of them apply to my particular problem. My phone works just fine when booted regularly and charges just fine. The only time I'm having an issue is if I boot into recovery. I just installed twrp 2.7.0.3 and tried to reboot in order to flash supersu. No dice. I've tried rebooting into fastboot and reflashing and I've tried the M8 toolkit. Reflashing works, but still won't boot to recovery and the toolkit just hangs trying to flash the file. I think that's where my issue lies. I waited 19 minutes and eventually closed the program and just rebooted. I'm thinking this caused an issue and corrupted my recovery but i figured reflashing would solve this.
I was wondering if someone could clarify this for me, in which i'll just sit tight and wait until an ruu releases and stick with stock sense. The phone works perfectly so I can deal for a little while. I was just hoping to move to the GPe rom and get xposed running on it.
Thanks yall. I'll keep searching until I have to go to work and if I find a solution before anyone responds I'll update this post so it can be locked.
I would make sure you adb files are up to date, and try flashing philz recovery instead.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
HolyAngel said:
I would make sure you adb files are up to date, and try flashing philz recovery instead.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you using philz instead? I flashed twrp and it's very buggy. Did you fastboot flash recovery etc...? How can I install philz over twrp?
Thanks
Sent from my HTC One_M8
yeah im using philz, have been since it came out as i thought the same about twrp, tons of issues.
definitely 'fastboot flash recovery philz_touch_6.25.5-m8.img'
It'll apply itself right over your current recovery no problem :good:
pokedroid said:
So I've tried researching this slight issue and I have seen a lot of different solutions but none of them apply to my particular problem. My phone works just fine when booted regularly and charges just fine. The only time I'm having an issue is if I boot into recovery. I just installed twrp 2.7.0.3 and tried to reboot in order to flash supersu. No dice. I've tried rebooting into fastboot and reflashing and I've tried the M8 toolkit. Reflashing works, but still won't boot to recovery and the toolkit just hangs trying to flash the file. I think that's where my issue lies. I waited 19 minutes and eventually closed the program and just rebooted. I'm thinking this caused an issue and corrupted my recovery but i figured reflashing would solve this.
I was wondering if someone could clarify this for me, in which i'll just sit tight and wait until an ruu releases and stick with stock sense. The phone works perfectly so I can deal for a little while. I was just hoping to move to the GPe rom and get xposed running on it.
Thanks yall. I'll keep searching until I have to go to work and if I find a solution before anyone responds I'll update this post so it can be locked.
Click to expand...
Click to collapse
Seems like every problem in here is when someone uses a toolkit. IMO it is easier just to use the commands. There is nothing wrong with twrp as most people including myself are using it flawlessly. Download fresh copy of twrp. Make sure you get .img file, not .zip. Boot your phone, plug in and type "adb reboot bootloader" it will reboot to fastboot, if not, you do not have newest adb drivers, get this fixed before moving on. once in bootloader type "fastboot reboot-bootloader" this will just reboot your boot loader and let you know fastboot is working. If not fix this. next move to your directory with twrp and type "fastboot flash recovery twrp***.img" should only take 5 seconds. next type fastboot reboot to make sure system is still booting. Then type "adb reboot recovery" and it should go to twrp. Make sure you are getting the UL_CA twrp and not the whl. whl is for sprint and will not work. let me know. UL_CA is not available on official site. search the xda forums for it.
I actually tried the commands first and couldn't get it that's why I tried the toolkit. That's actually what ended up working for me though, but at least I'm good to go! I should have updated this a few days ago but forgot lol this thread can be locked if a mod wants to. Thanks all
Sent from my HTC One_M8 using Tapatalk
HolyAngel said:
yeah im using philz, have been since it came out as i thought the same about twrp, tons of issues.
definitely 'fastboot flash recovery philz_touch_6.25.5-m8.img'
It'll apply itself right over your current recovery no problem :good:
Click to expand...
Click to collapse
Which version of the recovery did you download? I can't find an AT&T version . Just regular M8 version. Just wanna make sure
Sent from my HTC One_M8 using Tapatalk
Z51 said:
Which version of the recovery did you download? I can't find an AT&T version . Just regular M8 version. Just wanna make sure
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
The regular m8 version in original android development ^^
Sent from my HTC One_M8 using XDA Premium 4 mobile app