edit: guess not.
Pixel won't boot with these mods...need to be made with the pixel framework-res.apk and SystemUIGoogle.apk
Caused a bootloop and I had to wipe data after restoring my normal files
Edit: I used two to move the files
Thread closed as no longer supported.
Related
If I do a factory reset from the menu in settings will that replace my build.prop file or will it remain the same In case your wondering I was editing what I thought was my build.prop but it was my backup.
Maybe we should start a library of stock files for occasions like this. I'm sure a generic build.prop will work fine to get it back to A100.
wildrat58 said:
If I do a factory reset from the menu in settings will that replace my build.prop file or will it remain the same In case your wondering I was editing what I thought was my build.prop but it was my backup.
Maybe we should start a library of stock files for occasions like this. I'm sure a generic build.prop will work fine to get it back to A100.
Click to expand...
Click to collapse
All that does is delete /data, /system remains the same, so no, it won't touch your build.prop. A nandroid restore or flash over will replace it.
Edit: wrong wording, it doesn't delete /data, just what's in it, the partition remains there. Not sure if it formats or just deletes the files there.
Tapatalked from my A100 - Flex Reaper RF1.
Okay thanks. I did find an old.build prop and it did not help. Thanks again
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
solidhound said:
I was wondering whether anyone has experienced the following:
I was on Team Sonic-Free GS3 v.3.0.0. Everything was setup the way i wanted it. I booted into Recovery and created a Restore point.
Right after, I did the following:
- Wipe Data/Factory Reset
- Wipe Cache partition
- Wipe Dalvik Cache
- Format /System
- Format /Data
- Format /Cache
I installed the latest Nightly from Cyanogenmod 10 (12.26). Initially I used an older version of gapps-jb but immediately flashed the correct one. Everything went fine. The system loaded and nothing seemed wrong. After some messing around I noticed it was a big sluggish on my phone. So I decided to restore the phone back to its original setting.
When I went to backup/restore and hit the Restore option, it told me that I had no recovery points! :crying::crying: At this point I started freaking out.
I tried to see if I could flash from the SDCard and I noticed one thing. This was in order to get to the main folder of the SDCard i needed to enter a folder named "0". All the files were there including my CMW recover file. Although it was on the card the recovery option was unable to see it.
After this I decided to do the following. I clean swiped again and installed the Free GS3 version i had on the SDCard already. I booted into the system and saw that the folder "0" was there but also in the main directory there were still folders. In the main portion of the card i loaded my copy of the recovery.
I went back into recovery and and tried again. The restore file was there! :good::good: I was able to recovery my original setup. Unfortunately, all of my pictures and music were still located within the newly created "0" folder. I just copied those back.
Can anyone explain why this happened? I'm very curious!
I do apologize if this has been answered before. I have done a search and have only found scenarios for the SDcard is not seen as mounted. (also dont know if the icons mean anything for the post)
*Update - Folder "0" cannot be deleted. Root explorer says "failed" and Windows Explorer says "Cannot delete 0: THe storage is write-protected". Any ideas on this also?
Click to expand...
Click to collapse
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
milky1112 said:
Was it registering a different recovery version when you flashed CM10 from the FreeGS? If so that would be why it didn't register the backup that you made. (I had this issue or similar to on my Touch) flashed a different rom that used CVM 5.something.. and original was a newer version. Caused me some issues. As for the folder being write protected. Try using root explorer, mount as R/W and then try to delete from there. Just ensure you have everything out of it you want tho.
Click to expand...
Click to collapse
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
solidhound said:
hey milky1112.
Thanks for reading and providing your input!
I actually used the sames recovery when creating and trying to restore. That's the odd part. I did recently flash the newer version within the old recovery. Do you think that may have been it? Although the new one was used to create a nandroid and restore it.
I just tried deleting using Root Explorer and the same result. It's not a big deal since its only 69mb but it's quite annoying knowing I can't.
thanks again!
Click to expand...
Click to collapse
That is very possible, still odd that it will not let you delete even with R/W permissions set. But as long as everything is working.. Then i wouldn't fuss too much
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thanks for clarification Ed. I've been on TPR for a while so haven't flashed any 4.2 roms.
edfunkycold said:
The new rom you installed is on 4.2 not 4.1 which is probably what you had originally. The new 4.2 releases by Google move everything into the O folder its part of the new Android set up to dual boot devices. If the recovery is not set up to correct for this your phone will not recognize where the files have been moved to. In my understanding only TWRP is corrected to do this, we'll at least in the Gnex it is. Anyone on Cwm has had issues with this. The fix is to copy and paste your files back into its original location. You can not delete O folder it is an essential part now of your system and it's where it will reference everything from and originals must remain.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
hey edfunkycold,
thanks a ton for the response and clarification! i was thinking about swapping recoveries but i already reverted back to the original nandroid image i had at that point.
and you are correct. i was on 4.1 and not 4.2. i didn't know such changes were made but its great to see dual boot is coming up.
i will make sure to THANK both responses once i reach 10 posts. i'm trying hard to participate in these forums but haven't had time until recently.
hi, need a bit of help. i am running arconium 8.2 gingerbread on doomkernel 22.
i found a launcher that came from here
Code:
http://forum.xda-developers.com/showthread.php?t=978806
and mistakenly installed it by overwrite Home.apk in /system/app, set its permission as 644 (i did a backup of the previous one in there as Home.bak), then rebooted.
now the phone won't boot, stuck on the doomkernel logo.
so i tried restoring the old launcher, opened the arconium rom zip file, extracted out the META-INF folder and system\app\Home.apk ... created a new home.zip and installed it via CWM.
it installed but result is the same. i did a cache and dalvik wipe, reboot, same results, stuck on the doomkernel logo.
any quick solution for this, as i don't want to start flash fresh from scratch again.
i was thinking along the lines of mounting the /system while only on CWM and use adb to check it there, perhaps the Home.apk don't have the correct permission, or just rename back the old Home.bak to Home.apk. but of course adb won't work as phone won't boot.
any step by step to restore this i would be very grateful... its just a launcher restore i dunno why this happened...
thanks!
Try out the Aroma file manager by amarullz and try putting back the launcher that was previously there. If that doesn't work, you can go in CWM, make a backup of data and try reflashing the ROM.
If anything, you should try flashing official firmware with Flashtool and then flash the ROM and restore data. (unless you did make some changes to the /system partition, those changes will be lost, obviously)
I realized, my noob thinking of creating of my own flashable zip file to restore the original Home.apk was wrong. Within Aroma File Manager, I saw the entire /system/app is wiped out, save for 2 files superuser.apk and the restored Home.apk. Of course the phone will not boot. If I had known and tried that aroma file manager as the first solution, I may just have corrected the launcher and issue fixed quickly.
Anyways, I ended up restoring from that outdated (month old) nandroid. To get the recent data, I selected the recently updated data/apps using titanium backup, restored the data (only, not app) coming from the hanged (but recent) nandroid. Its the 1st time I used that feature and was really handy.
I learned my lesson now not to tinker with the launcher absent mindedly. That launcher that broke the phone in the 1st place is a really old launcher judging from the thread date. Too late, but lesson learned.
This solution maybe applicable in other similar unbootable scenarios.
Thanks xan1242 for the ideas!
Hello,
I'm a new user to xda-developers and I realize this is not the best place to post this, but it's all I can do for now, so hopefully I won't get flamed too bad. Another user reported this problem but did not know what to do so I thought I would post this in hopes he and the developer see this.
For some reason, nandroid does not backup /data/system, even when backing up "all", or just "data". I started using it and was playing with different releases and so forth, and every time I restored from nandroid I would have to extract data.tar manually, fix the permissions one by one, and copy the data back over after the restore, which took forever. This time I finally decided to look into the problem in more depth and realized the data.tar does not contain the system directory, which of course has all the UIDs and so forth for all the apps stored in the XML files.
With that said, Open Recovery is awesome! I love being able to have a full console and everything right there!! I'm using 2.09 and this has happened on multiple Photon Qs.
I'm trying to figure out why my new backed up in TWRP backups are no longer working. My SystemUI.apk is malfunctioning after a 2nd boot it will say that the SystemUI has crashed and you can report it or click ok. The first boot seems fine but the taskbar and software buttons are missing. I don't know what it is. I've looked through logcat and couldn't figure it. Can anyone help? I don't know where to begin to troubleshoot.
https://pastebin.com/raw/Q5sPQdda
XML: https://pastebin.com/WG5Ccucx
I will pay someone to fix this for me: https://drive.google.com/file/d/1mQ8x3B2WBqvayFbuYXpD3_JWAjlviEJF/view?usp=sharing
TWRP restore of a standard MOB30X backup ends with "extractTarFork() process ended with ERROR: 255". The backup is larger than the original size because symlinked files are copied multiple times, taking up extra space on an already tightly filled system partition. System is 100% used when the error happens...
Click to expand...
Click to collapse
Nexus 7'13 Stock ROM factory image MOB30X issues and solutions
SUMMARY TWRP restore fails with MOB30X backup. You need either repartitioning or the following storage space script. I use LineageOS but recently had to install the latest stock ROM due to the development of Restock app. I noticed two...
forum.xda-developers.com
If you have found no solution and have nothing to lose, try sysrepart and then hopefully you may be able to restore your backup.