Related
i installed the lag fix on my phone today and after rebooting the screen is black it makes the boot up sounds but nothing follows. the bottom buttons work and light up, it connects via adb but i cannot access SU mode.
i also did the adb shell to allow non market apps to be installed and the funny thing is i cannot access clockworkmod recovery.
Can someone help me boot up into clockworkmod recovery when i boot up vol+and vol- it takes me to the orginal recovery.
Which rom are/were you running? I897UCJF6/JH2, or an I9000 variant?
Which lagfix did you use?
soklean said:
Can someone help me boot up into clockworkmod recovery when i boot up vol+and vol- it takes me to the orginal recovery.
Click to expand...
Click to collapse
try selecting reload packages in the stock recovery, for me that takes me into clockwork
I'd also be interested in a potential fix for this issue. I have a vibrant, however my co-worker has the captivate, and hit this same issue. Can't get SU via ADB. Can boot into recovery, and download mode, but would prefer to get back into the OS without reflashing if possible. He used the .bat file provided for RyanZA's lag fix. I'm not sure which version. He's also running the original stock Captivate firmware.
Do your SD cards mount when plugged into a computer?
Can you access /sdcard via adb shell?
max_warheads said:
Do your SD cards mount when plugged into a computer?
Can you access /sdcard via adb shell?
Click to expand...
Click to collapse
Yep!
Both /sdcard and /sdcard/sd mount and are accessible via adb shell. I'm assuming that I can't run su as it depends on the "allow" button being clicked through superuser.apk. I of course can't click that without a working screen
I'm wondering if a version of su that doesn't use superuser.apk would allow me to get in there and undo the lagfix.
Well if you knew the exact lagfix version and type you used, you might be able to get that packaged into an update.zip that would remove the fix for you... albeit, if you're not 100% certain, it could wax all your application data.
If it was RyanZA/Tatuyama/Zilch/Myself tweaking the lag fix, it's very dependent on *which* version it was. But, I might be able to whip a removal tool.
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
avatarjo3 said:
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
Click to expand...
Click to collapse
Its hold volume down and then hold power...
tweaked said:
Its hold volume down and then hold power...
Click to expand...
Click to collapse
Right. That's to get in to Recovery mode. I can get into recovery mode, but I can't get into APX Mode, which is what I need to do to apply the NVflash. I can't apply the flash via CWM because it's not letting me mount my SDcard.
Thanks for the reply!
avatarjo3 said:
I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Click to expand...
Click to collapse
Go get a micro sd card and try again. Buy one, get it out of your phone if you have it or get one from your sister.
Not 100% sure but my GUESS would be that since you have no OS on your tablet.
Which mean it can't communicate with your dock for you to use the SD card on the dock. If you can still get into CWM recovery you are NOT "bricked"
baseballfanz said:
Go get a micro sd card and try again. Buy one, get it out of your phone if you have it or get one from your sister.
Not 100% sure but my GUESS would be that since you have no OS on your tablet.
Which mean it can't communicate with your dock for you to use the SD card on the dock. If you can still get into CWM recovery you are NOT "bricked"
Click to expand...
Click to collapse
Whew... what a relief. Alrite, I'll get a microSD card. How can I format it? There's a slot on my laptop with an SDcard slot, but not one for microSD. I've tried using a microSD straight out of the package, without formatting it. Even though I didn't put anything on it, it wouldn't mount via the CWM mount feature.
Thanks for the reply!
avatarjo3 said:
Whew... what a relief. Alrite, I'll get a microSD card. How can I format it? There's a slot on my laptop with an SDcard slot, but not one for microSD. I've tried using a microSD straight out of the package, without formatting it. Even though I didn't put anything on it, it wouldn't mount via the CWM mount feature.
Thanks for the reply!
Click to expand...
Click to collapse
They have microSD USB adapter. Mine came with one when I bought it.
Format to FAT32. Use a program like sdformatter for best results.
baseballfanz said:
They have microSD USB adapter.
Click to expand...
Click to collapse
Alrite. I'll give it a shot.
When you say OS, is that the same thing as a ROM? I want to flash this ROM (http://forum.xda-developers.com/showthread.php?t=1514658), so would I transfer that rom to the microSD and flash it via CWM?
Thanks again!
Yes put that ROM filter on the micro sd card, boot into cwm recovery and install zip from sd card
baseballfanz said:
Yes put that ROM filter on the micro sd card, boot into cwm recovery and install zip from sd card
Click to expand...
Click to collapse
So I have the microSD card. It's 2gigs. I followed this guide (http://www.xda-developers.com/android/how-to-root-the-asus-transformer-xda-tv/) while my device was version 8.6.5.21. All I was trying to do was to get CWM on there. I think the best approach now would be to flash back to 8.6.5.13, then try and install CWM from there. I looked at this guide (http://forum.xda-developers.com/showthread.php?t=1281161), but it said it doesn't come with CWM, but comes with CWM support... What does that mean?
Any suggestions?
Thanks!
Don't go to firmware before 8.6.5.19, it is pointless to go any further back. Flash that firmware, then use razorclaw to root and gnufabios recoveryinstaller to get cwm, see the guide in my signature.
luna_c666 said:
Don't go to firmware before 8.6.5.19, it is pointless to go any further back. Flash that firmware, then use razorclaw to root and gnufabios recoveryinstaller to get cwm, see the guide in my signature.
Click to expand...
Click to collapse
Thanks the advice. I won't root from 8.6.5.13, but I don't think I can take the razorclaw approach, because all the links for the 8.6.5.19 roms are dead. I'm looking at Nachoroot (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/) and will report back when finished.
Quick question. Are the commands provided on the website meant to be ran in cmd?
Thanks!
avatarjo3 said:
Quick question. Are the commands provided on the website meant to be ran in cmd?
Thanks!
Click to expand...
Click to collapse
Yes in CMD window.
OK I'm a little lost. Currently my firmware is 8.6.5.21 and I'm not sure how to follow the Nachoroot guide (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/)...
I have ADB setup. I downloaded the 2 files. Do I need to have the files in a certain location? What do I need to do???
avatarjo3 said:
OK I'm a little lost. Currently my firmware is 8.6.5.21 and I'm not sure how to follow the Nachoroot guide (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/)...
I have ADB setup. I downloaded the 2 files. Do I need to have the files in a certain location? What do I need to do???
Click to expand...
Click to collapse
The two files need to go into the SDK (platform-tools) folder.
baseballfanz said:
The two files need to go into the SDK (platform-tools) folder.
Click to expand...
Click to collapse
Great, so I did that and I shift+rightclick in the folder to open up cmd and I type in the commands, but after I get do the second reboot and type in "adb shell id" I never get id 0... I type everything out carefully. Each time the tablet reboots my computer says it's installing the software but fails everytime. Could this have something to do with it? Does this only work with Transformer Prime?
Also, I'm running windows 7 and installed the SDK package in Program Files x86. I put the 2 files in the folder platform-tools and shift+rightclick and ran the commands. What am I doing wrong?
I really appreciate the replies. They're very helpful!
Thank you!
Please anyone? I could really use your help
Just forget everything everyone says. Follow my idiot-proof procedure for dummies.
Part 0
(1) Go to the following website.
ASUS - Eee- ASUS Eee Pad Transformer TF101
(2) Choose android.
(3) Download the latest WW, US, TW, etc. version you need.
(4) Unzip that file. Inside, you will probably find a folder called update. Inside that folder, you will find another zip file. Keep this zip file.
(5) Place this zip file in the root of your micro sd card.
(6) Insert micro sdcard into your TF.
Part I
(1) Download the following zip file from my cloud account.
honeycomb_root_cwm.zip - File Shared from Box - Free Online File Storage
(2) Unzip it onto your desktop.
You should find 3 things after you've unzipped it.
a-folder name "apps"
b-folder name "root honeycomb"
c-file name "root-honeycomb-instructions.txt"
(3) Place the folder "root honeycomb" in your c: directory. where is this? Click on Computer and go into Local Disk (C: ). Place the folder in there.
Part II
(1) Connect your TF to your computer.
(2) On your TF, press on the sync icon in the lower right hand corner of the taskbar. It will fail to sync with your computer. Try again. Keep trying againi until your computer and TF recognize each other.
(3) On your PC, press on the start menu. In the search bar, type in "cmd".
(4) Type in "cd\" and press enter.
(5) In the command prompt, type "cd root-honeycomb".
Part III
(1) Open up the text file "root-honeycomb-instructions.txt".
(2) Copy the first line in the text file.
(3) Right click the command prompt window and choose paste. Press enter.
(4) Copy and paste the 2nd line. Do this for the first 4 lines.
(5) After the 4th line, your TF should restart. Wait for it to completely restart. Unlock your TF.
(6) Copy and paste the 6th and subsequent lines. When you see <wait for boot>, it means you wait for your TF to reboot. Do not copy and paste such lines.
Part IV
(1) Congrats. You are now rooted.
(2) Transfer the folder "apps" into your TF.
(3) Install those 2 apps found in the folder.
(4) Open up the app "superuser". Then go back to your homescreen.
(5) Open up the app recovery installer. Press that big-ass button in the middle of the screen. Allow.
(6) Wait for your TF to restart completely.
(7) Turn off your TF.
(8) Turn on your TF by pressing and holding the power and volume down buttons together. As soon as you see white texts on the upper left hand corner of your TF, immediately release the power and volume down buttons and press the volume up button.
Part V (Final)
(1) You are now in what we call clockworkmod recovery.
(2) Using volume up and down buttons, navigate to "Install from zip file". To enter, press the power button.
(3) Choose "Choose zip file from sd card".
(4) Navigate to the zip file you got from the asus website and choose it.
(5) Watch your TF install ICS.
(6) Once ICS finishes installing, go back and reboot system.
At this point, your system will reboot into ICS. You now have a non-rooted ICS stock rom and stock recovery.
avatarjo3 said:
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
Click to expand...
Click to collapse
If its till bricked press down power and vol down buttons together that should help and your tablet will BOOT back into an existing ROM (Im telling you because i was trying to ROOT with ICS and more than once i was stuck in same situation).
If you want to root then follow my step, it should help you to ROOT as i was able get ROOT and install Revolver ICS and i was on stock ICS (US version). Click on the link below and understand all the steps.
http://forum.xda-developers.com/showthread.php?t=1527926
Sorry for the late reply guys. I lost my microSD card so I haven't tested your method yet.
Thank you for replying with length posts guys. This is most helpful! I will return with positive results!
avatarjo3 said:
Great, so I did that and I shift+rightclick in the folder to open up cmd and I type in the commands, but after I get do the second reboot and type in "adb shell id" I never get id 0... I type everything out carefully. Each time the tablet reboots my computer says it's installing the software but fails everytime. Could this have something to do with it? Does this only work with Transformer Prime?
Click to expand...
Click to collapse
You are typing in --stage1 --stage2 also correct?
My daughter's Nexus S touchscreen has died. It died slowly in that on the first few occasions she couild pop the battery and it would come back. Now it won't come back at all and is stuck on the pattern lock screen.
Before we send the phone for repair under warranty she is keen to get the photos off the phone since a repair might reset the phone. I was thinking we could mount the phone as a USB device but it doesn't show up perhaps because it won't until the pattern lock is entered else anybody could get data off your phone bypassing security.
Any other things we could try before giving up and hoping the repair doesn't delete all the data?
Thanks
Boot into recovery, make a nand then extract data through adb?
adb pull /sdcard/path-to-whatever
Can you explain the path to whatever? Like if I want it in folder "A" on the desktop.
Sent from my Galaxy Nexus using Tapatalk 2
Check this thread
http://forum.xda-developers.com/showthread.php?t=1573744
treUse said:
adb pull /sdcard/path-to-whatever
Click to expand...
Click to collapse
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
lchiu7 said:
Out of interest I tried this on my GN. adb recognises the phone and adb devices shows the serial number. But adb pull /sdcard says invalid remote file. No idea what that means since using ES File Explorer sdcard is a valid directory on the phone (and I suppose it would also be on the Nexus S)
Click to expand...
Click to collapse
ADB "thought" you meant to copy a file.
To copy the entire sdcard directory you should do something like this:
Code:
adb pull /sdcard/ sdcard/backup/on/pc/
The command parameters are "adb pull <source> <destination>"
Just make sure source ends with a /
Maybe a Windows based software?? Droid Explorer, very useful.. http://de.codeplex.com/ :good:
Well I finally got the phone to play with. The screen indeed dead. I installed the Google USB drivers from the SDK and also the Samsung drivers.
When I boot the phone into the recovery menu I can run fastboot devices and see the following
????0AC4B09900?? fastboot (of course the ? are not there but I wanted to anonmyuse the serial)
So far so good.
In device manager under Android Phone it show Samsung Android ADB Interface
But if I try adb devices I get nothing.
Forgot to mention my daughter said USB Debugging was turned off but I am not sure that makes any difference and anyway, we can't boot Android to turn it on
So I select Recovery and see the Android with the exclamation mark. Windows beeps to indicate that some sort of devices has been installed,
But in Device Manager no phone shows which explains why adb can't fidn the phone but not why.
I can bring up the recovery menu but still no adb
Any suggestions?
Thanks
Boot into Fastboot and flash CWM Recovery.
RL77LUC said:
Boot into Fastboot and flash CWM Recovery.
Click to expand...
Click to collapse
But it looks like I have to unlock the bootloader to do that and the phone is still under warranty so that would invalidate the warranty wouldn't it? She would like to get the data off the phone. A screen fix shouldn't zap the memory but you never know.
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
cukdus said:
what this device installed CWM?? if installed cwm just bot it to cwm an goto mass storage
Click to expand...
Click to collapse
The phone is stock
lchiu7 said:
The phone is stock
Click to expand...
Click to collapse
If you unlock the bootloader to flash CWM your memory will also be wiped, so you will loose all the photos you want to save, so don't do that.
Also if you have the USB debugging off, the ADB commands won't work. I'm afraid you're SOL, since you have the bootloader locked you can't flash a kernel with USB host, that would allow you to use a mouse to navigate in the phone and since you don't have USB debug you can't pull files from the "SDcard"... Better take it to the store and try to ask them if they can save the photos before they do anything to the phone, but i guess if it's a digitalizer problem, they won't mess with the NAND.
Check out http://www.moborobo.com/ and see if it works for you.
If you have root you have extended functionality, like control the device from the PC. But if i recall correctly, even without root you should be able to get your files.
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
tiredofit said:
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
Click to expand...
Click to collapse
buddy as you are not able to boot in download mode or recovery i think it is bricked as you say black screen is observed
try triangle away to unbrick it
or customer care center always welcome you
tiredofit said:
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
Click to expand...
Click to collapse
Try it it recognised with pc odin. ...
If yes flash stock rom your issues will be solved
Dont Forget To HiT Thanks Button
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.
V0latyle said:
Due to the security implications of remotely enabling USB Debugging, the only way to enable it is through Developer Options. You can try rebooting to recovery and clearing cache although I am doubtful as to how much that might help you. If your device took a swim, you're going to be looking at repair, which will most likely result in wiping your data.
Click to expand...
Click to collapse
Do you know if changing the screen could solve the problem? Or do you think there's a way to copy data 1:1 on another device (such as a used mi 9t I could buy)?
Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?
Droidriven said:
How long ago was it dropped in water, have you allowed it thoroughly dry out? Can you open the body of the device to allow it to dry?
Click to expand...
Click to collapse
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.
Dona2592 said:
It stayed in the water for few seconds, the bottom half of it. I shut it down and I let it dry for 2 days, after removing the battery. Anyway I brought it to a center that made a treatment for electronic contacts, an they said that it's needed to change the display first, then run some tests to see what else is wrong. The problem is that changing the screen costs 130€ and, in my opinion, won't solve the issue.
Click to expand...
Click to collapse
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?
Droidriven said:
Can you find a stock update for your specific model number in the form ol stock update.zip that can be flashed in your stock recovery like a OTA update? If so, you might be able to extract the build.prop file from the update then open the build.prop file in a note editor and edit the file by adding or editing lines that enable USB debugging. Then save the file. Then remove everything from the update.zip except for the Meta-inf or "updater script" file/folder then place your modified build.prop file in the update.zip so that it is the only thing in the zip other than the Meta-inf/updater script. Then put it on external sdcard, insert it into your device and boot into stock recovery then choose the option that lets you install updates from sdcard and try flashing your modified update.zip file and reboot the device, if it works, it will enable USB debugging. The next obstacle is getting past your lock screen, which is pointless if the device reboots in seconds. If you can get it to stop rebooting, you might be able to use adb to unlock the lock screen by using adb commands that simulate the touch input required to unlock the screen. You'll have to do some searching to find out the "address" and order of each part of the screen that you need to simulate the touch input on the screen in the right order. It's a bit complicated for those that aren't familiar but it can be done if you do the research.
Or,you can try connecting a USB mouse to the device and see if it will let you open the lock screen.
Click to expand...
Click to collapse
Plus, I don't really get why the system fails right after the lockscreen, I'm actually able to enter the code and the phone unlocks but the launcher seems not working, while the notifications bar works fine, and after some seconds the phone reboots. How can the system work fine in some aspects and bad in others at the same time? Can it be some flash memory issue?
Dona2592 said:
The procedure looks good, I'd give it a try but is there any alternative to the SD card? Cause my phone has no SD slot available. Maybe an external usb card reader to plug into the phone?
Click to expand...
Click to collapse
Yes USB should work in place of sdcard
Dona2592 said:
Plus, I don't really get why the system fails right after the lockscreen, I'm actually able to enter the code and the phone unlocks but the launcher seems not working, while the notifications bar works fine, and after some seconds the phone reboots. How can the system work fine in some aspects and bad in others at the same time? Can it be some flash memory issue?
Click to expand...
Click to collapse
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.
Droidriven said:
That or kernel panic due to some other important hardware is damaged.
Maybe you can use a adb script to interrupt the running processes right after the device unlocks. Something to stop everything from loading beyond screen unlock. It might allow you to use adb to pull whatever you want from the device via adb pull commands.
Or, if there is a custom recovery for your device and if your bootloader is already unlocked(if it isn', don't unlock it, it will wipe your data), you can install the custom recovery and use it to create a backup of your data then extract your data from the backup.
Click to expand...
Click to collapse
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Dona2592 said:
Unfortunately I still have the stock recovery. Plus USB debug is deactivated. What really boggles me is the fact that I can still enter settings and get to developer options, turn ON the toggle of USB debug, but it's like the phone doesn't save the setting, cause if I go back to the main setting screen and enter again developer options, USB debug is OFF. I mean, what the hell?
Click to expand...
Click to collapse
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.
xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
Thanks mate, I'll give it a try for sure
Droidriven said:
Hardware damaged. You're going to have to repair the hardware or forget about retrieving your data, unless you can find a reputable shop that has the equipment and experience to pull your data directly from the chip itself.
Click to expand...
Click to collapse
Ok, but do you know what could be the damaged piece of hardware?
Dona2592 said:
Ok, but do you know what could be the damaged piece of hardware?
Click to expand...
Click to collapse
NO
xXx yYy said:
Having access to device's Stock Recovery you can try as shown below to enable ADB / USB Debug ging: yes you can run Android shell commands from within Android's Stock Recovery.
Unplug device's USB-connection , boot into recovery mode. Having successfully booted into recovery mode, connect device via USB-cable with computer - what switches the USB driver to ADB mode.
Now enable USB debugging via recovery:
Code:
adb shell
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=adb,mtp" >> /system/build.prop"
reboot
Click to expand...
Click to collapse
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.
Dona2592 said:
Hello everyone,
my phone (Xiaomi MI 9T) has fallen in the water and now it's partially working.
I really need to recover some data from it, but any method I've found on the internet requires USB Debug active. The phone turns on but it works only as long as it stays on the lock screen or if I go to settings from the notification bar. If I unlock it, the launcher doesn't work (but I can still drag down the notification's bar) and after few seconds the phone reboots I'm also able to activate the toggle of the USB Debug but it looks like it doesn't stay active because if I go back and re-enter developer's section, USB Debug is OFF.
At this point I don't really know what to do. The phone enters fastboot and recovery mode, unfortunately everything is stock, so my possibilities are limited.
I haven't tried to change the screen, but I doubt that would solve the problem, since if I stay in those specific areas, it works fine.
Android version: 10
MIUI 12
Thank you
Click to expand...
Click to collapse
Is your bootloader locked?
Droidriven said:
That might work but I've never had any luck with adb in stock recovery, not on the devices that I've owned, at least.
Click to expand...
Click to collapse
Yeah in fact when I type "adb shell" it gives me error, but I can enter fastboot mode and the phone is seen. Unfortunately I can't do much from there
Arealhooman said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yeah. **** me, for once I kept everything stock and this happened . I've always rooted and customized my phones and nothing like this has ever happened.