I was Softbricked, I restored a backup, the phone bootes normally but I can't do anything, it shows a message:"Unfortunatly, Application installer has stopped."
Does anyone have a solution to fix this problem ?
Well since your phone boots no problem its pretty easy to get it to a working state again. Just flash a stock ROM using Odin and you should be good to go.
You can get the latest stock Roms from sammobile.
Personally i would say forget the backup, factory reset data/cache and start fresh. However, since your previous rom appears to be unmodified stock, you may have luck flashing without doing a data reset.
I sent the phone to a repairer, he will solve my USB Port problem and he'll try to revive the phone, if he doesn't I'll try what you said.THANK YOU !
Related
Hey guys this is where I am with this issue. Kind of new to Android so forgive me if something is obvious and left out.
Bell Galaxy Note, unlocked via unlock code.
Please note that before I ever flash a new rom, I do a factory wipe, wipe cache, wipe dalvik..3 times first, then I redownload and install from Play
1. Noticed that my phone on Flappjaxx's rom was acting flaky. (ie FCs more than usual). This rom worked fine for a few weeks.
2. Tried CM9 via Rom Manager. Phone still a bit flakey.
3. Used CWM Recovery to return to FJ's rom which I made a backup first.
4. Phone even more flakey (ie. noticed some apps could get the internet, others could not. Phone would FC as well every time).
5. Tried clearing cache, dalvik, and fixed permissions. FJs rom still flakey (at this point 2-3 attempts to fully boot). Factory reset and caches cleared again but still the same.
6. Used Odin to flash the Bell stock system, recovery, and boot from this thread: http://forum.xda-developers.com/showthread.php?t=1599127
Did a factory reset using the stock recovery after this was flashed as well.
7. Having the same issues on the stock rom as I had on FJs rom and CM9.
8. I was eventually able to get the phone to allow me to see the baseband version before it rebooted (took a few tries) and I see the baseband is still UCLF6. I thought the baseband would have been reset too but I guess not.
Is there something else I should do? Will popping CWM recovery on there again and flashing another modem fix this?
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
This happens sometimes. You just have to find and flash the stock modem through odin to get it 100 percent out of the box.
As far as the warranty return, no one would allow it because you have no way of proving that the problems with the phone are not directly related to your modifications to the device even if they are not.
However, I would suggest flashing the stock modem and then reformatting your device through kies as a last resort. If this does not still work, I would suggest (although never used) the flash counter reset zip once youre on stock and sending it in for repair.
Hope you get it up and working
welchertc said:
How would that justify a warranty return? It's a result of you flashing custom software, warranty returns are for manufacturer defects. Are you restoring system apps or something in tibu? Otherwise just keep trying to get back completely stock and completely wipe everything.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Understood about warranty of course.
- not restoring anything...as mentioned, everything is always set up from scratch, including all apps from Play store.
- I'm trying to get back to stock, and everything looks stock except that my baseband reads UCLF6, which I assume is not stock GB. I have tried flashing the modems, kernals, and roms found here http://forum.xda-developers.com/showthread.php?t=1506330 and here http://forum.xda-developers.com/showthread.php?t=1599127
This is why I am asking if my hardware seems defective, or if there is something amiss in what I am trying to do (if I am seeing UCLF6 in my baseband, I am assuming I am missing something).
Last attempt to get rid of the UCLF6 baseband I downloaded this modem: http://forum.xda-developers.com/showthread.php?t=1506330 , did a reset, wiped caches, and still showing UCLF6.
Don't know what I did differently, but I tried pterry30's modem and flashed via CWM (I could not find an Odin modem tar) and my phone seems normal now (but very stock) and I got the 'mugla' version of the modem listed in my system settings.
Thanks for the suggestions...hopefully its really fixed. Since I went through all this trouble I'll try Bell's ICS update.
Problems like this are great learning tools...but a bit stressful lol
Happy all is well. Good luck.
something weird has happened and my phone wont boot stuck on Samsung logo and every time i boot into twrp recovery it asks for pass? i never set a pass so idk whats going on and so i press cancel and every time i try to wipe or factory reset or anything it says failed?
Edit: I did a format data and that worked luckily... i still dont know what was up with all that and it boots into rom until i restart phone then hangs at samsung logo again????
Edit: Found a fix!!! Read POST #6
twrp asking for pass?
:good:
after restarting phone still gets stuck on samsung logo?
it also still asks for password in recovery?
Had the same thing happen to me. I also got it to work after formatting the phone and reinstalling the image but after the first reboot the problem reappeared.
I was able to get Verizon to DOA my phone but you might have luck with flashing stock with http://forum.xda-developers.com/showthread.php?t=2301259 if the issue reappears
If this fixes the problem let me know because I am very hesitant about installing TWRP and custom roms on the S4 at this point but if this solves the problem that will be huge.
tgumina said:
Had the same thing happen to me. I also got it to work after formatting the phone and reinstalling the image but after the first reboot the problem reappeared.
I was able to get Verizon to DOA my phone but you might have luck with flashing stock with http://forum.xda-developers.com/showthread.php?t=2301259 if the issue reappears
If this fixes the problem let me know because I am very hesitant about installing TWRP and custom roms on the S4 at this point but if this solves the problem that will be huge.
Click to expand...
Click to collapse
I was about to make a trip to vzw myself (afraid they might find out it was custom) but now no need
After polling out my hair and staying up till early am I got it fixed...
Solution (trust me I had tried everything else) boot into odin install the SCH-I545_MDK_562219_Stock_Restore.
http://forum.xda-developers.com/showthread.php?t=2289325
You will lose root and go completely stock but at least now I am confident I cant brick my phone after finding out this worked
Same Problem here.. I did the Store Restore and all was good.. BUT, I then rerooted and the problem reappeared.. Is there any fix so we can root ?
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
Hey,
My friend was running a flawless custom rom on his s3. Suddenly, it turns off by itself and the phone is then stuck on boot logo.
1. I tried to factory reset with no luck.
2. I tried to install stock 4.3 with no luck.
3. I tried to install 4.1.2. The phone booted but with no recovery. Then i noticed that imei changed to *0049 and i'm not registered on network (even though it was working well on the custom rom).
4. I tried to upgrade to 4.3, i got succeeded but recovery didnt install.
5. I tried to install the custom rom again but no luck.
6. I tried all patches of modems and kernels and ariza. All Failed.
7. I also tried EFS backup/restore and Failed.
My only concern is to know what made this issue appear all by itself ?? Because i guess we should take it to a mobile repair shop.
One last thing to say is that every time i try to install a software, available space gets low, and even if i delete some files from internal storage the storage wont free up.
Thank you !
get stock 4.3 fom and flash it via Odin (wipe everything before flash). Then flash recovery via odin. then backup efs. then flash custom roms.
downgrade from 4.3 to 4.1.x causes efs to become corrupted
Seems like a corrupt nand. Was it rooted previously when it died the first time?.
Going from 4.3 to 4.1.2 will cause the imei to be lost as the efs encryption changed at 4.3. You cannot go back.
If the phone has a custom rom on it try an official cwm recovery, if not or it doesn't work then proceed to the following:
If you can get the phone into download mode try flashing the stock firmware twice or thrice with a factory reset in between each flash. Do not allow the phone to boot into the os!!. If it attempts to boot to OS after the blue pass in odin then pull the battery out immediately and boot to recovery or download mode respective of what you are doing at the time, resetting or flashing.
If that fails you can then call it a dead phone.
Beamed in by telepathy.
Wow these are new solutions to me..
I really thank you guys and i'll look forward into trying them in any upcoming problems.
Thank you so much for sharing your knowledge
And just to mention, yes the phone was rooted when it went bricked suddenly.
I'd try to flash an official cwm and if it takes then flash back to stock twice with a reset, reroot and leave it as that. Custom roms aren't worth the paper they're written on.
In addition to downgrading from 4.3 to an earlier version, but forgot at the time of writing, you can downgrade but you need an efs backup from the time it was at 4.1.2, which has to be restored but I'm not sure of the process. I couldn't tell you if it has to be restored before flashing, after or both.
Not a lot of people have an efs backup from 4.1.2. I do, but then my phone hasn't acted wierd yet. Sods law.
Kies 2 (not kies 3) can restore the phone but only if it was in original condition. You can try the emergency recovery routine but don't hold your breath.
Beamed in by telepathy.
You're right.. Efs is the only part most of us miss !!
I wrote all of the steps you said in order.. So that if any problem occur ill deal with it based on your info.
Btw do you suggest using KK TW 4.4.4 by back-to-n00t ? Or this wont be considered as a kind of official firmware ?