Related
[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.
If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P
I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!
A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P
The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.
I never use my HTC cable, I use a standard mini USB cable.
P
OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.
Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P
You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!
Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P
I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.
Try doing what modaco suggested and see where that ends up.
modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.
The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?
That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P
'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.
Does the bootloader still show the old version?
P
Hi guys,
I kinda rushed flashing my hero and I think while I rooted it ok, I flashed it with the wrong image (a file called Villain5.5.0.zip instead of VillainRom10.2-Full-signed.zip).
Now after the HTC logo, the phone switches off.
However if take battery out and in (won't do it otherwise) and I hold home and switch on, it goes to recovery menu and I can connect with sdk through usb and works ok.
However in order to recover the phone I have to push the correct firmware to the phone, but when I put this:
Code:
/adb push VillainROM10.2-Full-signed.zip /sdcard/VillainROM10.2-Full-signed.zip
It does not do anything..
can someone help?! thanks in advance!
just enable mass storage mode in recovery and copy new ROM on SD card as usual.
Is there a reason you're doing it this way? Just boot into recovery...
deadwilder said:
just enable mass storage mode in recovery and copy new ROM on SD card as usual.
Click to expand...
Click to collapse
Worked perfect thanks.
I tried to flash my MS2, but now I have no boot and no access to the phone.
Story:
- root via paxChristos' Linux Port of DooMLoRD's Easy Rooting Toolkit
- backup via Titanium Backup
- backup via Bootstrap
- installed CyanogenMod and the nightly build cm_droid2_full-139.zip
- realized ... it is the wrong Mod, because for Druid2 and I have a Milestone2 = not the same
- sudo ./sbf_flash MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf
And now, I have a dead phone ... even could not start it. It is just a black screen and nothing more!
The only thing that show "life" is the LED on the side of the USB-Cable plug!
I also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable!
Is there a way to flash the phone anyway?
Would be nice to have a little help!
A little more info:
Plug in USB cable and lsusb:
Bus 002 Device 013: ID 22b8:4280 Motorola PCS
Long press on the power button and lsusb:
no Motorola
Keep USB cabel in the phone, unplug the batterie and plug in back ... lsusb:
Bus 002 Device 015: ID 22b8:4280 Motorola PCS
And more info:
udev-rule1 (worked to flash the phone)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
udev-rule2 (tried after reboot of phone showed lsusb shown before)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
Also ... not worked:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ ./adb shell
error: device not found
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
First of all ... thanks for helping me!
Anonymous_ said:
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
Click to expand...
Click to collapse
Nothing happend ... screen is black, LEDs are off!
DreadPirateDan said:
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
Click to expand...
Click to collapse
Battery should be ok, it also don't work with Charger on!
If it is impossible to remove the locked bootloader, why can I still not boot?!
If the device bricked only a black screen shows up. This is bootloader mode. RSDLite will recognise your phone and flash an SBF.
Sent from my MotoA953 using XDA App
Damn ... just bought a used one on eBay and now I have my old one fixed! *lol*
Thanks to you all ..
I used my laptop with Windows7 and RDS light from Chip Online
Then I used the SBF Version 2.3.4!
reboot ...DONE ... Milestone2 worked again!
But ...
root via zergRush_automated_Linux_root
Installed bootstrap-1.0.0.5-droid2.apk from SD-Card because:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
I think the message is very clear. The bootstrapper never installed to begin with. Second of all, why are installing the bootstrapper like that? Instead of copying it to your SD-Card and execute it from the file browser on your phone. It will be installed, after which you should execute it. It will ask for root access when you press the bootstrap button. You give it and then you press the button Reboot Recovery. Then you'll be in CWM. You can't install CM7 from Motorola's recovery, which is what you've been doing all the time.
Further: Endless7 has written a guide here: http://forum.xda-developers.com/showthread.php?t=1310641
I'd suggest you follow it, and if you don't understand something ask it.
HAPPY NEW YEAR!!!
Okay, actual I have my MS2 with the original sbf and I wait until my second MS2 is here.
Then I try to install CM!
Never the less I have questions, just to be sure.
When I install the droid2bootstrap, I just copy the file to the sdcard and then install it at the phone?! Is this correct?
Then the HowTo says: 3.open droid2bootstrap and select install recovery
But there is nothing like "install recovery" to select. There is just a screen with two buttons (Bootstrap Recovery and Reboot Recovery) ... I think "Bootstrap Recovery" first, then reboot?
If I do the steps above, I have an bootloader installed on my phone?! Which I can start with the volume buttons at bootup?
Wow, I have to learn a lot about Android phones! I read the wiki, but asking questions will help me more!
Thanks to you all!
What you described is correct except the startup with volume buttons.
You have to use the Reboot Recovery button to get in CWM, where you can flash CM7.
And just for the record: every phone has a bootloader installed, otherwise it wouldn't be able to boot an OS. Fact is that you can't replace it on the Milestone 2.
Don't mix up Recovery and Bootloader. They're different things.
sasch42 said:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
Click to expand...
Click to collapse
bootstrap is not copied to /system/app , adb said "failed to copy...".
maybe copy it do /data/app ?
You wiped data and cache.. how about dalvik?
Because the copy failed, I installed the app from the sdcard (/data/app was also read only).
But as described here (http://forum.xda-developers.com/showthread.php?t=1310641) I used the wrong app!
IMHO it is the same to copy the app via adb or install it from sdcard?!
What the shizzle, you are making it so hard for yourself.
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
EDIT: on a side note, it would seem you flashed the official gingerbread sbf, so now you will only be able to use the gingerbread kernel roms. Which is pretty much the cm9 alpha version, endless 7's cm7 defy port. Not really sure about the other gb rom (argen2stone, blurless etc). So make sure you read up on what you need and what will work
DreadPirateDan said:
...
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
...
Click to expand...
Click to collapse
Have you read all the posts?
My mistake was ti follow this guide.
And my way to install the app was, to copy it tio the sdcard because the method in the guid didn't work!
Milestone 2 Bricked
Hello friend, i am having the same problem then you...
It only show black screen and the led on the side of the usb cable and i also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable, as you and nothing...
Can you help me? please!
Do you have RSDLite? If yes, then RSDLite should detect your phone as it is already in bootloader mode (the black screen). You can flash an SBF at this point.
Download an appropriate one, if you were on Froyo then Froyo and in case you had upgraded to Gingerbread then download a GB SBF.
Flash the SBF. You would probably end up in a bootloop. Go to moto recovery, wipe data and boot. You should be good to go.
Edit: I believe that only GB sbf is gonna work for you as I suspect that you were somehow on GB and then tried to flash Froyo which led you to the black screen.
Hello,
I just came back from my honeymoon and all of my pictures are on my N4. Of course before I pull the pictures, I drop the phone is the screen is cracked and the touch does not work anymore.
I'm really desperate to get these pictures. I've read all over online but my problems are this with all of the help out there:
My phone is the latest 4.4.2 on T Mobile.
It has stock EVERYTHING (bought straight form google), and the USB debugger is not enabled. (next phone I get this is the first thing I'm enabling.
I've been trying to follow instructions online but a lot of items have changed between last year and Kit Kat now and some steps such as unlocking the bootloader seems to wipe out everything on my phone.
I've been trying to use ADB and Freeboot but really havent gotten anymore.
I've also read that I can maybe use a usb mouse to substitute and unlock my phone? USB OTG? How do I know if my nexus has that enabled?
I'm even considering getting a new screen so I can try to replace the current one and get my photos. I dont care what happens to the phone but the pictures are priceless to me.
Is there any thread or guide that incorporates 4.4.2? the more detail the better of course.
Much thanks in advance.
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Shubhamqweasd said:
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Click to expand...
Click to collapse
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
zhanism said:
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
Click to expand...
Click to collapse
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Shubhamqweasd said:
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Click to expand...
Click to collapse
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
zhanism said:
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
Click to expand...
Click to collapse
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
acejavelin said:
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
Click to expand...
Click to collapse
I have same problem with broken screen, i bought for 56$ full kit on ebay, no need separate glass from screen. took me 1h20min, never done before but what a relief seeing everything working
You do not need USB debugging to transfer files. On windows, open file explorer and with your nexus 4 connected it should appear on the left side as Nexus 4. Or if you have osx use http://www.android.com/filetransfer/.
Hi, I have a S4 i9505 with a problem, screen broken and no display at all + usb debugging is disabled.
Phone: Not rooted, original software, usb debugging disabled, no display at all
What I want to achieve: restore all my photos / videos on the phone memory, no sd card
What I have attempted:
installed ADB & fastboot based on instructions from http://forum.xda-developers.com/showthread.php?t=2786395
What I need help with:
- When i try to get into recovery mode, i wasn't sure if i am indeed in there since i can't see anything, but in total there's a vibration when i turn on the phone, and another vibration when i release the power up+power+home after pressing them down for about 5 seconds.
- When in command prompt I type adb devices and there was none, and when i type adb shell it says error: device not found
I have ensured all drivers for my phone are installed (even with PdaNetA4180 & UniversalAdbDriverSetup6 from cynanogen) but the error remains. refer to attached image.
I have done extensive search on the forum but still couldn't find any ways to get usb debugging enabled on my crippled phone.
Any step by step guide would really be helpful! Thanks
Ps. Main problem = device not found in adb , usb debugging disabled, screen no display/cracked
What do you want? To recover files? To my knowledge that is not possible.
You would first need to flash a custom recovery for adb to work in recovery.
Then you would need to allow the connection on your device (which you can't do).
Yes I need to recover photos only. Nothing else.
Please kindly guide the steps on how to flash a custom recovery (w/o control of the phone's display or touch)
Thanks.
Your device is shown connected in windows
Why not use the mtp protocol and copy whatever you want
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
If the photos are deleted by the factory reset then i am sorry to day but you cannot recover them even if you get the screen fixed
bomby481 said:
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
Click to expand...
Click to collapse
Your photos are gone and there is no way to get them back.