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.
Related
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?
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
Hello,
Two days ago when I woke up my P6 suddenly didn't boot up anymore.
It's getting stuck on the fist boot screen where it says: Huawei Ascend.
I searched for a solution and tried the following things:
-Tried to get into recovery mode by pressing on/off+vol up, on/off+vol down, on/off+vol up+vol down.. Nothing helps, it turns on and off and shows the same screen again.
-Connected it to the PC, and the p6 is recognized as: Android sooner single ADB interface.
-Downloaded and installed this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
-Tried this: http://forum.xda-developers.com/showpost.php?p=45106541&postcount=11
-I also put Update.app in the dload folder of my SD card. (I downloaded the file from the Huawei website and used a cardreader to get it on the SD card)
Nothing helps
Can somebody please help me ?
Thanks!
Flash your device with stock Rom.
Salman Al-Badgail said:
Flash your device with stock Rom.
Click to expand...
Click to collapse
How do I do that when I can't access my phone?
It doesn't go past the first bootscreen at all.
I tried this:
C:\adb>fastboot flash recovery recovery_original_flashable.img
target reported max download size of 838860800 bytes
sending 'recovery' (7804 KB)...
OKAY [ 0.334s]
writing 'recovery'...
(bootloader) OKAY
FAILED (remote: verify failure, ErrNo:8)
finished. total time: 1.519s
It failed, I don't know what error 8 means..
You are having just a bootloop,
Salman Al-Badgail said:
You are having just a bootloop,
Click to expand...
Click to collapse
Yes, can you help me fix it?
I'm a noob at this, so I can use a little more help than saying what it is.
Thanks
Can somebody help?
Allow me some time to find USB drivers, Stock ROM and Flashing Tool for you.
Please Check your Device
Huawei Ascend P6
Please let me know your Previous Android Version.
Be specific with your answer so that I could help you.
Please Check Here
H-A-6
XDA HA6
Check HERE TOO
Still having problem please post it here
NOTE I am not responsible if you made it Hard Brick. Try it on your own
Salman Al-Badgail said:
Allow me some time to find USB drivers, Stock ROM and Flashing Tool for you.
Please Check your Device
Huawei Ascend P6
Please let me know your Previous Android Version.
Be specific with your answer so that I could help you.
Please Check Here
H-A-6
XDA HA6
Check HERE TOO
Still having problem please post it here
NOTE I am not responsible if you made it Hard Brick. Try it on your own
Click to expand...
Click to collapse
Hi
I can't get into recovery, I get errors using fastboot.
dload folder with the firmware in it doesn't do much either.
The other link you sent there is a program; Spreadtrum Upgrade Tool that needs .pac files, I don't know what that is.
Fastboot can see the device, but it cant flash the recovery?
C:\adb>fastboot devices
????????b?b?Û?§?b???????b?b?§?Ý???b?b?????b???b?b fastboot
C:\adb>fastboot flash recovery recovery_original_flashable.img
target reported max download size of 838860800 bytes
sending 'recovery' (7804 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) OKAY
FAILED (remote: verify failure, ErrNo:8)
finished. total time: 1.536s
C:\adb>
Try posting your problem here.
http://forum.xda-developers.com/showthread.php?t=2259645
Salman Al-Badgail said:
Try posting your problem here.
http://forum.xda-developers.com/showthread.php?t=2259645
Click to expand...
Click to collapse
OK, I did, thanks
Never mind, I bought a new phone..
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks
Hi there! My old Sony Xperia Tablet Z is running Resurrection ROM (Android 8), I use the tablet as a travelling companion. I also have TWRP as recovery.
Today I flashed the latest version of TWRP via the TWRP app, tried rebooting into it using a "quickboot" app (the tablet is rooted) but I ended up on a black screen. I can reset and Android runs no problem.
I then tried flashing TWRP via USB. I type
Code:
adb reboot bootloader
- it goes on a black screen and the status light is solid blue. I then run
Code:
fastboot flash recovery twrp.img
- the outcome is
Code:
sending 'recovery' (11796 KB)...
OKAY [ 0.379s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
Then I tried
Code:
fastboot boot twrp.img
- and I get
Code:
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.032s]
finished. total time: 0.411s
but nothing happens.
Someone suggested to use
Code:
fastboot flash recovery_ramdisk twrp.img
instead (as I am on Oreo) but same error
I am stuck. Any help please? Thank you!
If bootloader is not working Use QPST Flash Tool to reflash everything back to stock.
Thanks. Too bad I don't have the original ROM backup anymore. I will try to download one, I hope all works well.
Can you just refresh me: when into "bootloader" I am supposed to see the bootloader menu on screen?
Edit: it seems that I am unable to install the Qualcomm drivers - Windows 10 reverts to generic drivers or ADB drivers. The drivers I downloaded don't seem to work with Windows 10?
any help on this please? Thank you!
Sorry for insisting - any help please? Can you point me to the right direction?
edit: I've done some homework and here is where I am.
Following some threads I tried flashing the stock ROM using flashtool. I used both the latest version and the "Emma" version from Sony.
I can connect to the tablet but I receive a the bundle does not match the connected device as - I reckon - the device is seen as an unknown device. The same with the Emma version, unknown device and as such, a No matching services as a reply.
Edit2: I found the solution for the above, I had to use the previous version of Flashtool. I flashed a stock ROM. Now it does not boot anymore. I have the SONY static logo and then a black screen. I tried again and also another version for my device but no luck.
Please help!
I am a bit lost here. Any help is appreciated. BTW, I can boot up the tablet perfectly fine and it works ok.
I'll just complete my very lonely thread for future references.
The issue was that I needed an older stock ROM as I was coming from Android 8 - a known issue apparently. I found a very old ROM (10.1 "store front"), that worked ok. From that one, I can do whatever I want. I ended up installing LineageOS which I find much faster than Resurrection.