Ok can't get help from Dev's so I'm turn to you my fellow xda reader's . I flashed superevo v1 but wanted to try v2, it would get stuck at the cyanmods splash screen and loop. He said I have to update my hboot. I looked. All over in xda Google no help just more confusion. Can someone please help this noob.
Thanks
Ok problem solved thanks to skyler. I couldn't flash any other rom not sure why something to do with cm6 based roms, in order to fix that I had to flash a HTC kernel ( htc#11 or #7) then flash a none aosp based rom and presto I'm able to flash away!
Related
Hello everyone.
I recently installed pureness build 14 sp1 and xarc kernel.
Everything works fine except one thing i noticed. When I hit the reboot option I get stuck in a reboot loop.
I have to enter CWM and select power off in order to be able to start my device.
Any suggestions?
reflash the rom
check compatibility kernel with rom
This is the only problem I faced so far I think I will use shut down and restart for the moment. I thought it was some setting that I wouldn't see.
Because a lot of people are using this combination I think it is not a matter of compatibility.
Keep in mind that I am a rookie at this and this is my first experience with custom roms and kernels
first step use stock kernel, try
Can you please provide me with a link to a stock kernel?
fireillusion said:
Can you please provide me with a link to a stock kernel?
Click to expand...
Click to collapse
flash with "flash tool" in fast boot mode
http://forum.xda-developers.com/showthread.php?p=30358780
Thanks a lot. I will give it a try.
I just have to find some time to do it. :good:
Hey guys so I'm in boot loop. Yes I know there are many guides all over saying how to fix it but I have tried many of them and they didnt work.
What happens is I start the phone, it shows the boot image and then restarts after a time.
I can boot into the Recovery mode by spamming the back button when the Logo comes. And can install zip files from the SD card.
I also have tried flashtool to restore it to stock but when i try flashing it detects my device "Device connected in flash mode" but when i try toflash it, it gives an error "Error flashing. Aborted".
I tried many many room whit kernels but stuck on bootloop every time, no way. I have never seen this problem before. Maybe bricked bootloader ?
I tried to relock the bootloader but doesnt help either.
Any help?
Ok, since you can boot into recovery can you flash you ROM.zip and try to boot into ROM? I also need some details:
- ROM you were using
- Kernel you were using
- How you got bootloop
Flashtool should work, try to recover using flashtool.
僕のLT18iから送られてきた
popthosegaskets said:
Ok, since you can boot into recovery can you flash you ROM.zip and try to boot into ROM? I also need some details:
- ROM you were using
- Kernel you were using
- How you got bootloop
Flashtool should work, try to recover using flashtool.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Before this happened i was using Ultimate HD 4.0 and Vengeance kernel ayame. The telephone was crashed and i didnt any backup. I tried to upgrade it to android 4.2 or 4.1 and the probleme begin I relocked the bootloader but doesnt help. I flashed it but doesnt accept any firmware, show Error flash bla bla bla Flash aborted. tried almost roms and kernels but doesnt help. I can install rooms and flash kernels, and boot up to recovery but after that is just stuck on boot animation or bootloop.:crying::crying::crying:
During the upgrade to JB, did you flash the kernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.
僕のLT18iから送られてきた
popthosega-skets said:
During the upgrade to JB, did you flash e ä'ökernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.9
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Thank you very much but i need steps . Plzz
Best regards
popthosegaskets said:
During the upgrade to JB, did you flash the kernel that came with it?
I assume you wanted to update to CM10/10.1? Vengeance Kernel is not compatible with JB. You need to flash UHD4 back to /system partition if you want to stick with UHD or flash the boot.img that came with the JB ROM.zip.
Do a clean install. Your phone should be working again if you do the steps correctly.
If you still have problems, you can reply to this thread or send me a PM if you wish to be more private about it.
Regards, 日焼けさん.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Sorry but i want tell you that the last i tried is this but doesnt help, stuck on boot animation. I gone be crazy.
OBS !!!!!! When i install rom and not working whit me i look on SD on pc if the installation files are there but nothing just the rom zip. I changed the SD but the same happened
Having issues realted to this one. Here's my device info. Hope it helps.
Device:
-> never been modded.
-> all stock rom.
-> stuck on a bootloop due to bluetooth.
It doesn't even have a recovery mod. So I'm pretty much stuck.
Can you help me out? And another thing, sorry for bringing this
old topic back. Haha.
Hi,
I have been trying to install this http://forum.xda-developers.com/showthread.php?t=2383768 ROM for about a few hours now but don't seem to get it work on my Arc S (LT18i) I followed all the steps mentioned in the thread and everything installs correctly. The lupus kernel loads properly but after that I am stuck at a black screen showing nothing. Could anyone please help me with this.I event tried going back to stock and then rooting and then installing the ROM but the same black screen is displayed again.
Thanks and regards,
Amit Mirchandani
EDIT:
I was able to make the ROM work by installing the boot.img kernel inside the zip file. But it is not loading for me with the LUPUS kernel downloaded from here http://forum.xda-developers.com/showthread.php?t=1867265&highlight=lupus. Please can anyone help with this
EDIT:
Okay I was able to get it to work with lupus as well. I guess I downloaded the wrong kernel which was of ICS and was able to get it to work once I flashed the JB kernel. Sorry for bothering anyone.
Thanks and Regards,
Amit Mirchandani
Hi there,
Over the past few days I've been "messing" around with rooting my One X, starting with Cyanogen and then I was stupid and soft bricked it trying to put on a wrong ROM. I managed to sort all that out with a recovery and went back to Cyanogen.
I've just put Paranoid Android 3.10 on through the method that a youtube user "cursed4eva" followed which was the "standard" process as I was going from CM of which was just a "fastboot flash boot boot.img" in fastboot, then using recovery install the ROM and GApps from zip.
It's all working fine, apart from the WiFi won't turn on when you click the button in settings it flashes blue then back to grey.
Googling around it appears you have to repackage the ROM with a new Kernel (Seen XM 295 was meant to be good) So I have that downloaded but now I can't find any tutorials on how to go about actually repackaging the ROM for PA3.10 or XM295 with a One X.
Any help with getting this sorted or any other methods of getting my WiFi working would be great.
Thanks,
Tom.
You dont repack a rom......only repack the kernel. After that flash it. Google on nibble repack
Thanks for the reply,
my bad on the terms as mentioned I'm fairly new to the rooting of phones, Ok that site has finished,
Just to confirm, you use the new image file it's made, move that back into the PA zip file then do the normal process to install the ROM to the phone?
Ah i think you forgot to flash the boot.img from the rom.zip
The boot.img won't be flashed with the rom install. It needs to flashed via fastboot
Thanks for the reply,
First time around I flashed the boot image across I just wanted to ask if you move the "new boot.img" the website has made with the repackaged kernel into the paranoidandroid zip file or if you keep the standard one in there.
I'm aware I need to fastboot flash the new image across just not sure if it's also needed in the zip on the phone or not.
Ah no not needed
Thanks for all the help
Hi again.
It's all finished and the WiFi still doesn't want to turn on fully. To go with it Bluetooth also now doesn't want to turn on xD
Out of interest do you have any recomendations of kernels to use that can fix this issue?
Never used aosp roms. Check the thread OP. If the delivered boot.img won't work properly it should say something about in there.
It says repack with any aosp kernel. So repack the boot.img and flash the new boot.img, then flash the modules.zip via recovery of the kernel you repacked it with.
Did you try this one too ?
http://forum.xda-developers.com/showthread.php?t=2174855
Whilst trying to install the zip for that one it gets up to
"installing update..." then errors with:
"assert failed: getprop("ro bootloader") == "1.28.000" and repeats for the numbers from changing for 1.28, 1.31, 1.36 and 1.39.
I assume that is something to do with the bootloader rather than the rom?
on the bootloader screen all I can see is the HBOOT-1.72.000 etc. so not quite sure about that :/ that is with the 3.65 version on the link, attempting 3.99 now if all else fails will just go back to Cyanogen for now
Within the thread for the rom I was trying to start it didn't mention it, a few posts did which was met with repackage the kernel and that the XM 295 one worked for them.
Ah then you have to edit a file in the meta inf folder of the rom.zip.....hold on i for it somewhere
http://forum.xda-developers.com/showthread.php?t=2478409
Easiest is to remove for instance 1.39 and replace it with your bootloader version
Edit - Feel stupid, sorry didn't full read it xD HBOOT version is my bootloader.
Thanks once again.
Sorry for the double post but would just like to say a big thanks for all the help.
Phone is now running Paranoid Android 3.65 with working WiFi and signal So once again a big thanks
TrueSlawter said:
Sorry for the double post but would just like to say a big thanks for all the help.
Phone is now running Paranoid Android 3.65 with working WiFi and signal So once again a big thanks
Click to expand...
Click to collapse
Nice ! Good news then. Well enjoy
Hi,
Can anyone please extract Kitkat boot.img from the factory image for Deb from Google?
I am stuck in bootloop after installing franco kernel r8. :crying::crying:
I have unlocked my bootloader, rooted and installed CWM recovery and currently on Stock Rom 4.4.
i tried wiping cache and dalvik but still stuck in bootloop. Before hitting factory reset i want to try reflashing stock kernel from Google factory image.
So can anyone please extract boot.img from the factory image (4.4 KRT16S for razorg)and share it with me ?? i will be grateful forever.
please help me.
--- Sorry i posted this is dev thread. Please move it to QA thread.
I'm uploading the files. Sorry I have bad connection
When I finish I will put the link .. Cheere. Up
Here we go .. I hope it will fix your problem
https://www.dropbox.com/s/aki1k01o2xvm5m5/krenal multi
murad052 said:
I'm uploading the files. Sorry I have bad connection
When I finish I will put the link .. Cheere. Up
Here we go .. I hope it will fix your problem
https://www.dropbox.com/s/aki1k01o2xvm5m5/krenal multi
Click to expand...
Click to collapse
Thanks a ton !! It worked like magic. I will be forever grateful to you Sir.
here is the same boot.img i have repacked as a rar file.
Devs can use it as a backup option (and put it in the all-in-one-place thread) to people who bootlooped their device on flashing a bad/wrong kernel.
Devs. Please close this thread as it is solved.