Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
DroidJay123 said:
Hello all-
I was just recently running CM 10.2 RC1 but had to do an install of the correct gapps as it was randomly rebooting. Well the device now is stuck on the Samsung Galaxy S3 screen with the BLUE cyanogen. I have access to TWRP and am able to reflash the .zip file for CM 10.2 RC1 yet it still won't boot? I did the wipe of dalvik, cache, data and system but still no luck? The device is NOT recognized in Odin. I just want to get the phone up and running again, even if it means root is lost.
Please help!!
Click to expand...
Click to collapse
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Mr.Rageface said:
Do you have it put into Download Mode before you plug it into the computer for Odin to recognize it? If I had it plugged in before I put mine in download mode Odin would not want to pick it up.'
Mr. Rageface
Click to expand...
Click to collapse
Yes it is recognized once in Download mode...sorry about that. What can I do to get it up and running? I am not new to flashing, etc so it's got me really upset that I cant get it to boot. What could possibly go wrong?
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
http://fs1.d-h.st/download/00023/E5R/I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 You can download that file and put it in the PDA section once you run Odin and run it from there. This will put your phone back to the Stock Rom 4.1.1 and you can restart from there if you want.
Mr. Rageface
xXFl4sh said:
Get a sd card>download a new rom and put the rom in the sd card and flash like a normal ROM
Click to expand...
Click to collapse
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
DroidJay123 said:
I do have an sd card. Phone isn't recognized in Windows so Im not familiar with how I can get the ROM file onto the card from the computer? Can I download the latest AT&T Stock ROM and flash it via Odin?
What your saying is flash a ROM from the external SD card?
Click to expand...
Click to collapse
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Mr.Rageface said:
No, with the file I told you to download you do not need to have a SD card because you can't boot into the rom you have Windows will not recognize the phone like normal to drag and drop to it. So with this file you can save it to your computer, Open Odin, put your phone into Download Mode, plug it into the computer so that Odin detects it. Then Click PDA and browse to the file you downloaded and tell it to use that file and then Run the process and it will install the original rom onto your phone.
Mr. Rageface
Edit: Sorry I did not realize your previous comment was to xXFl4sh.
Click to expand...
Click to collapse
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
DroidJay123 said:
Ok I did the process with the file you referenced. Everything succeeded in Odin with no errors. It's still stuck on just showing the Samsung Galaxy SIII screen but now without the blue cyanogen? What is wrong with this phone??
Click to expand...
Click to collapse
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Mr.Rageface said:
Can you get into recovery mode by any chance? If you can do that then it should be possible to do a factory reset from within Recovery Mode and possibly get you past the boot screen. If that doesn't help let me know and I will see what else I can find out for you. Also what all did you have checked and unchecked when you Ran Odin to reinstall the Stock Rom? If you had any of them other than Auto-Reboot on that may also have caused a problem http://forum.xda-developers.com/showthread.php?t=1722686 here is a forum that will show you how to use Odin. I apologize for not remembering about telling you what to check and uncheck. But try recovery mode first and do a factory reset and if that does not work, redo the odin install this time only having Auto-Reboot checked.
Mr.Rageface
Click to expand...
Click to collapse
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
DroidJay123 said:
Thanks man! I went back into Recovery and did a factory reset/wipe data and it finally got past that screen. Thanks again for your guidance and help. Any ideas as to what could have possibly caused the issue in the first place? I do want to re-root the device again and I am assuming my best bet is to flash a Stock ROM like you referenced with ROOT injected? What order should I follow, flashing a Stock w/Root injected...and then the Recovery of choice? Or vice-versa? What do you recommend?
Again, your timely responses were greatly appreciated. Was really worried I would have to take it to ATT.
Click to expand...
Click to collapse
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Mr.Rageface said:
It could have been several things that could cause the ROM to do that. I recommend that you make sure that your Bootloader is up to date and then go from there. Download the newest CWM, do a backup of your current rom so that you can flash back to it if you phone messes up. Then when you try to install a new ROM make sure you Wipe: Data then Cache, then Dalvik Cache in Advanced then Format /System. Then from there Install the new Rom, then install the correct GApps, then wipe Cache and Dalvik cache then Reboot into System. It takes messing up a few times to get it right but as long as you follow the guides pretty close and keep a good backup that you know works or keep the knowledge of how to Inject the Stock Rom to your phone when it messes up you shouldn't have much to worry about.
Mr. Rageface
Click to expand...
Click to collapse
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
DroidJay123 said:
Sounds good. Thanks for the info. Obviously the device is not currently rooted or did the Factory Rom file you gave me have root injected? Do you have a recommended way of achieving Root with the Samsung SG3? Just installing a custom Recovery won't achieve Root, correct?
Thanks!
Click to expand...
Click to collapse
BTW, how can I confirm I have the most recent bootloader version? It looks like my phone's current baseband version is i747UCDLK3. I did download the boot_CWM_i747UCDMG2.zip file and put it on the internal storage. Do I just want to flash that file to update my bootloader?
Thanks again!
-Jay
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Mr.Rageface said:
Yea that is the newest baseband and yea you just flash it. As far as rooting the phone and everything I recommend this forum. http://forum.xda-developers.com/showthread.php?t=1725839 It has just about everything you could need to know!
Mr.Rageface
Click to expand...
Click to collapse
Thanks for the information. The phone that has been all screwed up and the reason I posted a thread in the first place is my gf's GS3. I have her's rooted again and running. I am going to update her baseband version and then install a custom ROM so she's up to 4.3.1. As far as mine goes, I have been fine. I myself also still have the outdated bootloader version. Is it ok to just flash that update for the bootloader without it doing anything wrong? I'm asking this since I'm rooted and running a custom ROM with no current problems. In other words, I don't want to end up saying "it wasn't broke, why did I mess with it" ? I did bookmark that thread you referenced in your last message. Damn that thread is LOADED with just about everything one would possibly need to know about Android and making it their own.
So my g/f accepted the OTA update today (not knowing obviously) and she got updated to 4.3 via AT&T, unfortunately!! I attempted to flash the latest Liquid Smooth ROM and I continue to get a FAILED message during installation. It mentions a bunch of bootloader numbers ( I am assuming the only ones this ROM is compatible with?) So is there any way to roll the bootloader back to a compatible one or just go a different route for the custom ROM?
Also, I attempted flashing the file to update my baseband yet when I so into the device, it doesn't show as having the updated version? Is there a different way of doing it or maybe a different file?
I'm not to sure about the troubles that may come about since your gf went with the 4.3 OTA but If I am not mistaken it will need to be downgraded before you try doing anything else to it and if it is not showing that you updated your bootloader on your phone I recommend grabbing the App called Root Checker to double check then look for another file, tho unless it failed it should have updated it or messed up your phone one.
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
aeneas1 said:
so i recently dove into rooting my s4 after first spending a lot of time reading this great board, thought i had a handle on it, thought things were going very well, but i've hit a snag, which came while attempting my first restore - i'm hopeful someone will give me a little help,
a little background:
1. before rooting i backed up my phone with titanium, also backed it up by copying all of its contents to my pc.
2. i followed the excellent "[SGH-M919] CF-Auto-Root" instructions and it worked without a hitch, it was a quick and easy process, no surprises.
3. confirmed that i was rooted using "root checker", all systems were go.
4. once the root was done i made another backup using titanium and sms backup. i also made a full system backup using online nandroid pro and, to be extra safe, i also backed up efs using efs backup tool.
5. i then moved some folders and files to my external card and once again backed up my phone as before, including to my pc.
6. feeling confident that i could now restore my system to its rooted stock state if things went south, i decided to flash my first rom with cwm, i went with cm11 m7 4.4.3 - i saved the cm11 and gapps zips to my external card using rom tool box pro, rebooted into cwm recovery, selected the two files, and flashed. i also did a data and cache wipe before doing so.
6. needless to say i was thrilled when cm11 loaded perfectly, it worked great, and it was just what i was hoping for.
7. having been bitten by the apparent ease of flashing roms, i decided to restore my system to it's pre cm11 state, to it's rooted stock rom state, and try another rom, rather than just flash another rom from cm11 - i wanted to make sure that returning to my rooted stock rom state would be a simple matter.
and that's where i've run into problems.
1. as i mentioned i made two system backups of my stock rom before flashing cm11, one right after i rooted my phone, and one after moving some folders and files to the external card.
2. after doing a wipe, i chose to restore the second backup, the one i made after moving files and folders, and it didn't quite work out - everything appeared to restore perfectly, but my device was immediately inundated with pop up warnings about stopped apps, i also got a persistent warning that the system had stopped responding as well, prompting me to choose between "wait" or "stop it". not only was the restored backup mired in popup screens, but it was impossibly slow, impossibly "laggy".
3. so i decided to restore the other stock backup, the one i made before i moved folders and files, and the results were the same, pop screens for apps not working, system warnings, severe lags, etc., identical to the first backup.
then i panicked.
1. i decided to flash my phone with the "[SGH-M919] CF-Auto-Root" file again, again with odin, hoping that it would put me where i started - i didn't stop to think that my phone was already rooted, that the file was was for unrooted phones.
2. not only did the reflash not work (my phone just booted as normal, as if the flash didn't get a chance to finish), but cwm recovery in boot mode was gone, replaced by what appears to be the andorid stock recovery screen, a screen with an animated dying/collapsing robot, - the screen was titled: "android system recovery <3e> and asked for an "update" from the external storage or cache.
3. not knowing what "update" it was looking for, i selected a backed system files (the first rooted stock rom backup i made, the second rooted stock backup i made, and even the cm11 file) - none worked.
4. i then downloaded a clean stock rom from cwm's website, converted it from zip to tar, and tried to flash it using odin with my device in upload mode, it didn't work either.
so how badly did i mess up my phone? any help would be greatly appreciated.
Click to expand...
Click to collapse
If it boots at all you didn't kill it.
Not sure what rom you got from the CWM site. They do recoveries, not roms. The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Skipjacks said:
f it boots at all you didn't kill it.
Click to expand...
Click to collapse
hallelujah!
Skipjacks said:
Not sure what rom you got from the CWM site. They do recoveries, not roms.
Click to expand...
Click to collapse
my apologies, i meant that i downloaded recovery files from the cwm website, not a rom files - i got them from https://www.clockworkmod.com/rommanager - i downloaded both (touch & non-touch) s4 t-mobile versions (6.0.4.7). i'm assumed those were recovery files?
Skipjack" said:
The ROM manager app does allow you to download roms, but you can't just convert those from zip to tar. That doesn't make them flashable in Odin.
Click to expand...
Click to collapse
again, my apologies - i meant that i downloaded *.img files, not zips, and converted them to tars for odin use. i used a batch file to convert them from img to tar, found at xda, here: http://forum.xda-developers.com/showthread.php?t=2281287 - it seemed to do the job, odin ran and reported success. wrong files? wrong conversion?
Skipjack said:
Here's what you do. Get the stock ROM from either here on XDA (use the search feature to find it) or from Sammobile.com.
Flash that in Odin.
Then you can start over.
---OR---
If you want to try to fix what you've got now, download CWM or TWRP RECOVERY (nor ROM) and flash that in Odin. Boot to recovery, wipe data and system, and flash any other rom you want. That will start you over with a fresh rom of your choice.
Click to expand...
Click to collapse
given a choice, i'd like to do what's bolded in red - but that's what i thought i was doing by flashing the cwm file i downloaded from the cwm website - but after the flash attempt it wouldn't boot into cwm, it would just boot into (i'm assuming") the stock rom i restored, which was a mess. i also unchecked auto-boot to see if that helped - but when i manually booted it didn't boot into cwm, it booted into the stock recovery, with the animated android.
i'll try downloading cwm from the sources you provided, and see if that does the trick. btw, why do you think i was able to flash the cm11 rom with (seemingly) perfect success, but wasn't able to restore either one of the full system (android) backups i made after i rooted my phone?
anyway Skipjack, thanks a ton for your assistance and i'll report back after i give your sources a try. fwiw, it sure is a great charge when a newbie like me sees a custom rom load for the first time, displaying a new ui as it boots, fun stuff.
Just download the ready yo flash tar files. Cwm has them. Twrp has them.
success Skipjack thanks to your generous time and assistance!
i ended up downloading the latest odin zip i could find and philz_touch_6.08.9-jfltetmo.tar.md5... my first try didn't take, with auto-reboot checked, my phone simply rebooted into the same problematic rom i had restored. i then tried it with auto-boot unchecked and manually booted when odin reported pass/success, and it worked. what struck me as odd was how long it took to flash, to report pass/success, around 3-5 minutes if i had to guess, a big difference compared to when i first used odin to root my phone with the["SGH-M919] CF-Auto-Root *.tar.md5 file - i'm guessing that's why it didn't work with auto-boot checked, just took too long?
anyway once i booted into philz_touch recovery i executed the wipe data/factory reset > clean to install a new rom command and then flashed the cm11 m7 (snapshot) rom, which i had flashed once before, right before i attempted to restore the stock rom it had replaced. and as was the case the first time around, it installed without a hitch and is running smooth and fast.
however now when i boot the phone, as soon as the cyanogen logo appears, very tiny text appears in the upper left hand corner which reads (i had to use a magnifying glass!) - it doesn't seem to effect the performance of he device but i'd like to get to the bottom of it, i've already searched and it appears to be a rather common issue.
kernel is not seandroid enforcing
set warranty bit: kernel
btw, i forgot to mention, when i purchased my sgh-m99 it already had 4.3 installed - when i flashed my first rom (cm11 m7) it included kitkat 4.4.2... could this be what caused my problems? did trying to go back to (restore) a 4.3 rom after flashing a 4.4.2 rom screw things up? can this even be done successfully?
and finally, at the risk of bugging the heck out of you, what roms do you prefer for your s4, assuming you have an s4? do you like aosp roms or touchwiz? does one type have a better reputation of being more stable? the primary reason i wanted to rot my phone was to get rid of a bunch of t-mobile / samsung bloatware, which i thought i could do by installing a lean custom rom. any suggestions, which are your favorites? thanks again Skipkack.
ouhned after
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
eclpsues said:
I'm not an expert in Android OS but I think this is not an error. It is more of a notification that the STOCK KERNEL has been change to a CUSTOM one.
Click to expand...
Click to collapse
Joku1981 said:
You are right.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2594483
aeneas1 said:
re the two lines of text i now get in the upper left hand corner of the screen whenever i boot, the kernel message:
kernel is not seandroid enforcing
set warranty bit: kernel
well after a lot of searching and reading, including coming across dozens of "fixes" and "solutions" that didn't seem to work for many folks, these two responses seemed to make some sense, what do you think?
http://forum.xda-developers.com/showthread.php?t=2594483
Click to expand...
Click to collapse
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Skipjacks said:
The tiny text on the boot screen is basically telling you that Knox has been tripped. You are right. It does not affect the performance of the phone.
Click to expand...
Click to collapse
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
aeneas1 said:
thanks skipjack... btw i'm really liking the cm11 m7 rom but, via the learning curve process, i've discovered it does not support wifi calling, something that apparently all aosp rom lack, guess i'll have to go with a touchwiz rom even tho the selection seems to be few and far between. also, is it possible to revert back to 4.3 once 4.4.2 has been flashed? seems like there's a lot of mixed opinions on this, altho in terms of those opinions it's hard for me tell who the pros are that should believed, and who the other guys are that really don't know. thanks again.
Click to expand...
Click to collapse
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling
Sent from my SGH-M919 using XDA Premium 4 mobile app
Kriptik210 said:
Once you are rooted you can flash any custom ROM 4.3, 4.4, 4.2, etc. and then go back to stock 4.3. And only TW ROMs allow wifi calling.
Click to expand...
Click to collapse
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
so if i'm using a 4.4.2 custom rom and want to restore a 4.3 backup i should be able to boot into recovery and restore from there? or would i need to do a 4.3 flash first, before restoring a 4.3 backup?
aeneas1 said:
very interesting... i guess i misunderstood the posts i read on the subject, maybe they were discussing whether or not you could revert to 4.3 from 4.4.2 on non-rooted phones, which i'm guessing isn't possible. anyway, as i mentioned previously, i fist rooted my 4.3 phone, did a full system backup (using online nandroid), flashed a 4.4.2 rom which worked perfectly, then tried to restore my 4.3 backup only to encounter a bunch of problems, thought going from 4.4.2 back to 4.3 may have caused the problems but i guess not?
Click to expand...
Click to collapse
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
serio22 said:
Did you wipe before you restored? And do not misunderstand this, you cannot downgrade firmwares once you go 4.3 and up, but you can downgrade the system, which is what you did with your backup
Click to expand...
Click to collapse
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
aeneas1 said:
thanks very much for the clarification, i was under the impression that firmware and system were somewhat synonymous in this context, i.e. if you upgraded firmware you were in effect upgrading the system, but i see that's not the case, again thanks. and yes i did do a full wipe before trying to restore the backup, was i not supposed to?
Click to expand...
Click to collapse
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it. And you should not experience any issues restoring your back up. What were this problems?
btw serio22, do you have a favorite tw rom?
Yea serio22, what is your favorite TW ROM?
Sent from my SGH-M919 using XDA Premium 4 mobile app
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple app not working popups that made navigating almost impossible. well now when i try to restore it fails and i get the following message:
checking md summs...
md5 mismatch
serio22 said:
Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware.
Click to expand...
Click to collapse
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
btw, fwiw, - now that i'm up and running thanks to skipjacks help, i decided to try restoring my 4.3 backup again. as i mentioned, when i tried this in the past it would restore to the same state as it was before but it was virtually unusable because of severe lags and multiple "app not working" popups that made navigating almost impossible. but now when i try to restore the 4.3 backup it fails and i get the following message:
checking md summs...
md5 mismatch
update:
well it looks like the *.md5 file was pointing to my internal drive rather than external which is where i had moved the 4.3 backup (and apparently the *.md5 file didn't update or account for the move), anyway i copied the backup to my internal drive and, viola, no more md5 mismatch errors. more importantly, it restored the 4.3 backup perfectly, in the exact same state as before, without all of lagging and pop up issues i was having before, so i'm one happy camper! not sure what i did the first time around, but all is good now, for he time being, sure wish i knew what i mucked up to cause the problems in the first place, i really have no idea, other than being a newbie at this. also, fwiw, the tiny text in the upper left hand corner that appears during boot (kernal message) no longer appears now that i have restored the 4.3 system backup... fwiw2, i'm liking the philz_touch_recovery but it sure has taken some getting used to, the commands are so close together and the thing is so sensitive, very easy to accidentally select the wrong option, and some of the wrong options aren't too friendly if it wasn't what you had intended to select.
aeneas1 said:
but the cm11 rom zip i flashed included 4.4.2, before flashing i was using 4.3 - so didn't i update (or change) both the system and firmware?
Click to expand...
Click to collapse
Read my previous post more closely below. Good to see you up and running though! And no I don't have a favorite tw Rom
serio22 said:
Updating firmware does update the system. Based on your previous comment the only thing you did was update the system by flashing a ROM which only contains the system, data, and kernel, so you can still flash the 4.3 firmware. Firmware consists of bootloader, recovery, modem, and system, what you cannot downgrade is the bootloader, the flash will fail every time because it will try to downgrade it.
Click to expand...
Click to collapse