Database Users

[solved] Bootanimations- Change impossible in ۵.ReflexTSenseHD v1.7 DHD

Hello:
i tried to change my Bootanimation but with no Luck.
1. i tried to make a "theme" via Online Kitchen; got a file (about 6mb) flashed it via Recovery but Botscreen stayed at white "HTC-Briliant"
2. i tried to manualy delete the bootaniamtion.zip at /data/app/local with androidmate (free)--> http://forum.xda-developers.com/showthread.php?p=10041079&highlight=bootanimation#post10041079
3. i tried to make my own update.zip ( http://www.londatiga.net/it/how-to-create-android-update-zip-package/)
script:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data\app\local data\app\local:
show_progress 0.1 10
4. tried to change the bootimage.zip in NEO's Reflext.Rom by deleting all unneccesary stuf and changing the bootanimation-zip
--> got stuck after Recovery so i had to reflash the whole ROM..
--------------------------------------------
why i'm not able to change this bootanimation ?
can someone provide me a funktional Update-zip for this ROM
(or a HowTo for doing it myself?)
i would like to test these Bootimages:
http://forum.xda-developers.com/showthread.php?t=648555
http://forum.xda-developers.com/showthread.php?t=905538 (android particle2)
PLEASE Help
EDIT: i also tried via
Terminal Emulator
- Connect your phone to your computer via USB
- Copy the downloaded file to your sdcard
- Disconnect phone from computer
- Open Terminal Emulator on your phone and enter the code below (press enter after every line)
su
cp /sdcard/480x800_AndroidGlow1.zip /data/local/bootanimation.zip
reboot
Click to expand...
Click to collapse
EDIT:

Try putting it into /system/customize/resource
thats where the bootanimation (and the boot sound..) was located on my desire rom.

tried this but:
1: i found no "resource" folder under /system/customize..
2. after creating this folder and copying bootanimation.zip nothing happens
it seems like NEO put it on a special place in his ROM so i cant't figure out..

Test this route: /system/etc/customer/bootanimation.zip ;-)

System/sd/app/local remplace the bootanimation.zip and reboot.

It worked !!
Thanks ASIER
the System/sd/app/local .. did the trick
why does neo uses this folder-structure.. weird ..
(and also thx to raa_ for his help)

does it make sense if i say, i don't have a /system/sd/app/local folder??? the sd part is nowhere to be found
any idea?
edit. found it on my Desire it was under /system/customize/resource/bootanimation.zip
cheers

i think it depends on the ROM you are using!
i use the ReflextSense 1.7 from NEophyte.360
that uses the "unusual" path as postet before.
"normal" Sense ore SenseHD Roms are using different locations as you found out..
it is sad that there's not a standard-path for all roms !

Asier said:
System/sd/app/local remplace the bootanimation.zip and reboot.
Click to expand...
Click to collapse
I have the reflext 1.7 rom on my desire and i have no folder named app in system/sd

neo2006pf said:
I have the reflext 1.7 rom on my desire and i have no folder named app in system/sd
Click to expand...
Click to collapse
are you sure youre on the system-"partition" ?
i first set the System to Read/Write in SPareparts and afterwards used ESData explorer (in the program you have to enable ROOT funktions..)
--> menu/settingsroot options --> mount filesystem
------
click on the button on the very left (sd-icon) and it should change into a "house"
the path should be a "/"
afterwards choose SYSTEM/SD/APP/Local
in this folder there should be bootanimation.zip, downanimation.zip, shutdown.zip and "placeholder"
hope it helps

I cant find my bootanimation.zip anywhere,Im using insertcoin 1.8f(trying to update to 1.8h with no luck )

this Thread describes Changing BOOTANIMATION in ReflextSense (1.7)
i think insertCoin uses an different Folder for Bootanimation.zip than this rom.
you could try one of these options:
get shure you hav read/write acces to your Root.. (as i described in de Posting before..)
search the "insert coin" thread for Bootanimation.zip
ask in the Thread about the neccesary "Path"
try to download a "change bootanimation" zip from online kitchen or from the forum..
apply the zip via Recovery and if it works !! ... open the zip and analyse the script file (which Path it uses..)
i hope it helps..

klefreak said:
are you sure youre on the system-"partition" ?
i first set the System to Read/Write in SPareparts and afterwards used ESData explorer (in the program you have to enable ROOT funktions..)
--> menu/settingsroot options --> mount filesystem
------
click on the button on the very left (sd-icon) and it should change into a "house"
the path should be a "/"
afterwards choose SYSTEM/SD/APP/Local
in this folder there should be bootanimation.zip, downanimation.zip, shutdown.zip and "placeholder"
hope it helps
Click to expand...
Click to collapse
I had the right path but was using a software that can't see the folder system/sd/app. I managed to replace the bootanimation.zip with SUFBS. Thank you for your help though.

[Q] how to install JELLYBLAST V3 on Galaxy Y Pro GT-B5510

Hi.
I need help i want to know how to install JELLYBLAST V3.0.3 on my galaxy y pro GT-B5510
i read on this post JELLYBLAST V3 that with some modification it can be installed on Galaxy Y Pro
THANKS

nedo113 said:
Hi.
I need help i want to know how to install JELLYBLAST V3.0.3 on my galaxy y pro GT-B5510
i read on this post JELLYBLAST V3 that with some modification it can be installed on Galaxy Y Pro
THANKS
Click to expand...
Click to collapse
1) download jellyblast + 4 OTA + CWM
2) open jellyblast zip ed delete "boot.img"
3) copy rom + 4 ota + CWM inside SD
4) reboot in recovery mode (vol up + home + power) and select CWM.zip
5) Backup your rom via CWM (backup and restore) [REQUIRED STEP! This take some time but you can restore previous rom and all you had before (apps, calls... everithing) in case of problems!]
6) Run " wipe data/factory reset" and " wipe cache partition" ("wipe data/factory reset" delete everithing from your device!)
7) Run "install zip from sdcard" > "choose zip"
8) Select jellyblast rom > "yes"
9) Than "reboot system now"
For ota:
1) Reboot in recovery mode (no need flash CWM again...)
2)Select "apply update"
4) choose first OTA
5) reboot
6) same for other ota (pass 1 to 5)
Install OTA update in number order (OTA 1, OTA 2...)
(Thanks to Roby293)
I tried this steps yesterday.
Full working for me, the rom is very smooth & fast.
Just some force stop to Phone process and PIN Dial pad not working.
Some people say fix this flashing "modem" & "csc" via ODIN.
But i'm not really sure.
Sorry for delay. Hope this help someone else.

Thanks
ciccione said:
1) download jellyblast + 4 OTA + CWM
2) open jellyblast zip ed delete "boot.img"
3) copy rom + 4 ota + CWM inside SD
4) reboot in recovery mode (vol up + home + power) and select CWM.zip
5) Backup your rom via CWM (backup and restore) [REQUIRED STEP! This take some time but you can restore previous rom and all you had before (apps, calls... everithing) in case of problems!]
6) Run " wipe data/factory reset" and " wipe cache partition" ("wipe data/factory reset" delete everithing from your device!)
7) Run "install zip from sdcard" > "choose zip"
8) Select jellyblast rom > "yes"
9) Than "reboot system now"
For ota:
1) Reboot in recovery mode (no need flash CWM again...)
2)Select "apply update"
4) choose first OTA
5) reboot
6) same for other ota (pass 1 to 5)
Install OTA update in number order (OTA 1, OTA 2...)
(Thanks to Roby293)
I tried this steps yesterday.
Full working for me, the rom is very smooth & fast.
Just some force stop to Phone process and PIN Dial pad not working.
Some people say fix this flashing "modem" & "csc" via ODIN.
But i'm not really sure.
Sorry for delay. Hope this help someone else.
Click to expand...
Click to collapse
Thanks my friend full working for me too

danhtien088 said:
helllo
Click to expand...
Click to collapse
this is not chatting site pal to say hello....ask q if u have any....

Hi! This rom works in GT-B5510 with all OTA Updates installed? Another question; I have a GT-B5510L You guys think the rom will work?

Suuichi said:
Hi! This rom works in GT-B5510 with all OTA Updates installed? Another question; I have a GT-B5510L You guys think the rom will work?
Click to expand...
Click to collapse
Yup it works with that device
Please press thanx if I am useful to you

ciccione said:
1) download jellyblast + 4 OTA + CWM
2) open jellyblast zip ed delete "boot.img"
3) copy rom + 4 ota + CWM inside SD
4) reboot in recovery mode (vol up + home + power) and select CWM.zip
5) Backup your rom via CWM (backup and restore) [REQUIRED STEP! This take some time but you can restore previous rom and all you had before (apps, calls... everithing) in case of problems!]
6) Run " wipe data/factory reset" and " wipe cache partition" ("wipe data/factory reset" delete everithing from your device!)
7) Run "install zip from sdcard" > "choose zip"
8) Select jellyblast rom > "yes"
9) Than "reboot system now"
For ota:
1) Reboot in recovery mode (no need flash CWM again...)
2)Select "apply update"
4) choose first OTA
5) reboot
6) same for other ota (pass 1 to 5)
Install OTA update in number order (OTA 1, OTA 2...)
(Thanks to Roby293)
I tried this steps yesterday.
Full working for me, the rom is very smooth & fast.
Just some force stop to Phone process and PIN Dial pad not working.
Some people say fix this flashing "modem" & "csc" via ODIN.
But i'm not really sure.
Sorry for delay. Hope this help someone else.
Click to expand...
Click to collapse
Hi friend
thanks for your help but i need it one more time
I do not get to use symbols, numbers on the keyboard only letters
to put numbers I have to use the onscreen keyboard but the screen is too small for typing with it so i would like fix it
do you have any idea??
i use it in spanish language

nedo113 said:
Hi friend
thanks for your help but i need it one more time
I do not get to use symbols, numbers on the keyboard only letters
to put numbers I have to use the onscreen keyboard but the screen is too small for typing with it so i would like fix it
do you have any idea??
i use it in spanish language
Click to expand...
Click to collapse
I'm having the same problem, and another ones... the customized keys (1 and 2), Backspace and Enter keys doesn't work, the camera can't be used in 3.15MP and most of apps doesn't install, just keep saying "downloading"

for problem with device/hardware keyboard, please copy keylayout and keychars from your stock rom into jellyblast (System/Usr)
dont delete the existing folder in jellyblast, just replace the existing files. the flash the modded jellybean rom again.
your keyboard will be working, overall keyboard function is ok, but i cant get symbol button working yet..
im using this, almost perfect but phone application looks bad because of the landscape view of our phone.
for camera, you can replace it with camera.apk from your stock rom. (system/app folder)
update: just wanna share, cant copy camera from stock rom, becuase stock is odexed. so, to get 3.2mp camera working, i downloaded ported jellyblast rom for galaxy mini pop plus, extracted it,copy camera.apk from system/apps and install on your phone.
suuchi, for 'apps doesnt install' problem, u need to remove a2sd or disable it before flashing the rom.

found today out position sensor not working properly..horizontal calibration wont help
update: got it working already, need to copy sensor file system/bin and system/lib folder from stock rom.

xshiro said:
for problem with device/hardware keyboard, please copy keylayout and keychars from your stock rom into jellyblast (System/Usr)
dont delete the existing folder in jellyblast, just replace the existing files. the flash the modded jellybean rom again.
your keyboard will be working, overall keyboard function is ok, but i cant get symbol button working yet..
im using this, almost perfect but phone application looks bad because of the landscape view of our phone.
for camera, you can replace it with camera.apk from your stock rom. (system/app folder)
update: just wanna share, cant copy camera from stock rom, becuase stock is odexed. so, to get 3.2mp camera working, i downloaded ported jellyblast rom for galaxy mini pop plus, extracted it,copy camera.apk from system/apps and install on your phone.
suuchi, for 'apps doesnt install' problem, u need to remove a2sd or disable it before flashing the rom.
Click to expand...
Click to collapse
I solved the symbol's problem using an app called 'Game Keyboard'. With the compatibility options the buttons will work properly. Can you upload the camera.apk? Thanks a lot!

Suuichi said:
I solved the symbol's problem using an app called 'Game Keyboard'. With the compatibility options the buttons will work properly. Can you upload the camera.apk? Thanks a lot!
Click to expand...
Click to collapse
ooh..thanks bro
i have attached camera apk here

xshiro said:
found today out position sensor not working properly..horizontal calibration wont help
update: got it working already, need to copy sensor file system/bin and system/lib folder from stock rom.
Click to expand...
Click to collapse
Hi! I've been using this rom for 3 days, it works really fast and smooth. I just need to fix the sensor's problem. Can you tell me which files I need to copy? Thanks!

Suuichi said:
Hi! I've been using this rom for 3 days, it works really fast and smooth. I just need to fix the sensor's problem. Can you tell me which files I need to copy? Thanks!
Click to expand...
Click to collapse
im not sure which sensor file that responsible for screen position, so i just copied all sensor related file ..hehe...
the files are
system/bin
- atx
-memsicd
system/lib
-libacc.so
-libsensorservice.so
-libaccsensorcal.so
-libaccelcal.so
-libaccsensorcaltest.so
what i did was, using the root explorer (setting - mount / and /system as writable is checked) delete all the existing sensor file, then copy paste, because the explorer cannot replace the existing files.
then i set the permission back..to enable 'read write exec' for all user group...
then restart the phone..
you will notice horizontal calibration app wont show the correct position (maybe you need to replace horizontal calibration app also), but your sensor is working by using sensor diagnostic (dial *#0*#)
bro do have any solution for dialer/phone app not displayed correctly?

xshiro said:
im not sure which sensor file that responsible for screen position, so i just copied all sensor related file ..hehe...
the files are
system/bin
- atx
-memsicd
system/lib
-libacc.so
-libsensorservice.so
-libaccsensorcal.so
-libaccelcal.so
-libaccsensorcaltest.so
what i did was, using the root explorer (setting - mount / and /system as writable is checked) delete all the existing sensor file, then copy paste, because the explorer cannot replace the existing files.
then i set the permission back..to enable 'read write exec' for all user group...
then restart the phone..
you will notice horizontal calibration app wont show the correct position (maybe you need to replace horizontal calibration app also), but your sensor is working by using sensor diagnostic (dial *#0*#)
bro do have any solution for dialer/phone app not displayed correctly?
Click to expand...
Click to collapse
Thanks! You are awesome! I tried to modify or replace the phone.apk, but didn't work... If I find a solution, I will post it here!

Suuichi said:
Thanks! You are awesome! I tried to modify or replace the phone.apk, but didn't work... If I find a solution, I will post it here!
Click to expand...
Click to collapse
ok,..currently using exdialer
now occasionally will have problem with flickering screen with some apps...suspect power management issue...

HELP PLZ
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
---------- Post added at 03:25 AM ---------- Previous post was at 02:47 AM ----------
xshiro said:
ok,..currently using exdialer
now occasionally will have problem with flickering screen with some apps...suspect power management issue...
Click to expand...
Click to collapse
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
Wondering if a clockwork back up could get me back the kernel?

zip not opening
brothers whenever i try to install zip fro cwm , it gives error like zip opening failed.
i hv installed the zip package of jelly blast without deleting boot.img nd it didnt give any error while opening zip but after installation i was facing half screen error.
so i m assuming that when i delete boot.img nd re zip the file at that point i m doing some mistake.
is thr some specific zip format or compression ratio which i should have to consider while zipping it?

far4z said:
brothers whenever i try to install zip fro cwm , it gives error like zip opening failed.
i hv installed the zip package of jelly blast without deleting boot.img nd it didnt give any error while opening zip but after installation i was facing half screen error.
so i m assuming that when i delete boot.img nd re zip the file at that point i m doing some mistake.
is thr some specific zip format or compression ratio which i should have to consider while zipping it?
Click to expand...
Click to collapse
When you download the Rom zip do not unzip it... Open the rom zip in winrar or 7zip and then delete the boot.img file from the compressed zp

Mariofrith said:
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
---------- Post added at 03:25 AM ---------- Previous post was at 02:47 AM ----------
I was trying to flash the Jelly Blast Rom to my B5510L... but I think I forgot to delete the boot.img file
Now my phone is not loading and only half the screen shows. Help plz.
Wondering if a clockwork back up could get me back the kernel?
Click to expand...
Click to collapse
yes you can. if you have backup your stock rom using cmw, you know the combination key to recovery? press vol up + home + power on
then select update zip from sdcard, select cmw.zip -> restore
or you can take out your sdcard copy the correct jellyblast zip, with deleted boot.img. reflash again, bro make sure you have disable/removed a2sd for smooth installation

[Q] how to recover data from a phone that will not boot

I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.

toggly said:
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
Click to expand...
Click to collapse
I would make a backup in your recovery and then flash the rom you had installed. See if that helps.
Edit: You didn't try to update. I changed my comment saying you had tried.

1. Download Aroma File Manager
2. Put a external sd into your phone.
3. Boot into the custom recovery and flash the Aroma file.
4. It will boot into a file browser and you can copy all the files from internal to your external.
ps it's possible that your custom recovery already has a filemanager build in. Then all these steps are obsolete.

I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?

toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.

toggly said:
Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Lennyz1988 said:
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
Click to expand...
Click to collapse
I don't know, that's why I am asking what that icon means?

You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?

toggly said:
I don't know, that's why I am asking what that icon means?
Click to expand...
Click to collapse
The icons means that it's symlinked. If it's not encrypted then you should find the data. It can be in an other place then where you are looking. Try looking in /data/media or some other maps in /data
Or just flash the rom you are currently on without wiping.
soldier9599 said:
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
Click to expand...
Click to collapse
Adb won't work unless he already has authorized adb when his device was booted.

toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager

Lennyz1988 said:
Adb won't work unless he already has authorized adb when his device was booted.
Click to expand...
Click to collapse
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.

peppe130 said:
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Click to expand...
Click to collapse
That did the trick, thanks!!

Nothing

soldier9599 said:
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
Click to expand...
Click to collapse
Yes and I believe that. But from version 4.2.2 android forces rsa encryption. So you need to boot into your rom and enable it. Unless the custom rom/kernel has disabled it, but I haven't seen any that have.

Soft-Bricked phone (SM-9005, OS: 4.4.2), problem with /system

So Hello everyone, i got interesting problem...
I bricked my phone
Phone: SM-9005
OS: Android 4.4.2
Firmware: N9005XXUGNG1
Recovery: TWRP 3.0 installed.
Root software installed which may be interesting "Xposed Additions, Lucky Patcher, SuperSu, Greenify"
Step by step.
// maybe helpful - cache / dalvik cache wiped and after reboot i started playing stuff
I used Root Browser (com.jrummy.root.browserfree) to copy 2 directories from my /downloads to /system.
There were /lib & /bin which contained unique libs and one executable so this would not affect system if everything went ok, but i didn't
After i started coping, root explorer asked me that "File already exist, overwrite or make a copy"? i pressed overwrite, in same second all apps in android started to generate "unexpected error", i tried to reboot and got boot into recovery
after i watched /system i found that what i tried to copy actually copied not to /system/lib & /system/app but to /system/system/lib & /system/system/app.
So i think there was some folder or file called system in /system directory which was overwritten. Or any kind of problem with dir / file permissions.
Any ideas of how to fix this / what was in /system/system / where to get bootlog to find after what "kernel panic" takes place or any other help?
Thanks.
// maybe somebody with same model version, same os version can upload zip file of own /system folder without /apps, /priv-apps and build.prop so i can compare whats lost compared to my data?

Fixed myself, root browser set wrong permissions to /system while was coping files... set back to 755 and it works

Nexus 6p stuck on Google screen during boot due to replacing build.prop

I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.

Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.

dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?

If you can boot to bootloader you should be able to replace the file with a standard one.

Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out

1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.

Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?

Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/

RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.

istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!

Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0

same thing happened to me.... stuck on google even after flashing stock....

dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app

Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.

RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too