Hello guys,
Im not new in rom development. But my p9 makes not that i want. Its very difficult to find out the problem.
if i check the files the kernel wont boot up. The other side the file construction in updater script is bad and it wont boot.
really strange, if twrp says all is ok, but it doesnt boot. I need some help, maybe we get together the next rom.
http://txt.do/584mg
All fixed and working.
How you fixed it?
Related
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...
Hi,
Sorry if this seems like a dumb question - A bit confused from reading up all the info on upgrading to ICS on the p990.
Im running a volk custom kernel, and CM 7.2 - OS Version 2.3.7.
Whats the "best" way to upgrade to the new ICS? I tried running the LG software update but it doesnt go too well, fails after it tries to detect phone - even though it detects it initially.
Can I get the release that LG released with my setup?
Please advise.
Thanks!
Same situation here. I'm on official cm7.2 and would like to upgrade to ics. But don't think that useing official lg update tool is so good idea - it might brick your phone. It won't update to ics because you aren't running the official GB rom so lg update tool won't upgrade (correct me if i'm wrong).
Maybe the AIO tool would do the trick.
Anyways, people we need your advice!
LOL, use NVflash ICS rom like TG.
for me the best way is using the toolkit to install new partition, new bootloader and recovery
than boot into recovery and flash the room as usual
Thanks Wakata.
Much appreciated. I have tried downloading the toolkit but its always corrupt.. ill download the 7 zip format.
I take it that I will need to back everything up and wipe everything, install new partition, boot loadder and recovery(CWM??), then flash with the new rom and kernel?
I've also used the All-In-One P990-Toolkit to upgrade to ICS.
You can use 1. to backup your internal SD in case you need it later.
Then hit 4. to change the partition layout and after that 8. to flash the new unlocked bootloader. That's all.
Thanks again
Slight problem - I downloaded the 7z file, and extracted them, but cant seem to run the .cmd file? What am i doing wrong here?
scratch that last question.. for some reason the files are corrupt when i download them.. grrrr.
So I followed the instructions, and suprise suprise, I get an error -
Nvflash started
nvflash configuration file error: file not found
An error occured. Read above lines for details
Help please
Nevermind, I had a fiddle and flashed ics 6.0.xxx.. lets see how it goes. Hopefully I havent bricked it lol
Sorry, problem.
I first tried option 1, then 4, then 8.. after its all done, no errors - I boot the phone, and its stuck on the red LG logo.. I've left it there for around 10-15 mins with no luck? Help!
Haha, actually I figured it out. I did realise I didnt have a ROM! Doh! lol rookie mistake.
I downloaded this rom and kernel(1.4ghz OC) and its running pretty well, no bugs so far(touch wood)
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.
This is kind of frustrating. I'm trying to unbrick my device. I have my boot loader unlocked and all that stuff
but I am having trouble installing a custom ROM.
When I want to install A custom rom TWRP gives me error 7. I looked at how I can fix it and when I do I still get. TWRP runs fine and I can get ADB to work I have the right equipment but I'm always running into
problems when I try to install a custom ROM, It just never works.
i'm mainly looking into trying to create a flash-able ZIP with my update.app file and if that doesn't work then try to install a custom ROM. But i'm really stuck and my phone has been in soft brick mode for 2 days now.
does anyone have a different/easier method of unbricking.
I cant really be stuffed about writing about all my problems so if you need to know something please ask in comments.
So lately I made an edit to my build.prob file. I wanted to make my device think it's a Note 9 so I can get the Galaxy Skin Fortnite (I'm a stupid brat, I know). I restarted it and noticed, that it won't boot. No problem I thought. I just flashed the same rom again I was running on (Stock Rom) but I got this weird sw rev check fail fused 2 binary 1 error
Then I tried installing several custom roms through TWRP but guess what? I got a bootloop.
I think it's because there's a problem with the Kernel or something like that. Still don't know what this exactly is and how important.
Please don't tell me, that I'm stupid, because I already know that. I just want to get some help by some pros!<3
Update
SoraCreates said:
So lately I made an edit to my build.prob file. I wanted to make my device think it's a Note 9 so I can get the Galaxy Skin Fortnite (I'm a stupid brat, I know). I restarted it and noticed, that it won't boot. No problem I thought. I just flashed the same rom again I was running on (Stock Rom) but I got this weird sw rev check fail fused 2 binary 1 error
Then I tried installing several custom roms through TWRP but guess what? I got a bootloop.
I think it's because there's a problem with the Kernel or something like that. Still don't know what this exactly is and how important.
Please don't tell me, that I'm stupid, because I already know that. I just want to get some help by some pros!<3
Click to expand...
Click to collapse
I think it's because I've flashed older roms, but I was already using the latest one. So it won't let me go back. Right now I'm downloading the latest stock rom. I'll try to flash that one. If it works, I'll let you know :good:
[FIXED] Update
SoraCreates said:
I think it's because I've flashed older roms, but I was already using the latest one. So it won't let me go back. Right now I'm downloading the latest stock rom. I'll try to flash that one. If it works, I'll let you know :good:
Click to expand...
Click to collapse
Got it to be working again! This means the error mentioned in the main question is just because you installed the wrong/ too old rom!