Related
Hi all,
I've generated root-ing boot.img for Pixel C, based on my root ( http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ):
Based on latest factory image (MXB48K)
The boot.img is available at http://superuser.phh.me/nexus/ryu/MXB48K/
There are three interesting variants: eng, noverity, nocrypt.
- eng is "standard" version with crypted /data, and dm-verity enabled for /vendor and /system
- noverity only has dm-verity on /vendor and /system disabled
- nocrypt has both dm-verity and crypted /data disabled.
The process to flash it is:
- Go in Settings, Developer settings, tick "Allow OEM Unlock"
- Reboot to fastboot mode
- fastboot oem unlock
- fastboot boot boot-su-eng.img
- install phh's Superuser from Play Store ( https://play.google.com/store/apps/details?id=me.phh.superuser ) (or FDroid)
- And if it works, to really install it, do fastboot flash boot boot-su-eng.img
This is working, thanks to everyone here, especially @cheep5k8
I might be getting my usb type c cable today! If I do I'll definitely test this out!
Potential tester
phhusson said:
Hi all,
I've generated root-ing boot.img for Pixel C, based on my root ( http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ):
Based on latest factory image (MXB48K)
The boot.img is available at http://superuser.phh.me/nexus/ryu/MXB48K/boot-su-eng.img
The process to test it is fastboot oem unlock, fastboot boot boot-su-eng.img and then install phh's Superuser from Play Store ( https://play.google.com/store/apps/details?id=me.phh.superuser )
And if it works, to install it, do fastboot flash boot boot-su-eng.img
Can someone test it for me on a Pixel C?
Thanks
Click to expand...
Click to collapse
I take it you don;t have a Pixel C to test yourself? Just got one yesterday and a type c cable today, adb working fine. Not sure I want to be guinea pig though :-\
the unlock command on the pixel c is the same as the 6p
CharlesW123 said:
I take it you don;t have a Pixel C to test yourself? Just got one yesterday and a type c cable today, adb working fine. Not sure I want to be guinea pig though :-\
Click to expand...
Click to collapse
You can do fastboot boot nameoffile.img
It won't change anything .. Fastboot flash flashes to memory
Sent from my Nexus 6P using Tapatalk
I wish this device came with a data cable. I would've already tested this if it wasn't for that.
Sent from my Pixel C using Tapatalk
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
ericvh said:
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
Click to expand...
Click to collapse
Tried flashing to recovery image and booting from that, but also didn't seem to work - I think ultimately it just dumped me into normal boot.
Maybe part of the problem is the double-clutch bootloader, what loads first isn't fastboot -- its something else. Looking at headers in the recovery image, seems like maybe a chromeos loader?
Also tried to just go ahead and flashboot flash boot boot-su-eng.img, but its complaining about multiple of block size:
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.047s]
sending 'boot' (9413 KB)...
OKAY [ 0.257s]
writing 'boot'...
(bootloader) writing flash
FAILED (remote: image not multiple of block size)
finished. total time: 0.342s
I got around this with some rounding, but maybe that's what is screwing up for me.
Well you weren't supposed to flash it until you booted it first to make sure it worked.
The obvious fix would be to flash the stock boot and recovery then factory reset in recovery. Then try again from a clean slate with encryption turned off.
Sent from my iPhone using Tapatalk
ericvh said:
This may be because of my fault -- but on boot its always asking me for my password (encyrpted device I suppose because I enabled device protection when I first got it). Even though I put in the right password, I guess the different boot has a different salt because it says it can't decrypt and then it asks me to factory reset the tablet. Even going through that I end up back at the same spot. Not sure how to remove decryption from the beast.
Click to expand...
Click to collapse
Interesting.
Have you done the fastboot flashing unlock? (some devices might allow fastboot boot without fastboot flashing unlock)
(Or oem unlock?)
Did the unlock forced factory reset?
I guess flashing back stock boot.img made everything back working?
What have you done to go past the rounding error?
Please note that this boot.img is signed, so rounding it shouldn't be just appending zeros to the end (though it might be interesting to test withotu signing)
This bootloader is really interesting.
It shows the bootloader has been done by Chrome team, which is amazing news compared to N9's HTC crappy bootloader.
This means that actually most (all?) of the source of the bootloader is available in chromium os tree, to better understand what happens.
Thanks for your tests
Edit 1: Ok, the bootloader is:
git clone https://chromium.googlesource.com/chromiumos/third_party/coreboot -b firmware-smaug-7132.B
Edit 2: I'm not seeing anywhere where fastboot could be handled...
If this isnt tested and what not when I get mine I'm sure I could try it
But...google screwed me and sent it overnight tonight but fedex is saying its not coming until tuesday...
superchilpil said:
Well you weren't supposed to flash it until you booted it first to make sure it worked.
The obvious fix would be to flash the stock boot and recovery then factory reset in recovery. Then try again from a clean slate with encryption turned off.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Indeed, I tried the vanilla boot first following the instructions exactly, I just did the flash to see if that made a difference after the 'test' boot failed. It was easy enough to reflash with a recovery image. It does seem to be the case that booting with fastboot somehow messes with whatever encyrption is being used on the user data. Although perhaps the 'flashed' boot just didn't get far enough to trip over it.
---------- Post added at 06:13 AM ---------- Previous post was at 06:09 AM ----------
I have not tried fastboot flashing unlock yet, oem unlock is done however - that did force a factory reset, but from what I can tell Marshmellow always enforces an encrypted image. I got past the rounding error by appending zeros as you suggest. flashing back stock boot.img restored the device to normal use.
There appears to be a two stage boot, when I boot into the bootloader it has an option to enter fastboot, enter android recovery (which doesn't work), enter usb recovery (which doesn't work) and continue with the boot process. Neither fastboot nor ADB interact with the system when its in this state. Once I'm in fastboot mode on the tablet, I can see interact with fastboot. Its also worth noting that despite enabling developer mode, I can't see the tablet with adb when running.
phhusson said:
Interesting.
Have you done the fastboot flashing unlock? (some devices might allow fastboot boot without fastboot flashing unlock)
(Or oem unlock?)
Did the unlock forced factory reset?
I guess flashing back stock boot.img made everything back working?
What have you done to go past the rounding error?
Please note that this boot.img is signed, so rounding it shouldn't be just appending zeros to the end (though it might be interesting to test withotu signing)
This bootloader is really interesting.
It shows the bootloader has been done by Chrome team, which is amazing news compared to N9's HTC crappy bootloader.
This means that actually most (all?) of the source of the bootloader is available in chromium os tree, to better understand what happens.
Thanks for your tests
Edit 1: Ok, the bootloader is:
git clone https://chromium.googlesource.com/chromiumos/third_party/coreboot -b firmware-smaug-7132.B
Edit 2: I'm not seeing anywhere where fastboot could be handled...
Click to expand...
Click to collapse
ericvh said:
[/COLOR]I have not tried fastboot flashing unlock yet, oem unlock is done however - that did force a factory reset, but from what I can tell Marshmellow always enforces an encrypted image. I got past the rounding error by appending zeros as you suggest. flashing back stock boot.img restored the device to normal use.
There appears to be a two stage boot, when I boot into the bootloader it has an option to enter fastboot, enter android recovery (which doesn't work), enter usb recovery (which doesn't work) and continue with the boot process. Neither fastboot nor ADB interact with the system when its in this state. Once I'm in fastboot mode on the tablet, I can see interact with fastboot. Its also worth noting that despite enabling developer mode, I can't see the tablet with adb when running.
Click to expand...
Click to collapse
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
I am welcome to testing. Just got my Pixel C and would love to help achieve root thank you for your work thus far and if needed let me know what I can do!
Okay, will give unsigned a shot. About to jump on a plane to Europe so I may not be as responsive (and less likely to want to factory reset) for about a week.
I was speaking of android developer mode, not aware of any chromeos development mode. Depending on level of "commitment" I may consider just going for coreboot to Linux and ditching android all together. I'm assuming I can probably prototype that on my JTX1 which has a serial port and then prep images for the Chromebook -- but that would mean ditching android altogether which in some ways would be a shame. Dual boot is definitely the preference for me at the moment.
phhusson said:
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
Click to expand...
Click to collapse
ericvh said:
Okay, will give unsigned a shot. About to jump on a plane to Europe so I may not be as responsive (and less likely to want to factory reset) for about a week.
Click to expand...
Click to collapse
Ok no problem.
I was speaking of android developer mode, not aware of any chromeos development mode. Depending on level of "commitment" I may consider just going for coreboot to Linux and ditching android all together. I'm assuming I can probably prototype that on my JTX1 which has a serial port and then prep images for the Chromebook -- but that would mean ditching android altogether which in some ways would be a shame. Dual boot is definitely the preference for me at the moment.
Click to expand...
Click to collapse
That's unrelated, but I think I'll probably buy a Pixel C when we'll see first non-Android development (Or I might jump straight to it, I already did it for good old Toshiba AC100)
I almost expect Google to publish a ChromeOS image for Pixel C, or at least see an official Chromium OS....
Considering you definitely sound like the hacker-type. How does the keyboard feel? Do you feel you could code hours-long on it?
Also, since there is "usb recovery" mode, I think you could always dual-boot back to Android with a usb stick (ok, there is no usb type c usb stick yet, that means ugly cable ATM)
Linux4Tegra should make porting full-blown Linux very easy, including OpenGL/GLX
phhusson said:
Ok, thanks. There will be many things to try :/
First, I generated an unsigned boot.img:
http://superuser.phh.me/nexus/ryu/MXB48K/boot-tmp.img
Can you test it?
Next step will be to factory reset with an unsigned recovery.img as well, then totally disable encryption in the fstab (I really hope it won't come to this...)
Further step would be to try to pack with ChromeOS tools ( https://android.googlesource.com/platform/external/vboot_reference/ )
In my understanding, "usb recovery" simply refers to the possibility to boot system from USB rather than internal storage.
When you speak of developer mode, are you speaking of standard Android developer mode? (I'm expecting to see a ChromeOS-like developer mode somewhere...)
Click to expand...
Click to collapse
boot-tmp.img has the same behavior.
My theory is fastboot is just there for reflashing via otg, not for actual booting and we'll need a chromeos wrapper + the payload burned to flash in order to get anywhere. I need to do some reading up on chromeos and coreboot and probably go thorugh and setup a chromeos enviornment.
ericvh said:
boot-tmp.img has the same behavior.
My theory is fastboot is just there for reflashing via otg, not for actual booting and we'll need a chromeos wrapper + the payload burned to flash in order to get anywhere. I need to do some reading up on chromeos and coreboot and probably go thorugh and setup a chromeos enviornment.
Click to expand...
Click to collapse
What has to be tested first is building from AOSP (i assume aosp tree is available for ryu?)
Not sure. I briefly looked for the kernel source, but wasn't sure I found the right one. There's some stuff in there for Smaug, but I assume the android kernel is probably bit different (although it doesn't seem to be the same as the one on the JTX1 or the Nvidia Shield TV -- so google must be doing something a bit more aggressive than Nvidia is in their products).
phhusson said:
What has to be tested first is building from AOSP (i assume aosp tree is available for ryu?)
Click to expand...
Click to collapse
I'm still in hope to find who implements fastboot...
Can someone give me the result of:
fastboot getvar product
fastboot getvar kernel
This doesn't require oem unlock, and doesn't have any risk, so anyone with working fastboot can do that
Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
joedajoester said:
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Click to expand...
Click to collapse
Try a different USB port.
Ensure you have USB drivers installed first.
TonikJDK said:
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
Click to expand...
Click to collapse
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
michaelbsheldon said:
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
Click to expand...
Click to collapse
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
joedajoester said:
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
Click to expand...
Click to collapse
Just curious, but when your in the OS, and open a command prompt on the platform-tools folder and type...adb devices...do you see your device ID?? Same thing for when your in bootloader mode and type...fastboot devices...??? ?
did you fix this? im in the same boat, on p beta tried to flash factory image back to 8.1 and getting "target didn't report max download size".
Im using platform tools
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
This is likely not your issue, but if your computer has less than 4 gigs of RAM, or you are trying to flash a file larger than your available RAM you will get this message.
This (i.e. rebooting PC) worked
DanteXXL said:
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
Click to expand...
Click to collapse
This indeed worked when I rebooted my pc.
Hello I have an urgent request. My phone isn't working currently because I tried to switch kernels but ended up flashing the wrong boot.img and was stuck on boot. With g logo.
Now whenever I try to boot system it goes to TWRP. due to bank of America app not allowing developer options, I had it turned off but I know USB debugging was on. When I used Tool All in one, it did recognize my phone but typing adb devices on command prompt doesn't show anything. Please help!!!
Flash magisk
@trizzv: There should be two ways for you to resolve your issue. The first and arguably the least painful is to change your slot and reboot, which you can do in the reboot menu of TWRP. The second is to download the latest full OTA image from Google and flash it through TWRP. And yes, flashing the OTA through TWRP will work, although you will end up losing TWRP and will need to reinstall it after fully booting the system.
@akellar: His boot.img is the wrong one. Flashing Magisk won't help here, based upon what trizzv has said.
Flash flactory image if all else fails. Don't panic. I got into a similar situation.
Strephon Alkhalikoi said:
@trizzv: There should be two ways for you to resolve your issue. The first and arguably the least painful is to change your slot and reboot, which you can do in the reboot menu of TWRP. The second is to download the latest full OTA image from Google and flash it through TWRP. And yes, flashing the OTA through TWRP will work, although you will end up losing TWRP and will need to reinstall it after fully booting the system.
@akellar: His boot.img is the wrong one. Flashing Magisk won't help here, based upon what trizzv has said.
Click to expand...
Click to collapse
I can't drag any files to my phone and right now it doesn't have anything-- magisk, TWRP file, or boot.img
azpatterson3 said:
Flash flactory image if all else fails. Don't panic. I got into a similar situation.
Click to expand...
Click to collapse
What would be the steps? Fastboot? Tried that but I couldn't get it to work
trizzv said:
What would be the steps? Fastboot? Tried that but I couldn't get it to work
Click to expand...
Click to collapse
https://developers.google.com/android/images
If for some reason it won't write and ends with an error. Open the flash script and remove the "-w" on the last line before it says "update"
I wonder, since you can boot into TWRP, if sideloading an OTA image won't fix your boot partition -- as I understand it, OTA's would overwrite and essentially reinstall/reinitialize the boot partition... If others concur or you decide you wish to try this route, say so and I could lay out steps to take...
But, if anything, reboot into Bootloader (can be done from TWRP), open up a command prompt (elevated, or powershell if you're more familiar with), have it directed at your platform-tools folder (or whatever folder you have adb.exe and fastboot.exe), and input the commands
Code:
fastboot --version
and
Code:
adb devices
*to load emulator and such...
if, after all of this, those two commands return info without an error, that should establish that you would be good to go in re-flashing the boot partition (as well as the system, vendor, modem, etc.) without losing any data and, at the very least, confirm that you have fastboot working...
do these and get back to us/me and can take steps from there towards repairing your pixel...
use Deuces Bootloop-Recovery & Flashing Script and just follow instruction :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
simplepinoi177 said:
I wonder, since you can boot into TWRP, if sideloading an OTA image won't fix your boot partition -- as I understand it, OTA's would overwrite and essentially reinstall/reinitialize the boot partition... If others concur or you decide you wish to try this route, say so and I could lay out steps to take...
But, if anything, reboot into Bootloader (can be done from TWRP), open up a command prompt (elevated, or powershell if you're more familiar with), have it directed at your platform-tools folder (or whatever folder you have adb.exe and fastboot.exe), and input the commands and *to load emulator and such...
if, after all of this, those two commands return info without an error, that should establish that you would be good to go in re-flashing the boot partition (as well as the system, vendor, modem, etc.) without losing any data and, at the very least, confirm that you have fastboot working...
do these and get back to us/me and can take steps from there towards repairing your pixel...
Click to expand...
Click to collapse
Please let me know what the steps are. Will try it today.
trizzv said:
Please let me know what the steps are. Will try it today.
Click to expand...
Click to collapse
...the suggestion @goti(0) actually gave is rather simpler, but do require pretty much the same steps (downloading factory image, extracting, placing the files in correct place, etc.)...
What did the commands return when you entered them? I am not reluctant to give you the steps, rather I gave you those commands to narrow down where your issues might be; if your fastboot and emulator aren't set up properly, giving you further steps might carry you down a less-stable and "skewed" path because things would be "based" at it's source incorrectly...
Let us/me know what those commands return and I'll get those steps to ya right away!
goti(0) said:
use Deuces Bootloop-Recovery & Flashing Script and just follow instruction :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
THIS WORKED!!!!! THANK YOU so much for the suggestion.
trizzv said:
THIS WORKED!!!!! THANK YOU so much for the suggestion.
Click to expand...
Click to collapse
it was a great suggestion...I'm glad it worked out for you! :victory:
Also you can just reflash corrupt boot.img the original for what image you have. You can load on flash drive through your type c .
There's a lot of ways to fix your stuff
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.