I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?
Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
greenmaze said:
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?
Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
Click to expand...
Click to collapse
first you need same build.prop from same device. ask your friend use xda.
ask them to give you build.prop
after getting build.prop
use adb delete your first build.prop
and then push your build.prop(which you got from your friend)
to /system/
just press me thank if i helped you
greenmaze said:
I messed up my build.prop and now my tablet (10.1) won't boot. Is there any way to fix build.prop in download or recovery mode?
Using the "apply update from ADB" option in recovery doesn't seem to permit normal adb commands like pull and push.
Click to expand...
Click to collapse
Whenever you mess up with system files like build.prop, a backup of that file is automatically created in the same location with .bak extension. So if you want you can use aroma file manager to find that file and rename it to build.prop, set permissions and that's it !
Thanks for the help. The problem is that I can't get any adb commands to work (i.e. push or pull) in recovery mode. The devices command lists the tablet with the name "sideload". Am I doing something wrong?
Sent from my Nexus 5 using Tapatalk
To elaborate a little more, whenever I try an adb command I get the following message:
Code:
error: closed
Is there another way to get the tablet into a mode where it will accept adb commands?
AbhiLP said:
... So if you want you can use aroma file manager to find that file and rename it to build.prop, set permissions and that's it !
Click to expand...
Click to collapse
I wasn't sure what Aroma Filemanager was so I looked it up. Unfortunantly I'm unable to get Aroma Filemanager to work. I downloaded the zip to a SD card, booted into recovery, selected "apply update from ADB" and then selected the Aroma zip file. Some messages scroll on the screen and then tablet reboots. If I try sideloading the Aroma zip I get this output:
Code:
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
Fixed it
I finally fixed my problem. I pieced together information from various posts to get me there. In case someone else runs into a similar issue, here's what I had to do:
Install TWRP via Odin. You won't find a TWRP for 10.1 WiFi model (SM-T520) on the TWRP website. I found a link in another thread for TWRP that works: http://goo.im/devs/OpenRecovery/picassowifi
Boot into recovery and copy /system/build.prop to an SD card.
Fix* the build.prop issue on a PC (or anything else than can edit the file on the SD card)
Back in TWRP, copy the build.prop file from the SD card over the /system/build.prop file.
* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
greenmaze said:
I finally fixed my problem. I pieced together information from various posts to get me there. In case someone else runs into a similar issue, here's what I had to do:
Install TWRP via Odin. You won't find a TWRP for 10.1 WiFi model (SM-T520) on the TWRP website. I found a link in another thread for TWRP that works: http://goo.im/devs/OpenRecovery/picassowifi
Boot into recovery and copy /system/build.prop to an SD card.
Fix* the build.prop issue on a PC (or anything else than can edit the file on the SD card)
Back in TWRP, copy the build.prop file from the SD card over the /system/build.prop file.
* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
Click to expand...
Click to collapse
Can't access SD here, when mounting in CWM it mounts as a CD Rom and can't access it, never seen this...
I always recommend to flash the whole rom using odin if you don't have a custom recovery
greenmaze said:
* I'm not even sure my build.prop file was messed up. I performed the steps above and still the tablet wouldn't boot. Remembering that I had changed the permissions on the build.prop file (back when my tablet was still working), I went back into TWRP and changed the build.prop file permissions back to 744. After rebooting my tablet powered up normally. So after all of this it might have just been that the file permissions on build.prop were wrong -- I'm surprised this would prevent the tablet from booting... but what do I know.
Click to expand...
Click to collapse
Thanks for posting your solution(s) when you found them! I had done some manual editing on my build.prop after copying it to my computer and after replacing it on the device I forgot to reset the permissions. Luckily I came across your thread.
Thanks again for posting your solution!
Second thanks for sharing your solution too Greenmaze! My HTC M8 booted to a blank non-responsive screen after modifying the build.prop file. I found out how to go back into recovery mode from another thread below and then fix the build.prop permission from this thread.
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
Basically, I had find a way to get into recovery mode by holding down the power button and volume up button at the blank screen and then exactly after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. Then I use TWRP to chmod the sytem/build.prop permission to 0744 to fix the original boot issue.
T-Ching said:
Second thanks for sharing your solution too Greenmaze! My HTC M8 booted to a blank non-responsive screen after modifying the build.prop file. I found out how to go back into recovery mode from another thread below and then fix the build.prop permission from this thread.
http://forum.xda-developers.com/htc...ter-download-mode-t2853100/page2#post62490577
Basically, I had find a way to get into recovery mode by holding down the power button and volume up button at the blank screen and then exactly after 10 seconds, switch from pressing the volume up to volume down button before the HTC logo white screen shows while still holding down the power button. Then I use TWRP to chmod the sytem/build.prop permission to 0744 to fix the original boot issue.
Click to expand...
Click to collapse
Oh ok, so your HTC is a Samsung Galaxy Tab Pro. Really interested on how you managed that....
Sent from my MB860 using XDA Free mobile app
Build.prop permission boot problem is a generic android issue.
Build.prop permission boot problem is a generic android issue. I added how to go back into recovery specifically for HTC M8 since that was another hard to find solution also in order to fix the build.prop issue. Just being helpful since this solution worked for my M8 and I found it on this Samsung device thread and the other solution on a M8 thread. Don't want people to just get half the fix.
Related
What is it and why am I getting this prompt? I'm rooted with 2.3.4
Obviously I shouldn't accept this update but does anyone know what this is?
Sent from my Xoom using xda premium
Hi. I am new.
I just installed the ROM 2.3.4 last night that was posted in the xda forum(upgraded manually from 2.2 on a Unrevoked rooted Dinc).
I installed the 4.06 ROM and I am reading the official was 4.08...
Do I need another upgrade? Or is this 'the' upgrade that is for root users?
Not trying to steal your post ugxvibe. both of our questions might have similar answers.
if you update will you lose root control? What about all the apps? I'm most concerned about not being able to tether...
Just flash wildstangs 4.08.605.2 ota rom. It is the newest ota update, but already rooted.
how do I do that? Through rom manager?
Is there a way to stop the update reminder from popping up without actually installing it? I'm afraid I might mess up my phone and don't want to risk losing everything g on it.
Guys, to stop the prompt from appearing just press install and it will try to reboot but will just error and u will never see it again trust me .
Sent from my HTC Droid Incredible using xda premium
d-pabs said:
how do I do that? Through rom manager?
Is there a way to stop the update reminder from popping up without actually installing it? I'm afraid I might mess up my phone and don't want to risk losing everything g on it.
Click to expand...
Click to collapse
Yes thru rom manager.
You can dissable the notifications by editing your /system/build.prop file. Look for:
ro.config.htc.nocheckin = 0
and change the 0 to a 1. If you dont see that line add it somewhere in the file.
I went to make the nocheckin = 1 modification, but I already had it, and I'm still getting the update notifications. Not even sure how it got there. All I've done is root with Unrevoked, maybe that does the edit?
NetGoo said:
I went to make the nocheckin = 1 modification, but I already had it, and I'm still getting the update notifications. Not even sure how it got there. All I've done is root with Unrevoked, maybe that does the edit?
Click to expand...
Click to collapse
It should have worked, you may need to clear the cache partition. Or there is another method go to /etc/security and rename otacerts.zip to otacerts.zip.bak
Like what was said above...
If you have Clockwork or some other custom recovery, if you just allow it to update when prompted, it will not install and will cause no other problems. You must have the stock recovery in order for the update to install.
It CANNOT install if you don't have the stock recovery.
But, I would also go into the /cache directory and find the update file and zap it (It will be obvious). I just use ADB and "rm" it from my PC. You could use root explorer or something. Otherwise you will have a big update file just sitting there and hogging space.
cmlusco said:
It should have worked, you may need to clear the cache partition. Or there is another method go to /etc/security and rename otacerts.zip to otacerts.zip.bak
Click to expand...
Click to collapse
I found the file thru root explorer but cannot change it due to message that says it's read only. other options?
Thanks.
bgtruitt said:
I found the file thru root explorer but cannot change it due to message that says it's read only. other options?
Thanks.
Click to expand...
Click to collapse
At the top of the screen in Root Explorer, change r/o to r/w. Then make your change.
Sent from my ADR6300 using xda premium
im rooted n using the clockworld mod for roms, I attempted to run the 4.08 update from User wildstang following the instructions but after installing the update n rebooting it just sits at "Dorid incredible" white screen and never boots. I may be doing something wrong here, can someone break it down for me? suggestions?
NOTE: I use CWMR 5X. Some wipe options below are not included in earlier recovery versions. Still wipe what is available the best you can.
1. Put the Rom on the root of your SD Card
2. Compare MD5 Sum
Windows: MD5 Calculator
LINUX: Open Terminal and type: md5sum [path to the rom on your sd card]
Mac: Open a terminal and type: md5 [path to the rom on your sd card]
3. Reboot to Recovery
4. Wipe these:
Main Screen:
wipe data/factory reset - x2
wipe cache partition - x2
Advanced:
Wipe Dalvik Cache - x3
Wipe Battery Stats - optional
Mounts and Storage:
Format-
/boot - x2
/system - x2
/datadata - x2
/data - x2
/cache - x2
5. Install Rom from SD Card by going back and selecting install from SD card.
6. Reboot and enjoy!
followed each step to the letter but still wont boot : /
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
clutchdroid said:
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
Click to expand...
Click to collapse
Uncheck fastboot in menu > applications.
Thank you sir.
clutchdroid said:
Ok i changed nothing in the method of installing the rom and for whatever reason it worked!! 4.08 now phone is 10X faster and im loving it. Only issue i see now is i cannot get back into clockworld mod! why is that? i hold down power and vol down for a long time and when release it just starts the boot sequence any suggestions?
Click to expand...
Click to collapse
I had the same problem, but after two times running the install its still getting the hang. Hopefully I'll get better luck on try #3.
Did you figure out what caused the temporary issue?
spitzaf said:
I had the same problem, but after two times running the install its still getting the hang. Hopefully I'll get better luck on try #3.
Did you figure out what caused the temporary issue?
Click to expand...
Click to collapse
I may have missed a format inside mounts and storage make sure you hit them all.
cmlusco said:
Yes thru rom manager.
You can dissable the notifications by editing your /system/build.prop file. Look for:
ro.config.htc.nocheckin = 0
and change the 0 to a 1. If you dont see that line add it somewhere in the file.
Click to expand...
Click to collapse
OK I've found the file you're talking about and it doesn't have that line in it so I need to add it. I can't easily get access to a computer right now to run the command line on my phone so i have been trying to use the terminal emulator instead. It says I doesn't have a text editor...is there a way to edit via the emulator? Do you wkno which commands to use?
Thanks again
Yep, still having a minor issue with this. I have added the line suggested and I have cleared my cache yet I still get periodic prompts to install the update. I'm not really keen on doing so. Can anyone else suggest a way to stop the (weekly) prompts?
Thanks
Hey guys,
I have done something stupid.
The phone.
GSM Galaxy Nexus - Android 4.0.2 (ICL53F)
Rooted. otherwise stock.
Current status - will not boot android. Will load fastboot/recovery
I was trying to change the bootanimation.
Could not do it with adb push.
So i tried by copying the .zip file to the phone.
Opened up file File expert (unsure how many use this) clicked on "internal Memory" and tried to mount for read/write.
Copied bootanimation.zip from sd card to /system/media would not paste.
Tried again. Did not paste but it did delete the stock bootanimation.zip file.
Unsure what i clicked but when i tried to open /system/media it try to "execute" it, stated that it could not find a program to do so.
Closed program.
Phone started to come up with differnt apps stating that they have stopped working.
turned off phone, reboot.
Will not load boot animation, just loads to recovery!
I think I will have to flash the stock rom to solve this.
Any help would be great.
Tiggerbits said:
Hey guys,
I have done something stupid.
The phone.
GSM Galaxy Nexus - Android 4.0.2 (ICL53F)
Rooted. otherwise stock.
Current status - will not boot android. Will load fastboot/recovery
I was trying to change the bootanimation.
Could not do it with adb push.
So i tried by copying the .zip file to the phone.
Opened up file File expert (unsure how many use this) clicked on "internal Memory" and tried to mount for read/write.
Copied bootanimation.zip from sd card to /system/media would not paste.
Tried again. Did not paste but it did delete the stock bootanimation.zip file.
Unsure what i clicked but when i tried to open /system/media it try to "execute" it, stated that it could not find a program to do so.
Closed program.
Phone started to come up with differnt apps stating that they have stopped working.
turned off phone, reboot.
Will not load boot animation, just loads to recovery!
I think I will have to flash the stock rom to solve this.
Any help would be great.
Click to expand...
Click to collapse
If this was my phone I'd find a nice rom, stock or not, and install it. I'd follow the dev's installation instructions to a "T".
You could also go this way: http://forum.xda-developers.com/showthread.php?t=1399210
Good luck.
Geezer Squid said:
If this was my phone I'd find a nice rom, stock or not, and install it. I'd follow the dev's installation instructions to a "T".
You could also go this way: http://forum.xda-developers.com/showthread.php?t=1399210
Good luck.
Click to expand...
Click to collapse
I've just flashed the stock image, luck i remembered that i did an adb back up not long ago. so just restoring that.
Than to root and flash cwm and start again. this time i'll be careful
I edited a configuration file for Bluetooth(main.conf) in which i changed the device discoverable for value to be 0 (by default 120). then i left the folder as is (r/w) mode and saves and rebooted.
rescue mode is available(volume up - home -power)
boot loops continously
Kies not recognising when connecting when the device is turned off
there is a backup of the file at the same folder..
if you can provide me too ..how do i upload to my phone.
need help ASAP.
try installing firmware with odin
Other better ideas!
I am pretty sure that this matter was triggered because of that tweak..(editing of the file). I hope that restoring the original file would help.
Do you know about adb...?
Also i forgot where the actual bluetooth configurations file was in the root folder structure
adb will not work on device in recovery/download mode
to use adb mobile needs to be running
you can flash cwm in your mobile then upload the file and send me the link i will make a flashable zip and upload it then you can flash it
adb is running...just
Adb is running (while the phone keeps on showing boot animation-samsung logo-bootanimation-samsung logo-bootanima....) but it seems that it has permissions issues..i unrooted my phone before using adb .
i can access adb shell and list root directories but cannot enter further directories such as data\ permission denied
I donot have the file that i changed and quiet cannot remember it..
Check on your mobile and see for
data/misc/bluetoothd/
if it has files such as music.conf,main.conf etc etc..then this is the needed folder..
can you create a update.zip
like i used for rooting/ unrooting .that doesnt need CWM
that empties the directory ,because it has some backup files .bak created by root explorer
loads files from your mobile
i am currently unrooted ..do i need root?
actually adb works during splashscreen
get the original file and push it through the system, set permission and it should work
if all else fails,..... odin
download update.zip from http://dl.xda-developers.com/attach...5498d4d803e6a/4fcc0dd2/7/6/3/0/8/8/update.zip and place it in the root of your sdcard
go to recovery flash it you will get root then you can use adb
if it is not flashing first flash cwm through Odin then flash this update.zip through cwm
The file you sent is invalid. corrupt..?
what does this do..exactly.
i already have a update.zip and update-unroot.zip to root unroot my device
so
do i need root permission to use adb..because commands like
adb root gives"error not available in production devices"
&
adb shell
$ su
etc are showing permission denied.
if you have the original files on your galaxy y.. can you make update.zip with the above instruction
if adb works..i dont exactly remember the file path that i changed..so using the hints above please can you send me the file path
My aim here is to use odin or factory reset only at the last.
just root the device by flashing the root.zip in recovery and then use
adb shell
su
and it will work
No still get permission denied.... like always.
cd data
ls
open directory failed, Permission denied.
1. flash cwm recovery through odin
2. then upload the original file
3. I will create a update.zip and will upload it
4. you will need to flash it in cwm recovery
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
y2k2r2d2 said:
i will flash CWM using cwm.zip
i dont have the original file as i could not pull through adb..i hope your file may work
Finally i remembered the directory
/etc/bluetooth
the file i modified was main.conf however whole folder can be replaced from your mobile's or original one.
Thanks
Click to expand...
Click to collapse
http://db.tt/2NStXBF8
flash it in recovery but it may not work as I don't have galaxy y I have a different mobile
it didnt allow installation both through cwm and recovery mode
& now
i messed up with CWM
backup-restore feature
create backup
edited the system.tar
put the original file
calculated md5 for new system,tar
edited the nandroid.md5 with appropriate editor and filled with the new calculated md5 of system.tar
advance restoore....select system files...
md5 check pass
restore fail
now boot stuck at initial screen
pretty sure even wipe data wont work
So i Had to resort to ODIN..Thanks for your time mate...
humm
I also think Odin is the last choice
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root
phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?
phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..
pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.
Hi Guys,
Firstly, thanks so much for the info on this community. I've followed loads of the threads and almost all of what I need to know is here.
I have a KF2 @ v10.3.1. I've rooted it and applied the 2nd bootloader using a homemade lead (thanks to the thread on that!). I started in Windows but switched to Kubuntu after getting driver issues etc.. To compound the problem, the KF2 is blocked by Amazon, which didn't help as I couldn't load apps whist it was stock. (It's not stolen or otherwise illegally obtained. Amazon sent it in error, and despite me contacting them to ask how to return it, they've never replied)
Anyhow, After following THIS thread, which appeared to go OK, after rebooting I'm unable to boot into Recovery. The blue screen just stays there. I can still boot normally, but I would like to load CM10 which is loaded as per the thread, along with gapps, both in zip format. I have read many threads about being stuck on the blue screen, but these are always locked and need to be restored, but I have no problem booting normally and the KF2 is not locked. I've searched this site and googled plenty.
I don't expect an exact answer, but if someone could just point me at what to look at, I'm sure I can find the rest of the info I need on here. :good:
Oh, also. Another quick question. I see that the CM10 images are constantly being updated, if (when I get mine working) I want to use one of these, is it simply a case of copying the zip file over? Or is there more to do than that.
Many thanks in advance.
You can boot normally? Into stock, I assume.
Run the apk tool from here:
http://forum.xda-developers.com/showthread.php?t=2106463
Should get you fixed right up
The zip file will have to be flashed from recovery. So, its a matter of copying the zip file (and gapps) over. Boot into recovery. Wipe data, cache, dalvik and system. Then flash rom first, the gapps.
Also, be VERY CAREFUL and make sure you have a GOOD DOWNLOAD by checking the md5 on the file. If you wipe the system (which deletes the stack file) you will not be able to boot into recovery or anything.
I still recommend that you purchase a fastboot cable.
Edit: also, when booting into recovery you might have to hit the power button a couple of times.
--
Sent from my mind to your screen.
Cheers mindmajick. I've tried to do this but still having a few problems.
If I use the wired version, the runme.bat does not have permissions to the data/app folder. I can't seem to run it in Kubuntu as it says I can't run a binary file if I make it executable, but says I don't have permission if I remove execute. (I'm looking into this - but I'm not very good with Linux, so lots of Googling!!...lol....) Also I see that there are some issues with this version with the wireless version being favored. Unfortunately as I'm unable to log onto my Amazon account, I can't use this method.
I will continue to try, I'm almost there now, thanks for you help so far.
SportyPorty said:
Cheers mindmajick. I've tried to do this but still having a few problems.
If I use the wired version, the runme.bat does not have permissions to the data/app folder. I can't seem to run it in Kubuntu as it says I can't run a binary file if I make it executable, but says I don't have permission if I remove execute. (I'm looking into this - but I'm not very good with Linux, so lots of Googling!!...lol....) Also I see that there are some issues with this version with the wireless version being favored. Unfortunately as I'm unable to log onto my Amazon account, I can't use this method.
I will continue to try, I'm almost there now, thanks for you help so far.
Click to expand...
Click to collapse
Really confused. Pm me with your gmail account and I'll chat you through it
--
Sent from my mind to your screen.
Cheers, PM'd you.
Sorry if I've not explained it very well.
I tried to use the KF2CM10.zip via the Desktop method. I downloaded and ran the runme.bat file. This is what I get -
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C:\Users\Steve\Desktop\Kindle Fire Root\KF2CM10>ECHO off
Press any key to continue . . .
.
Removing install-recovery.sh to ensure that stock rom does not overwrite TWRP
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Usage: mount [-r] [-w] [-o options] [-t type] device directory
rm failed for systemetcinstall-recovery.sh, No such file or directory
rm failed for systemRECOVERY-AMZN-4430-OTTER2-PROD, No such file or directory
.
Pushing stack
failed to copy 'stuff\stack' to '\sdcard\': Read-only file system
sdcardstack: cannot open for read: No such file or directory
.
Inserting stack override to \system
datalocaltmpstack: cannot open for read: No such file or directory
.
Pushing freedom-boot
failed to copy 'stuff\boot.img' to '\sdcard\': Read-only file system
.
Pushing TeamWinRecoveryProject
failed to copy 'stuff\recovery.img' to '\sdcard\': Read-only file system
.
Writing freedom-boot to \boot via dd
sdcardboot.img: cannot open for read: No such file or directory
.
Writing TWRP to recovery via dd
sdcardrecovery.img: cannot open for read: No such file or directory
.
Rebooting
.
Make sure to press the power button during the secondary bootloader to reboot in
to recovery.
.
Give credit where credit is due: Script written by [email protected]
Press any key to continue . . .
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'm still unsure how to run the runme.sh from Kubuntu command line.
I tried - ./runme.sh
but error is - unable to run a binary file - or something like that.
I'm unable to use the cordless version com.powerpoint45.FMKilo-2.apk due to the fact that as the KF2 is blocked by Amazon, I'm unable to log in and download or install .apk files.
Is there is an alternative way to install .apk files without needing to log in?
Hopefully that makes a little more sense. Cheers
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
You could alternatively push the file via adb to the system Directory.
Is USB debugging enabled? Are you rooted?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
Click to expand...
Click to collapse
Yup, that did it. I had overlooked the fact that I was still able to use the browser on the KF2 and didn't really know you could install .apk's using that method anyway. So now I have carried on and installed Jellybean 4.2.2 on there and it works a treat.
Thank you ever so much Mindmajick for taking an interest in my problem, I really do appreciate yours and the rest of the developers time on here. :good:
Cheers
Sporty
fmkilo apk link shows as removed
mindmajick said:
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
You could alternatively push the file via adb to the system Directory.
Is USB debugging enabled? Are you rooted?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Went to link for fmkilo apk and, link shows link removed?
galearned said:
Went to link for fmkilo apk and, link shows link removed?
Click to expand...
Click to collapse
Correct. Tried to talk them out of removing but it was removed. Only removed so no one uses it stupidly...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
fmkilo apk removed from link
mindmajick said:
Correct. Tried to talk them out of removing but it was removed. Only removed so no one uses it stupidly...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Not a problem: Thanks
I think this is a method of pushing the flash and image files to the tablet and then installing using ADB by the way it is described.
I think I have that method copied down some place else.
I have never used this method but, sounds like it would work.
I also presume you need root to do the install via ADB.
Regards Jerry