Develop Bugs

[Q] SD Card not mounting & Fastboot errors

Hey guys!
My SD card won't mount in Recovery mode... When I try to flash zips or partition the SD card I get the following error:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
Upon further reading, I've tried going into Fastboot (which does work thankfully) but every command I use, including:
Code:
fastboot oem enableqxdm 0
Chucks me the following error:
Code:
... FAILED (status malformed (1 bytes))
I'm totally at a loss here guys, and I'm way out of my depth with this one. Any help would be appreciated!

first try fastboot devices
to see if ur phone is detected

It does list the device in Fastboot, but not in adb shell devices :S

now re type fastboot oem enableqxdm 0

FAILED (status malformed (1 bytes))

type fastboot oem boot
then take a print screen of the writing
ur phone will reboot

Same error.

let me look for a fix

is ur desire s-off

Yup. It's running AlphaRev's 1.8 HBoot with S-OFF
HBoot version is 0.93.0001

what does fastboot devices show
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
just post the first two letters or numbers

HT*********421
Blanked of course

good ok do u have a sd card reader i.e sd to usb

do u have windows 7 or xp and are the hboot and fastboot drivers installed propery

I have all of the above. I've been installing ROMs for some time now, its only just happened after I installed AlphaRev's Hboot.

the only thing i can say is do u have a ruu for ur phone if not i can find 1 for u

I've downloaded the RUU.exe for my phone, but it requires a working ROM in order to work, of which I don't have. :-/

not true i used my ruu from fastboot usb plug
run the ruu

It's an .exe... you saying just to Run that? I've ran it and it tries to find the phone, but it can't as it searches for USB debugging, but since theres no running ROM it fails.

what os are u on win 7 or xp

M8 / Bootloop

Hi,
and sorry for my poor english...*
My Device:
HTC One M8
M8_UL UNKNOW
Tampered / Unlocked / Root / S-OFF
CID 11111111
TWRP: latest
Rom: viperone
Problem: bootloop.
The problem occurred after installation of the dualsim adapter from the Magicsim (magic-sim.com]). That did not work, so I tried to reinstall the rom with full wipe.
Result: bootloop and no access to the viper's rom, and no access to recovery.
M8 is seen by the fastboot:
fastboot devices returns <ùOu☼ÚQÞÁ¾ £ ╦ <~)
M8 is not seen by ADB:
adb devices returns nothing
*
I think the drivers are OK. But I can reinstall drivers if necessary?
What I have noticed abnormal, it is in fastboot getvar all:
INFOserialno <ùOu☼ÚQÞÁ¾ £ ╦ <~)
INFOmodelid: ☻◄
I have incomprehensible symbols. I can not rewrite the mid or serial ...
Anyway ... I can not fix the problem ...
*
Also HBOOT gives:
Loading ... [0P6BDIAG.zip]
No image!
Loading ... [0P6BDIAG.nbh]
No image or wrong image!
Loading [0PGBIMG.zip]
Loading [0PGBIMG.nbh]
No image or wrong image!
*
Do you know how can I fix it ?
Thx!

Sorry, I haven't a verizon, but HTC M8.
If a moderator can redirect it ?
Thx

noxarv said:
Hi,
and sorry for my poor english...*
My Device:
HTC One M8
M8_UL UNKNOW
Tampered / Unlocked / Root / S-OFF
CID 11111111
TWRP: latest
Rom: viperone
Problem: bootloop.
The problem occurred after installation of the dualsim adapter from the Magicsim (magic-sim.com]). That did not work, so I tried to reinstall the rom with full wipe.
Result: bootloop and no access to the viper's rom, and no access to recovery.
M8 is seen by the fastboot:
fastboot devices returns <ùOu☼ÚQÞÁ¾ £ ╦ <~)
M8 is not seen by ADB:
adb devices returns nothing
*
I think the drivers are OK. But I can reinstall drivers if necessary?
What I have noticed abnormal, it is in fastboot getvar all:
INFOserialno <ùOu☼ÚQÞÁ¾ £ ╦ <~)
INFOmodelid: ☻◄
I have incomprehensible symbols. I can not rewrite the mid or serial ...
Anyway ... I can not fix the problem ...
*
Also HBOOT gives:
Loading ... [0P6BDIAG.zip]
No image!
Loading ... [0P6BDIAG.nbh]
No image or wrong image!
Loading [0PGBIMG.zip]
Loading [0PGBIMG.nbh]
No image or wrong image!
*
Do you know how can I fix it ?
Thx!
Click to expand...
Click to collapse
Did you try to reflash your recovery ? Your recovery may has been corrupted. I would try flashing the newest twrp 2.8.1.0 recovery and see if that fixes your issue.

Hi, and thx,
Yes, I do it.
I've try to reflash my recovery (latest ie 2.8.1.0) and RUU.
But fastboot returns error :
FAILED (remote: 41 model id check fail)
That the reason why I think it's probably a problem with M8 identification (mis & seial) ?

No idea ?

noxarv said:
No idea ?
Click to expand...
Click to collapse
Until this thread gets moved and/or you look in the I international section you likely won't get a response here.
Sent from my HTC6525LVW using Tapatalk

dottat said:
Until this thread gets moved and/or you look in the I international section you likely won't get a response here.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Moved to International, thanks.

Thanks !
At this level, I think it is not possible to repair my M8.
I've read this related post : http://forum.xda-developers.com/showthread.php?t=2627411
Because of this thread and of the failure of my attempts, I would like to send my phone to HTC. The warranty period is valid, BUT, I have red text, SuperCID tampered and S-OFF...
How can I build a "good" android-info.txt ?
Correct modelid : 0P6B10000
Corrupt modelid : ☻◄
Can you suggest me a solution to find a issue ?!

I try to do somthing...
With an Hexaditor, I have write this android-info.txt :
Hexa :
Code:
6d 6f 64 65 6c 69 64 3a 20 e2 98 bb e2 97 84 0a
63 69 64 6e 75 6d 3a 20 31 31 31 31 31 31 31 31
0a 6d 61 69 6e 76 65 72 3a 20 33 2E 31 36 2E 30 2E 30 30 30 30 0A
Texte :
Code:
modelid: ☻◄.cidnum: 11111111.mainver: 3.16.0.0000
In the android-info.txt, it gives the following result :
Code:
modelid: ☻◄
cidnum: 11111111
mainver: 3.16.0.0000
But after flashing process, fastboot return a 41 model id check fail.
At this point, do I persist in this way?
Thx a lot,

restart loop with V10.3.5.0.ODEMIXM after factory reset

I have my MI MIX 2 with official global V10.3.5.0.ODEMIXM. I upgraded to this version via regular OTA update about 2 weeks ago.
After factory recovery I did last day I stuck in restart loop with error.
I picked up language, region, and after that on Just a sec screen I have error Find Device closed unexpectedly and going to restart loop.
Via Mi suite 3 beta I am able to flash same firmware, but this is causing same error and loop. Older firmwares are not possible to flash because of error. (flashing firmware older the nactual firmware on phone)
Via fastboot I am not able to flash anything as phone has locked bootloader and is not assigned to my Mi account so unlock tool is not able to unlock it.
So.. what can I do to fix it ?

hi , if you have access to fastboot look if arb is on , download this => https://androidfilehost.com/?fid=24686681827312411 and copy/paste that => fastboot getvar anti ,, if you get 4, arb is on ..... if you have under , you can flash older firmware
So if you have 4 , search '' Anti-rollback Protection and Fastboot Unlocker '' to download antirbpass dummy.img

So
fastboot getvar anti
anti: 1
fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.002s]
writing 'antirbpass'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.006s
Mi suite 3.0 still says:
Sorry, I can't support the rollback to a non-newer previous version.
Push Man Brush Pack Version: V10.3.5.0.ODEMIXM

hi you have anti 1 , you can flash older rom without brick , you have unlock bootloader
rom 10.2.2.0 =>http://bigota.d.miui.com/V10.2.2.0....XM_20190109.0000.00_8.0_global_ffb701bb41.tgz ,, you can flash ,, after that make upgrade firmware via update
ps: un flash.bat it will ask for 0 to flash ............. i did mistake ....... you can try flash beta rom , it's under pie , i flashed it to and it's stable
=> https://bigota.d.miui.com/9.5.30/ch...30_20190530.0000.00_9.0_global_6c535734e7.tgz
after flash search update normaly get 9.6.13

I really appreciate your help, but I was not succesfull.
Bootloader is locked and unlocking via MI Unlock is not succesfull because no Mi account is bound to the device.
Flashing via Mi Suite 3 always ends like this:
V9.5.8 (pie) -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V9.6.13 -> Unable to flash between different android versions. Please flash ROM via Fastboot Flashing
V10.2.2.0.ODEMIXM - > ROM Package verification failed Unknown Error[2013]
V10.3.1.0.ODEMIXM -> Sorry, I can't support the rollback to a non-newer previous version.
V10.3.5.0.ODEMIXM -> Succesfull, but always get boot loop with error FIND DEVICE CLOSED UNEXPECTEDLY
I also tried to reboot to EDL with help of this srticle: https://www.xiaomigeek.com/edl-mode-xiaomi.html second option - 2. How to Boot into EDL From Fastboot Mode.
But it always restarts and goes to boot loop.
So is last try open the phone and test point method? http://en.miui.com/thread-1351514-1-1.html

XA1 Data CRC32 error.

I have xperia XA1 which was dead a few days ago. It wont go into fastboot mode nor turn on and show sony logo. It only goes into flashmode. So i downloaded firmware form xperifirm and try to flash using value flashtool. But flashtool finishes flashing after writing TAunit value 01. My stderr.log file is given. After searching I found that it was issue due to firmware mismatch between current device and one I try to flash. If I am wrong please correct me also give me a better solution. Sorry for my bad english. Thank you.

s.subash said:
I have xperia XA1 which was dead a few days ago. It wont go into fastboot mode nor turn on and show sony logo. It only goes into flashmode. So i downloaded firmware form xperifirm and try to flash using value flashtool. But flashtool finishes flashing after writing TAunit value 01. My stderr.log file is given. After searching I found that it was issue due to firmware mismatch between current device and one I try to flash. If I am wrong please correct me also give me a better solution. Sorry for my bad english. Thank you.
Click to expand...
Click to collapse
EDIT: Forget what I just said I have seen your post and Debug.log on the FlashTool Github.
I don't see what's causing the no boot issue except maybe you didn't flash all touched partitions.
EG: Flash the stock fotakernel (recovery) also might need a cache data wipe so add those to the flash.
Flashtool seems to be flashing the wrong TA units & data · Issue #101 · Androxyde/Flashtool
I used Flashtool 0.9.25.0 to flash munjeni's D5503_openbootloader.ftf. The enclosed preset1.ta file says this: 02 0000084f 0054 1A CE 28 00 01 00 06 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 ...
github.com

bigrammy said:
EDIT: Forget what I just said I have seen your post and Debug.log on the FlashTool Github.
I don't see what's causing the no boot issue except maybe you didn't flash all touched partitions.
EG: Flash the stock fotakernel (recovery) also might need a cache data wipe so add those to the flash.
Flashtool seems to be flashing the wrong TA units & data · Issue #101 · Androxyde/Flashtool
I used Flashtool 0.9.25.0 to flash munjeni's D5503_openbootloader.ftf. The enclosed preset1.ta file says this: 02 0000084f 0054 1A CE 28 00 01 00 06 05 00 02 02 51 00 10 03 00 02 04 02 05 00 01 03 ...
github.com
Click to expand...
Click to collapse
bigrammy thanks for your response.
I had been tried out with all sort of partitions flashing but none of them worked.
Then i try to download the source file and made some changes to check the value of crc32 and finally I found that each time I start flashing the crc32 data taken from mobile varies. I don't know if this is normal or not.

s.subash said:
bigrammy thanks for your response.
I had been tried out with all sort of partitions flashing but none of them worked.
Then i try to download the source file and made some changes to check the value of crc32 and finally I found that each time I start flashing the crc32 data taken from mobile varies. I don't know if this is normal or not.
Click to expand...
Click to collapse
Flash the full stock ROM with no alteration, include data and cache in the flash too.
All the stock .sin files contain info to prevent sony's tool flashing corrupted image files from what I know. (which is not much).

Asus Rog Phone ZS600KL unbootable

I'm stuck in unbootable mode, can you help me step by step? I ran the "partition" command and got the following results:
PartitionNumber DriveLetter Offset Size Type
1 1048576 260 MB System
2 273678336 16 MB Reserved
3 C 290455552 212.23 GB Basic
4 D 228168040448 25 GB Basic
5 255011586048 1000 MB Recovery
So, I think no memory is burnt. I've been trying for two days, but I don't understand what I'm doing wrong. I tried "flash_allAFT" but it gives me a failure. Can you tell me which code I can post? Thank you all.

"FAILED, fastboot.exe flash all WW_ZS660KL_17.0240.2103.75_M3.23.44.19-ASUS_1.1.229_Phone-user.raw failure, EXIT!"

anto-chipset said:
"FAILED, fastboot.exe flash all WW_ZS660KL_17.0240.2103.75_M3.23.44.19-ASUS_1.1.229_Phone-user.raw failure, EXIT!"
Click to expand...
Click to collapse
Flash in edl mode with edl Firmware

"I have an EU version, but I can only find WW or CN. Can you translate this into English?"

anto-chipset said:
"I have an EU version, but I can only find WW or CN. Can you translate this into English?"
Click to expand...
Click to collapse
Tutorial to flash your phone in edl mode.
If you can access fastboot mode then connect it to pc and open cmd and enter following command to enter in edl mode fastboot oem enter-dload
Make sure you have fastboot and qualcomm drivers installed and driver signature verification is disabled on your windows machine.
if no access to fastboot mode then please use the edl cable to boot in edl mode.
Repair your ROG2 phone with EDL mode，Official firmware！
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
And here are the files required
Asus ROG 2 Firmware by VIKRANT.zip
drive.google.com
MI flash tool link to flash the firmware
MiFlash2018-5-28-0.zip
drive.google.com

fastboot devices
JAAZGV200231FRL fastboot
PS C:\Users\wras\Documents\rog> fastboot oem enter-dload
...
FAILED (remote: unknown command)
finished. total time: 0.000s
miflash : can not found file flash _all bat.
thanks for your patience if you can get me to fix this dead cellphone i will give you a fee