Hi everyone,
I hope anyone can help me with this.
After trying to change lcd density with apps from the playstore.
The mojo brings me a black screen, no logo at startup, the only thing what i can do is the root procedure, it displays me " Key driver not found.." etc.. but nothing after that.
I don't know how to restore it, or factory reset it, or acces to build.prop etc.. and also i can't acces to devices via usb => computeur(adb not listed)
If anyone get an idea, it will be great.:good:
LCD density? What app did you use? Why are you adjusting an LCD setting on a device that does not have an LCD screen? Try unplugging it for 15 minutes and then plug it back in.
EDIT: I see what you did. You used LCDDensity to try to increase the resolution. Not a great idea. You probably picked some value that is way outside of what the Mojo will display. Since this app requires root you had to grant privileges to it in order to do this. I don't know if you will be able to fix it until some method if sending a recovery image to the device (and a recovery image for that matter) is revealed.
EDIT 2: Can you try this:
http://www.freaktab.com/showthread.php?12075-FOUND-MAD-CATZ-M-O-J-O-RECOVERY-MENU
If you can get to be able to choose "Yes" for factory reset maybe it will help. It's something to try.
re :Black screen
I put a windows typical keyboard and try the mojo recovery menu procedure, always same black screen.
Now i found an image.zip call "mojo-signed-ota-MO0202-WW.zip" but how to use it now, maybe via fastboot or anything else because it's only way for now that displays me something from mojoto hdmi monitor.
daves94 said:
I put a windows typical keyboard and try the mojo recovery menu procedure, always same black screen.
Now i found an image.zip call "mojo-signed-ota-MO0202-WW.zip" but how to use it now, maybe via fastboot or anything else because it's only way for now that displays me something from mojoto hdmi monitor.
Click to expand...
Click to collapse
You'll need to contact, Madcatz for support.
gwaldo said:
You'll need to contact, Madcatz for support.
Click to expand...
Click to collapse
Hi,
I've allready contact Mad Catz support and submit a ticket, we will see if they give me a way to unblock this box.
Thanks
daves94 said:
Hi,
I've allready contact Mad Catz support and submit a ticket, we will see if they give me a way to unblock this box.
Thanks
Click to expand...
Click to collapse
Keep us updated. I am curious to see what their solution is. Either RMA the unit or reveal a recovery method to you. If the latter, I am certain many folks (myself included) would really like to know!
zektor said:
Keep us updated. I am curious to see what their solution is. Either RMA the unit or reveal a recovery method to you. If the latter, I am certain many folks (myself included) would really like to know!
Click to expand...
Click to collapse
Hi,
We will see, i posted a ticket on friday, and a guy "symphatic" told me on live chat support that it would take 2-3 open days to have an answer.
I saw in another post on xda that one guy have similar problem but due a rom update i think.
I will keep you up to date with this an we'll check at the same time if they have a good technical support.
Thanks guys.
http://forum.xda-developers.com/showthread.php?p=52563100#post52563100
davhttp://forum.xda-developers.com/showthread.php?p=52563100#post52563100es94 said:
Hi everyone,
I hope anyone can help me with this.
After trying to change lcd density with apps from the playstore.
The mojo brings me a black screen, no logo at startup, the only thing what i can do is the root procedure, it displays me " Key driver not found.." etc.. but nothing after that.
I don't know how to restore it, or factory reset it, or acces to build.prop etc.. and also i can't acces to devices via usb => computeur(adb not listed)
If anyone get an idea, it will be great.:good:
Click to expand...
Click to collapse
Do not play with a build prop on a m,o,j,o it wil screw it up likely,but if you can access a terminal on the console or command it in windows/linux/mac osx etc somehow,then you can reset the screen resolution,to do that use this set of commands in a terminal for the mad catz m.o.j.o if possible: type: su ,no comma though then hit the enter key, then type: am display-size reset ,no comma though and again hit enter key.
If a terminal is accessible which i guess it should be if usb debugging option was left turned on if usb debugging was turned off before this your [email protected],but don't ask me how you do this as i am not a developer,but it would reset the resolution on the console to factory and allow it to work for sure if performed on a terminal within the console which you cannot get access to at present,but i do think it may be possible in windows over usb debugging somehow?
I found the recovery menu i covered it in a thread here,but it only says erase not erase/restore so i guess it is dangerous doing that,the other question is does root work on erase if it does restore it,and or did altering your resolution alter the build prop file which erase/restore may/may not restore to factory after such changes making erase option in recovery dangerous although you could try it but be warned it could wipe/brick the device possibly.1st try to use the commands i gave it's easier and safer to toy with.It also 100% worked within the os when i used resolution changer pro and got it stuck in a shrunken screen size you couldn't see all the icons in.
the link to the post about accessing the recovery menu is at the very top of this post #8 post, it links to my freaktab page on how to access the recovery menu,you can only use a usb keyboard for this in usb 2.0 port though to be on the safe side remove any sd card carrying data on it if you choose to erase do not erase cache etc though at a guess?To be completely safe ask what each erase option does on the site 1st otherwise you may completely brick your m.o.j.o at present it is ok but semi bricked and still would function if you can get terminal up to alter the resolution.
PHYSC-1 said:
http://forum.xda-developers.com/showthread.php?p=52563100#post52563100
Do not play with a build prop on a m,o,j,o it wil screw it up likely,but if you can access a terminal on the console or command it in windows/linux/mac osx etc somehow,then you can reset the screen resolution,to do that use this set of commands in a terminal for the mad catz m.o.j.o if possible: type: su ,no comma though then hit the enter key, then type: am display-size reset ,no comma though and again hit enter key.
If a terminal is accessible which i guess it should be if usb debugging option was left turned on if usb debugging was turned off before this your [email protected],but don't ask me how you do this as i am not a developer,but it would reset the resolution on the console to factory and allow it to work for sure if performed on a terminal within the console which you cannot get access to at present,but i do think it may be possible in windows over usb debugging somehow?
I found the recovery menu i covered it in a thread here,but it only says erase not erase/restore so i guess it is dangerous doing that,the other question is does root work on erase if it does restore it,and or did altering your resolution alter the build prop file which erase/restore may/may not restore to factory after such changes making erase option in recovery dangerous although you could try it but be warned it could wipe/brick the device possibly.1st try to use the commands i gave it's easier and safer to toy with.It also 100% worked within the os when i used resolution changer pro and got it stuck in a shrunken screen size you couldn't see all the icons in.
the link to the post about accessing the recovery menu is at the very top of this post #8 post, it links to my freaktab page on how to access the recovery menu,you can only use a usb keyboard for this in usb 2.0 port though to be on the safe side remove any sd card carrying data on it if you choose to erase do not erase cache etc though at a guess?To be completely safe ask what each erase option does on the site 1st otherwise you may completely brick your m.o.j.o at present it is ok but semi bricked and still would function if you can get terminal up to alter the resolution.
Click to expand...
Click to collapse
Yeah i saw your method,but in my case i can't acces to an adb shell (termnial) to put "am display reset" command, i'm on macos and i can't list my mojo attached via mac's terminal in adb mode, (i've done kill...start...adb server) my mojo only appear in fastboot mode (fastboot-mac devices) it seems that it can't past the bootloader.
I've found a ROM named "mojo-signed-ota-MO0202-WW.zip" but can't flash it coz i think this rom can only be applied via recovery mode (clockword etc..).
I know that in fastboot mode we can also flash a rom, it has command to do it, but need the right files(img, etc...) which is not in that rom.
I know also that we can make system.img etc... from a rom like this but i'll be laborious, coz i am not develloper too, and i just have some basics on linux distro's but if mad catz don't give me a method to unblock my box or give me a fully stock rom, i will try it.
Well, we'll see i'll keep you up to date.
Thanks.
daves94 said:
Yeah i saw your method,but in my case i can't acces to an adb shell (termnial) to put "am display reset" command, i'm on macos and i can't list my mojo attached via mac's terminal in adb mode, (i've done kill...start...adb server) my mojo only appear in fastboot mode (fastboot-mac devices) it seems that it can't past the bootloader.
I've found a ROM named "mojo-signed-ota-MO0202-WW.zip" but can't flash it coz i think this rom can only be applied via recovery mode (clockword etc..).
I know that in fastboot mode we can also flash a rom, it has command to do it, but need the right files(img, etc...) which is not in that rom.
I know also that we can make system.img etc... from a rom like this but i'll be laborious, coz i am not develloper too, and i just have some basics on linux distro's but if mad catz don't give me a method to unblock my box or give me a fully stock rom, i will try it.
Well, we'll see i'll keep you up to date.
Thanks.
Click to expand...
Click to collapse
TMK, fastboot only flash the boot rom, at least that's what in the v2 update the sys files are just overwritten, but not a rom.
I dont think fastboot can flash the nand/OS partition.
Yeah if you get a system rom and way of installing, I too would be interested.
I'm guessing it's something they can't openly distribute...
I guess it's something we can do ourselves... just have had the time to research...
daves94 said:
Yeah i saw your method,but in my case i can't acces to an adb shell (termnial) to put "am display reset" command, i'm on macos and i can't list my mojo attached via mac's terminal in adb mode, (i've done kill...start...adb server) my mojo only appear in fastboot mode (fastboot-mac devices) it seems that it can't past the bootloader.
I've found a ROM named "mojo-signed-ota-MO0202-WW.zip" but can't flash it coz i think this rom can only be applied via recovery mode (clockword etc..).
I know that in fastboot mode we can also flash a rom, it has command to do it, but need the right files(img, etc...) which is not in that rom.
I know also that we can make system.img etc... from a rom like this but i'll be laborious, coz i am not develloper too, and i just have some basics on linux distro's but if mad catz don't give me a method to unblock my box or give me a fully stock rom, i will try it.
Well, we'll see i'll keep you up to date.
Thanks.
Click to expand...
Click to collapse
The recovery menu has update from zip file so why not try it? Put the file on an sd card and see if recovery install from zip allows that 202 update to be done without being inside the os,It's going to be risky but in your case if they opt not to fix it free,and i gather they won't without charge it's not going to hurt, as you've voided the warranty any way messing without being insulting.
daves94 said:
Hi everyone,
I hope anyone can help me with this.
After trying to change lcd density with apps from the playstore.
The mojo brings me a black screen, no logo at startup, the only thing what i can do is the root procedure, it displays me " Key driver not found.." etc.. but nothing after that.
I don't know how to restore it, or factory reset it, or acces to build.prop etc.. and also i can't acces to devices via usb => computeur(adb not listed)
If anyone get an idea, it will be great.:good:
Click to expand...
Click to collapse
Hi Dave,
I had the same problem after a reboot of the m.o.j.o ...
I only could push an image on it but without success.
The hotline sent me this link :
http://www.freaktab.com/showthread.php?12075-FOUND-MAD-CATZ-M-O-J-O-RECOVERY-MENU
But the keyboard was not recognized.
I think the best way is to push all the rom "mojo-signed-ota-MO0202-WW.zip" on it.
Because the image is only 6Mb against 240Mb.
Do you fix it ?
TE=French_Dev;52669246]Hi Dave,
I had the same problem after a reboot of the m.o.j.o ...
I only could push an image on it but without success.
The hotline sent me this link :
http://www.freaktab.com/showthread.php?12075-FOUND-MAD-CATZ-M-O-J-O-RECOVERY-MENU
But the keyboard was not recognized.
I think the best way is to push all the rom "mojo-signed-ota-MO0202-WW.zip" on it.
Because the image is only 6Mb against 240Mb.
Do you fix it ?[/QUOTE]Yes that's my freaktab page i made lol.But it's going to have to be usb not a ps2/usb adaptor,it does work trust me if your using usb 2.0 port it works with a usb keyboard,the only time it won't is if your not 100% right in how you press the keys.
can get it on my usb keyboard a cheap 5 quid generic keyboard,so i seriously doubt you can't.Unless your pressing the order of the key differently
you need to :boot from cold with keyboard in 1st read bottom paragraph then start step 1.
Step 1.1st press alt then print screen and then i hold them in as you are pressing them in that order after turning on the m.o.j.o before the light comes on though not after it will not work if you do that,doit very quickly
Step 2.Then you see the blue light appear release and repress i key holding the rest down still keep i key held in for 5 seconds release press again for five seconds release press down for 5 seconds keep doing that until white writing appears keep those alt and print screen keys on all the time whilst doing the 5 second press of i key,until white writing appears.
Step 3.Once done you'll land at a broken robot screen tust me you can do it,once there you need to press the windows symbol key hold it on, then press the print screen key hold that on as well keep both held on and finaly press home key this means you have all 3 keys held in now press down arrow with the keys held on if not working press up arrow with all 3 other keys held on.You will 100% go to the recovery menu i guarentee that.
JOB DONE
VERY IMPORTANT NOTE:
If it doesn't work turn the console off at the wall and then leave a bit turn back on then repeat until it works keep doing that,it maybe the keyboard isn't picking up if you use reboot in comand or if your using a reboot tool to reboot it use the power for the mains to turn it off on not a reboot command,it needs to be done from a cold boot.
Re
H guys
Bad news for my mojo.
First of all, mad catz did the same thing as French_Dev (Salut à toi le français), they sent me the PHYSC-1 method to recover my mad catz.
After that i have retry the method with another keyboard, and i thought i recovered it coz i was able to see the android logo(robot screen broken), and recovery menu, but impossible to have access to data factory reset.
And now Ladies & Gentlemen...
I give my mojo to a friend who sometimes unblocks android phones, thinking he will find the way...
But he bring's me back the mojo now bricked, no blue logo at startup, and no access to fastboot mode with the male male usb cable.
He told me that he finds an another rom tu put on it, but after cleaning and flash it ===> bricked...
I can i confirm that the PHYSC-1 method work, but in my case i couldn't apply data/factory reset or maybie it's coz keyboards which i have.
Now i must find the way to unbrick it if it's possible. (i think it's possible for sure, linux based...)
Thanks for all your replies guys.
daves94 said:
H guys
Bad news for my mojo.
First of all, mad catz did the same thing as French_Dev (Salut à toi le français), they sent me the PHYSC-1 method to recover my mad catz.
After that i have retry the method with another keyboard, and i thought i recovered it coz i was able to see the android logo(robot screen broken), and recovery menu, but impossible to have access to data factory reset.
And now Ladies & Gentlemen...
I give my mojo to a friend who sometimes unblocks android phones, thinking he will find the way...
But he bring's me back the mojo now bricked, no blue logo at startup, and no access to fastboot mode with the male male usb cable.
He told me that he finds an another rom tu put on it, but after cleaning and flash it ===> bricked...
I can i confirm that the PHYSC-1 method work, but in my case i couldn't apply data/factory reset or maybie it's coz keyboards which i have.
Now i must find the way to unbrick it if it's possible. (i think it's possible for sure, linux based...)
Thanks for all your replies guys.
Click to expand...
Click to collapse
It would be bricked he's attempted some or should i probably say has likely flashed clockwork mod or some rom for eg.a samsung phone or nexus tablet etcetc.Which they don't work for any other tablet or phone because they are device specific,hence the need to flash only a zip file in recovery and only a zip file from mad catz not any other rom or backup is made for a m.o.j.o except the mad catz m.o.j.o 202 update zip file so nobody should try anything else like erase etc only flashing the provided update from mad catz at a guess it won't need previous cache erase or any other erase because the zip when inside the os seems to fromat it for you so should do the same in recovery mode in theory to.Try all over again to get to recovery with a usb stick plugged in somehow with the 202 update on if possible,i am of the 'assumption' that is how it is done with a usb stick in usb 3.0 port with the zip on it but not 100% i have never done it nor do i need to chance a rick of a working m.o.j.o mate? Really feel for you though it can't hurt to tinker with it some more though now can it?
OK sorry ,may have misread a bit there,so before giving it a mate you did flash the 202 update file yes/no?
Secondly if you did flash it it tried to boot logo the lot yes/no?
Thirdly you gave it a mate who [email protected] it up for you yes/no?
Sorry i see what you mean now,you don't erase you flash the zip 202 update zip job done mate that's all no erase no nothing else to do barr that i am guessing,but you need it on usb stick or think about this,if it was downloaded on the m.o.j.o prior this 202 update zip and you click update from zip in recovery menu,i think it may ask where giving you the choice to look for the file on what ever device it may be on including the console,so you may not need a usb stick?
Perseverance is the key if at 1st you don't succeed try try and try again trust me i have used that motto to my advantage many times it's the only thing i learned from school.
That's how i found that recovery menu,it's how i found my tv secret menu last night,it's how i found all necissary flash files for and flashed a haipi phone,how i flashed my mates bb 9820 curve etcetc,i never stop trying,i have recovered iphones before and that haipai when bricked etctc so you have nothing to loose in persistantly trying it again and again until you have found the way to flash it over with 202 update.zip
I always find ways to mod (hack) devices on my own from what i label as ethical hacking although it's not the real terminology but it sort of is in a way,i basically scour forums finding bits here and bits there puting them together to find the complete path to flashing something,i may resort to taking one sentance in a forum then another then another finaly i get the full guide and i flash it,so my view is it's a sort of ethical hacking it's diuling infromation to perform a hardware hack in an ethical way as modding a rom is legal 99.9% of the time.
It's how i managed to get pi****u on a k-r42android tv box and then upgrade it to ubuntu trusty tahr 14.04 by looking at ubuntu forum posts for commands to upgrade the installation,the reason was it's ubuntu on pi****u os so therefore it can be upgraded as is done in ubuntu.So the story goes where there is a will there is a way.
Hey there,
My LG D802 32GB just fall out of my car and the complete Display is bricked (I think Digitizer is also harmed) and I am not able to touch anywhere.
I know a lot about fastboot, adb and so on. But I do not really know much about this device, since I hadn't got the time to do so, too busy with other stuff. Unfortunately I disabled USB debugging a week ago after I finished some development stuff. And I just want to make a new backup (last one was a few weeks ago ) of my data before I try to repair anything or buy a new one.
I do not know why, but I cannot enter Stock Recovery (just keeps rebooting), Download Mode is working. Phone is also booting normally, just no way my fingers are recognized.
I tried to enter Recovery Mode (stock), to perhaps have adb access (don't know if it is so on d802), with Volume Down+Power, release when Logo appears and then press again, USB Cable was connected. I know i entered it once after buying this phone, but now I am not able to do so. Are there any special drivers which are perhaps missing (installed them with PC Suite, all upgrades were done with it, cause I do not like OTAs for several personal reasons).
Thank you very much for reading it and perhaps helping me!
just want to add something:
Also tried with LG Onscreen Phone, but also deactivated ...
Some recoveries can be used only with hard keys. Or use a mouse to navigate
Thank you for this great idea. Just ordered an OTG adapter.
What do you mean with hard keys? Volume Up/Down ?
akamarukiba said:
Thank you for this great idea. Just ordered an OTG adapter.
What do you mean with hard keys? Volume Up/Down ?
Click to expand...
Click to collapse
Yes exactly. I think cwm can Do this
Ok backup done... Could have thought about this simple option too...
Hey everyone!
Just a few days after ordering a different phone which should get here tomorrow, I managed to drop my N4 and shatter the screen. The screen 'works' but the digitizer's broken below the crack so I can't get past the lock screen. I'm running Cyanogen mod and I honestly just want to get a few files off and update a few things onto drive so I can move to my new phone.
I was really hoping USB OTG would work, but I tried an external mouse with the right cable and the cursor wasn't showing up.
I don't think I have debugging mode enabled unless it carries forward if you update cyanogen. I do have CWM recovery 6.0.5.1. I tried mounting the drives through this, but it sadly didn't show up.
Is there any way I can enable USB OTG or get the files off without replacing the screen assembly? I tried using ADK Studio but I couldn't even get the command prompt open... If anyone has a link to a good walkthrough for this or suggestions for what I can do I'd be really grateful. Is there any way to force the USB OTG driver onto the phone? If I can use a USB keyboard/mouse combo to get everything off that would be the simplest way I think. Or if there's some way to get into the phone and have the display show up through my monitor, then that'd be great too.
Thanks a lot. I really appreciate any help.
You could try flashing twrp in place of cwm to mount the data partition.
audit13 said:
You could try flashing twrp in place of cwm to mount the data partition.
Click to expand...
Click to collapse
I can hit mount and unmount through CWM but nothing seems to happen. Nexus shows up as an empty device.
How would i flash TWRP at this point? Is there a way to push a zip into the phone if I can't get into it?
ridethecliche247 said:
I can hit mount and unmount through CWM but nothing seems to happen. Nexus shows up as an empty device.
How would i flash TWRP at this point? Is there a way to push a zip into the phone if I can't get into it?
Click to expand...
Click to collapse
If your physical buttons work then simply boot into fastboot by holding volume down and power and flash a TWRP recovery via fastboot. I've never had luck with CWM when it comes to reading files. TWRP opens up Android File Transfer right away on my Macbook when I connect it (Should do the same for Windows, not sure what OS you use)
fireball0093 said:
If your physical buttons work then simply boot into fastboot by holding volume down and power and flash a TWRP recovery via fastboot. I've never had luck with CWM when it comes to reading files. TWRP opens up Android File Transfer right away on my Macbook when I connect it (Should do the same for Windows, not sure what OS you use)
Click to expand...
Click to collapse
This seems promising, but how would I get it in via fastboot? Sorry I've never used fastboot before, but use the power+vol down command pretty often.
Would that also allow me to flash in the zip for USB otg once I'm in?
ridethecliche247 said:
This seems promising, but how would I get it in via fastboot? Sorry I've never used fastboot before, but use the power+vol down command pretty often.
Would that also allow me to flash in the zip for USB otg once I'm in?
Click to expand...
Click to collapse
Ok, you will want to be on your computer to do this. Download the latest TWRP recovery, which is here, you'll want to download the twrp-3.0.0-0-mako.img at the top of the list. You'll then have to open up fastboot in terminal/command prompt, and when you boot into your bootloader by holding volume down+power, connect your N4 and first I would type fastboot devices to make sure that your computer is recognizing that it's attached. Next type fastboot flash recovery twrp-3.0.0-0-mako.img and afterwards use the volume buttons to navigate and reboot to recovery. From there see if it connects to your computer and you can view files and if not, move forward with the USB otg. I have no experience with USB otg so I can't help you there, but hopefully this helps out at the very least!
fireball0093 said:
Ok, you will want to be on your computer to do this. Download the latest TWRP recovery, which is here, you'll want to download the twrp-3.0.0-0-mako.img at the top of the list. You'll then have to open up fastboot in terminal/command prompt, and when you boot into your bootloader by holding volume down+power, connect your N4 and first I would type fastboot devices to make sure that your computer is recognizing that it's attached. Next type fastboot flash recovery twrp-3.0.0-0-mako.img and afterwards use the volume buttons to navigate and reboot to recovery. From there see if it connects to your computer and you can view files and if not, move forward with the USB otg. I have no experience with USB otg so I can't help you there, but hopefully this helps out at the very least!
Click to expand...
Click to collapse
Ive had issues in the past trying to get the terminal to open. Do you have a link that could help?
Thanks so much!
ridethecliche247 said:
Ive had issues in the past trying to get the terminal to open. Do you have a link that could help?
Thanks so much!
Click to expand...
Click to collapse
Do you use Windows, Linux, or OS X?
fireball0093 said:
Do you use Windows, Linux, or OS X?
Click to expand...
Click to collapse
Windows.
ridethecliche247 said:
Windows.
Click to expand...
Click to collapse
Take a watch through this entire video, it's the most in depth one I can find that actually gives examples on things dealing with ADB and of course Fastboot. Make sure that the recovery .img is in the same directory that the fastboot prompts are in. If I didn't use OS X I'd walk you through it myself but I apologize there because I know the setup and way you enter commands is slightly different on Windows xD
Thank you! I'll give it a try!
ridethecliche247 said:
Thank you! I'll give it a try!
Click to expand...
Click to collapse
Just quick popping in to see how the progress is on it. Any luck at all?
fireball0093 said:
Just quick popping in to see how the progress is on it. Any luck at all?
Click to expand...
Click to collapse
I have finals next week so I was going to give it a try afterwards or if I get a study break. I'll definitely keep you posted on this thread though.
Thanks again!
Hi guys,
i tried searching the forums, but i can seem to find a solution (if it exists) to my specific problem.
The story is that i had broken my touch screen to the point where only about 1,5 - 2 cm from above are working. I am stuck at the screen where i have to enter the password to decrypt and start android, but i can't press those buttons.
So, the question is: is there any possibility at all to access the data on the phone? Some way to externally control the phone? Would ADB work in this situation?
Thank you in advance for the help.
sadgsdg said:
Hi guys,
i tried searching the forums, but i can seem to find a solution (if it exists) to my specific problem.
The story is that i had broken my touch screen to the point where only about 1,5 - 2 cm from above are working. I am stuck at the screen where i have to enter the password to decrypt and start android, but i can't press those buttons.
So, the question is: is there any possibility at all to access the data on the phone? Some way to externally control the phone? Would ADB work in this situation?
Thank you in advance for the help.
Click to expand...
Click to collapse
Well, if you had a custom kernel flashed, using USB OTG and a mouse could help you get your stuff back.
i don't think i had a custom kernel, i didn't modify anything in the phone. It was not rooted.
So i was able to enter the menu from where i can choose recovery mode. Is there any way to proceed from here?
I tried to use ADB, but it won't see my phone, neither does fastboot. Maybe i didn't install Nexus 4 drivers, since windows told me that the device is not properly installed, when i connected it in recovery mode.
Hello I have a "a2017u" model, without a working touchscreen. I need to sent it in for a warranty repair. can anyone explain to me how to restore the device, currently it has twrp+lineage os. I CAN'T use the touchscreen, however you can see everything, only touch doesn't work. I really need help since this is my only phone and I'm borrowing one.
So where are you getting stuck?
I don't think you need to use the screen for anything.
lafester said:
So where are you getting stuck?
I don't think you need to use the screen for anything.
Click to expand...
Click to collapse
I tried to use axon 7 toolkit, I run the check under option one and get this message.
So I don't know what's happening
cato1986 said:
I tried to use axon 7 toolkit, I run the check under option one and get this message.
So I don't know what's happening
Click to expand...
Click to collapse
EDIT: Some guy gave me an awesome idea: Use an OTG adapter and a USB mouse on TWRP. From there you can install some zips, I don't know anything about A2017s but you can look for guides on how to get to stock (not mine though)
Right. If you have an SD card I think you can:
- find a stock recovery.img, use fastboot to install it to recovery (fastboot flash recovery yourfile.img)
- then wipe data/factory reset with the stock recovery
- install an official system zip with your sdcard
You have a Chinese version phone so I don't have any recovery zips for that, sorry. If you can, look for the recovery img and send the link of where you got it here.
Axon7toolkit is a little bit too hardcoded, it needs adb first, then from ADB it boots to fastboot, then from there it boots a twrp img...
Well that's a no go. Besides the fact it refuses to show the mouse. It just doesn't work. I did manage to get to the desktop. But parts of the digitizer work and then it goes crazy clicking things on its own.
Chinese version? Mines the American. Zte a2017u
cato1986 said:
Chinese version? Mines the American. Zte a2017u
Click to expand...
Click to collapse
Then why did you write A2017 in the title and the OP?? Change that
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
Okay there may be an easier way. Try putting your phone in FTM mode (while off, hold Vol down + power) and a message that says FTM mode should appear. Now try axon7toolkit.
Or, if you have an USB mouse and an OTG adapter, enable USB debugging and connect your phone to the PC. Then use axon7toolkit