phone process crash after flashing ROM - G3 Q&A, Help & Troubleshooting

IGNORE - this is a dup post of this one.

Related

Thread Removed.

Post Removed.
Add on
Post Removed.
maybe your phone not bricked
that say on cwm, your cwm cant mount everything right?
what cwm you use?
maybe your cwm doesnt support to mount ext4
because on my cm7 build, all partition will be ext4. except sdcard
have you try to format system, data, cache & sd-ext on your cwm?
now, all your partition must be at RFS again
and how you flash stock rom?
from odin? or?
Post Removed.
InMyBedNow said:
People with this phone, DO NOT FLASH CUSTOM ROMS THAT ARE MADE FOR JUST THE GTS5660 NOT THE M Model. I flashed CM7 ported by phiexz (amazing build btw) and when i wanted to flash back to stock, It bricked.
Click to expand...
Click to collapse
Sorry to hear about your issue but your assumption that you can't use other versions on an "M" is a little bit of a blanket statement. I've tried almost every release made and posted on xda and other than boot loops on occasion haven't had any lasting issues.
I do flash back to the lightly tweaked stock release by Darkshadow once in a while when starting fresh, which IS a "M" only release, but that's just so I have a clean starting point to upgrade from so I have the right WiFi and CSC already installed.
Heck, in my Odin ROM folder I have 7 different main release branches I liked and continue to follow from version to version. 3 of which I still switch between from week to week as new versions come up.
Like most things you just need to read, be careful, and try to know what your doing first. There will ALWAYS be risk, even with a stock ROM, that something will go wrong and brick your system but if you back things up and do your due diligence and wait until a trusted source posts a release with instructions you can mitigate the risk and get support.
As long as you can use Odin, CWM Recovery, or boot into phone you have a very good chance to fix or roll back. Just don't panic and/or fail to wait long enough for things to finish. Sometimes I've had to wait 5 minutes for a loop screen to reboot itself and complete...at other times pulling the battery was the only way to stop things. At other times a reboot into recovery to wipe all info was needed, including mounting all partitions first.
The only "M" versions I'm even aware of all come from Darkshadow....up to version 8 last time I checked.
So...yes...be careful...but to say you can't use GT-S5660 ROMs on a GT-S5660M isn't correct.
InMyBedNow said:
Yeah, from Odin. I'm pretty sure I was using the CWM from your Cm7 build, I installed it by flashing over my old cwm which was this one http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559. I think i semi-bricked by pulling out the battery during bootloop, I shouldn't have. I'll probably sent it in to Samsung since I reflashed everything stock, even the recovery.
Click to expand...
Click to collapse
try to use your old cwm, and go to mount & storage
and you should format system. data & partition
and try to flash stock rom again
are u using adb?
can you paste here your log?
use: adb logcat
maybe i can help you
I thought the "rule" was don't flash the modem/radio - i.e. do a multi file Odin update and select nothing for modem/radio.
I took a stock s5660 2.3.5 rom from this forum and flashed my S5660m in this way, and it's fine.
Post Removed.
Post Removed.
Post Removed.
congratulation man
i'm happy to hear that ^^

Cant't flash any roms

First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.

[Q] Stuck on boot animation after flashing new rom..

I'm trying to install the SUPERLITE CM10 JB4.1.2 RoM by vincom. I've followed the installation instructions as well as I can, using TWRP 2.4.2.0 and making sure to wipe cache, dalvik, system and factory reset twice. TWRP finishes flashing the new rom without giving any error messages, which I assume means all went well.
However, when I reboot from TWRP after flashing the rom, it stays stuck at the boot animation. Vincom's guide says the initial boot after the flash should take a minute, but I've left it for up to ten minutes and it just stays at the looping boot animation. If I pull the battery and restart the phone, it'll go back to the boot animation, but then a message appears, saying "android is being upgraded | 0/61 apps". It'll go up to 61/61 then disappear, which I assume means whatever it was doing is finished, but just stays stuck on the boot animation. And yes, I've made sure the MD5 checksum of the downloaded file matches the one listed at the download website.
For the time being, I'm going to go back to nandroid backup and install CWM recovery, and try to reflash the new rom from there, but I'm wondering if anyone has any idea why this is happening?
If it makes any difference, the rom I was on before is [TouchWiz] EMBRYO 6 -5 (The Gold Standard) (now the rom is up to release 6 -8, I am currently on 6 -5 but I was too lazy to update, then I decided to switch to vincom's superlite CM10)
Very good possibility you had a bad download. Try downloading it again and see if the problem persists
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Unfortunately, it still fails. There are two versions of the superlite CM10 rom, one with slim gapps and the other without. I made sure the MD5 checksums match the ones listed on the download pages. Both stay stuck at the boot animation. Flashing from CWM recovery didn't change anything, either.
RGM79 said:
Unfortunately, it still fails. There are two versions of the superlite CM10 rom, one with slim gapps and the other without. I made sure the MD5 checksums match the ones listed on the download pages. Both stay stuck at the boot animation. Flashing from CWM recovery didn't change anything, either.
Click to expand...
Click to collapse
This may sound like a real pain to do...but... you can go thru Odin and return to stock. Erase your internal memory and sd card. Then re-root.
I did that myself not to long ago due to my phone lagging on any rom I flashed.
I am now running Jedi Jelly 6....and it the SH%T.
Alright, I'll give that a try when I have time and I'll see how it goes, thanks.
In that case that rom's kernel was faulty. You can either restore to your old backup or mount sd card and install another rom. If you want that rom really bad wait for an update and pm the developer
---------- Post added at 05:30 PM ---------- Previous post was at 05:28 PM ----------
I dont think it is ur phone or the current rom your running's fault i think it is just a bad rom u downloaded.
Yeah, that does sound right. I've updated my current rom instead for the time being, thanks for the replies.

TWRP System Image Backup Error

Hello all!
This is my first time posting in the G4 thread, but not my first time playing with Android. I'm normally quite adept at stuff like this, but to make sure I don't goof up my pretty new phone, I want to ask-
When I attempt to back up my System Image in TWRP (which is something new to me entirely- I've never even seen the option to back up a system image) I keep getting this error:
dd if=/dev/block/mmcblk0p47 of='/external_sd/TWRP/BACKUPS/LG815[numbers]/[Date]//system_image.emmc.win' bs=4194304 count=1035 process ended with ERROR: 1
I would like to try OctOS and CM13, just to see how they perform on the G4, but don't really want to unless I KNOW I can get back through a Nandroid backup.
Any ideas or opinions? Does backup of the system image even matter?
Thanks so much! Thumbs up to whoever answers my questions.
I had the same error. (ERROR: 1)
And I also ask - how much is it important to backup the system image?
I don't have custom rom, though, just root access...
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
I had the same error.
And I also ask - how much is it important to backup the system image?
I don't have custom rom, though, just root access...
Thanks a lot...
...
---------- Post added at 17:36 ---------- Previous post was at 17:34 ----------
I add this as an answer instead of na comment..
1. Go to the official twrp thread.
2. Tell which twrp version you are using!
3. Provide the recovery log! You find instructions in the twrp thread

[ROM][6.0][VIBE] VibeUI v3.5 1631 MULTILANGUAGE (Update 1631.2) by sixito007

Code:
I am not responsible for bricked devices, dead SD cards.
YOU are choosing to make these modificiations!!!!!
I am not Developer, i'm just post share from needrom by user sixito007
This is a port from K50-T5 (Lenovo K3 Note)
Installation:
Flash zip file on TWRP Recovery:
Wipe Data, Wipe Cache, Wipe Dalvik Cache, Wipe System.
Install ROM zip
Installing Complet and Reboot.
※Please make a backup of your device before installing or updating ROM
Changes:
DOLBY ATMOS™
SU
ROOT EXPLORER,
MIRAVISION™
SONY MUSIC PLAYER ™
Port Version Information
K50-T5_USR_DEV1631_7.165.1_1607250221_mp1V2.39_CN
Originally posted Here (Needrom)
Downloads
Update-OTA Installer.zip (OTA Updater Official application) https://drive.google.com/file/d/0B4DceN8HABzoSXNJcmQ1NEJYNGc/view?usp=sharing
ROM v2 https://drive.google.com/file/d/0B4DceN8HABzoSkcxVF9wZEF1cDg/view?usp=sharing
TWRP AIO ROW https://drive.google.com/file/d/0B4DceN8HABzod3FPcDNidU5iQjQ/view?usp=sharing
Update 1631.2 https://drive.google.com/file/d/0B_rwx9TBvDU9Wnk1YWs0ODBua2s/view?usp=sharing
Error is fixed
Tried. waited for 25 mts, still remains in boot loop.
cvpillai said:
Tried. waited for 25 mts, still remains in boot loop.
Click to expand...
Click to collapse
thats sad(
How you tried to install?
I am on TWRP, MM Stock ROM. followed usual ROM instalation procedures under TWRP and flahed. Waited 25mts on boot screen.:crying::crying:
cvpillai said:
I am on TWRP, MM Stock ROM. followed usual ROM instalation procedures under TWRP and flahed. Waited 25mts on boot screen.:crying::crying:
Click to expand...
Click to collapse
Added twrp. download from first post.
cvpillai said:
I am on TWRP, MM Stock ROM. followed usual ROM instalation procedures under TWRP and flahed. Waited 25mts on boot screen.:crying::crying:
Click to expand...
Click to collapse
LINK UPDATED, Error is Fixed.
Tried. Some improvement is there. It goes up to Welcome screen, waits for Language option, remains there after choosing the language - indefinitely.
Witch kernel is used in this ROM ? Thanks
Is there any way to remove those ugly grey icon backgrounds?
Like in the first post, in the second screenshot, it can be seen that Titanium backup has a grey background
Similarly, pre-included apps like syncit has no background.
This difference of icons makes the phone look quite ugly.
Please tell me what's working wrong, or not working at all...
Added update v3.5 1631.2.
-added more Lenovo apps
-added full slovak and czech language
-added Dolby Atmos™ on Settings
-added Update system on Settings/Device info
- more free RAM memory cca.1300MB
Installed successfully. So far only Bluetooth problem detected. Shall get back after some use.:good::good:
Firefox and other apps won't open. They crash as soon as tapped. And Bluetooth isn't working.
nvidiageek said:
Firefox and other apps won't open. They crash as soon as tapped. And Bluetooth isn't working.
Click to expand...
Click to collapse
you need to install rom first, then update 1631.2, and tap "format dalvik&cache" when install ends.
after that reboot - and system works fine. only bluetooth can crush at the first boot.
Dumaxa said:
you need to install rom first, then update 1631.2, and tap "format dalvik&cache" when install ends.
after that reboot - and system works fine. only bluetooth can crush at the first boot.
Click to expand...
Click to collapse
I'll try and report.
---------- Post added at 08:32 PM ---------- Previous post was at 07:33 PM ----------
Worked. Thanks.
Update on ota updater (update-v3.5-1631.3)
I cannot take any picture in camera is show need sd card... Even i cannot take picture of my screen. Please fix this :'(
Can i install this on K50-T5 (Lenovo K3 Note)?
inouext said:
Can i install this on K50-T5 (Lenovo K3 Note)?
Click to expand...
Click to collapse
I don't think you have read the OP carefully. It clearly says that the Rom is ported FROM the K3 note. Search the relevant thread in xda for your device. It'll be there. Good day.

Categories

Resources