Strange, bricked-ish? - Huawei P9 Lite Questions & Answers

So... I f**** up. Won't bore you with the details, but the situation is this:
- /system is wiped, as is /data. There is no OS on the phone. Previously installed was B336. It's an L21.
- Can get into Fastboot
- Can also get into TWRP and/or the stock recovery, whatever is installed
- Can't get into Meticulus Recovery if I install it - just sits at the untrusted screen
- DLoad will not work at all. It's either stuck at 5 percent or quits with an 'incompatible' error immediately.
- When flashing a file, TWRP gives me a cryptic error message as to a missing META-INF thingy in the update.zip. This is new today because yesterday it just didn't work without multiple lines of red text. I have tried multiple update.zip from the original source, it's the same with all of them.
What I have tried:
- DLoading pretty much every firmware under the sun.
- Flashing Paranoid Android (which seemed to work but it won't boot beyond the untrusted screen)
- I tried CM too but it requires Meticulus' Recovery. Which won't work.
- Manually fastboot flashing recovery, boot, system, cust. This has worked on occasion but the install was stuck at booting up (at the Android logo). Now it doesn't work any more - FAILED. I can flash boot though.
- Hisuite... desperation. Nope, says it can't be used with the P9?!
- ... and of course eRecovery won't download and recover anything.
Kinda out of ideas here. Help?

You must first downgrade to stock MM.
You have to flash Revolution recovery, then the correct oeminfo (c432), after that you should be able to flags stock mm with the dload method.

Damn dirty oeminfo
Thanks buddy, that did it. MM did install via DLoad. On to new adventures!

Related

Update failed n stuck at google logo

was on 4.3 JWR66Y with stock kernel, unlocked bootloader, rooted - super su, busybox & a Custom recovery i.e. TWRP.
with Few Mods i.e. 4 way reboot, battery circle & Custom softkeys.
my nexus 4 showed OTA 4.4 update notification, i followed process - it downloaded OTA & accepted "reboot to install", automatically restarted to twrp nothing happened further. so i did factory reset to try again but found out that the downloaded OTA file was gone! & it shown "no latest update" later i manually downloaded "KRT16S frm JWR66Y" zip (238.9 mb) frm google/android server & tried to flash using TWRP, well it aborted saying some error in the middle of flashing (flashing didnt complete). So i wiped cache, dalvik etc (excluding partition & internal storage) to try flashing the file again. Worst thing is the "reboot to system" says "there is no OS you still want to continue?" stuck at google logo. (did read somewhere to rename zip file to update.zip unfortunately it didnt work)
good thing is i still have access to fastboot/bootloader and of course TWRP
what are my options ? use NRT to go back to 4.3 stock everything & then try to update again?
Please help, thank you XDA..
(could not find any other similar thread i.e. rooted, twrp, unlocked bootloader, with few mods etc.)
rajeshkoshti said:
was on 4.3 JWR66Y with stock kernel, unlocked bootloader, rooted - super su, busybox & a Custom recovery i.e. TWRP.
with Few Mods i.e. 4 way reboot, battery circle & Custom softkeys.
my nexus 4 showed OTA 4.4 update notification, i followed process - it downloaded OTA & accepted "reboot to install", automatically restarted to twrp nothing happened further. so i did factory reset to try again but found out that the downloaded OTA file was gone! & it shown "no latest update" later i manually downloaded "KRT16S frm JWR66Y" zip (238.9 mb) frm google/android server & tried to flash using TWRP, well it aborted saying some error in the middle of flashing (flashing didnt complete). So i wiped cache, dalvik etc (excluding partition & internal storage) to try flashing the file again. Worst thing is the "reboot to system" says "there is no OS you still want to continue?" stuck at google logo. (did read somewhere to rename zip file to update.zip unfortunately it didnt work)
good thing is i still have access to fastboot/bootloader and of course TWRP
what are my options ? use NRT to go back to 4.3 stock everything & then try to update again?
Please help, thank you XDA..
(could not find any other similar thread i.e. rooted, twrp, unlocked bootloader, with few mods etc.)
Click to expand...
Click to collapse
If you have the zip you can sideload it. Or you can flash the factory images in fastboot mode. This is post here for the guides. http://forum.xda-developers.com/showpost.php?p=47762352&postcount=2

CM 13 - Stuck in Recovery Mode after update

Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?
Do u have a back up to your stock Rom or any other Rom aside from CM?
Flash back to stock and start over with twrp, cm, and gapps.
I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.
My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.
So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?

no bootloader(/fastboot) menu, rooted stock rom lolipop. cannot install custom rom

Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.

Stuck in bootloop in all LOS and OOS based roms

Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state

[Q] Failed flash, stuck...

I was running xXx 4.5, and decided to "upgrade" to 5.0.
I did the usual, wiped data/system, then flashed.
I got stuck in a bootloop, and found I had to double back and wipe /data.
I did that, got stuck at the boot animation.
If I go back to recovery, all the data is jumbled, I assume encrypted? I flashed a different twrp for 8.0 compatibility, no change.
I can't push/sideload anything (roms, recovery zips sideload fine), it fails.
So I flashed the stock recovery in fastboot, rebooted there, and tried to sideload via adb the stock 8.0 flash files.
Now it works at it for a few minutes and just comes back as "Installation Failed".
Where do I go next? All i can get to is recovery, fastboot, bootloader.
I've already factory reset/wiped everything, so don't care if I lose anything anymore.
Help?
Thanks.
It appears I found a solution, just a few posts below my own! I hate it when that happens.
Anyways ,
https://forum.xda-developers.com/showpost.php?p=75364805&postcount=7
seems to have got the ball rolling, I was able to copy files to my phone while in twrp, which I couldn't do before, and currently have xXx installing. The first time it installed it didn't ask about encrypted/decrypted and didn't give me any warnings, this time it did.
xXx still won't boot after flashing, trying stock full flash file..
edit 2: Was able to flash full oneplus update file and boot. had to do a factory reset after rebooting as it was crashing a ton and wouldn't get through setup. It's been running fine since though. Now I'm a little skittish to try again, there are some root features I'd really like to still have.
I have a OnePlus 5 phone stuck in the Fastboot mode, been contacting them for days now but I still keep hearing the same excuses that the matter has been escalated to their tier 2 tech support team Nd would be contacted. Please is there a way to copy files off the phone in this state before it's flashed?

Categories

Resources