Develop Bugs

[Q] Flashing Kernels on my HOX with ViperX 2.7 doesn't seem to be working

I have tried flashing using the Venom Flasher script.
I have tried manually flashing the Boot.img from the Faux 10 mainline Kernel and then flashing the Kernel.
it just doesn't seem to be taking and my battery life is just terrible, maybe 3-4.5 hours before im below 20%
What am I doing wrong?

If I selected the option during the ROM install to not use a custom kernel, would that matter?
Sent from my Nexus 7 using Tapatalk 2

Are you getting 3-4 hours with the screen on or on standby?
off-topic: going sydney christmas holidays

Standby
Sent from my Nexus 7 using Tapatalk 2

Sydney is awesome by the way
Sent from my Nexus 7 using Tapatalk 2

Probably something draining your battery. Install BetterBatteryStats (http://forum.xda-developers.com/showthread.php?t=1179809) and monitor partial wakelocks in the app.

tomascus said:
Probably something draining your battery. Install BetterBatteryStats (http://forum.xda-developers.com/showthread.php?t=1179809) and monitor partial wakelocks in the app.
Click to expand...
Click to collapse
Thanks, I'll give it a go but what would be stopping me flashing new kernels?
Sent from my Nexus 7 using Tapatalk 2

Nothing would be stopping you, I flash a different kernel weekly actually.
Process:
1. Download kernel and place somewhere
2. If you don't need to repack skip to step 5
3. Get the boot.img from your current ROM
4. Repack kernel at http://nibble.cc/repack/
5. Reboot to bootloader, into fastboot, make sure to plug in USB
6. type: fastboot flash boot (name of file here)
7. fastboot erase cache
8. fastboot reboot-bootloader
9. select HBOOT
10. Go to recovery
11. Mounts and Storage -> Mount USB
12. Copy the modules (zip file) to SD card
13. Unmount
14. Choose zip to install from and install the modules
15. Reboot
16. Profit
I've flashed so many kernels in my life and never have had a bootloop (except the time I flashed my first custom kernel).
Let me just tell you firstly that the battery drain you're experiencing is not normal and changing kernels would really do much to help it.

tomascus said:
Nothing would be stopping you, I flash a different kernel weekly actually.
Process:
1. Download kernel and place somewhere
2. If you don't need to repack skip to step 5
3. Get the boot.img from your current ROM
4. Repack kernel at http://nibble.cc/repack/
5. Reboot to bootloader, into fastboot, make sure to plug in USB
6. type: fastboot flash boot (name of file here)
7. fastboot erase cache
8. fastboot reboot-bootloader
9. select HBOOT
10. Go to recovery
11. Mounts and Storage -> Mount USB
12. Copy the modules (zip file) to SD card
13. Unmount
14. Choose zip to install from and install the modules
15. Reboot
16. Profit
I've flashed so many kernels in my life and never have had a bootloop (except the time I flashed my first custom kernel).
Let me just tell you firstly that the battery drain you're experiencing is not normal and changing kernels would really do much to help it.
Click to expand...
Click to collapse
hahahah I just tried to reflash rom and now I am just getting a bootloop constantly now. I am awesome

lol i don't understand man, best to start over:
1. Flash the original boot.img located in the ROM zip
2. fastboot erase cache
2. Go to Recovery
3. Format /System
4. Wipe Data/Factory Reset
5. Wipe Cache
6. Wipe Dalvik
7. Flash ROM
I swear this should work xD

should be good, im not worried about getting rom back, its just my luck tonight... as in none.
BTW besides the repacking thing, which i haven't done then I have done those exact steps and still no love

Did the original kernel work at all? 10:11PM, still got time.

wait up I am going to try the repack with both the boot.img's. sounds different so it might work

jpustin said:
wait up I am going to try the repack with both the boot.img's. sounds different so it might work
Click to expand...
Click to collapse
Yep let me know how to goes mate. Remember to flash modules and erase cache

no go, it just doesn't seem to want to let me flash new kernels

I have viperX on my hoxas well. I flashed bricked kernel a few days ago and it works like a charm ( except for the occasional reboot because of the ****ty hotplug that keeps setting my min CPU to 1.6 GHz ...). What worked for me was to flash the repacked boot.img, then wipe cache, then flash the kernel zip in CWM, then wipe dalvik .
Sent from my HTC One X using xda app-developers app

its cool bro, just out of interest, what should the kernel version say?

jpustin said:
its cool bro, just out of interest, what should the kernel version say?
Click to expand...
Click to collapse
mine says

tomascus said:
lol i don't understand man, best to start over:
1. Flash the original boot.img located in the ROM zip
2. fastboot erase cache
2. Go to Recovery
3. Format /System
4. Wipe Data/Factory Reset
5. Wipe Cache
6. Wipe Dalvik
7. Flash ROM
I swear this should work xD
Click to expand...
Click to collapse
Nice, and easy. Thanks mate!
What if an idiot (me) didn't do step 2. fastboot erase cache? :silly:
Does any of the following steps 3, 4, 5, & 6 do the same?
Can I do it now, after I installed ROM? What could go wrong if I did step 2 on an operating kernel/ROM?
Cheers!

It says this.
Sent from my HTC One X using xda app-developers app

Question regarding kernel

Ok... this is weirdest bug i ever seen.
After wipe all data (all thing) up new rom eg. paranoid, AOKP, myOneV... all of them.
1/Stock kernel is default, but modder need uploaded new kernel to run ether rom.
2/Flash new rom needed...yeah we got new kernel at first time... but when reboot phone.... what the f.... auto back-up to default kernel??
IE: AOKP, myOneV, CM10, ... need newest kernel to run, done... but only first time, the second boot is bricked....
=>Solve this for me plzzzz
My idea: why we don't cook new kernel vs new rom when release new version?

u need to do fastboot flash recovery (nameofrecovery). img
u must have done fastboot recovery (nameofrecovery). img
Sent from my One V

paarthdesai said:
u need to do fastboot flash recovery (nameofrecovery). img
u must have done fastboot recovery (nameofrecovery). img
Sent from my One V
Click to expand...
Click to collapse
"Flash new rom needed...yeah we got new kernel at first time" i know so do i ... that's my problem, flash done 1st run is ok but reboot in 2nd is bricked. So i MUST flash recovery when 2nd and 3rd and 4th when reboot... fk... i my phone gonna R.I.P

i ain't understanding a **** u tokn dude
Sent from my One V

paarthdesai said:
i ain't understanding a **** u tokn dude
Sent from my One V
Click to expand...
Click to collapse
lemme explain what did he say, he got prob when up new rom, the rom needed flash boot (new kernel), he know about it. The 1st is flash, boot to phone, he can see new kernel in setting then use whatever like overclock, undervolt, install app,... then he make a reboot (restart) go to setting menu, he regconize the original kernel is back, overclock is disable, same at undervolt and bricked phone if original kernel no compatible with that rom. That's the PROBLEM.

kenintel said:
lemme explain what did he say, he got prob when up new rom, the rom needed flash boot (new kernel), he know about it. The 1st is flash, boot to phone, he can see new kernel in setting then use whatever like overclock, undervolt, install app,... Then he make a reboot (restart) go to setting menu, he regconize the original kernel is back, overclock is disable, same at undervolt and bricked phone if original kernel no compatible with that rom. That's the problem.
Click to expand...
Click to collapse
bootloop is not bricked phone!!!
If you had a bricked phone you will never ever be able to power up your phone!

1ceb0x said:
bootloop is not bricked phone!!!
If you had a bricked phone you will never ever be able to power up your phone!
Click to expand...
Click to collapse
err my bad, so how to solve this?
I mean default kernel loop when 2nd reboot...

Do this
Go to fast boot
Open cmd
Fastboot flashboot boot.img
Now don't restart go to the recovery and wrote all cache and then flask which ever roms u want, believe me this will work ....
Sent from my One V using xda app-developers app

cybervibin said:
Do this
Go to fast boot
Open cmd
Fastboot flashboot boot.img
Now don't restart go to the recovery and wrote all cache and then flask which ever roms u want, believe me this will work ....
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
1/Go to fast boot
Open cmd
Fastboot flashboot boot.img <---- which boot.img? "stock kernel"
When flashboot device MUST restart, i cant resist that...
2/Now don't restart go to the recovery and wrote all cache
Wipe all data or wipe all cache? dalvik cache? can u explain....

See when u go.to a rom page there will be a link for kernel......and take the kernel and don't restart our it will be stuck in boot loop....
No go to recovery with out restarting....wipe all data if a new rom...
And then download the link and
Sent from my One V using xda app-developers app

i think they are using hassoon tool to flash the kernel, because that script will automatically reboot the phone after the kernel is flashed .
1.You need to first, take THE kernel for the RESPECTIVE ROM
2. Rename it to boot.img
3. You have to have installed the Android SDK + the platform tools to be able to take advantage of fastboot
4. Reboot your phone into bootloader.
5. Connect your phone to your PC.
6. Press start, enter RUN and type cmd. Press enter.
7. Type your path where your sdk is installed (i.e CD C:\Program Files\Android\android-sdk\platform-tools\)
8. Put the boot.img into the platform-tools folder
9. Now go back to CMD use "fastboot flash boot boot.img" without the quotes.
10. It will send a message like "sending boot.img.... done... writing boot img.... done.... elapsed x seconds).
11. Reboot Recovery from bootloader.
12. Wipe everything and then flash your rom.
13. Reboot and that's it.
As simple as that. If you don't know how to use android sdk or you don't have it installed, simple use the search bar and type android sdk tutorial.

thanhi said:
Ok... this is weirdest bug i ever seen.
After wipe all data (all thing) up new rom eg. paranoid, AOKP, myOneV... all of them.
1/Stock kernel is default, but modder need uploaded new kernel to run ether rom.
2/Flash new rom needed...yeah we got new kernel at first time... but when reboot phone.... what the f.... auto back-up to default kernel??
IE: AOKP, myOneV, CM10, ... need newest kernel to run, done... but only first time, the second boot is bricked....
=>Solve this for me plzzzz
My idea: why we don't cook new kernel vs new rom when release new version?
Click to expand...
Click to collapse
I edited your thread title. In the future, please follow forum rules and include a relevant and descriptive thread title. Using vulgarity is unnecessary, offensive, and not welcome on XDA.

Stuck on boot

Hey again..
I was hoping my first custom ROM flashing would be successful considering I've read plenty of threads on how to do it and were pretty careful, but that's not the case.
I tried to give Slim Bean a shot, downloaded Slim-endeavoru-3.1.0-OFFICIAL from their page, and Slim_Gapps along with it.
HBOOT is 1.39, CWM is 5.8.4.0
So I did just as instructed, booted into recovery, wiped data, formatted /system, and then flashed Slim Bean, and Gapps after that was done. When I reboot I just get stuck in the Slim Bean loading screen for a while without anything happening. Tried rebooting and re-flashing a couple of times doing the same procedure - but nothing. Can anyone help me out?

do u flash the boot.img

beanbean50 said:
do u flash the boot.img
Click to expand...
Click to collapse
boot.img is in the Slim-endeavoru-3.1.0-OFFICIAL.zip file already so I thought if I flashed the whole zip it would flash the boot.img along with it, no?

No, you should flash boot.img via your computer.
Search in this forum how to do it.
Unfortunately in developer's tread for the ROM you choose it is not good explained...
Sent from my HTC One X using xda premium

BlueSingA said:
boot.img is in the Slim-endeavoru-3.1.0-OFFICIAL.zip file already so I thought if I flashed the whole zip it would flash the boot.img along with it, no?
Click to expand...
Click to collapse
Someone tell me if I am wrong but the reason you have to flash the boot.img separately is because we have not achieved S-OFF with the HTC One X which gives us unbridled access to everything.
Take the boot.img out of the rom '.zip' and put your phone into fastboot mode. Using the command line and fastboot type 'fastboot flash boot boot.img' obviously for this exact command to work the boot.img needs to be in the same folder as fastboot.exe. Otherwise just type the exact location of it.
Your phone should boot if everything else has been done perfectly.

I'll try that right away.

BlueSingA said:
I'll try that right away.
Click to expand...
Click to collapse
and:
fastboot erase cache
fastboot reboot

beanbean50 said:
and:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks, I always forget to do that myself haha

leonforthewin said:
Someone tell me if I am wrong but the reason you have to flash the boot.img separately is because we have not achieved S-OFF with the HTC One X which gives us unbridled access to everything.
Click to expand...
Click to collapse
correct...!

Okay so I went into fastboot mode, shift-right click on where the fastboot folder on my PC is, opened command prompt (previously pasted the boot.img from Slim Bean to that folder), typed in fastboot flash boot boot.img, fastboot erase cache and fastboot reboot. After reboot I went straight into recovery, flashed the ROM and Gapps, rebooted and now it's stuck HTC's boot screen. :/

With what unzip program you extracted the boot.img?
Try with 7zip...
One more thing- if I remember correct you need to use special boot.img for using 4.1 or 4.2 roms, because they do not work with latest hboots 1.31-39.
Search for such boot.img.
Sent from my HTC One X using xda premium

WinRAR. Okay, gonna try with 7zip.. Also, by extracting the boot.img from the zip you guys mean just to extract it or taking it out of the zip completely? Because I removed it from the zip entirely and flashed it via fastboot only.

WinRAR. Okay, gonna try with 7zip.. Also, by extracting the boot.img from the zip you guys mean just to extract it or taking it out of the zip completely? Because I removed it from the zip entirely and flashed it via fastboot only.
Click to expand...
Click to collapse
You'll be fine with WinRAR. Check back on the forum thread page of the rom you downloaded and look for a md5 sum/number. Google MD5 checker or something to that effect and check whether the MD5 checks up. Could be that a few 1's and 0's are out of place.
My other concern is the rom you have flashed. SlimBean – not tried it, I'm guessing it's a light weight Jelly Bean yeah? Are you sure that you have the correct hboot version for Jelly Bean yet? You can't force update all HOX's to Jelly Bean yet.
EDIT: Missed a bit of your post – I'm not aware of the implications but I and many others have always just copied the boot.img not cut. Obviously if you cut it and it gets zipped back up the MD5 will definitely not match. Save yourself a the head ache and download the rom again to be 100%. Delete the old.

Please see here:
theDroidfanatic said:
Here you go,
It is the NCX AOSP Kernel v13 (Latest) repacked with Seadersn's ramdisk for the new hboots, and has AMAZING Battery life. Download from here and flash in fastboot. Dont forget to flash modules from here
Click to expand...
Click to collapse
Hope this helps you.
Sent from my HTC One X using xda premium

Okay, checked the MD5 sums and they indeed didn't match.. redownloaded again, and it matched since I didn't cut out the boot.img. I'll try again.
@jorjino can you just give me a really short insight (since I bugged you enough, lol) on what is that kernel supposed to do? And do I flash those modules from fastboot as well?

You have to download the newhboot.img from my previous post, rename it to boot.img and flash it via fastboot and cmd menu your PC. That's all. No more downloads or steps.
Sent from my HTC One X using xda premium

Now I'm in a bootloop with the new boot.img... think I'm going to try a different ROM.

jorjino2000 said:
You have to download the newhboot.img from my previous post, rename it to boot.img and flash it via fastboot and cmd menu your PC. That's all. No more downloads or steps.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I don't wish to be rude but did you ignore the fact that the MD5's didn't match?

Last try with this download:
poggus said:
I confirm NCX 217 v13 run very well on Jelly Bam Rom (no need to repack, except for newer hboot you have to repack with this kernel source before flash : http://forum.xda-developers.com/attachment.php?attachmentid=1523418&d=1354254249</p> )
Click to expand...
Click to collapse
Do not forget to rename the file to boot.img.
Sent from my HTC One X using xda premium

BlueSingA said:
Now I'm in a bootloop with the new boot.img... think I'm going to try a different ROM.
Click to expand...
Click to collapse
Can you post me the link to the rom you downloaded? I'm looking on their site and there are no current files in the Jelly Bean HTC One X category. They have old unsupported roms for the HTC One X here.. http://www.slimroms.net/index.php/downloads/all/viewcategory/144-endeavoru.

[Q] Com.android.phone on boot

Hello,i was having a problem with my HTC one x tegra 3 32gb version.I rooted,put a TWRP recovery.Then try to flash with a cianogenmod.I wipe data before.Clear cache both.The flash was succesfull but when phone load up to home screen it shows this error "Unfortunately,the process com.android.phone has stopped.".Then i try to flash with a venom rom and the same problem apears again.

Same problem here.Please help..

Did you flash the boot.img?
Sent from my IceCold One X

TToivanen said:
Did you flash the boot.img?
Sent from my IceCold One X
Click to expand...
Click to collapse
Do you mean flash recovery like CWNM or TWRP?

quasar iKrime said:
Do you mean flash recovery like CWNM or TWRP?
Click to expand...
Click to collapse
No. You must extract the boot.img from the ROM zip file and put it to your fastboot folder. Type fastboot flash boot boot.img to flash it.
Then full wipe and flash the ROM in recovery.
Sent from my IceCold One X

TToivanen said:
No. You must extract the boot.img from the ROM zip file and put it to your fastboot folder. Type fastboot flash boot boot.img to flash it.
Then full wipe and flash the ROM in recovery.
Sent from my IceCold One X
Click to expand...
Click to collapse
Im Just Downloaded Slimrom.And selected install zip from sd form CWM.There is need for flash?Please help and thanks.

quasar iKrime said:
Im Just Downloaded Slimrom.And selected install zip from sd form CWM.There is need for flash?Please help and thanks.
Click to expand...
Click to collapse
Download this : https://www.dropbox.com/s/0y31poo1ki...e script.zip
1. Flash The boot.img from the rom.zip(Open rom.zip using winrar/winzip and extract the boot.img from it). Put the boot.img in fasboot folder and then boot into fastboot and run the following line in cmd:
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
2. Boot into recovery and use the super wipe script.
3. Flash the rom.zip and then gapps.zip
4. Reboot.
5. Enjoy!

@vin4yak
Thanks but he already figured it out and informed me via PM.
Now we wait for @Mvalev95 to pop up...

[email protected] i didnt flash the boot.img now i've done your steps but i have new problem but i can use the phone.The problem is i get error android.process.acore

Mvalev95 said:
[email protected] i didnt flash the boot.img now i've done your steps but i have new problem but i can use the phone.The problem is i get error android.process.acore
Click to expand...
Click to collapse
If you have followed the exacts steps which I have given, then it should work fine!
Maybe its a bad download? Download the ROM/Gapps again OR try downloading a different ROM like IceColdJelly (which I'm using) and repeat the steps again which I have given...
ROM Link : http://tunsd.de/downloads/ICJ/IceColdJelly421/aokp_ICJ422-V3.0.zip
Gapps: http://goo.im/gapps/gapps-jb-20130301-signed.zip

I am such a newb i forgot to put the gapps zip when flashing.What i need to do now to flash the rom with the with the rom and the gapps.I think i dont have to do with boot.img now.

Mvalev95 said:
I am such a newb i forgot to put the gapps zip when flashing.What i need to do now to flash the rom with the with the rom and the gapps.I think i dont have to do with boot.img now.
Click to expand...
Click to collapse
Yes you don't need to flash the boot.img again... Just boot into recovery... wipe cache+dalvic and then flash gapps.zip (Download the one which I gave you)... and then reboot!
Edit: The above way can be followed if your booting into ROM correctly... If you can't then just follow the steps again which I had posted earlier in the thread...

Everything is fixxed thanks i add only gapps and the problem persist but clear contact storage and now is ok.

Mvalev95 said:
Everything is fixxed thanks i add only gapps and the problem persist but clear contact storage and now is ok.
Click to expand...
Click to collapse
great!! :good:

[q] q. About maximus hd 20.0.0

Full wipe is obligatory
Installing Kernel via Kernel flasher is obligatory, otherwise your device won’t boot!
^^^
^^
^
in rom installation details written like this >>
THE QUESTION HERE !! FLASHING THE BOOT.IMG FOR ROM VIA CMD IS NOT ENOUGH ????

I haven't tried yet but I think the kernel flasher also flashes modules which may not be present in the Rom
Sent from my ViperX

command for boot.img work fine

Is available a FAQ post about MaximusHD 20 at this link
About it you must flash the given boot.img in the kernel flasher and perform a full wipe. Other kernels don't working on it. TWRP 2.6 is recommended because with other recoveries you may be stuck on 0% or 8% during the installation.
All is totally working with no bugs, if you have one you should retry a celan flash.
Good luck and enjoy :laugh:

frezd91 said:
Is available a FAQ post about MaximusHD 20 at this link
About it you must flash the given boot.img in the kernel flasher and perform a full wipe. Other kernels don't working on it. TWRP 2.6 is recommended because with other recoveries you may be stuck on 0% or 8% during the installation.
All is totally working with no bugs, if you have one you should retry a celan flash.
Good luck and enjoy :laugh:
Click to expand...
Click to collapse
Works fine with twrp 2.4, for some reason twrp 2.6 won't respond to touch on my hox
Sent from my HTC One X using xda premium

Whoareyou said:
Works fine with twrp 2.4, for some reason twrp 2.6 won't respond to touch on my hox
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Which version of hotboot do you have? Have you clean dalvik via fastboot after flashing?

Whoareyou said:
Works fine with twrp 2.4, for some reason twrp 2.6 won't respond to touch on my hox
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thats because you updated the phone to at least 3.17 software or higher (updated touch drivers !)
Indeed use twrp (repacked) or philz. Btw flashed it with philz myself, no issues
Sent from my HTC One X using XDA Premium 4 mobile app

@Mr Hofs
is clockwork recovery fine for installing this rom ?
or do u recommend philz recovery ??
If yes then how do i change from cwm to philz ?
Philz has a zip file whereas cwm is .img file
I installed cwm through cmdpromt
But how do i install philz through cmd ?

ronu said:
@Mr Hofs
is clockwork recovery fine for installing this rom ?
or do u recommend philz recovery ??
If yes then how do i change from cwm to philz ?
Philz has a zip file whereas cwm is .img file
I installed cwm through cmdpromt
But how do i install philz through cmd ?
Click to expand...
Click to collapse
hey mate,
1. +2. All recoverys should work. TWRP 2.6 is recommand. Some Philz users reported issues (stuck @ 0%, bootloop etc.).
3. Just flash it via fastboot.
4. Unzip it and you will find a .img file
5. fastboot flash recovery recovery.img
fastboot erase cache

ryman95 said:
hey mate,
1. +2. All recoverys should work. TWRP 2.6 is recommand. Some Philz users reported issues (stuck @ 0%, bootloop etc.).
3. Just flash it via fastboot.
4. Unzip it and you will find a .img file
5. fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks i will try this ! :good:

Guys official OTA is available in many countries. The new base is 4.18.401.2 but the Maximus is on 4.18.401.1. Also the hotboot is updated to 1.72.
I hope in a OTA update of Maxiums and not in another clean flash

I won't recommend any recovery. But philz has a fully functional one. Twrp is a good recovery but in the repacked version adb and ums does not work. And in philz it all does work. I use philz and flashed the sense 5 rom with succes. Just sharing my experience
Sent from my HTC One X using XDA Premium 4 mobile app

And as for the kernel, flashing it via fastboot is fine. the kernel flasher is a simple batch file to simplify things, but it doesn't appear to fastboot erase cache, so imo it is better to flash the boot image manually. I did and it's working flawlessly

MaximusHD 21 with base 4.18.401.2 is available, but on OTA you find the full rom, so 700MB.
I don't know if in the kernel flasher provided by football there is the wipe cache script, maybe the missing wipe can cause wifi issue.

frezd91 said:
MaximusHD 21 with base 4.18.401.2 is available, but on OTA you find the full rom, so 700MB.
I don't know if in the kernel flasher provided by football there is the wipe cache script, maybe the missing wipe can cause wifi issue.
Click to expand...
Click to collapse
kernel flasher only flash boot.img, no wipe of any kind.

wackywonderkid said:
kernel flasher only flash boot.img, no wipe of any kind.
Click to expand...
Click to collapse
An alternative is instead of rebooting your device from fastboot is to go back to hboot, load into recovery and manually wipe cache partition.

Tigerlight said:
An alternative is instead of rebooting your device from fastboot is to go back to hboot, load into recovery and manually wipe cache partition.
Click to expand...
Click to collapse
In any case if you select full wipe while installing the rom in the log you can read wiping cache so theoretically no problem. But a dev daid to me that is safer clean from fastboot

ar3na2012 said:
command for boot.img work fine
Click to expand...
Click to collapse
Yep, Flashing using cmd and erasing cache is working just fine.
See whats inside "Flash kernel.bat": nothing special but standard "fastboot flash boot boot.img"