yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] marpek:
htc one 802w -help!!

My : fastboot getvar cid

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. Με επιφύλαξη κάθε νόμιμου δικαιώματος.

C:\Windows\system32>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.49.0000

(bootloader) version-baseband: U3.19.3509.04

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 7.19.1402.1

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: ------------

(bootloader) imei: ---------------

(bootloader) meid: 00000000000000

(bootloader) product: m7cdug

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0771000

(bootloader) cidnum: HTCCN703

(bootloader) battery-status: good

(bootloader) battery-voltage: 3746mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d0e3b226

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.092s

C:\Windows\system32>

Thanks
[One (M7) Q&A, Help & Troubleshooting] aaser:
Bricked and dumped M7_UL Canadian Wind for a year!

I'm quite a newbie, rooted and unlocked the phone but when I was trying disparately to gain S-Off - as far as I remember - I installed several Revolution HD ROM's, which was working fine! but ended up with a T-Mobil RUU that massed up my recovery, stopped touch screen and doesn't allow me to get OTA update (using a mouse and OTG cable). I also remember fiddling with cidnum !!:cyclops:

I'd really appreciate some newbie walkthrough help to bring my phone from brickhood back to life :D

fastboot getvar all:

MacBook-Pro:HTCOneRoot aser$ ./fastboot-mac getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.27.3218.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: GLOBA001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4209mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-e47fb74b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!
[One (M7) Q&A, Help & Troubleshooting] pekseg:
bricked htc one mini

I have two pieces of htc one mini, both died on the same way, OTA killed the devices.

Only fastboot is working:

cmd: fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.22.0000

(bootloader) version-baseband: N/A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.09.401.3

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: XXXX

(bootloader) imei: 355xxxxxxxxxx

(bootloader) meid:

(bootloader) product: m4_ul

(bootloader) platform: HBOOT-8930

(bootloader) modelid: PO5820000

(bootloader) cidnum: HTC__J15

(bootloader) battery-status: good

(bootloader) battery-voltage: 3755mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e1af350

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

boot error:

fastboot oem boot

...

(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000

(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2

(bootloader) [SD_HW_ERR] read data fail in CMD18

(bootloader) CMD18: cmd failed

(bootloader) [SD_HW_ERR] SD: Read data fail..

(bootloader) [ERR] partition_read_emmc(876): error 2

(bootloader) [DISPLAY_ERR] read sp1 partition fail!!!

OKAY [ 0.138s]

finished. total time: 0.139s

RUU also cannot flash the phone.

Any option, or shall I throw it in the waste bin?
[One (M7) Q&A, Help & Troubleshooting] alray:
Looks like a defective emmc chip, you're not the first one.
[One (M7) Q&A, Help & Troubleshooting] pekseg:
Could be, I'm just wondering how two devices died on the same day, after they received the same OTA...
[One (M7) Q&A, Help & Troubleshooting] ali262883:
when i type getvar i get this.. i have connected the device in fastboot mode..please help
[One (M7) Q&A, Help & Troubleshooting] alray:
http://xdaforums.com/showpost.php?p=63955546&postcount=6
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
HTC One M7 bootloader not unlocking

In a failed attempt to downgrade the M7 I flashed stock 3.62.401.1 , relock the boot loader and flashed the respective firmware. Then after 4.4.2 ota the device stuck in boot loop . So, I unlocked the bootloader again flash twrp and adb push arhd 93 . Then again relocked it for firmware update and flash the the firmware. Then tried to unlock the bootloader again and it failed. After couple of tries it bricked. Now, its showing some sign of life :D ( showing the chraging display). Any help with how to unlock the bootloader will be highly appreciated. btw, its s-on.
[One (M7) Q&A, Help & Troubleshooting] alray:
Which firmware file did you flashed exactly and what was your firmware version (version-main) before flashing that file?

Also post the output of "fastboot getvar all" (without IMEI and SN)
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
Previously it was 3.62.401.1 . Now, its 7.19.401.22.

K:\android backup\fastboot>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.61.0000

(bootloader) version-baseband: 4T.35.3218.16

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 7.19.401.22

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4296mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e2a13e5

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.031s
[One (M7) Q&A, Help & Troubleshooting] alray:
I said what file did u used? Provide a link please.
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
7.19.401.22.zip firmware: https://www.androidfilehost.com/?w=files&flid=32777

Rom : http://www.androidrevolution.org/do...ndroid_Revolution_HD-One_93.0.zip&hash=ef29f7
[One (M7) Q&A, Help & Troubleshooting] alray:
So you did updated the firmware from 3.62.401.1 directly to 7.19.401.22 using that zip file? If you look at the 7.19.401.22.zip file, its only about 20Mb.... Its not a full firmware package, they are usually about 50Mb. Flashing this file might have bricked your phone since it is not packed with all the firmware files that need to be updated.

Are you able to boot in bootloader mode?
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
yes I can boot into the bootloader and stock recovery. Also the phone can boot, but after optimizing 6 apps it reboots.
[One (M7) Q&A, Help & Troubleshooting] alray:
You should try to flash the 7.19.401.22 RUU. That should fix everything.

File at Post 2

Instructions at Post 1

http://xdaforums.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
Didnt work. Stuck in the successful screen on cmd. After rebotting the devices took me directly to the recovery. File used : PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
[MENTION=4654136]alray[/MENTION] Thank you :D solved. After, using the old unlock binary which failed, used a new binary that successfully unlocked the bootloader and with out any further delay twrp is flashed :D rely appreciated the help :D Thank you :D
[One (M7) Q&A, Help & Troubleshooting] sohojmanush:
:( its still not working. After flashing the twrp there is no internal memory (0 MB). adb push doesnt work,neither the adb sideload works. Only thing that work is adb push mkfs.ext4 /tmp. Still no phone :(
[One (M7) Q&A, Help & Troubleshooting] alray:
Format data then reboot the recovery
[One (M7) Q&A, Help & Troubleshooting] yc30337:
Unable to get to recovery after series attempts

Long story short, I got an M7 that had the screen shattered but still able to work for the last 1 1/2 years, and I finally bought the front/back covers to replace the damaged parts. After reassembling, I was not able to get into the recovery nor the OS whatsoever, while the screen keeps going back to the white HTC screen. Below is some of my details:

HTC One M7, AT&T model, non-developer

Unlocked and S-Off

Custom ROM: ARHD 92.0

After finding out I couldn't get to the recovery, I tried to do something myself to see if magic happens (actions not necessarily in the order described below).

fastboot flash recovery (several I have tried, with the ones I installed previously: openrecovery-twrp-2.6.3.3-m7.img, openrecovery-twrp-2.8.0.2-m7ul.img, recovery-clockwork-touch-6.0.4.8-m7.img, etc.)

Flash the Google edition RUU, including: RUU-HTC_One_GE-5.0.1-5.11.1700.3_rooted.zip, RUU-HTC_One_GE-5.0.1-5.11.1700.3.zip, RUU-HTC_One_GE-4.4.2-3.62.1700.1.zip)

Flash the firmware and the recovery that matches with Google Edition: 5.11.1700.3.firmware.zip, 5.11.1700.3.recovery.img.

Flash the AT&T RUU: RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip

Re-lock the bootloader and unlock afterwards

Flash the firmware and recovery some more times...

All of the attempts I did still got me nowhere to get to the recovery, and I am running out of ideas. During the re-assembly, I tried to make sure all of the connector into proper contacts and no damage done, although this is the first time I open up a cellphone doing repair myself.

Below is the dump of the attributes:

C:\Users\bruce\Downloads\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.087s

I really appreciate if anyone can provide me some other procedures to uncover what I can do in order to get this phone back up working again.

Thanks

Bruce
[One (M7) Q&A, Help & Troubleshooting] FLASHGOTHOPS:
are HTCs the only phones you can help with?
[One (M7) Q&A, Help & Troubleshooting] alray:
If its not a M7 you can post in your specific device forum (its off topic here), if there is no forum for your device, you can post in the general Q&A section. I can direct you to the correct forum if you can give more information about your device.
[One (M7) Q&A, Help & Troubleshooting] FLASHGOTHOPS:
LG G Stylo

Carrier-MetroPCS®

Type-Smart Phone

Form Factor-Bar

OS-Android™ 5.1 (Lollipop)

Technology-GSM, WCDMA, LTE*

Processor-Qualcomm® Snapdragon™ 1.2 GHz Quad-Core MSM8916

RAM-2 GB

Network-GSM 850/900/1800/1900, WCDMA Bands 1/2/4/5, LTE Bands 2/4/12*

Frequencies-GSM 850/900/1800/1900 MHz, LTE Bands 2/4/12*

Data-Transmission	LTE*
[One (M7) Q&A, Help & Troubleshooting] alray:
Yup there is a forum for the LG G Stylo here

You can post your questions there so ppl with the same device can help you.

Good luck :good:
[One (M7) Q&A, Help & Troubleshooting] Pharva:
Hello,

Its been a while since I've messed with my HTC. Tonight it powered off and then when I tried to boot, it would only go to the bootloader. I tried to install a nightly cyanogen zip from recovery, but it failed. This is what it displayed when trying to install:

Instaling update...

detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system

mount: Failed to mount /dev/blockplaytform/msm_sdcc.1/by-name/system at /system: Invalid argument

unmount of /system failed; no such volume

Patching system image unconditionally...

E: Error in /data/media/0/cmupdater/cm-12.1-20151129-NIGHTLY-m7vzw.zip

(Status 0)

Installation aborted

When I return to the recovery menu after trying the above install, it displays:

E: Can't open /cache/recover/last_log

E: Can't open /cache/recover/last_log

E: Can't open /cache/recover/last_install

E: Can't open /cache/recover/last_install

I've wiped all user data from recovery and wiped cache partition.

When connected to my computer (windows 10) I hear the notification letting me know the phone is connected, however it doesn't show up in My Computer. In the device manager I see:

Android USB Devices

>My HTC

But only when I'm in Fastboot USB. ADB and Fastboot will show <waiting for device>

Your help is greatly appreciated. Thanks for your time.
[One (M7) Q&A, Help & Troubleshooting] alray:
Looks like you are not using the right recovery version... What recovery (name + version) are you using?

Also write down all the info you can see from the bootloader menu.

can't open /cache.... error is pretty normal if you did wiped the cache. How the recovery is supposed to open a file that doesn't exist anymore (wiped)? ;)
[One (M7) Q&A, Help & Troubleshooting] Pharva:
I don't remember what recovery I used. It was a while ago, and I've forgotten. I think I used Firewater (?) to root the phone. I'm sorry I can't recall more information.

EDIT: ClockworkMod Recovery v6.0.4.8

When I power on (power button and vol down button) this is what is shown:

***UNLOCKED***

M7_WLV PVT SHIP S-OFF RH

CID-VZW__001

HBOOT-1.57.0000

RADIO-1.13.41.0421

OpenDSP-v32.120.274.0909

OS-

eMMC-boot 2048MB

Apr 22, 2014, 18:03:29.0

HBOOT

<VOL UP> to previous item

<VOL DOWN> to next item

<POWER> to select item

FASTBOOT

RECOVERY

FACTORY RESET

SIMLOCK

CHECK SMARTSD

IMAGE CRC

SHOW BARCODE
[One (M7) Q&A, Help & Troubleshooting] alray:
You have a verizon variant of the M7 so are you using the verizon version or CWM? I see you are already trying to install the right (verizon) version of CM:good:.... Maybe you could try another version number, nightly builds are known to be very buggy version.
[One (M7) Q&A, Help & Troubleshooting] Pharva:
CWM? ClockworkMod?

I would like to flash a ROM on to it, but ADB and Fastboot does not recognize my phone. When I enter into FASTBOOT USB my phone shows up in the device manager and HTC Sync Manager automatically starts on my computer. Once I'm in FASTBOOT USB, I run Minimal ADB and Fastboot and enter " adb devices " to check to see if my device is there, but nothing shows up. If I could get Minimal ADB and Fastboot to recognize my phone, I think I could try to install a fresh OS.
[One (M7) Q&A, Help & Troubleshooting] alray:
First, uninstall HTC sync (but not the drivers), you don't want that s**t installed on your computer if using fastboot and adb.

2nd, adb commands only works from a custom recovery or from a booted os with USB debugging turned on in the developer options menu. In bootloader mode, only fastboot commands will work, so its 100% normal your phone isn't detected by using "adb devices" when in bootloader. Use "fastboot devices"

Here the magic table that explain everything:
[One (M7) Q&A, Help & Troubleshooting] Pharva:
Okay, that worked. I entered "fastboot devices" and ADB and Fastboot returned: a_serial_number fastboot

I followed these instructions: https://twrp.me/devices/htconem7verizon.html I've installed platform-tools from android SDK. Then I downloaded TWRP-2.8.4.0-m7wlv.img and placed it in c:\program files (x86)\minimal adb and fastboot and renamed it to twrp.img. The file path is C:\Program Files (x86)\Minimal ADB and Fastboot\twrp.img

I then open Minimal ADB and Fastboot and run this command: fastboot flash recovery twrp.img

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img

sending 'recovery' (11992 KB)...

FAILED (command write failed (No such device or address))

finished. total time: 0.004s

I then downloaded twrp-2.8.7.0-m7wlv.img, and tried the same thing. I got the same error.

Next, I changed directories to C:\Program Files (x86)\Android\android-sdk\platform-tools and placed the twrp.img file in there. I ran the same command, but got:

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img

sending 'recovery' (12534 KB)...

FAILED (command write failed (Invalid argument))

finished. total time: 0.003s

I'm not sure what to do next. Thanks for your responses.

EDIT: I rebooted my phone and tried the twrp 2.8.4 version again. I got this message instead:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img

target reported max download size of 1514139648 bytes

sending 'recovery' (11994 KB)...

OKAY [ 1.526s]

writing 'recovery'...

FAILED (remote: image update error)

finished. total time: 2.858s
[One (M7) Q&A, Help & Troubleshooting] alawiishiro:
I have a problem with my htc, i deleted the os by mistake using the recovery

my phone is S-on but i have twrp 2.8.7.0 installed

how can i falsh the os

i tried falshing two zip files both says failed to flash

cid = HTC__J15

mid = PN0711000

please help me guys i really need to solve this problem, im with no phone for two days
[One (M7) Q&A, Help & Troubleshooting] alray:
Post the output of "fastboot getvar all" *(remove your IMEI/Serialno before posting)

What zip exactly did you tried?
[One (M7) Q&A, Help & Troubleshooting] Vasilios1:
HTC One M7 doesn't boot anymore - black screen after HTC logo

Hello,

I have T-Mobile(german) branded HTC One m7 with OS 7.18.111.2 and i recently I made an OTA update which somehow didn't work. After the reboot I just could not boot my phone anymore. The weird part is that the phone was not rooted and everything was as far as my knwledge goes stock. I tried everything to somehow get it going again including a root where I also flashed a custom recovery to try to restore the phone with a TWRP backup, but nothing worked. I really need your help and I'm looking forward to your replies.

Additional info:

S-On

HBoot: 1.61

Bootloader unlocked
[One (M7) Q&A, Help & Troubleshooting] Pharva:
Are you stumped with my last post?
[One (M7) Q&A, Help & Troubleshooting] alray:
Not easy to pinpoint what the problem might be when working from 2 different folders... Better to start over, uninstall everything then install the latest HTC drivers version and latest android sdk tools, try different usb ports (usb 2.0 only), usb cables or even a different computer. I'm a little worried of that "image update" error... that doesn't sound good.... Might worth to post the output of "fastboot oem dmesg" and "fastboot oem last_dmesg". Just want to make sure there is no problem with the emmc of your phone...
[One (M7) Q&A, Help & Troubleshooting] alawiishiro:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.61.0000

(bootloader) version-baseband: 4T.35.3218.16

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) meid: 00000000000000

(bootloader) product: m7_u

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0711000

(bootloader) cidnum: HTC__J15

(bootloader) battery-status: good

(bootloader) battery-voltage: 4237mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e2a13e5

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

i tried

Google-Plus-Edition-LP_m7_v3.2_072915

OTA_M7_U_K44_SENSE60_MR_HTC_Europe_5.11.401.110-4.19.401.5_release_3724106akzxaksbvcwdgds
[One (M7) Q&A, Help & Troubleshooting] Fir3Dolan:
Htc one m7

Hey, you are my last chance to help me I guess.

I rooted my old M7 long time ago and didn't S-Off. Never updated firmware

Now I am stuck with a 3.61 Vodafone(?) firmware where all roms go into bootlop and the only rom which is working now is a gpe Rom where the device is offline in adb and I don't get mobile data because I'm S-On and that's a rom sided bug because everyone reported that in the comments.

What can I do now?
[One (M7) Q&A, Help & Troubleshooting] alray:
Flash the 7.19.401.102 RUU (see post 1 of this thread for instructions and file). You might need to follow instructions at the end of post #2 of that same thread before flashing the RUU (hard to tell with a blank version-main)

---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------

Post the output of "fastboot getvar all" like the guy above your post did.
[One (M7) Q&A, Help & Troubleshooting] Fir3Dolan:
Somehow I got adb / fastboot working now with the ViperOne ROM after waiting almost an hour to boot up.

But now I still don't know how to S-FF or go back to Stock for updating the firmware.

C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.55.0000

(bootloader) version-baseband: 4A.22.3263.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: FA428W910973

(bootloader) imei: 359405059034932

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: VODAP102

(bootloader) battery-status: good

(bootloader) battery-voltage: 3886mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-ea0bccbd

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.103s
[One (M7) Q&A, Help & Troubleshooting] alray:
you could flash a kitkat rom, s-off using rumrunner or sunshine then change your cid for supercid, flash the 7.19.401.2 firmware and then flash any rom you'd like.
[One (M7) Q&A, Help & Troubleshooting] Fir3Dolan:
I'm going to test a KitKat ROM now. Hopefully it won't end in a bootlop again. :rolleyes:

Update #1 : Bootlop on CarbonRom KitKat [m7]

Update #2: LiquidSmooth v3.0 is booting up, waiting if something happens

Update #3: Didn't boot up. Now trying an older version of ViperOne because that one actually booted up in the Lollipop version.

Update #4: ViperOne 6.1.0 Bootlop. Now trying 5.0.0

Update #5: The Installer is not even opening. New ROM incoming..

Update #6: And it's another bootlooping one..

Update #7: Don't know why, reflashing the working ROM so I can use my M7 as MP3 Player for work tomorrow. If you have any ideas on how to go on, let me know.