Develop Bugs

[Q] Copy and Install New Rom On Crashed Galaxy Nexus

Hi
I've tried instal a new rom on my Galaxy Nexus (i9250) but I fail.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Opening Update Package..."
"Installing Package..."
"Set_metadate_recursive: some changes failed
"E:Error in /sdcard/cm-11-20140607-NIGHTLY-maguro.zip
(Status 7)
Instalation aborted
I'm a new newbie and I cant post directly in downloaded rom : http://forum.xda-developers.com/galaxy-nexus/development/rom-carbonrom-kitkat-t2635637
I want to instal a new Rom on my device but I cant 'cause it doesn't have memory card slot and windows 8 didn't recognize my device
How can I copy the files on my deivce?
Anyone can help me to fix this problem?

you probably need to update your recovery img version, easiest way is using fastboot or a toolkit, like wugfresh toolkit(Google wugfresh Gnex it will come right up)
you need to install the drivers.for windows to recognize galaxy nexus as attached, wugfresh can do THAT for you as well.
although I'm a proponent of using manual methods like adb/fastboot, wugfresh can help get you started in the right direction

Wugfresh
First of all , thanks for quick reply.
You're right.My recovery img is old and didn't update since about a year and a half.
I install wugfresh but when I run the program, that doesn't recognize the device.
When I connect the mobile to laptop, I heard a sound about plug a USB Device.
The Mobile phone is on bootloader....
and becaue I didn't know device build number, I click Auto Detect Device + Build....
But doesmn't happen anything

if you aren't worried about losing any user data, first flash a factory stock image which will put device back to out of box state, then you can pick which build and such,
or, before that, do a quick google search for "xda, galaxy nexus, windows 8.1 driver issue" I think I recall someone having similar issues and getting them resolved and the thread should have the info you need in it.
let us know if you find the info you need.

Wugfresh
I Use wugfresh (Nexus Root Toolkit)
Before that , I installed the adb drivers and also change my o.s from Win8 to win XP.
but I see this error while repairing my phone : (the attached file)
I'm so confused...
I didn't what to do...

Install the adb and fastboot drivers.
EDIT: Use the "Full Driver Installation Guide"
Sent from my Galaxy Nexus using XDA Free mobile app

AGoogleUser said:
Install the adb and fastboot drivers.
EDIT: Use the "Full Driver Installation Guide"
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I'm trying....

I Couldn't
I even try this : http://forum.xda-developers.com/showthread.php?t=2588979
It doesn't recognise my phone.
I feel dumb!

Let me explain my problem by photos :
I run nexus Root Toolkit
In advanced utilities , click on "Launch"
In apperaed window , "Boot Temporary" , I click on "Custom Recovery", then I must browse the file "openrecovery-twrp-2.7.0.0-maguro.img"
After browse the file , this Message Appear : Reebooting your device into bootloader . . .
Then after afew secondes , This message blowes my mind : Fastboot Device Was Not Found . . . .
Also in other parts of Nexus Root Toolkit I have the same problem....
Is there anyway to solv ethis problem?

I would recommend removing the drivers that are installed. it seems that the wrong ones, or maybe something just "borked" with them, happened on original install.
when you plug in device, go into device manager, should be able to right click on your device and uninstall drivers.
then I recommend putting device in bootloader mode. plug in, and see if it installs the drivers automatically for you.
there should also be an.option in wug to "install drivers" I think.
(in your pictures, window on the right side, "Full Driver install....", long button on the top)
::::TRY THIS FIRST::::
I just noticed that you have chosen ICS for model/OS. it is probably trying to use the old fastboot binary for it or something, change that and try 4.2 or even 4.3, you could also try 4.1 but I'm thinking the 4.2or4.3 choice will work for you.
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
do you KNOW how to manually put phone into bootloader/fastboot mode correct?
if not, from powered down state, hold power, volume up, and volume down, all at the same time for a few seconds, it will vibrate, and bring up the bootloader.
I know on my machine, I befoee had to uninstall drivers, then plugged device in while in bootloader mode, and waited as it installed automatically the correct drivers needed.

A million times thanks to you.............................
You saved me
You're my hero....
Thank u so much for your patience & helpful guides....
God bless you....:good::good::good::good::good::good::good:

arashcd said:
A million times thanks to you.............................
You saved me
You're my hero....
Thank u so much for your patience & helpful guides....
God bless you....:good::good::good::good::good::good::good:
Click to expand...
Click to collapse
no problem at all buddy! happy to help!
can I ask what exactly solved it do you know?
also, if issue is resolved, if you can edit your initial post's thread title to say [SOLVED] in front so others know the issue is resolved and others looking for the info provided with the same issue can easily find the fix/steps if needed.
(I don't know if you use tapatalk for forum browsing, but you may have to edit the title of thread via web browser)
if you need anything else feel free to ask here or PM!

I think my problem returns to install drivers.
After your last guide, I removed drivers and for install drivers, I use from Nexus Root Toolkit....
Just one Question :
For last time : How Can I add "Solved" to topic title?
I didn't find any button to do that...

arashcd said:
I think my problem returns to install drivers.
After your last guide, I removed drivers and for install drivers, I use from Nexus Root Toolkit....
Just one Question :
For last time : How Can I add "Solved" to topic title?
I didn't find any button to do that...
Click to expand...
Click to collapse
go to your initial post, there should be button below it that says "edit" or similar. click that, then you probably have to click "go advanced" or "advanced edit" or something like that, I think then you will be able to edit the post title.
if not it's not THAT important

Touch not working after display assembly replacement

Got my replacement display assembly a couple days ago and went on to replace the screen. Connected everything back and everything seems to work - except for the touch screen functionality.
Checked the ifixit tutorial for display assembly replacement and found that someone commented that he has the exact problem, stating he found a guide to "remove the metal protection over the connector to properly disconnect it and reconnect after"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Checked the connection multiple times, seems to be connected properly, which makes me assume that what he did works. Thing is - I don't understand how am I supposed to remove everything and put it back together.
Any help?
Thanks.

firecharge said:
Got my replacement display assembly a couple days ago and went on to replace the screen. Connected everything back and everything seems to work - except for the touch screen functionality.
Checked the ifixit tutorial for display assembly replacement and found that someone commented that he has the exact problem, stating he found a guide to "remove the metal protection over the connector to properly disconnect it and reconnect after"
Checked the connection multiple times, seems to be connected properly, which makes me assume that what he did works. Thing is - I don't understand how am I supposed to remove everything and put it back together.
Any help?
Thanks.
Click to expand...
Click to collapse
The copper looking piece is held in with small clips around the edges. I used a small flat head inserted into the corners and pried straight up to lift it out of the clips. It came off pretty easily. Then you just need to line it back up with the clips and press down to replace it.
Sent from my ASUS_Z00A using Tapatalk

buddy factory reset your device once. there might be difference in touch version.

kenbo111 said:
The copper looking piece is held in with small clips around the edges. I used a small flat head inserted into the corners and pried straight up to lift it out of the clips. It came off pretty easily. Then you just need to line it back up with the clips and press down to replace it.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks
That worked great - though there is a different issue now.
Phone seems to keep locking and unlocking itself every few seconds.
Seems to be an issue in the connection between the bottom and top parts of the mobo.
Any idea about what could be the issue here?

Hi, I don´t want to make new thread, maybe someone can tell me how to fix my problem.
I changed Lcd+touch for my ZE500CL/Z00D and first Touch Panel Firmware update failed, but after hard reset trough recovery it started to work. But now every time I turn it off nad on / or just reboot, it updates touch panel firware.. luckily successfully... but every time.. I use last official SW version (V12.16.5.126 ).

Mairo said:
Hi, I don´t want to make new thread, maybe someone can tell me how to fix my problem.
I changed Lcd+touch for my ZE500CL/Z00D and first Touch Panel Firmware update failed, but after hard reset trough recovery it started to work. But now every time I turn it off nad on / or just reboot, it updates touch panel firware.. luckily successfully... but every time.. I use last official SW version (V12.16.5.126 ).
Click to expand...
Click to collapse
really appreciate that its good to not to start new threads without any actual requirement
flash raw firmware once. you can get the firmware from following thread
https://forum.xda-developers.com/zenfone2/help/guide-bring-to-life-zenfone-2-ze500cl-t3503144

sukhwant717 said:
really appreciate that its good to not to start new threads without any actual requirement
flash raw firmware once. you can get the firmware from following thread
https://forum.xda-developers.com/zenfone2/help/guide-bring-to-life-zenfone-2-ze500cl-t3503144
Click to expand...
Click to collapse
it looks too much struggle, so if there is no other way then I leave it so. ( I have Win 10 and usb keyboard, so I can´t disable driver signatures ). Or can I flash this raw.zip in root folder like odher updates?

Mairo said:
it looks too much struggle, so if there is no other way then I leave it so. ( I have Win 10 and usb keyboard, so I can´t disable driver signatures ). Or can I flash this raw.zip in root folder like odher updates?
Click to expand...
Click to collapse
buddy that link was to get raw firmware only. you do not need to disable signature enforcement. just download rar firmware file and flash it with AFT. use the only section flash raw firmware. you need to install only asus usb driver

sukhwant717 said:
buddy that link was to get raw firmware only. you do not need to disable signature enforcement. just download rar firmware file and flash it with AFT. use the only section flash raw firmware. you need to install only asus usb driver
Click to expand...
Click to collapse
impossible to find proper step by step AFT using guide, 1. like do in need first unlock bootloader? 2. when I boot (power + vol up) fastboot mode then AFT dont find phone and "fastboot cmd waiting" .. . is in red, everywhere I can see users have blue text there. 3. do in need activate USB debuging?
Flashing is not something unknown for me , I have using 3 years Nexus 5 and still using it, but flashing asus devices is unknown and strange.
I better leave this phone as it is. I hope user have extra 10 sec time to wait touch panel update on every boot.

Mairo said:
impossible to find proper step by step AFT using guide, 1. like do in need first unlock bootloader? 2. when I boot (power + vol up) fastboot mode then AFT dont find phone and "fastboot cmd waiting" .. . is in red, everywhere I can see users have blue text there. 3. do in need activate USB debuging?
Flashing is not something unknown for me , I have using 3 years Nexus 5 and still using it, but flashing asus devices is unknown and strange.
I better leave this phone as it is. I hope user have extra 10 sec time to wait touch panel update on every boot.
Click to expand...
Click to collapse
to use AFT all you need is device in fastboot mode. check if drivers are properly installed. which version of AFT you are using?

Amazon Recovery <3e>

Hello together,
have a problem with my first gen Fire TV 2014 box.
Went on vaccacion and turned everyhting off, when i came back and turned everything back on, the Fire Tv is only booting into recovery mode.
Is there a way to fix it? the box was not modified in any way, except a sideloaded kodi.
So im wondering if its possible to somehow reinstall the full-software, on a phone it would be possible using odin for samsung for example, but is there anyway to do so on a firetv? jtag, anything?
regards
Vin

Does if give you the option to wipe cache? I have not dealt with the factory recovery, but you can always wipe the cache then reboot and see what happens. Worst case wipe Data and cache (that is like a factory reset and you will have to reinstall everything).

No its just a blank Page unfortunately with the Information to wait till it reboots (it doesnt) and in case it doesnt to pull the cable, which also doesnt help.
Would love to wipe everything regardless of the Data, but cannot figure Out how to get this Option
Amazon Recovery Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm having the same issue. Chatted with amazon and tech told me this is a know issue and there is a master ticket and my info was added to the list. Someone should contact me within 3 days. I think an update probably bricked my device. What are the odds they send me a new one? Will post update.
I tried some troubleshooting prior. Was trying to adb into it but checking router, it doesn't have an ip, wireless or wired, which is what is needed to adb into it. I also put the firmware on a usb and renamed it recovery.bin but wouldn't load. Connected it to laptop via usb to usb cable. Using a usbview windows 10 debug program, it only connects when booting and on the white logo screen. So when you get that recovery message, there is no power to usb port.
Just have to now wait for them to contact me.

any news so far?
when i called the amazon support hotline (germany), they said its no known issue and there is nothing they can do, also since the warranty is over, there wont be any solution, or replacement whatsoever, very disappointing to be honest

This is exactly the same problem i have.
My FireTV 1 just boots into the colored animated logo and doesn't go any further.
From there i can get a adb shell via a usb a-a cable. But i don't know what to do at this point.

Mine Bricked Thursday during a software update. A gen 1 box. If I could get the software reload onto a USB drive, I know it would reboot. Amazon admitted they had been getting calls all night ( I called at 10:00 PM). The rep promised me a replacement (fat chance) but didn't send me anything. I tried a USB keyboard but no go.

m0r0k said:
This is exactly the same problem i have.
My FireTV 1 just boots into the colored animated logo and doesn't go any further.
From there i can get a adb shell via a usb a-a cable. But i don't know what to do at this point.
Click to expand...
Click to collapse
You could always try wiping from the shell... Cache or a factory reset, just throwing out ideas....

something like this still a possibility?
https://www.youtube.com/watch?v=IgC4iDzQ8gw
or is there a way to boot up an original amazon update via usb?
Still have a working recovery menu, so there must be something usefull to do with it, just cant select anything on the screen (see picture in previous post)

m0r0k said:
This is exactly the same problem i have.
My FireTV 1 just boots into the colored animated logo and doesn't go any further.
From there i can get a adb shell via a usb a-a cable. But i don't know what to do at this point.
Click to expand...
Click to collapse
You have a different issue. We have a white logo and the 3e error. Wish I had your problem, I could recover it.
Google how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software. Can't post urls since I'm new
---------- Post added at 11:11 PM ---------- Previous post was at 10:55 PM ----------
Vin 2 said:
something like this still a possibility?
or is there a way to boot up an original amazon update via usb?
Still have a working recovery menu, so there must be something usefull to do with it, just cant select anything on the screen (see picture in previous post)
Click to expand...
Click to collapse
Unfortunately we don't have a working recovery menu. It should have other options. Google how-to-unbrick-by-entering-recovery-mode-and-factory-reset-the-amazon-fire-tv, and you'll see the options we should have. Can't post urls, too new. They called today and scheduled someone to pick it up to have it delivered to lab for review. Was hoping they would give me the steps to access and recover it but looks like they will be doing it instead since they probably have to open it up like that youtube video you posted to access it directly. I hope they send me an updated device and just keep mine for review and testing.

Toonice007 said:
You have a different issue. We have a white logo and the 3e error. Wish I had your problem, I could recover it.
Google how-to-revert-an-amazon-fire-tv-back-to-stock-recovery-and-stock-software. Can't post urls since I'm new
Click to expand...
Click to collapse
First of all, thank you. The problem is my device is unrooted.
Booting into recovery gives me the same unusable Amazon system recovery <3e> screen.
It looks like my FireTV (gen1) has the newest software, which is maybe the cause of the problem:
Code:
$ cat system/build.prop | grep fireos
ro.build.version.fireos=5.2.6.0
Is there a way to root it via adb shell?
Thanks for any hints.

m0r0k said:
First of all, thank you. The problem is my device is unrooted.
Booting into recovery gives me the same unusable Amazon system recovery <3e> screen.
It looks like my FireTV (gen1) has the newest software, which is maybe the cause of the problem:
Code:
$ cat system/build.prop | grep fireos
ro.build.version.fireos=5.2.6.0
Is there a way to root it via adb shell?
Thanks for any hints.
Click to expand...
Click to collapse
I could be wrong but I don't think you can root that version yet. Sorry I do see in the instructions you need to be rooted.

Sorry all. They had me ship them the firetv and gave me $85 promo credit on Amazon. Was hoping they would instruct me on how to fix it.

same for me, nobody was able to give a solution, was redirected to real technical support in the backoffice>no solutions
finally after many tries, amazon was ready to give a accommodating arrangement, they will replace my 2014 model, with the 2017 model thats going to be released end of october, despite the lack of warranty
but yes still its a disappointment to have working hardware, but broken software here, would have liked to continue using the old model

Looks like they realize it's an issue with the update that affects at least the first gen Fire TV. Good that they are doing the right thing. That's why I like and buy Amazon. Hopefully others see this post and get the same compensation.

I'm using the firetv 1 model too. I'm rooted and have blocked updates, thankfully. I really wonder if this update bricked all the aftv 1 models. I'm hoping for a prerooted @rbox image. This new software is really needed, because all software revisions before have the very serious bluetooth vulnerability that affects all operating systems (your device grants console access to any attacker in bluetooth range without your notice).
For me, the 2017 model is no option since i depend on the optical out.

Sorry for bumping an old thread, but I have a Fire Tv Stick 2nd Gen (not rooted) and getting the same amazon system recovery 3e as posted by OP.
Wondering if any fix was found for the same as I do not see a resolution mentioned in this thread.

rocker123 said:
Sorry for bumping an old thread, but I have a Fire Tv Stick 2nd Gen (not rooted) and getting the same amazon system recovery 3e as posted by OP.
Wondering if any fix was found for the same as I do not see a resolution mentioned in this thread.
Click to expand...
Click to collapse
You may just unlock the stick. With twrp recovery you can fix your issue.

Sus_i said:
You may just unlock the stick. With twrp recovery you can fix your issue.
Click to expand...
Click to collapse
Is there an easier way out... The steps listed for TWRP installation seem to be a bit complex..
Tried plugging in a USB keyboard to my TV, (alt+ prt sc+ I), did not work for me..
Is there a physical button inside the AFTT to do a hard reset ?

rocker123 said:
Is there an easier way out... The steps listed for TWRP installation seem to be a bit complex..
Tried plugging in a USB keyboard to my TV, (alt+ prt sc+ I), did not work for me..
Is there a physical button inside the AFTT to do a hard reset ?
Click to expand...
Click to collapse
No, there isn't any button inside
A way easier solution is to buy a new device...

Firestick Gen 2 Stuck In Update Boot Loop

Hey, I have an Amazon Firestick, I believe that it is generation 2 because of the model number on the back of the device. I have an issue with my device. When I plug it in it says that it is installing the latest software then it will proceed to say that it was unsuccessful and reboot. Into the most annoying loop ever. If you guys have any ideas PLZ let me know I have been looking to fixing it for a while now and I would love for my kids to stop bugging me!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Jlopezisthebest said:
any ideas PLZ let me know I have been looking to fixing it for a while now
Click to expand...
Click to collapse
The unbrick for the second generation stick is here.

I'll give it a try and let you know. Thanks for the response!!

Sus_i said:
The unbrick for the second generation stick is here.
Click to expand...
Click to collapse
Hey, I know its been a couple of days, I just wanted to let you know that the process/ exploit did not work. I'm not quite sure what I did wrong.
I updated everything in ubuntu
I downloaded the zip
Extracted using WinRAR
Opened the file in Ubuntu
Ran the ./bootrom-setup.sh in ubuntu
Shorted the stick using a piece of conductive wire
Then waited for the terminal to do its thing, but nothing happened.
Please let me know if I did anything wrong or anything that can help my situation.
EDIT: Couldn't find lsusb btw that might have been the issue, not sure where to find that or run it
Juan

Jlopezisthebest said:
Hey, I know its been a couple of days, I just wanted to let you know that the process/ exploit did not work. I'm not quite sure what I did wrong.
I updated everything in ubuntu
I downloaded the zip
Extracted using WinRAR
Opened the file in Ubuntu
Ran the ./bootrom-setup.sh in ubuntu
Shorted the stick using a piece of conductive wire
Then waited for the terminal to do its thing, but nothing happened.
Please let me know if I did anything wrong or anything that can help my situation.
EDIT: Couldn't find lsusb btw that might have been the issue, not sure where to find that or run it
Juan
Click to expand...
Click to collapse
Idk if you did something wrong, except the winrar thing.
Ubuntu is fine, but you need to run all commands from the unlock/unbrick OP up to the disable modemmanager thing.
Download and unzip the amonet.zip (to the desktop) with ubuntu (don't use windows for this, all file permissions get lost).
Browse in the extracted folder and open a terminal in there.
Then run this
Code:
sudo su
./bootrom-step.sh
Now you need to short the CLK resistor to ground.
Don't use sharp steel tools, best is a fine soft flexible copper wire...
Keep the short (steady and proper, until the script tells you to remove the short), then connect the usb cable...
It should take up to 10 seconds to find the stick and do the handshake.
If nothing happens within 15 seconds, the short wasn't that proper, in this case unplug the stick and retry again.
But it's possible too, that you've got one of the newer patched sticks!?
How old is your stick?
You can take a look into lsusb,
the first boot stage is the bootrom, it prints something about 'phone' (this should pop up in lsusb while shorted),
next stage is the preloader (if you see this, the short wasn't steady/proper).
Good luck^^
Edit: PS, to run lsusb command, you need to open a second terminal window...

Sus_i said:
Idk if you did something wrong, except the winrar thing.
Ubuntu is fine, but you need to run all commands from the unlock/unbrick OP up to the disable modemmanager thing.
Download and unzip the amonet.zip (to the desktop) with ubuntu (don't use windows for this, all file permissions get lost).
Browse in the extracted folder and open a terminal in there.
Then run this
Code:
sudo su
./bootrom-step.sh
Now you need to short the CLK resistor to ground.
Don't use sharp steel tools, best is a fine soft flexible copper wire...
Keep the short (steady and proper, until the script tells you to remove the short), then connect the usb cable...
It should take up to 10 seconds to find the stick and do the handshake.
If nothing happens within 15 seconds, the short wasn't that proper, in this case unplug the stick and retry again.
But it's possible too, that you've got one of the newer patched sticks!?
How old is your stick?
You can take a look into lsusb,
the first boot stage is the bootrom, it prints something about 'phone' (this should pop up in lsusb while shorted),
next stage is the preloader (if you see this, the short wasn't steady/proper).
Good luck^^
Edit: PS, to run lsusb command, you need to open a second terminal window...
Click to expand...
Click to collapse
I gave up and just bought a lite on amazon, its ONLY $18, can't beat it. Thanks for all of the assistance. If I ever get around to it ill give it another shot. Yet again thank for the help!!
Juan

Question is it possible to backup my phone with my current issue?

i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone

testask123 said:
i need help making a backup of my phone, my screen is black so i can't see anything. my pc does recognizes it when connected.
p.s. haven't rooted my phone
Click to expand...
Click to collapse
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.

TechnoSparks said:
does the phone still have touch working despite screen is black? Touch is required because you will need to enable Developer Options and then USB debugging. Afterwards, you should be able to control your device via scrcpy using a computer. Or, make file backups by leveraging ADB command "adb pull", though this would already be possible when you connect the device and choose "File transfer" on a window that appears.
Click to expand...
Click to collapse
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?

testask123 said:
i can't tell, i don't here or feel vibration.
if i can't access debug, can i not backup?
is there no program that can make one?
Click to expand...
Click to collapse
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?

TechnoSparks said:
I have an idea but i may have to test first.
Is your phone stock or have you unlocked the bootloader?
Click to expand...
Click to collapse
bootloader is not unlocked

testask123 said:
bootloader is not unlocked
Click to expand...
Click to collapse
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
edit: also because i totally forgot that unlocking the BL will definitely wipe the device, which defeats the purpose of this thread!

TechnoSparks said:
Is the warranty still valid? If YES, then i cannot help you, because unlocking the bootloader may render the warranty void (but i am not sure, you may confirm with relevant Xiaomi service centres).
ignore everything. this is because there is nothing we can do without the authorization from adb, or choosing "file transfer" during USB connection when in the OS
i am sorry
Click to expand...
Click to collapse
is there no trustworthy program that could back it up?

testask123 said:
is there no trustworthy program that could back it up?
Click to expand...
Click to collapse
With what i knew so far with [AOSP] Android, no, because there needs to be a user confirmation on the screen. I suppose maybe Xiaomi have some proper backup tools? (I guess)

Oh yeah, maybe an external display could work. Please wait while I try to gather some limited information

After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?

Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
Could you go into details as to how to modify boot.img to enable adb?
I tried searching a bit but nothing came up

It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.

Renate said:
It's mostly changing prop.default in the image, maybe add something to start adbd earlier in the boot process.
Or making a rooted recovery.
But this is all based on being able to flash something, either in fastboot or at a lower level with EDL/MSM.
Click to expand...
Click to collapse
Ahhh I see , but why boot.img? It's rather difficult to modify for you gotta unpack ramdisk and all? ( I tried doing this long time ago but got stuck on how to repack properly x: )
System.img / vendor.img should be better targets for u can unsparse them ( make rw ) on PC and easily edit .prop files
It's a rly good idea

It's easier to pack something if you never unpack it.
imgutil.exe in my sig lets you modify boot images without taking it all apart.
Warning: Android moves on and many busy bees are working to make our lives more difficult.
If you have problem with imgutil.exe contact me about it.
Code:
C:\>imgutil.exe /v /x boot.img prop.default
C:\>my-fave-editor.exe prop.default
C:\>imgutil.exe /v /r boot.img prop.default
Just don't use some ignorant Windows editor like "Notepad" that uses \r\n.
I like Notepad++.
Also, with a boot image you can try booting it without flashing it.

TechnoSparks said:
After some quick googling @testask123 , the Poco F3 does not support HDMI-out through the usb-c port. This looks to me like a dead end, and we won't be able to backup the data from the phone. Because as previously mentioned, in order to backup any meaningful data, the user have to interact with the screen for confirmations.
I actually under the assumption that you want to backup the device before sending it for warranty replacement. I also assume that your screen is broken in some way, but the device is functional, for example, you can receive calls. If you are not going to warranty claim the phone, then you may replace the screen at repair shops without needing to format your data at all, thus giving you access to everything on your device once everything is up and running.
Final question, does the touch screen still work despite the screen is black?
Click to expand...
Click to collapse
it's hard to tell, maybe i should try to see if i can pull it of, but don't know the exact position of the usb setting in the dropmenu.
if someone could provide some screenshot, it might give me an idea where to tap.

Renate said:
Did you have a recovery on it? Did it have ADB enabled on it? Can you get to recovery?
If you were unlocked and especially if you had Magisk'ed it we could easily mod the boot image to enable ADB.
Click to expand...
Click to collapse
i remember turning on wifi debugging, but dont know if that's still the case or even useful

testask123 said:
i remember turning on wifi debugging, but dont know if that's still the case or even useful
Click to expand...
Click to collapse
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)

Renate said:
Well, try to connect. Is WiFi on? Do you know the IP address? Can you get it from the router? Can you ping it?
Code:
C:\>adb connect 192.168.1.?
("?" is not literally a question mark, put a small number in there.)
Click to expand...
Click to collapse
the ip from the phone?
sorry i'm not so knowledgeable about these things and wanted to make sure

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, the IP of your phone.
If you're on your own router you can log in and see if your phone is there and what IP.
Now you know that my cheap Walmart tablet is on (local) IP 192.168.1.4