Hello,
I have M7Tmob, it had installed cyanogenmod 10.2.1. I downloaded and tried to install custom ROM United_Advance_v6.2.2. I booted into my custom recovery clockworkmod 6.... and it failed to flash the rom. I so decided to flash a new custom recovery image from my Linux Mint 16 machine.
I typed the command:
fastboot flash recovery "recovery...." Whatever recovery I was trying to flash... And it would just stay on waiting for device. After a little research I found out that I had to be logged in as "root" in order for the commands to work. And so I did, and apparently the flash was successful. Unfortunately, it was not. Now the phone will not boot into any rom and all I can get to is the boot manager. When I choose to boot into recovery all I get is the splash screen of whatever recovery image I put there and after two seconds, the recovery crashes and the phone reboot itself into the "HTC quietly brilliant" splash screen. And there vicious circle begins again. I reboot the phone into fastboot, and tried flashing some other recovery, but in the end I always ended up there, with a bricked phone.
I would appreciate if any of you could provided me with the much needed assistance!
Regards,
GSALTAR
Related
Early today, I was working on a G2 trying to get it rooted with a custom ROM installed. I managed to root the phone and disable the bootloader security. From here, I attempted to install clockwork recovery via rom manager... here's where the disaster starts.
Everything seemed to be going well (no errors), so I tried to load a custom ROM. The Rom installation started but failed partway through. This is when I noticed that the clockwork recovery wasn't working properly. It was flickering and none of the options worked (screen just flashed or turned black if you selected anything). So at this point, the phone would not boot since the ROM installation didn't complete, and I had a buggy recovery image installed.
Unfortunately, the fun doesn't stop here. I figured that I should load the PC10IMG.zip and start from scratch... bad idea. This flashed the bootloader (relocking it) then failed-- leaving me with a bad ROM, bad recovery image, and a locked bootloader. Luckily for me, I was able to use adb via the buggy recovery to unlock the bootloader again.
At this point, I got a bit antsy and jumped the gun. I decided to use fastboot to erase and load a new recovery image. Unfortunately, I realized that I didn't have a recovery.img file to flash... just after I used the fastboot erase recovery command.
I'm hoping that someone here has a recovery.img file compatible with the T-Mobile G2 so I can flash the recovery partition with fastboot. If anyone has any better ideas I'm open to suggestions.
Thanks in advance for any help.
Install amon recovery. It's much better then clockword. Do it using adb
Sent from my HTC Hero using XDA App
Just an update. I couldn't get into adb but I was able to flash clockwork via fastboot. For whatever reason, the amon recovery would go through. Nevertheless, I installed cyanogen using clockwork and everything is gravy!
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Have you tried downloading the twrp pg86img.zip & make sure it's named PG86IMG.zip then put it on the root of you're sdcard, boot into bootloader and update that way?
CM powered EVO 3D, enough said.
luca73n said:
hi guys iive unlocked my evo with the htcdev mod and no problem has come out , bun i'm unable to run any recovery.
iìve tryed all cwm twrp and any i found on the site.
i try with fastboot method and abd, all say that the recovery vas written , no error but when i try to lunch recovery the phone show the htc logo stay 10/15 second then reboot the phone.
pls help me
Click to expand...
Click to collapse
when the device either hangs on the htc logo or reboots while on the htc logo, it means there is an issue with the actual kernel/ramdisk.
when dealing with a custom recovery, they should always boot without any issues. the best suggestion off the top of my head is to make sure if you're on the CDMA version, use the shooter recovery and if you're on the GSM version, use the shooteru version of the custom recovery.
otherwise, as suggested above, reflash the confirmed correct custom recovery for your device. there are a few ways to flash the custom recovery although, being you used the htc unlock method, regular custom recovery mode will not have write access to the boot/kernel partition.
if you're interested in loading any ROMs which come with kernels or separately flashing a custom kernel, there are essentially two complete methods:
1) use my Flash Image GUI app from normal android mode to flash the kernel. then flash the ROM from custom recovery.
2) use fastboot boot c:\android\cwm-recovery.img . this will temporarily boot the custom recovery and htc unlock will grant it write access to the kernel/boot partition. this command is different than fastboot flash recovery c:\android\cwm-recovery.img. the fastboot boot will temporarily boot into the custom recovery while fastboot flash will permanently write it into the recovery partition.
hope all the extra details make sense and helps!
Ummm.....Just my 2 cents, but it sounds as though the most basic possible problem has been overlooked here. You need to go into menu>settings>power and uncheck the "fast boot" box or do a battery pull, then try to boot into your bootloader to access recovery. With your phone completely powered down (fast boot unchecked or after battery pull), hold volume down and press power. That will put you in your bootloader with an option to boot recovery from there.
ok i'm a noob i've used thr shooter and not the shooteru cwm img, now all works
ty guys
Greetings, my lenovo a526 is stuck at lenovo logo.
I already tried wiping cache in stock recovery, but in wipe data/factory reset it says default data flag fail something like that.
Reboot, im still stuck
Then i tried flashing stock rom using spft it was successful yet still stuck at logo.
So I thought i should flash twrp or cwm recovery to install custom rom in sd card
I used adb fastboot. To flash those recovery because my stock recovery doesn't have "install zip in sdcard"
In fastboot,
My device is detected when i execute
Fastboot devices
"mt6582_phone --- device"
I cannot flash cwm or twrp directly because when i do it says remote partition does not support flash.
I believe i need to unlock bootloader first.
So i execute
Fastboot oem unlock
The result is 3 dots loading like forever
Now im in a dead end, i know i have to confirm it in my device but it has no display only logo.
Please, i need help. Is there any way to execute fastboot oem unlock without confirming in my device?
C'mon someone here had experience using fastboot. Any ideas guys?
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/