yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] Perry2547:
I was looking on eBay and saw a G2 I'm considering buying.

In the description it listed as OLED.

Is that correct?

Unfortunately, Camera has stopped.
[G2 Q&A, Help & Troubleshooting] takeoff342:
No, the G2 have in each Version in IPS Diplay, no OLED

The LG G Flex have an OLED Display, maybe the seller make a mistake
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Hi everybody,

I've been flashing custom ROMs for years now, but now I screwed up -.-

I've got a One M7UL and accidentally flashed a Sprint ROM .. Now the only thing left working is fastboot.

If I try to boot into TWRP recovery (tried different versions already) the splashscreen will appear and crash back into bootloop. If I try to boot into clockwork recovery, it will boot but throw various errors 'E:Can't mount /cache/[..]' .. as soon as I try to do anything @ clockwork, it will crash back into bootloop.

I thought about flashing a RUU, but the bootloader is unlocked but still s-on. Modelid: PN0170000 Cidnum: VODAP102. I think the device has to be s-off to flash a RUU.exe, correct ? How about a RUU.zip ? oO Is there a way to get the device s-off without having ADB working ? How do I find a working RUU for this device, because I've read that I need a '1.xx.161.xx' for it's a Vodafon-brand and I won't find a damn usable RUU for it .. Is there a way to use a different RUU ?

help would be MUCH appreciated :D

thx & greets

hendi
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Ok, got ADB working at the damaged clockword recovery .. but sideloading another ROM won't work and it seems like Revone S-OFF only works with a booted 4.2.2 ROM -.-

Any suggestions ?
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Here's the output off 'getvar all':

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.14.3250.13

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.29.161.11

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

(bootloader) serialno: xxxxxxxx

(bootloader) imei: xxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: VODAP102

(bootloader) battery-status: good

(bootloader) battery-voltage: 4246mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435

getvar:all FAILED (unknown status code)

finished. total time: 0.052s
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
If I could get my hands on another HTC ONE M7ul PN0710000/VODAP102 would I be able to build my own RUU ?

Help would be really appreciated ^^
[One (M7) Q&A, Help & Troubleshooting] nateboi81:
Have you tried fastboot erase cache?
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
yep, sadly without any success.. I also tried different versions of TWRP & clockwork recovery.

thx for the reply :)
[One (M7) Q&A, Help & Troubleshooting] clsA:
it's been a while but i think the old developer edition RUU may work

this is the one for hboot 1.44

http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
hey there :)

Don't I need a RUU with the version 1.xx.161.xxx because of the s-on + Vodafon-branding ? oO
[One (M7) Q&A, Help & Troubleshooting] clsA:
Yes .. but some of the developer RUU had a different android-info.txt that encompassed a bunch of different models .. I'm just not sure which ruu it was

Maybe [MENTION=2605798]nkk71[/MENTION] could chime in
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
ah, cool that's good to know oO - I am already downloading :)
[One (M7) Q&A, Help & Troubleshooting] clsA:
Sorry I was doing some more reading ..that RUU requires CID 11111111 and MID PN0712000, I'll keep looking
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Sorry, didn't read, but if s-on, then don't start fashing things not for your phone... High chance you won't be able to unlock bootloader again!

If s-off, then ok.
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
big thanks, pal :)
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
hey, yeah I am afraid it's still s-on .. but I didn't try to flash it so far.

How can I manually lock the bootloader again ? oO I've just tried method 1 from your guide (http://xdaforums.com/showpost.php?p=47794190&postcount=3) but the bootloader still says it's unlocked oO

I haven't tried yet, but 'fastboot oem lock' should do the trick .. Now I just need a fitting RUU oO

Damn it, I'm kinda flashoholic since the good old Windows Mobile 6.51 Pro-times .. but I never took the wrong ROM xX

You guys really seem to know what you are doing .. the wrong ROM seems to have messed up at least the cache partition, may be there is another way than flashing a RUU, to fix this ? If I would be able to get clockwork recovery to install a working rom, it should reconstruct everything or at least give me the opportunity to s-off the device oO

I would be really grateful for some help :)

I just got an idea: Is it possible to tweak an developers RUU ? oO

Sorry for all the questions, I just really want to get that baby up an running again ^^
[One (M7) Q&A, Help & Troubleshooting] clsA:
sure you can try

Unlock the bootloader at HTCDEV

then from fastboot USB

Flash recovery TWRP 2.6.3.3

http://techerrata.com/browse/twrp2/m7ul

fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img

fastboot erase cache

fastboot reboot-bootloader

then sideload this Rom to your phone

http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip

TWRP / Advanced / ADB Sideload - swipe to sideload

From PC adb / fastboot folder

you use

adb sideload name-of-rom.zip

make sure the rom is in the same folder as adb / fastboot
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
sorry, may be you misunderstood me: The bootloader is open & s-on. I've tried to flash different versions of TWRP & Clockwork Recovery via fastboot, including erase cache.. TWRP won't even start and Clockwork will start but throw multiple 'Can't Mount / Open /cache/[...]' errors and crash as soon as I try to do anything :(
[One (M7) Q&A, Help & Troubleshooting] clsA:
try and flash the stock recovery and do a factory reset

then try and flash TWRP again

Stock recovery's are here >> http://d-h.st/users/guich/?fld_id=29380#files
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
damn, sorry I've spent the whole day and night, reading how to possibly fix this and already tried to flash stock recovery .. The recovery won't start at all. It doesn't matter if I try to start via 'Factory Reset' or 'Recovery'.

According to the errors clockwork recovery throws, I guess the partition table got (partly?) messed up oO

*edit* Of cause I've tried again, following the link you've just sent me - thx for the effort :)
[One (M7) Q&A, Help & Troubleshooting] clsA:
do you know how to start stock recovery ?
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
After flash, erase cache & reboot-bootloader, I've tried 'Factory Reset' @ Hboot and the 'usual' way via the bootloader oO
[One (M7) Q&A, Help & Troubleshooting] clsA:
and you never get to the red triangle screen ?
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Nope, just as if I try to start TWRP, the bootloader turns black for about a second, than the device vibrates once and reboots.. and of cause gets stuck at bootloop.
[One (M7) Q&A, Help & Troubleshooting] clsA:
did you try locking the bootloader back with stock recovery installed ?

before you give up completely you can try the AT&T RUU here

http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe

The only problem is you may not be able to unlock the bootloader again ... you'll be stuck with a working phone though

it should flash this is the android-info.txt in it
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Nope, I haven't tried that .. It didn't seem to be the problem oO

Mhh when I loose all hope, I'll give the RUU a try, thx! But for the moment I hope somebody comes up with a solution

Big thanks for your help so far! :good:
[One (M7) Q&A, Help & Troubleshooting] clsA:
I have a HTC First that bootloops till you lock the bootloader after you get s-off.

took hours to figure that out .. it works fine with the bootloader locked
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
huh ? strange behavior ^^ but the thing is that it wasn't necessary before the 'flash-accident'.. If I lock the bootloader via fastboot, will I have to go through the HTC-Dev unlock-process again, or is it possible to unlock via fastboot (since it's only 'relocked') ? Because I don't know if the HTC unlock method will work entirely ..

But since it's 6 o'clock in the morning (localtime) .. it's time to get some sleep ^^ See ya in a few hours ;)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
so I sort of read your thread.

with s-on, i wouldn't risk locking bootloader (at least not yet), can you give me the link of the ROM you flashed... let's see which partitions it messed up, maybe we can fix it without RUU.

EDIT: or even easier, open the ROM.ZIP, extract and upload the updater-script found in \META-INF\com\google\android
[One (M7) Q&A, Help & Troubleshooting] clsA:
Good morning, your in good hands with nkk71 ...if i remember correctly the last time this occurred it was fixed with a TWRP install followed by a DATA format in TWRP... Good luck to you
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
And good night to you, sir ;) yeah, I also got the feeling this man knows what he's doing, so I still got some hope left ^^

When I first unlocked the One (I bought it as soon as it were available here ..) there weren't any 'stable' ways to get it s-off and as there were, I thought I shouldn't risk bricking it .. lol know I wished I would have set it s-off .. pwnd by irony ^^
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Hey buddy, how's everything, all well i hope :)

Well, I don't know what this "/tmp/backuptool.sh" does, but from the rest of the script:

* userdata was mounted as /system

* mmcblk0p39 (which doesnt exist on m7_u/ul) was mounted as /data ... hmm, what would that even give :confused:

* and the kernel was written to /system

do you remember any error during the install?

but anyway, we need a working recovery, so when you say TWRP shows splash and bootloops, have you made sure MD5 is okay on it?

if not please get TWRP from:

2.6.3.3: http://techerrata.com/browse/twrp2/m7

(make sure MD5 is correct, that site does not play nice with download managers)

in bootloader/FASTBOOT USB:

fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img

fastboot erase cache

fastboot reboot-bootloader

C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31

C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]

C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s

C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s

C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s

-> enter RECOVERY

EDIT: unable to mount cache is perfectly normal, it's due to the fastboot erase cache

I'll leave this link here for later (in case we need it): http://www.htc1guru.com/dld/ota_m7_...-7_release_315813_signedoj2qp335qmm8qjso-zip/
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Ah so it did get meshed up oO

Sorry I haven't seen any errors during the install.. It just blacked out and went straight to bootloop.

Mhh I think I have tested the 2.6.3.3 but I'll give it another shot (and check the md5).

Ah ok, so that's where the cache-errors are coming from .. but it's still strange that clockwork works while TWRP doesn't and crashes as soon as I try to do anything oO

Will be right back with feedback.

**edit**

The md5 is correct, but the result is the same .. as I try to enter recovery, the One vibrates ones, shows the white htc logo with a pink message 'entering recovery'. It loads for about 2-3 seconds and shows the TWRP spalsh for about 2-3 seconds. The screen turn black then and it's back at the white htc logo, at bootloop.

Here is my cmd-output:

I:\HTC One Toolkit - Squabbi - 3.1.2>adb version

Android Debug Bridge version 1.0.31

I:\HTC One Toolkit - Squabbi - 3.1.2>fastboot devices

HT33ZW903022 fastboot

I:\HTC One Toolkit - Squabbi - 3.1.2>fastboot flash recovery openrecovery-twrp-2

.6.3.3-m7.img

sending 'recovery' (9184 KB)...

OKAY [ 1.328s]

writing 'recovery'...

OKAY [ 0.682s]

finished. total time: 2.014s

I:\HTC One Toolkit - Squabbi - 3.1.2>fastboot erase cache

erasing 'cache'...

OKAY [ 0.049s]

finished. total time: 0.050s

I:\HTC One Toolkit - Squabbi - 3.1.2>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.037s]

finished. total time: 0.039s

**edit 2** tried it several times :\
[One (M7) Q&A, Help & Troubleshooting] nkk71:
okay, which recovery does work CWM? reflash it, then while in recovery, try running these commands:

adb shell

mount

and report back.... don't close the shell
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
CWM 6.0.4.6 works (it's the latest version).

output:

I:\HTC One Toolkit - Squabbi - 3.1.2>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

~ # mount

mount

rootfs on / type rootfs (rw,seclabel)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)

tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)

tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)

~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
okay, let's manually format your partitions using the shell:

get this: http://www.androidfilehost.com/?fid=23329332407585868

open a second command prompt to push the file:

adb push mkfs.ext4 /tmp/

then go back to the shell, and run the following commands (this will format /data, /system, and /cache)

chmod 777 /tmp/mkfs.ext4

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p35

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p36

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37

if those are successful, continue with:

mount /data
mkdir -p /data/media/0
exit

credits go to [MENTION=1631739]mike1986.[/MENTION] for his article: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html

then go ahead and push ARHD 31.6 (because you're using CWM) to the phone and install it.
[One (M7) Q&A, Help & Troubleshooting] clsA:
I'm doing well thanks ... just watching quietly in the background while you work your magic :cool:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
wish him luck, let's hope this get's it solved!! (and hope nothing else was corrupted)
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Nice! that sounds promising :) but .. please tell me you've got that script stashed somewhere .. androidfilehost stucks at 'searching for mirrors..' -.- .. is somebody or something kidding me, here ? *laugh*

tested with chrome @ pc and firefox nightly & opera @ laptop ..

*edit* registering an account did'nt help ^^
[One (M7) Q&A, Help & Troubleshooting] nkk71:
here you go: https://www.dropbox.com/s/9q5s7fzspp1937e/mkfs.ext4
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
ah, thanks buddy xD
[One (M7) Q&A, Help & Troubleshooting] nkk71:
i prefer push to be honest, and hopefully CWM (and other recoveries won't crash anymore since you formatted the partitions),

adb push Android_Revolution_HD-One_31.6.zip /data/media/0/

Example:

C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31

C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]

C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]

[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]

C:\ADB3>

-> in recovery, select "install" and install the ROM

.

except in you're case you push to /data/media/0/ since the symlink to /sdcard/ may or may not be there, so safer to push it to /data/media/0/

---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------

^^ yes, exactly!
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
alright, thx - will comply ;)

I'll be back in a few minutes - hopefully with good news :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
fingers are crossed :fingers-crossed:

good luck :good:
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
push initiated ^^

jeez when everything is working again, I should s-off the bootloader .. It would have made things quite more easy, wouldn't it ? ^^

thx! I've got a good feeling about this :D
[One (M7) Q&A, Help & Troubleshooting] nkk71:
if you want to s-off, i should have given you a different ROM :)

Let's have a nice booted up phone first, then i can tell you how to s-off your phone.
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
aye, this ROM should do the cleanup-job, first in line :)

Installation is on it's way *thrilling*

thx! A little hint would be nice ;D Since hboot is at 1.44, I should use Revone, I think .. But first things first :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
S-Off for 1.44 using revone: http://xdaforums.com/showpost.php?p=48955645&postcount=251

and here's a AFH mirror http://www.androidfilehost.com/?fid=23329332407589108

EDIT: and it's way more than 15 users by now... another user just did it a couple of days ago.

oh and sorry about the other file before, it didnt upload to AFH correctly due to the extension, hence you never got a mirror... the file wasn't even on AFH :p
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
OH DAMN YEAH :D AHRD works :D Thank a lot, bro - You are a magician indeed :D

ah, that explains why AFH stated your upload was made in1970 .. and strangely wandering back in time the more often I tried to download it xD

Alright, the structures should now be back to normal, correct ? So tonight I'll give Revone a shot :) When the device is s-off & unlocked, would you advise to update the firmware for coming releases and s-off & unlock again, using rumrunners ? oO
[One (M7) Q&A, Help & Troubleshooting] clsA:
Congratulations !! You have a working phone.

you only have to s-off one time and it stays their forever (unless you undo it)

I have successfully used rumrunner on hboot 1.44 on my 2nd HTC One

All I did was flash the rom and rumrunner worked first try

Don't forget to hit the Thanks button on [MENTION=2605798]nkk71[/MENTION] posts he's very good with these type of problems
[One (M7) Q&A, Help & Troubleshooting] nkk71:
:cowboy: :cowboy: :cool:

Nice, congrats!! :good:

I didnt even notice that :D

1- If you decide to S-Off, you do NOT go back S-On... ever!! (well unless you know exactly when and how to do it!!

2- with s-off you can flash anything anytime, no need to lock/relock or any of that, refer to my chart (Not so FAQ#2) about what you can and cannot do: http://xdaforums.com/showthread.php?p=52135024&postcount=2

3- firmware threads can be found here: Here are three good threads for firmware(s) for your model:

[Guide] Vomer's Ultimate AIO - S-OFF, SuperCID, Firmware Upgrade & Custom Recovery (in the firmware section)

or

[2014.03.30][GUIDE] [MOD] GSM Firmware Flashing & Hboots red warning gone

or

[HTC ONE M7] Newest Firmware 4.19.401.11 for KITKAT modified HBOOT, (No Red warning)

remember you need to be S-Off, and don't even THINK about going S-On!!

EDIT: and

please

only flash things suitable for your phone!!! with S-Off you can easily brick!!! so no flashing M8 firmware on M7 -> instabrick!!
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
hey there, thx a lot :D

aye, I already hit the 8-thanks-a-day-limit xD

man really knows how it's done :good:

ah cool, so I only have to s-off once ? nice! thx for the info :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yeah both rumrunner and firewater should work also, I can just confirm that ARHD 9.4 with a 1.xx firmware (hboot pre June 2013) works perfect with revone from the first try.

OP, if all is good now, can you also edit the main thread title to include [SOLVED] or [RESOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title), thanks
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
hey thanks bro, you're the man :D :highfive: :good::good:

yeah, nice - thanks for the links :) I'll have to leave for about 2 or 3 hours, but than look into it :) So I guess I'll s-off [MENTION=4951492]hboot[/MENTION] 1.44 and than look for a fresher firmware :)

I haven't yet looked into it, but I guess when the device is s-off I can change die CID and just have to look that I take a firmware for the M7ul Europe, correct ? ^^
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Thread title is updated :)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yep, once s-off just change to SuperCID:

fastboot oem writecid 11111111 <- eight characters exactly, CID is always 8 characters, no more, no less

fastboot reboot-bootloader

then you can flash any M7_U or M7_UL firmware (no other M7_something!!), and remember that firmware updates are done as follows:

fastboot oem rebootRUU

fastboot flash zip <name of firmware>.zip

fastboot flash zip <name of firmware>.zip <- yes TWICE !!

fastboot reboot-bootloader

and no need to lock/relock bootloader if you are S-OFF!!!!

---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------

Thank you (and I pressed the button) for following xda rules :good:
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Nice! Thanks for the infos! :laugh:

Really: Thanks a lot, bro - You saved my month! (considering the price of a new M7) :victory:
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Hey guys, just to let you know:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4A.25.3263.21

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.19.401.11

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

(bootloader) serialno: prnhtcone

(bootloader) imei: 0190666666

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4096mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9d12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.109s

:cool:

Everything works more than fine! :good:

Thank again for your help :D
[One (M7) Q&A, Help & Troubleshooting] clsA:
nice job