Hi,
I got the rooted, deodexed, and debloated version of the latest stock rom.
After I flashed it, I keep getting the error messages "unfotunately the process ... has stopped unexpectedly". I used CWM to flash this rom multiple times. I also wiped data/factory, cache, and dalvik cache. I saw some others are reporting the same error.
I was wondering if there is a solution for this out there.
Thanks
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
gc84245 said:
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
Click to expand...
Click to collapse
No I didn't try the infamous superwipe. I will do it. What is cache wipe, is it same as the option in CWM recovery mode?
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
gc84245 said:
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
Click to expand...
Click to collapse
Ok, BTW, I moved from Juggernaut 5.0 to JB Stock using ODIN and it worked fine. It's the rooted version of the JB Stock that gives me these errors. In fact, the main reason that I tried rooted version is because it supposedly doesn't have bloadware either.
Well using odin removes more than flashing a zip, for example it replaces your recovery. I'm not an expert and don't know much about the details, but that's probably why it worked using odin.
Related
Hi everybody....Ive been flashing ROMs from ROM Manager and never had problems...until I tried to flash from CM7 nightlies #66 to a leaked G2 ROM][04/28/11] TMOUS G2 Gingerbread 2.13.531.5.
I did the usual wipe cache and dalvik and proceeded, it seemed like it was downloaded but got stuck on the reboot, it was stuck on the HTC logo for a long time. I thought I bricked it but managed to get it to work by taking the batterie out and going into recovery by clockworkmod.
Is there any special way to flash ROMs from the nightlies on a G2?
You said you wiped cache and dalvik, but did you wipe data too(factory reset)? Pretty sure you need to do that if coming from cm to the stock tmo leak. Could be wrong but sounds about right
Sent from my T-Mobile G2 using XDA Premium App
that is right anytime change roms that are not linear to the same dev, it is best to wipe all, data/factory/cache then flash rom
ilostchild said:
that is right anytime change roms that are not linear to the same dev, it is best to wipe all, data/factory/cache then flash rom
Click to expand...
Click to collapse
Hmm, I checked everything that ROM Manager suggested, cache/ dalvik, the only thing I didnt check is to back up current ROM.
If you wanna wipe all that data/factory/cache do yo have to flash it manually?
Flashing other roms I think messed up my phone lol. I just stay with cm7 now lol
Nonsense!
ms9007 said:
Hmm, I checked everything that ROM Manager suggested, cache/ dalvik, the only thing I didnt check is to back up current ROM.
If you wanna wipe all that data/factory/cache do yo have to flash it manually?
Click to expand...
Click to collapse
even if you did say to wipe /system and /data in addition to /cache, CWM is notorious for not actually formatting the partition. go into the dev section and find SuperwipeG2 and if you are switching from aosp<->sense or, as earlier mentioned, from one dev's rom to another, run superwipe before doing so.
How do I flash a new version of a ROM without re installing all my apps or contacts? For example if I have v1 of a person's ROM and they upgrade to v2, How would I flash the new version of the ROM without having to redo all my apps, contacts, email etc...?
All you do is flash the updated ROM the wipe cache and dalvik then reboot
Sent from my SPH-L710 using Tapatalk 2
daniel4653 said:
All you do is flash the updated ROM the wipe cache and dalvik then reboot
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok thank you so much.
Simpoh said:
Ok thank you so much.
Click to expand...
Click to collapse
Where he is right, you should still do a full wipe even when flashing the same rom if its a firmware upgrade, or major backend framework has been modified.
If you do a android backup prior to flashing, you can do an advanced restore of data only, from your nandroid backup, and all of your apps & data will restore just as it was before - while maintaining the integrity of the updated version of the ROM you use.
Super easy, super fast, super efficient.
ROM - Odexed Blue LJ7 JB "Holy Grail"
Kernel - KT747
Baseband - LJ7
Sent from my Sprint Samsung Galaxy S3 using XDA Premium
clarify best clean install, ie what needs to be wiped
I posted in a different thread, "moment to epic now S3" asking basically what constitutes a full wipe when flashing a rom, or flashing mods. On my epic CWM it was pretty clearly stated in almost all OP wipe all 3, times 3. If not it was said wipe davlik and cache times 3. I'm using the twrp recovery and there are so many wipe options, and I don't know which ones are necessary for a clean install when flashing a new ROM. My phone was giving my so much trouble yesterday i wiped all but the external and flashed a stock rom, then odined a stock rooted to be back at square one. But I don't want to flash a new rom until I here from others the cleanest way to install. I noticed for flashing a kernel it said I had to fix permissions also? So I guess it seems less cut a dried, 3 options (with epic recovery) and before I start screwing around with my phone I wanted some clarification, for flashing roms, flashing modems, flashing mods...what needs to be wiped, or what constitutes a full wipe. I can't assume that a clean wipe means everything and if it doesn't well obviously that would be nice to not have to wipe internal card etc if i don't have to
thank you much
My T-Mobile Galaxy s4 M919 will not boot after any custom ROM flashes. I tried 4 different ROMs with success messages. As soon as I reboot my phone after the ROM flash, it's stuck at the Samsung Galaxy S4 logo and would not enter the "phone desktop". I can easily enter download mode and recovery mode without any issue.
Background: I rooted with Odin successfully. (Used both CWM and OUDHS with the same no-boot results after flashing any custom ROMs). I can restore back to stock and phone boot up fine but tried root again and then with custom ROM and it would not boot. Any help would appreciate it.
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
After flashing a rom, go into recovery, and erase stuff. Like cache and dalvik cache. Possibly even data
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
anothersaddream said:
I did that after each ROM flash. 1. Wipe data/factory reset, 2. wipe cache part, 3. wipe dalvik cache. Did not fix the problem. No good. Please clarify "possibly even data". I am not sure which wipe is that.
Click to expand...
Click to collapse
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
I switched to PhilZ Touch Recovery a couple of weeks ago and have not had Any issues as I did before.
TWRP 2.5.0.2 was issue free for months, until I started flashing ROMs with Aroma.
Nothing but issues re Samsung splash screen freezes, different solutions working sometimes and sometimes not, having to ODIN back to stock on many occasions, having to wipe INTERNAL SD on many occasions, etc., etc.
PhilZ was the solution.
This is coming from a hard core TWRP guy......
Check the link in Red in my sig for PhilZ and other good stuff
dynospectrum said:
using CWM:
*wipe data/factory reset
*wipe cache
*wipe, dalvik cache
*wipe system
*wipe sdcard (only if you have the ROMs you plan on flashing on your external sdcard, this will erase internal sd)
now flash your ROM of choice. reboot (will take 1-2min on first boot)
use cwm touch. what ROMs have you tried so far?
Click to expand...
Click to collapse
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
DKYang said:
Yeah, what ROMs have you tried already? Have you tried TWRP 2.5 recovery?
Sometimes it'll take up to 10 minutes to boot up (I haven't experienced this yet with the GS4, but I have with other phones). How long did you wait before determining it was just stuck?
Click to expand...
Click to collapse
I have not tried TWRP 2.5 recovery yet. I mostly use CWM. I have waited 20+ minutes after flashing a custom ROMs but to no success.
I have done the following ROMs:
Insanity v1
VirginROM
stevessvt said:
I am thinking you are flashing something not specific to the TMo S4, so your not getting the right kernel installed. Try installing a TMo specific kernel immediately after flashing a rom and see what happens.
Click to expand...
Click to collapse
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
anothersaddream said:
I did try the InFamous ROM for Tmobile s4. This ROM also has a kernal. Same results, stuck at Samsung Galaxy s4 Logo screen. It would not go anywhere after that.
Really needing help here.
Click to expand...
Click to collapse
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
anothersaddream said:
Where do you "wipe system"? I see a format /system inside Mounts and Storage Menu. Please confirm.
Click to expand...
Click to collapse
wipe = format
yes, format system in mounts/storage.
Skipjacks said:
Okay let's start over from scratch.
First off can you restore the stock ROM using your nandroid backup?
Second, I don't think you are properly wiping everything prior to flashing the new ROM. You need to wipe system, data, dalvik, and cache in the CWM wipe menu prior to flashing the new ROM.
Wipe all 4 things. Wiping any less than all 4 things will cause the problems you are experiencing.
Once you've done that, then flash the ROM.zip and reboot and it should work just fine.
Click to expand...
Click to collapse
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung S4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
anothersaddream said:
I did exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things. ROM flash stated success. Still NO good. Stuck samsung g4 logo. You think there is something wrong with the hardware???? The s4 does randomly reboot on stock.
Click to expand...
Click to collapse
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
find stock kernel, flash the roms you want and flash the stock kernel after and see if you boot
Biker1 said:
When I was flashing ROMs w/Aroma using TWRP 2.5.0.2, I would sometimes get Samsung boot screen freezes. The only way I could resolve this was by wiping Internal SD, in addition to the other wipes mentioned, and flashing the ROM again.
Click to expand...
Click to collapse
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
anothersaddream said:
I also tried your suggestion exactly what you stated. Restored to stock. Rooted successfully. Wiped all 4 things + format /sdcard (internal SD). ROM flash stated success. Still NO good. Still Stuck Samsung S4 logo.
Is there any custom ROMs I can flash using odin?
Click to expand...
Click to collapse
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Biker1 said:
ODIN Samsung Stock Firmware.
Boot.
ODIN Custom Recovery.
(I use PhilZ Touch Recovery. Flashes ROMs flawlessly )
Boot.
Flash custom ROM afterwards.
If ROM doesn't have Root, then Root with CF-AUTO-ROOT by Chainfire via ODIN prior to installing Custom Recovery.
Then flash custom ROM.
Click to expand...
Click to collapse
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
anothersaddream said:
I did as you stated. I love Philz Touch recovery UI. Very nice. Unfortunately, did not work as well. It stated successfully. I tried 2 rom, Infamous S4 v.2.5 and also the VirginROM v2.3.1. Both stated successful flashed but would not boot into the phone desktop. Stuck for over 10 minutes on black and white "Samsung Galaxy S4" logo.
I will send you a nice Starbucks gift card if anyone can fix this problem.
Click to expand...
Click to collapse
I have no idea why it ain't working for you.
On the plus side, I don't know everything
If you ODINd Stock.
ODINd Recovery.
Did a Md5 Checksum match between the ROM file and your Download.
Wiped Internal SD.
Flashed the ROM......
and you're still having issues.......
I'm at a loss....
Try again is my only suggestion, and insure the steps taken are correct, including ODINing the proper files for your device.
Check & Double check
Including making sure you have a good usb cable, which sometimes can work and sometimes not....
If you haven't, try flashing from internal sd card. Maybe remove th external sd card just in case.
Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro
Just dropped a rooted stock rom back on my t989 (from this thread), and I'm geting com.android.phone has stopped message. Came from Cyanogen, Infamous, and Jedi, no problems, but for some reason, the stock rom installed via twrp seems to fail. I need it more or less stock, and I'd really rather not Odin it. Any ideas?
SaddamHussein said:
Just dropped a rooted stock rom back on my t989 (from this thread), and I'm geting com.android.phone has stopped message. Came from Cyanogen, Infamous, and Jedi, no problems, but for some reason, the stock rom installed via twrp seems to fail. I need it more or less stock, and I'd really rather not Odin it. Any ideas?
Click to expand...
Click to collapse
Did you wipe system, cache, dalvik, cache, data, and android secure before flashing? If so, after flashing wipe data, cache, and dalvik cache and reboot
Sent from my SGH-T989
jrc2 said:
Did you wipe system, cache, dalvik, cache, data, and android secure before flashing? If so, after flashing wipe data, cache, and dalvik cache and reboot
Sent from my SGH-T989
Click to expand...
Click to collapse
Yep. Per the instructions, performed all of the above wipes, as well as darkside super wipe and wipe before installing the ROM.
Also wiped cache and dalvik after flashing, but haven't tried wiping data after flash...I'll give that a try this evening.
Last night, out of necessity to have SOMETHING running on the device, I threw on AOKP, which runs without issue. I've seen a few other debloated/rooted stock T989 UVMC6 roms floating around, but the comment threads underneath them seem to indicate problems of various types.
If someone knows of a UVMC6 TW ROM that is known good, and can be installed via installed via TWRP, I'd be very interested, even if it still has the bloat. Its the wifes phone and she is a bit of a touchwiz nazi, but hates all the custom boot logos, etc, that come with roms like Infamous. Stock is where she is at.
SaddamHussein said:
Yep. Per the instructions, performed all of the above wipes, as well as darkside super wipe and wipe before installing the ROM.
Also wiped cache and dalvik after flashing, but haven't tried wiping data after flash...I'll give that a try this evening.
Last night, out of necessity to have SOMETHING running on the device, I threw on AOKP, which runs without issue. I've seen a few other debloated/rooted stock T989 UVMC6 roms floating around, but the comment threads underneath them seem to indicate problems of various types.
If someone knows of a UVMC6 TW ROM that is known good, and can be installed via installed via TWRP, I'd be very interested, even if it still has the bloat. Its the wifes phone and she is a bit of a touchwiz nazi, but hates all the custom boot logos, etc, that come with roms like Infamous. Stock is where she is at.
Click to expand...
Click to collapse
AOSPA KitKat runs SOO much better than TW. You can change the boot animation to something else very easily.
Sent from my SGH-T989
I'd use the "infamous" wipes before flashing...just for anything touchwiz based. Not aosp. And don't use the darkside wipes...they are outdated.
Search Google or XDA..."t989 infamous wipes"
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
You can also just Odin stock 4.1.2 and debloat it yourself with titanium backup. Freezing bloat, no sense in uninstalling it.