Related
Boots into recovery every time. Tried cwm restore to earlier backup with no luck
Sent from my DROIDX using XDA App
reflashed gtabcomb. still boots to recevoery. does this mean nvflash time?
joshtb86 said:
reflashed gtabcomb. still boots to recevoery. does this mean nvflash time?
Click to expand...
Click to collapse
Try wiping the "misc" partition while in CWM: Boot the gTab into recovery mode, connect the USB cable to it and run adb on the PC:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Edit: Or, use the attached zip file to erase "misc". Just "install" the zip file as usual using CWM.
Edit2: As to why this "always boots into recovery" happens, see this post.
rajeevvp said:
Try wiping the "misc" partition while in CWM:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Click to expand...
Click to collapse
already reflashed. but will try that next time! thanks!
rajeevvp said:
Try wiping the "misc" partition while in CWM:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Click to expand...
Click to collapse
rajeevvp your are magical man!
Everytime I get in trouble I search for a solution and find, that you already solved it :-D
Same here.
After moving to BL 1.2 I used "reboot recovery" in advanced menu of CWM and got into boot loop.
I tried nvflashing new boot.img and also recovery.img, but in vain.
Erasing misc partition magically helped ;-)
THANKS!
johny.mnemonic said:
I tried nvflashing new boot.img and also recovery.img, but in vain.
Erasing misc partition magically helped ;-)
Click to expand...
Click to collapse
It isn't magic--just details gleaned from reading the CWM code. If it were magic, it would be mysterious, and therefore, less interesting, wouldn't it?
The misc partition is used for communication between the ROM/kernel, the bootloader, and CWM; and if the tablet is going into recovery mode everytime, then logically, wiping misc should fix things. However, I couldn't test this scenario on my gTab because of my switched misc/bootbmp partitions: if I select "Reboot Recovery", CWM would just erase my (first) boot splash screen instead of going into a boot loop.
The various other versions of CWM have these minor sorts of bugs and irritations. The recently posted CWM-4.0.1.5 is the least annoying and it is what I will be using from now on. It a) understands my switched misc/bootbmp partition, b) "Reboots Recovery" w/o boot loops, and c) does USB mounts correctly.
Thanks for telling me that the technique worked. I've suggested it on other threads, but, this is the first time a user has told me that it fixed their problem. Most often users will just use nvflash--unnecessarily, and superstitiously--instead of waiting for the correct solution.
Im having the same problem, stuck in Clockwork. I dont see any option to 'wipe Misc partition. I also can't find a command line where I could enter the command 'C:\> adb shell erase_image misc'.
How do I wipe out that partition from Clockwork?
adb quick install
rajeevvp said:
Try wiping the "misc" partition while in CWM: Boot the gTab into recovery mode, connect the USB cable to it and run adb on the PC:
Code:
C:\> [B]adb shell erase_image misc[/B]
(You may have to wipe the "bootbmp" partition, instead, on some gTabs, because those 2 partitions have switched places on them.)
Click to expand...
Click to collapse
This is FANTASTIC! It absolutely fixes the CWM loop - and it is simple! (Once you have ADB working on your computer.)
I thought that I had read somewhere (but I cannot find it now) that you only needed ADB and FASTBOOT to run simple ADB commands. Is there a SIMPLE install for ADB? For Windows & for Linux. That would be even more fantastic!
I would like to provide that to my readers who accidentally do the "reboot to recovery" when them really mean "reboot system now." That simple error is what causes the CWM loop.
raywaldo said:
I thought that I had read somewhere (but I cannot find it now) that you only needed ADB and FASTBOOT to run simple ADB commands.
Click to expand...
Click to collapse
FASTBOOT does not apply to the gTab which uses a different, and proprietary, bootloader. To run ADB commands you just need the adb binary and its (standard) libraries.
Is there a SIMPLE install for ADB? For Windows & for Linux. That would be even more fantastic!
Click to expand...
Click to collapse
As I mentioned above, on Linux, you just need the adb binary. You don't have to install the entire Android SDK. I don't use Windows, so I don't know much about ADB there, but, I suspect that even there you would only need the exe file, its libraries and the Google/VS(?) USB driver.
EDIT: adb installed, but not configured with the USB driver before stuck in my CWM bootloop and adb never recognizes the tablet, whether its in cwm, mounted or in apx mode. does anyone have any suggestions?
any suggestions?
i think i need to nvflash. unabvle to get drivers installed since my device wont boot, so cant configure adb to work correctly
Im running into this as well. I got the Android SDK installed but ADB says that no devices are attached. Windows recognizes the Tegra 2 device when its mounted fine. It appears to be using the microsoft driver though. I attempted to change to the "android_winusb.inf" driver, but it wouldnt let me install/change it. I am running Windows 7 64bit if that matters in regards to the driver.
Try nvflash if you're having problems with adb.
Thanks. nvflash says no usb device found though. I tried it with and without 'mount usb storage'.
Coldfirex said:
Thanks. nvflash says no usb device found though. I tried it with and without 'mount usb storage'.
Click to expand...
Click to collapse
Try the CWM-flashable zip file in post #3 of this thread.
That worked great, thanks!!!
This fix worked great! Much better than nvflashing and reinstalling everything.
Thanks.
Thanks!!!, fix thanks to this magical command.
rajeevvp said:
Try the CWM-flashable zip file in post #3 of this thread.
Click to expand...
Click to collapse
I could really use a little more direction on this... I've finally gained access to mt tablet bymounting the USB storage command in CWM. I have this zip file on my desktop, not sure what to do from there...
Pleaase help!
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Thanks for the thought but you don't need to credit me here
You should mention that running "fastboot format userdata" wipes the entire phone including pics/vids, texts, etc. Someone will run this command ignorantly.
Sent from my Nexus 5X using Tapatalk
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
chucky8 said:
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
Click to expand...
Click to collapse
First off. TWRP couldn't decrypt N right now, so to overcome this, we decrypt the device.
Forced encryption is implemented through the kernel. The modified boot image disables that. So now upon booting, your device shall not be encrypted.
As for the future, you will have to do the same and flash the corresponding modified boot.img, when it comes out.
How do i know if my nexus is decrypted or not ?
ariefabuzaky said:
How do i know if my nexus is decrypted or not ?
Click to expand...
Click to collapse
If you don't know, then you are Encrypted. Look under Settings/Security/Encryption. It will either read "Encrypted" which is obvious or "Encrypt Phone" which means you are decrypted.
Sent from my Nexus 5X using Tapatalk
You don't have to decrypt. You can just push things you wanna flash to /tmp instead of decrypting data
farshad525hou said:
You don't have to decrypt. You can just push things you wanna flash to /to instead of decrypting data
Click to expand...
Click to collapse
Exactly. But then again, it is all about personal preference. I personally don't like connecting any external device to flash anything. Too slow to first download the files, then push 'em up to the HDD or Pen drive and then connecting it to the device to flash. I believe there are more users here, just like me.
For those who would need to decrypt, this is aptly the right process to begin with. Appreciations to @hackarchive for making this thread. Over at the three N based threads, I see several people asking about the decryption process, and this thread would definitely help the newcomers to get their foot in the right direction.
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
lbcary said:
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
Click to expand...
Click to collapse
NM, read that as flash userdata ...
Sent from my Nexus 6P using Tapatalk
I just did this and it worked but now I rebooted to TWRP to flash suhide, all I did was to swipe right on the warning twrp gives at the start and flash suhide, now I'm stuck at the splash screen again
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Sent from my ONEPLUS A3003 using Tapatalk
shamps said:
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Click to expand...
Click to collapse
Doesn't work that way.
The Fix is not needed anymore, newest TWRP is able to decrypt your phones storage. Only use newest twrp.
hackarchive said:
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Click to expand...
Click to collapse
Dude you saved my ass. My phone would not show correct battery % reading and I decided to drain it completely. Then my phone got stuck in bootloop and recovery stuck on splash screen. I am really lucky I found out your post.
Tysm.
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?
100% working TWRP recovery.. my first port but everything works amazing
Thank You Sir!
Edit - Flashed and works good so far; boots anyway; ill test more and repost in awhile
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
svoc said:
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
Click to expand...
Click to collapse
Is this the only missing feature, R/W capabilities for all device partitions or only for a few of them?
I'm assuming you are referring to a permanent setting to allow R/W permissions for /system and not an all encompassing problem of this TWRP image lacking that? In other words, nandroid backups are working?
No rw anywhere not even in Android or twrp but everything else works of this twrp it can be flashed to the device too
No but there's a thread in here with an app called super repack and you'll actually have to hook it up to a computer for this one but it works and it unpacks and repacks your super partition on the Android just follow the directions.. and I have an updated recovery file because the old one the fastboot didn't work
My system product and vendor is RW capable now.. so don't tell me it can't be done
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
That is the link to the super repack thread
tbirdguy said:
Thank You Sir!
Edit - Flashed and works good so far; boots anyway; ill test more and repost in awhile
Click to expand...
Click to collapse
You might want to download the updated image I uploaded.. the fast boot works on this one.. it's hell learning how to get fast boot and MTP to work when you are teaching yourself
svoc said:
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
Click to expand...
Click to collapse
mario0318 said:
Is this the only missing feature, R/W capabilities for all device partitions or only for a few of them?
I'm assuming you are referring to a permanent setting to allow R/W permissions for /system and not an all encompassing problem of this TWRP image lacking that? In other words, nandroid backups are working?
Click to expand...
Click to collapse
svoc said:
No rw anywhere not even in Android or twrp but everything else works of this twrp it can be flashed to the device too
Click to expand...
Click to collapse
svoc said:
Flashed it to device and it works use gravity box to get advance power menu but everything is working just need to get read write in it would be nice any ideas been trying
Click to expand...
Click to collapse
Look at the time on the picture if you think I'm lying
Ok I can get it to work but my device will not boot after words but it has rw in twrp and if I just do product I loose all settings and your new twrp adb is not working and if you try to bring a back up over 4gb it fails
Can you tell me what steps you took to get it done I have tried over 10 times having to reflash each time
are you able to share the source so I can attempt to build this for g10/capri?
Hi bro, thanks for your help porting TWRP, I've flashed the recovery succesfully but the touchscreen doesn't work, so I can't type anything on the screen.
I used this code to flash the recovery on fastboot mode:
Code:
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
fastboot reboot recovery
When the recovery starts, I get stuck on the password screen.
rogjr1986 said:
100% working TWRP recovery.. my first port but everything works amazing
Click to expand...
Click to collapse
how do i install it
All right so you download your recovery hook your phone up to the computer in fastboot mode and open up your command prompt on your computer you should have ADB and fastboot installed type into the command prompts fastboot flash recovery name.img
Do I need to unlock bootloader?
I am getting
target reported max download size of 798511104 bytes
sending 'recovery_a' (35428 KB)...
OKAY [ 0.836s]
writing 'recovery_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.922s