Ok so i flashed a new rom gbsense_s_4.5 and then tsm_sense_m_ext4_5.0.1 both and 2.3.4 where as i WAS 2.3.3, I did a backup of original rom then wiped and installed roms. I didnt like then to much so i went back to the back up and when i tried to install the back up i get a sum5 mismatch error. I then tried to flash the original Rom Zip and i get a aborted error. I cant figure it out. Do i need to downgrade again in order for it to work. I have wiped cache and factory reset phone as i always do. Oh and i Renamed the backups to original root rom and root rom w.apps. I can redo the apps and contacts manually but i cant seem to get the rom to install on the Inc. 2. Any help would be appreciated. Thanks
Related
I rooted my Evo a few days ago. I removed some of the factory programs that I did not use and now I want them back. I have 2.3.3 on the phone. I tried to download the rom and install it. I used rom manager and Clockworkmod both and I got a error status 7. Can anyone point me in the right direction to reinstall the factory rom?
Thanks
Have the same issue with mine i cannot get it to load anymore.
Both of you need to go to the development section, then seach for a stock 4.24....rom. Do a full wipe, then flash it in recovery and you'll be set.
I would suggest finding stock PC36IMG flash thru hboot!
Im sorry if this is being repeated, but I'm relatively new to flashing custom ROMs and up until now haven't really had any issues.
I recently flashed the latest PACman rom 4.3 and I'm not sure what went wrong. I'm coming from 4.2. I did everything the same as usual, wiped cache and dalvik, installed the zip. As soon as the phone rebooted, I started getting error messages. "Acore has stopped working, blame tyler", same thing for the system UI. So I decided to do a wipe and restore. Well now my restore wont work. I've had to go back to a PAC version from back in February because none of my other restore files will work. I'm not sure what to do. Even on this restore file, I'm getting "insufficient storage" messages when I havent even uploaded all my apps yet.
Please help!
justxan said:
Im sorry if this is being repeated, but I'm relatively new to flashing custom ROMs and up until now haven't really had any issues.
I recently flashed the latest PACman rom 4.3 and I'm not sure what went wrong. I'm coming from 4.2. I did everything the same as usual, wiped cache and dalvik, installed the zip. As soon as the phone rebooted, I started getting error messages. "Acore has stopped working, blame tyler", same thing for the system UI. So I decided to do a wipe and restore. Well now my restore wont work. I've had to go back to a PAC version from back in February because none of my other restore files will work. I'm not sure what to do. Even on this restore file, I'm getting "insufficient storage" messages when I havent even uploaded all my apps yet.
Please help!
Click to expand...
Click to collapse
I had similar problems going to 4.3 as well. Mine kept getting frozen at the boot screen, and wouldn't restore any of my backups. I tried flashing back to previous versions of android and nothing was really making any difference. Finally I ended up flashing the whole phone back to stock. From there I flashed the new 4.3 stuff on top of that and now everything is working flawlessly like it should again. I still have no idea what caused the issues, it's gotta be something in the new 4.3 stuff that's trickling in.
Here's what I did:
Download the most recent complete firmware file (which is UCDLK3 for d2att)
Download the pit file for my phone
Flash stock image and pit file with repartition through ODIN
Flash custom recovery back through ODIN (CWM, TWRP, etc)
Download and flash latest UCDMG2 bootloader (for d2att)
Download and flash your choice of ROM, kernel & gapps
and optionally -
Update modem to latest UCDMG2
Now you should be back to a fresh install of 4.3 which works the way it should! Hopefully you had your apps backed up with titanium or something similar which can be restored now as well.
exodus454 said:
I had similar problems going to 4.3 as well. Mine kept getting frozen at the boot screen, and wouldn't restore any of my backups. I tried flashing back to previous versions of android and nothing was really making any difference. Finally I ended up flashing the whole phone back to stock. From there I flashed the new 4.3 stuff on top of that and now everything is working flawlessly like it should again. I still have no idea what caused the issues, it's gotta be something in the new 4.3 stuff that's trickling in.
Here's what I did:
Download the most recent complete firmware file (which is UCDLK3 for d2att)
Download the pit file for my phone
Flash stock image and pit file with repartition through ODIN
Flash custom recovery back through ODIN (CWM, TWRP, etc)
Download and flash latest UCDMG2 bootloader (for d2att)
Download and flash your choice of ROM, kernel & gapps
and optionally -
Update modem to latest UCDMG2
Now you should be back to a fresh install of 4.3 which works the way it should! Hopefully you had your apps backed up with titanium or something similar which can be restored now as well.
Click to expand...
Click to collapse
Thank you for responding and providing details. I guess I'm not understanding where to find these files. I have the firmware downloaded. The pit file, I can't seem to find no matter what I search for. I can find help on creating my own, but I'm afraid I'll screw something up if I start messing with things. The stock image, bootloader and modem...no idea where to find those either. I've never had to do any of this before. Are these files within the rom I'm trying to flash??
I flashed a new kernel to test and didn't like it, so I reflashed the ROM to get the stock kernel back and all hell broke loose. I lost root access and cant flash anything. I used Odin, re rooted and am on stock rooted 4.2. I've tried both TWRP and CWM to flash a ROM and from 2 different SD cards or restore my backup and it either says bad ROM or MD5 mismatch.
What am I missing here? In the meantime I'm just stock rooted with no mods, only restored user apps through Titanium.
92drls said:
I flashed a new kernel to test and didn't like it, so I reflashed the ROM to get the stock kernel back and all hell broke loose. I lost root access and cant flash anything. I used Odin, re rooted and am on stock rooted 4.2. I've tried both TWRP and CWM to flash a ROM and from 2 different SD cards or restore my backup and it either says bad ROM or MD5 mismatch.
What am I missing here? In the meantime I'm just stock rooted with no mods, only restored user apps through Titanium.
Click to expand...
Click to collapse
Check to make sure your usb cable is good. Many a time it is tthe usb cable which is bad.
Check to make sure the md5 checksum matches between the file you downloaded and the download itself.. From your device, use md5 checker.
From your pc, there is a similar program to do so.
The ROM has the Kernel cooked into it.
Read the ROM op to make sure.
If you dl a new Kernel file, always check the md5, in addition to inquiring if it's compatible with the ROM.
Always have the Kernel that was working saved somewhere so you can reflash it if necessary.
Always have a Nandroid Backup just in case.
When things don't play nice, always try going into Recovery and wiping
Cache & dalvik cache, and reboot.
Your initial is was:
A Kernel that didn't play nice with the ROM
or a corrupt dl
etc.
Your 2nd issue is most likely related to:
Bad usb cable or
Md5 mismatch, which can be because of a bad dl or a bad usb cabl.
re: stock firmware
92drls said:
I flashed a new kernel to test and didn't like it, so I reflashed the ROM to get the stock kernel back and all hell broke loose. I lost root access and cant flash anything. I used Odin, re rooted and am on stock rooted 4.2. I've tried both TWRP and CWM to flash a ROM and from 2 different SD cards or restore my backup and it either says bad ROM or MD5 mismatch.
What am I missing here? In the meantime I'm just stock rooted with no mods, only restored user apps through Titanium.
Click to expand...
Click to collapse
You need to start from scratch, put your phone into DOWLOAD mode and ODIN flash the stock M919 Samsung Galaxy S4 firmware.
(TAR file)
Here is the link to the official stock tmobile m919 firmware for your samsung galaxy s4 phone: http://www.hotfile.com/dl/213469534/9ff06bd/M919UVUAMDL_M919TMBAMDL_TMB.zip.html
Once you do this you can root the phone if you like or leave it stock.
Good luck!
So I odin'd back to stock and rooted, I may leave it this way, the battery life is killer lol
Thanks for the help guys.
Well I got restless and tried flashing again and still no luck. I odin'd back to stock 4.2 and rooted just fine, have setcpu running and supersu installed but still cant flash anything or restore a backup, I'm really confused now.
While in download mode it says write protection enabled, is this normal? It also says this while I try to delete any files via USB. This is screwy.
O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred
gapps stops after cwm restore
Phederico said:
O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred
Click to expand...
Click to collapse
I have the same issue. Did you find an answer?
psawood said:
I have the same issue. Did you find an answer?
Click to expand...
Click to collapse
NOPE...no one's said a word and I've just been rolling back to my last stock rooted ROM and then taking the O.T.A. then re-rooting whenever I do something stupid. LOL If you have an answer for me..or anyone does for that matter, I'd sure like to hear it!
P.S. sorry, gave up on this thread, so hadn't kept up on it...just now saw your post.
~Fred
I ran into this issue.
What I did is :
DL Rom Manager
Open Rom Manager
Fix Permissions
Boot into Recovery
Wipe Cache
Wipe Dalvik
Reboot
Haven't had the issue since.
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
ladd76 said:
Greetings,
I was attempting to install a ROM through CWM 6.0.4.7 recovery and it failed during the installation. More like crashed as I did not get an error message or have the robot fall over. After this happened my galaxy s3 started bootlooping. During the bootloop I could still see the cyanogen mod icon present which I thought was strange as I had done a full wipe/factory reset/system format before attempting to install the other ROM. I have been flashing ROM's for over a year but am still learning. Anyway I got back into CWM recovery and attempted to wipe user data/factory reset again to make sure I had a clean install before making a 2nd attempt and I was able to wipe both caches no problem but when I attempt to do factory reset it crashes. I thought maybe it was the recovery so I flashed TWRP through ODIN and tried to factory reset and it also crashes.
I am still able to access download mode and get into custom recoveries but I am not sure what to do now. I have attempted to flash back to CM 11 and Task 650 4.4 but I receive status 7 errors. I have not been able to locate stock restore tar files for 4.3 as all I have read is that 4.3 was an OTA and there is no tar file for it. Any thoughts? Thanks in advance.
Click to expand...
Click to collapse
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Larry2999 said:
Are you using the AT&T i747 or the i747M? Looks like your phone does not have a working OS. Please see the post below for a similar problem. If you have the AT&T version, you may try the same recommended solution to get your phone back to working condition via stock restore which you can do from custom recovery ...
http://forum.xda-developers.com/showthread.php?t=2743241
Click to expand...
Click to collapse
yes i747 thanks
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
audit13 said:
Try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
That is actually what i was flashing when I encountered my problem. I was finally able to get one of my old ROM's to install after re-flashing the newest CWM through ODIN and reinstalling my bootloader. I am not sure what the problem was as the stock rom 4.3 shouldnt have downgraded it? Perhaps a random crash which corrupted something. The developer on the stock rom has provided a tar file which I may try this time around. Thank you all for your help.