NEW TWRP-3.2.3-0-scorpio(Mi note 2)
DOWNLOAD twrp-3.2.3-0-scorpio.img: https://dl.twrp.me/scorpio/twrp-3.2.3-0-scorpio.img
Regards
vcx77 said:
NEW TWRP-3.2.2-0-scorpio(Mi note 2)
DOWNLOAD twrp-3.2.2-0-scorpio.img: https://mega.nz/#!3BUkSSbT!r_okak_V21oNGpW7ArdiR2njcxR0VQtYOvY_b02xCu0
Regards
Click to expand...
Click to collapse
Why the hell should you put the mega link? Did you customized it? If not just give the official twrp link. Thx
https://dl.twrp.me/scorpio/
I can not install Android 8.0 Oreo with TWRP 3.2.2
After installing TWRP, Android is not restarted. It remains on the reset screen. How do I solve this problem?
NEW TWRP-3.2.3-0-scorpio(Mi note 2)
Alexurso said:
I can not install Android 8.0 Oreo with TWRP 3.2.2
After installing TWRP, Android is not restarted. It remains on the reset screen. How do I solve this problem?
Click to expand...
Click to collapse
Make sure you have flashed the correct oreo firmware first if coming from Nougat.
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
Tried to flash the new recovery but it wont load. Phone just powers off. How can i roll back on previous version? Do i need adb and commands? Feel a little naked without a recovery
Edit : looks like the twrp file downloaded was incomplete so recovery was wiped. Tried to download it tru official site on my phone but was getting incomplete files everytime. Downloaded and flashed tru official twrp android app.
how to install this twrp from hermes?
vcx77 said:
NEW TWRP-3.2.3-0-scorpio(Mi note 2)
Click to expand...
Click to collapse
I have same proble on my mi note 2 8.0
---------- Post added at 07:44 PM ---------- Previous post was at 07:36 PM ----------
hello sir , i have error or says : C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery.img "C:\XiaoMi\MiPhoneManager\Download\twrp-3.2.2-0-scorpio.img" target reported max download size of 536870912 bytes sending 'recovery.img' (25240 KB)... OKAY [ 0.560s] writing 'recovery.img'... FAILED (remote: partition table doesn't exist) finished. total time: 0.584s
rah_asia said:
Why the hell should you put the mega link? Did you customized it? If not just give the official twrp link. Thx
https://dl.twrp.me/scorpio/
Click to expand...
Click to collapse
Valko67 said:
I have same proble on my mi note 2 8.0
---------- Post added at 07:44 PM ---------- Previous post was at 07:36 PM ----------
hello sir , i have error or says : C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery.img "C:\XiaoMi\MiPhoneManager\Download\twrp-3.2.2-0-scorpio.img" target reported max download size of 536870912 bytes sending 'recovery.img' (25240 KB)... OKAY [ 0.560s] writing 'recovery.img'... FAILED (remote: partition table doesn't exist) finished. total time: 0.584s
Click to expand...
Click to collapse
have you unlock the bootloader? did the downloaded file corrupted?
Yes bootloader is unlock , yes it is possible i downloaded from corrupt file after problems om my computer i haves to clean up all the mess i did )) yes this could happened when your knowledge is just to less , hahahaha , no madder , i have my Mi Note i preferred to work with , much easier to , hate this MTK , never would take again , it is not that it aint good , but so complicated to me than the Qualcomm Version's i enjoy your few words dear rah_asia , many thanks for that ; wish you sweet day Sir
what about twrp-3.4.0-1??
Related
C:\Users\Jason\Downloads>moto-fastboot devices
TA20705TET fastboot
C:\Users\Jason\Downloads>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\Users\Jason\Downloads>moto-fastboot flash recovery recovery-green-atrix3.2.im
g
sending 'recovery' (4780 KB)... OKAY [ 0.498s]
writing 'recovery'... FAILED (remote: (00180002))
C:\Users\Jason\Downloads>
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Ok so I'm not sure why but it wouldnt let me type anymore on original post. Anyways, i am trying to flash using fastboot the atrix unlocked CWM. However when i type the commands i keep getting errors. Any ideas on what this is?
jason.hamilton said:
C:\Users\Jason\Downloads>moto-fastboot devices
TA20705TET fastboot
C:\Users\Jason\Downloads>moto-fastboot erase recovery
erasing 'recovery'... FAILED (remote: (00180001))
C:\Users\Jason\Downloads>moto-fastboot flash recovery recovery-green-atrix3.2.im
g
sending 'recovery' (4780 KB)... OKAY [ 0.498s]
writing 'recovery'... FAILED (remote: (00180002))
C:\Users\Jason\Downloads>
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Ok so I'm not sure why but it wouldnt let me type anymore on original post. Anyways, i am trying to flash using fastboot the atrix unlocked CWM. However when i type the commands i keep getting errors. Any ideas on what this is?
Click to expand...
Click to collapse
Did you find your solution because I'm stuck at the same thing. I had touch screen issues after flashing a ROM. So I RSD back to stock but the touch screen problem persist. I read of the PDS fix in a post and I'm getting the same error but with trying to erase/write my PDS backup to the phone.
Make sure you put the image you are trying to flash in the same folder as your fastboot.
Vangelis13 said:
Make sure you put the image you are trying to flash in the same folder as your fastboot.
Click to expand...
Click to collapse
OP said it fails when trying to erase as well. So it's not file placement issues.
Speedily sent from CM7 Beta
Having same problem here... any solution?
why not just flash the one from rom manager then flash the zip to the one you want through that. thats what i did works perfect!
C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. I also get the android laying down with a red exclamation point while in recovery mode. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Which directory is your recovery located. It needs to be in your adb folder. And what version of Android are you on? If you're on MM then Fastboot commands will not work. But if you're on LP it should still work.
---------- Post added at 11:02 PM ---------- Previous post was at 10:58 PM ----------
-Atlas__ said:
C:\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (31748 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 1.076s
C:\Android\sdk\platform-tools>fastboot flashing unlock ...
(bootloader) Device already : unlocked!
OKAY [ 0.012s]
finished. total time: 0.013s
I have both oem unlock and usb debugging checked on the developer options plus i was able to unlock the devices oem through fastboot. I opened the command prompt in androids/sdk/platform tools but nothing happens just repeats recovery failed. I also get the android laying down with a red exclamation point while in recovery mode. What am I doing wrong? (My goal is to download twrp onto my lg V10)
Click to expand...
Click to collapse
..
I have been Having the same problem
I recently updated my H901 to MM and have been receiving this error every time. I have attempted this on multiple computers that have been used to successfully root the phone before on LP. I am convinced this is a phone issue related to MM.
None of the root guides available online seem to address this type of problem.
is there a new process for MM?
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
spencercnorton2012 said:
I recently updated my H901 to MM and have been receiving this error every time. I have attempted this on multiple computers that have been used to successfully root the phone before on LP. I am convinced this is a phone issue related to MM.
None of the root guides available online seem to address this type of problem.
is there a new process for MM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-v10/help/how-root-lg-v10-android-6-0-rooted-t3346387
spencercnorton2012 said:
I recently updated my H901 to MM and have been receiving this error every time. I have attempted this on multiple computers that have been used to successfully root the phone before on LP. I am convinced this is a phone issue related to MM.
None of the root guides available online seem to address this type of problem.
is there a new process for MM?
---------- Post added at 04:13 PM ---------- Previous post was at 04:09 PM ----------
http://forum.xda-developers.com/lg-v10/help/how-root-lg-v10-android-6-0-rooted-t3346387
Click to expand...
Click to collapse
Fastboot commands are blocked onthe MM update. therefore no recovery can be flashed atm.
This worked for me
Hi. Im a newbie, so I can't post links yet, but I was having the same error, but I found a method that worked for me. It began:
HOW TO ROOT LG V10 T-MOBILE H901 RUNNING ANDROID 6.0 MARSHMALLOW
Download the KDZ ROM and save it to your desktop.
Download the TOT TWRP file and save it to your desktop.
Download the LGUP tool and save it to the desktop.
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Click to expand...
Click to collapse
U are mistaken , issue is u do installed Cm13 over b418 or b420++ ..
If iam right ur device wasn't bricked .I can help u here .raise the discussion with your thoughts and I will end it up with success
Sent from my KIW-L22 using Tapatalk
if u still can recognize the phone with fast-boot then u can go back to stock ( only latest to get match build version or upgraded one ) downgraded build will fail .
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
Click to expand...
Click to collapse
Havnt u made a twrp backup ?
Sent from my KIW-L22 using Tapatalk
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
Click to expand...
Click to collapse
When the twrp boots up, let the phone alone until the screen turns off. Press power and see if it starts working.
This usually does the trick for me.
muradulislam said:
When the twrp boots up, let the phone alone until the screen turns off. Press power and see if it starts working.
This usually does the trick for me.
Click to expand...
Click to collapse
Oh wait . I had the solution
Sent from my KIW-L22 using Tapatalk
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
hrstoyanov said:
Hello everyone!
I tried to install CM13 nightly on my brand new Honor 5X. Followed the process, installed TWRP 3.0.2 bootloader and then the CM13 and Google Apps zips. When I booted the phone I saw the blue face for CM, but the phone never booted and kept rebooting! I tried to launch in TRWP recovery mode, but the swipe is locked and I can not go back to the install menu. TWRP is completely unresponsive no matter how i swipe or press the volume/power button. Why is TWRP like that?
Model: KIW-UL00
Click to expand...
Click to collapse
I think am the only one who can solve ur issue .. If u are online now , quote me. I will help u for sure .trust me ur touch screen works in recovery after doing what I said
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
Oh wait . I had the solution
Sent from my KIW-L22 using Tapatalk
---------- Post added at 07:48 PM ---------- Previous post was at 07:47 PM ----------
I think am the only one who can solve ur issue .. If u are online now , quote me. I will help u for sure .trust me ur touch screen works in recovery after doing what I said
Click to expand...
Click to collapse
Be civil and stop doing that please...
muradulislam said:
Be civil and stop doing that please...
Click to expand...
Click to collapse
Ohh .. I was just saying ! Don't take it soo serious .
Sent from my KIW-L22 using Tapatalk
---------- Post added at 08:02 PM ---------- Previous post was at 07:56 PM ----------
muradulislam said:
Be civil and stop doing that please...
Click to expand...
Click to collapse
I had faced this multiple times . I used get a jerk in my body if touch dint won't on twrp . almost phone in dead state and we still had to ability to access fastboot but twrp never work and even other recoveries .
So my solution is just soo easy .
Twrp touch failure is caused due to the kernal in Cyanogenmod .
So , just flash the stock boot.IMG and tadaaa .
Reboot to twrp and that's it .
And I may not be the only one ,but am just boosting the OP's anxiety and confidence levels making him aware that his phone is still alive .
Take it easy my frn . Am not a god to know everything , and I always try to live civil.thanks for your advice and I will take it sportive .
And +1 for you
gopinaidu77 said:
Ohh .. I was just saying ! Don't take it soo serious .
Click to expand...
Click to collapse
Well, what can I say, you said it and I did take it seriously but let's forget all that.
And the trick I said, I used it with honor 6 and 7 and it worked, we are all here to help so I tried that too.
muradulislam said:
Well, what can I say, you said it and I did take it seriously but let's forget all that.
And the trick I said, I used it with honor 6 and 7 and it worked, we are all here to help so I tried that too.
Click to expand...
Click to collapse
But that thing dint work on 5x . if that do , I could have kept silent with your post . but your answer is obvious .thanks
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
But that thing dint work on 5x . if that do , I could have kept silent with your post . but your answer is obvious .thanks
Click to expand...
Click to collapse
Then just point it out to me straight using the words "You are wrong" with the explanation, why do you think so...
It will make me learn that my approach is wrong and will make me learn something new.
Using a direct and honest approach is much better than a sarcastic one. IMHO.
muradulislam said:
Then just point it out to me straight using the words "You are wrong" with the explanation, why do you think so...
It will make me learn that my approach is wrong and will make me learn something new.
Using a direct and honest approach is much better than a sarcastic one. IMHO.
Click to expand...
Click to collapse
Ha ha , well said . I would have done that ! But when I said that , I dint pointed u actually . still thanks for your great words . will remember till I last in xda
gopinaidu77 said:
But that thing dint work on 5x . if that do , I could have kept silent with your post . but your answer is obvious .thanks
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
Guys,
Thanks, I will keep trying with your recommendations, here is where I left yesterday:
My issue is that TWRP does not recognize any touch event and I cannot swipe to unlock it and go to the menus. Not sure how it happened, but it used to work initially.
Out of desperation, I downloaded the US stock firmware from Huawei, placed the UPADTE.APPP under /sdcard/dload/update.zip
When I boot now (power+ volume up) I see a circle EMUI initial screen and some menus in Chinese (which I don't understand). With the volume, I am able to switch to the next menu where it discovers all wireless networks around me. But, I cannot select mine network with touching the screen, and the EMUI recovery does not work with the volume.
At this point my concern is that somehow I broke the phone as it is not responding to screen touch events. Could that be the reason why I cannot unlock TWRP?
I can install CM13 recovery image or TWRP any time, but that's about it - I cannot run CM13 (rebooted all the time and now TWRP is toast) or put back the stock firmware (blocked swipe on the screen items).
hrstoyanov said:
Guys,
Thanks, I will keep trying with your recommendations, here is where I left yesterday:
My issue is that TWRP does not recognize any touch event and I cannot swipe to unlock it and go to the menus. Not sure how it happened, but it used to work initially.
Out of desperation, I downloaded the US stock firmware from Huawei, placed the UPADTE.APPP under /sdcard/dload/update.zip
When I boot now (power+ volume up) I see a circle EMUI initial screen and some menus in Chinese (which I don't understand). With the volume, I am able to switch to the next menu where it discovers all wireless networks around me. But, I cannot select mine network as with touching the screen, and the EMUI recovery does not work with the volume.
At this point my concern is that somehow I broke the phone as it is not responding to screen touch events. Could that be the reason why I cannot unlock TWRP?
I can install CM13 recovery image or TWRP at will, but that's about it - i cannot run CM13 (reboots all the time) or put back the stock firmware (blocked swipe)
Click to expand...
Click to collapse
If u have twrp backup ..
Open the backup
Rename boot.ext4.win to boot.img
(U can also extract any marshmallow boot.IMG from update.app)
Put it in fastboot folder
Then put ur phone in fastboot mode
Type this command
Fastboot flash boot boot.img
Later type this command .
Fastboot reboot
And come back up to recovery.
Tada. It will work now.
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
If u have twrp backup ..
Open the backup
Rename boot.ext4.win to boot.img
(U can also extract any marshmallow boot.IMG from update.app)
Put it in fastboot folder
Then put ur phone in fastboot mode
Type this command
Fastboot flash boot boot.img
Later type this command .
Fastboot reboot
And come back up to recovery.
Tada. It will work now.
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
he says that touch is not working with TWRP .
Romiui said:
he says that touch is not working with TWRP .
Click to expand...
Click to collapse
Yes .. The solution is for that
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
If u have twrp backup ..
Open the backup
Rename boot.ext4.win to boot.img
(U can also extract any marshmallow boot.IMG from update.app)
Put it in fastboot folder
Then put ur phone in fastboot mode
Type this command
Fastboot flash boot boot.img
Later type this command .
Fastboot reboot
And come back up to recovery.
Tada. It will work now.
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
...Tried to follow your instructions, but no luck
1. I don't have TWRP backup. So, I downloaded the latest HUAWEI Honor 5x stock: (KIW-L24, Android 6.0.1,EMUI 4.0,C567D003,United States)
2. Extracted UPDATE.APP first, and then extracted boot.IMG from it.
3. Deployed the boot.img:
? platform-tools ./fastboot flash boot ~/Downloads/BOOT.img
target reported max download size of 266338304 bytes
sending 'boot' (44266 KB)...
OKAY [ 1.407s]
writing 'boot'...
OKAY [ 0.698s]
finished. total time: 2.105s
4. Deployed TWRP recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.438s]
writing 'recovery'...
OKAY [ 0.713s]
finished. total time: 2.151s
5. Rebooted the phone - it keeps rebooting endlessly :
? platform-tools ./fastboot reboot
rebooting...
finished. total time: 0.002s
5. Reboot the phone in recovery mode (power+Vol Up+Vol Down)
TWRP comes with the lock on the screen. No touch events, swipe as before. Dead as a door nail again!
6. Desperate, I also tried to deploy the CM13 recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/cm-13.0-20161216-NIGHTLY-kiwi-recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (48114 KB)...
OKAY [ 1.517s]
writing 'recovery'...
OKAY [ 0.751s]
finished. total time: 2.268s
This works - I am able to boot in CM recovery now, but the CM recovery tools is pretty useless and limited. Well, at least it does not rely on the touch screen and one can access the items ...
... So I am even more frustrated now with the whole experience. This process was not supposed to be such a descent into a black hole .
My thinking is that my Honor 5x lost its touch screen permanently due to this CM endeavors.
Also, is there any problem that it is a Chinese model (KIW-UL00) and I used US stock image in step 1 ?
Any other ideas?
i can say that u flashed US version which might have wrong display driver ! .. u need to go back to the stock as same what came with the phone
use full software dload or flash it throw fastboot after extracting update.app .
this link might help u . just make account and download the latest update .
Honor 5X KIW-UL00 - B239
hrstoyanov said:
...Tried to follow your instructions, but no luck
1. I don't have TWRP backup. So, I downloaded the latest HUAWEI Honor 5x stock: (KIW-L24, Android 6.0.1,EMUI 4.0,C567D003,United States)
2. Extracted UPDATE.APP first, and then extracted boot.IMG from it.
3. Deployed the boot.img:
? platform-tools ./fastboot flash boot ~/Downloads/BOOT.img
target reported max download size of 266338304 bytes
sending 'boot' (44266 KB)...
OKAY [ 1.407s]
writing 'boot'...
OKAY [ 0.698s]
finished. total time: 2.105s
4. Deployed TWRP recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.438s]
writing 'recovery'...
OKAY [ 0.713s]
finished. total time: 2.151s
5. Rebooted the phone - it keeps rebooting endlessly :
? platform-tools ./fastboot reboot
rebooting...
finished. total time: 0.002s
5. Reboot the phone in recovery mode (power+Vol Up+Vol Down)
TWRP comes with the lock on the screen. No touch events, swipe as before. Dead as a door nail again!
6. Desperate, I also tried to deploy the CM13 recovery:
? platform-tools ./fastboot flash recovery ~/Downloads/cm-13.0-20161216-NIGHTLY-kiwi-recovery.img
target reported max download size of 266338304 bytes
sending 'recovery' (48114 KB)...
OKAY [ 1.517s]
writing 'recovery'...
OKAY [ 0.751s]
finished. total time: 2.268s
This works - I am able to boot in CM recovery now, but the CM recovery tools is pretty useless and limited. Well, at least it does not rely on the touch screen and one can access the items ...
... So I am even more frustrated now with the whole experience. This process was not supposed to be such a descent into a black hole .
My thinking is that my Honor 5x lost its touch screen permanently due to this CM endeavors.
Also, is there any problem that it is a Chinese model (KIW-UL00) and I used US stock image in step 1 ?
Any other ideas?
Click to expand...
Click to collapse
Bro , please flash boot.img of stock ROM in boot partition n
And keep twrp in recovery partition and reboot to recovery will fix
Don't flash cm recovery .
Do this way.
Flash stock ROM boot.img in to boot partition first .
Now reboot to recovery . touch will work then
gopinaidu77 said:
Bro , please flash boot.img of stock ROM in boot partition n
And keep twrp in recovery partition and reboot to recovery will fix
Don't flash cm recovery .
Do this way.
Flash stock ROM boot.img in to boot partition first .
Now reboot to recovery . touch will work then
Click to expand...
Click to collapse
... but this is exactly what I did? And after rebooting nothing improves!
➜ platform-tools ./fastboot flash boot ~/Downloads/BOOT.img
target reported max download size of 266338304 bytes
sending 'boot' (44266 KB)...
OKAY [ 1.393s]
writing 'boot'...
OKAY [ 0.690s]
finished. total time: 2.082s
➜ platform-tools ./fastboot flash recovery ~/Downloads/twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.429s]
writing 'recovery'...
OKAY [ 0.710s]
finished. total time: 2.139s
Thread Closed
Thread Closed
Dude, this may work on the xt1772??
If no, you can port to it??
If you need something like the boot image, i can give upload one
Sorry for my english
hetor99 said:
Dude, this may work on the xt1772??
If no, you can port to it??
If you need something like the boot image, i can give upload one
Sorry for my english
Click to expand...
Click to collapse
No, its not working in XT1772.
Please upload your device recovery image & boot image here.
Francesco Franz said:
No, its not working in XT1772.
Please upload your device recovery image & boot image here.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1jbSjLAMabwDar9tcc_VCSlPCNFVizWt1/view?usp=drivesdk
https://drive.google.com/file/d/1tKGXsT4qSkSoXj17Ur-QsdgsGtl1Fz_Q/view?usp=drivesdk
hetor99 said:
https://drive.google.com/file/d/1jbSjLAMabwDar9tcc_VCSlPCNFVizWt1/view?usp=drivesdk
https://drive.google.com/file/d/1tKGXsT4qSkSoXj17Ur-QsdgsGtl1Fz_Q/view?usp=drivesdk
Click to expand...
Click to collapse
Wait, until i upload a test version of twrp here?
After installing stock rom,i m not getting any info(shows null) on SKU in fast boot mode.please help
RagChith said:
After installing stock rom,i m not getting any info(shows null) on SKU in fast boot mode.please help
Click to expand...
Click to collapse
Me too, my device is the xt1772 and as you said, on the bootloader doesn't show any info, sku, model, imei and some other info, but the device is working well when it boot
---------- Post added at 06:47 PM ---------- Previous post was at 06:11 PM ----------
Francesco Franz said:
Wait, until i upload a test version of twrp here?
Click to expand...
Click to collapse
Sure guy, i will wait
@hetor99
You have to wait till this sunday.
Francesco Franz said:
@hetor99
You have to wait till this sunday.
Click to expand...
Click to collapse
It's fine dude, take your time
Im working on build LOS 14.1 for the mediatek variant, but i dont know how to build twrp
hetor99 said:
Me too, my device is the xt1772 and as you said, on the bootloader doesn't show any info, sku, model, imei and some other info, but the device is working well when it boot
Click to expand...
Click to collapse
Don't worry about it, it is kind of normal behavior in the fastboot mode
Sent from my Nexus 7 using Tapatalk
sir ............ can we flash using SP flash tool
rsmani1965 said:
sir ............ can we flash using SP flash tool
Click to expand...
Click to collapse
Yes, you can. But only when you have a working scatter file else use fastboot method.
#UPDATE
Click Here For TWRP Recovery For Moto E4 Plus XT1772 MediaTek Variant !
@Francesco Franz
Well, i think that the recovery is working fine, i tried the functios of wiping partitions like a factory reset and works, it detects the adoptable storage, the unique "bug" is when the recovery boot and stuck on black screen like on other variants.
I tried to take sc from all the options but i dont understand the lenguage that have the recovery pre-selected.
sorry for my english and any misunderstood
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Recovery mode is still the same No command with the dude on his back
DrunkenPanda2000 said:
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Boot to Recovery mode is still the same No command with the dude on his back
EDIT:
Apearantly i have a model 1762 And not 1772 Annyne got anny tips on how t proceed is this a fulitele task or will someone be a hero once again?
Click to expand...
Click to collapse
DrunkenPanda2000 said:
DrunkenPanda2000 said:
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Boot to Recovery mode is still the same No command with the dude on his back
EDIT:
Apearantly i have a model 1762 And not 1772 Annyne got anny tips on how t proceed is this a fulitele task or will someone be a hero once again?
Click to expand...
Click to collapse
Already mentioned its for xt1772 not xt1762.
Upload your device recovery and boot image. i will make one for you.
Click to expand...
Click to collapse
hetor99 said:
@Francesco Franz
Well, i think that the recovery is working fine, i tried the functios of wiping partitions like a factory reset and works, it detects the adoptable storage, the unique "bug" is when the recovery boot and stuck on black screen like on other variants.
I tried to take sc from all the options but i dont understand the lenguage that have the recovery pre-selected.
sorry for my english and any misunderstood
Click to expand...
Click to collapse
Its not a bug anymore since it takes few secs to enter into recovery mode. Black screen issue not at all. since you have a working twrp in your device. if theirs a black screen issue you will be on default recovery.
will fix the language bug soon.
@DrunkenPanda2000
That is because this section of xda is for the moto e4 plus, not the e4
the moto e4 already have twrp and to many roms on development
Hi there,
New here so thanks in advance for any help you guys could provide.
I need to root my Honor 9 for Android Development purposes so I tried to unlock the bootloader to install a TWRP.
(following this thread : https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110)
When it comes to the "adb reboot recovery_ramdisk", it loads to that error message :
Error Mode
Attention!
Please update system again
Error!
Func no: 11 recovery image
Error no: 2 (load failed!)
Any clues of what i'm doing wrong and how I can get rid of that error message...?
(The goral is to root the phone using that Magisk thing everyone's talking about )
Thanks a lot!
still need help ?
oslo83 said:
still need help ?
Click to expand...
Click to collapse
Hi Oslo83!
Yup, still need help. I don't understand what i'have done wrong :/
Phone is still booting in normal mode ?
You got this error screen only when bootinng to recovery ?
Do you still have access ro bootloader ?
---------- Post added at 12:09 ---------- Previous post was at 12:09 ----------
-ro +to
phone is still booting, no probs with that, and I still have access to bootloader yup.
i get the error message when i boot into recovery with adb reboot recovery_ramdisk
if i boot into nrecovery by pressing the buttons, i have the default honor recovery appearing.
What firmware version and region are you on ?
8.0.0.xxx (Cyyy) ?
Recovery mode is 'recovery_ramdisk'...
You should boot in twrp 0.3 when booting into recovery, as you flashed it, if you typed the right command...
recovery and erecovery are 2 differents mode on differents partition.
oslo83 said:
What firmware version and region are you on ?
8.0.0.xxx (Cyyy) ?
Recovery mode is 'recovery_ramdisk'...
You should boot in twrp 0.3 when booting into recovery, as you flashed it, if you typed the right command...
recovery and erecovery are 2 differents mode on differents partition.
Click to expand...
Click to collapse
Version : 8.0.0.364
Region: C432
Well, as i said, i followed the thread step by step and yet, still no twrp.
Thing is, if I want to flash it again with adb (in case of something went wrong during flash?), well, i get a "FAILED" error
it wont flash with adb, but with fastboot it will...
I really think you messed the command you previously typed. Can you post them ?
You'll have to
Code:
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
again then to boot to recovery mode.
---------- Post added at 12:57 ---------- Previous post was at 12:56 ----------
Fant0hm said:
well, i get a "FAILED" error
Click to expand...
Click to collapse
Post the whole error output...
well, first, i connect the phone with usb debug and OEM enabled.
i do
Code:
adb reboot bootloader
wich give me the "fastboot&rescue mode" with phone unlocked and FRP unlock in red
then i do
Code:
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
and it tells me :
Code:
target didn't report max-dowload-size
sending 'recovery_ramdisk' (0KB)...
FAILED (command write failed 'No error))
finished. total time : 0.016s
You're stf-twrp-zxz-0.3.img is wrong or not i' your working folder. Download it again.
---------- Post added at 13:45 ---------- Previous post was at 13:45 ----------
-you're +your -i' +in
Oh! it worked!
Problem apparently wasn't the .img but the "Minimal adb and fastboot"
I downloaded sdk platform tools on my home personnal computer and managed to install twrp (plus, buttons and flash work correctly, yay!)
So, problem solved i guess.
Thanks a lot for your time, Oslo!
I'm using Minimal adb and fastboot without any problem.
oslo83 said:
I'm using Minimal adb and fastboot without any problem.
Click to expand...
Click to collapse
well, i don't know what else it could be. used the same files, the same commands...