I unlocked my phone's bootloader .It has S-ON .
After that I flashed twrp recovery through fastboot.
Then when i reboot system , it restarts into recovery again. Not able to normally boot up.
Pls help !
jass619 said:
I unlocked my phone's bootloader .It has S-ON .
After that I flashed twrp recovery through fastboot.
Then when i reboot system , it restarts into recovery again. Not able to normally boot up.
Pls help !
Click to expand...
Click to collapse
fastboot erase cache
Make sure you don't deleted system anyhow
Hello guys
Need your help or ideas
So i Hard Bricked my P9 i can only enter fastboot.
Phone was on Android N first build,flashed it with TWRP,but i dint have stock app likes camera calculator e.t.c
Phone was working OK but i whanted to get original camera.
So there was made TWRP for android N, i flashed it TWRP worked system was booting, but TWRP not mounting /data, so there was tuto for fix that.
Need to flash zip -> repair /data -> resize ( thats was begining of problem )
zip was success, but format and repair was with error 4
system not booting anymore stuck on bootloop, with twrp.
Tried re-flash N with TWRP dint helped . Only lost TWRP
So i flashed L19C432B136 with dload. update was success, but I don't know why system wast booting, there was no orginal recovery i can't enter it or update with dload.
Stuck in screen "Phone is unlocked and can't be trusted"
Flashing TWRP for MM or N is success but phone don't enter IT
Flashing stock recovery from B136 dint helped ( i tried stock recovery from B322 ; no success)
Tried flashing SYSTEM.img BOOT.img RECOVERY.img from 322, all is sucess but phone not skipping screen ( Phone is unlocked and can't be trusted )
Any idea how to get phone back from dead?
I can only enter fastboot.
Is i possible to flash something true fastboot?
I have full updates of L19C432B182 and L19C432B161.
richish said:
Hello guys
Need your help or ideas
So i Hard Bricked my P9 i can only enter fastboot.
Phone was on Android N first build,flashed it with TWRP,but i dint have stock app likes camera calculator e.t.c
Phone was working OK but i whanted to get original camera.
So there was made TWRP for android N, i flashed it TWRP worked system was booting, but TWRP not mounting /data, so there was tuto for fix that.
Need to flash zip -> repair /data -> resize ( thats was begining of problem )
zip was success, but format and repair was with error 4
system not booting anymore stuck on bootloop, with twrp.
Tried re-flash N with TWRP dint helped . Only lost TWRP
So i flashed L19C432B136 with dload. update was success, but I don't know why system wast booting, there was no orginal recovery i can't enter it or update with dload.
Stuck in screen "Phone is unlocked and can't be trusted"
Flashing TWRP for MM or N is success but phone don't enter IT
Flashing stock recovery from B136 dint helped ( i tried stock recovery from B322 ; no success)
Tried flashing SYSTEM.img BOOT.img RECOVERY.img from 322, all is sucess but phone not skipping screen ( Phone is unlocked and can't be trusted )
Any idea how to get phone back from dead?
I can only enter fastboot.
Is i possible to flash something true fastboot?
I have full updates of L19C432B182 and L19C432B161.
Click to expand...
Click to collapse
You have 2 choices with this.
If you can still boot into TWRP,
1. Flash the Beta Update.zip
2. Power off phone.
3. Press up button whilst powering up phone.
4. You will now be in stock recovery and you can perform a factory reset.
5. the device will now boot in to N beta but will be missing the vendor apps.
There is another way to fix if this doesn't work. Tell me if this method works first.
Edit: I just read in the op that you flashed the update and had stock recovery.
The reason it won't boot is because you need to have b322 flashed and you have to factory reset to repair the corrupt file system. To do this follow these instructions.
1. You need to flash the Boot, Recovery and System images from b322 in fastboot.
2. Then enter stock recovery (Vol + and Power)
3. Then factory reset (this is essential as it repairs the file system and enables boot)
4. The device will then boot.
5. (Optional )If you want to go back from the beta you have to flash the rollback.app to b300 through th dload method first then you can flash a Android 6.0 through the dload method.
Regards
Lee
thel2dab said:
You have 2 choices with this.
If you can still boot into TWRP,
1. Flash the Beta Update.zip
2. Power off phone.
3. Press up button whilst powering up phone.
4. You will now be in stock recovery and you can perform a factory reset.
5. the device will now boot in to N beta but will be missing the vendor apps.
There is another way to fix if this doesn't work. Tell me if this method works first.
Regards
Lee
Click to expand...
Click to collapse
Cant Enter TWRP
noone of recoverys work
richish said:
Cant Enter TWRP
noone of recoverys work
Click to expand...
Click to collapse
Edited my previous post with another method.
thel2dab said:
Edited my previous post with another method.
Click to expand...
Click to collapse
fast qestion
there is 2 recoverys, does both need to be flashed?
@richish
If you get really stuck I can teamviewer your pc and help.
Or you can facebook message me direct.
I had exactly the same issue when I first tried to flash the properdatafix with TWRP for N
Regards
---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------
richish said:
fast qestion
there is 2 recoverys, does both need to be flashed?
Click to expand...
Click to collapse
You can flash both.
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
I don't think it is essential but it won't hurt to do it anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:26 PM ----------
[/COLOR @richish
I seen you PM. I am not sure it will wok by flashing B182. I think you have to flash B322 first.
Regards
fist you have to flash stock recovery from emui 5(android N) through fastboot.
second , download the rollback package,extract it and put it on dload folder of external storage.
third, turn off the phone , and press vol up + vol down + power button together to enter forced update mode.
if it is successful system will boot and you should flash android M firmware using dload method then u should unlock bootloader,install twrp,wipe /system /cache /data and then flash update.zip(android N) and hw_data of your firmware one after another.
i hope this help you.
still phone is not booting
I redownload b322, extracted Boot.img System.img Recovery.img Recovery2.img and Cust.img with
http://forum.xda-developers.com/showthread.php?t=2433454 Update Extractor
Flashed all .img true fastboot
But still nothing
Stuck on bootloader screen "Your device is unlocked, and can't be trusted"
Maybe i need flash some more images from b322.
Its look like phone cant pass bootloader.
Any sugestions?
P.S. Phone still have warranty, but booloader is unlocked
and fastboot oem relock ************** ends with failed.
"Failed - root cant trusted"
Sugestions how to lock it?
I had my phone bricked from testing cm, and going back to stock. My solution was to flash dload and recovery from the 182, followed by dload flash of 182.
@richish
caution : these commands will format the partition
can u use these command ?
"fastboot format /system"
"fastboot format /data"
or "fastboot erase /system"=> this will erase system partition
Phone is live now.
I downloaded DC-Phoenix and bought 15 credits
flashed stock B182 via DC-phoenix and phone booted.
I recomand this apllication for everybody who have similar problems.
THX for everybody who helpped.
richish said:
Phone is live now.
I downloaded DC-Phoenix and bought 15 credits
flashed stock B182 via DC-phoenix and phone booted.
I recomand this apllication for everybody who have similar problems.
THX for everybody who helpped.
Click to expand...
Click to collapse
How can i sign up for an account, it alway said wrong username or password !:crying:
DC-Phoenix is not cheap but it also cured my phone after bricking it with flashfire where all other methods did not work.
if you use it follow the instructions carefully and do the 2 step flashing although it will work after the first one. if you don`t do the second flash the partition sizes are wrong and a dload update will fail.
smartmobee said:
How can i sign up for an account, it alway said wrong username or password !:crying:
Click to expand...
Click to collapse
First u must buy credits, activate your account in email and then login in aplication.
Hi everyone
I would like to share the problem that i am having with my p9 , so maybe i can get your help.
Firstly i had L19C185 version and i changed Oeminfo in order to install c636 Beta 7.0 Nougat.
I installed the nougat but then realized that i dont have stock apps in my phone, so by mistakely tried to install TWRP for 6.0 Marshmallow and my problem started here.
Now my phone can not boot. its stuck in Phone is booting now ( the screen when you unlock bootloader after huawei logo) , and its never booting. it stays like that.
I tried to flash rboot.img , recovery.img and System.Img from fast boot. but whenever im trying to flash system.img after boot and recovery.img, a get an error and never succeeded to flash system.img. Im trying to flash these .img files from L19C636b180.
Can you please help me or give me some advice because none of mobile services couldnt fix and flash new software. maybe because they dont know exactly what should they do. and in my country i couldnt find anyofficial huawei service provider.
Please help me how to fix my phone.
I also had serious problems with flashing the thing back to stock.
TWRP was broken too for me.
I've done that to fix it all
The ONLY way that worked for me was
1. Download EVA-L19C636B168 from here http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
2. Download that SRK tool http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
3. Flash the recovery from the SRK tool, you can do that with the tool or directly via fastboot (i don't know other proper source for the correct recovery img)
4. Put the image EVA-L19C636B168 (UPDATE.app) in the "dload" folder of your sd card
5. Start phone in dload mode (Hold all 3 buttons at start) and let the update do it's job
What about recovery??? Does 3 button combination works? Whats heppens if u hold volup and power button when turning phone on!
Situation looks similar what i had.
Only solution for me was dc-phoenix.
U have tu buy 15 points to flash phone (15eur) But it works.
I'm 99% sure that there are bootloader comands what is same as for dc-phoenix,but i dont know them.
Sent from my EVA-L19 using XDA-Developers mobile app
please help
i had bricked my p9 L09 twrp not working noting working only fastboot mode is working plzzz help me in finding boot.img recovery.img system.img
Guyz..I have mistakenly flshed a custom rom while booting with a patched image for rooting..I rooted phone but couldn't install TWRD coz sideload driver didn't connected..
However after flashing the custom rom,now its keep restarting every time boot in to Android One logo..I have downloaded a fastboot rom but while flashing using Mi Tool I get an error called device and firmware version mismatch...last time I was in july security patch...what should I do..?
Plz help
try edl mode "fastboot oem edl"
Problem solved..
Just booted using twrp img and flashed CR again...on the reboot menu, changed the partition...booted successfully...
Thanks & credits goes to this thread :
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
leerh said:
is there any reason why flashing twrps via ADB would send z5 pro gt into boot loop into bootloader unable to access the custom recovry or phone needing to do emergency flashing via qfil to stock firmware i did previously use trwps on device to flash files and to sign boot to always boot twrps recovery when trying to access recovery mode . (before bootlooping)
affter bootlooping and fixing via qfil i have been unable to successful install trwps if i do it bootloop to bootloader.
whats the difference between "meta" / "flat" options in qfil
tried locked and unlocked bootloader on both 10.5.304 and 11.1.021 also tried to go straight to recovery mode affter twrps flashing on both firmware same thing lead me bootloop needing to qfill to 10.5.30
another question can i qfil flash to 11.1.021 straight away without having having to qfil 10.5.30 then ota updating to 11.1.021..
thanks in advance
Click to expand...
Click to collapse
Okay ?
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
IamRdw said:
Okay
The point is ? I must unlock , install twrp and flashing via ota ?
Flash via qfil done and isn't working
My touchscreen still have thats issue
Click to expand...
Click to collapse
if you want OTA(over the air) updates you need to lock bootloader. otherwise the updater will say something like phone has been rooted and they cant provide you an update
https://forum.xda-developers.com/z5-pro-gt/how-to/installing-ota-update-11-5-141-via-twrp-t4050027
http://anago.2ch.sc/test/read.cgi/sm...ne/1577014188/ theres a lot of information on this link here are some highlights for me
_____________________________________
>> Crash dump loop of 113 ROM burnt Z5PROGT can be restored by burning CNROM for the time being,
Even if I tried it again, it was useless, so if I look at the syntax at the time of batch execution, it seems that vbmeta.img is not burned.
It says unrecognised option `--disable-verification '.
This time, the boot loader loop only started, and TWRP couldn't start.
This time it may be packed
__________________________________________
>> 117
I'm sorry I want to confirm.
Where did you use the fastboot command?
①fastboot --disable-verification flash vbmeta vbmeta.img
②fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It is ① that I instructed, but it looks like there are two kinds when I check it on the net.
He seemed to have hit it without knowing it.
Excuse me, can you hit both again?
________________________________________
>> 150
>> I burned 113 ZUI11 version Gro ROM.
I re-added TWRP, but when I started it, it was usable normally, so I could add Magisk,
After that, it only seems to be unavoidable that it only starts up in normal recovery mode.
It is troublesome to do it every time you want to use TWRP, but it can't be helped.
__________________________________________________ _______
this helped Solved
hey guys! i recently unlocked the bootloader of my realme c11 to flash lineage os 17 . so to do so i installed twrp recovery and there i accidently wiped my system partition .from then on i cant mount my system and vendor partition in twrp and i'm stuck now cause nor i have any os installed , so after that there remained the option to flash oppo stock firmware image using fastboot , with fastboot i flashed boot.img successfully but when i tried to flash system.img using "fastboot flash system system.img" it said that there is no such partition as system. i mean why ......why does it happen why can't i flash system even with fastboot guys anyone who can help is gladly appreciated ,it'll be very nice of you . itll be great if anybody provide a straightforward answer to this......i'm counting on you guys........i'm on the verge of giving up//,/.;'.,//.;
You still need the fix?
najib6973 said:
You still need the fix?
Click to expand...
Click to collapse
yeah, i need the fix , i have no os installed, stuck in a recovery boot loop for i have corrupted boot.img i guess , and if anyone can provide system.img too of realme c11
HRZ110695 said:
yeah, i need the fix , i have no os installed, stuck in a recovery boot loop for i have corrupted boot.img i guess , and if anyone can provide system.img too of realme c11
Click to expand...
Click to collapse
try flashing this. wrong or outdated twrp can show the boot.img and system.img corrupted too. if the phone is in orange mode, you'll be able to fix it all with just twrp. but if red, it's gonna be a big process
this
SAME PROBLEM WHAT HAPPEN NOW?