Related
I have changed the build.prop of my rooted TF201 to play the gameloft games.
After changing the TF201 got stuck in a bootloop. I tried the hard reset but it is still not starting.
I read that it is possible to push the orginal build.prop to the TF201 via APX-Mode but i dont now how to do it.
My computer recognizes the TF201 as a Asus Transformer Prime APX mode or in MTP when i start it regular. Unfortunatly i can not get any access to the Data of my TF201.
Is Asus able to see the root and that i changed the build.prop if i sent it to RMA?
Would be so happy if anybody could help me.
Thank you.
(And i know it was stupid to change the build.prop but didnt expected to brick it http://media.xda-developers.com/images/icons/icon9.gif)
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
stf996 said:
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
clmz88 said:
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
Click to expand...
Click to collapse
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Turge said:
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Click to expand...
Click to collapse
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
clmz88 said:
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
Click to expand...
Click to collapse
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
EDIT: Here you go.
http://forum.xda-developers.com/showthread.php?t=1480428&highlight=bricked
Now don't go doing such stupid things again.
Turge said:
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
Click to expand...
Click to collapse
Ok. Thanks though.
I would be happy about some other ideas
Doktaphex said:
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
Click to expand...
Click to collapse
I already got that thread and asked for his solution.
Im unfortunatly not able to sent him a private message because i am a new member.
clmz88 said:
Ok. Thanks though.
I would be happy about some other ideas
Click to expand...
Click to collapse
EDIT: I'll see what I can do for you, give me some time.
Doktaphex said:
EDIT: I'll see what I can do for you, give me some time.
Click to expand...
Click to collapse
Thank you!!!
clmz88 said:
Thank you!!!
Click to expand...
Click to collapse
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Doktaphex said:
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Click to expand...
Click to collapse
I actually dont know what version is on my Prime. I did the official update two weeks ago. So it is probably V9.4.2.11.
I have a app called "adb made easy" on my pc and this on can not find my device.
Does your device constantly reboot or does it stay at the boot animation?
Doktaphex said:
Does your device constantly reboot or does it stay at the boot animation?
Click to expand...
Click to collapse
It stays constantly in the boot animation.
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
EDIT: unplug and plug back in a couple of times, does windows make it's usual connection noises?
Doktaphex said:
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
Click to expand...
Click to collapse
adb made easy and cmd dont show any adb devices.
the devices manager shows
mobile devices: Asus Android MTB Device (could not be started)
windows is always making the pluggingsound
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Doktaphex said:
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Click to expand...
Click to collapse
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Turge said:
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
I think it is setup for MTP but im not sure about it...
I didnt find a way yet to get access to the prime via usb.
Already tried different drivers, adb, apx but nothing is working.
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
I have this exact same problem right now.
Would love to get a solution for this.
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
COLDrum said:
I have this exact same problem right now.
Would love to get a solution for this.
Click to expand...
Click to collapse
Please post here if you find a working solution for this.
demkantor said:
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Im on hold when it gets to downgrading so far. Im not familiar with Android Commander, but Droid Explorer requires adb to be working. And that is kinda my whole problem. I cant accept my PC as a secure adb-client since the digitizer is broken (touch input wont work). I hope there is a way to override this through recovery or some other way.
Breakdown:
When connecting device to computer (adb), I have to (on my device) accept my computer as secure. This is a problem since digitizer is broken.
Sent from my Nexus 7 using xda app-developers app
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
demkantor said:
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Indeed this seems to be a fix. Thanks!
Do you know if there is a way to get rid of the authorization through adb. Are there any files who could be manipulated? Would be great if I could use some sort of screencast-app eg. Droid Explorer.
Sent from my Nexus 7 using xda app-developers app
I'm sure being you can use adb shell in recovery that there is a way, can't say off hand but a bit of digging will probably get you there, it couldn't be all that hard I wouldn't think
Sent from my Nexus 4 using xda premium
Streaker said:
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
I do have more than one instance of ADB.exe installed yes, but does that matter to my problem? My Nexus isnt even showing up in fileexplorer in windows. So I cant access my files. Or am I wrong here?
Sent from my Nexus 7 using xda app-developers app
maxrfon said:
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
Click to expand...
Click to collapse
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
....
maxrfon said:
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
Click to expand...
Click to collapse
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have had the same problem with my S4.
After updating ADB i did "adb devices" and got my S4 as offline, and i noticed the popup on my phone, accepted and my samsung is now working fine with ADB.
FYI before the above mention operation i have tried everything, even making sure i run the correct adb.exe but there was no popup.
First of all kill the adb server via task manager then when you start the adb command-line type In ADB root this may solve your problem :thumbup:
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Somehow I managed to delete the stock OS and CM on my LG G2 (Verizon) and now my device is stuck on the loading LG screen. I am also getting the unauthorized device when checking ADB devices. I've got TWRP running as the bootloader, but just need to be able to push over the CM file to boot and I'll be good to go. Any suggestions on how to force the file over to the phone?
Boot into your twrp recovery and use adb sideload to flash a ROM from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
VreebieZ said:
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
Click to expand...
Click to collapse
I'm having the same problem as the OP... This is impossible. *the screen and digitizer are broken*
The question is "How can I bypass the New authorization, since I can't click anything on my phone". I can't check "USB Debugging" - I need the phone screen and digitizer to do that. come on people, read the post.
Has anyone figured this out? I'm having a similiar problem except my screen isn't broken. I forgot to make a backup and my OS got erased and I'm getting the unauthorized notification in ADB. You have to be able to get into the OS to accept the authorization so I'm at a catch 22. I have a Nexus 7 so I can't swap out a different SD card.
Hello!,
After trying changing the display resolution with lcd density or similar apps, my XTS doesn't want to boot anymore. After sony's logo, i get black screen. Many times, i got this error while trying changing values and parameters, but with full wipe, it always worked as new... not now.
I also rooted my dev. installing also the new updates, using AIO...
I'm on stock kernel / recovery
ANDROID SYSTEM RECOVERY 3a
rev.44, BL:0X00000009, EC: 0.21, master
my dev is SGPT121US/S without 3g 4.1.1 R1, i did not installed the R2 last update.. I've downloaded many firmware, but the installation aborted everytime when trying to verificate the update, so:
install /sdcard
Findind update package...
Desklunvr update package...
Verifying update package...
Installation aborted.
do you have any ideas??? my idea of tablet is quite different from a wedge for dancing tables...so i must (if possible) unbrick my dev!
The same thing happened to me...
The screen goes black after the SONY logo at boot.
I did an android reset but did not fix the problem.
I realized that the touch screen is still working because although the screen is black,
when I have the volume at max and touch different areas I hear the click sound telling me that
the touch screen is responding. I found out that I can unlock the screen and etc.
BUT the screen is black so there is nothing I can do...
nickfee said:
Hello!,
After trying changing the display resolution with lcd density or similar apps, my XTS doesn't want to boot anymore. After sony's logo, i get black screen. Many times, i got this error while trying changing values and parameters, but with full wipe, it always worked as new... not now.
I also rooted my dev. installing also the new updates, using AIO...
I'm on stock kernel / recovery
ANDROID SYSTEM RECOVERY 3a
rev.44, BL:0X00000009, EC: 0.21, master
my dev is SGPT121US/S without 3g 4.1.1 R1, i did not installed the R2 last update.. I've downloaded many firmware, but the installation aborted everytime when trying to verificate the update, so:
install /sdcard
Findind update package...
Desklunvr update package...
Verifying update package...
Installation aborted.
do you have any ideas??? my idea of tablet is quite different from a wedge for dancing tables...so i must (if possible) unbrick my dev!
Click to expand...
Click to collapse
Try any update and the use adb pull /tmp/recovery.log and post the recovery.log here. See my stickied FAQ for mor info
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
naka307 said:
The same thing happened to me...
The screen goes black after the SONY logo at boot.
I did an android reset but did not fix the problem.
I realized that the touch screen is still working because although the screen is black,
when I have the volume at max and touch different areas I hear the click sound telling me that
the touch screen is responding. I found out that I can unlock the screen and etc.
BUT the screen is black so there is nothing I can do...
Click to expand...
Click to collapse
Try as above
@stifilz
This is what I got.
naka307 said:
@stifilz
This is what I got.
Click to expand...
Click to collapse
Ok so firstly we fail due to trying to install what is currently install. You should be able to install when/if there is a new release...
After failing it switches to the other partition which fails due to messed up vendor files. Third and Forth are the same as it does not switch back.
All in all you will need to wait for a new update and that should install on the first try. Other than that off to Sony it is
Stifilz
You can try using 'setprop' to change the value within that DPI property since you have ADB, now we just need to know the original DPI for the XTS so you can fix this.
Sent from my Nexus 4 using Tapatalk
andyabc said:
You can try using 'setprop' to change the value within that DPI property since you have ADB, now we just need to know the original DPI for the XTS so you can fix this.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
the original resolution is 1280 x 800, but i don't know if adb is working in recovery mode. I've to test it.
nickfee said:
the original resolution is 1280 x 800, but i don't know if adb is working in recovery mode. I've to test it.
Click to expand...
Click to collapse
Found it, it is 161 PPI.
EDIT: Can you ADB Pull the build.prop and give it to me?
ADB should work on the black screen since the system is still running.
Sent from my Nexus 4 using Tapatalk
andyabc said:
Found it, it is 161 PPI.
EDIT: Can you ADB Pull the build.prop and give it to me?
ADB should work on the black screen since the system is still running.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I hope so...now i'm trying to connect via adb/recovery my XTS, but after ADB DEVICES command, it says that there's not dev connected.
I'm on W8, and i've read that there were some troubles using adb and w8, so now i don't know where is the problem, maybe on my pc, or XTS.
I'm going to test it on W7.
i'll let you know ASAP.
thanks in advance.
nickfee said:
I hope so...now i'm trying to connect via adb/recovery my XTS, but after ADB DEVICES command, it says that there's not dev connected.
I'm on W8, and i've read that there were some troubles using adb and w8, so now i don't know where is the problem, maybe on my pc, or XTS.
I'm going to test it on W7.
i'll let you know ASAP.
thanks in advance.
Click to expand...
Click to collapse
The Windows 8 problem is just to do with installing the driver, not detection, I have Windows 8 Pro and it works fine.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 01:06 PM ---------- Previous post was at 12:57 PM ----------
Ok so to fix it you must do the following in the CMD:
adb shell
su
adb shell mount -o rw,remount /system
setprop ro.sf.lcd_density=160
chmod 644 /system/build.prop
reboot
Sent from my Nexus 4 using Tapatalk
andyabc said:
The Windows 8 problem is just to do with installing the driver, not detection, I have Windows 8 Pro and it works fine.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 01:06 PM ---------- Previous post was at 12:57 PM ----------
Ok so to fix it you must do the following in the CMD:
adb shell
su
adb shell mount -o rw,remount /system
setprop ro.sf.lcd_density=160
chmod 644 /system/build.prop
reboot
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Nada, nothing to do... adb can't recognize my XTS. I'm sure that adb drivers work correctly. this is what i've done:
1 - check the drivers and adb shell
2 - boot my dev. in recovery mode
3 - connect usb cable from tablet to my pc
4 - run cmd and adb prompting adb devices
5 - result : List of devices attached (EMPTY)
so i can't edit any kind of files and posting any logs.
nickfee said:
Nada, nothing to do... adb can't recognize my XTS. I'm sure that adb drivers work correctly. this is what i've done:
1 - check the drivers and adb shell
2 - boot my dev. in recovery mode
3 - connect usb cable from tablet to my pc
4 - run cmd and adb prompting adb devices
5 - result : List of devices attached (EMPTY)
so i can't edit any kind of files and posting any logs.
Click to expand...
Click to collapse
Recovery mode does not help, you only need to be on the system where the black screen is.
Recovery mode needs a key to unlock so you can use the actual ADB interface fully.
Try an other USB port if you can.
Sent from my Nexus 4 using Tapatalk
Adb shell works with my XperiaZ, so i know that the usb port that i'm using is working. Now i'll reboot my XTS, trying to connect adb whit the black screen on the display, but i think this won't work as well. I thought that adb worked also in recovery mode.
nickfee said:
Adb shell works with my XperiaZ, so i know that the usb port that i'm using is working. Now i'll reboot my XTS, trying to connect adb whit the black screen on the display, but i think this won't work as well. I thought that adb worked also in recovery mode.
Click to expand...
Click to collapse
It does work in recovery but you need to unlock the recovery first.
It should work on the black screen since the OS is running.
Sent from my Nexus 4 using Tapatalk
andyabc said:
It does work in recovery but you need to unlock the recovery first.
It should work on the black screen since the OS is running.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ok so i think that it is not a display fault, but a boot fault. I'd like to know why i can't install any original zip through recovery. i was on 4.1.1 r1 rooted with condi's script, (before factory reset), and my dev is US region.
i've downloaded all the zip from sony's site, and get the same error while rec. validates the package.DAMN
install /sdcard
Findind update package...
Desklunvr update package...
Verifying update package...
Installation aborted.
Under black screen i can't ear any sound, for example while touching the screen or increase/decrease volume with volume bottom, so i'm quite sure that the dev is not booted correctly.
nickfee said:
ok so i think that it is not a display fault, but a boot fault. I'd like to know why i can't install any original zip through recovery. i was on 4.1.1 r1 rooted with condi's script, (before factory reset), and my dev is US region.
i've downloaded all the zip from sony's site, and get the same error while rec. validates the package.DAMN
install /sdcard
Findind update package...
Desklunvr update package...
Verifying update package...
Installation aborted.
Under black screen i can't ear any sound, for example while touching the screen or increase/descrease volume with volume bottom, so i'm quite sure that the dev is not booted correctly.
Click to expand...
Click to collapse
It is just the build.prop, you see the System UI and other elements cannot adjust to that DPI what so ever so it messes up and shows up all black, the build.prop is like a list full of properties which is wiped and loaded to the system at every boot and applications/services such as System UI and the settings reads the whole thing during boot time so all you should need to do is just do all those commands.
Please follow it on runtime to see if it works.
Sent from my Nexus 4 using Tapatalk
andyabc said:
Please follow it on runtime to see if it works.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
can you tell me how?
can you also explain me why with factory reset, the build.prop is not gone back to default values?
nickfee said:
can you tell me how?
can you also explain me why with factory reset, the build.prop is not gone back to default values?
Click to expand...
Click to collapse
Factory reset does not change anything within the system partition.
andyabc said:
Factory reset does not change anything within the system partition.
Click to expand...
Click to collapse
i think today i'll send my dev to sony's support center...hoping there'll be a solution
i've finished all the ideas...
thanks for your help.
nickfee said:
i think today i'll send my dev to sony's support center...hoping there'll be a solution
i've finished all the ideas...
thanks for your help.
Click to expand...
Click to collapse
So ADB is not working for you on the black screen?
I'm not sure if this is considered a boot loop but when turned on, after the logo it turns into a blank screen.
Anyway, I was stupid enough to install 3D chainfire when it's not compatible (I neglected the description since it worked on my previous galaxy ace) ... Soooo can anyone help me on this?
I've tried going to recovery mode to:
- wipe data/factory reset
- wipe cache partition (but shows error)
Not sure what else can I do anymore. I'm noob at these. Since Ace 3 is fairly new, it's quite hard to find a solution with google haha.. Also, I have zero knowledge about flashing ROM or of the sort..
Extra info in case it helps:
- My phone is Samsung Galaxy Ace 3 GT - S7275R
- Rooted with a Chinese universal rooting program
- When entering recovery mode, it shows "no command" for a few seconds before entering the menu.
Thanks in advance for helping!
try
try 1 goto recovery and wipe cache/data
try 2 download adb shell install kies in pc
goto recovery mode and connect phone to pc
type in adb shell remove your.apk in aystem app
gohel.vishal said:
try 1 goto recovery and wipe cache/data
try 2 download adb shell install kies in pc
goto recovery mode and connect phone to pc
type in adb shell remove your.apk in aystem app
Click to expand...
Click to collapse
For try 1, it's not working
For try 2, I don't really understand the way to do it. I'd downloaded adb, installed kies. Other than that, I'm not sure what to do.
Sorry, really a noob here.
try
xahjun said:
For try 1, it's not working
For try 2, I don't really understand the way to do it. I'd downloaded adb, installed kies. Other than that, I'm not sure what to do.
Sorry, really a noob here.
Click to expand...
Click to collapse
.
goto recovery & connect to pc
open folder where is adb
press shift+right click
open command prompt here
type adb shell
in adb shell
type su
goto system/app
ls
look at your chainfire app and delete type rm xxx.apk
gohel.vishal said:
.
goto recovery & connect to pc
open folder where is adb
press shift+right click
open command prompt here
type adb shell
in adb shell
type su
goto system/app
ls
look at your chainfire app and delete type rm xxx.apk
Click to expand...
Click to collapse
This is embarrassing, but I don't really know if I'm even doing it right or wrong. After all, I don't fully understand how adb work(even after reading about it).
Anyway, this is what I get after typing adb shell.
h t t p ://s18 .postimg .org/ov55a21pz/Untitled .png (sorry can't post image cause I'm a new user)
Though I think I'm actually doing it wrong.
never
xahjun said:
This is embarrassing, but I don't really know if I'm even doing it right or wrong. After all, I don't fully understand how adb work(even after reading about it).
Anyway, this is what I get after typing adb shell.
h t t p ://s18 .postimg .org/ov55a21pz/Untitled .png (sorry can't post image cause I'm a new user)
Though I think I'm actually doing it wrong.
Click to expand...
Click to collapse
i have never seen error like that i cant help you
gohel.vishal said:
i have never seen error like that i cant help you
Click to expand...
Click to collapse
Ahh I see... Thanks anyway for those quick reply :good: Appreciate it.
Anyone else can give me a helping hand?
so
xahjun said:
Ahh I see... Thanks anyway for those quick reply :good: Appreciate it.
Anyone else can give me a helping hand?
Click to expand...
Click to collapse
goto samsung service center ...
or try to flash stock rom google it
gohel.vishal said:
goto samsung service center ...
or try to flash stock rom google it
Click to expand...
Click to collapse
Can't find Ace 3's stock rom...
go to here and choose your country and download
xahjun said:
Can't find Ace 3's stock rom...
Click to expand...
Click to collapse
http://samsung-updates.com/device/?id=GT-S7275R
Thaaaaaaaanks!
gohel.vishal said:
http://samsung-updates.com/device/?id=GT-S7275R
Click to expand...
Click to collapse
Thanks a lot!! It worked! I took long to try because the file size is huge and my internet connection is unstable. Regardless, thanks for the help! Really appreciate it! :good:
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Edit:
No luck yet, but I remember a way I did before.It's not quite the same situation but...
I left the kindle on for a long time, and pressed the power button beyond the point from where it showed out of battery screen. It had like no batterypower at ALL. Yhen i plugged back up to PC and...
I'm trying it out now, if anyone is in the same position as me do the same!
Remember,charge only about 1-2%,if it doesn't work!
Thank you guys a LOT for support! I am in process of getting adb and stuff to work on linux...
let's see how it goes...
ferrouskid said:
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Click to expand...
Click to collapse
Does adb work ?
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No, unfortunately!
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No,
well
ferrouskid said:
No,
Click to expand...
Click to collapse
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
jimyv said:
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
Click to expand...
Click to collapse
Man any ideas?
Thanks
Hashcode and I have talked about it. There IS a working fastboot, but you can't get to it with a fastboot cable, and it's very buggy and not too useful. So it sounds like you are SOL. Sorry. :/
Sent from my Amazon Tate using Tapatalk
?
ferrouskid said:
Man any ideas?
Thanks
Click to expand...
Click to collapse
Fastboot system files?
jimyv said:
Fastboot system files?
Click to expand...
Click to collapse
Wait I know android cowboy had the same problem some time ago. I'll ask him.
ferrouskid said:
Wait I know android cowboy had the same problem some time ago. I'll ask him.
Click to expand...
Click to collapse
If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.
http://forum.xda-developers.com/showthread.php?t=2588608 QUOTE=ferrouskid;53393803]If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.[/QUOTE]
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
HI, you did the factory reset, too?
ARUSTORI said:
HI, you did the factory reset, too?
Click to expand...
Click to collapse
I didn't, though you should try my solution (I'd got a black screen after the grey logo).
I'm sorry but I won't try the factory reset to see if it works
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Ause said:
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Click to expand...
Click to collapse
I'll be over the moon if this works, adb is installed, now waiting for flat kindle to charge...
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Please expand on that. Thank you so much.
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
ferrouskid said:
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
Click to expand...
Click to collapse
Connect your device to your computer.
By typing "adb devices", you should get this output :
Code:
List of devices attached
???????????? no permissions
Then type "lsusb" and note the ID of the Google Device (Should be 18d1:0001, but I'm not sure you will get the same).
Edit the file "/etc/udev/rules.d/51-android.rules" and add the following lines (If the file doesn't exists create it). Replace 18d1 and 0001 with the values you get in lsusb :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_fastboot"
Run "sudo chmod a+r /etc/udev/rules.d/51-android.rules".
Restart your computer and you should be access your device using "adb shell".
Follow this post to restore your device : http://forum.xda-developers.com/showpost.php?p=53388919&postcount=23
Crap. I dont have access to a linux OS..ill have to call amazon i think.
Sent from my LG-D800 using XDA Premium 4 mobile app