Develop Bugs

[Q] need help rooting dinc2 please

so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[

simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder

In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.

im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes

Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk

nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally

drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.

how did you get it too work???

simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....

the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk

simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!

yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod

ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2

I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.

nothing is working out for me this is not fun

same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.

simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.

yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that

[Tutorial][Marvelc]How To Solve Common Marvelc Issues

Marvelc Problem Solving​We all have problems with our Marvelc, so why isn't there a guide for it? There is.
If you're having issues, check out my guide at http://teamblueridge.com/marvelc-problem-solving/ for how to fix the most common issues.
You don't have to live with a hard-to-manage Marvelc anymore.

Changelog:
May 24, 2012 10:12 PM EDT
Added a link to vbhtt's tutorial for solving different brick types.
July 19, 2012 8:04 AM EDT
Revised guide to say that all Marvelc HBOOTs can be S-OFF'd.
August 7, 2012 3:48 PM EDT
Revised to say how to fix <remote: not allowed>
Explain issues with Three-Vibe Brick
August 7, 2012 4:59 PM EDT
Link to guide on Team BlueRidge site.

Three Vibe Brick
So far, no 100% guaranteed method has been found to cure the infamous three-vibe brick. Your phone is presently in Qualcomm Diagnostics Mode
Click to expand...
Click to collapse
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.

vbhtt said:
I have posted a tutorial to unbrick a wfs, and i also posted how to get out of the three vibe brick. I don't know if it really works (because i don't have a marvelc) but a user has reported it working.
Click to expand...
Click to collapse
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)

kalaker said:
I apologize. I heard that in some cases, not even that could fix it. I meant to say that there is not a fix that works in 100% of scenarios (my three-vibe could not be rectified without the use of JTAG, which I did not want to get into here.)
Click to expand...
Click to collapse
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!

vbhtt said:
There's no need to apologise my friend I was not trying to tell you that you are wrong, i was trying to help you!!!!
Click to expand...
Click to collapse
Oh! I understand that! I was just trying to provide a common method that I had read. I understand you weren't saying I was wrong. I was actually about to add something about your tutorial, but I had another project I was working on.
Yes, my goal is that this can be a place to help most Marvelc users solve most of their problems with as many alternatives as possible while still being fairly noob-friendly.
Thank you for reminding me of your tutorial as it slipped my mind while I was writing this in the beginning!

Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks

CoLlisiionZz said:
Hi I read your thread and I can some what understand it Hopefully you can shed some light on my situation My marvelc htc wfs is stuck at the white htc screen and won't go any farther I've flashed and reflashed roms ive always formatted data and other necessary items like I should. I did flash one rom that worked but wasn't happy with it, it worked fine but was going for cm7 now that I've read at least 100 posts I come to understand its not to reliable anyway and was just wanting anything to work stock rom would be great I understand I may need to update my CWM my current version is 5.0.2.6 I've read 5.0.2.8 was more stable for the wfs but I have no clue how to flash it when I currently have no rom on my phone. this is what my hboot says currently
***unlocked***
marvelc evt1 ship s-off RL
HBOOT-1.09.0000
Microp-0354
Radio-0.94.00.0824
Hopefully the info will help you out. any help would be so grateful thanks
Click to expand...
Click to collapse
What you need to do is download ClockWork Mod 5.0.2.8 from http://download.clockorkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.img and then rename it to recovery.img. If you're on Windows, put it into the same directory as your ADB and fastboot commands. Next, you'll need to put your phone in fast boot mode. Go into HBOOT and choose "Fastboot" by scrolling with the volume keys and selecting with the power key.
Connect your phone to your computer.
Next, depending on the OS of your computer, launch Command Prompt (Windows) or Terminal (Linux/Mac). Navigate to the directory with recovery.img. Now type: fastboot flash recovery recovery.img and then power off your phone when it's done.
Now boot into recovery. Go to HBOOT and choose recovery. Now, get on your computer and find a ROM that you like (something fairly stable). Download it. Find Simon's super wipe. Download it.
Connect your phone to your computer (if you removed it earlier).
In recovery, scroll to Mounts and Storage. Go to USB Connect or something similar (it will be near the bottom). Then on your computer, place your desired rom and the super wipe. Remove the phone from your computer and choose "Go back" on your phone. Go back to the main menu.
Backup.
Flash the super wipe. Then flash your ROM.
Go back to the main menu and reboot.
Sent from my NookColor using XDA

Great!! thanks this seems legit I will try this as soon as I get to my PC uhm I have windows btw and have no clue how to put the cwm into my adb / fastboot directory but I will search more about it when possible thanks for your help

Well, if you're on Windows, you should have a directory like C:\Android\ or something like that.
If you're on a Mac just do:
Code:
fastboot flash recovery /path/to/recovery.img
If you want to have the file anywhere on Windows, you still need to have fastboot somewhere and then do the same command I just typed above.
For more instructions, follow the instructions in the guide under "I can't flash a custom recovery"

Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?

CoLlisiionZz said:
Ok In your tutorial you say "go to the folder "tools" and launch "android". Download "Android SDK Platform-Tools" " when I try to launch android nothing happens only a black cmd: box will appear for a split second then goes away. The android I'm trying to launch in the tools folder is a Windows Batch File is this the correct file?
Click to expand...
Click to collapse
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.

kalaker said:
Do you have Java installed? http://www.java.com/en/download/manual.jsp
Also, you should get the JDK: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1637583.html
See if that works.
Click to expand...
Click to collapse
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.

CoLlisiionZz said:
I downloaded java and the JDK file installed etc
Tried unzipping the sdk file again then went to the android tried to launch and same result I'm on (windows 7 64x bit).
I downloaded something when I was searching forums that kind of sounded like the file I'm suppose to be downloading the platform tools but there called android tools instead here's the files in it below
adb
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot
Do you think this is the same thing? I've flashed roms on the Optimus V before so I am a little familiar with the platform tools but when i downloaded them last time I just have to go into SDK manager.
Click to expand...
Click to collapse
That's what you want. Move them into a folder at the root of your hard drive (C:\) called "Android". (C:\Android\)

Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?

CoLlisiionZz said:
Okay great!! I went ahead and tried doing some command prompts and this is what I typed
I'm in the android file it currently says
C:\Android>
I tried typing "adb reboot bootloader" and it says
*daeon not running. starting it now on port 5037 *
*daemon started successfully *
error: device not found
now my phone is connected to my PC its in fastboot mode it says in red on my phone FASTBOOT USB so I know for sure it's connected is there something wrong?
Click to expand...
Click to collapse
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.

kalaker said:
You're already in the bootloader. Fastboot is the bootloader, or at least part of it. You have use fastboot commands in fastboot.
Click to expand...
Click to collapse
Okay that's what I kind of thought so I tried typing fastboot flash recovery recovery.img
and it says
error: cannot load 'recovery.img'
it is placed in the same directory as the tools are too.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
Okay nvm I tried something and it worked!!!
I went and re downloaded your CWM on your tutorial and deleted the one I renamed and didn't rename it this time just kept it the way it was I then tried flashing it and success I'm now going to reboot my hboot and see if it worked but also I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on

CoLlisiionZz said:
Okay that's what I kind of thought so I tried typing I was searching forums and google but could not come across simmons super wipe... I will keep looking though but if you have time maybe throw a link on a post for me but thanks for helping me I hope it goes smooth from now on
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1598143
I'm glad to hear you got it working!

A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2

insink71 said:
A thought just occured that I may have overlooked in my many (unsuccessful) attempts of curing a sent-to-me 3 vibe...
Correct me if I'm wrong on this, but sd needs to be made a goldcard; so that PG76IMG.zip will auto-load...
Been a long time since I attempted but I don't remember if I checked the sd to make sure it was goldcard'd. I will go charge it up and test this new theory tomorrow (still sitting in a side-basket at work). Sometimes my mind takes a minute to put ALL the pieces together
Rob
Sent from my Marvelc using Tapatalk 2
Click to expand...
Click to collapse
Right, a Goldcard (unless one is S-OFF or ENG) will be required. However, achieving a goldcard requires ADB access to your phone. (The Simple GoldCard tool reads a file in /proc/*/*/ I believe to get the CID required for goldcard.) Now, ADB access is quite difficult with a bricked phone as you cannot boot into Android (or recovery) and to get S-OFF you would need to borrow the HTC Wildfire S (it MUST be a Wildfire S) to get the goldcard required.
Even with what I just said, depending on how bad your phone is bricked (Flashing a GSM RUU, for example), you may have a 100% bricked radio, thus resulting in an entirely bricked HBOOT not allowing you flash a PG76IMG.zip.
Another idea I have is that the Marvel is a PG761**** for the model number, and an incorrect RUU is the most common brick for Marvelc. What may be an issue is that the Marvelc is a PG762**** model number. The current files we have for un-bricking are Marvelc, but the android-info.txt for modelid says PG762000, therefore a GSM HBOOT (especially a locked, RUU HBOOT) would not take that file as it is for Marvelc.
What I think would be necessary is: a goldcard + a PG76IMG.zip with a GSM android-info.txt, but Marvelc radio, ROM, HBOOT, etc.
This is my idea on how we may need to do this. However, as the GSM HBOOT cannot get S-OFF without XTC-Clip which we can't use due to a lack of SIM card slot.
To get a 100% working-in-all-methods 3-Vibe Brick Recovery Method, we are waiting for the people in the S-OFF thread to get a full software S-OFF. However, even with that, we may still have issues...
I have spent a lot of time thinking about this, actually. (I'm a planner; not a dev :crying: so I can't be of much help with the dev part.) However, if it ever becomes a Team BlueRidge project to fix this type of brick (or a project by any group) I will be happy to plan (but not test just yet).
Since now we're moving into a very difficult and not-so-noob-friendly as I am intending for this thread to be, it may be a good idea to either start a new brainstorming thread or to PM or IRC or something.
Anyway, those are my thoughts.

[Q] B117 update - assert failed: apply_patch_check

Hi there,
for some time now I have been trying to update B116 to B117 getting the same error message every time:
View attachment 2311424
assert failed: apply_patch_check ("/system/app/HwCloudDrive.apk" ... )
E:Error in /sdcard/HwOUC/update.zip
(status 7)
I am guessing the update does not match the HwCloudDrive.apk (not sure, new to this). What have I tried:
1. Check the /system/app/HwCloudDrive.apk - not found in the folder, nor anywhere else on the phone. Searched the web, downloaded one apk, install failed for no reason (reason not stated, just that it failed)
2. Restoring factory settings several times
3. re-downloading many times
4. updating online as well as localy
So far nothing worked out. Some details about my phone:
Its P6-U06, android 4.2.2, baseband IMC1202_PENTA, kernel 3.0.8-00821, build B116SP01, bought in China, using New Zealand SIM (could this be a problem?)
Any help would be much appreciated
Thanks to all!

Same issue updating error
Hi! I'm stucked with the same problem, I have tried to update it from external, wipe all data but nothing is worked, did you find a way??
ouzoliny said:
Hi there,
for some time now I have been trying to update B116 to B117 getting the same error message every time:
View attachment 2311424
assert failed: apply_patch_check ("/system/app/HwCloudDrive.apk" ... )
E:Error in /sdcard/HwOUC/update.zip
(status 7)
I am guessing the update does not match the HwCloudDrive.apk (not sure, new to this). What have I tried:
1. Check the /system/app/HwCloudDrive.apk - not found in the folder, nor anywhere else on the phone. Searched the web, downloaded one apk, install failed for no reason (reason not stated, just that it failed)
2. Restoring factory settings several times
3. re-downloading many times
4. updating online as well as localy
So far nothing worked out. Some details about my phone:
Its P6-U06, android 4.2.2, baseband IMC1202_PENTA, kernel 3.0.8-00821, build B116SP01, bought in China, using New Zealand SIM (could this be a problem?)
Any help would be much appreciated
Thanks to all!
Click to expand...
Click to collapse

Hi there,
nope, I haven't found the way. I tried a few more time since the post, no change, still the same problem. I have posted the message on huawei support, no reply. I'm at the stage of no-trying anymore, waiting for the next update and see...
Mrpinkman said:
Hi! I'm stucked with the same problem, I have tried to update it from external, wipe all data but nothing is worked, did you find a way??
Click to expand...
Click to collapse

I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?

rutenio3 said:
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
Click to expand...
Click to collapse
up

rutenio3 said:
I have the same problem
apply_patch_check ("/ system / build.prop")
Is there any solution?
Click to expand...
Click to collapse
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.

extrem23 said:
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
Click to expand...
Click to collapse
I need more information.
Is very little information as to touch something random change.
A minitutorial would be nice.
thanks

i have the same problem
rutenio3 said:
I need more information.
Is very little information as to touch something random change.
A minitutorial would be nice.
thanks
Click to expand...
Click to collapse
assert faild: apply_patch_check("/system/app/MyBitCast.apk". "7e89b40472e4fe3d1459fb19f02b2901f281cea9".
"01c881b5cd2aad035329684eddd0471644914bb2")
update.zip is not correct

Format Sdcard And Try Again. If It Didnt Work Download Latest B125 And Try Again Hope This Works.

Please supply more info about this fix.
extrem23 said:
There is a non so straight forward way to get it though by editing the "updater-script" file in the [ROMFileName].zip
You will need to unzip, edit the file (remove the line) with notepad and zip it back.
I've able to make it works with P6's MIUI V5 Offline OTA update rom.
Click to expand...
Click to collapse
Please explain: what line should be erased from this file?
Thanks

rainbringer said:
Please explain: what line should be erased from this file?
Thanks
Click to expand...
Click to collapse
Yes please explain a little further. I am having update issues as well.
My Huuawei Ascend Mate MT1-U06 Found an OTA Update HwOUC, I downloaded it, and when I try to apply the update it fails.

[Q] Lg g3 D855 adb issues <no found solution>

Hi guys im unsure if you would call me a noob since ive been playing with androids and custom ops for a while, however my girlfriend purchased an lg d855 (stock as a rock)and "all of a sudden" it failed to reboot, now from what i have found it appears to be quite unusual for this to happen but common for the os to crash into a boot freeze or boot loop, i have no complete load of download mode, it comes up with the little blue dots and the picture of the phone or whatever the symbol is. i can get it into fastboot for use with the adb or fastboot apps, i have obtained the stock LAF.img for the 32gb variant, the issue is that after the phone is connected and ready to send operations
i send the command
c:\adb\fastboot erase recovery >
erasing recovery>
FAILED <remote: failed to erase partition>
and on the phone it says
<start>
fastboot: processing commands
fastboot: getvarartition-type: recovery
fastboot erase: recovery
partition getsize 16777216 bytes
erasing card: 0x48000:0x8000
error: command never completed
error: command timeout error
error: command completed with errors
failed to send erase grp start address
mmc erase failed
<end>
so the question, what the hell does that mean, also if i try other commands it also failes to complete them such as erasing the laf file and or replacing it, i feel like i am mostlikely not the only one with this issue, i do have all the correct drivers installed, using the adb that i have which is 1.3 and one that comes with a kit of the sdk tools and all that, i feel like it is a phone issue more than computer as its failing to erase the mmc, i am wondering if there is other commands i could put in the phone to figure this out or if anyone knows what it all means i would greatly appreciate any help Thanks guys an gals.

iv tried also to load a custom recovery but cant do that because it comes up with incomplete bootloader on the phone, is anyone even able to help? i have no idea what the hell i am doing and nobody seems interested to try and help me.

Same problem here
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx

ferreirix said:
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
Click to expand...
Click to collapse
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.

tallman43 said:
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
Click to expand...
Click to collapse
I can start to see the light with the tuto you recommended thank you so much !

Question Issues trying to go back from Xiaomi.eu to MIUI stock (on POCO F3). Help please!

Hello everyone:
Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.
Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.
I would appreciate, please, if you help me.
A greeting and thanks in advance.

Tukan41 said:
Hello everyone:
Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.
Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.
I would appreciate, please, if you help me.
A greeting and thanks in advance.
Click to expand...
Click to collapse
Try to follow this guide to the letter.
How to flash a stock rom [alioth]
Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...
forum.xda-developers.com

Hey! Thank you for the soon reply. I have read the tutorial quickly, but i will reread slowly as soon as i can. Anyway, i think that i have tried with all this and the errors persist. But, as i have said, i will re read slowly and let you know what happened with with my retry following your instructions.
Thanks a lot!

Put miflash and rom on local disk C.

Thx a lot for the help! I have tried these two options, and it gives me the "file is too large" error.

RollDload said:
Try to follow this guide to the letter.
How to flash a stock rom [alioth]
Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...
forum.xda-developers.com
Click to expand...
Click to collapse
Fiend, would yo be so kind to provide me the exact link to de file of "SDK platform tools", please? The page you gave me is a little bit chaotic. Thx in advance!

Tukan41 said:
Fiend, would yo be so kind to provide me the exact link to de file of "SDK platform tools", please? The page you gave me is a little bit chaotic. Thx in advance!
Click to expand...
Click to collapse
If you have followed my guide to the letter and it gives you an error again, try changing the USB port, or the cable, or with another pc, if it has intel cpu and win10 it is better. Try to download the rom again from one of the sites linked in the guide.
I have attached sdk for Windows:

RollDload said:
If you have followed my guide to the letter and it gives you an error again, try changing the USB port, or the cable, or with another pc, if it has intel cpu and win10 it is better. Try to download the rom again from one of the sites linked in the guide.
I have attached sdk for Windows:
Click to expand...
Click to collapse
Thx a lot for the file and for all your help. What do you think about "the file is too large" error? I have read over there that is relationed with Hard Disk FAT 32 format, but i have NTFS.
Thx in advnace.

Tukan41 said:
Thx a lot for the file and for all your help. What do you think about "the file is too large" error? I have read over there that is relationed with Hard Disk FAT 32 format, but i have NTFS.
Thx in advnace.
Click to expand...
Click to collapse
Honestly, this has never happened to me and it is the first time that I have ever heard this error. I know that the fat32 file system does not allow the storage of a single file larger than 4gb, but this does not seem to me to be the case. In addition to the advice I have already given you, such as downloading the rom again, or a different version, change usb port, cable, and do it all over again, you could try using the february 2021 version of miflash, I do not know what to think. It could also be a conflict on your pc, if you can't use another one try to create a small partition and install a clean version of win10 Otherwise I don't know ...

Thx a lot one more time, friend.
Do you think it could affect (if there is any difference) using cmd or using MI Flash? Do you think that wanting to close the bootloader or not can influence on the success flashing? Do you think it can influence to use MIUI GLOBAL or MIUI EEU, which is the one that corresponds to me, or not?

Tukan41 said:
Thx a lot one more time, friend.
Do you think it could affect (if there is any difference) using cmd or using MI Flash? Do you think that wanting to close the bootloader or not can influence on the success flashing? Do you think it can influence to use MIUI GLOBAL or MIUI EEU, which is the one that corresponds to me, or not?
Click to expand...
Click to collapse
No problem bro!
There is no difference between cmd and miflash, because miflash performs the same operations that the script on cmd does, I don't think that's the problem.
I don't think it even depends on closing the bootloader, also because it is a command that is done at the end of the ROM flash. (I wouldn't close it unless absolutely necessary. I advise you to do it only with the original rom of the phone, like if you bought it with global, close only with global and not with eea, it could go into brick, even if some have succeeded.)
I have changed region a couple of times, bought it with rom eea and flashed the global and went back to eea without problems (without blocking the bootloader) so it shouldn't cause any problems.
More than anything else, I think it's a conflict in your pc system, maybe in the drivers. I would try to make a partition in the hd and install win10 and everything you need for the flash and see if it works. What pc are you using?

Thx one more time for your help and patience (are you spanish or spanish speaker?).
I'm using a Huawei Matebook D, with an Inter(R) Core(TM) i5-7200U CPU @ 2.50GHz 2.70 GHz, 8,00 GB RAM Memory. I have never ever had any issue with the performance of my PC.
Anyway, yesterday night i followed your guide, firstly i tried the "1) How to flash a stock rom using miflash", but when i refreshed in order to check if MIFlash detected my Phone, a strange little window error appeared ("Unhandled exception from the application. If you click Continue, the application will ignore this error and try to continue. If you click Quit, the application will close immediately"). So, when if i clicked "Continue" and i tried to refresh again, the error reapeared, and when i clicked "Quit" MiFlash closed. I recognize that i didn't do the "Disable driver signature enforcement in windows" step (is it mandatory?).
Due to this unexpected error, i tried the way "2) How to flash a stock rom using cmd",with not doing, again, i recognize, the "Disable driver signature enforcement in windows". So when i flashed from the cmd, unlike all the precedent tries doing with this way, the rom started flashing succesfully. All seems to going perfectly, but when the process arrived to the 7/10 poing, i had an "super flash error" (actually, the cmd screen specified me one concrect error, but i was a little bit nervous and didn't copy it; i think was (or it was something like) the "sparcecrclist error", but i'm not very sure). The rom, then stopped flashing, the phone was blocked (as the other precedent failed times) at fastboot mode, and i could only recuperate it by flashing the Xiaomi.eu room.
It was very sad, because i really thought that in this time i would succeed. I don't really know what to do. I got really scared, because that "super flash error" terrified me, but fortunately nothing bad happened thanks to the succesfull flash of the Xiaomi.EU rom. I could flash the rom stock again, in order to copy here the exact error i had on "7/10" step, but that "super flash error", which i have never had, really scares me. It seems like you are my only help here and, anyway, following your guide has been has been the nearest point of installing the stock rom succesfully.
I would love to hear from you again.
***EDIT: that MIFlash error never happened to me preciously. I used the last version which was on the link of your guide.

Tukan41 said:
Thx one more time for your help and patience (are you spanish or spanish speaker?).
I'm using a Huawei Matebook D, with an Inter(R) Core(TM) i5-7200U CPU @ 2.50GHz 2.70 GHz, 8,00 GB RAM Memory. I have never ever had any issue with the performance of my PC.
Anyway, yesterday night i followed your guide, firstly i tried the "1) How to flash a stock rom using miflash", but when i refreshed in order to check if MIFlash detected my Phone, a strange little window error appeared ("Unhandled exception from the application. If you click Continue, the application will ignore this error and try to continue. If you click Quit, the application will close immediately"). So, when if i clicked "Continue" and i tried to refresh again, the error reapeared, and when i clicked "Quit" MiFlash closed. I recognize that i didn't do the "Disable driver signature enforcement in windows" step (is it mandatory?).
Due to this unexpected error, i tried the way "2) How to flash a stock rom using cmd",with not doing, again, i recognize, the "Disable driver signature enforcement in windows". So when i flashed from the cmd, unlike all the precedent tries doing with this way, the rom started flashing succesfully. All seems to going perfectly, but when the process arrived to the 7/10 poing, i had an "super flash error" (actually, the cmd screen specified me one concrect error, but i was a little bit nervous and didn't copy it; i think was (or it was something like) the "sparcecrclist error", but i'm not very sure). The rom, then stopped flashing, the phone was blocked (as the other precedent failed times) at fastboot mode, and i could only recuperate it by flashing the Xiaomi.eu room.
It was very sad, because i really thought that in this time i would succeed. I don't really know what to do. I got really scared, because that "super flash error" terrified me, but fortunately nothing bad happened thanks to the succesfull flash of the Xiaomi.EU rom. I could flash the rom stock again, in order to copy here the exact error i had on "7/10" step, but that "super flash error", which i have never had, really scares me. It seems like you are my only help here and, anyway, following your guide has been has been the nearest point of installing the stock rom succesfully.
I would love to hear from you again.
***EDIT: that MIFlash error never happened to me preciously. I used the last version which was on the link of your guide.
Click to expand...
Click to collapse
Ciao! no i am not spanish, but i love spain and i have been there for six months and i speak some spanish, however i am sardinian, italy.
So, disabling driver signing in Windows is essential to be able to correctly install unsigned drivers such as those present in the miflash program.
Sparse crclist It happened to me as an error, I solved it by downloading the rom again and unzipping it and renaming it with a small name and no spaces in the miflash folder and then it successfully flashed and special characters like $ # & etc.
I asked you which pc you use because some users with pc with amd processor the miflash program gave problems, even if you use the front usb ports or usb3.1, hence the advice to use rear doors and 2.0.So try to follow the guide to the letter by changing the usb port and downloading the fastboot rom again, I am sure that sooner or later you will be able to flash the rom, or at least I hope so. I too got scared when that error appeared to me.I hope it works, and what you tell me more and more makes me think that it is a conflict between miflash and the system. Happy flash bro!
Also try the February 2021 version of miflash, I used that. They have recently updated it and I haven't tried it, maybe the bag is his fault.

Ok, i will repeat the guide adding the step of driver disabling driver signing.
And i have checked the device administrator and, of my 3 usb ports, two of them are "3.0 - 1.0", but ¿how can i know which of the 3 are the 3.0? Sorry about my inexperience. And thank you a lot.
***EDIT: And when you mention "renaming it with a small name and no spaces in the miflash folder", you refer to the rom's folder or the rom (.bat) properly said?
***EDIT(again): And all the difficualties couldn't be related to the fact of the "Rollback" problems, because i'm trying to get back from Android 12 to Android 11? i don't know.

Tukan41 said:
Ok, i will repeat the guide adding the step of driver disabling driver signing.
And i have checked the device administrator and, of my 3 usb ports, two of them are "3.0 - 1.0", but ¿how can i know which of the 3 are the 3.0? Sorry about my inexperience. And thank you a lot.
***EDIT: And when you mention "renaming it with a small name and no spaces in the miflash folder", you refer to the rom's folder or the rom (.bat) properly said?
***EDIT(again): And all the difficualties couldn't be related to the fact of the "Rollback" problems, because i'm trying to get back from Android 12 to Android 11? i don't know.
Click to expand...
Click to collapse
Ok. follow the guide it should work with the February 2021 version of miflash.
Generally the USB 3 ports are of a different color, usually blue or light blue, the 2.0 are black.
Don't worry, no one is born with infused wisdom
When I say to rename the folder, I am referring to that of the rom, I generally use the version like 12.5.6 or in any case choose a name that has no spaces or special characters such as% $ # etc.
The anti rollback is only present on stock roms so you don't run the risk if you switch from custom like xiaomi.eu. i also checked the stock miui 13 china and it is not active on this phone.

What your bootloader status now..?, you can check it by typing fastboot command "fastboot oem device-info"
did you remember exactly of what the stock rom version (detail MIUI version including region code) that came from the phone before you flashing it..?

JJeamy said:
What your bootloader status now..?, you can check it by typing fastboot command "fastboot oem device-info"
did you remember exactly of what the stock rom version (detail MIUI version including region code) that came from the phone before you flashing it..?
Click to expand...
Click to collapse
Thx a lot for your interest in helping me. This is what i had with that command:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s
And the the exact rom version vas MIUI 12.5.7 (EEA).
I would thank you any help from you. Thx in advance.
***EDIT: MIUI 12.5.7 GLOBAL (EEA).

Tukan41 said:
Hello everyone:
Going back from Xiaomi.EU to STOCK EEA stable for a little f3, tried to flash by fastboot but it gives me the antirollback error. In fact, if I double-click or run the "flash_all_lock" file as administrator (because I would like to close the bootloader) it doesn't run, but instead makes a pretense of opening and closing. I can only run it by opening a command window (cmd) and running it from there, but it doesn't work.
Later, he tried to do it with the MI FLASH, which he did not know, and it gives me the same error. So, I followed the instructions in this video (
) ) ) (take a look at it, please, it lasts only 1:30 minutes), and after solving the two errors that it solves, it gives me a third one, something like "file It's too big" or something like that.
I would appreciate, please, if you help me.
A greeting and thanks in advance.
Click to expand...
Click to collapse
Well i hope you got the answer till now case u havent got the solution please refer for the firmware flash to global or the initial firmware .. yes it will make xiaomi.eu rom into a bootloop the go for the flash by the images folder but not the actual folder and do flash in fastboot mode & not in oem mode that will brick the device also just in case things turn back swith to aosp and then firm flash back again this is the nth solution for the error this has nothuing to do with NTF or FAT32 format
\
in case the solutions request for a thumbs up to the post
Regards
DroidEditor
[email protected]

Tukan41 said:
Thx a lot for your interest in helping me. This is what i had with that command:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s
And the the exact rom version vas MIUI 12.5.7 (EEA).
I would thank you any help from you. Thx in advance.
***EDIT: MIUI 12.5.7 GLOBAL (EEA).
Click to expand...
Click to collapse
No problem bro.. actually yesterday i'm doing back to stock rom again same as yours..but lucky in my case..doesn't find any trouble at all while flashing back stock fastboot rom
Firstly i need some more detail info from you so we can analyze what become wrong exactly that causing trouble
So the fastboot rom that you've download is POCO F3 EEA V12.5.7.0.RKHEUXM right..?
What windows version..?, windows 10 or 11..?
did you already tried to flashing the rom without re-locking option the bootloader..?, also what the result is..?
i will trying help if i can..but unfortunately right now in my country already middle of the night.. and i'm too sleepy, but it's ok we can continue discuss tomorrow then.

JJeamy said:
No problem bro.. actually yesterday i'm doing back to stock rom again same as yours..but lucky in my case..doesn't find any trouble at all while flashing back stock fastboot rom
Firstly i need some more detail info from you so we can analyze what become wrong exactly that causing trouble
So the fastboot rom that you've download is POCO F3 EEA V12.5.7.0.RKHEUXM right..?
What windows version..?, windows 10 or 11..?
did you already tried to flashing the rom without re-locking option the bootloader..?, also what the result is..?
i will trying help if i can..but unfortunately right now in my country already middle of the night.. and i'm too sleepy, but it's ok we can continue discuss tomorrow then.
Click to expand...
Click to collapse
Thx a lot for trying to help me!
-The rom i have download, yes, is POCO F3 EEA V12.5.7.0.RKHEUXM.
-My Windows version is Windows 10 Home.
-Yes, yesterday i tried to flashing with "clean all", i mean, without trying to close bootloader nor maintaining internal storage.
Mainly, i used the guide which Rolldload kindly provide me, except the "Disable driver signature enforcement in windows 10", and my flashin went gone until the flashing 7/10 phase, where the command window gave me a "super flash error", and all ended there.
I hope all these information serve you.
Regards.