Related
My vzw nexus has been running mRom version x.x for sometime. I went to install the upgraded 4.2 rom via clockworkmod, (wipe cache and dalvik, flash over current rom) and it appeared to install successfully. However, when I rebooted I saw the lock screen for a split second and it just started to boot loop. I rebooted back into recovery and wiped all data and tried to reinstall the rom via through the new 0 partition, but I get the error symlink: some symlinks failed
E: Error in /sdcard/0/mRom_v3.0_JOP40C.zip (status 7)
I think that this may have something to do with the multiple users in 4.2, but don't quote me on it. I cannot get my computer to recognize my phone, when I go to mounts in cwm I can mount everything except the sdcard, although I think this problem was evident before I flashed. Any suggestions? I could try to restore to stock using galaxynexusrestore-- http://forum.xda-developers.com/showthread.php?t=1743939 but I have not tried it before so I cannot speak to weither it will work or not.
HELP!
Always always wipe data when changing an Android version. Unless it comes via OTA, which is specifically designed to fix all the little problems that will arise.
As to how to fix the problem, flashing a factory image
http://forum.xda-developers.com/showthread.php?t=1626895 will probably work. Just follow the rules for Toro. The toolkit you linked may work, but it's generally a better idea to not use them and actually familiarize yourself with how to fix things yourself, you'll be less likely to make mistakes in the future.
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Misread OP.
ironerd said:
Same thing happened to me.
when i try to restore from backup Clockwork can't locate the backup file because the root file structure has changed to \0.
Is there an update to Recovery that fixes this?
Help!
Click to expand...
Click to collapse
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
same problem, stuck at JB logo
Marisa said:
Clockwork dev said he knows about the issue and is working on a fix.
TWRP already has a patch out that solves the problem. If you decide to temporary move to TWRP it can be flashed through fastboot or Goomanager. CWM and TWRP backups are not compatible however.
http://teamw.in/androidmultiuser useful reading for how TWRP fixed it.
Click to expand...
Click to collapse
I was running stock JRO03O with Clockwork Recovery Mod and decided to flash the JB 4.2 ROM from Grouper (http://forum.xda-developers.com/showthread.php?t=1993545 - I can't post there since I'm too new).
The update must have succeeded, because I can see the new 0/ partition on my phone, but it won't boot past the "X" logo. I can boot into CWM and try various things, but of course because of the data structure changes, I can't actually recover to my last save. When I'm home, I'm hoping I can get the CWM backup off my phone to restore later, but without a terminal in CWM, I can't try to fix the path.
It's nice to hear that CW is working on a fix - I hope it's retroactive (I mean, helpful to those of use who already screwed up). Also, I've never flashed anything but OTA, so I didn't realize I needed to wipe data before flashing something that's supposed to be almost stock. I guess it matters how different from stock the ROM actually is.
What's next? I'll try to interface with my PC at home. If others have this problem, I'd be happy to hear your success (or fail) stories. I'll share mine once I've tried it.
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Koush
When trying to restore CWM backup move previous backups AND blobs folder to /data/media/clockworkmod if the folder does not exist simply create one or if unsure just go to recovery and make new backup, it will create necessary folders for you then move (or copy to be safe) files to location.... The blobs folder is what I was missing and why I kept getting error while trying to restore.
Click to expand...
Click to collapse
This should help your problem solving for the moment, if you're familiar enough with ADB to move the files that way it shouldn't take very long at all
thanks, and update of my status
Marisa said:
The issue with non-OTA version updates is that the OTA is specifically designed to know what little bits and pieces need to be updated, removed, or left alone.
Flashing a ROM is usually intended as a fresh slate, as the dev cannot know exactly from where you started. Basically without the wipe, you could end up with old files loitering about the system and making it do things incorrectly at boot.
Click to expand...
Click to collapse
Thanks for the extra insight. I wrestled with my phone all night and finally got it back to 4.1.1 (JRO030). Along the way I screwed up my adb or fastboot drivers, and for all my efforts I couldn't get any of my nexus toolkits to recognize the phone as in fastboot mode. Adb was fine, but fastboot was a no-go. I moved to a fresh computer after someone else had success with that, and read up on how to do a manual (adb command line) flash to factory image.
Now that that's done, I'm hoping I can restore from CWM to get back to where I was. If not, then yuck, but I'm optimistic.
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
so, as the title kind of says, i would like to flash the Android 5.1.1 - Unofficial Cyanogenmod 12.1 onto my AT&T GS3, however i can't seem to find any clear instructions on how to do so, mostly when it comes to rooting as all the rooting guides that i've found do not list my build number as supported
KOT94H.I747UCUFNJ2 with android version 4.4.2
any help would be appreciated, thanks
If you want to install a custom ROM such as CM12.1, you do not need root.
You need to install a custom recovery such as TWRP or CWM so you can flash a custom ROM, supersu for root if necessary, and gapps.
logoster said:
so, as the title kind of says, i would like to flash the Android 5.1.1 - Unofficial Cyanogenmod 12.1 onto my AT&T GS3, however i can't seem to find any clear instructions on how to do so, mostly when it comes to rooting as all the rooting guides that i've found do not list my build number as supported
KOT94H.I747UCUFNJ2 with android version 4.4.2
any help would be appreciated, thanks
Click to expand...
Click to collapse
Honestly this is a pretty helpful guide
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new/
There are a few versions of ODIN floating around but I would use the one in the link and if that won't work then check out one of the others but I would recomend getting the latest version of TWRP (which is the custom recovery I'd recomend and I'd recomend getting the latest version from here: https://twrp.me/devices/samsunggalaxys3att.html
If you ind you're not booting into TWRP then do the following steps:
2) Hold down Volume Down, Center Home, and Power buttons together until you see a warning screen
3) Open Odin but uncheck reboot, install TWRP
4) After Success, remove battery and unplug usb
5) Hold down Volume Up, Center Home, and Power button together
6) Go to Advanced File Mangaer and Mount System Partition
7) Go to File Manager and delete:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
8) Install SuperSU
Hope that helps
audit13 said:
If you want to install a custom ROM such as CM12.1, you do not need root.
You need to install a custom recovery such as TWRP or CWM so you can flash a custom ROM, supersu for root if necessary, and gapps.
Click to expand...
Click to collapse
ok, i don't suppose you know of a good guide for installing CWM?
or would TWRP be easier to install, as i've read in some posts that CWM can't be installed via odin because of it being in a .IMG file instead of .tar
EDIT: @Matt K
so TWRP would be easier basically? ok, sounds good to me, thanks
EDIT2:
so question, i currently have TWRP installed as the recovery, and CM12 nightly installed for the rom, i took a backup of my phone from within twrp right before i did any factory resets or flashing of roms of any kind, if i wanted or needed to get back to stock touchwiz as my phone was before cm12 would restoring from the backup do that? or would there be something else i have to do to go back to touchwiz
logoster said:
EDIT2:
so question, i currently have TWRP installed as the recovery, and CM12 nightly installed for the rom, i took a backup of my phone from within twrp right before i did any factory resets or flashing of roms of any kind, if i wanted or needed to get back to stock touchwiz as my phone was before cm12 would restoring from the backup do that? or would there be something else i have to do to go back to touchwiz
Click to expand...
Click to collapse
On occasion it is necessary to format the internal sdcard when you wipe data/dalvik/cache prior to flashing stock TW when coming back from a LP rom. Many who don't find they are stuck at the AT&T logo when booting.
ok, so i needed something from before cm12 today, did as you said, factory reset, then format data, i then restored from backup
while i did get into android, i kept getting all sorts of messages of "APPNAMEHERE has stopped" and after going to settings i couldn't get back to the home screen, everything was broken
decided to just do what you said, except this time flash http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006 this instead (and yes i am sure my phone is ucufnj2) and it always got stuck at the end of the AT&T boot logo, so i tried your way again, except this time the flash failed and it said something about "E: command not found", i was able to reflash cyanogenmod though, but i'd like to be able to get my touchwiz back
you know what, don't want to deal with this, how do i get my phone back to normal, i've never had a problem with touchwiz, it's not slow (or at least not nearly as slow as people say it is) and it worked pefectly fine for me, so how the hell do i get this backup to work correctly (i did have some apps on my external sd card, but AFAIK they weren't removed as the same amount of storage space is still being used
according to the TWRP log this is what's happening:
Code:
I:operation_start: 'Flashing'
Installing '/external_sd/roms/samsungofficial/UCUFNJ2_rooted.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Register_libbootloader_updater Qcom msm8960
Register_libbootloader_updater Qcom msm8960
no file_contexts in package
Creating filesystem with parameters:
Size: 1572864000
Block size: 4096
Blocks per group: 32768
Inodes per group: 8000
Inode size: 256
Journal blocks: 6000
Label:
FLEX_BG size: 16
Blocks: 384000
Block groups: 12
Reserved block group size: 0
Labeling /system/ as u:object_r:system_file:s0
Created filesystem with 11/96000 inodes and 12038/384000 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
Wipe(discard) takes 1 secs and 591424 usecs.
Extracing stock system.img... Please be patient, this will take several minutes.
minzip: zlib inflate call failed (zerr=-3)
minzip: Can't extract entry to file.
package_extract_file: install error 6
script aborted: assert failed: package_extract_file("system.img", "/dev/block/mmcblk0p14")
E:unknown command [install_error]
assert failed: package_extract_file("system.img", "/dev/block/mmcblk0p14")
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/external_sd/roms/samsungofficial/UCUFNJ2_rooted.zip'
Error flashing zip '/external_sd/roms/samsungofficial/UCUFNJ2_rooted.zip'
Updating partition details...
I:Data backup size is 6126MB, free: 5866MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1
ok, managed to get that unufnj2 rom to flash, i guess the one on my phone got corrupted somehow and deleting then re-copying fixed it, however i still only get a black screen with a bunch of "APP Has stopped working here"
that and the power options are the only things that work from touchwiz anymore, however cm12 still installs and works fine, so obviously it's not my phone, so what the heck is wrong with touchwiz
Before installing a 4.4.2 rom, try doing a full wipe from twrp before restoring a kk backup or installing a kk rom.
The full wipe recommended by audit13 is more than wiping /data, /cache, /dalvik-cache. It includes formating the internal sdcard, as previously recommended. A factory reset and wipe of data does not do the needed function.
I did do a full wipe, twrp was literally the only folder still on the internal storage, at least as far as I could tell, are you saying I have to use that wipe buttton and select everything except external, and uab otg?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
logoster said:
I did do a full wipe, twrp was literally the only folder still on the internal storage
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
Click to expand...
Click to collapse
The other thing I have seen a few say was necessary for them to be able to flash and boot back into stock TW after returning from 5.1.1 was to factory reset from the stock recovery. You can find a flashable zip of the stock recovery in the NJ2 thread by enewman17.
dawgdoc said:
The other thing I have seen a few say was necessary for them to be able to flash and boot back into stock TW after returning from 5.1.1 was to factory reset from the stock recovery. You can find a flashable zip of the stock recovery in the NJ2 thread by enewman17.
Click to expand...
Click to collapse
first off, sorry if i come off like an asshole in any of posts, i tend to do that a lot when i don't mean to
second off i edited the post you replied to, by full wipe does that mean i have to use the "wipe" button and choose everything except USB-OTG and external storage?
and if you did but it still doesn't work, for recovery stuff, i'm assuming i'd have to flash touchwiz first, THEN stock recovery (and i'm assuming recovery from odin) yes?
logoster said:
first off, sorry if i come off like an asshole in any of posts, i tend to do that a lot when i don't mean to
second off i edited the post you replied to, by full wipe does that mean i have to use the "wipe" button and choose everything except USB-OTG and external storage?
and if you did but it still doesn't work, for recovery stuff, i'm assuming i'd have to flash touchwiz first, THEN stock recovery (and i'm assuming recovery from odin) yes?
Click to expand...
Click to collapse
Not a problem, but thanks.
Yes, all but external storage and USB_OTG.
I think enewman17 actually has recovery flashable TW stock roms and a recovery flashable stock recovery; here for NJ1 and NJ2 and stock recovery. The ROMs are pre-rooted.
actually already knew about the roms, but i was actually looking about XDA and found this:
http://forum.xda-developers.com/galaxy-s3-att/development/s3-r3born-rom-based-likewise-s5-t3106075
this should be flashable via TWRP yes? the reason i'm asking is that i would like to do touchwiz, but at the same time the s3's is a bit out of date by now, this seems to be a combination of touchwiz from the s5, and s6 all ported to the s3, however in the requirements it says CWM recovery, so i'd like to be sure it will work via TWRP before trying it
logoster said:
actually already knew about the roms, but i was actually looking about XDA and found this:
http://forum.xda-developers.com/galaxy-s3-att/development/s3-r3born-rom-based-likewise-s5-t3106075
this should be flashable via TWRP yes? the reason i'm asking is that i would like to do touchwiz, but at the same time the s3's is a bit out of date by now, this seems to be a combination of touchwiz from the s5, and s6 all ported to the s3, however in the requirements it says CWM recovery, so i'd like to be sure it will work via TWRP before trying it
Click to expand...
Click to collapse
It should work fine with TWRP, in fact it has been so long since CWM was updated that it won't install all ROMs. I have been watching that thread for a bit also and am waiting until he finishes the update he is working on. If you like the R3ARMED rom because of the S5/S6 bits, you may also like the Likewise ROM.
ok, so now the only thing i'm wondering is how do i tell if i'm on the 4.4 modem/bootloader?
the last stock rom from OTA i had installed was from august, and android version 4.4.2, according to download mode my boot loader is 3
whatever that means i have no idea
logoster said:
ok, so now the only thing i'm wondering is how do i tell if i'm on the 4.4 modem/bootloader?
the last stock rom from OTA i had installed was from august, and android version 4.4.2, according to download mode my boot loader is 3
whatever that means i have no idea
Click to expand...
Click to collapse
There is an app in the Playstore, Phone Info *Samsung* by vndnguyen.
If you have Terminal Emulator on your phone you can tell with two commands:
Code:
getprop ro. bootloader
getprop | grep version.baseband
The 4.4.x versions for the i747 are NE4, NJ1, and NJ2.
ok, so everything go's good until it reboots after installing rearmed, i see the TWRP style samsung galaxy s3 logo, then my blue notification light comes on and pulses as if it was booting, then it reboots again but this time into recovery mode, i factory reset and wiped data as the instructions said to, and i did get some armoa installation thing (one part of which also asked me to choose a kernel, i chose the one that said "stock ob3 kernel" as i don't know what the other ones would do)
the installer even said that battle frontier 4.1 rom was installed successfully, but like i said earlier in the post, nothing but the blue notification light
any idea's? (atm i'm trying to restore from my backup again after doing a full wipe, so that i have something to use until i get the rearmed thing working)
huh, i've noticed something, cm12 is the ONLY rom that seems to want to work, tried likewise, it stayed at the samsung boot logo for ages, i did eventually get rearmed to correctly install, but it has the same problem as likewise, touchwiz doesn't seem to like working at all anymore, while cm12 installs perfectly every time
what the heck is wrong with my phone
logoster said:
huh, i've noticed something, cm12 is the ONLY rom that seems to want to work, tried likewise, it stayed at the samsung boot logo for ages, i did eventually get rearmed to correctly install, but it has the same problem as likewise, touchwiz doesn't seem to like working at all anymore, while cm12 installs perfectly every time
what the heck is wrong with my phone
Click to expand...
Click to collapse
My first guess is that CM12 is not the only rom that will work. Try another 5.1.1 based AOSP or CM ROM to verify this.
Going back from a 5.1.1 ROM to a KitKat TouchWiz ROM will probably require formating the internal sdcard. Selecting wipe in recovery is not the same as formating. Did you actually format the internal sdcard? If formating alone doesn't do it then installing a stock recovery and factory reset from within the recovery should fix things.
dawgdoc said:
My first guess is that CM12 is not the only rom that will work. Try another 5.1.1 based AOSP or CM ROM to verify this.
Going back from a 5.1.1 ROM to a KitKat TouchWiz ROM will probably require formating the internal sdcard. Selecting wipe in recovery is not the same as formating. Did you actually format the internal sdcard? If formating alone doesn't do it then installing a stock recovery and factory reset from within the recovery should fix things.
Click to expand...
Click to collapse
there doesn't seem to be a format button in twrp other then the format data button
hi,
today, i tried to update my op3 from lineageos 14.1-201703202 to the new lineage-14.1-20170309 with twrp. but i when flashing, i get error 7.
i already had the same issue the last time and could solve the issue with first flashing oxygen 4.0.3.
i guess when i flashed oxygen 40.3, i got the newest firmware and modem (and still have it, of course). why do i get this "error 7" again?
i thought it was because of the "false" twrp (i have 3.0.4-1) and then i made the big mistake to update twrp to 3.1.0.0. this version of twrp wiped my phone. thanks good, i had a one day old full nandroid backup to restore phone including going back to twrp 3.4.0-1.
but what should i do to get the newest lineageos flashed?
i am a absolute beginner and dont have deeper knowledge, but i am already a little bit angry that everytime i want to flash an lineageos update, i get into trouble. is this normal with oneplus3 and lineage? what am i doing wrong?
thanks a lot for your help.
best regards,
flotsch1
I have a similar issue with LineageOS updates.. I flashed LineageOS14.1-20170208 nightly on my Oneplus 3 with twrp-3.0.4-1, however I cannot upgrade to newer nightly releases. For some reason they always fail to install, it actually boots on recovery mode but installation using twrp quickly fails and I cannot even see the exact error it throws. Any ideas?
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
jim262 said:
If you do a search, you will see how to fix this error. It is an error in the script and you simply have to remove a couple lines.
Click to expand...
Click to collapse
It isn't, it is a check for firmware... Could be that lineage is using OB12 firmware now..
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309.
But there's new fw/modem here https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Install latest and flash new lineage. No error 7 here!
kebeil said:
Same here, had the error 7 when i flashed 20170302. Fixed it with a new modem firmwae installation.
Now i have the same error again installing 20170309. But theres no new fw/modem ... https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Click to expand...
Click to collapse
The fix is mentioned in the official weekly lineageos thread. basically you need to factory reset, flash the zip file attached in the thread and then flash the latest lineageos nightly/weekly image, followed by wiping dalvik and cache. It worked for me anyway, although everything got wiped so I had to restore my apps from backup (I use titanium backup).
flashing the betafirmware was the solution for error 7, but please see my other tread explaing my gapps-problems after successful lineagos update.
Here is how you fix error 7 in TWRP. You simply edit the first Two lines in the updated script by deleting them. https://youtu.be/XkwSO_I9GfE
Earlier today I tried to reboot my BND-L24 into TWRP, but I got seriously stuck and have been unable to get unstuck ever since.
TWRP will not load. It starts to load and then gets stuck on the splash screen.
I have tried to wipe from (standard) recovery, but that doesn't work either.
I have tried to install several different TWRPs (fastboot seems to be working ok).
If I could just get into TWRP I should be able to restore the System partition. I had previously installed the Morfuz kernel, but I would have to be able to get into TWRP to restore the original kernel.
I'm seriously stuck. Any advice??
Thanks!
I dont understand. What do you mean by "seriously stuck?"
Use these TWRPs....
https://drive.google.com/open?id=18uHjW73Th8iYKIs5m_QgwleMIOjsZd7S
RECOVERY TWRP OREO 3.2.1
the file is automated. http://zipansion.com/2t6QB
https://forum.xda-developers.com/devdb/project/dl/?id=28883
TWRP will not load - it is stuck at the flash screen. I've tried several variants of TWRP and will try yours as well.
I've flashed the first one before without any luck. The second failed with "FAILED (remote: partition length get error). Didn't matter whether I flashed to recover-ramdisk or recovery, same error both ways.
egalambos said:
I've flashed the first one before without any luck. The second failed with "FAILED (remote: partition length get error). Didn't matter whether I flashed to recover-ramdisk or recovery, same error both ways.
Click to expand...
Click to collapse
it is recovery_ramdisk... that is the partition, not "recover-ramdisk" or "recovery"
I finally got into TWRP!!! Progress!!
I thought I had a good System partition backup, but apparently I don't.
How can I use TWRP to install a good System.img file that I do have?
egalambos said:
I finally got into TWRP!!! Progress!!
I thought I had a good System partition backup, but apparently I don't.
How can I use TWRP to install a good System.img file that I do have?
Click to expand...
Click to collapse
you should always use fastboot to flash .img files. at this point, i suggest you wipe internal storage, cache, dalvik and art cache, system, and data. then flash hurupdater and get back to stock.
I did that, except that I left the Data and the internal partition alone and it worked. I'm in the process of re-installing Magisk, etc., but, from what I can see, everything seems to be pretty much back to normal.
Thanks for the help! It was unbelievably frustrating. Can't believe I mixed up a dash with an underscore!
PS Do you have any idea why I was unable to do a System Update before I re-installed TWRP? I believe I was about as stock as stock can be at that point!
egalambos said:
I did that, except that I left the Data and the internal partition alone and it worked. I'm in the process of re-installing Magisk, etc., but, from what I can see, everything seems to be pretty much back to normal.
Thanks for the help! It was unbelievably frustrating. Can't believe I mixed up a dash with an underscore!
PS Do you have any idea why I was unable to do a System Update before I re-installed TWRP? I believe I was about as stock as stock can be at that point!
Click to expand...
Click to collapse
probably because the bootloader was unlocked. one way to install updates manually is using firmware finder app, if the update is approved.