Solved unknown brick! - P8lite Q&A, Help & Troubleshooting

I installed KangVip Rom backup and got unexpected bootloop!
1. It powers on starts boot after bootanimation aperance it dies (reboots) and loops again!
Here is what i did to unbrick it.
1. Flashed Stock Rom (no success)
2. Flashed Boot Cust System in Fastboot mode (no success)
3. Restored My Backups (no success)
I gone try Downgrading it! Recovery is available and Fastboot too!
There was Virus on software! I removed it!

RootingPro-18 said:
I installed KangVip Rom backup and got unexpected bootloop!
1. It powers on starts boot after bootanimation aperance it dies (reboots) and loops again!
Here is what i did to unbrick it.
1. Flashed Stock Rom (no success)
2. Flashed Boot Cust System in Fastboot mode (no success)
3. Restored My Backups (no success)
I gone try Downgrading it! Recovery is available and Fastboot too!
Click to expand...
Click to collapse
Did you try format all partitions in twrp and flash b632 ZIP rom?

Adi5 said:
Did you try format all partitions in twrp and flash b632 ZIP rom?
Click to expand...
Click to collapse
Yes! Still same

Comeon! Help!

Related

fastboot boot on 4.4.4 WORKED!

So here's my story.
My device is :
S-ON, 4.4.4 Droid stock, 3.29.161.9.
Yesterday i tried to get root while keeping stock rom for no tampered msg at bootloader.
I was following guide from http://forum.xda-developers.com/showthread.php?p=51383278&highlight=ota#post51383278
so with unlocked bootloader i tried to fastboot boot CWM recovery image.
and it hanged my phone as everyone reported for > 4.4.3 ..... so i gave up for this time.
Today i was in mood for flashing some custom rom and then rooting, but with TWRP(newest 2.8.3.0).
just for gigles i tried to fastboot boot newest twrp. only thing i did was renaming .img file to recovery.img.
guess what? it worked! so i got root, reboot and started enjoying not tampered stock
So now im sharing this lil'christmas story with you.
Of course if it's irrevelant or already found please delete this topic.
happy christmas nevertheless.!
i'm on 4.1.1 and can't install room with 4.4.4 cus it's request 3.28.401.6 firmware or above and when i do it and trying
fastboot boot recovery.img
Click to expand...
Click to collapse
i can touch the recovery screen but cant see what i'm doing.
now using TWRP 2.8.3.0 the phone just doing reset and not going to recovery
any advice?
Plomiwn said:
...
just for gigles i tried to fastboot boot newest twrp. only thing i did was renaming .img file to recovery.img.
guess what? it worked! ...
Click to expand...
Click to collapse
Oh, really...?
Merry Christmas to you.
mb0 said:
i'm on 4.1.1 and can't install room with 4.4.4 cus it's request 3.28.401.6 firmware or above and when i do it and trying i can touch the recovery screen but cant see what i'm doing.
now using TWRP 2.8.3.0 the phone just doing reset and not going to recovery
any advice?
Click to expand...
Click to collapse
Use older recovery. That one has new display drivers.
Merry Christmas to you too.
Sent from my HTC One_M8 using Tapatalk
this is what i get when upgrading the firmware http://oi58.tinypic.com/e0jxqq.jpg
was using Stock Firmware + NoRedText Hboot from here: http://forum.xda-developers.com/htc-one-m8/development/ota-3-28-401-6-t2899900
been trying the following recovery files:
openrecovery-twrp-2.7.0.1-m8 - not working, screen stuck in fastboot
openrecovery-twrp-2.8.0.0-m8 - going reset
* to be clear: this "no display" in the recovery thing happening only after i flash InsertCoin 5.0.6 http://insertcoin-roms.org/2014/12/...rol-market-ota-icon-packs-stable-performance/
(haven't flashed another room yet)
now i need do what i always do when this happen:
- fastboot oem rebootRUU
- fastboot flash zip 2.22.401.4-Firmware-noredtext
after that go back to recovery and restore the backup i made before.
mb0 said:
this is what i get when upgrading the firmware http://oi58.tinypic.com/e0jxqq.jpg
was using Stock Firmware + NoRedText Hboot from here: http://forum.xda-developers.com/htc-one-m8/development/ota-3-28-401-6-t2899900
been trying the following recovery files:
openrecovery-twrp-2.7.0.1-m8 - not working, screen stuck in fastboot
openrecovery-twrp-2.8.0.0-m8 - going reset
* to be clear: this "no display" in the recovery thing happening only after i flash InsertCoin 5.0.6 http://insertcoin-roms.org/2014/12/...rol-market-ota-icon-packs-stable-performance/
(haven't flashed another room yet)
now i need do what i always do when this happen:
- fastboot oem rebootRUU
- fastboot flash zip 2.22.401.4-Firmware-noredtext
after that go back to recovery and restore the backup i made before.
Click to expand...
Click to collapse
not sure what your point is ? this thread is about booting the LATEST twrp on the LATEST firmware because older ones couldn't boot but could only be flashed.

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

Error loading zip and img on twrp

Hi guys. I have a problem with my ze500KL. I can install only the twrp 2.8.7.7 version. But when i try to install img or zip of roms /original firmware, the twrp fails the operation , saying " error data", "unable to mount"... i have problems with wipe too. any solution?
nik91thebest said:
Hi guys. I have a problem with my ze500KL. I can install only the twrp 2.8.7.7 version. But when i try to install img or zip of roms /original firmware, the twrp fails the operation , saying " error data", "unable to mount"... i have problems with wipe too. any solution?
Click to expand...
Click to collapse
I can't understand what you mean. If you want to install stock rom from TWRP recovery, you have to modify updater-skript.
Why do you can install only the twrp recovery 2.8.7.7, when we have the twrp recovery 3.0.0.2
File img you can flash from fastboot mode. Commands:
fastboot flash system file.img
fastboot flash recovery file.img
fastboot flash boot file.img
or
fastboot boot file.img for example twrp recovery img or stock recovery img. This is command for once booting.
I want to return to original firmware , i download it from the site of asus. So, i booted twrp in fastboot mode (i tried different version of twrp, but the only that starts is the 2.8.7.7 version) using adb.
Now i am in recovery with twrp 2.8.7.7. I can push using .zip files or img files on internal storage.
But i have different problems with this recovery:
IF i use wipe function: error opening sys, could not mount, enabe to mount, ... (failed)
If i install rom or firmware with zip files: error unable to mount, unable to find partition for path.... (failed)
Adb sideload goes failed too.
What should i do???
I think that the problem is in the internal partition... I have to install using a min usb ext storage? or what????? thanks :fingers-crossed:
nik91thebest said:
I want to return to original firmware , i download it from the site of asus. So, i booted twrp in fastboot mode (i tried different version of twrp, but the only that starts is the 2.8.7.7 version) using adb.
Now i am in recovery with twrp 2.8.7.7. I can push using .zip files or img files on internal storage.
But i have different problems with this recovery:
IF i use wipe function: error opening sys, could not mount, enabe to mount, ... (failed)
If i install rom or firmware with zip files: error unable to mount, unable to find partition for path.... (failed)
Adb sideload goes failed too.
What should i do???
I think that the problem is in the internal partition... I have to install using a min usb ext storage? or what????? thanks :fingers-crossed:
Click to expand...
Click to collapse
Easiest way to fix your phone is flash stock rom from stock recovery. Stock rom put to sd card. Reboot to stock recovery and choose flash rom from sd card. New version number system must be the same or higher than installed in the phone.
Do you want to return to the lower version of Android.
http://forum.xda-developers.com/zenfone-2-laser/general/guide-downgrade-zenfone-2-laser-to-t3382172
Do you want to flash stock rom from twrp recovery.
http://forum.xda-developers.com/zen...uide-how-to-flash-stock-rom-via-twrp-t3409768
Muminek111 said:
Easiest way to fix your phone is flash stock rom from stock recovery. Stock rom put to sd card. Reboot to stock recovery and choose flash rom from sd card. New version number system must be the same or higher than installed in the phone.
Do you want to return to the lower version of Android.
http://forum.xda-developers.com/zenfone-2-laser/general/guide-downgrade-zenfone-2-laser-to-t3382172
Do you want to flash stock rom from twrp recovery.
http://forum.xda-developers.com/zen...uide-how-to-flash-stock-rom-via-twrp-t3409768
Click to expand...
Click to collapse
Stock recovery doesn't work man. The only recovery that works is the twrp 2.8.7.7. But it has problems.
nik91thebest said:
Stock recovery doesn't work man. The only recovery that works is the twrp 2.8.7.7. But it has problems.
Click to expand...
Click to collapse
Do you have Lollipop or Marshmallow and what is your version number.
For Marshmallow you need to this working twrp recovery.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
For Lollipop you need to this working twrp recovery.
https://drive.google.com/file/d/0B7F3ZXr565GkY1NQbUtoVzdwWEU/view?usp=drivesdk
If you haven't installed stock recovery, it's not no problem. You can it flash from fastboot mode.
i had mawshmallow. i tried but failed...
nik91thebest said:
i had mawshmallow. i tried but failed...
Click to expand...
Click to collapse
How did you flash the file twrp.img.
OK guys I've solved the problem. I moved in this way:
1) Volume up + power to go in fastboot mode
2) after installing adb and the other drivers, i've insered these commands:
fastboot erase cache
fastboot erase userdata
fastboot erase system
3) after downloading twrp version 3.0.0 (for the zenfone 2 laser), I load it using the command "fastboot boot (name file twrp).zip"
4) the recovery starts automatically. Now i downloaded the file "back2stock.zip" and the original firmware (WW, worldwide) form the official site of the Asus
5) this passage is the most important:using 7zip I've extracted the file zip of the firmware and the backtostock, then i created a new file using 7zip : in this new zip i've loaded the files inside back2stock and the files file_contentexts, system.new.dat, system.patch.dat, boot.img e system.trasfer.list inside the zip of the official firmware
6) I've loaded this new file on the phone using the command "adb push (new file name).zip /"
7) at last i have installed this file on the phone ENJOY it

boot loop / stuck after installing TWRP

hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
shikaji said:
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
Click to expand...
Click to collapse
I had a very difficult time rooting my Xperia X Compact (F5321) using the method you describe above. I had exactly the same problem with bootloop and sticking on the Sony screen. My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
So I opened up ADB and flashed the renamed boot.img file, followed by Twrp. Then I booted into TWRP recovery (power button + volume down) and installed the supersu (or magisk if you prefer) and drmfix.
Then I rebooted to system and after a few minutes it booted normally into the Xperia homescreen.
Regards,
Dave
funkoot said:
My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
Click to expand...
Click to collapse
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
shikaji said:
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
Click to expand...
Click to collapse
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
shikaji said:
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
Click to expand...
Click to collapse
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Bluestar01 said:
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Click to expand...
Click to collapse
unfortunately i've tried that as well already. same thing - stuck at sony screen or bootloop.
Hello, any updates ? I have the same problem, after flashing my F5321 with Flashtool to update from android 6 to 8...

Fastboot Failed (data transfer failure(unknown error)

Hello and thanks for inteterest to help. (My phone Redmi 2 Prime)
So to the point, i have my phone installed custom ROM. And today when i try to reset factory, it stuck in the MI Logo (Show and then turned off). So i forgot to flashing the twrp again last time, so i left it without any recovery. The only way is repairing it with Fastboot and installing TWRP. So i start installing all driver and flashing. But, when i want to flash twrp to my phone, it keep showing me this
fastboot flash recovery recovery.img
flashing 'recovery.img'
FAILED (Data Transfer Failure(unknown error)
DONE! 5.8 sec
But it doesnt installing any recovery. I have installing MiFlash driver. Is there any driver that i should install again? Or anything that i can do? Also my PC doesnt read my phone storage at all, it doesnt show in the explorer, but can read "my phone" and my phone model. And I'm using USB 2.0. I also have try USB 3.0 but it doesnt work too.
Any help would be appreciated. Sorry for the long post, eh?
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
dabakale said:
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
Click to expand...
Click to collapse
Thank you for replying
So i've try it, but why its stuck at 'downloading boot.img' for 2 hours?
Can i download the boot.img manually? If yes, what should i download?
Can you share a photo of error.
Or you can try miflash to flash stock rom. Then you try to flash twrp. I suspect there would be something wrong with your recovery partition.(i also had similar problem while flashing different roms.)
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Egalito Rieans said:
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Click to expand...
Click to collapse
Try this method
[No More Errors] [Fastboot Rom Flashing] [Direct Method]
Hi all, Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error ;). I tried many things but no luck. Then i followed direct method and that worked...
forum.xda-developers.com

Categories

Resources