I started with a CM12 ROM and everything was looking good, but I decided I wanted to try a different kernel, so I made a backup and downloaded AGK and Nuk3rn3l:
http://forum.xda-developers.com/htc-one/development/kernel-agk-lollipo-v1-0-t2945268
http://forum.xda-developers.com/showpost.php?p=56831059&postcount=3
I downloaded both, since there seemed to be mixed reviews for each of them. First I installed AGK, then when that didn't seem to work, I installed Nuk3rn3l (without any wiping in between; mistake?). They both caused the phone to boot up and stick at the CM boot animation forever. I figured I was safe with my backup, so I just wiped and restored, but that didn't fix anything. Then I wiped and installed the CM12 zip I still had on the phone. That still got stuck at the boot animation.
What's causing this? Evidence suggests this was brought on by the kernels, but I thought that the kernel was overwritten when ROMs were installed or restored. Is that not correct?
So can it be fixed? And can it be fixed without losing everything on my phone?
Now that I'm home, I have more flexibility in my options. I got the AGK kernel with the Aroma installer, which was kind enough to inform me that that kernel wasn't made for Sprint. Who knew?
I just got the Elite AOSP kernel (ostensibly for Sprint) and tried flashing that:
http://forum.xda-developers.com/sprint-htc-one/development/kernel-elite-kernels-t2961835
So far, still not looking great.
I also grabbed Nuk3rn3l from the Sprint CM12 thread:
http://forum.xda-developers.com/showpost.php?p=56833611&postcount=3
I'll give that a go in a minute.
If there's something I'm doing fundamentally wrong here, I'd love to be corrected!
No luck with Nuk3rn3l. I gotta be doing something wrong...
Related
Hey guys; i'll try to provide you with all the information but honestly i'm not 100% on all of it so try and be patient.
I'm trying to go back to SuperE from Froyo by Laszlo which was absolutely killing my battery without me even using it. However, every time i flash it (and i wipe everything) after it goes past the G1 screen it just resets again.
I'm not sure if this is maybe because of the new kernel (2708) which i'm PRETTY sure i have, but am not 100%. I do know that i have one of the new radios though.
Would the kernel be causing the problem? If so how do i downgrade?
I hope you can help me out!
Thank you!
Q: Can you mention step-by-step what did you flash? And confirm the exact setup before flashing. I believe you mentioned your radio is 2708.
Powered by Android
Thank you for replying. I'll definitely try.
I'm back on FroyoByLaszlo-int2.1 because i couldn't successfully flash either Super D or Super E.
My Radio is 2.22.28.25
Kernel version says 2.6.35.10 - froyobylaszlo
Basically i did what i always do. I wiped everything, first by flashing the "all-wipe" and then going back and wiping it all manually.
Then i flashed the appropriate gapps, followed by the ROM. Rebooted afterwards, but every time it gets passed the G1 screen it reboots.
The only thing i can think of is incompatibility with the kernel but then again, i don't know crap, so that's why i'm asking
Yep, most likely it is indeed the incompatibility of the kernel with the radio.
I'd try flashing the ezBiffTestKernel20101106-2708.zip after the ROM+GApps.
Just use Google to find the kernel.
Powered by Android
The battery drain could be becos of the new kernel. Try installing the 35.9 kernel from ezterry (the one he had for CyanogenMod 6.1 2708) It is working good for me, the battery last for a whole day.
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
My Phone was on 4.2.2 (12B). It was rooted.
I wanted to go to 26A bootstack.
Here's what I did:
1. Installed flashify.
2. Installed TWRP recovery and rebooted in to recovery.
3. Chose install and selected the xdabbeb_vs98026a_bootstack.zip and then rebooted.
Since then all it does is to power on - shows LG logo - a few seconds later reboots again.
What should I do now please?
FIXED IT Thanks to @undeadking for his response in another thread. I followed it and now Paranoid android running on my G2.
Glad you got it running!!! There's a few things that I ALWAYS keep in a separate folder on any phone- 12B,24A,and now 26A xdabbeb's bootstack/radio zips, ROMs that I know will boot on one or more of them, supersu 2.16 zip, TWRP 2.7.0.1/2.8.0.1 (dr87's custom builds), and a stock ROM backup... Might seem a bit excessive to some people but these items(along with the "search" option on XDA) have saved/helped me more then once and may be beneficial to you as well... Anyways glad you are up and running now- check out PlainAndy 14.2 by @Snuzzo its super smooth, stable, and more vanilla instead of customization heavy--you would like it better than Paranoid Android.
@undeadking
Good to see you helped out! Feels good? Either way, what I suggest is just keeping a backup of a rooted ota and a backup of your previous ROM. No need to switch back to a different baseband and confirmed to always boot.
Yeah ive been helped/taught a hundred times by the more experienced in the forums and I know what a panic one can get in when something goes wrong haha but yeah always try to help when I can.
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
forvrknight said:
Quick question. Is there any reason flashing cm13 on a 20p phone would cause issues? I had to get a refurb due to boot loop and tried to load cm13 on it but ended up with no sound card. I got that fixed by kdz to 20o and then updated to 20p but I don't really like the stock ROM much and am wary about flashing CM again because the back order on this phone is ridiculous.
Click to expand...
Click to collapse
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Wolf2231 said:
What do you mean "because the back order on this phone is ridiculous"
OK let me revise
First, you unlock bootloader, and "unlocked bootloader" appear when you turn on your device.
Next, you installed TWRP custom recovery.
Then you boot into recovery (TWRP)
Before installing (flashing) CM you first wipe your previous OS. In TWRP you Advance wipe (delvak,system,data,cach) and internal if you already backed up your data.
After completely wiping. Now you install (flash) latest CM13.
Then, after flashing complete reboot system. Don't install Gapps yet. Every thing should be working fine.
Last but not least, Gapps you install, it might be tricky because if you try to install an app that has an alternative pre installed. some problems could appear. For me Camera and keyboard the stop working.
I'm a noob myself. But if there would be a problem between a software and a hardware. I would blame it on the kernel.
Or the CM file you downloaded is corrupted.
Re download it and check the md5.
Please keep me updated. And any further Q.
Give me a like if this was helpful.
Click to expand...
Click to collapse
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
forvrknight said:
The backorder for a refurbished is about a month. My 1st G4 was rooted and running several roms but mostly cm13. It randomly boot looped after a flash and in an attempt to fix it used the LG flash utility and a 20n kdz. When it would boot it would be so laggy that it was unusable. Managed to look at logcat and saw errors related to asound device missing. Turned that phone on for a replacement at a t-mobile store and it just arrived.
The new phone came on 20n I think and I unlocked, rooted, and flashed cm13 again. After about a day I rebooted for something and got the exact same problem. After some searching I managed to find that kdz to 20o would fix it and it did. Not really sure but was thinking that maybe some filesystem change or something might have happened between versions that didn't play nice with cm13.
Not really sure this isn't my area of expertise or anything so just guessing. I'd rather not go through all this again so figured I'd ask if anyone knew any reason that cm13 could have caused it or if I'm just unlucky.
Thanks for the response though I'll make sure to double check the md5 I'm really bad about that lol
Click to expand...
Click to collapse
I see you went through a lot. Well the possibility of one of us getting this problem is low, under same consequences. Anyways, on this page, we just try to share info between each other to find the best solution. That's what its about.
Hey, thanks for sharing your experience you just added a possible problem and solution. This will be helpful for the community. About md5 google how to check it. There are really easy ways. Checking the md5 is worth it, that's for CM ROM. I believe LGUP does check for kdz automatically, since the kdz are stock.
Good luck, and don't stop sharing.