Hi guys,
after flashing original recovery from Rashr, I have a hard bricked Meizu M1 Note. I can only boot into fastboot or VCOM (for SP Tool), no recovery, not normal boot.
Hope you can help me,
Thank you
Same story, even worse! I wanted to downgrade from LP to KK. I followed step by step guide posted in other forum. Everything works, but after 2 or 3 days, phone started to act very strange. Volume keys did not react properly (cant switch in recovery and made an screen shot for example), phone started to loose network coverage . I tried to reset it, but unfortunately no fastboot and recovery modes were present. The only way to switch in recovery was rashr tool. I decided to reflash recovery again and everything went wrong! The result was permanent restart, no recovery and fastboot modes. Maybe this method should be avoided. I know that everything I made is at my own risk, dont blame me.
Need advice to unbrick it. I was thinking to disassemble it and disconnect battery and try to resurrect it with adb?! The bad thing is that it wont turn into fastboot...pfuu.
Have some progress - phone can go into fastboot mode, but when I try to flash stock recovery, it reports error:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)
OKAY [ 0.616s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017 because it is locked
)
finished. total time: 0.665s
Click to expand...
Click to collapse
Will appreciate any help. Thanks!
Any help?
Help
I have the same problem. Could anyone help us?
any help?
I have more or less the same problem but my cellular conects disconects preloader usb driver and don't see nothing in the screen, not logo, not recovery, not fastboot mode, any help?
Related
My almost two-year-old Hero froze this morning, so I had to take out the battery, but after this I've been unable to boot, it's stuck on the HeRO screen. I can't start recovery either, the only thing working is hboot / fastboot. Erasing user data using fastboot doesn't do anything.
Also, plugging the phone into charger doesn't signalize charging – the LED doesn't light up, and the PC doesn't recognize the phone either. Only fastboot does connect the phone to the PC, but adb doesn't work and all attempts to flash a new recovery or do anything else via fastboot end with "FAILED (remote: not allowed)":
Code:
c:\adb>fastboot devices
HT97JL903267 fastboot
c:\adb>fastboot boot recovery-RA-hero-v1.7.0.1.img
downloading 'boot.img'... FAILED (remote: not allow)
c:\adb>fastboot flash boot recovery-RA-hero-v1.7.0.1.img
sending 'boot' (3972 KB)... FAILED (remote: not allow)
I tried installing the official RUU updates (2.73.405.66, 2.73.405.5 and 1.76.405.1 too) but none of them could connect to the phone, Error [170]: USB Connection error.
I was using Elelinux-Hero-2.1-update1-Reloaded with radio 63.18.55.06SU_6.35.17.03 and recovery was Amon RA 1.6.2 I guess.
The phone did a similar thing 3 weeks ago but I was able to boot into recovery and erase data and cache and it worked fine afterwards. Now only fastboot is accessible.
Is there anything else I can do at this point or is the phone dead for good?
Disregard my previous post.
I left the phone booting for 30 minutes, the battery got uncomfortably hot, but the phone booted up eventually. Then I managed to install the official RUU from here.
It didn't solve anything though – it still takes around 20 minutes to boot, the touch screen doesn't work and I get an "android.process.acore" error all the time – but since the phone seems untouched (thanks to the RUU install) I can lodge a claim and get a replacement phone hopefully.
You could try putting HEROIMG.NBH on the sdcard and booting into hboot. If you go into fastboot and press vol-down it quickly scans for files on the SD, of which heroimg is one, and if it finds them, installs them.
Can't really help more than that. My phone did that last year, took it to the shop and ended up getting a new motherboard, cause the ROM chip was knackered.
One thing I would recommend though when you get it fixed is to flash an engineering bootloader, do if it breaks again you've got none of this "remote not allow" rubbish.
Of all the times to say disregard my last post.........
Sorry about that, thanks a lot though!
I suppose some hardware is broken in my Hero as well, I will take it back to the shop tomorrow.
Thanks again!
My device(HTC desire 526g+) is in soft brick state and i can only access fast boot but whenever i try to flash recovery or any other thing from fastboot it display :-
sending 'recovery' (5766 KB)...
OKAY [ 0.179s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.196s
Can you help me please.
Update:
now one more thing happens. I was searching a way to solve soft brick and my device was in fastboot mode while connected to pc but it get shutdown of no reason and when i open fastboot by volume up and power it show three options as usual Recovery, fastboot and normal and when i select fastboot it just restart to normal boot and normal boot is under loop.
what the **** happen to this device.
ME too facing same problem.
Sukhman Bajwa said:
My device(HTC desire 526g+) is in soft brick state and i can only access fast boot but whenever i try to flash recovery or any other thing from fastboot it display :-
sending 'recovery' (5766 KB)...
OKAY [ 0.179s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.196s
Can you help me please.
Update:
now one more thing happens. I was searching a way to solve soft brick and my device was in fastboot mode while connected to pc but it get shutdown of no reason and when i open fastboot by volume up and power it show three options as usual Recovery, fastboot and normal and when i select fastboot it just restart to normal boot and normal boot is under loop.
what the **** happen to this device.
Click to expand...
Click to collapse
Hellow me to facing the same problem. Did u found any solution for this error? If yes please tell me.
vechan said:
Hellow me to facing the same problem. Did u found any solution for this error? If yes please tell me.
Click to expand...
Click to collapse
it looks like we all are faceing the same error
truzz_patel said:
it looks like we all are faceing the same error
Click to expand...
Click to collapse
did you find a solution. even i am facing same issue. pls help
janajackie said:
did you find a solution. even i am facing same issue. pls help
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=xT017FtECZI = Here is the full process on how to unlock the bootloader from htc 526g+ made by Salman
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Johanna12221 said:
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Click to expand...
Click to collapse
Flash aboot it will ok..
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Johanna12221 said:
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Click to expand...
Click to collapse
By looks of it, you have a locked bootloader and hence, are unable to flash fastboot files. The only way for you to make your device usable again is to somehow boot into the 'edl' mode and use MiFlash to falsh the fastboot ROM from there.
Hi! Thanks for your reply.
I didn't do anything to the bootloader, so yeah it should be locked.
I will contact the store I bought it from and try to get it returned.
So sad to have made this purchase. I hope I can find another phone, perhaps one that is not as cheap as this.
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Johanna12221 said:
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Click to expand...
Click to collapse
I can help you. Talk me in PM.
Hi!
Thanks for offering your help, andersonaragao.
I finally got it to work by doing a "Flash all" of the MIUI 8 package.
So the steps so solve was just this easy:
Boot in fastboot (Volume down + power)
Make sure you have kenzo or kate (fastboot getvar product)
Get correct fastboot rom, depending on kenzo/kate: (http://en.miui.com/a-234.html)
Boot in edl (Fastboot_edl-v2: fastboot reboot-edl)
MiFlash 2016.04.01 (Flash all)
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Hi !
My friend yesterday gave me a phone, and asked that i could repair it.
Phone getting a bootloop everytime, have to use red bottom or power on + volume up.
1 st thing that i tryied to do, was install a new rom via flashtool.
Unfortunately i coudn't did it. Stuck on:
INFO - Reading device information
Second thing that i tryied to do was install recovery via fastboot using
Minimal ADB and Fastboot .
I can see device as a :
CB5A20DPRA fastboot
But when i try to install recovery or boot.img i getting a :
target didn't report max-download-size
sending 'recovery' (11570 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.378s
There is something more that i can do about it or phone is broken beyond repair ?
Futhermore device was unrooted, it have been installed cfw before it broken,
but i not sure, it have bootloader unlocked.
Hi
Your problem is version of flashtool, try to install older flashtool (that solved my problem).
If i helped you please press thanks button
Wish you all the best
TepaC said:
Hi
Your problem is version of flashtool, try to install older flashtool (that solved my problem).
If i helped you please press thanks button
Wish you all the best
Click to expand...
Click to collapse
Which exactly version of flashtool i need to download?
Downloaded 0.9.16.1, still same issue .
Stuck on : Reading device information
Try to force power off your device first
Then flash stock ftf
Use flashtool v0.9.18.6 and change Usb cable.
same problem same phone any help please
Hi, try to use Sony (Emma) Flashtool if it can detect the phone and flash the firmware available.