Hi,
I edited my build.prop and it's causing my phone to boot loop. I know I can odin back the factory image to fix the issue but I have important data on it that I can't loose. Is there a way to only odin the correct build.prop?
Thanks
hnamanh said:
Hi,
I edited my build.prop and it's causing my phone to boot loop. I know I can odin back the factory image to fix the issue but I have important data on it that I can't loose. Is there a way to only odin the correct build.prop?
Thanks
Click to expand...
Click to collapse
Not to my knowledge. Always make a backup before modding your phone.
Yeah, I should have. Thanks
Update: I got really lucky and used "elliwigy's" G925VVRU1AOE2_G925VVZW1AOE2_VZW.ZIP and odin the phone. What did you know my I didn't loose anything from it.
I'm about to experiment with my build.prop regarding memory management. One thing I'm not sure I understand with Flashfire backups is restoring after a boot loop. I assume i need to odin back to stock, then ping-pong root again, then load Flashfire and restore my backup? I hope I'm missing something and there is an easier way. Sure miss having TWRP!
rkirmeier said:
I'm about to experiment with my build.prop regarding memory management. One thing I'm not sure I understand with Flashfire backups is restoring after a boot loop. I assume i need to odin back to stock, then ping-pong root again, then load Flashfire and restore my backup? I hope I'm missing something and there is an easier way. Sure miss having TWRP!
Click to expand...
Click to collapse
That sounds right. When restoring with flashfire you obviously have to have root but also you need to be on the same build that you were on when you did your backup in the first place. I don't believe you can be on OC3 and restore a OE2 backup.
---------- Post added at 03:14 PM ---------- Previous post was at 03:03 PM ----------
hnamanh said:
Yeah, I should have. Thanks
Update: I got really lucky and used "elliwigy's" G925VVRU1AOE2_G925VVZW1AOE2_VZW.ZIP and odin the phone. What did you know my I didn't loose anything from it.
Click to expand...
Click to collapse
The ones named "low_ship_MULTI_CERT.tar" are full wipe. Ones ending in "Home" are not. Couldn't tell with elliwigy's but that is good to know.
test post
Tulsadiver said:
That sounds right. When restoring with flashfire you obviously have to have root but also you need to be on the same build that you were on when you did your backup in the first place. I don't believe you can be on OC3 and restore a OE2 backup.
---------- Post added at 03:14 PM ---------- Previous post was at 03:03 PM ----------
The ones named "low_ship_MULTI_CERT.tar" are full wipe. Ones ending in "Home" are not. Couldn't tell with elliwigy's but that is good to know.
Click to expand...
Click to collapse
test post
Related
Hi,
I want to root my device, which i have upgraded recently to 4.1.2
the thing is, I found some information in root threads regarding build no. like XXAMA1, XXAMA2, XXAMA4 ...etc
what are the differences between them? if all of them are 4.1.2 JB?! will anyone work?
to make it easier, which thread can work to root my SG3mini device:
Android version: 4.1.2
Baseband version: I8190XXAMA3
Kernel version: 3.0.31-860525
Build number: JZ054K.I8190XXAMA3
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
tys0n said:
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
Click to expand...
Click to collapse
can you root with a 4.1.1 custom version on a 4.1.2?
TerenceTP7 said:
can you root with a 4.1.1 custom version on a 4.1.2?
Click to expand...
Click to collapse
Yes you can, but only if you make a factory reset first. Otherwise you'll have bootloops or force closed apps.
tys0n said:
Yes you can, but only if you make a factory reset first. Otherwise you'll have bootloops or force closed apps.
Click to expand...
Click to collapse
now i have a official firmware 4.1.2 ,baseband I8190XXAMA2.before this i had a rooted 4.1.1 by avicoh.but my phone didnt boot anymore,so i flashed with the official 4.1.2 and after that with PARAM.
so now i need to factory reset,but the one that i now have isnt the one that came with my phone from the store.doesnt it give any problems when i factory reset?
original from the store was 4.1.1 JB
TerenceTP7 said:
now i have a official firmware 4.1.2 ,baseband I8190XXAMA2.before this i had a rooted 4.1.1 by avicoh.but my phone didnt boot anymore,so i flashed with the official 4.1.2 and after that with PARAM.
so now i need to factory reset,but the one that i now have isnt the one that came with my phone from the store.doesnt it give any problems when i factory reset?
original from the store was 4.1.1 JB
Click to expand...
Click to collapse
No it shouldn't be any problem. Factory reset makes sure there is no leftovers from previous install. Clears cache, settings, user data.
tys0n said:
No it shouldn't be any problem. Factory reset makes sure there is no leftovers from previous install. Clears cache, settings, user data.
Click to expand...
Click to collapse
alright,i trust you on this.i did the reset my phone rebooted and now its stuck on the bootlogo(galaxys3mini gt-i8190).do i need to wait?or?
..
..
still stuck on bootlogo after 10minutes.doesnt look good.use param again?
---------- Post added at 06:04 PM ---------- Previous post was at 05:40 PM ----------
ok,that didnt work..man im getting headache of this..
i booted my phone again using PARAM.
do you know a root version for my phone?maybe a version that clear all my data too?
---------- Post added at 06:28 PM ---------- Previous post was at 06:04 PM ----------
TerenceTP7 said:
alright,i trust you on this.i did the reset my phone rebooted and now its stuck on the bootlogo(galaxys3mini gt-i8190).do i need to wait?or?
..
..
still stuck on bootlogo after 10minutes.doesnt look good.use param again?
---------- Post added at 06:04 PM ---------- Previous post was at 05:40 PM ----------
ok,that didnt work..man im getting headache of this..
i booted my phone again using PARAM.
do you know a root version for my phone?maybe a version that clear all my data too?
Click to expand...
Click to collapse
the one that you have http://forum.xda-developers.com/showthread.php?t=2178346 is this a root version?for the netherlands?can i use it on my phone?
Just flash a wipe.tar and then your firmware.
I never had to flash param.lfs to get it boot.
Once I had to pull the battery and power on again when it got stuck on boot after flash.
tys0n said:
Just flash a wipe.tar and then your firmware.
I never had to flash param.lfs to get it boot.
Once I had to pull the battery and power on again when it got stuck on boot after flash.
Click to expand...
Click to collapse
i did used it once that wipe.tar but get stuck on bootscreen.
do you need to wait long on bootscreen while flashing with wipe.tar?
and how does it work?just odin>pda,select wipe.tar>start?
TerenceTP7 said:
i did used it once that wipe.tar but get stuck on bootscreen.
do you need to wait long on bootscreen while flashing with wipe.tar?
and how does it work?just odin>pda,select wipe.tar>start?
Click to expand...
Click to collapse
Yes flash as pda. It's basicly the same as a factory reset.
If your phone reboots after, just put it in download again and flash firmware.
tys0n said:
Yes flash as pda. It's basicly the same as a factory reset.
If your phone reboots after, just put it in download again and flash firmware.
Click to expand...
Click to collapse
and what if its get stuck on bootscreen again.use PARAM?
TerenceTP7 said:
and what if its get stuck on bootscreen again.use PARAM?
Click to expand...
Click to collapse
Afaik the param.lfs is mostly just a bunch of pictures. Don't know what it does, except loads the phone with startup/downloadmode pictures.
http://forum.xda-developers.com/showthread.php?t=1750645
http://z4ziggy.wordpress.com/2010/09/18/looking-into-param-lfs-file/
tys0n said:
Afaik the param.lfs is mostly just a bunch of pictures. Don't know what it does, except loads the phone with startup/downloadmode pictures.
http://forum.xda-developers.com/showthread.php?t=1750645
http://z4ziggy.wordpress.com/2010/09/18/looking-into-param-lfs-file/
Click to expand...
Click to collapse
i dont get it.i have my 4.1.2 rooted now,but after flashing ,my phone doesnt boot.it only boots when i flash the PARAM file.i restarded my phone to check if that works and that works fine.i dont think this is a big problem,is it?
at first sight everything works fine.
WIPE doesnt work,and factory reset doesnt work either.is there a option to do this manually.i have clear master,is that the same?
tys0n said:
You can just root the one you got. No need to re-flash the whole rom.
---------- Post added at 10:54 PM ---------- Previous post was at 10:39 PM ----------
Here is also a very good explanation on these PDA/PHONE/CSC codes.
Click to expand...
Click to collapse
thank you tys0n for your replies! i kept my CSC, didn't change it.. since i'm already having 4.1.2 (last firmware for s3 mini till now)
and followed this way to root my device:
http://forum.xda-developers.com/showthread.php?t=2150979
and it worked
the only thing is, this way increased the flash counter! i dont know how is this bad, but i guess just if i want to give it to someone to check it, they will know, right?!
BUT I found other rooted ROM that they will reset binary count after flash to "none"! and will show firmware as "official" instead of "custom"..
anyway, good to learn and i'm saying all that just in case any noob like me saw this thread in the future maybe they can find one useful info or two
sorry TerenceTP7 that i can't help you.. still new to those things..
and thank you again tys0n
Sv: [Q] for 4.1.2 root, what is the difference between build no.?
Search triangle away here on xda. It's an app that will reset your binary count to zero
Sent through time and space from my s3mini.
I have the MJ5 build and I want to do a clean install. Is there an Odin ready build out there for me to do this task. I have found threads about this, but they are to confusing and I don't want to flash the wrong one. Any help would be very much appreciated. Thanks
BR7fan said:
I have the MJ5 build and I want to do a clean install. Is there an Odin ready build out there for me to do this task. I have found threads about this, but they are to confusing and I don't want to flash the wrong one. Any help would be very much appreciated. Thanks
Click to expand...
Click to collapse
Clean install of what? Of mj5?
posersk8r said:
Clean install of what? Of mj5?
Click to expand...
Click to collapse
YES sir
BR7fan said:
YES sir
Click to expand...
Click to collapse
You can use this to restore back to stock mj5. Complete steps to have root, stop at step 9 if you dont want to.
---------- Post added at 10:41 PM ---------- Previous post was at 10:33 PM ----------
posersk8r said:
You can use this to restore back to stock mj5. Complete steps to have root, stop at step 9 if you dont want to.
Click to expand...
Click to collapse
Im dumb somehow i cant post a link, just look at general section for restore mj5.
posersk8r said:
You can use this to restore back to stock mj5. Complete steps to have root, stop at step 9 if you dont want to.
---------- Post added at 10:41 PM ---------- Previous post was at 10:33 PM ----------
Im dumb somehow i cant post a link, just look at general section for restore mj5.
Click to expand...
Click to collapse
Thanks. That's what I was confused about. I wasn't sure if I could use that one to restore MJ5 to MJ5. The reason I needed to is because when I unrooted kingo with kingo, I couldn't reroot and the custom lock won't go away.
BR7fan said:
Thanks. That's what I was confused about. I wasn't sure if I could use that one to restore MJ5 to MJ5. The reason I needed to is because when I unrooted kingo with kingo, I couldn't reroot and the custom lock won't go away.
Click to expand...
Click to collapse
Yeah the restore would remove the custom padlock if you decide not to root. Would wipe everything though so be sure to back up important stuff.
hi, im using 4.4.4, my device is unlocked and rooted.
i was trying to enable the advanced options in Camera+ as mentioned here in the forum, changed the line on build.prop, rebooted the device, and it got stuck at the "bootloader unlocked" screen, not passing that anymore.
so, i got in to recovery > and wiped data and cache. the device rebooted itself and now is stuck again in "bootloader unlocked" screen.
now if i press power button to turn off it gives "2 vibrations", like its doing something (but is in this screen for past 5 minutes)
any help apreciated.
You need to reflash a firmware.. I would flash back to stock firmware and then go from there.
---------- Post added at 04:54 PM ---------- Previous post was at 04:53 PM ----------
Plug into computer and use adb and/fastboot to flash the firmware. There might be a toolkit in the original moto x forum to help do this.
---------- Post added at 05:02 PM ---------- Previous post was at 04:54 PM ----------
Do you have a twrp backup you can restore ? What firmware are you on?
dobbs3x said:
You need to reflash a firmware.. I would flash back to stock firmware and then go from there.
Click to expand...
Click to collapse
im downloading the firmware (Firmware Retail Brasil XT1097 4.4.4 KXE 21.187-30.3)
its the same as was in the phone i believe (KXE21.187-30.3)
dobbs3x said:
[/COLOR]Plug into computer and use adb and/fastboot to flash the firmware. There might be a toolkit in the original moto x forum to help do this.
Click to expand...
Click to collapse
thanks. i found a forum with explanations on how to use adb/fastboot to reflash. i hope it works
dobbs3x said:
Do you have a twrp backup you can restore ? What firmware are you on?
Click to expand...
Click to collapse
noopz. i just got the phone a few days ago, didn't even finish to install my apps
thanks for your help, appreciated
You could always mount the system partition with twrp and edit the build.prop to put it back to its original state. It is also possible you need to fix the permissions on the build.prop file.
Steve-x said:
You could always mount the system partition with twrp and edit the build.prop to put it back to its original state. It is also possible you need to fix the permissions on the build.prop file.
Click to expand...
Click to collapse
i will look into twrp as i'm not familiar with it. i also thought about the file permissions may be the problem cause i did not edit the file, i modified on the PC and replaced the file on phone. maybe this was the cause? cause i installed a lot of apps and Xposed stuff before that reset, so im not sure if exactly that was the problem. but as i didn't know how to edit the permissions on the file with the phone in that situation, i didn't even consider possible to fix it.
but i flashed with the same ROM and the phone is now fully working (at least this i could do miself )
thanks dobbs3x and Steve-x for the help! :good::good:
As it says in the title. How to i get it to install. My Tablet is rooted.
Updating this tab to lollipop isn't a good idea (lots of bugs) but have a look here: http://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965
Saarge said:
Updating this tab to lollipop isn't a good idea (lots of bugs) but have a look here: http://forum.xda-developers.com/memo-pad-7/general/me176c-x-collection-roms-updates-t3012965
Click to expand...
Click to collapse
I had seen that but it didnt work at all.
Dublin2275 said:
I had seen that but it didnt work at all.
Click to expand...
Click to collapse
If you have a ww sku try to put this file (http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip) on the root of you microSD card and reboot the tab, it should try to flash it (well not on first reboot, you'll have a notification asking you if you want to do the update); if this doesn't work either try the nandroid (https://www.androidfilehost.com/?fid=24052804347832070) from jerbear, it was done on an unmodified me176c with lollipop, you must use the tethered recovery, make a backup, reboot, replace your back up files by the files of the nandroid, then reuse the tethered recovery and restore from the new back up. Ask jerbear from this forum for further explanation, i'm just a user who had the same problem, not a specialist.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Ps; the system will do an update after the nandroid restore, it is an older version of the me176c's lollipop rom.
Saarge said:
If you have a ww sku try to put this file (http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36_KK-user.zip) on the root of you microSD card and reboot the tab, it should try to flash it (well not on first reboot, you'll have a notification asking you if you want to do the update); if this doesn't work either try the nandroid (https://www.androidfilehost.com/?fid=24052804347832070) from jerbear, it was done on an unmodified me176c with lollipop, you must use the tethered recovery, make a backup, reboot, replace your back up files by the files of the nandroid, then reuse the tethered recovery and restore from the new back up. Ask jerbear from this forum for further explanation, i'm just a user who had the same problem, not a specialist.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Ps; the system will do an update after the nandroid restore, it is an older version of the me176c's lollipop rom.
Click to expand...
Click to collapse
I have the ME176CX not the ME176C i think that has something to do with it
Dublin2275 said:
I have the ME176CX not the ME176C i think that has something to do with it
Click to expand...
Click to collapse
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Saarge said:
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Click to expand...
Click to collapse
Does that update mess up the current root i have? Will i need to do a fresh install?
Saarge said:
No, it's the same rom, the difference between them is just the quality of the cams, btw i have a 176cx too and can guaranty you it works.
Click to expand...
Click to collapse
And also if i do a factory reset will i still have the update or can i get it all the way back?
Dublin2275 said:
Does that update mess up the current root i have? Will i need to do a fresh install?
Click to expand...
Click to collapse
You'll have to root again indeed, but remember what i said in the start, you're likely to regret it if you manage to do the update, it's a very bugged one.
---------- Post added at 09:51 AM ---------- Previous post was at 09:44 AM ----------
Dublin2275 said:
And also if i do a factory reset will i still have the update or can i get it all the way back?
Click to expand...
Click to collapse
a factory reset doesn't give you the original rom, the update will still be there, the downgrade is a very tricky process, and i answered you only because you asked, but i repeat myself, you should really keep your tab the way it is now, i regretted having done the update for months until someone finally found a way to roll-back to kitkat.
With lollipop you'll have:
-memory leak (can be fixed anyway).
-overheating.
-crashes.
-apps closing themselves or refusing to launch.
-random reboots of the tab itself.
-some users even had clock issues on the tab (too slow).
-others had battery life issue (tablet discharging too fast).
---------- Post added at 09:56 AM ---------- Previous post was at 09:51 AM ----------
oh and i forgot, google apps crashs.
I rooted and installed and tried to change DPI with Le DPI Changer, after reboot softbricked
Will not boot at all but I can get into recovery
Tried to reset to factory with no help at all
Any help would be great
Ok, i kinda fixed it, has to reflash the stock rom, but at least it is working now....ugh, all that configurations for nothing
can anyone tell me why it bricked/boolooped
LicQuyd said:
Ok, i kinda fixed it, has to reflash the stock rom, but at least it is working now....ugh, all that configurations for nothing
can anyone tell me why it bricked/boolooped
Click to expand...
Click to collapse
Which value did you set ?..I think 480 is stock..
Probably you've set it to low....
cultofluna said:
Which value did you set ?..I think 480 is stock..
Probably you've set it to low....
Click to expand...
Click to collapse
I actually set it to 480
just root, and then install TWRP. now go into a file manager, and make a backup of build.prop then edit the original build.prop for your DPI change and reboot. After that if it doesn't boot, use twrp to restore the backup via the file manager in twrp.
For info on build.prop, google is your friend.
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
You can always make a backup of your entire ROM. Make changes. And if crashes happen just restore the backup. It takes time. But no brain power
Same for me, tried to set 400. Phone doesn´t boot anymore. I can get to twrp.
no issue here adding this line in build.prop
ro.sf.lcd_density=400
kenzolo said:
no issue here adding this line in build.prop
ro.sf.lcd_density=400
Click to expand...
Click to collapse
I will try that when i can get it to boot. Factory reset didn´t help either.
---------- Post added at 18:31 ---------- Previous post was at 18:19 ----------
LicQuyd said:
Ok, i kinda fixed it, has to reflash the stock rom, but at least it is working now....ugh, all that configurations for nothing
Click to expand...
Click to collapse
Where did you find the stock rom? It seems that i need to reflash it too. I´m just stuck at the 1+ logo now.
lindahl85 said:
I will try that when i can get it to boot. Factory reset didn´t help either.
---------- Post added at 18:31 ---------- Previous post was at 18:19 ----------
Where did you find the stock rom? It seems that i need to reflash it too. I´m just stuck at the 1+ logo now.
Click to expand...
Click to collapse
Official 3.5.3 rom, get it here