Develop Bugs

Fastboot failed. 'remote: not allow'

Hi, i'm following a guide to root my Hero http://myandroidblog.wordpress.com/2009/08/03/htc-hero-root-access/
But when ever I run the first CMD command (fastboot.exe boot.img.insecure) i get this error:
'downloading 'boot.img'... FAILED (remote: not allow)'
Any ideas what that means or what I can do to fix it.
Thanks
ps I tried searching but couldn't find any similar topics so hope I haven't repeated someone else

You have to use flashrec to flash recovery image
http://forum.xda-developers.com/showthread.php?t=559613

Yup, got the exact same error when I tried to root my Hero, doing the backup flash that Exit93 links to, did the trick for me too
I did a backup of my recovery flash prior to installing the "modded recovery" as well, so should be reversable if needed as well.
Make sure you shut down as many apps as possible before attempting the flash. At least I had to shut down pretty much everything in order to do both backup and flashing.

Thanks for the help guys, i'll they that tomorrow (getting pretty late now).
This is a big change from the WM devices i'm used to, taking some getting used to

you did the official update of HTC, the Boot is replaced..
fastboot will not work then

Well, after doing the Flashrec thing and then going onto the Rooting process (I used a different method from http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38 and although I got through the process (there seemed to be a few errors when mounting) after rebooting I don't have root access, tried it x2 now and nothing changed. Any other ideas?
Thanks, Wez

[Q] Huawei Ascend Y300: Back to Stock ROM Problems.

Hello,
I need some help, because I can't find any solution on my own.
Short story: I need to go back to stock rom and it doesn't work. I can't flash it via fastboot, and recovery mode doesn't work, because I can't use touch and CWM doesn't work either.
Long story:
This morning I wanted to install a Custom ROM, because I've got problems with RAM and touch lately. I heard that touch might be a software problem, so I thought this could solve it.
After several problems with installing Cyanogenmod, I finally made it, just to find out it doesn't find my sd card, which meant I couldn't load my backuped files onto my phone, which meant it was useless.
When I finally gave up on the sd card problem, I just wanted to go back to stock ROM. I also found out that touch doesn't seem to be a problem caused by software, because it doesn't even work in recovery mode.
So now I can't go back to stock ROM. I downloaded the original version from the Huawei Website.
FIRST WAY: Recovery mode.
I can't make a factory reset, because my touchscreen doesn't allow me to swipe, which is needed in TWRP. CWM doesn't work for me, I've tried it several times, but when I go to recovery mode, I only stay at the "huawei ascend" logo. So TWRP; but this doesn't work because of touch problems.
SECOND WAY: Fastboot.
This should work better. BUT:
for fastboot -w I get this error:
Code:
erasing 'cache'...
FAILED (remote: Command not allowed)
for fastboot erasing cache it's the same.
When I just ignore that and go by fastboot update [file], I get the following:
Code:
sudo fastboot update '/home/laura/Schreibtisch/root/HUAWEI_Y300_firmware%28Y300-0100%2CAndroid%204.1%2CEmotion_UI%2CV100R001C00B189%2CGeneral%20version%29.zip'
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
At the moment I have TWRP installed and no OS, because I can't flash any.
Please help me out! I'm sitting here for eight hours, it's in the evening in Germany and I need my phone.
Thanks!!!
Laura

Help - Pixel 3 stuck after failed flash-all...

Hi, I'm new here... After browsing all over Internet and trying for many hours, hope I can get some help here.
So I was brave yesterday and wanted to root my pixel 3 to install some new themes. Unlocked bootloader, but I screwed up with Magisk / TWRP and the phone could not boot any more. At that point, I was still able to see the phone in adb. Then I tried to flash the stock rom using flash-all, but the process failed at one file (vendor_a?).
Unfortunately, I decided to reboot the phone - and now I'm stuck because the phone will be deadlocked showing the Google screen, and my PC cannot recognize the phone any more. adb shows no device, and device manager doesn't see any Android device. I have the latest developer tools and also installed the latest Google USB driver (at least I think), but now when I plug the phone in, I do hear the new device sound, but it is only recognized as a general USB device.
I can't even turn off the phone. Long pressing power will only go back to restart the phone and the first screen shows "this device is corrupted". Go on to the second screen will only give me an option to pause, with nothing else to choose from. I can't reboot into TWRP or recovery.
Any thoughts? Thanks a lot...

edx2000 said:
Hi, I'm new here... After browsing all over Internet and trying for many hours, hope I can get some help here.
So I was brave yesterday and wanted to root my pixel 3 to install some new themes. Unlocked bootloader, but I screwed up with Magisk / TWRP and the phone could not boot any more. At that point, I was still able to see the phone in adb. Then I tried to flash the stock rom using flash-all, but the process failed at one file (vendor_a?).
Unfortunately, I decided to reboot the phone - and now I'm stuck because the phone will be deadlocked showing the Google screen, and my PC cannot recognize the phone any more. adb shows no device, and device manager doesn't see any Android device. I have the latest developer tools and also installed the latest Google USB driver (at least I think), but now when I plug the phone in, I do hear the new device sound, but it is only recognized as a general USB device.
I can't even turn off the phone. Long pressing power will only go back to restart the phone and the first screen shows "this device is corrupted". Go on to the second screen will only give me an option to pause, with nothing else to choose from. I can't reboot into TWRP or recovery.
Any thoughts? Thanks a lot...
Click to expand...
Click to collapse
First off, if you did successfully unlock your bootloader there is a 99% chance you will be able to recover from this. In fastboot mode is the phone state shown as "unlocked" ? Do you have a second PC or laptop to install the standalone adb/fastboot binaries on? adb does not work in fastboot mode, only in stock recovery mode. First re-try fastboot flashing the full image while in fastboot mode without modifying the flash-all.bat (allow it to wipe). You may also want to check the CRC (checksum) on the image you downloaded to verify it is not corrupt. If unlocked and that install fails capture the error and report back. Then try using adb from the stock recovery. You Tube how to get into recovery and use update via adb with a (different) full OTA image. The full OTA images are also available on the same Google dev site as the factory image, and is sometimes called a rescue OTA. You're in the right place to get help, but you need to provide all relevant information (such as previously installing a custom rom).

try holding power and vol down until the phone reboots and comes back to the menu where you should hopefully get back to Android Recovery mode where you should be able to use adb and the OTA via a sideload......for some strange reason I always get screwed on the vendor partition when using the flash-all script....never have figured it out
GL!!

v12xke said:
First off, if you did successfully unlock your bootloader there is a 99% chance you will be able to recover from this. In fastboot mode is the phone state shown as "unlocked" ? Do you have a second PC or laptop to install the standalone adb/fastboot binaries on? adb does not work in fastboot mode, only in stock recovery mode. First re-try fastboot flashing the full image while in fastboot mode without modifying the flash-all.bat (allow it to wipe). You may also want to check the CRC (checksum) on the image you downloaded to verify it is not corrupt. If unlocked and that install fails capture the error and report back. Then try using adb from the stock recovery. You Tube how to get into recovery and use update via adb with a (different) full OTA image. The full OTA images are also available on the same Google dev site as the factory image, and is sometimes called a rescue OTA. You're in the right place to get help, but you need to provide all relevant information (such as previously installing a custom rom).
Click to expand...
Click to collapse
cmh714 said:
try holding power and vol down until the phone reboots and comes back to the menu where you should hopefully get back to Android Recovery mode where you should be able to use adb and the OTA via a sideload......for some strange reason I always get screwed on the vendor partition when using the flash-all script....never have figured it out
GL!!
Click to expand...
Click to collapse
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.

edx2000 said:
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
Click to expand...
Click to collapse
Have you also tried a 2.0 USB A to USB C cable, or a different set of cables period?

do what I told you....I always fail at the vendor junk but can easily get the ota sideloaded....give it a try, forget flash-all
EDIT: just read the rest of your post...hmm....
well assuming you get the correct hash after downloading, it should work. after that its computer, port, drivers, sdk, and cable thats a potential issue.
again for me, I always fail on vendor. it happened on my pixel 2xl and still on the 3xl. I have tried multiple pc's, cables, etc and always fail at the vendor partition, but the ota sideload through android recovery always worked. YMMV

cmh714 said:
do what I told you....I always fail at the vendor junk but can easily get the ota sideloaded....give it a try, forget flash-all
EDIT: just read the rest of your post...hmm....
well assuming you get the correct hash after downloading, it should work. after that its computer, port, drivers, sdk, and cable thats a potential issue.
again for me, I always fail on vendor. it happened on my pixel 2xl and still on the 3xl. I have tried multiple pc's, cables, etc and always fail at the vendor partition, but the ota sideload through android recovery always worked. YMMV
Click to expand...
Click to collapse
If vendor "always" fails on your PXL3 you may want to find out why. Could be a symptom of some problem with your phone.

Homeboy76 said:
If vendor "always" fails on your PXL3 you may want to find out why. Could be a symptom of some problem with your phone.
Click to expand...
Click to collapse
I doubt that....happened with my xl2 as well....tried multiple PC's, ports, cables, etc. nothing seems to work so I have been using the OTA as that has been bulletproof thus far

Make your you have latest fastboot and adb, a good non usbc to usb c cable, boot into fastboot, flash all, profit. If your bootloader is unlock your good.

edx2000 said:
Thank you guys. I was able to make some progress but now I'm stuck somewhere else.
If I run flash-all, the error message I get is:
"Sending sparse 'vendor_a' 1/2 (262140 KB) FAILED (Error reading sparse file)
Finished. Total time: 108.152s
Press any key to exit..."
Alternatively, I tried sideload in recovery mode, and I get:
"E:footer is wrong
Update package verification took 0.2s
E:Signature verification failed
E:error:21
So it seems the zip I downloaded is corrupted? But I downloaded two different versions from Google Developers and both failed.
Any suggestions? I'm going to try it one more time with another computer.
Click to expand...
Click to collapse
You should verify the crc checksums of the files you are using. There are many tools to do this and the signature is posted with each image. That, and like Badger says.. try a different cable (A to C). and try another PC. Google provides these image files to enable users who have unlocked their bootloader to completely restore the phone to it's factory state. I'm thinking the problem is with a corrupt image, a marginal cable, or the adb/fastboot setup on your PC/laptop. You don't need the complete Android SDK, only the standalone platform tools. The fact you have a working stock recovery and are bootloader unlocked means your likelihood of success is very high.

Badger50 said:
Have you also tried a 2.0 USB A to USB C cable, or a different set of cables period?
Click to expand...
Click to collapse
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!!

edx2000 said:
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!![/QUOTGlad you got it working :good:!! Pixel 2 & 3 XL's definitely have something in common. They're both picky sons of guns when it comes to cables! :good:
Click to expand...
Click to collapse

edx2000 said:
Wow, using a USB A to C worked!!
Changing to another computer did nothing.
Thanks everybody!!
Click to expand...
Click to collapse
Pixel 3a here. Found this through a bit of intense google-fu. This did the trick. Hilarious that this was the source of it. Previously was using usbc to usbc on a win10 laptop and it failed at the same part mentioned here.
Sorry for the necro bump but I think it deserves a mention. Thanks everyone here

Flashing Issues (Fastboot, TWRP and MAGISK)

Hey. So I've unlocked the device and had Lineageos running on the device but decided I wanted to access google pay functionality and read up on installing magisk and TWRP to circumvent the safetynet issue. I managed to flash TWRP through fastboot perfectly fine, but then when I tried to push + install magisk is when the problems started. I received the error "Failed to mount system_root (device or resource busy)" on attempting to install, which I could not resolve. I decided to use TWRP to format data and factory reset and try again, which is when I ran into "failed to mount /data" when trying that.
At this point I tried flashing an older TWRP, thinking maybe the old guide doesn't work for the newer TWRP I was using. Following the same steps of fastboot flash recovery ..." which I used previously, I now have this problem
"Writing 'recover' FAILED (remote: '(recover) No such partition')"
and the device no longer boots back into lineageos, although I am able to run the fastboot boot filename command, and using that I was able to reinstall a working lineagos so the phone isn't entirely useless. A whole sleuth of fastboot commands I've seen suggested as solutions to some of these issues now no longer work however, such as 'fastboot format userdata'.
The mounting of the data folder is resolved... or at least I haven't seen it crop up again, however I still can't install magisk due to the system_root mount problem. Another weird thing is that I can install lineageos from TWRP recovery without running into the system_root problem, but using the same process for magisk results in system_root mount failure. Also, when I installed lineageos through it's own recovery image it referenced magisk (i believe it said it failed to install but I didn't copy the log).
I briefly tried the mi flash tool but ran into a Not catch checkpoint (\$fastboot -s .* lock),flash is not done problem which I haven't really delved too deeply into yet but might tomorrow after work.
Is my phone screwed?

Question HELP, device stuck in bootloop, tried every method.

Hi everyone,
maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.
And oh boy did that started a very long day of messing with miflash tool and twrp.
The situation right now is like this,
I have full access to TWRP, and fastboot and mi flash tool.
I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.
Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.
Tried sideloading with adb some ROMs and same results, stuck on POCO logo.
Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...
I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...
Is there anything I'm missing?
Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?

kmo1997 said:
Hi everyone,
maybe someone here might help me. I was on bliss rom and my phone suddenly froze yesterday.
And oh boy did that started a very long day of messing with miflash tool and twrp.
The situation right now is like this,
I have full access to TWRP, and fastboot and mi flash tool.
I tried flashing stock rom with mi flash, got success with no error and yet still stuck in frozen POCO logo.
Tried flashing with TWRP couple of ROMs with correct fw and still got POCO logo stuck.
Tried sideloading with adb some ROMs and same results, stuck on POCO logo.
Also tried to use flash_all bat without mi flash tool, and it boots me to MIUI recovery...
I can always come back to fastboot and boot to TWRP and tried miflashtool many time , I always result in success (0) but nothing works...
Is there anything I'm missing?
Of course I waited at least half an hour every time on POCO logo beacuse I know It can take some time for first boot but nothing happens, If I had to guess is there a possibility that the Storage it self in the phone is broken?
Click to expand...
Click to collapse
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.

DarthJabba9 said:
Did you format the data partition at all while doing this? If not, then try running "fastboot -w" while in bootloader mode.
Click to expand...
Click to collapse
yes i tried. it gives me an error :
Erasing 'userdata' OKAY [ 0.032s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata

kmo1997 said:
yes i tried. it gives me an error :
Erasing 'userdata' OKAY [ 0.032s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\Users\Moti\Desktop\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Click to expand...
Click to collapse
Hmmm ... that shouldn't happen. You may have a hardware problem.
Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.

DarthJabba9 said:
Hmmm ... that shouldn't happen. You may have a hardware problem.
Try booting to recovery and formatting data from there. If that doesn't work either, then I have no other suggestions.
Click to expand...
Click to collapse
i tried , no luck.
is there any way to fing out if it is truely hardware problem?

Hi,
just a thought,
I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.
After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms,
its worth a try

i do the same

johnr64 said:
Hi,
just a thought,
I have been in a situation were Miui stock would not complete it`s installation, I don`t use MIflash tool, i found a tip that involved moving the ADB flies from Miflash and put them into the Miui fastboot stock rom folder and move the re-named folder to my C: Drive.
After some panicking i tried my old faithful a "Xiaomi.eu Fastboot rom", i installed it from fastboot, it completed as it should and i carried on where i left off, flashing custom roms,
its worth a try
Click to expand...
Click to collapse
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.
regardless I tried your advice and no luck

I have tried a couple more things, I flashed with locking the bootloader the oldest MIUI ROM I found on the archive, of course no luck, still stuck on POCO logo and as always somehow, I'm able to boot into fastboot so unlocked the bootloader again and tried a xieomi.eu rom without mi flash tool with the .bat file and flash_all.
same result, no luck
I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.

kmo1997 said:
.... I'm starting to think it might really be a hardware issue, yet I'm baffled at how the phone was working perfectly fine and suddenly froze while i was using it and started bootlooping which started this whole mess.
Click to expand...
Click to collapse
That is often how hardware problems manifest themselves.

kmo1997 said:
thanks for the answer, in my situation miui stock completes the installation successfully with a beautiful green success in miflashtool and yet I'm still stuck at the POCO logo till botting itself to MIUI recovery.
regardless I tried your advice and no luck
Click to expand...
Click to collapse
If possible try gsi builds to boot bro it may boot directly to system

Try flashing different Fastboot stock Roms using miflash, don't use just one version, try only without locking the bootloader, probably it is a boot partition error, you just need to find the right one, also use a different miflash version (older ones seem to be more stable)

I have just read one of your recent comments, it seems like e miflash problem, flashing with lock must lock the bootloader, try using known versions especially older ones

Have you tried turning it off and on again?

Jk.
First of, which twrp Version are you using? You should try the latest skkk versions. https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/alioth/
Are you sure that you have full twrp storage access? If you boot into twrp, how big is your internal storage, as seen from twrp? Does it show 0?
I had this error once, couldnt flash anything anymore because twrp couldnt handle some encryption and needed to reformat the internal storage to ext2, then back to ext4 again. Then the storage was readable and writable again.
Encryption can be a weird, just like A/B partitioning.

Make sure to use the latest version of MIUI for your specific region.
A.k.a. the exact version of MIUI that your phone shipped with, but use the latest version of it.
And don't download from a weird third party website.
I think the official site is mi.com (but you'll have to google the exact link).
Otherwise, my go-to for MIUI ROMs is xiaomifirmwareupdater.com