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.
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
riazrahman said:
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
Click to expand...
Click to collapse
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Higgs_Boson said:
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Click to expand...
Click to collapse
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
riazrahman said:
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
Click to expand...
Click to collapse
Sorry. After re-reading your post, I do see where you mentioned switching to PhilZ. However, please make sure that you have the latest version of PhilZ (which can be found at the link I previously provided).
After reading up on MerkMod, I have no reason to believe that ROM to be the cause of your issues. It is OMNI ROM-based and I have run OMNI ROM on my device without any issues. I, personally, use CM11 as my daily driver. But, as long as you are using the latest PhilZ recovery and flashing D2LTE ROMs to your device, there should be no issue. Also, make sure the GAPPs package you are using matches the Android version of the ROM you are flashing (e.g. 4.4.4 GAPPs --> 4.4.4 ROM)
If you download the .MD5 version of PhilZ, you can flash that via ODIN. Good luck to you.
Also, forgot to mention it in my previous post, but congratulations in advance on your engagement!
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
CNexus said:
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
Click to expand...
Click to collapse
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
riazrahman said:
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
Click to expand...
Click to collapse
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Higgs_Boson said:
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Click to expand...
Click to collapse
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
riazrahman said:
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
Click to expand...
Click to collapse
The only thing that repartitioning will do is restore the memory partitions in your phone in the event that one of the partitions became corrupted.
This is essentially what a PIT would be restoring:
Code:
sprint # cat parted.txt
cat parted.txt
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8192s 131071s 122880s modem
2 131072s 131327s 256s sbl1
3 131328s 131839s 512s sbl2
4 131840s 132863s 1024s sbl3
5 132864s 136959s 4096s aboot
6 136960s 137983s 1024s rpm
7 137984s 158463s 20480s boot
8 158464s 159487s 1024s tz
9 159488s 160511s 1024s pad
10 160512s 180991s 20480s param
11 180992s 208895s 27904s ext4 efs
12 208896s 215039s 6144s modemst1
13 215040s 221183s 6144s modemst2
14 221184s 3293183s 3072000s ext4 system
15 3293184s 28958719s 25665536s ext4 userdata
16 28958720s 28975103s 16384s ext4 persist
17 28975104s 30695423s 1720320s ext4 cache
18 30695424s 30715903s 20480s recovery
19 30715904s 30736383s 20480s fota
20 30736384s 30748671s 12288s backup
21 30748672s 30754815s 6144s fsg
22 30754816s 30754831s 16s ssd
23 30754832s 30765071s 10240s grow
Info credit: http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html
Hence, I have no reason to believe this would help you.
I thank @frantisek.nesveda for his Agnostic-kernel - partition independent kernel flasher on which I base this. I also thank everyone he thanks. Additionally, I thank anyone who posted about F2FS and formatting partitions. I read a lot of threads and I’m sure I gleaned something from everything I read.
For now this has to be done after flashing your preferred firmware (ROM). I recommend you make all your desired changes especially changing kernels.
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. If you put it on your internal card it needs to be outside the /system and /data partitions because you'll lose them during formatting.
Also, I have only tested this on PhilZ Touch 6.58.9 recovery. I would appreciate anyone testing on other recoveries if you find one that supports f2fs.
If you are not on PhilZ 6.58.9, flash the zip and reboot to recovery.
Make a full back up of your ROM.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back. This may not be the case with this latest PhilZ.
Format the partitions to f2fs.
It is in "Wipe and Format Options", then "Custom Format Options" then "Toggle f2fs <-> ext4 migration"
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
See warnings in post #2
I include a testF2FS zip to confirm the formatting.
Then use custom restore to get the data and/or the system from the backup. You can skip cache since it gets rebuilt.
Then flash GS3-F2FS-kernel-fstab-Fixer to adjust the kernel boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
It appears to only work with the PhilZ recovery I built. If someone finds another please let us know.
Also, it does not work on TouchWiz ROMs. If someone finds one that it does work on please let us know.
Do not use the phone setting Factory Data Reset
XDA:DevDB Information
F2FS, Tool/Utility for the AT&T Samsung Galaxy S III
Contributors
RoryB
Version Information
Status: Beta
Beta Release Date: 2014-11-13
Created 2014-10-21
Last Updated 2014-12-06
Reserved
Latest files on Android File Host
Remember, to format data you pick /sdcard. Also, this will remove everything on your internal card.
Do not factory reset through the phone settings. This appears to format as ext4 and does not keep your formatting.
If you do you would need to try the f2fs fixer before rebooting. I have not so let us know how it goes if you try.
[OLD WAY]
For now this has to be done after flashing your preferred firmware (ROM).
Copy the files to your sdcard where you typically put flash files. I recommend an external card, because this is the only way I do it and I have not tested the other way. Also, I have only tested this on PhilZ Touch 6.48.4 recovery. I would appreciate anyone testing on other recoveries.
Make a full back up of your ROM.
It seems it is best to get everything the way you want before the back up, including any kernel changes.
I also recommend you have an Odin based recovery plan. During my trials I ended up with a blank screen and used Odin to get back.
Flash the zip file for what format you want to change. I include a testF2FS zip to confirm the formatting. For some reason it sometimes takes more than one try to format the partitions. Sometimes rebooting recovery helps before trying to confirm the formatting.
NOTE: Sometimes the phone reboots on its own while formatting. Be prepared to press the home and volume up buttons for two vibrations to get back to recovery. The first is the final power down and the second is the powering up. Remember to wait for the blue text in the upper left corner.
Then I use custom restore to get the data and/or the system from my backup. You can skip cache.
Then I flash GS3-F2FS-kernel-Fixer to adjust the boot image to support the new formats.
This only fixes the fstab and if the kernel does not have f2fs support it will not work. If they are getting upstream changes they should have it.
As always, no one is responsible for what happens to your phone. Everyone does this on their own and at their own risk.
Please do NOT mirror these files.
yahoo!!!! thank you for what had to have been alot of research , testing , and i cant imagine what-nots.:victory:
will try out tonite and report back
err on the side of kindness
Saving my response until after class... Thus is awesome
Sent from my HTC One_M8 using XDA Free mobile app
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
TheSchatz said:
Look forward to testing tonight! Will post with results when I have them
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Two different phone both liquid ROM. F2fs all versus f2fs none
Thanks again Rory!!
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
aircooledbusses said:
I tried some stuff before with formatting partitions in twrp and it always failed. Even the newest 8.whatever just freaks out with unrecognized file system. I've not been a fan of philz ever before, but since that's what is working I Will adapt
Click to expand...
Click to collapse
I guess Philz it is, as latest CWM failed in the same fashion.
Yeah, same here with CWM.
Running vanilla CM11. Took a full nandroid, formatted system, cache, and data with Philz. Restored nandroid, installed latest Quantum kernel and flashed the kernel fix.
Everything is up & running, but performance has downgraded. AnTuTu score down by about 20%. I have seen other f2fs discussions that said it needs time to settle in, so I'll let the phone on all night and check it in the morning.
Just some more scores I am not too sure what to make of. But obviously f2fs has the edge.
Html5 test seems a bit fictitious but again shows f2fs showing some advantage....... If more birds is a good thing that is.
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
mrrocketdog said:
one more to confirm: failed with twrp 2.6.3.1 . tried multiple times. running Q v3.66 with appropriately dated kernels = QK / dkp / BMS .
ohh philzzz , where are you ? time to come and play.!
err on the side of kindness
Click to expand...
Click to collapse
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/
I used one for d2lte. Please ignore the update to latest binary message
TheSchatz said:
Didn't work for me in TWRP, with latest Carbon Nightly. Just finished in about two seconds, and the test zip failed, indicating nothing changed.
Next step is a CWM I guess!
Sent from my CARBON-SGH-I747
Click to expand...
Click to collapse
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flash quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
RoryB said:
Remember, sometimes it takes a few times. I've been trying things like adding sleeps to "rest" between each format command. It did not help. I sometimes had to format, reboot to recovery, format again and then maybe it showed up as changed.
I think I got things mixed up. I have to set up boot image to support the new format and then flask quantumkernel. I"ll update the first post.
Yup, I use this one https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.zip
Click to expand...
Click to collapse
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
TheSchatz said:
Well, now I can't get past the kernel splash. Philz finally sees everything as f2fs, but I can't mount data at all... I've managed to royally screw up everything, lol. Off to Odin, I'll try again sometime but it's a no go for now.
Thanks for the files though, I'm really excited for the opportunity!
Click to expand...
Click to collapse
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
aircooledbusses said:
Yes, formatting is a bit wonky but the test zip file is very helpful. After formatting I'd run the test zip till desired partitions showed f2fs and not unknown. I also rebooted recovery before restoring. That custom restore really messed me up and I had to have only one back up to keep stuff straight. Then the fix file and a reboot. I only flashed qk 10.11 after it was all running.
Don't know if This will help anyone but it worked for me.
Click to expand...
Click to collapse
Eventually everything read f2fs, but I wasn't doing any data restoration. I was just going to start with a fresh rom install, but that's when I was stuck on the kernel splash with no adb. I'll probably try again tonight after work, maybe I'll have better luck!
Sent from my CARBON-SGH-I747
Many ROMs have format built into their updater script and that would undo your format to f2fs unless the ROM is written to support it.
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
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
A Lineage OS rom is still under development and not released yet. Have you tried flashing the stock image (6.2.7.1)? Flash this in recovery, to see if it fixes the update error. You may need to flash Magisk to be rooted again. And this stock image WILL NOT overwrite TWRP. The prerooted roms that are released have Magisk built in so there's nothing different between those and the stock image in which has no root at all. Let me know if you have any questions!
Stock Image for Fire TV Stick 4K: https://drive.google.com/open?id=1LlOFUO8o_8GKm-kQLR9QCMmql2Zyu8W8
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a pre-rooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
From what I have seen, the tutorial for flashing the prerooted is really a dirty flash, and certainly from my experience (where I forgot to reset the device before flashing the image) all my apps were still there.
I'm sure you can wipe your system & data partition from TWRP, and then flash the image.
The only problem I can foresee is that the pre-rooted image might not be a full image which would cause your Firestick not to boot.
I suggest you head over to the pre-rooted image thread and ask if it's ok to wipe those partitions and also what the actual commands are.
I'm curious also - just for future reference....
p.s I just found this
https://twrp.me/faq/openrecoveryscript.html
which lists TWRP's commands, Just check first to see if it's safe to wipe those partitions.
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
I think the system partition would be the important one to wipe, data is mostly user data from what I remember.
If Skel40's link is a full image (as the prerooted one i might be), then maybe do all the wipes and try that one 1st..
Normally when I use TWRP I don't dirty flash, and I wipe system,data,dalvik,cache...
Good luck with whatever you try
Retch_100 said:
Hello,
i've had this issue with the stock firmware so i thought installing twrp with a prerooted image should do it, but the same issue appears. After the language and network setup, the update (searching for an update) goes wrong. I've got another 2 4k's here and they work, so it's not network related.
Installing twrp and the rooted image was quite easy, nice to see twrp running on these devices.
But does a lineage or another custom rom for the 4k actually exist? I think with a clean rom the error would be gone.
I don't know how to make lineage for this device, i. just know how to install it
I've attached an image, maybe someone has an idea.
Click to expand...
Click to collapse
Retch_100 said:
Okay, i will install it tomorrow. Is there a Source to the lineage Development? The Stick is unusable for me, so i Would install anything to Pass the error.
@tinybilbo
Good question, i didnt Know Either what to do so i Wiped cache and dalvik and data, but That should be considered as a Dirty Flash thought, i will ask there.
@Skel40
What to Wipe before flashing?
Click to expand...
Click to collapse
You need to wipe system, data, dalvik-cache, and cache before flashing. Upon boot up after flashing 6.2.7.1, it skips the updates, I have a backup if needed!
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Retch_100 said:
I wiped all Partitions and Flashed the Image, but it searches for backups and the error appears. Could you send me the Backup? @Skel40
Click to expand...
Click to collapse
You wiped everything (data, system, internal, cache, dalvik). There is nothing else, if you are flashing the full stock upgrade image. The device finds remote, connects to bluetooth, then finds Wifi, connects to wifi. Then the device errors (when checking for an update). Since you bought this device used, i highly suspect the device is blacklisted. Firestick 4k's are on sale for $25 again. I would cut my loses and hope someday for a custom (you can ask for a copy of the buggy one diegocr and Rortiz2 over in the tank 12.1 thread. But it is likely unusable at this time.
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Retch_100 said:
Okay thank you @Michajin
What do you think, would be installing TWRP on one of the others and restoring a backup from them onto the broken one help?
Click to expand...
Click to collapse
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Michajin said:
I don't think so. I believe it is sending its serial number to amazon when it connects to the internet. There used to be a work around that would bypass registration, but i believe that was blocked about a year ago. Maybe someone on here knows a work around since you have access with TWRP (file manager), If it were me, i would find the update files in TWRP and rename or delete them... i think they are in the root/system folder. Since you have a full backup i dont see much risk. If it fails to boot or work, just restore your system from a backup.
The files should be called:
device.software.ota
com.amazon.device.software.ota.override
Click to expand...
Click to collapse
Okay thanks I will see.
BTW: the Stick does not have any value to me anymore, so bricking it would be okay if I learned something this way
But it'd be better if the Stick could be resurrected to work as a Stick.
Maybe anything of this.
Pass OOBE:
==========
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
adb shell settings put secure install_non_market_apps 1
adb shell settings put global adb_enabled 1
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
pm disable com.amazon.tv.oobe
Your fire stick blacklisted by Amazon.