Related
hey. just now i unlocked my device and want toflashe rom cm10 in this forum,i didnt do root ,i flashed the kernal faux 0010b4 and flashe the rom and the gapps,i did all this ,iand not its in boot loop alot of time,i tried to restore to hwat i backed up- ,and still in boot loop... what i can do? pliz help.
Can you get into recovery? You can charge it there.
Sent from my HTC One X using xda app-developers app
you sure?
you sure in that? because i dont see red light when i am in recovery...
bardahan123 said:
hey. just now i unlocked my device and want toflashe rom cm10 in this forum,i didnt do root ,i flashed the kernal faux 0010b4 and flashe the rom and the gapps,i did all this ,iand not its in boot loop alot of time,i tried to restore to hwat i backed up- ,and still in boot loop... what i can do? pliz help.
Click to expand...
Click to collapse
Did you repack the kernel for the ROM.
Dude, I got to where you are a couple of weeks ago and I panicked. 10 minutes later I was sorted.
Download the rom and kernal again (prolly best to use a kernel already packed for the ROM you want to take a variable out of the equation). May I recommend Tripndroids CM10 ROM and the kernel that comes with it. This will be fast to flash before your battery dies and I am very familliar with flashing it so I'll be able to help more easily. You can always start again when you've charged. Alternatively, Use the boot.img from any ROM you like. Stick to a matching ROM and kernel for now as it saves the repack and a couple of steps in flashing.
Copy ROM zip to your SD (using ADB is easy: adb push yourfile.zip /sdcard/yourfile.zip)
Extract the boot.img from the rom zip (on your PC)
Go into fastboot and connect USB
fasboot flash boot boot.img
fastboot erase cache
Full wipe in recovery
erase cache and dalvik in recovery
Flash the ROM in recovery
Reboot - First boot will take a while.
very ty
hey, ty for the good explain ,now i tried another kernal and its worked,mabey the kernal just was fail,but now the phone is work ,very ty.
just 1 question,which rom is good and stable? and if good life battery that you can tell me? because i saw all the roms in this forum and i dont know which one is the best
ty for the help
bardahan123 said:
hey, ty for the good explain ,now i tried another kernal and its worked,mabey the kernal just was fail,but now the phone is work ,very ty.
just 1 question,which rom is good and stable? and if good life battery that you can tell me? because i saw all the roms in this forum and i dont know which one is the best
ty for the help
Click to expand...
Click to collapse
That's very subjective but I like TripNRaVeRs CM10 Endeavour Unleashed. It comes with a completely stable 2.x kernal and there is an almost totally stable 3.x kernel and an experimental (not at all stable) 3.x kernel. All cna be flashed without the re-pack.
BTW. If you ever get to panic stations again you can charge by going into fast boot and choosing power down. Then you can charge for a while before starting again.
BTW agian, there is a thanks button. You could click it if you wanted!
if you want to use other kernel (faux, ncx) than the one supplied in rom you should always repack it using online repacker http://nibble.cc/repack/
if not you will be 90 % stuck in bootloop
I am currently running Leedroid and I sometimes switch to Paranoid Android just to see how things are developing there. Great rom but I cant do without sense camera and like the decent weather app with all its animations.
Back to reason, sorry, I cant change my kernel on neither rom. Just gets stuck on boot animation/loop. Knew problem because I used to be able to change kernels but now just cant. Any idea's to why. Much appreciated - I feel handicapped...
Well, did you repack the kernels AND flash modules?
tomascus said:
Well, did you repack the kernels AND flash modules?
Click to expand...
Click to collapse
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
veroby said:
Cheers for quick response. :good:Yes, as I said I used to be able to try different kernels but just stopped last dozen attempts. Have tried repacking boot image several times, via online repacker but had no joy. Am i doing something wrong.
Click to expand...
Click to collapse
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
tomascus said:
You put the original boot.img in the source img, correct?
Then repacked, flashed the kernel, erased cache and then rebooted to recovery to flash modules?
Click to expand...
Click to collapse
Correct. I have tried erasing cache via command line and I have tried erasing cache via cwm as well. Still no joy
Actually because of desperation I have tried everything in different orders as well. Example- flashing boot image before after flashing kernel. Still doesnt boot and eventually after long wait just loops. This problem is with both roms.
Stock kernel works right?
tomascus said:
Stock kernel works right?
Click to expand...
Click to collapse
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
veroby said:
Yeap, have had to restore to backups everytime. And they function fine but even tho I am a believer in "if it aint broke don't fix it", I cant help but try and fix wat aint broke. If you know what i mean.....
Click to expand...
Click to collapse
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
KaiseRRUby said:
Maybe a dumb answer, but i had the same problem. Do you flash in the right order? Do you flash your kernel before or after your rom flash? And you're flashing using fastboot?
Click to expand...
Click to collapse
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
veroby said:
No not dumb, i really appreciate attempt in help. As to right order, have tried right order, fastboot flash boot boot.img with repack and original image to kernel but nothing is working. Just will not allow change kernel. Have tried re-flashing boot image after flash kernel as well. Have tried erasing cache partition with wiping dalvik cache together but no go. Have tried erasing nothing but still boot loop. Any ideas:crying:
Click to expand...
Click to collapse
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
ARHD 11.1 jellybean smooth and sense camera full package
tomascus said:
doesn't matter what order you flash the boot.img, as long as you flash the modules after you flash the ROM.
btw, try another ROM.
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid ( i know you said try another rom but hadnt thought it to be necessary because I was having same problem with Leedroid and Paranoid Android jellybean), kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...:crying:
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
KaiseRRUby said:
So this is your order:
- Backup
- full wipe
- flash rom
- flash kernel
- flash modules
- restart
?
Click to expand...
Click to collapse
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
veroby said:
Ok here's what I did, full wipe, Flashed knew copy of Leedroid, kinda custom the rom a little with mods and tweaks. Got a bit ahead of myself because I then fastboot faux kernel boot image and flashed the modules. Gutted BOOt-LooPED...
Have gone back to my backup Leedroid. At least I know its not the full wipe. Any more ideas welcome.
Forgot to mention I did not repack the boot image until after boot loop. Still did not work.
Click to expand...
Click to collapse
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
KaiseRRUby said:
Well, the best way to do it as far as i know is:
-boot.img flash (the one included in rom)
-wipe
-flash rom
-reboot
-wait for 10 minutes
-rebooten (full reboot again)
-reboot to fastboot
-boot.img flashen (custom kernel)
-modules flashen (custom kernel)
That 's how things work by me, you can try this?
Click to expand...
Click to collapse
Yeah understand, I used to be able to just fastboot flash kernel boot image, flash kernel modules via cwm and bobs ya uncle. Done. But no more. Guess I'll have to wait until i jump ship and update firmware to 1.28 for JB roms and re-format or something. Cheers anyways..
Extract Rom and grab the boot.img
Make a Full Wipe (Factory Reset,System,Cache,and Davlik Cache)
Install ROM
Fastboot flash boot boot.img
REBOOT
Enjoy!!!
With these instructions *i've never flashed a rom before* I should download the rom, extract the boot.img where I have the fastboot.exe on my computer, do full wipe, put the zip file on my sd card and install in recovery, reboot and go into fastboot mode and flash the image, and then reboot again right? Or am I missing something? Sorry, as I said i've never done this before.
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
donhashem.dh said:
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Click to expand...
Click to collapse
atonz said:
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
Click to expand...
Click to collapse
Thanks for your help. I actually went ahead and tried mine first, to see because i'm impatient and it worked totally. Thanks everyone!!!
Ok, I'm having issues with this installing ROMs/kernels.
I entered fastboot
I flashed the boot.img for the kernel I want
I toggled to hboot
I went into recovery (twrp 2.2.0)
I did wipe -> Factory Reset, Cache, Dalvik Cache, System
I installed the zip for ROM I want to use [found here]
I flashed the zip for the kernel I want to use (to install the libs) [found here]
wiped dalvik/cache again
reboot system
Now my phone just bootloops. Not sure what I did wrong.
I should mention I did get it to boot once back when I first installed the ROM because I did a normal reboot not a reboot into fastboot (was doing the install the ROM then the boot.img approach at the time) and hadn't installed any boot.img (still had the stock) but ever since I overwrote it all i get is bootloops.
Also, I even tried the same steps using the boot.img included with the ROM as opposed to the other one.
To make things worse, backups are almost useless because with the phone being S-ON even if the boot.img is being backed up, it not getting restored. A point made extremely obvious by the fact that it still bootloops after restoring my backup.
I am currently running the RUU but am hesitant to try and install any ROMs without some idea of what I did wrong.
Any help is appreciated.
-----EDIT------
Ok, I think the problem was the recovery I used. I installed the CDMA TWRP from the OneV tool, and one linked in the cdma development thread and a couple CWM version found there as well. But what seemed to work was getting TWRP straight from the source. After running the RUU I installed version 2.3.1.0 and repeated the steps using the boot.img included in the ROM and it worked. If I'm feeling adventurous later I'll try my luck with the other kernel lol.
Noob question, again.
I successfully rooted my One V, GSM. I want to flash this custom ROM
http://forum.xda-developers.com/showthread.php?t=1640995
What kernel i should i use, or do i need to flash kernel at all? And does that ROM have languages, i want to use finnish. More noob questions: In TWRP, do i make a nandroid backup, and is that i can flash the stock ROM if i am not happy with custom ROMs?
For Suprimo ROM,use this kernel
boot-TK-USB-201212251804.img from
http://www.mediafire.com/?e1chs7tzcsstc.
Its the sense kernel,works with sense ROMs.
Yes,flash the TWRP recovery and make a backup of the stock ROM before flashing anything.you can restore it whenever you like.
And yes,you will have to flash the kernel or your custom ROM won't boot.
Sent from my One V using xda app-developers app
mihirengg19 said:
For Suprimo ROM,use this kernel
boot-TK-USB-201212251804.img from
http://www.mediafire.com/?e1chs7tzcsstc.
Its the sense kernel,works with sense ROMs.
Yes,flash the TWRP recovery and make a backup of the stock ROM before flashing anything.you can restore it whenever you like.
And yes,you will have to flash the kernel or your custom ROM won't boot.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Thanks, i try it.
putkimonitori said:
Thanks, i try it.
Click to expand...
Click to collapse
And i selected "BACKUP" on TWRP, and backed up System, Boot and Data, Recovery and cache, is that enough, can i now proceed to flashing custom ROM and kernel? Does it matter what order i do it, first kernel or custom rom? Sorry for stupid questions but i am quite nervous so i need to confirm that do i do stuff correct, my first Android phone and now cannot afford a new so don't want to brick it! =)
And can i use Hasoon2000's All In One kit or is this done in TWRP to flash kernel, and how i backup the original kernel, or is it even possible? As you can see i am a quite big noob.. It's better to ask than to be sorry, right? So that should be a good kernel for this? Should i be in recovery mode, in bootloader or what if i use the All In One kit?
I prefer flashing kernel before flashing ROMs.the boot.img is backed up.if you open the backup,you will find the boot.img.
Yes,the toolkit will flash the kernel.
Sent from my One V using xda app-developers app
mihirengg19 said:
I prefer flashing kernel before flashing ROMs.the boot.img is backed up.if you open the backup,you will find the boot.img.
Yes,the toolkit will flash the kernel.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
So if i did backup those things what i said in earlier post, should i be fine? System, boot, cache, data, recovery are backuped in TWRP using the "Backup" menu.
Should i be in bootloader when i flash the kernel?
E: Does it take long to get forward from the boot screen (thats coming after that HTC queitly brilliant logo), now my phone is in this text which says "htc Desire HD" and "beats audio" in bottom of screen, i did flash the kernel.
E2: Never mind, it just took time, first time always bit slow huh? I find this funny that when i boot my phone i get "HTC Desire HD" text, although it is One V. Now just waiting that it unlocks my SIM card and sets up my phone. Glad to see all went fine. =)
This is probably a noob question, but is it safe to restore a kernal backup with a kernal manager/flasher? I'd assume most
would recommend a dirty flash, or restore dtbo partitions. Thank you!
Adelino80 said:
This is probably a noob question, but is it safe to restore a kernal backup with a kernal manager/flasher? I'd assume most
would recommend a dirty flash, or restore dtbo partitions. Thank you!
Click to expand...
Click to collapse
Assuming you backed up the kernel on the same firmware/ROM version you're running now, should be fine. I've switched between stock kernel and custom kernel (and back) this way several times. I use EX KM instead of Franco, same thing though.
terlynn4 said:
Assuming you backed up the kernel on the same firmware/ROM version you're running now, should be fine. I've switched between stock kernel and custom kernel (and back) this way several times. I use EX KM instead of Franco, same thing thoug
Click to expand...
Click to collapse
terlynn4 said:
I backed it up stock kernal, and am still using stock Oxygen OS since my phone is my daily driver, and I need it to work. Can i just flash the Stock_Op9pro_30_boot.img and restore said partitions that way, since im still on A11? and if so do i need to wipe my dalvik cache, etc, and then flash boot.img, dtbo, and vendor_boot imgs to both slots?
Click to expand...
Click to collapse
terlynn4 said:
Assuming you backed up the kernel on the same firmware/ROM version you're running now, should be fine. I've switched between stock kernel and custom kernel (and back) this way several times. I use EX KM instead of Franco, same thing though.
Click to expand...
Click to collapse
I backed it up stock kernal, and am still using stock Oxygen OS since my phone is my daily driver, and I need it to work. Can i just flash the Stock_Op9pro_30_boot.img and restore said partitions that way, since im still on A11? and if so do i need to wipe my dalvik cache, etc, and then flash boot.img, dtbo, and vendor_boot imgs to both slots?
Adelino80 said:
I backed it up stock kernal, and am still using stock Oxygen OS since my phone is my daily driver, and I need it to work. Can i just flash the Stock_Op9pro_30_boot.img and restore said partitions that way, since im still on A11? and if so do i need to wipe my dalvik cache, etc, and then flash boot.img, dtbo, and vendor_boot imgs to both slots?
Click to expand...
Click to collapse
I have not done it by flashing partitions, though I'd expect it to work. I've only flashed kernels (both custom .zips and backups) via kernel manager on A11. I don't see any reason why you'd need to flash the additional partitions unless the custom kernel (or other customizations you're using) made changes to any of those.
terlynn4 said:
I have not done it by flashing partitions, though I'd expect it to work. I've only flashed kernels (both custom .zips and backups) via kernel manager on A11. I don't see any reason why you'd need to flash the additional partitions unless the custom kernel (or other customizations you're using) made changes to any of those.
Click to expand...
Click to collapse
I see, well I was able to restore back to my stock kernel. I had made a backup prior with Franco Kernal Manager and was able to restore stock, and flashed to Arter Kernal. Thanks for the help!
Adelino80 said:
I see, well I was able to restore back to my stock kernel. I had made a backup prior with Franco Kernal Manager and was able to restore stock, and flashed to Arter Kernal. Thanks for the help!
Click to expand...
Click to collapse
If you go back to stock from arter kernel you will need to flash vendor_boot.img dbto.img and boot.img from the version you are currently on though.