Hello, I've got a BIG problem. I've used LCD Density Changer on my ONDA TQ150 (Gingerbread 2.3.4) but I've chosen a wrong value and the phone shows a black screen after the bootscreen. I've tried with update.zip via recovery but even if I've signed the file with autosign I've got a sign error message. How can I repair this?
Thanks in advance. I attach both build.prop and update.zip files
What do you need the density set at?
EDIT: There are 2 update scripts in meta-inf/com/google/android. Try deleting update-script and leave updater-script (use 7-zip to open zip, navigate to folder and right click, delete update-script)
Then try and flash again, should work then. NOTE: current density is set to 120dpi on the build.prop in the update zip. If you need to change that let me know and ill upload another update zip for you.
Ok I'll try I think I won' t try to change density again :-D
Thanks a lot.
Sent from my X8 using XDA
I've just tried, nothing to do I receive the same message (signature verification failed) but if I've already signed the update.
I use the android stock recovery because there aren't others tools for my phone (it's not a popular model because it's sold only in Italy, even if I think it's a rebrand).
What do you need the density set to? Ill make an update zip for you.
Sent from my HTC ENR_U using Tapatalk
I don't want to change density for now, I want only to resume my phone so, 120 would be good (it's the default value)... thanks in advance but if I apply your zip I will not have the signing error?
Hopefully the attached update zip should work. Let me know how it goes.
Same error
E:signature verification failed
Ok i think its something to do with how stock recovery handles update zips. I found some info HERE I think the only way you can do it is to install a custom recovery. Google is your friend from now im afraid, ive reached the end of my expertise. Good Luck!
Thanks for evertything... I cannot root again the phone because it doesn't boot so I think I'll ship it to the seller. Thanks again, I appreciated it so much.
If its already rooted, do you still have the rom zip on your sd card? Could you not just reflash the rom? Or take the memory card out, put it in a card reader, plug into your computer, put rom on sd card, put back in phone, flash. That will revert dpi back to standard.
No it's not rooted now, 'cause after this problem I've made a wipe data/cache hoping to resolve but without luck. So actually it's not rooted and I've not got a backup because the stock recovery doesn't permit this
use adb pull system/build.prop
then u can edit it and
push
adb push (pullthe build prop here) system/
As I specified the phone refuses to boot so I cannot access ADB. But today I'll go to the seller and I see what can I do. I brought this 5 days ago.
By the way, for this price I think it's good, so if someone want to buy this phone can find it in two stores: www.marcopoloshop.it and http://www.expert-italia.it/
It's not too much fast (cpu @600 MHz) but he's got a full qwerty and Gingerbread for 69 euros! I use it as second phone. Not bad
Related
I have an S-OFF HTC Incredible S 4G running 2.3.3 trying to get it rooted, I am trying to keep up but so use to stupid iPhone modding/themeing so just lost on how to send or use my SD card for ROMS? Can I just use the old word (shsh) files over to my phone while its plugged in its the Fdisk and do I put the files into 'root', I have installed Superuser app/ROM Manager app onto my phone also have Gingerbreak.v.120apk on my desktop plus Superuser.apk am I lost or what and anyone willing to help but go easy on me?
Thanks, TheCrow
Do you have ClockworkMod Recovery installed?
I have ROM Manager installed off the Market but my question is probably the one that I'm can't get the answer for which is, how do I transfer things onto my SD card cuz I have played a lot with my old iPhone 4 with mods/themes and so on but never had to write to my SD card atleast I don't think I did thats why I ask if its as easy as dragging and dropping files over to my phone while its plugged into my computer as 'use as driver'? I can't even get the CWM to work properly because it says something about 'special privillages', I have S-OFF but just want to get rooted so I can move on to the fun . Do I need something set on my phone or installed to get going, I also put Superuser & Astro on my phone from the Market so can if you have the time just give me a few dumby steps to point me in the right direction and I am over at the Android Newzealand site which is awesome but they get most files from here and only one guy is trying to help
Thanks, TheCrow
@Crow1372
I am all about trying to get things done in the easiest way possible to help the people that are new to Android.
This method has worked for me but there is no guarentee that it will work for you and I am no way responsible for anything that happens to your device.
DO THE ROOTING PROCESS AT YOUR OWN RISK
Procedure to Root HTC Incredible S
1. Install the ADB on your computer, but before that you will have to turn on the USB debugging in your incredible S which can be turned ON by pressing the “Menu” key first then “Settings” > “Applications” > “Development”. Now here you will find an option of “USB debugging”, select the option and just accept the warning which it will pop up. It’s very important to put the device in the USB debugging and also important to go through the ADB setup process without which it’s not advised to proceed.
2. Now you will have to download the Rooting package which you will have to unzip the same and need to place in the location path c:\adb after which you will have to connect the phone to the computer.
3. Now, open the command prompt and key in the “cmd” and then you will have to make use of the change directory command so that the directory in which you have placed the rooting file can be accessed.
4. Next type in the “pushroot” and enter the same, basically this will push in the pushroot.bat file.
After this type in adb shell /data/local/tmp/getroot and after that type in adb shell and press enter.
After typing in the above commands, you will now be prompted as # after which you will have to type in /data/local/tmp/pushroot.
That’s it you have now successfully rooted the HTC Incredible S
TheCrow1372 said:
I have ROM Manager installed off the Market but my question is probably the one that I'm can't get the answer for which is, how do I transfer things onto my SD card cuz I have played a lot with my old iPhone 4 with mods/themes and so on but never had to write to my SD card atleast I don't think I did thats why I ask if its as easy as dragging and dropping files over to my phone while its plugged into my computer as 'use as driver'? I can't even get the CWM to work properly because it says something about 'special privillages', I have S-OFF but just want to get rooted so I can move on to the fun . Do I need something set on my phone or installed to get going, I also put Superuser & Astro on my phone from the Market so can if you have the time just give me a few dumby steps to point me in the right direction and I am over at the Android Newzealand site which is awesome but they get most files from here and only one guy is trying to help
Thanks, TheCrow
@Crow1372
Click to expand...
Click to collapse
Try reflashing CWM Recovery. Since you have S-OFF, it should work. If you get it to work, then flash (install zip from SD in CWM) the attached file and you should be rooted.
Theonew said:
Try reflashing CWM Recovery. Since you have S-OFF, it should work. If you get it to work, then flash (install zip from SD in CWM) the attached file and you should be rooted.
Click to expand...
Click to collapse
I appreciate the one above yours and kinda understand it but waaay too indepth maybe, I also tried yours but when I go to HBoot menu and Recovery to look for the .zip file it is no where and I plugged my device into computer and 'debugging Enabled' also set my connection as 'disk drive' to load the file to my SD card but still can't find it?? I can't believe it is this hard cuz I see many others rooted and flying away on their Incredible S 4G, I was able to get the Gingerbreak.v.1.20apk on my device but it just keeps loading and saying that it will reboot once successful but after 20-30mins I figured it was not going to work also I have ROM Manager installed already but as you know no Superuser previlliages yet so can't load CWM
TheCrow1372 said:
but as you know no Superuser previlliages yet so can't load CWM
Click to expand...
Click to collapse
Have you tried searching for the zip when your device is NOT connected to your pc? And just so you know, you do NOT need superuser privileges (root) to be able to use ClockworkMod especially since you already have S-OFF. Have you tried flashing a different version of ClockworkMod? You could try using this: http://forum.xda-developers.com/showthread.php?t=794638 to flash it from your PC.
Theonew said:
Have you tried searching for the zip when your device is NOT connected to your pc? And just so you know, you do NOT need superuser privileges (root) to be able to use ClockworkMod especially since you already have S-OFF. Have you tried flashing a different version of ClockworkMod? You could try using this: http://forum.xda-developers.com/showthread.php?t=794638 to flash it from your PC.
Click to expand...
Click to collapse
I'll try finding it without being plugged in to pc, I put Gingerbreak.v.1.20apk on my SD card no issues so I shouldn't have an issue putting the CWM on but do you have a newer version (sorry) also do you think one of my issues is that I have a CWM on my 'Astro' file finder but the files say they don't exist so should I delete it and start over with a newer one that you may have and should I take of ROM Manager until I finish putting these files in cuz it should not be this hard others are rooted on their Incredible S 4G 2.3.3.
TheCrow1372 said:
so I shouldn't have an issue putting the CWM on
Click to expand...
Click to collapse
Please explain this. Here's the image: http://downloads.unrevoked.com/recoveries/cwm-4.0.1.4-vivo.img .
I can't open that image, my Winrar is acting up can you explain the image please (sorry)?
Also when I go to my 'Programs' on my computer 'Uninstall' it shows the SDK Tools with an 'X' beside it like it did not fully install, I don't know if I really need the ADB & SDK tools but I'll keep trying that later but I want to try your methods as well cuz as I mentioned it should not be this hard to root my phone right but I have to go to Doctors so I will check in later and keep trying
TheCrow1372 said:
I can't open that image, my Winrar is acting up can you explain the image please (sorry)?
Click to expand...
Click to collapse
You are not supposed to open the image. Download Android Flasher, connect your device to your pc, run Android Flasher, select recovery (at the side), find the image file you downloaded, select it, click ok (and again if necessary), and it'll do the rest.
Question, I drag and drop files over to my phone while plugged in to my SD card but everyone says to the root folder I just don't have a 'root' folder so one guy said to drop the files into the very first one and that is what I did with Gingerbreak.v1.20apk but it just says its rooting and will reboot device when done? After 3 attempts each at 15-25mins the wheel is still spinning so am I putting it in the right spot, Gingerbreak does show up in my apps drawer but the unzipped versions of CWM or Superuser never show up on my device even when I go to 'recovery' through Revolutionary to unzip it?
TheCrow1372 said:
Question, I drag and drop files over to my phone while plugged in to my SD card but everyone says to the root folder I just don't have a 'root' folder so one guy said to drop the files into the very first one and that is what I did with Gingerbreak.v1.20apk but it just says its rooting and will reboot device when done? After 3 attempts each at 15-25mins the wheel is still spinning so am I putting it in the right spot, Gingerbreak does show up in my apps drawer but the unzipped versions of CWM or Superuser never show up on my device even when I go to 'recovery' through Revolutionary to unzip it?
Click to expand...
Click to collapse
Did you read/understand my previous post?
Kinda but how does that have anything to do with rooting my Incredible S (sorry) its just that I'm new to HTC devices and I've been told that I have to be rooted to put ROM themes on my device and I have S-OFF, thats not enough is it? I tried the guy above yous method of ADB but my computer does not 'recognize that path', I did exactly what his video says but again is either of these methods going to get me 'rooted cuz all I want to do is start enjoying my phone plus your saying I don't have to have 'Superuser Permissions' to use CWM?? Sorry bro if I'm being difficult but I just want to be rooted already and have you heard of this angermod or what ever its called, like Gingerbreak or something?
HELP PLEASE lol, thanks
Forget about Gingerbreak. The tool (and instructions) is to flash the custom recovery (ClockworkMod) to your device. I said this before, and I'll say it again, using ClockworkMod recovery DOES NOT require root. You are going to root your device by using Clockwork to flash the file attached in post #5. After flashing that file, your device will be rooted.
When I go to extract it they ask for a gehroot password, I copied what looks like a password under my Incredible S/Vivo but that one did not work for the CWM download
I will try this tomorrow 4 sure and thanks for your patients, fill you in when I'm rooted (hopefully) Also is there a special password to download the CWM for my Incredible S/Vivo, sorry again?
One more question (sorry) the one I did download the other day was supposed to be CWM but it has all kinds of other files with it like 13 files including 'SuperOneClick' also suv1/v2/v3 plus 'busybox' but don't see cwm anywhere so anyway do I use the 'Android Flasher' and flash all of them like the whole folder or each one individually?
In the CWM image file, there are like 13 files that came with it like suv1/v2/v3 plus busybox and SuperOneClick so which or all of these files do I flash with Android Flasher?
[GUIDE-IMPORTANT!] "rescue-backdoor" - regarding bootloop, do it before change in sys
UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- do not use "File Manager HD" or other filemanager, which doesn't support root operations (thx kryddan),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
To enter RECOVERY-MODE - power off device,
hold vol-down + power button.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Remember, that after reflash in recovery, your build.prop will be updated back
to higher value, then to be safe you need to reapply modification!
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
great guide, thank you
I think an automated-script would be much appreciated
condi said:
Hi guys,
We've got now ROOT. We can do a lot of things, which we couldn't do before.
But before you begin to make changes in system files, first you need to know few things.
Few users experienced "bootloop". Its brick state. There is no access to shell, no adb.
Damaged device.
How to avoid that?
Yes, there is a solution. We need to get proper update zip for our device.
We also need to fool device, that it is a newer file, than the firmware in device.
How to, step by step:
Of course, ROOT is required.
To get proper ota-update-zip for your device you have to edit /build.prop:
- easiest way is via "Root Explorer", or directly via "build.prop Editor" (in market, free),
- always make backup of files, which you are modifying,
- change value of "ro.sony.build.incremental" to lower one to fake firmware version,
- for example on my device newest firmware has: "ro.sony.build.incremental=111201022" - decrease that value,
in my case to 111201021.
Reboot device.
OTA update notification will appear - click on "Download" button.
Wait until download finishes, but don't click "Update"!!!
I repeat - DON'T CLICK UPDATE! It will reflash firmware,
and you will have to make everything from the beginning (inc. root).
Update zip is located in /cache/ota/signed-nbx03_.......zip - make a copy to safe place - external sd and/or in pc.
Leave build.prop modified. IMPORTANT. Don't revert back changes.
When you want to flash your device, Sony Tablet is checking few things:
is update zip proper one - signed one,
is the update zip - for your region - SKU value,
is the update zip is newer one than firmware in device - equal and higher will not update,
only lower - thats what we're faking.
If you will revert back build.prop = update will fail,
if you will try to update with other region update zip = update fail.
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
I have tested that "rescue-backdoor" on my own device,
deleted some system framework file - of course bootloop, without adb access.
Flashed through recovery - voila, device fixed
Of course, everything what you do with your device, you are doing at your own
risk. I'm sure that in 99% cases with "rescue-backdoor" you will fix your device,
always could be that other 0,01% case.
One condition for sure = build.prop file has to be correct.
[OPTIONAL]
You can disable ota update notification - which appears on every reboot.
To do this use "Titanium Backup" app, look for "System Update" app on list,
and use "Freeze" option
Any questions, suggestions - just ask
PS. I'm thining about writing auto-script for that...
br
condi
Click to expand...
Click to collapse
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
It should be under '/cache/ota' ... nowhere else ..
Judah001 said:
Thanks Condi! Download worked great but under my cache there is nothing. Could the file be located elsewhere?
Click to expand...
Click to collapse
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
condi said:
Be sure that ota has been download, check again /cache/ota.
If still no zip, then run 'adb shell' then:
Code:
su
find -name *signed*
or
Code:
find -name *.zip
If your ota update will be in different location, then please post it.
br
condi
Click to expand...
Click to collapse
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Thank you condi... The instructions worked perfectly!!
Judah001 said:
ok I will try once I am home through adb. So far there is nothing under my cache folder. I am using file manager HD but it should pick up a zip file.
Click to expand...
Click to collapse
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
kryddan said:
Just a little tip. I'd suggest you use Root Explorer instead of File Manager HD.
You see, File Manager HD does not show the files in /cache. (mine didn't)
I tried File Manager HD on my tablet and found nothing inside /cache
But with Root Explorer I found three different directories. There among OTA.
Click to expand...
Click to collapse
That did the trick. I used the root browser in rom tool box and copied the zip to my sd card. Thank you for the help guys.
Good advice kyddan ... same on my tab with file manager HD.
I work normally with Root Explorer or File Expert.
Both show the folders and files in /cache .. File Manager HD do not.
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
EDIT: nevermind. I did so. Worked.
sebarkh said:
my ro.sony.build.incremental is 111201038
Do I have to decrease it by 1 to 111201037 ?
Click to expand...
Click to collapse
Yep, exacty. And then you will get newest ota zip of 111201038 pozdro
hahahahah I just had brick... I'm working on auto-install script for "rescue-backdoor", and accidentally I've pushed empty 0bytes build.prop - after reboot - sony logo, then black screen.... and guess what...
recovery reads incremental value (which doesnt exists..) as "0" zero
so i've got lower value, and reflash done.
after reboot my tab started correctly, but.. after reboot again brick - black screen.
fortunatelly - after few min with black screen i've got adb access.
but for first - i can't get root access.. 'su' not works.
but... '/system/xbin/su' works root lets check - build.prop still empty,
remounted system as rw, pushed correct build.prop - ahhh again working !!
that was good experience hahah.
-------------edit:
i've got auto-install tool ready... need to make one more full test with my device and will publish it.
full automatic !!!!!
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
ase3000 said:
This is driving me crazy. why everyone is getting update message when changing the incremental value while my dumass tablet keeps saying that my system is up to date
Click to expand...
Click to collapse
Just wait for automatic-tool. Its ready, but need to make final tests.
condi said:
So if we stay with modified build.prop = we can just enter recovery,
and update from external sd card, to our downloaded update zip
Click to expand...
Click to collapse
In which way we can enter to recovery??
riccardo91 said:
In which way we can enter to recovery??
Click to expand...
Click to collapse
power off, hold vol-down + power.
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
riccardo91 said:
All done! It works well! Thanks! Avoiding bootloop it's even a good thing!
Click to expand...
Click to collapse
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
condi said:
Great Just remember one thing - after reflash in recovery, your build.prop will be updated to higher value - then to be safe you need to reapply modification!
--- my 100th post !
Click to expand...
Click to collapse
I bricked my XTS playuing with build.prop. Shame I didn't see this post before. For future - how can I edit build.prop in a safe way? I changed file permission then I forgot to restore default. After restart brick. Do I need to change permission to edit build.prop then do i NEED to restore proper permission back? I'm still confused with it
Galaxy S2
Long story short I tried to change dpi to 160 and it never booted again, managed to make a backup with the build.prop which has now got 160 in it
after trying adb and clockwork recovery to work, I gave up on my phone and re installed the rom.
The backup which I made has 5 files in it, I need help with this file:
system.ext4 which is a (.tar) file. Somehow I have to get the right build.prop file back inside. I can't use the 'system.ext4 ' of any previous backup as it gives me md5 mismatch, I have even tried to recover backups from previous date but recovery keeps telling me md5 mismatch. The main thing I am trying to get done is put the right build.prop from the previous backups 'system.ext4' to the latest backup which has the wrong dpi settings in it.
If anyone knows how to change a .tar file and can help me with it, please let me know. I have looked and tried at every alternative way but nothing is working out. Its 5 am and now I am going to sleep, hopefully by tomorrow I will get some helpfull reply.
Thank you surgeons.
So adb doesn't work? If it does have you tried doing "adb push build.prop /".
You could just extract the .tar from both and replace the build.prop from the bad one then push the new system to the phone with adb
Sent from my GT-I9100 using Tapatalk 2
thisisuzair said:
Galaxy S2
Long story short I tried to change dpi to 160 and it never booted again, managed to make a backup with the build.prop which has now got 160 in it
after trying adb and clockwork recovery to work, I gave up on my phone and re installed the rom.
The backup which I made has 5 files in it, I need help with this file:
system.ext4 which is a (.tar) file. Somehow I have to get the right build.prop file back inside. I can't use the 'system.ext4 ' of any previous backup as it gives me md5 mismatch, I have even tried to recover backups from previous date but recovery keeps telling me md5 mismatch. The main thing I am trying to get done is put the right build.prop from the previous backups 'system.ext4' to the latest backup which has the wrong dpi settings in it.
If anyone knows how to change a .tar file and can help me with it, please let me know. I have looked and tried at every alternative way but nothing is working out. Its 5 am and now I am going to sleep, hopefully by tomorrow I will get some helpfull reply.
Thank you surgeons.
Click to expand...
Click to collapse
Install droid explorer. Boot into cwm. Replace the build.prop with 240dpi or whichever you like.
victorator said:
Install droid explorer. Boot into cwm. Replace the build.prop with 240dpi or whichever you like.
Click to expand...
Click to collapse
Right now I am on a fresh rom, would I be able to send the right build prop using your method. Into the system.ext4 tar file I have. If that works I can recover the whole backup.
Update:
I extracted the system.ext4 files of the backup and paste the right build.prop file inside the extracted folder. Now using the explorer app from the android market I have been able to recreate the new 'system.ext4.tar' file with the right build.prop which has 240 as its dpi.
Now this is where I need your advice people. I can go ahead and change the nandroid.md5 and change the md5 value to match the value for the new 'system.ext4.tar' file. So this will not give me the md5 mismatch error. My question is that would this actually work?
Thread to be closed.
Sent from my GT-I9100 using cracked xda premium
Thread closed
Per request.
Hi folks
I hope I am not breaking any rules. I tried my best to read up on the problem and see if it's already been fixed. So far I haven't encountered anything which is specific to my needs, but I learned enough to pose a well-formed question.
Phone: Samsung Galaxy SIII International (GT-I9300)
ROM: Stock Samsung, version 4.1.2, the update with Multi-window. Do not have the exact build number unfortunately.
Root status: Rooted
Recovery: Stock recovery. (I JUST rooted the phone, nothing else.)
So the problem is:
1. I used ES File Explorer in root mode, mounted /system as writable, and made an edit to build.prop (added "qemu.hw.mainkeys=0" to the end of the file to enable navbar) and saved the file. I rebooted the phone and now it is stuck with a looping Samsung logo.
2. I have made a backup of build.prop and placed it in /sdcard/ but unfortunately I haven't made a copy on my PC. Also note that I don't have an external SD card, I am using the 16GB space that came with the phone. So the build.prop backup is on the phone.
3. I do not have a USB cable (I have one that has a loose connection somewhere and my phone is not detected 99% of the times I've used that cable)
What I have found after 2 hours of searching online:
1. Factory Reset through recovery (I am able to boot into stock recovery by doing Vol Up + Home + Power) will not restore /system partition so that won't fix this.
2. ES File Explorer might have messed up the file permissions of the build.prop file.
3. I can use PC ODIN to flash the stock firmware (I might lose data but at least the phone would be back to normal).
4. I can use adb to push a good build.prop file and set the correct permissions (my most fav. set of instructions are from here: http://forum.xda-developers.com/showthread.php?t=1660596 Of course I got the idea from several other threads)
5. I can sideload a good build.prop file that someone might be generous to provide me using adb.
I don't have a data cable, so you can see how that Might be a problem. What I DO have is a USB OTG cable and a pen drive. Now, in the stock recovery, I noticed an option "apply update from external storage". Assuming I have an update.zip with the proper build.prop in it, can I load the update.zip into a usb pen drive (formatted to fat32)? Does "apply update" here work for such zip files or is it only meant to be used for full firmware images? If so, can I just download the latest stock firmware and apply it from here without wiping the /data partition?
If I can get this resolved tonight I can get my phone up and running before tomorrow's work week. I will buy an USB cable ASAP (it's 12 AM here so going out to get it is not an option now). But even if I do, I still have 5 months worth warranty left and I'd like to stick with the stock recovery and avoid incrementing the flash counter altogether, despite Triangle Away.
Thank you very much for the help in advance.
Adb pull your backup» then push it back?
slaphead20 said:
Adb pull your backup» then push it back?
Click to expand...
Click to collapse
I don't have a working data cable, so I cannot connect to the PC. That was my first idea, though, thanks! I am currently reading about making an Update.zip. It's very unfortunate that I didn't note my firmware details after the OTA...
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work.
LenAsh said:
Just set permissions - use Properties in ES FE in root mode. RW. R.. R.. should work. If not try 777 for giggles.
Click to expand...
Click to collapse
I am unable to boot into the phone, it is stuck in a bootloop
I don't have a USB cable to use ADB. I don't even have a custom recovery. All I have is the stock recovery and the option to "apply update from external storage". I now remembered that I also have an SD card on which I can put an update.zip or the stock firmware. Unfortunately I didn't note down the firmware details after the last OTA from 4.1.1 to 4.1.2, so I don't know which one to download.
Can I use the option "apply update from external storage" to flash an update.zip or is that only meant for full firmwares? Thanks!
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
LenAsh said:
Oops - silly me.
You are running stock recovery - never use it but does it have a fix permissions option?
Failing that you may have to reflash the ROM. Stock recovery is very restrictive on what you can flash.
Click to expand...
Click to collapse
Fix permission option on the stock recovery? I don't think so, haven't been able to find it. Here are the options I have:
reboot system now
apply update from adb
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Interestingly, when I selected the last option, it had these 3 folders:
fota/
lost+found/
recovery/
I was hoping fota/ had the files from my last OTA update but nope.
I guess you are not sure whether I can flash an update.zip through stock recovery... so I just have to wait till I get my USB cable and try out some adb magic?
EDIT: I'm retiring for the day. Thanks for the suggestions @LenAsh and @slaphead20. I'm gonna buy a cable next week and try to set the permission to 644 (RW-R-R) using this thread as my reference (http://forum.xda-developers.com/showthread.php?t=1660596). Thanks for your suggestions, I will post back when this is all resolved.
In the meanwhile, please keep the ideas coming
PS: Oh wait, I am still curious. What is the worst thing that could happen if I try to flash an update.zip through stock recovery? I am very curious to see if it will work.
You could flash a later custom recovery (this one works well http://forum.xda-developers.com/showthread.php?t=2002953) via Odin and then fix permissions that way. Even if that doesn't work, you could then flash anything you like without having issues that the stock recovery presents.
EDit: still need a cable though...
Trouble is he hasn't got a cable, I had same thinking, that he could use the aroma file manager in philz but he's stuffed without a cable!
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
LenAsh said:
Stock recovery won't let you flash anything much... so perhaps his only option is Odin. When he has a cable.
On a side-note, how can someone not have a USB cable of any kind kicking around??
Click to expand...
Click to collapse
Just edited my post
Sent from my GT-I9300 using xda premium
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
ficti0n851 said:
Possible to make an update.zip with just the build.prop in it. Copy it to a memory card and use recovery to flash it?
I would try that first.
Edit: i just remembered i have done that a few times with my htc desire. Was running clockwork mod though.
Its really easy, find a small flashable mod in zip format and delete all the mod files and copy your build prop in. Edit the updater script to just write your /system/build.prop.
Copy the zip to you mem card. Use a usb adapter in a pc, stick it in your phone and use recovery to flash from external sd.
And after typing all that i reread your post and your running stock recovery and i think you would need a signature or something on the zip so it would not work. Ooops.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
gautham_y said:
@LenAsh, @slaphead20, @ficti0n851
Hehe, yeah, I'm stuffed without a cable I lost it recently and I'm the only one with a recent phone. All my family members' phones use different cables.
Anyway, I managed to borrow a friend's cable and am currently downloading drivers for the S3. Once that's done I will use ADB to set the file permission and try rebooting my phone, failing which I will restore the backup build.prop, set permissions and reboot the phone. Failing which... well, maybe I'll reflash the stock firmware (I managed to find out the exact build details btw! )
I'll keep you posted, thanks for taking the time guys
--
EDIT:
ADB was a success! I got in and changed the permission to 644 and rebooted, done! Funny thing was that /system/build.prop file was not even there, there was only /system/build.prop.bak. I was not able to find my original backup on the sd card, but I copied the .bak file (probably generated by ES FE) and set its permissions and that worked. And now I have also have the software keys!
Thanks for your comments guys. This was fun!
----
EDIT 2:
For anybody else who has the same problem, I did it using the commands in these great ADB guides:
http://forum.xda-developers.com/showthread.php?t=1660596
and
http://forum.xda-developers.com/showthread.php?t=879701
Also, how do I edit the title of the topic? Want to add a [Solved] tag.
Click to expand...
Click to collapse
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
black_hawk1990 said:
Hey, I know this post is from forever ago, but is there a chance you could explain this step by step for a noob?
I have got my phone stuck in a bootloop by fiddling with build.prop, and I have the original file before playing with it. I have a rooted device with custom recovery, so how I could I use minimal ADB to push the original build.prop located on my device (sdcard) to root/system??
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
Bro, I got the same problem as you had, except that I have a custom recovery, and the original build.prop file, and a USB cable, but I still haven't figured out what to do completly. Can you please take a minute to explain this for a complete noob? You have probably forgot all about this, but I am shooting for this chance. :/
Click to expand...
Click to collapse
Hey, are you still having problems or did you solve it yourself? Anyway... If you still don't know what to do, describe best what you did to end up in a bootloop. As far as I understand what your problem is, you should use your recovery to move the backup of the original build.prop file to the system folder.
I changed my phones build.prop and when rebooted it does not started and ended up in bootloop and when I searched for how to fix this problem it showed that clear all the data from the phone but nothing happened and when I tried to install custom ROM in my phone my pc is not detecteing my phone .so what should i do ?
@Rajsh90: pull out battery for some minutes, put it in, reboot into downloadmode. Connect with PC, start Odin and hope that a COM-flag colours. Flash latest firmware.
Hi guys!
I was hoping one of you could help me.
Yesterday i modified a build.prop file on my NextBook EBM8000ND (Next800T) tablet, causing it to get stuck in a bootloop every time it's turned on. I've been searching the Internet all day long but it's hard to find support when you have a device which no one in the world uses . It was rooted but I did a factory reset hoping that it would fix it. It didn't and now it's also unrooted. I tried to make a custom update.zip with the backup of the original build.prop file but the stock recovery simply refuses to load any update file. It always stops at verification. I used 7zip with store option. I tried signing the zip, I even edited the updater script to only print some text on the screen but the recovery still wouldn't load it. I tried to find a way to install CWM using sdcard but with no luck. When i tried to use ADB in recovery the device says: "failed to open driver control: No such file or directory". It might be worth mentioning that I found my device's ROM online with boot.img and recovery.img files and a .tar file which contains the original system folder.
Is there any way to make the stock recovery (since installing CWM or TWRP seems impossible) read my update file? Or is there another way to fix this? I only need to replace that single file.
Hoping to get help soon.
Cheers!