Hi I am quite new to this but I have gone through every tutorial I can find and cannot get TWRP on my Le Max 2. I start with the standard recovery screen.
I type the command ADB DEVICES and it returns a device number says ok
I put my phone into fastboot mode by pressing POWER/VOL - together and get the fastboot screen in chinese and english.
I type FASTOOT DEVICES and it returns the same device number
then FASTBOOT OEM UNLOCK - comes back already unlocked
then FASTBOOT FLASH RECOVERY X820_TWRP_3.0.2.IMG - it goes and does what it needs to says WRITING RECOVERY and says all ok no error messages on OK's
then FASTBOOT REBOOT to reboot phone. I have also tried just rebooting stright to recovery after flashing holding POWER/VOL+ and after 2-3 mins screen goeas black and the little signal LED goes BLUE I have to hold POWER buton for 15secs to reboot phone.
After that it still just boots into stock recovery screen.
Please any help. I also wonder where it is flashing the update coz i says it works but doesnt.
The X820 recovery of Chinese model is not compatible with our Indian X821 model. I tried and get the same black screen with Blue LED problem. You are not alone. We just have to wait for someone to come up with a compatible recovery.
thanks for he reply, but i have alredy used v3.0.0 which i was told was the chinese version and get the same problem
pfoxy said:
thanks for he reply, but i have alredy used v3.0.0 which i was told was the chinese version and get the same problem
Click to expand...
Click to collapse
Hi,
i Also had problems with the 3.0.2 TWRP. (not the same problems as you, mine wouldn't flash)
after renaming the XXXX TWRP. image to just TWRP.IMG and the "fastboot flashboot recovery TWRP.IMG command it workd for me.
and didn't used the reboot command after flashin, directly hold power and volume up.
really strange that you're phone needs 2-3 minutes to reboot in this modus, should rebooting within 10 sec.
Also..use the 3.0.2 from teamspain..I tried another one..but didn't workd for me
Thanks for replying - I had tried that but have just give it another try just in case but still same I hold POWER/VOL+ and goes to a black screen with blue led at top of fone - anything else to try?
Right now X821 is just incompatible with all the X820 recoveries out there.
hi - what is x821? I thought these were X820 processors?
pfoxy said:
hi - what is x821? I thought these were X820 processors?
Click to expand...
Click to collapse
X820 = Chinese Le Max 2 model
X821 = Indian Le Max 2 model
S820 = Snapdragon 820 which is the name of the SOC in both the above models.
I know it is slightly confusing.
I was just looking in About Phone in Settings and it says model Le X820 and I bought it from Geekbuying which is in china
pfoxy said:
I was just looking in About Phone in Settings and it says model Le X820 and I bought it from Geekbuying which is in china
Click to expand...
Click to collapse
The Indian version is encypted to prevent people from messing with their stock rom.
jim262 said:
The Indian version is encypted to prevent people from messing with their stock rom.
Click to expand...
Click to collapse
but i think i ave a chinese version
jim262 said:
The Indian version is encypted to prevent people from messing with their stock rom.
Click to expand...
Click to collapse
Even though it is encrypted, I managed to flash Official 14S CN ROM using update from Storage option. Don't bother booting up as it has plenty app crashes. Straight boot into fastboot mode and flash TeamSpain's TWRP. According to @STEVE_MARS we need to remove registered fingers and PIN to be able to flash TWRP on Indian 15S ROM.
I am not sure of what you doing then. I have deleted mine and reinstalled various Roms on it and have not had these issues, so I am not sure what you are doing, but before installing new ROM, did you wipe or dirty flash? Could possibly be residual files/data causing conflicts on boot.
Thanks sanke1 and jim262
Jim262 - i am not sure what clean and dirty flashes are. Do you mean i should do a clear data before trying to fastboot?
Sanke1 - I shall try now thanks both of you
A clean flash is where you wipe pre existing data, prior to installation of ROM and dirty flash is where you install ROM on top of existing data.
LOL bricked it now i think - after flashing recovery with twrp after running clearup when i reboot left half of the screen flashes ble for a second and the the screen goes blank and the blue LED comes on. Any ideas greatly appreciated.
No, you haven't bricked your phone. You are just installing over old data. That is what causes that. Download Revolution Rom 5.8_15s onto your c:\ drive of your PC. Reboot your device into fastboot mode (make sure you have your USB cable attached and the drivers loaded on your PC for ADB). Next make sure you have the twrp.img downloded and copy it to your ADB folder. Then open up a command prompt session. Change the directory to your ADB directory. Type <adb devices>, this this will start the server and return info from your phone (provided you have installed the drivers). Verify that you can see your device in Windows File Explorer. If you can see the device, type <fastboot boot twrp.img> at the adb prompt. Once in TWRP, wipe your device's internal storage. That means Dalvick, cache, system, data and internal storage. That is for a clean install. Once it is all wiped, go back to your pc and copy the rom from you c: drive to your internal storage. Once the copy is complete you should still be in TWRP on your device. Simply go to <INSTALL> and flash the rom. If you have done everything properly upon completion of the install, reboot into system. All should be good.
I can only get into fastboot now. I can not get into recovery now. I cannot clear dalvik or anything not even into stock eui recovery - is there any way to reinstall stock recovery partition. I have tried installing twrp all versions I have found but they do not work for me - sniff - .
The above directions are for a fast boot install. At the Open adb prompt, type <Fastboot boot twrp.img> this will boot twrp. Wipe your drive, copy the file and flash it from there. No need to access recovery.
pfoxy said:
LOL bricked it now i think - after flashing recovery with twrp after running clearup when i reboot left half of the screen flashes ble for a second and the the screen goes blank and the blue LED comes on. Any ideas greatly appreciated.
Click to expand...
Click to collapse
You are not using TeamSpain's CM13 recovery. Try to flash that recovery. Even I had the half corrupt screen. Then I realized that I was flashing wrong TWRP.
Related
Malfunction " x " appears on the screen !! help me what is going on
Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.
Did you flash any ROM if so, did you clean your Dalvic+REgular Cache
If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM
you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is
Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?
study it ,thank you
study it ,thank you
Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i
not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!
Glad that you got it
Hi. Looks like I fkced my phone. Was using Darkobas twrp, flashed this room and it boot-looped at the beginning (phone was turning on and off on the "Coolpad" screen). I can enter the recovery however can't transfer roms into the card. While pushing big files with ADB push (it takes few minutes) it randomly stops responding/hangs in the middle of a transfer. Tried multiple times and it stops randomly ( I've wiped/formatted whole storage )
I managed to flash another recovery 3.1.0.0 but still I need to push some rom to see if I can flash it. After PC reboot it stopped detecting my phone...
Fastboot is not working, power + vol down goes to black screen / turning off the phone.
Tool_all_in_one does not detect my phone. In fact I do not see it in Windows Device Manager. Tried different usb 3/2 ports
Commands in console like fastboot oem device info gives:
< waiting for any device >
adb reboot bootloader gives:
adb server version (39) doesn't match this client (36); killing...
* daemon started successfully *
error: no devices/emulators found
It's done guys?
Update: somehow managed to restore connection, so phone is visible in Device Manager as "Android Composite ADB Interface" .
Managed to push AICP ROM with adb but can't see it on sdcard. Usually, it was in the main directory, now nothing is there.
Adb sideload? It still seems to me like youre having connection issues w/the pc. Tried rebooting to fastboot from twrp menu?
1 - Enter Twrp Recovery
2 - Wipe -> Format Data then type "yes". This command gonna wipe your internal storage behold.
3 - After this reboot recovery and go to mount then enable mtp.
4 - Transfer rom file.And after a clean wipe flash it.
That rom have bootloader and some modem file that can bring up some issue mate.And those files belongs to Changer not to our beast.
Both device very very familiar but its different product anyway you can't trust it.
I RECOMMEND ALL OF PEOPLE GONNA FLASH ROM please first check the firmware files .If there, then clean it and wipe from the updater-script.
For an alternative you can flash your stock firmware files from QFİL but it's risky too.
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Make sure you are not using a USB hub, or extension cable. Also make sure you are plugged directly into the PC motherboard, not one of the front ports. I had transfers stalling and it was my USB extension cable.
Thes1ev said:
Thanks for the replies. MTP was enabled all the time in the recovery. I have unmounted all partitions, repaired, formatted etc. After multiple tries, I managed to push and flash AICP rom. Good it's only ~500Mb. Transfer of bigger files was interrupted every time.
By the way this JUI ROM has replaced the starting screen. Phone is quietly squeaking for few seconds (in fastboot all the time) after every reboot on 'CoolPad' screen, similar to this 42sec 12000Hz. Any way to back to 'original' LP3 one?
Click to expand...
Click to collapse
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
trizex said:
Sure, you need to flash the firmware files, download 23s from the official site, and fastboot flash all the files, that'll return you to stock fastboot, splash, etc.
Follow this guide (no need to format data, and flash system again, just the files in firmware update folder).
https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-manually-upgrade-firmware-t3609786
Click to expand...
Click to collapse
Can't flash anything using fastboot - "fastboot flash xxx.img" gives me: < waiting for any device > and nothing happens.
At the moment trying to flash stock 23s but it's hanging on "Patching system image unconditionally" for 5+ minutes already.
This JUI fcked bootloader in my phone somehow. It's blocked/can't be replaced or no idea what's going on here.
Edit: so ye after 20+ minutes of "Patching system image unconditionally" looks like I'm unable to flash stock 23s using TWRP 3.1.0.0.
Probably it wants to replace this fkn JUI bootloader and freeze there.
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
Yap, was flashing official stock 23s from this site via twrp.
Okay today gonna try Alba ROM as you suggested.
trizex said:
Wait, are you trying to flash complete official update.zip via twrp?? You cant do that. Find a 23s package customised for flashing via twrp, I think I used alba's package from 4pda
Click to expand...
Click to collapse
That helped, thanks a lot!
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
testreaper said:
Is there any solution to restore Leeco bootloader? I just cant flash anything because device is unknown during fastboot mode. Tried to uninstall and reinstall driver but no luck.
I am stuck with coolpad bootloader which is not recognised from my pc. Serves me right because i didnt check the zip of jui which i flashed that had another bootloader, fml.
If any kind soul has any info on that please say it, thanks.
Click to expand...
Click to collapse
That is litterally what this whole topic was about? See my responses, if you still have access to twrp (dont see why wouldnt you), you can use it to flash a 23s "stock" rom through it (such a package will contain, among others, the leeco bootloader etc)
---------- Post added at 08:00 PM ---------- Previous post was at 07:59 PM ----------
Thes1ev said:
That helped, thanks a lot!
Click to expand...
Click to collapse
Youre welcome, everything back to normal?
trizex said:
Youre welcome, everything back to normal?
Click to expand...
Click to collapse
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Thes1ev said:
Yeah, I got rid of this JUBU bootloader after flashing stock-like rom. Also thanks to this there is no more strange noise during the boot sequence.
Click to expand...
Click to collapse
Ya, I heard that squeeling too, when booting, and in fastboot mode
Thes1ev thank you so much pal, i flashed 2 different 23s with all wipes and they gave me errors but your rom installed perfectly.
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
TWRP: https://dl.twrp.me/karate/twrp-3.1.1-1-karate.img
Gapps: http://opengapps.org/ (ARM64)
J.D.M said:
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
Click to expand...
Click to collapse
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Crolys said:
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Click to expand...
Click to collapse
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem. Remembering that in the site https://dl.twrp.me/karate/ has two versions of TWRP, the version twrp-3.1.1-0-karate.img is 32bits and the version twrp-3.1.1-1-karate. img is 64bit.
J.D.M said:
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem.
Click to expand...
Click to collapse
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Crolys said:
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Click to expand...
Click to collapse
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Crolys said:
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Click to expand...
Click to collapse
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
got same 255 error,just now i reflashed stock rom and issue resolved
vasu009 said:
got same 255 error,just now i reflashed stock rom and issue resolved
Click to expand...
Click to collapse
how did you reflashed the stock rom, please reply cause im stuck with the twrp and unable to do it. my phone doesn't have an os now
what s the password of the trwp
J.D.M said:
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
Click to expand...
Click to collapse
Can install this ROM on any Lenovo K6 Power device ??
dushd95 said:
Can install this ROM on any Lenovo K6 Power device ??
Click to expand...
Click to collapse
Yeah
J.D.M said:
Yeah
Click to expand...
Click to collapse
It says device not supported why??
Dont forget to reboot again into twrp - after flashing 64bit twrp . This is a step that is very important if you will not reboot your phone into twrp after flashing 64 bit twrp then , it will keep showin you the error 255.
So check that .
wacccim said:
what s the password of the trwp
Click to expand...
Click to collapse
Go for 3.2.1.0 it is better then 3.1.1.1 in 64 bits it ain't ask password i use it to flash all roms
Tere 3.1.1-1 asking for password to encrypt data
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Erase the data
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
Use erase the data from wipe option then you will be able to install rom and g-apps.
Every time you will need password, I don't know why but after erasing data you install all files otherwise you need to erase data again and again
Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
I Faced same problem. It's ok that your phone is in weird state for time now. And also possible to recover.
Hopefully you have adb-tool, custom-rom & gapp, twrp.img on your PC.
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
fastboot oem reboot-recovery
3)Wait for mobile to boot in to recovery mode with TWRP
Now need to flash custom-rom followed by gapps installion.
I) You can use pendrive with otg to flash custom-rom followed by gapps
OR
II)You can use phone storage/SD card to flash the custom-rom followed by gapps
OR
III)adb sideload command as fallow
a)In TWRP recovery on mobile, goto Adavanced->ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify custom rom path inside ""
adb sideload "C:\adb\images\MyCustomROM.zip"
Have a patience to complete the operation.
Click back for Adavanced Menu again.
b) Select ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify Gapp path inside ""
adb sideload "C:\adb\images\open_gapps-arm-7.1-pico-20180611.zip"
c)Have a patience to complete the operation.
Once complete go to TWRP Screen.
d)Now go back TWRP main menu & select wipe->format Data.
Go to Reboot->system.
How to install TWRP if no OS there
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
a) To check the device is connected to PC or not
fastboot oem device-info
b) To flash the recovery. Give twrp path inside the ""
fastboot flash recovery "C:\adb\images\twrp.img"
c) To boot into recovery mode
fastboot oem reboot-recovery
---------- Post added at 10:03 PM ---------- Previous post was at 09:57 PM ----------
[/COLOR]
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
In my case, It worked with PIN.
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
I stupidly tried using franco's app to flash cleanKernel on my rooted phone on 9.0.11, it failed of course and now can't boot my phone. I'm able to fastboot boot twrp.img but I'm not sure what is needed next. I've downloaded the full 9.0.11 ota file thinking something in it (or all of it) needs to be flashed from twrp. Afraid to do anything at this point for fear of losing data. Any tips are appreciated.
I've downloaded mauronofrio's rom-stock-fastboot utility but see he says it will clear data. I'm assuming all the .bat files will do this. Any way to avoid clearing internal storage?
soundneedle said:
From bootloader screen, using fastboot boot twrp.zip results in OP going to "Fastboot Mode" screen...and staying there. The zip is pushed to the phone but won't boot into TWRP. This started after I stupidly tried using franco's app to flash cleanKernel on my rooted phone. It failed of course and now can't boot my phone. My phone recently updated itself to 9.0.11, fyi.
Any ideas on how to fix this boot issue? Is it just a matter of flashing something from the full ota 9.0.11 file---some img file or something?
Click to expand...
Click to collapse
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
I was able to recover...thank god. Just used mauronofrio's flash utility. Removed the "-w" flag from the flash-all.bat file and all is good.
Stuck on Fastboot Mode screen once I run fastboot boot twrp.img
bp328i said:
Wouldn't you want to be using a twrp.img not .zip?
fastboot boot twrp.img
Boot twrp from the img and then flash the zip once twrp boots?
Click to expand...
Click to collapse
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Is the twrp.img even being flashed
SimmoMaz said:
Hi, I have just got a OnePlus 6T and I am getting this same error even though I am using the twrp.img - when I run fastboot boot 'twrp.img' it sticks on the Fastboot Mode screen.
I have the .zip on the phone's internal storage along with Magisk ready to install but I can't get there.
I did manage to get into Recovery once in the last 3 hours but under Advanced the only 2 options I have are to reboot to fastloader of reboot to recovery which just takes me round in circles!
Have tried everything I can find/think of right now and am no further down the line
Any help guidance will be greatly recieved as nothing I can find on the threads here seem to help
Thanks
s
Click to expand...
Click to collapse
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
SimmoMaz said:
When I think about it, it seems that the twrp.img I am flashing is not taking. When I go into recovery I get to choose 1 of 3 languages, I choose English and then I just get the 2 options as above - thing is, the font, layout etc. make it look like stock recovery and nothing like TWRP I have used before, no TWRP logo etc. Nothing
Click to expand...
Click to collapse
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
TWRP isn't there
lilbrat said:
Ok.. can you get into TWRP? Is so reflash the stock rom.. the once it has flashed do not reboot, go back to install and flash the lastest twrp .zip do not reboot, go back to install and flash/install magisk, once it installs then reboot to system... It will take a bit... Once it reboots check your Magisk manager you may need to reinstall it, reboot to TWRP and reflash it.. reboot to system band you should be good to go...
Click to expand...
Click to collapse
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
SimmoMaz said:
Thanks and apologies if a two posts appear from me, I submitted one about 20 minutes ago and it isn't showing.
The issue is more than that, even when I try to flash the TWRP image it doesn't seem to take. The phone gets stuck on the 'Fastboot Mode' OnePlus flash screen and hangs there.
I have to hold the power and vol+ keys to get the device to restart and I then receive a message saying 'bootloader unlocked, data insecure etc.' and to press the power to stop the boot process. If I leave it the phone boots into OOS10.3.3.
If I press the power button I can get to recovery mode (albeit there is a password screen there which I have never seen on other devices I've had). I put my password in and choose English. I am then given the two options; reboot to fastboot or reboot to recovery. There is no advanced option to allow me to install TWRP or Magisk zips, as a matter of fact I don't get any TWRP at all, it looks like stock recovery.
Is the phone defaulting to stock recovery and not the TWRP image? That is what, in my very non-expert opinion seems to be happening. Is that possible and if so, any ideas how to fix?
I have completely flashed the phone so it is on stock OOS (10.3.3.) so can start afresh. It is a refurbed 'like new' so could that have anything to do with it?
Thanks for reading the long post - am wondering if there are some other tools I need use to change how it boots?
S
Click to expand...
Click to collapse
Ok.. are you using the latest TWRP? If you want in the guide section you can you the msmdow like ad tools to reset you phone to stock, and retry again..
THIS. I have the exact same issue. In short, I have the T-mobile version, and was able to unlock successfully. I am using twrp-3.2.3-0, and I have the img and zip in the same folder, same way Techibee does on Youtube. I then type "fastboot boot twrp-3.2.3-0-fajita.img", I get the "OKAY... OKAY... Booting... Finished" response in console. Then, the Fastboot screen appears and never leaves. I have done this 3 times now. I kept tweaking the process, but I'm nervous to keep debugging.
Stuck (
Hello guys,
I wanted to overclock my 6t global. so i had unlocked the bootloader then flashed the twrp. In twrp i firstly reset the os to factory setting and then i flash magisk and smurf kernel. but when i reboot after this my phone is stuck on the phone unlocked message.
ive tried flashing magisk only and then boot, it works. but when i flash smurf kernel i get stuck . why this happening plz help (