Database Info

[fix] to those having bootloop issues with CM5 based roms

I posted in the CM5 rom thread about my phone bootlooping when either
1)the phone froze and rebooted
2)i selected reboot
this meant that this rom was basically unusable because you lose everything when you have to reboot.
This problem was persistent throughout test 1-3
I had received multiple PMs about other users also experiencing this so i know its not just me.
Well... I finally got it working!
hers what i did:
1) go through the whole flashing procedure
2) boot it up
3) do not touch the phone for at least 10 minutes (i waited 15)
4) do not sign into google, skip everything
5) once it starts to load the home screen do not touch your phone again for 10 minutes
6) sign your google account in
7) while everything is syncing, do not touch phone for 15 minutes ( at least until its done)
8) take it slow and try to avoid any reboots due to freezing
eventually the rom will accept reboots and not bootloop, my phone finally rebooted itself the next morning when it froze up. But it booted up fine, i can now reboot without bootloop!
I hope this guide helps any other android users who are very angry at not having this wonderful rom work on their phones due to bootlooping after reboot.

no but there have been apps that are missing from market when running cyan roms . i pmed him but hes too busy to respond so back to ce for me !

My "solution" (workaround?): If your phone fall into bootloop do:
1. Go to recovery mode (you may have to remove the battery to restart the phone)
2. Go to console mode.
3. Type in console: "mount -a" and hit enter. It may take some time...
4. Type in console "umount -a" and hit enter.
if you did not do steps below you may need to step between 2 and 3 do
1. Type in console: "mount -a". Hit enter.
2. Type "mkdir /system/sd". Also hit enter
3. Type "umount -a".
These steps wil allow you to properly mount ext partition from sdcard. Perhaps these steps are not needed.
I'm using AmonRA recovery 1.6.2 and this solution works for me every time. Btw. I'm not sure but I think that bootloop cause is slightly damaged system files on one partition. Maybe system detects that partition wasn't unmounted properly and not allow to mount this partition and continuing to boot system.

Coby Kyros Internet Tablet MID7005-4G

HSN Launches Coby Kyros Internet Tablet 7" Android OS 2.1, 800MHz with 1080p HDMI review by me (note just click on the image to get to the review)
Coby Kyros Internet Tablet MID7005-4G Work-in-Progress Review by me
(note just click on the image to get to the review)

hi
hi where did you buy this ive been looking for a while?

I got a 7105-4g at k-mart yesterday.

Hey, I have a Kyros MID 7005-4G too. Unfortunately, it's pretty screwed at the moment. I'm looking for a recovery image for the device. If anyone can get me a recovery image of one of these, I'd be very grateful. I've tried a recovery image MID 7015, but they don't seem to be similar enough to work. Anyone?
Edit: On second thought, the Framework.jar file from an MID 7005-4G would help too.

Market
Yea, I just bought the MID7005 and it's cool. The resistant touchscreen is a little difficult at times. I really want googles market on it though. Id love to know how? Anyone?

clockworkmod/cyanogenmod/market on 7005
If you're interested in modding your 7005, I bought a used one on ebay. It was locked and the password lost by the previous owner when I got it, and it seems like it's been dropped because the charger is pretty intermittent. I don't think my battery is charging...
Anyway, if you want google market on it you will need to root your device and install a custom recovery.
What you will need:
SD card 1gb <
computer with the Android SDK (you need to use the ADB)
z4root
dump-recovery-signed.zip
clockworkmod recovery for the X5A-G
Cyanogenmod 7 for X5A-G
GAPPS (Google Apps) flashable zip
NOTES
***if you're very brave you can try using terminal emulator, but I don't recommend it. This tablet doesn't have a lot of power and crashing or freezing at any time during this process will almost definitely brick it. Just use the ADB and don't take the risk!***
I can confirm that both Clockworkmod Recovery and the Cyanogenmod 7 ROM for the X5A-G work on Kyros 7005.
1. install z4root and permanenty root. reboot
2. link removed at owner's request
you can get into the recovery by either holding home and power at bootup, or by enabling USB debugging on the tablet and then issuing the command
Code:
adb reboot recovery
Once you are in the recovery, select update from .zip file. This will trick your tablet into thinking it is preforming a firmware update, when in fact it is running a script that is backing up the recovery to your SD card.
3. download the x5a-g clockworkmod recovery .zip. Renaming it as 'update.zip' and attempting to flash using stock recovery does not work. You will have to do this manually, either via the adb or terminal emulator. I strongly suggest using the adb.
4. extract the clockwork mod recovery .zip file and find the recovery.img file. Copy recovery.img to the root of your sd card (in other words just drag and drop the recovery.img into the sd card)
5. obtain a root shell. If you don't know what that means you REALLY should not continue with this tutorial!!! open up a terminal/cmd prompt and start the adb.
Code:
adb shell
Code:
su
The prompt should now change to # indicating that you have gained root access. a prompt screen may show up on your tablet asking you to allow "unknown" root access. Click allow and proceed to the next step.
6. Flash the recovery.img from the root of your SD card
Code:
flash_image recovery /sdcard/recover.img
* I think this should go without saying, but you do have to insert the sd card into tablet and allowing android to mount it...
7. reboot into your new recovery
8. make a backup of your system. This is a precautionary measure to ensure that you will have at the very least a working system to boot back into. Reboot.
9. before you flash the cyanogenmod rom, you will have to do a factory reset and format /system from recovery. Once you've done this, you can proceed to flashing Cyanogenmod 7 rom. After the flash completes, reboot the tablet. Don't be alarmed or think that you've bricked your device. The first boot takes a LONG time. After you boot up for the first time you should be prompted to calibrate the screen. if the tablet doesn't automatically prompt you to calibrate the screen, fire the adb shell back up and enter the command
Code:
am start -a android.intent.action.MAIN -n org.zeroxlab.util.tscal/.TSCalibration
** it has been my experience that after first calibration the screen will not operate properly until after a reboot. Don't be alarmed! Just reboot using the command
Code:
adb reboot
since you probably won't be able to get the tablet to do so from the screen/buttons.
10. Once you have booted back into your tablet which should take considerably less time than the first boot after flashing, you will now be looking at the Cyanogenmod 7 desktop for the first time! Now you need to gain access to the google market. reboot into recovery, which can easily be done now from the shutdown menu.
11. flash the gapps .zip file and reboot
12. Your tablet will go through the "New Phone Setup" process. you will be prompted to set up a bunch of things, but you can skip past a lot of it. once you get to the desktop, connect to your wifi, open the market and off you go!

Automatic boot into CWM

Sorry for my English.
I have a problem. I try to install some custom ROMs on my Asus Transformer TF101G, and it works fine, but now, when i try to boot system after install, CWM automatic start, and i can't boot the system. Someone know what is problem, and how i can solve it?

ivance95 said:
Sorry for my English.
I have a problem. I try to install some custom ROMs on my Asus Transformer TF101G, and it works fine, but now, when i try to boot system after install, CWM automatic start, and i can't boot the system. Someone know what is problem, and how i can solve it?
Click to expand...
Click to collapse
Did you install CWM recovery with ROM Manager?
If you did here's your problems/solutions
http://forum.xda-developers.com/showthread.php?t=1530337

I've also found that you don't have to flash a new recovery (it's recommended though)
Once it is booted up into recovery, plug it into your computer, open up a command prompt and change directory to where you have adb installed. For me, I type the command
cd c:/android-sdk/platform-tools
Once I type that and press enter I'm in the folder where adb is installed and I can access adb commands. Type in:
adb shell
then press enter, you should see a little # sign
Type in:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
and press enter.
Make sure you exit the shell by typing:
exit
then press enter.
Now you can reboot using adb by typing:
adb reboot
press enter.
This is important, do not reboot using the CWM "reboot device" otherwise you'll just boot up to CWM recovery again.
Forewarning though, if you don't boot a new recovery image, next time your device restarts it will boot loop into CWM recovery again, unless you redo these steps, or follow the thread the previous poster linked and install a new recovery image.

[Q] CWM Recovery boot loop.

So I have the issue where my CWM version is boot looping. I know how to fix it by flashing the CWM roach fix but my SD card directory is not visible either. It's only showing the internal sd card. I unfortunately can not get my transformer driver to install on my pc. The driver that is provided from the asus website isn't working. That and the driver should be showing "APX" i believe, and it's showing "Transformer".
I've done a lot of searching for help and all the recommendations are saying connect it to the computer and use adb to push the file or to create a micro sdcaard directory. Or use nvflash.
Suggestions are appreciated.
And for info, i've used a pc with windows xp, and 2 laptops one with windows 7 and one with windows 8. No luck with the drivers.

same problem, I can't ADB either.

Brand New said:
same problem, I can't ADB either.
Click to expand...
Click to collapse
I'm still actively looking for a fix. I'm trying to see if I boot in linux if I can get the tablet recognized. I'll report back. If you find a fix yourself please share.

I wonder if we flash a new update.zip and just return to complete stock if it'll work?

No, the recovery (if you have the same one I have) is that it is a bug in the recovery that continually boot loops. I have nand and tried to install fresh and it doesn't fix. If you can read your sdcard not your internal memory you can easily just install the fixed roach recovery that doesn't boot loop and that will fix it for you.

If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.

This helped. Step one was slightly pointless due to the fact that the CWM recovery doesn't read the SD card but the internal storage. But after doing the cold reboot, I loaded the new one, and then followed the steps 1-3 without the exit and it applied with no issue. I'm now on the new touch recovery with no boot loops. Thanks very much for your help.

Yeah I should have pointed out to cold boot first and put the files needed on the internal sd.
Edit above post to show that

How do you coldboot?

Brand New said:
How do you coldboot?
Click to expand...
Click to collapse
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot

baseballfanz said:
Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot
Click to expand...
Click to collapse
Thanks buddy I owe you one.

Thank you guys

thanks
Hi guys, I just registered today, I have been using XDA for a while now, and hadn't created an account. I rooted my asus tf and Flashed CWM and ended up getting the recovery bootloop. Within 10 minutes I had found this post and used baseballfanz suggestion to use terminal emulator, and Flashed the touch Recovery and got out of the bootloop. Now running AOKP on my TF-101 and its smooth as butter. I felt i needed to make an account today just to thank baseballfanz. You guys rock, thanks again.
**EDIT** stryke504, i neglected to thank you as well in my earlier post.

This is what this place is all about. I created an account back in 2007 and just started posting last year for the same reason.

Sick!!!! It worked!!!

Hi guys I'm in trouble!! I have continuos bootloops in recovery. I tryed to flash a rom as usual but always bootlooping adn when I tryed to make a cold boot it remain in the same " colod booting linux ".. I can't restore my backup cause I move it on my memory card and cant restore it! Can I do something? I can't boot anymore... Any suggestions? I can only install the rom I have put in the internal memory..

same issue and nothing seems to work.....help
I was caught in a bootloop with CWM 3.2....something or other...couldnt adb. Couldn't cold boot...just clicked and stayed on screen...now I have lost the recovery I did have and feel like I am royally screwed....I am on tf101 b90....so nvflash doesn't work so I read....exactly how screwed am I?

What do you mean? You don't know what recovery you are using anymore?? Have you tried NVflash? Does your computer recognize the tablet?
Sent from my PG86100 using xda premium

thank you
helped fix my problem i was having but i was caught in the terminal and it kept denying root access the way i solved this was to
cold boot
re root using vipermod 4.5 and using option 1
http://bit.ly/Ac63pA
then following the steps with the terminal commands
fully working transformer

baseballfanz said:
If you guys are able to cold boot into the OS, use Terminal Emulator to do what
ADB would do.
1 - Cold boot into the OS and move files needed to internal sd storage.
2 - Reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...
3 - Once installation is done , don't press "reboot system now" , do a cold boot directly (Vol down plus power button, wait till you get the option of cold boot or wipe data, choose cold boot)
4 - Once you've booted your rom , run terminal emulator.
type : su (if superuser appp ask to you , allow). will give you a #
type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
type : exit
type : reboot
NOTE: Someone say the above steps only work when they skipped the exit part so try it both way.
Click to expand...
Click to collapse
hum, sorry, i don't mean to be slow but im not understanding how i can install from zip (sdcard) if my bad cwm can't read it.
i can cold boot, i can use terminal but how can i flash the files if i need to be in recovery to do it and that recovery won't read the sd?
is it possible to flash from terminal?
thanks,

[RECOVERY][TOUCH]TWRP 2.7.0.0 Touch Recovery [UPDATE TO #define's thread]

Since, @#define doesn't has the device anymore and I was working on updates of TWRP Recovery, so after some talks with him, I am making a new thread where I will maintain TWRP Releases.
OFFICIAL TWRP HTC EXPLORER PAGE
Latest Release - v 2.7.0.0 by @thewisenerd
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Removed Superuser prebuilt binary and Superuser.apk (By me not in Official TWRP) to trim the recovery size.(Thanks for the idea @galaxyfreak )
Older Changelogs
For the new people, here are the instructions..
----> For Windows :
1) Download the recovery zip and the tools given above..
2) Extract the zips someplace safe (for eg, C:/TWRP)..
3) Open the command prompt, and navigate to the folder in which you extracted the files..
4) Boot your phone into Fastboot mode, and connect it to the computer.. It should show "Fastboot USB"
5) In the command prompt, type :
Code:
fastboot flash recovery recovery.img && fastboot reboot
6) Enjoy your new recovery!! :good:
----> For Linux :
1) ADB and Fastboot for linux are also attached above..
2) Download and extract all the stuff in a safe location (for eg, ~/TWRP)
3) Open terminal, and navigate to the goodies folder..
4) Put your phone in fastboot mode, and connect to USB, and it should show "Fastboot USB"..
5) Now in terminal, type :
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot
6) Enjoy your new touch recovery!! :good:
Credits -
@#define
@galaxyfreak
@thewisenerd

thank you for updating this man

Nice Work mann!!
Thnks!! for update!!

a bug is it reboots when wiping partitions sometimes

theBstep said:
a bug is it reboots when wiping partitions sometimes
Click to expand...
Click to collapse
Yes I know. Restarting device/recovery fixes it!

v_superuser said:
Yes I know. Restarting device/recovery fixes it!
Click to expand...
Click to collapse
just letting you know cus so far no one's been posting around about this cus it's just a minor bug but if you can fix it for further builds that will be good

Bug founded
When restore/wipe than recovery restart not rebooting recovery.second time working?
If it's already noticed,solve in next version?
logcat:

Recovery restarts when try to fix permissions

Was anyone able to get fastboot working?
I remember it working in my home builds, but I don't recollect it working in this recovery though.
Is this "bug" only for me?
Edit: NVM, borked USB
edit: spoke too soon. Yes. adb *is* broken. works at times, doesn't work, at times.
edit: let's put this post to good use:
Download: http://www.mediafire.com/download/sx78aa9eu21c54q/twrp_21may2014.img
Don't give the crap that you're even interested in changelog. You just need something that works. You'd not even know if this is just the same file, with a different name.
For those who really are, go over to https://github.com/omnirom/android_bootable_recovery/commits/android-4.4, and check the commits from Mar 28, 2014.

Nand recovery partition burned
For those who are encountering NAND Recovery Partition burned.
booting on recovery,
TWRP logo shows
then go black screen
then TWRP logo shows again
then stucked at TWRP Logo.
SOLUTION:
BOOT into BOOTLOADER.
FLASH Latest PhilZ Touch Recovery (here: http://forum.xda-developers.com/showpost.php?p=41061154&postcount=3)
Download flash_erase.txt *rename and remove .txt* it's a binary file.(here: http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526)
Flash any rom that has working ADB.
Push flash_erase on /system/xbin then set and fix permissions.
Code:
adb push flash_erase system/xbin/
adb shell
su
cd system/xbin/
chomd 755 flash_erase
Reboot
Then perform a NAND Recovery on /recovery partition. (Needs USB debugging enabled and Root access on Apps and ADB)
Code:
adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd1 0 0
FLASH TWRP Recovery.
NOTE: IF YOU GOT WHOLE YOUR MTD PARTITION BURNED. flash_erase mtd0 to mtd6.

Agaphetos said:
For those who are encountering NAND Recovery Partition burned.
booting on recovery,
TWRP logo shows
then go black screen
then TWRP logo shows again
then stucked at TWRP Logo.
SOLUTION:
BOOT into BOOTLOADER.
FLASH Latest PhilZ Touch Recovery (http://forum.xda-developers.com/showpost.php?p=41061154&postcount=3)
Then perform a NAND Recovery on /recovery partition (http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526)
Code:
flash_erase -N /dev/mtd/mtd1 0 0
FLASH TWRP Recovery.
Click to expand...
Click to collapse
I would suggest you do that not from the recovery.
You can also do the same procedure with any ROM booted and ADB or Terminal Emulator

thewisenerd said:
I would suggest you do that not from the recovery.
You can also do the same procedure with any ROM booted and ADB or Terminal Emulator
Click to expand...
Click to collapse
yeah. i just cut the instructions. haha. they must flash ROM first then put flash_erase on /system/xbin.
then perform flash_erase -N /dev/mtd/mtd1 0 0.
it's only for those who got whole MTD partition got burned.
they can't boot into both /system and /recovery.
Edit: I updated my post already.

Agaphetos said:
yeah. i just cut the instructions. haha. they must flash ROM first then put flash_erase on /system/xbin.
then perform flash_erase -N /dev/mtd/mtd1 0 0.
it's only for those who got whole MTD partition got burned.
they can't boot into both /system and /recovery.
Edit: I updated my post already.
Click to expand...
Click to collapse
I have burnt my nand several times and i couldnt get into TWRP recovery at all ( stuck at the logo ). The solution I found was to downgrade to CWM 5 and then format boot/system/data. Then flash back TWRP 2.7 and superwipe for nand recovery - thanks to thewisenerd works like a charm.

boko_to said:
I have burnt my nand several times and i couldnt get into TWRP recovery at all ( stuck at the logo ). The solution I found was to downgrade to CWM 5 and then format boot/system/data. Then flash back TWRP 2.7 and superwipe for nand recovery - thanks to thewisenerd works like a charm.
Click to expand...
Click to collapse
i suggest you to still flash_erase your /recovery partition.
flashing another recovery on your /recovery partition doesn't recover bad blocks.

Agaphetos said:
i suggest you to still flash_erase your /recovery partition.
flashing another recovery on your /recovery partition doesn't recover bad blocks.
Click to expand...
Click to collapse
Yes right, - I was just giving a workaround if someone can't get into recovery - and what worked for me - after re-flashing TWRP i never had any problems with the recovery partition again.

Do you need to have your device to S-OFF?

fgaurano said:
Do you need to have your device to S-OFF?
Click to expand...
Click to collapse
Pico has no s-off so no developer expects it
Sent from my Xperia S using XDA Free mobile app

I have my Fastboot USB connected, and after typing the command, it justs " < waiting for device> " I tried removing USB a lot of times already and fastbooting USB.

fgaurano said:
I have my Fastboot USB connected, and after typing the command, it justs " < waiting for device> " I tried removing USB a lot of times already and fastbooting USB.
Click to expand...
Click to collapse
That also happened to me. If youre using windows 8.1, maybe thats the problem. The only way was flashing through terminal emulator.

I have the recovery partition burned, but the instrutions to fix are not clear enough for noobs like me.
EDIT: Based on the @Agaphetos instrutions and from this thread http://forum.xda-developers.com/showthread.php?t=2389445
Note: This method WON'T work on Windows 8/8.1. It will work fine on windows 7.
Backup your apps and stuff before doing anything
1. Download and Install HTC Sync Manager http://www.htc.com/pt/software/htc-sync-manager/
2. Download and Install ADB fastboot drivers http://forum.xda-developers.com/showthread.php?t=2588979 (I dont know if this is really necessary)
3. Get the adb and fastboot drivers, you can use the ones from this recovery, just remove the "recovery.img" that comes with http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100
4. Download this PhilZ Touch Recovery http://forum.xda-developers.com/showthread.php?t=2265055 and rename it as: recovery.img
5 Place the "recovery.img" that you have renamed to the "A310E Recovery" folder
6. Remove the Battery and SIM card (in case you dont have a mobile network plan) If the rom youre using has the "Reboot to Bootloader" option in "Power Menu" you can use that instead.
7. Place the battery, and press "Volume Down" and "Power Button" at the same time till you boot into "Bootloader".
8. Connect your phone to the PC and choose "Fastboot", it will show "Fastboot USB" in red, then go to the "A310E Recovery" folder and run the "recovery.bat". You have flashed the PhilZ Touch Recovery.
9. Press "Power Button" to exit "Fastboot". In "Bootloader" menu choose "Recovery" to enter in PhilZ Touch Recovery.
10. In there make a "Wipe Data/Factory Reset", "Wipe cache", go to Advanced: "Wipe dalvik cache". Go to "Mounts and Storage" and format everything except "/sdcard". (Maybe you dont need to wipe everything Ive mentioned:silly
11. Scroll down and choose "Mount USB storage".
12. Download a CM rom, Ive used this one http://forum.xda-developers.com/showthread.php?t=2535682, and place the .zip rom in root of sdcard. Im sure other CM roms will also work.
13. Download this AROMA Filemanager http://forum.xda-developers.com/showthread.php?t=1646108 and place it in root of sdcard.
14. Download (Save this file as) flash_erase.txt http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526 and remove the ".txt" file extension and place it also in root of sdcard.
15. Flash the CM rom. Once flashed the rom go to "Mounts and Storage". Mount everything till you see all "unmount", go back.
16. Flash the "aromafm.zip". It will open AROMA filemanager. Scroll down and enter in "sdcard" and copy the "flash_erase" file, go back. Look for a "system" folder, scroll it down till you find one saying "xbin", enter there and paste the "flash_erase" file.
17. Look for the "flash_erase", and then long press it till you see a menu, choose "Set permissions". The first 3 lines should be all green already, Exit AROMA Filemanager. and reboot system.
18. Once youve booted into the CM rom, go to "Settings" -> "About Phone", In there scroll down to "Build Number" and press it several times to enable "Developer Options".
19. Go back and enter "Developer Options", make sure "Android debugging" is enabled. Connect your phone to the PC. Now go to "Terminal Emulator" and enter the following commands.
Code:
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd1 0 0
It will show up a message with something about 100% I cant remember:silly:
20. Boot into "Recovery" again, make a Wipe and Format everything, like you did in step .10.
21. In "Power Off" menu of the Recovery, choose "Reboot to Bootloader"
22. Plug in the phone in "Fastboot USB" and repeat the step .4, .5 and .8 but for the TWRP Recovery instead.
23. You should now be able to boot into the TWRP recovery, make sure you Wipe Everything again in "Wipe" -> "Advanced Wipe", except "sdcard". If the recovery reboots while wiping, reboot recovery and try again.
DONE!