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?
Related
Hi all,
This issue is a little bit different. I already searched for any thread that might fix my issue but no luck yet.
Issue started when trying to reformat the internal partition to 4096mb using Tenfar's CWM recovery. After that I rebooted the Atrix and got RSD err 1?? or something. I searched for solutions and tried to flash using the [GUIDE] Flash SBF to Motorola Atrix 4G from "kennethpenn. It failed half-way and stuck @ "swith BF mode failed" and giving the failed message.
Now the phone is out of battery and it's not charging at all. Not sure if RSD mode isn't allowed to charge or something.
When I connected AC Adapter to the phone and these are messages i have:
"Modem did not power up (2)"
"Starting RSD protocol support"
and with M logo in the center.
It will not do anything if i connected the Atrix the computer. Anyone knows how to fix this issue, please show me. I really really appreciate it. thanks in advance.
Daniel T
after 3 tries, I finally flashed the Atrix and got it working again. But i got odd screen issues. The Menu, Home, Back, and Search buttons are not working anymore. When I tap on something (button or letter from keyboard), I have to tap below the actual position (about 0.2 inch below) to work. Any suggestions on to how to fix it. thanks very much in advance.
danieldtien said:
after 3 tries, I finally flashed the Atrix and got it working again. But i got odd screen issues. The Menu, Home, Back, and Search buttons are not working anymore. When I tap on something (button or letter from keyboard), I have to tap below the actual position (about 0.2 inch below) to work. Any suggestions on to how to fix it. thanks very much in advance.
Click to expand...
Click to collapse
Re-flash on different computer? Im not entirely sure....
Good Luck.
Magoodigan said:
Re-flash on different computer? Im not entirely sure....
Good Luck.
Click to expand...
Click to collapse
I also tried that too but it's same issue. I think the issue is the screen itself. Got it replaced at AT&T store.
danieldtien said:
I also tried that too but it's same issue. I think the issue is the screen itself. Got it replaced at AT&T store.
Click to expand...
Click to collapse
which sbf did you try to flash?
I heard of this happening with reformatting of the internal memory, but sadly I didn't see a resolution....
bongd <------- contact him, his is the only one that seems has a solution for the screen issue
Sent from my MB860 using XDA App
help
mramirezusa said:
bongd <------- contact him, his is the only one that seems has a solution for the screen issue
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
hey man how do i contact him cause im having the same issue
Lol I think tenfar should update hes thread underline that partition option will brick your phone...
Anyway you formatted your psd partition, so no buttons and no screencalibration.
Search the thread used tenfar recovery...
You need the psd.img dumped from github and push in your phone using adb dd command.
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
Just take mmcblk0p3.img from atrix engeneering dump and push it
from a terminal (win or linux commands are the same, just remember usb debuggin on and that you are typing commands from the adb folder, place the file in the same folder)
adb push mmcblk0p3.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/mmcblk0p3.img
dd if=/data/local/tmp/mmcblk0p3.img of=/dev/block/mmcblk0p3
Reboot
I learnt it the hard way...
KeRmiT80 said:
Lol I think tenfar should update hes thread underline that partition option will brick your phone...
Anyway you formatted your psd partition, so no buttons and no screencalibration.
Search the thread used tenfar recovery...
You need the psd.img dumped from github and push in your phone using adb dd command.
http://dev.gitbrew.org/~dasmoover/android/atrix/atrix-devkit-fs.tar.gz
Just take mmcblk0p3.img from atrix engeneering dump and push it
from a terminal (win or linux commands are the same, just remember usb debuggin on and that you are typing commands from the adb folder, place the file in the same folder)
adb push mmcblk0p3.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/mmcblk0p3.img
dd if=/data/local/tmp/mmcblk0p3.img of=/dev/block/mmcblk0p3
Reboot
I learnt it the hard way...
Click to expand...
Click to collapse
Can you please re-upload the file, I'm having screen miss-calibration and from what I've read this file helps?
Nevermind I don't need'em no more.
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.
Hello everybody
at first I installed Ultimate Dynamic Navbar through this:
http://forum.xda-developers.com/showthread.php?t=2270198
after that I enabled it and it rebooted my device with no problem, but it didnt hide the navbar, so I disabled it to remove it later,
then my device rebooted and it's bricked!!!
Now:
1- Start the device
2- Sony logo
3- Black screen (the screen is on)
From recovery:
ADB shell : error: closed
ADB is working fine except the shell
Device: Sony tablet s
ROM: R5A OTA rooted
Region : US
Any help???
Thanx in advance
Make a factory reset.And use S.onyTablet.S flasher if you can.
Sent from my Sony Tablet S using xda app-developers app
Thanx for your reply
but this is what I get:
[*] Press enter to begin...
[*] Firmware data ready...
[*] Waiting for device...
and nothing happens after that
although I can use adb normally but when trying "adb shell", I get "error: closed"
mstfyounis said:
Thanx for your reply
but this is what I get:
[*] Press enter to begin...
[*] Firmware data ready...
[*] Waiting for device...
and nothing happens after that
although I can use adb normally but when trying "adb shell", I get "error: closed"
Click to expand...
Click to collapse
The reason you are getting the "error: closed" message is because System Recovery installed with Android 4.0.3r5a inhibits use of ADB Shell.
I will post the hack recovery which enables adb shell in the recovery when i find it.
Sent from my Sony Tablet S using xda app-developers app
the _hack_recovery.zip is also not working, tried it before
it has a low incremental value
Same problem but with sony tablet p
same problem. im missing region.zip, vendor.prop, build.prop and a whole lot of other files. :crying: . adb shows closed. tried to push with adb shows permission denied. can only access recovery. maybe root cant tell. any help appreciated. and also mstfyounis, go to adb and try this command. "adb pull / C:\android\backup" and then wait and check which files you have and then post theme here.
@techkrayken, here attached
mstfyounis said:
the _hack_recovery.zip is also not working, tried it before
it has a low incremental value
Click to expand...
Click to collapse
It should throw error, it gets adb working in recovery
Sent from my Sony Tablet S using xda app-developers app
smgdev said:
It should throw error, it gets adb working in recovery
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
It's not the "Error: 7 ........." , it says "Prohibit update as a result of checking version or base sku"
and the shell is still closed
thnx
mstfyounis said:
@techkrayken, here attached
Click to expand...
Click to collapse
thnx but cant download. sorry. but check in configs folder if u hav region.zip.
also check in vendors in u hav vendor.prop.
techkrayken said:
thnx but cant download. sorry. but check in configs folder if u hav region.zip.
also check in vendors in u hav vendor.prop.
Click to expand...
Click to collapse
nothing found
also, if you could get them, how would u put them back in the device??
depends
mstfyounis said:
nothing found
also, if you could get them, how would u put them back in the device??
Click to expand...
Click to collapse
Depends. i dont have root anymore so i cant.
but if you get adb (google it) and the drivers for your phone,
you might be able to push the files with root access with "adb root" (i think anyway)
but if youve got the same problem as me and when you try anything in the aio tool it shows " "su" binary not found no root " (something like that)
than unluckily i cant help you anymore.
ive ordered a pickup from sony since i realised i had warranty with it.
fingers crossed they cant find out its been rooted.
sorry for any dissapointment. if you bought this of someone then phone sony and give theme the serial no. . theyll check if you have warranty
(dont tell them anything about the aio or rooting it. say it was an ota update)
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
I have updated my old script to root ZVB as well as ZVA. This should solve issues that some people were having.
Just extract the zip file, run the .bat file and follow the instructions. Should be pretty simple. Let me know if you run into any problems.
Note: If you are having issues with the script hanging try unplugging your phone and plugging it back in. That should help.
Prerequisites:
Code:
adb debugging
LG drivers
Diag mode enabled ##diag (makes things easier but you can do without it, eg. manual reboots.)
Reserved
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
wpmetts said:
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
Click to expand...
Click to collapse
Yeah you might need to update your drivers in device manager once in download mode (searching automatically for the best driver should do the trick)
wpmetts said:
I have yet to be able to root my G3. The files get pushed over to the device but after reboot I have to manually boot it into download mode but then the device never gets recognized by the script.. I am running Windows 10 and wonder if that could have an effect on how the LG drivers work??
Click to expand...
Click to collapse
On line 27 in the bat file, change
Code:
adb reboot
to
Code:
adb reboot download
.
That worked for me.
Tried on Windows 10 and Windows 7 machines, After I manually put my phone into download mode (will not go into download mode automatically) the script detects my phone and I get "Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#"
Then the script just stops with nothing else happening, I've let it sit for 30 minutes thinking it was doing something but nothing. Any suggestions on what to do. My phone and sd card are encrypted, could this be causing the issue?
Out2kill said:
Tried on Windows 10 and Windows 7 machines, After I manually put my phone into download mode (will not go into download mode automatically) the script detects my phone and I get "Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#"
Then the script just stops with nothing else happening, I've let it sit for 30 minutes thinking it was doing something but nothing. Any suggestions on what to do. My phone and sd card are encrypted, could this be causing the issue?
Click to expand...
Click to collapse
Yes an encrypted phone/sdcard is probably the issue.
Sorry for the nooby question, but will autorec work after using this to root ZVB? I'm about to get a new device through insurance and world hate to only have root and not custom recovery.
golpeen420 said:
Sorry for the nooby question, but will autorec work after using this to root ZVB? I'm about to get a new device through insurance and world hate to only have root and not custom recovery.
Click to expand...
Click to collapse
no autorec doesn't work.. but you can use twrp manager (free on google play) or flashimg.
l33tlinuxh4x0r said:
no autorec doesn't work.. but you can use twrp manager (free on google play) or flashimg.
Click to expand...
Click to collapse
Oh wow, had no idea twrp manager supported this device now. That makes things so much easier. Cause I just ordered my new device today and it'll probably come stock with ZVB. Thanks for the info, really thought id be doomed to stock for a minute there.
Bought a G3 from someone off Craigslist last night & used this earlier today to gain root & it worked perfectly. Thanks for sharing!
So when I run the bat file, it just says waiting for device, but my device is plugged in and I know the drivers are installed, even installed them again to be sure and still nothing, and advice?
---------- Post added at 10:50 PM ---------- Previous post was at 10:34 PM ----------
nevermind, I got it
This method worked for me, thanks!!! @l33tlinuxh4x0r your the man, thanks for sharing your knowledge with the community and helping others. After trying several other root methods and having none of them work this root method actually worked! I have a LGLS990 LG G3 32GB SPRINT Shine Gold Smartphone. Goodbye Sprint / LG bloatwear and hello new xda gear!
One tip I can give is towards the end you need to unplug the USB cable, power off your phone and manually go into download mode again. The script doesn't prompt you to do that action but I figured it out when I kept getting stuck at around 90%. After I put my phone into download mode manually and reconnected the USB the root completed and SuperSU was installed. I am now running CloudyG3_2.5 and it's working flawlessly, thanks again.
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Jamesredmond82 said:
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Click to expand...
Click to collapse
I am having the same issue after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out... any help will be appreciated.
Duplicate
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Jamesredmond82 said:
i have tried this rooting method and it gets to the point after entering download mode the command script recognizes it goes to the next step then the command prompt just closes out.....what the heck is going on there? its done that repeatedly every time it hits that step
Click to expand...
Click to collapse
You can use this method, i just rooted my LG G3 using mathod B on the link below.
http://forum.xda-developers.com/spri...stock-t3211878
hkhan1 said:
Duplicate
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
You can use this method, i just rooted my LG G3 using mathod B on the link below.
http://forum.xda-developers.com/spri...stock-t3211878
Click to expand...
Click to collapse
your link didnt work
http://forum.xda-developers.com/spr...990-zvb-root-method-zvb-rooted-stock-t3211878
On this forum go to page number 5 for instructions.
Try this link, this should work.
Rooted a brand new LG G3 sold for Boost Mobile with this method. Lollipop v 5.0.1
twelfth said:
Rooted a brand new LG G3 sold for Boost Mobile with this method. Lollipop v 5.0.1
Click to expand...
Click to collapse
how exactly did you go about doing this?