Hello everyone,
I've recently been experimenting a lot with my p880, flashing a couple of different custom roms and kernels.
Whenever though I wanted to flash a kernel that doesn't say “anykernel verion” I ended up in a bootloop. Oppositely, all anykernel-versions are working fine.
I do look at correct smartphone model, cm version and not stock (as I'm currently running the newest cm11 nightly), make a couple of reboots when the first one's unsuccessful, read the developer's instructions and so on...
This is actually not a big deal, but I am still interested in what might be causing this...
Thanks in advance for any suggestions
Phil
No ideas? I don't need a solution, but maybe someone has a thought as to in which direction this problem is pointing.
For instance I thought that this might have to do with the way my sd is formatted...
Still would be great if anyone can think of something.
All works great now changing from cwm to the newest twrp recovery.
Related
Hello guys,
I have a samsung gt-i9000 with cyanogen 10.1.3 and a few days ago I had experienced some problems, the home button stopped working. I tried quite a few things, based on the info I found on this site and others (like factory reset), but no joy.
SO I thought to myself, better reflash the ROM, but to be honest, if I do that, I might as well install the latest one (10.2.1), and so I decided to do that, but before I start I have a few questions:
I had a look around but I couldn't really find a definite answer to the following questions, so I thought I might post here.
1)Has anybody encountered any issue on the gt-i9000 with the latest ROM?
2)Can I backup all my apps, upgrade the ROM and then reinstall everything from the backup, rather than downloadeing all the apps again? I have never done that before, so I am not sure if it is possible
3)I had a look at the cyanogen mode site and found the relevant info http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd, but I was wondering something: occasionally on my phone a message appears
and asks me whether I want to update the ROM to the latest available one. I have always dismissed that, but I am thinking, can I do the upgrade from there without going through the trouble of reflashing
it (following the instructions above), or is it essentially the same thing?
4)In the instructions it says "The install guide assumes the Galaxy S is running Android 2.3.". Now, last time I have upgraded - from cyanogen 7 to 10.1 - I attempted to install directly 10 over 7 and things
went horrible wrong. I then reflashed the ROM to 2.3 and then installed cyanogen 10.1 and it was OK. DO I have to do the same thing again and install 2.3. first and then 10.2? If so where do I get 2.3 from?
Thanks
Sorry, can somebody move this under questions, just realized that this isn't the right place.
duratto said:
Hello guys,
I have a samsung gt-i9000 with cyanogen 10.1.3 and a few days ago I had experienced some problems, the home button stopped working. I tried quite a few things, based on the info I found on this site and others (like factory reset), but no joy.
SO I thought to myself, better reflash the ROM, but to be honest, if I do that, I might as well install the latest one (10.2.1), and so I decided to do that, but before I start I have a few questions:
I had a look around but I couldn't really find a definite answer to the following questions, so I thought I might post here.
1)Has anybody encountered any issue on the gt-i9000 with the latest ROM?
2)Can I backup all my apps, upgrade the ROM and then reinstall everything from the backup, rather than downloadeing all the apps again? I have never done that before, so I am not sure if it is possible
3)I had a look at the cyanogen mode site and found the relevant info http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd, but I was wondering something: occasionally on my phone a message appears
and asks me whether I want to update the ROM to the latest available one. I have always dismissed that, but I am thinking, can I do the upgrade from there without going through the trouble of reflashing
it (following the instructions above), or is it essentially the same thing?
4)In the instructions it says "The install guide assumes the Galaxy S is running Android 2.3.". Now, last time I have upgraded - from cyanogen 7 to 10.1 - I attempted to install directly 10 over 7 and things
went horrible wrong. I then reflashed the ROM to 2.3 and then installed cyanogen 10.1 and it was OK. DO I have to do the same thing again and install 2.3. first and then 10.2? If so where do I get 2.3 from?
Thanks
Click to expand...
Click to collapse
duratto said:
Hello guys,
I have a samsung gt-i9000 with cyanogen 10.1.3 and a few days ago I had experienced some problems, the home button stopped working. I tried quite a few things, based on the info I found on this site and others (like factory reset), but no joy.
SO I thought to myself, better reflash the ROM, but to be honest, if I do that, I might as well install the latest one (10.2.1), and so I decided to do that, but before I start I have a few questions:
I had a look around but I couldn't really find a definite answer to the following questions, so I thought I might post here.
1)Has anybody encountered any issue on the gt-i9000 with the latest ROM?
2)Can I backup all my apps, upgrade the ROM and then reinstall everything from the backup, rather than downloadeing all the apps again? I have never done that before, so I am not sure if it is possible
3)I had a look at the cyanogen mode site and found the relevant info http://wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd, but I was wondering something: occasionally on my phone a message appears
and asks me whether I want to update the ROM to the latest available one. I have always dismissed that, but I am thinking, can I do the upgrade from there without going through the trouble of reflashing
it (following the instructions above), or is it essentially the same thing?
4)In the instructions it says "The install guide assumes the Galaxy S is running Android 2.3.". Now, last time I have upgraded - from cyanogen 7 to 10.1 - I attempted to install directly 10 over 7 and things
went horrible wrong. I then reflashed the ROM to 2.3 and then installed cyanogen 10.1 and it was OK. DO I have to do the same thing again and install 2.3. first and then 10.2? If so where do I get 2.3 from?
Thanks
Click to expand...
Click to collapse
1) Didn't use CM, been on OmniROM
2) You can use Titanium Backup
3)Yeah, you could do that, update it via CMUpdater
4)Just before you install a ROM with a higher android Version, always wipe /system partition.
cool thanks!
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.
hi, i got my hands on an i9000, i've been trying for several days now to flash cm11 or any other kitkat rom on my device, but nothing works, i used mackay, semaphore and a few other kernels but nothing seems to work. cm9 runs fine, but any higher version wont flash
doe anyone here know how to resolve this?
i alteady checked tis tutorial but none of the steps helps
http://forum.xda-developers.com/showthread.php?t=2434225
thx in advance GreeTTz Kevin
Hello guys,
Firstly, I would like to point out that I'm very much a newbie in terms of customizing phones (rooting,recovery,flashing ROMs etc). However, after much research, I decided to flash a ROM on my S3 Mini i8190n. The ROM I used was CM11 4.4.4 Kitkat. I pretty much followed the flashing process down to a tee, but I've encountered a significant problem. My phone starts up and then the animation comes on, furthermore, nothing happens after this, it's just a continuous animation. The animation is new to me, so I'm guessing the ROM partly flashed ok, but I don't understand why my phone sticks at this point. I'd like to point out that I have tried wiping data/dalvik and factory reset to no avail.
If you guys could assist me with this problem, I would greatly appreciate it.
Many thanks,
Pinda
RESOLVED
Hello guys,
I'm surprised I haven't received any responses from the experts on this site, but I understand sometimes threads go unnoticed.
Just an update, after a stressful week trying to fix my phone, I finally managed to restore it back to the stock ROM. I still don't know what cause the start-up animation to stick and constantly loop, it's a mystery to me. However, I finally managed to flash the stock ROM via Odin after downloading the official firmware from Samsmobile. It was such a relief seeing the green 'PASS' sign and seeing my precious S3 mini boot up, it was blissful seeing something other than the boot-up animation on repeat. The whole ordeal has made me realise that flashing custom ROMs etc just isn't worth it, especially if the handset you own is pretty decent anyway.
Just a quick question for you folks, a lot of forums mentioned flashing a pit file with the firmware on Odin and that's what I did to successfully restore my phone. However, I am still quite unsure what the pit file did, can anyone shed some light on this..
Good afternoon
I would just like to say that my phone is still running smoothly, so I think the official stock firmware is running ok without problems. However, I've noticed that my phone still has CWM recovery installed despite flashing the original firmware for my variant, is this normal? Seems strange to not have root and still have CWM on my handset....
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.