venue 3730 without sim option
stuck on dell logo
already did hard reset but same
i try fastboot flashing
recovery and boot file written but error in system.img
any solution ?
C:\fastboot devices
DellVenue7000123667 fastboot
C:\fastboot flash fastboot
G\Venue_7_WiFi_KK4.4.2v1.33.fast
target reported max download siz
sending 'fastboot' (11941 KB)...
OKAY [ 1.768s]
writing 'fastboot'...
OKAY [ 1.493s]
finished. total time: 3.265s
C:\fastboot flash sy
Venue_7_WiFi_KK4.4.2v1.33.system
target reported max download siz
sending 'system' (514147 KB)...
OKAY [ 54.347s]
writing 'system'...
OKAY [ 98.005s]
finished. total time: 152.355s
after witing system.img still stuck on logo
any solution mates..................?
Hello everyone. I have some issues with Fastboot. whenever I try to flash recovery.img i get this error. my device is Cherry Mobile Touch xl 2 with android 6.0 and mt6580.
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot flash flash recovery.img
target reported max download size of 134217728 bytes
sending 'flash' (10678 KB)...
OKAY [ 0.266s]
writing 'flash'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.281s
When I try to just boot into custom recovery, everything goes well except that the phone just reboots. it does not boot into custom recovery. I heard it from somewhere that fastboot boot recovery.img command did not work anymore. Is this true?
C:\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.281s]
booting...
OKAY [ 0.063s]
finished. total time: 0.344s
Thank you for your help.
OPTIONAL READING
Hi, let's go:
Scénario: you know nothing Jon Snow, but you want root, so you install fastboot, no matter which twrp, you follow a couple of tutorials you found in the wild and you play around with slot a -slot b twrp option. You find funny erase partitions, that way you have more internal space, maybe. You erase devil cache, and good boy cache and everything, because why not? You do not make backups, 'cause your not a coward, but a little nervous-impulsive. Magisk? it sound cool, I´ll take 4, thanks
Strange, things start going badly: The nokia 3.2 goes crazy and you just have fastboot. You manage to have twrp again thanks to the command fastboot flash boot twrp-3.2-dpl-00eea
Buuuuuuut you cannot install img nor zip files from sdcard using install options, then you discover that there is /sdcard an /external_sdcard¡¡¡ but it does not matter, file is corrupted, even drinking bleach does not improves the situation. Yo cannot install lineage-17.1-20200413-UNOFFICIAL-treble_arm64_avN. img or .zip (ahhhh it is RAR, so I have to change the extension to zip? maybe the system folder?) and you do not even know if you are arm64 a/b or just arm or legs.
You try to install system-quack-arm-ab-vanilla via adb push commands or fastboot commands, you fight with qualcomm drivers, the qfil tool, with not command found little android robot message, your system is corrupt message, go to see google nokia page (why? they are the enemy who bloats my phone!!!) you do not even know if you were in andorid 10 or 9 or 1909? You start filling up your desktop with images boot.img, .exe files OST LA bizarre programme... You try to open the nokia 3.2 to search 2 pins to enable eld supermode-mode with no chance 'cause you are not strong enough and it is really well ... glued? MAybe if I pay someone else tou fix it? 140 euros... 120 dollars, no, wait it is reaaaaaly expensive¡¡¡
REAL HINT
Have a try to download HMDSW_DPL_sprout-015B-0-00WW-B01 and search for boot vbmeta and other .img files and flash them manually via fastboot, if you are lucky as me, you may fix the self provocated prob:
PS C:\Users\ike\Desktop> cd platform-tools-new PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img < waiting for any device >
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash boot \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\boot.img Sending 'boot' (65536 KB) OKAY [ 2.072s]
Writing 'boot' OKAY [ 0.620s]
Finished. Total time: 2.692s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash custom \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\custom.img Sending 'custom' (6204 KB) OKAY [ 0.203s]
Writing 'custom' OKAY [ 0.062s]
Finished. Total time: 0.282s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash persist \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\persist.img Sending 'persist' (32768 KB) OKAY [ 1.038s]
Writing 'persist' OKAY [ 0.315s]
Finished. Total time: 1.354s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash system \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\system.img Sending sparse 'system' 1/6 (523260 KB) OKAY [ 16.927s]
Writing 'system' OKAY [ 6.093s]
Sending sparse 'system' 2/6 (523260 KB) OKAY [ 16.899s]
Writing 'system' OKAY [ 6.657s]
Sending sparse 'system' 3/6 (523260 KB) OKAY [ 16.888s]
Writing 'system' OKAY [ 5.328s]
Sending sparse 'system' 4/6 (492416 KB) OKAY [ 15.869s]
Writing 'system' OKAY [ 6.127s]
Sending sparse 'system' 5/6 (502344 KB) OKAY [ 16.201s]
Writing 'system' OKAY [ 4.613s]
Sending sparse 'system' 6/6 (24680 KB) OKAY [ 0.793s]
Writing 'system' OKAY [ 1.132s]
Finished. Total time: 119.152s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash userdata \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\userdata.img Sending 'userdata' (1268 KB) OKAY [ 0.031s]
Writing 'userdata' OKAY [ 0.031s]
Finished. Total time: 0.079s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vbmeta \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vbmeta.img Sending 'vbmeta' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot flash vendor \Users\ike\Desktop\Nokia_3.2_TA-1156_HMDSW_DPL_015B-0-00WW-B01_QFIL\Firmware\vendor.img Sending 'vendor' (424560 KB) OKAY [ 13.363s]
Writing 'vendor' OKAY [ 3.931s]
Finished. Total time: 17.497s
PS C:\Users\ike\Desktop\platform-tools-new> ./fastboot reboot Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
PS C:\Users\ike\Desktop\platform-tools-new>
I'm willing to help, as far as I have to stay home because of a biological hacking. And if you do not know what are you doing or you are not confident, do not do it. Thanks
hello
can you please explain step by step?
thank you
kntb said:
hello
can you please explain step by step?
thank you
Click to expand...
Click to collapse
First tell me what have you done so far
Hi
Thanks for guide
but I am unable boot after following all above steps
Just as a tip: I once got mine soft-bricked (that was a scary one. No partitions, can't flash, boot, or erase anything at all, even saw the linux penguin logo instead of "Android One"), but after lots of googling i decided to check my active slot, turned out it was something like "UNAVAILABLE" (or so)
So I just set my active slot to A (or B, doesn't matter) and I recovered everything.
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> adb devices
adb server version (31) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
fa9bd412 device
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> adb devices
List of devices attached
fa9bd412 device
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> adb reboot bootloader
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> fastboot devices
fa9bd412 fastboot
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash recovery twrp-3.2.3-1-miui.blog-whyred.img
Sending 'recovery' (36536 KB) OKAY [ 0.980s]
Writing 'recovery' FAILED (remote: 'Anti-rollback check failed')
fastboot: error: Command failed
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash antirbpass dummy.img
Sending 'antirbpass' (8 KB) OKAY [ 0.010s]
Writing 'antirbpass' OKAY [ 0.000s]
Finished. Total time: 0.020s
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> fastboot flash recovery twrp-3.2.3-1-miui.blog-whyred.img
Sending 'recovery' (36536 KB) OKAY [ 0.987s]
Writing 'recovery' OKAY [ 0.000s]
Finished. Total time: 0.987s
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools> fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
PS C:\Users\USER\Desktop\Redmi Note 5\platform-tools_r30.0.4-windows\platform-tools>
After i done it, my red mi note 5 cant access twrp, can someone pro tell me any problem?
Thanks in advance
After flashing completes
Don't disconnect the phone
Just one more thing
In fast boot mode
Type cmd screen in following
fastboot boot recovery.img
RECOVERY IMAGE NAME IN YOUR REC. IMG
Hello guys, I am trying to root my device for the first time.
Version is MIUI 13.0.5, Bootloader and MIUI unlocked.
I've followed youtube video.
Now my device has failed to boot a lot of times. Now when I turn on the device it goes to fastboot.
What I've done is below
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.032s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot flash boot magisk_patched-23000_74Ls8.img
Sending 'boot_b' (131072 KB) OKAY [ 3.181s]
Writing 'boot_b' OKAY [ 0.639s]
Finished. Total time: 3.839s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.003s
Boot failed, and I tried again.
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.038s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot flash boot magisk_patched-23000_74Ls8.img
Sending 'boot_a' (131072 KB) OKAY [ 4.603s]
Writing 'boot_a' OKAY [ 0.639s]
Finished. Total time: 5.382s
C:\Users\zxxzy\Desktop\platform-RootRN10_Miui13-0-5>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.003s
What do I have to do from now?
Can I still download other diffrent magisk patched image file and try it again?
Or do I have to fix my device first and challenge this again?
I've downloaded this now: mojito_global_images_V13.0.5.0.SKGMIXM_20220209.0000.00_12.0_global_36ff0ca7ff.tgz
I am currently confused to what to do.
I'd appreciate if you can give me any advice or tips. Thank you.
I felt like that I need to flash official firmware.
So I did it with MiFlash. But it says "Missmatching image and device".
How do I find correct image for my device when I can't boot?
Since firmware files are quite heavy, I can't download and try all.
What I know is that It was MIUI 13.0.5 Global and Android 12 when I tried to root it.
What I have found by IMEI i:
Description: Redmi Note 10 JE Chrome Silver 4 RAM 64 ROM
IMEI: 868096051729159
Brand: Xiaomi Communications Co Ltd
Model: XIG02
Name: XIG02
Purchase Country: Japan
Production Date: 2021-12-10 16:18:19
Does anybody know what is the correct image for my device?
Ok nevermind this thread. I found out that my device isn't Redmi Note 10. It is Remi Note 10 5G.
can i have a stock rom ive lost mine please help