Hi , please i need help with this huawei p6.:crying:
the device first was stuck in bootlogo , then i try flash a stock rom, (DLOAD) but the 3e recovery told me fail, later i unpack Update.app and try install system.img via fastboot but the ADB fail with ( FAIL Unknown status error and invalid Sparse file at header magi) i investigate a little then i install TWRP recovery 2.6.3.3 , and discover fail to mount System partition , i use the Terminal emulator of the TWRP and run this commands
mke2fs dev/block/mmcblk0pxx (XX number 13 to 21)
i dont know the number of each partition ( system, cache,internal storage, etc)
then i run the same command for format that partitions, after that i run this
mount -w -t dev/block/mmcblk0pxx (XX number 13 to 21)
the error was fixed in that moment i have success to mount the system partition, but i reboot the device for flash again 3e recovery for flash the ROM.
so in this moment i have a brick , my pc dont recognize the device , no fastboot, no run the last recovery (TWRP 2.6.3.3) dont do nothing. only vibrate , no led light when charging.
please someone can help me with this,how can i flash kernel now? or recover the fastboot?:angel:
excuse me for my bad english guys.
Related
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
sasawatd said:
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
Click to expand...
Click to collapse
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Lgrootnoob said:
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Click to expand...
Click to collapse
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
sasawatd said:
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
Click to expand...
Click to collapse
Driver issue?
Syntax for fastboot stuffz
try flashing:
Code:
fastboot flash recovery recovery.img
If flashing isn't working then try booting it directly
Code:
fastboot boot recovery.img
Hi, my brothers xt 1022 its bricked on initial looping.
The original bootloader works, i try hard reset, wipe data, but doesnt work.
I got unlock bootloader, because debug is disable, i dont be twrp or cwm or stock recovery works.
In the last time i try most tutorials for recovery with fasboot, .bat files, but doesnt worked.
i try send stock recovery in the update via sideload.
In this mode adb devices show the xt but returns error closed on adb usb.
I try kill-server but error closed persist
The sideload of zip rom goes to 100% but xt returns error to update.
Please help me
updating
in fastboot in try to twrp = incomplete boot image for booting.
how do i give the backup files via sideload, to try move the files and try recovery like a backup via side load, its possible?
update 2
I edit the adb_usb.ini and include id of device in recovery update adb and in fastboot. with the 2 adress include the name in managment device change to faastboot condor S. But still dont work the install twrp etc
Help
Hi, with fastboot these comands i have sucsses
fastboot flash partition gpt.bin
version downgraded for primary gpt
fastboot flash motoboot motoboot.img
downgraded for tz
fastboot flash boot boot.img
downgraded for boot
the outhers comand for flash doesnt work
Please help me with unbricked theses paper holder moto e
In android device info
show my device
condor_niibr_ds-user 4.4.4 KXC21.5-44 2 release-keys
kxc21.5-44
Anybody show me one rom .zip , to sideload from stock recovery. Or this rom to reinstal via sideload
Thanks
Hi I have installed miui 8 lollipop cn dev whith UB. When I install any recovery, first time there is a error shows that can not mount internal storage and second time when I reboot to recovery it shows it cant mount system. Plz note that I have wiped userdata after flashing twrp in fastboot and also have tried without data wiping. After second recovery reboot, system wont boot. I dont have hte same problem on mm firmware.
Errors:
Failed to mount /sdcard
Failed to mount system(invalid argument)
RE
SMYM said:
Hi I have installed miui 8 lollipop cn dev whith UB. When I install any recovery, first time there is a error shows that can not mount internal storage and second time when I reboot to recovery it shows it cant mount system. Plz note that I have wiped userdata after flashing twrp in fastboot and also have tried without data wiping. After second recovery reboot, system wont boot. I dont have hte same problem on mm firmware.
Errors:
Failed to mount /sdcard
Failed to mount system(invalid argument)
Click to expand...
Click to collapse
1) Try to flash ALKA Recovery OR
2) Dload ANDROID IMAGE KITCHEN extract boot.img from rom you want to flash put it in AIK Folder extract then open folder RAMDISK and edit file fstab.qcom where you will find ( ,verify ) delete this and then you will find (forceencrypt) change it to encryptable repack boot.img and flash it via fastboot this might solve your problem if anything goes wrong simply flash original boot.img
I wanted to get rid of the Chinese bloatware that came with the phone and decided to install the xiaomi.eu rom.
This is what I did;
unlock the bootloader
downloaded TWRP from official website (3.2.1-0)
installed TWRP with adb, reboot into TWRP with VolUp+Power buttons combination
factory reset and clean data partition
reboot
PROBLEM 1: stuck at MI logo... I said "whataver" and reboot into TWRP
plugged into PC, and transferred rom into internal memory manually
PROBLEM 2: I couldn't push with adb because the device is not recognised in fastboot
in TWRP press install, try to install rom zip
PROBLEM 3: get error 7 message "This package is for device gemini.."
I say "whatever" and download global stable rom from MIUI
did another system data cache clean, tried to install rom
PROBLEM 4: "unmount of /firmware failed: no such volume" "mount:failed to mount /dev/block/bootdevice/by-name/sec at /firmware: invalid argument"
It says "scripting succeeded: result was [1.000000] Updating partition details...done", but when I reboot I'm stuck at the MI logo again!
Any help is very appreciated!
tryhardernow said:
I wanted to get rid of the Chinese bloatware that came with the phone and decided to install the xiaomi.eu rom.
This is what I did;
unlock the bootloader
downloaded TWRP from official website (3.2.1-0)
installed TWRP with adb, reboot into TWRP with VolUp+Power buttons combination
factory reset and clean data partition
reboot
PROBLEM 1: stuck at MI logo... I said "whataver" and reboot into TWRP
plugged into PC, and transferred rom into internal memory manually
PROBLEM 2: I couldn't push with adb because the device is not recognised in fastboot
in TWRP press install, try to install rom zip
PROBLEM 3: get error 7 message "This package is for device gemini.."
I say "whatever" and download global stable rom from MIUI
did another system data cache clean, tried to install rom
PROBLEM 4: "unmount of /firmware failed: no such volume" "mount:failed to mount /dev/block/bootdevice/by-name/sec at /firmware: invalid argument"
It says "scripting succeeded: result was [1.000000] Updating partition details...done", but when I reboot I'm stuck at the MI logo again!
Any help is very appreciated!
Click to expand...
Click to collapse
Well, you need here some corrections to do things in the right way.
In the 3rd step you say that installed twrp through adb but twrp can´t be installed through adb; maybe you wanted to mean fastboot that is other thing.
In the 4th step most important is at first reboot to twrp swipe to allow modifications and then you have to perform "format data" to can reboot normally to system although some times is required no-verity zip for R5P vince (just Google) some users refer that is needed despite I never did.
In the 8th step; fastboot mode can´t work simultaneously meanwhile are you using adb so you don´t need it when you are using adb although this you can´t transfer a file from pc to your device using simply adb; you need to enable first in advanced options from twrp the feature adb sideload then placing the file that you want to transfer from pc to device in the same adb folder you have to type in a terminal with admin rights adb sideload nameoffile.zip but this is not to transfer a file only but to transfer it and flash it onto device.
In the 10th step first open the zip file of the rom with notepad++, go to META-INF/com/google/android/updater-script and check what device is it made for and additional you can browse to system/build.prop and similarly open it and check ro.product/model cause gemini is other variant.
So I think that you flashed firstly a rom for other device and maybe you need to restore some partitions to correct this using MiFlash tool.
But first to this if most of all partitions are working and not damaged you can flash almost any partition through fastboot mode, unzip the rom in the same adb folder and type every file for every partition one by one but maybe you need only system, boot and userdata partitions so try first these three, I hope that you know syntax of fastboot commands.
Hello everyone, a year ago a I had installed a custom recovery on my Lenovo S5000-F and it caused a bootloop and I lost the recovery, fastboot is working fine but it only allow me flash boot, system, userdata and cache partitions. I already tried do:
1-Unpack boot.img
2-Edit default.prop to allow adb debugging and then create a custom OTA update to install by adb sideload.
But when I boot the system I get device offline. So looking through system.img I found an interesting thing, a flash recovery script: install-recovery.sh
Bash:
#!/system/bin/sh
echo 1 > /sys/module/sec/parameters/recovery_done #tony
if ! applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:boot:5781504:94079a17dc0e061e417363e4d44d7d8d0e609f16 EMMC:recovery b1d3582729e0f954b16931a7a87d4c09b6854396 6156288 94079a17dc0e061e417363e4d44d7d8d0e609f16:/system/recovery-from-boot.p
if applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then #tony
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image completed"
else
echo 2 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image not completed"
fi
else
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Recovery image already installed"
fi
This script means to replace any recovery installed by the user to the original one, but for some reason its not working.
So I would like to know if there is any way to flash a recovery partition through a script, so I can write this script to init.rc to install the stock recovery and fix bootloop.
EDIT: The install-recovery.sh had installed the stock recovery but I didn't noticed lol, the cause of bootloop is because the recovery and logo partitions its in the same file so when I flashed TWRP with a size bigger than my recovery partition it wrote to logo partition too.
Solved by creating a custom script using the same "applypatch" binary to flash the logo partition and worked fine
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Pachacouti said:
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Click to expand...
Click to collapse
But I can't flash stock booloader, fastboot only flash boot, system, userdata and cache partitions, since I can flash boot I can make a modified init.rc script to flash the stock recovery during boot time, but I don't know how to do this :/
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Pachacouti said:
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Click to expand...
Click to collapse
Oh I got it now, you mean flashing stock bootloader into boot partition so when I turn on the device it will be on bootloader, I can try it but there's another problem, I don't have the stock bootloader lol
GO get it then lol...
Pachacouti said:
GO get it then lol...
Click to expand...
Click to collapse
Unfortunately I didn't found the bootloader, but I tried flash the stock recovery into boot partition, but when I reboot the device boots into grey screen and then shutdown. I have no idea why this not worked :/ I already tried boot the recovery through fastboot but its just transfer the recovery.img and not boot.