help!!!! Venue 8 3840 - Dell Venue
I used the files from dell opensource and did the bootloader unlock and flashed a rooted boot image and now my tablet wont load to the os. it juszt goes to a black screen that say [email protected]:/ in upper left hand corner? I dont know what to do now. help!
It appears that you are trying to root the device. Please review [GUIDE] How to root Android 4.4.4 on the Dell Venue 3840
(Merrifield) Tablet
You may post there if you need additional information.
I did
Perseus said:
It appears that you are trying to root the device. Please review [GUIDE] How to root Android 4.4.4 on the Dell Venue 3840
(Merrifield) Tablet
You may post there if you need additional information.
Click to expand...
Click to collapse
I did go there and used those instructions. and the file that was provided. thats when it all happened. I have since flashed the boot.img from opensource back onto it and it works again. and used kingo root program. so it is showing rooted. but now I see that I am no longer running kitkat 4.4.4 but kitkat 4.4.2. I want to upgrade back but I am having the hardest time finding roms for my tablet. and I notice that so much of the main stuff like google play services take way too much ram, leaving me with barely 200 mb ram left to work with. and its a 1 gb. hmmm and I wanted to change my recovery to clockworkmod but it says my device isnt supported yet. I really am coming against roadblocks to optimizing the tablet. I cant even run my fb games cuz they wont sign into fb. they just keep restarting. grrrr any thoughts or ideas? thanks. also I could never get xfstk to work.
xFSTK downloader
I am trying to follow the tutorial but the xFSTK downloader is not working. It says "Details: No provisioning activities in progress..."
Anyone know what could be causing this issue?
Thanks in advance,
tomasro27 said:
I am trying to follow the tutorial but the xFSTK downloader is not working. It says "Details: No provisioning activities in progress..."
Anyone know what could be causing this issue?
Thanks in advance,
Click to expand...
Click to collapse
Post a screenshot of your computer showing this message.
turn off device
plug in
hit begin button
press volume up and power
takes like 3-5 seconds and goes as told to?
Perseus said:
I will request to have this thread moved to appropriate forum so other experts for that device may be of help.
Click to expand...
Click to collapse
Hi Perseus,
I am wondering if you know where this thread has been moved thus I could check for more updates. I have the same issue after following this - http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Presently my tablet goes black and I can see only "[email protected]:/" on top left.
Thanks!
3480
You can always flash back the original rom 4.4.4
https://www.androidfilehost.com/?fid=95784891001602440
did you manage to get your tab rooted with kingo on 4.4.2.
hamzilla said:
Hi Perseus,
I am wondering if you know where this thread has been moved thus I could check for more updates. I have the same issue after following this - http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
Presently my tablet goes black and I can see only "[email protected]:/" on top left.
Thanks!
Click to expand...
Click to collapse
---------- Post added at 11:39 AM ---------- Previous post was at 11:11 AM ----------
You have to select those 4 files downloaded from here (opensource.dell.com/releases/Venue_8_3840_Merrifield/developer-edition/A195/OTA/)
FW DnX= dnx_fwr_*.bin
IFWI= ifwi_*.bin
OS DnX= dnx_osr_*.bin
OS Image= droidboot.img.POS.bin
then put your tablet into fast boot mode
1. Enable fastboot mode
1) Open “xFSTK Downloader 1.5.1”.
2) Select the second “MRD AO/BO + MOOR AO + CRC” tab as the following................................
tomasro27 said:
I am trying to follow the tutorial but the xFSTK downloader is not working. It says "Details: No provisioning activities in progress..."
Anyone know what could be causing this issue?
Thanks in advance,
Click to expand...
Click to collapse
HELP
after writing system in fastboot mode this gets me error
C:\Users\home\Desktop\Venue 8 1.22>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 1.016s]
finished. total time: 1.016s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash /tmp/partition.tbl partition.t
bl
sending '/tmp/partition.tbl' (1 KB)
fname=partition.tbl...
1 KB / 1 KB
OKAY [ 0.766s]
writing '/tmp/partition.tbl'...
OKAY [ 1.031s]
finished. total time: 1.797s
C:\Users\home\Desktop\Venue 8 1.22>fastboot oem partition /tmp/partition.tbl
...
OKAY [ 1.156s]
finished. total time: 1.156s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase system
erasing 'system'...
OKAY [ 55.253s]
finished. total time: 55.253s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase cache
erasing 'cache'...
OKAY [ 9.079s]
finished. total time: 9.079s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase data
erasing 'data'...
OKAY [ 26.158s]
finished. total time: 26.158s
C:\Users\home\Desktop\Venue 8 1.22>fastboot erase logs
erasing 'logs'...
OKAY [ 11.329s]
finished. total time: 11.344s
C:\Users\home\Desktop\Venue 8 1.22>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.984s]
finished. total time: 0.984s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash boot boot.img
sending 'boot' (8342 KB)
fname=boot.img...
8342 KB / 8342 KB
OKAY [ 1.235s]
writing 'boot'...
OKAY [ 1.422s]
finished. total time: 2.657s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash fastboot droidboot.img
sending 'fastboot' (11114 KB)
fname=droidboot.img...
11114 KB / 11114 KB
OKAY [ 1.375s]
writing 'fastboot'...
OKAY [ 1.594s]
finished. total time: 2.985s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash recovery recovery.img
sending 'recovery' (10202 KB)
fname=recovery.img...
10202 KB / 10202 KB
OKAY [ 1.313s]
writing 'recovery'...
OKAY [ 1.531s]
finished. total time: 2.860s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash system system.img
sending 'system' (728453 KB)
fname=system.img...
102400 KB / 728453 KB
204800 KB / 728453 KB
307200 KB / 728453 KB
409600 KB / 728453 KB
512000 KB / 728453 KB
614400 KB / 728453 KB
716800 KB / 728453 KB
728453 KB / 728453 KB
OKAY [ 50.565s]
writing 'system'...
OKAY [ 45.752s]
finished. total time: 96.317s
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash splashscreen_7 oemlogo_7.bin
error: cannot get size of 'oemlogo_7.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash splashscreen_8 oemlogo_8.bin
error: cannot get size of 'oemlogo_8.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash dnx dnx_fwr_0003_20CA_YT2_TB2_
signed.bin
error: cannot get size of 'dnx_fwr_0003_20CA_YT2_TB2_signed.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash dnx dnx_osr_0003_20CA_YT2_TB2_
signed.bin
error: cannot get size of 'dnx_osr_0003_20CA_YT2_TB2_signed.bin'
C:\Users\home\Desktop\Venue 8 1.22>fastboot flash ifwi for_product_ifwi_0003_20C
A_YT2_TB2_signed.bin
error: cannot get size of 'for_product_ifwi_0003_20CA_YT2_TB2_signed.bin'
C:\Users\home\Desktop\Venue 8 1.22>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Renz Kell said:
HELP
after writing system in fastboot mode this gets me error
Click to expand...
Click to collapse
It's been a while since I had those tablets I had three of them I remember having a similar problem I tried lots of times to reflash so I started over I redownload the tablets images again and the Odin and I dont know which one was at fault but that did the trick also made sure I was using 7zip on my PC rar or zip won't work 7zip I seem to recall having a big issue there as the images I downloaded were zipped up and I had to convert to 7zips to work anyways I hope that helps a little good luck
Related
Dell Venue 7 3740 Totally Bricked
I have run multiple bat files at the tablet and as far as I can get is either the Droidboot loop or to the recovery mode where I run Super SU off the SD card and reloops to droidboot. Here is my bat file output: fastboot oem start_partitioning fastboot flash /tmp/partition.tbl partition.tbl fastboot oem partition /tmp/partition.tbl fastboot erase system fastboot erase cache fastboot erase data fastboot erase logs fastboot oem stop_partitioning fastboot flash boot boot.img fastboot flash fastboot droidboot.img fastboot flash recovery recovery.img fastboot flash system system.img fastboot flash splashscreen_7 oemlogo_7.bin fastboot flash splashscreen_8 oemlogo_8.bin fastboot flash dnx dnx_fwr_PRQ.bin fastboot flash ifwi for_product_ifwi_PRQ.bin pause fastboot reboot This runs and creates: C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot oem start_partitioning ... (bootloader) Start partitioning OKAY [ 0.617s] finished. total time: 0.619s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot flash /tmp/partition.tbl partition.tbl sending '/tmp/partition.tbl' (1 KB) fname=partition.tbl... 1 KB / 1 KB OKAY [ 0.512s] writing '/tmp/partition.tbl'... OKAY [ 0.604s] finished. total time: 1.119s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot oem partition /tmp/partition.tbl ... FAILED (remote: GPT command failed ) finished. total time: 0.478s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot erase system erasing 'system'... FAILED (remote: unable to format) finished. total time: 0.996s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot erase cache erasing 'cache'... FAILED (remote: unable to format) finished. total time: 0.760s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot erase data erasing 'data'... FAILED (remote: unable to format) finished. total time: 0.775s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot erase logs erasing 'logs'... FAILED (remote: unable to format) finished. total time: 0.769s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot oem stop_partitioning ... (bootloader) Stop partitioning OKAY [ 0.626s] finished. total time: 0.628s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot flash boot boot.img sending 'boot' (9585 KB) fname=boot.img... 9585 KB / 9585 KB OKAY [ 1.155s] writing 'boot'... OKAY [ 0.863s] finished. total time: 2.022s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot flash fastboot droidboot.img sending 'fastboot' (11373 KB) fname=droidboot.img... 11373 KB / 11373 KB OKAY [ 1.155s] writing 'fastboot'... OKAY [ 0.912s] finished. total time: 2.071s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot flash recovery recovery.img sending 'recovery' (11449 KB) fname=recovery.img... 11449 KB / 11449 KB OKAY [ 1.152s] writing 'recovery'... OKAY [ 0.893s] finished. total time: 2.048s C:\Users\Chris\Downloads\ANDROID2\YTP802A119500-2014-07-16-22-3\images-YTP802A11 9500>fastboot flash system system.img sending 'system' (1282554 KB) fname=system.img... 102400 KB / 1282554 KB 204800 KB / 1282554 KB 307200 KB / 1282554 KB 409600 KB / 1282554 KB 512000 KB / 1282554 KB 614400 KB / 1282554 KB 716800 KB / 1282554 KB 819200 KB / 1282554 KB Failed to write to usb; ret=0 errno=31FAILED (status read failed (Too many links )) writing 'system'... FAILED (command write failed (No such device or address)) finished. total time: 62.219s Any advise?:good:
[help]where can i get this files in the error
please help me about this error how can I fix this error My Model is Dell Venue 8 3840 C:\Users\home\Desktop\Venue 8 1.22>fastboot oem start_partitioning ... (bootloader) Start partitioning OKAY [ 1.016s] finished. total time: 1.016s C:\Users\home\Desktop\Venue 8 1.22>fastboot flash /tmp/partition.tbl partition.t bl sending '/tmp/partition.tbl' (1 KB) fname=partition.tbl... 1 KB / 1 KB OKAY [ 0.766s] writing '/tmp/partition.tbl'... OKAY [ 1.031s] finished. total time: 1.797s C:\Users\home\Desktop\Venue 8 1.22>fastboot oem partition /tmp/partition.tbl ... OKAY [ 1.156s] finished. total time: 1.156s C:\Users\home\Desktop\Venue 8 1.22>fastboot erase system erasing 'system'... OKAY [ 55.253s] finished. total time: 55.253s C:\Users\home\Desktop\Venue 8 1.22>fastboot erase cache erasing 'cache'... OKAY [ 9.079s] finished. total time: 9.079s C:\Users\home\Desktop\Venue 8 1.22>fastboot erase data erasing 'data'... OKAY [ 26.158s] finished. total time: 26.158s C:\Users\home\Desktop\Venue 8 1.22>fastboot erase logs erasing 'logs'... OKAY [ 11.329s] finished. total time: 11.344s C:\Users\home\Desktop\Venue 8 1.22>fastboot oem stop_partitioning ... (bootloader) Stop partitioning OKAY [ 0.984s] finished. total time: 0.984s C:\Users\home\Desktop\Venue 8 1.22>fastboot flash boot boot.img sending 'boot' (8342 KB) fname=boot.img... 8342 KB / 8342 KB OKAY [ 1.235s] writing 'boot'... OKAY [ 1.422s] finished. total time: 2.657s C:\Users\home\Desktop\Venue 8 1.22>fastboot flash fastboot droidboot.img sending 'fastboot' (11114 KB) fname=droidboot.img... 11114 KB / 11114 KB OKAY [ 1.375s] writing 'fastboot'... OKAY [ 1.594s] finished. total time: 2.985s C:\Users\home\Desktop\Venue 8 1.22>fastboot flash recovery recovery.img sending 'recovery' (10202 KB) fname=recovery.img... 10202 KB / 10202 KB OKAY [ 1.313s] writing 'recovery'... OKAY [ 1.531s] finished. total time: 2.860s C:\Users\home\Desktop\Venue 8 1.22>fastboot flash system system.img sending 'system' (728453 KB) fname=system.img... 102400 KB / 728453 KB 204800 KB / 728453 KB 307200 KB / 728453 KB 409600 KB / 728453 KB 512000 KB / 728453 KB 614400 KB / 728453 KB 716800 KB / 728453 KB 728453 KB / 728453 KB OKAY [ 50.565s] writing 'system'... OKAY [ 45.752s] finished. total time: 96.317s C:\Users\home\Desktop\Venue 8 1.22>fastboot flash splashscreen_7 oemlogo_7.bin error: cannot get size of 'oemlogo_7.bin' C:\Users\home\Desktop\Venue 8 1.22>fastboot flash splashscreen_8 oemlogo_8.bin error: cannot get size of 'oemlogo_8.bin' C:\Users\home\Desktop\Venue 8 1.22>fastboot flash dnx dnx_fwr_0003_20CA_YT2_TB2_ signed.bin error: cannot get size of 'dnx_fwr_0003_20CA_YT2_TB2_signed.bin' C:\Users\home\Desktop\Venue 8 1.22>fastboot flash dnx dnx_osr_0003_20CA_YT2_TB2_ signed.bin error: cannot get size of 'dnx_osr_0003_20CA_YT2_TB2_signed.bin' C:\Users\home\Desktop\Venue 8 1.22>fastboot flash ifwi for_product_ifwi_0003_20C A_YT2_TB2_signed.bin error: cannot get size of 'for_product_ifwi_0003_20CA_YT2_TB2_signed.bin' C:\Users\home\Desktop\Venue 8 1.22>pause Press any key to continue . . . Click to expand... Click to collapse
nokia 3.2 unbrick alt. method
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.
Please help with P20 lite , can not flash fw, board sw booting OK
Hi, Can someone please help me with fix of my P20 lite dual? I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹ The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly" Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7 Factory reset and cache wipe did not help. Any attempt to SD or USB update via recovery failed, always got "Install failed" So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP. No luck, phone was in fastboot mode only or bootloops. Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0) With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK. So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"? Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message. From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found. Or is there some easy way to flash to official ? Or did I messed up some system files that need to be fixed? PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts. Can be this a problem? (I hope not) Thank you for any ideas !
hdano said: From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found. Click to expand... Click to collapse HwOTA will won't help you - it cannot identify the device in this state... (model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB ) In fastboot mode run commands: fastboot oem get-build-number fastboot oem get-product-model fastboot getvar vendorcountry fastboot oem oeminforead-CUSTOM_VERSION fastboot oem oeminforead-SYSTEM_VERSION and post the results.
-Alf- said: HwOTA will won't help you - it cannot identify the device in this state... (model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB ) In fastboot mode run commands: fastboot oem get-build-number fastboot oem get-product-model fastboot getvar vendorcountry fastboot oem oeminforead-CUSTOM_VERSION fastboot oem oeminforead-SYSTEM_VERSION and post the results. Click to expand... Click to collapse C:\adb>fastboot oem get-build-number ... (bootloader) :ANE-BD 1.0.0.40(log) OKAY [ 0.011s] finished. total time: 0.013s C:\adb> C:\adb>fastboot oem get-product-model ... (bootloader) ANE OKAY [ 0.011s] finished. total time: 0.013s C:\adb> C:\adb>fastboot getvar vendorcountry getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo) finished. total time: 0.022s C:\adb> C:\adb>fastboot oem oeminforead-CUSTOM_VERSION ... FAILED (remote: The reason of failed input oem_nv_item error!) finished. total time: 0.018s C:\adb> C:\adb>fastboot oem oeminforead-SYSTEM_VERSION ... FAILED (remote: Read oeminfo failed!) finished. total time: 0.021s
hdano said: any ideas Click to expand... Click to collapse maybe the following will help you: - Download TWRP Service ROM oeminfo and Recovery_ramdisk for Oreo - Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT. - Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP - Install TWRP over eRecovery (only read the principle, not download links) - boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it. - Go back to the main TWRP's menu, select Reboot and Turn off. - Use three button combo and try to install Service ROM . Note: you do everything at your own risk, I hope that's clear
Hi Alf, thanks for reply, worked like a charm ! Phone booted in official rom, was working well. But.. If I try to download OTA update from menu, it shows me update to ANE-LX1 8.0.0.174(C432)-FULL size 2.92GB , but after downloading phone shows install error. I did factory reset and cache clear, same result, can not install. So I downloaded to SD card latest sw Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru].zip but verify goes 5% then 6% then back to 5%, then 6% then shows "install failed" After attempt to update by *#*#2846579#*#* from menu, phone did the same, 5% 6% 5% 6% "install failed", but after reboot I have attached photo error :-( Now not booting again, stuck in this error. So how can I update to some new sw ? Do I have to use some special version to go higher? Or is it some other problem? BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet :-O
hdano said: BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet Click to expand... Click to collapse Yes, service ROM lock the bootloader , it's normal. hdano said: FRP locked, Click to expand... Click to collapse You can unlock FRP manually in Developer options - "Enable OEM unlock". Run again fastboot commands and post results.
C:\adb>fastboot oem get-build-number ... (bootloader) :ANE-LX1 8.0.0.126(C432) OKAY [ 0.011s] finished. total time: 0.012s C:\adb>fastboot oem get-product-model ... (bootloader) ANE-LX1 OKAY [ 0.009s] finished. total time: 0.010s C:\adb>fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.010s C:\adb>fastboot oem oeminforead-CUSTOM_VERSION ... FAILED (remote: Read oeminfo failed!) finished. total time: 0.020s C:\adb>fastboot oem oeminforead-SYSTEM_VERSION ... (bootloader) :ANE-LX1 8.0.0.126(C432) OKAY [ 0.012s] finished. total time: 0.013s
hdano said: C:\adb>fastboot oem get-build-number ... (bootloader) :ANE-LX1 8.0.0.126(C432) OKAY [ 0.011s] finished. total time: 0.012s C:\adb>fastboot oem get-product-model ... (bootloader) ANE-LX1 OKAY [ 0.009s] finished. total time: 0.010s C:\adb>fastboot getvar vendorcountry vendorcountry: hw/eu finished. total time: 0.010s C:\adb>fastboot oem oeminforead-CUSTOM_VERSION ... FAILED (remote: Read oeminfo failed!) finished. total time: 0.020s C:\adb>fastboot oem oeminforead-SYSTEM_VERSION ... (bootloader) :ANE-LX1 8.0.0.126(C432) OKAY [ 0.012s] finished. total time: 0.013s Click to expand... Click to collapse Okay, now boot into eRecovery (not Recovery) and select option Download latest version and recovery.
This ***** sucks :-(
hdano said: This ***** sucks Click to expand... Click to collapse Try to install .174 Service ROM via dload method. If you get Install failed error again, then you need unlock bootloader (if it's possible) and flash some partitions in fastboot. You can use this tutorial . Use downloaded .174 ROM. Extract and flash - kernel -ramdisk - recovery_ramdisk - system - cust Note: cust.img can be found in update_ane-L21_hw_eu Reboot and turn off the phone, then flash .174 Service ROM or try update via eRecovery.
C:\adb>fastboot flash kernel KERNEL.IMG target reported max download size of 471859200 bytes sending 'kernel' (24576 KB)... OKAY [ 0.893s] writing 'kernel'... OKAY [ 0.388s] finished. total time: 1.286s C:\adb>fastboot flash ramdisk RAMDISK.IMG target reported max download size of 471859200 bytes sending 'ramdisk' (16384 KB)... OKAY [ 0.602s] writing 'ramdisk'... OKAY [ 0.075s] finished. total time: 0.681s C:\adb>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG target reported max download size of 471859200 bytes sending 'recovery_ramdisk' (32768 KB)... OKAY [ 1.208s] writing 'recovery_ramdisk'... OKAY [ 0.169s] finished. total time: 1.381s C:\adb>fastboot flash system SYSTEM.IMG target reported max download size of 471859200 bytes sending sparse 'system' 1/8 (460799 KB)... OKAY [ 19.946s] writing 'system' 1/8... OKAY [ 3.866s] sending sparse 'system' 2/8 (424020 KB)... OKAY [ 17.042s] writing 'system' 2/8... OKAY [ 2.164s] sending sparse 'system' 3/8 (458375 KB)... OKAY [ 18.384s] writing 'system' 3/8... OKAY [ 2.219s] sending sparse 'system' 4/8 (460418 KB)... OKAY [ 18.557s] writing 'system' 4/8... OKAY [ 2.213s] sending sparse 'system' 5/8 (425536 KB)... OKAY [ 17.164s] writing 'system' 5/8... OKAY [ 2.157s] sending sparse 'system' 6/8 (457971 KB)... OKAY [ 19.231s] writing 'system' 6/8... OKAY [ 2.855s] sending sparse 'system' 7/8 (460016 KB)... OKAY [ 19.003s] writing 'system' 7/8... OKAY [ 3.147s] sending sparse 'system' 8/8 (192362 KB)... OKAY [ 7.791s] writing 'system' 8/8... OKAY [ 1.015s] finished. total time: 156.792s C:\adb>fastboot flash cust CUST.IMG target reported max download size of 471859200 bytes sending 'cust' (139283 KB)... OKAY [ 5.096s] writing 'cust'... OKAY [ 0.794s] finished. total time: 5.894s C:\adb>fastboot reboot rebooting... Now the only I can get is this, no way to get in eRecovery
hdano said: Now the only I can get is this, no way to get in eRecovery Click to expand... Click to collapse Chinese??? Wow... As I said before, -Alf- said: turn off the phone, then flash .174 Service ROM Click to expand... Click to collapse Have you tried bro?
-Alf- said: Chinese??? Wow... As I said before, Have you tried bro? Click to expand... Click to collapse how? I can not get in eRecovery, only that chinese recovery or what it is....
hdano said: how? I can not get in eRecovery, only that chinese recovery or what it is.... Click to expand... Click to collapse Service ROM has nothing to do with eRecovery.
As the bootloader got locked, I had to do the whole procedure again, Board sw 1.0.0.39 , and -Alf- said: Download TWRP Service ROM oeminfo and Recovery_ramdisk for Oreo - Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT. - Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP - Install TWRP over eRecovery (only read the principle, not download links) - boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it. - Go back to the main TWRP's menu, select Reboot and Turn off. - Use three button combo and try to install Service ROM . Click to expand... Click to collapse But I can not get it to work state, 3 button combo always fails. Can I just simply flash all needed files by fastboot ot TWRP ? What are all the necessary files for phone to boot up? - kernel -ramdisk - recovery_ramdisk - system - cust what else? Can I just simply flash some custom ROM that will boot up after TWRP flash ? BTW, why it should not be possible to directly flash erecovery from fastboot? For me worked.. C:\adb>fastboot flash erecovery_ramdisk TWRP-oreo-smart.img target reported max download size of 471859200 bytes sending 'erecovery_ramdisk' (24790 KB)... OKAY [ 0.660s] writing 'erecovery_ramdisk'... OKAY [ 0.128s] finished. total time: 0.796s
hdano said: what else? Click to expand... Click to collapse Nothing. But keep in mind, that "writing OKAY" does not mean that the file is actually installed (it is too long story to tell why...). hdano said: BTW, why it should not be possible to directly flash erecovery from fastboot? For me worked.. Click to expand... Click to collapse Running working stock firmware it's impossible.
hdano said: Hi, Can someone please help me with fix of my P20 lite dual? I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹ The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly" Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7 Factory reset and cache wipe did not help. Any attempt to SD or USB update via recovery failed, always got "Install failed" So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP. No luck, phone was in fastboot mode only or bootloops. Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0) With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK. So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"? Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message. From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found. Or is there some easy way to flash to official ? Or did I messed up some system files that need to be fixed? PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts. Can be this a problem? (I hope not) Thank you for any ideas ! Click to expand... Click to collapse I’ve exactly the same as your issue. But I’ve no service and dual iemis are right! What could be the problem, did you solve yours? Or even were you having same no service issue while you were on this case? My device originally is nova 3e ANE l-LX1 c185 dual sim and flashed oeminfo for c185 by editing the oeminfo for c432 and by using oeminfo tools. Also using howta8 to change oeminfo. It was changed ok to c185 but still no service and software not installed. I used build 160 because it’s the only have 3 files, it was installed from hisuite document/hisuite/rom folder
Question Failed to boot
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