I am trying to get Arch to run on my zf2 and I got both and unmkbootimg and a mkbootimg binary. I tried to unpack the stock boot.img, replace the kernel and initramfs with those from Arch, change the command line and boot that image using `fastboot boot new_boot.img` but nothing happened (no I did not expect it to be this easy, but gotta try still!)
So my question is: once I have a booting boot.img I can populate the /system partition with Arch and then see if everything will start up properly, so how can I make a boot.img using the kernel and initramfs from Arch?
I am rooted, have TWRP and my bootloader is unlocked btw
fastboot boot command isn't supported on ZF2.
You have to flash boot and then boot it as usual.
Hi.
Can someone help me to get back to scratch?
I want the OTA update. (Software update 2.10.401.1 (831.88MB))
The phone is unlocked, rooted, stock ROM, I have deleted some default apps. S-ON. And I do not have any backup to restore from.
I have read a hell lot of post, but I can't figure out what way is the best for me. I have tried to flash Stock recovery, but can't update OTA.
After what I can read I might need to flash an RUU?
Can some help me to what I need to do, and in with order?
(And eventually link to correct RUU, if needed)
Note: I'm a Linux user
Note: I have an idea, that i might be the best solution to start from scratch. (Correct me if you think I wrong) So I can make a backup before rooting, and so on.
I have backup, of all my personal stuff, so a complete wipe, would not be a problem.
My phone is:
Code:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***
Code:
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.02_U11440261_60.03.50505G_F
OpenDSP-v22.2.6-00452-M8994_0318
OS-1.40.401.8
May 27 2015,22:14:34(549783)
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226066******
(bootloader) version-main: 1.40.401.8
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__Y13
And stock recovery is right now: M9_stock_recovery_2.10.401.1.img
hyhansen said:
Hi.
Can someone help me to get back to scratch?
I want the OTA update. (Software update 2.10.401.1 (831.88MB))
The phone is unlocked, rooted, stock ROM, I have deleted some default apps. S-ON. And I do not have any backup to restore from.
I have read a hell lot of post, but I can't figure out what way is the best for me. I have tried to flash Stock recovery, but can't update OTA.
After what I can read I might need to flash an RUU?
Can some help me to what I need to do, and in with order?
(And eventually link to correct RUU, if needed)
Note: I'm a Linux user
Note: I have an idea, that i might be the best solution to start from scratch. (Correct me if you think I wrong) So I can make a backup before rooting, and so on.
I have backup, of all my personal stuff, so a complete wipe, would not be a problem.
My phone is:
Code:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***
Code:
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.02_U11440261_60.03.50505G_F
OpenDSP-v22.2.6-00452-M8994_0318
OS-1.40.401.8
May 27 2015,22:14:34(549783)
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 357226066******
(bootloader) version-main: 1.40.401.8
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__Y13
And stock recovery is right now: M9_stock_recovery_2.10.401.1.img
Click to expand...
Click to collapse
Either you flash a RUU or you restore a backup. Both can be found in my signature. Instructions how to use the backups can be found there, too.
Since you're using Linux and I never tried to use adb or fastboot with that OS I would suggest you to use the SD card method if you choose the RUU. Connect the SD card to your pc, copy the RUU to the root directory of a SD card that is not bigger than 32gb and formated to "fat32". Rename it to "0PJAIMG.zip" (that's a zero not an O), put it back into your phone and boot to Download Mode. Then follow the instructions on the screen. If your phone boots to system instead of rebooting to Download Mode during the process you just need to power your phone off and boot to Download Mode manually. The flashing process will then continue automatically.
Flippy498 said:
Either you flash a RUU or you restore a backup. Both can be found in my signature. Instructions how to use the backups can be found there, too.
Since you're using Linux and I never tried to use adb or fastboot with that OS I would suggest you to use the SD card method if you choose the RUU. Connect the SD card to your pc, copy the RUU to the root directory of a SD card that is not bigger than 32gb and formated to "fat32". Rename it to "0PJAIMG.zip" (that's a zero not an O), put it back into your phone and boot to Download Mode. Then follow the instructions on the screen. If your phone boots to system instead of rebooting to Download Mode during the process you just need to power your phone off and boot to Download Mode manually. The flashing process will then continue automatically.
Click to expand...
Click to collapse
Hi. Thanks
I'm think to use the RUU and SD methold then.
But a few questions before I start.
Bootloader: locked, unlock or does not matter?
Recovery: Stock, TWRP nad eventually should it be a speciffic version?
And just for a note on adb/fastboot on linux (Kubuntu in my case) it's quite easy:
INSTALL
Eventually install repository, if it's missing:
Code:
sudo add-apt-repository ppa:phablet-team/tools && sudo apt-get update
Install adb and fastboot:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Then use it as on windows. But instead of moving files to folders i reference it directly like:
Code:
fastboot flash recovery /home/myUserName/m9/Recovery_1.40.401.8.img
hyhansen said:
Hi. Thanks
I'm think to use the RUU and SD methold then.
But a few questions before I start.
Bootloader: locked, unlock or does not matter?
Recovery: Stock, TWRP nad eventually should it be a speciffic version?
Click to expand...
Click to collapse
If you use the SD card method the state of your bootloader doesn't matter (at least from my experiences). The recovery doesn't matter, either, since it's going to be overwritten by the stock recovery that is provided by the RUU.
Hello! I have recently used Pc Companion and went from Stock to LCA43 and flashed Twrp successfully. Now im attempting to flash New Kernel and flash appears to be successful but...upon reboot and checking kernel with adb command (adb shell cat /proc/version) and it continually shows old Kernel with Swan signature. Prior to this upgrade from Pc Companion i was running LDZ22D and flashed New Kernel and first attempt was flawless. but i cant seem to get LCA43 version Kernel to take.
Question: I wonder if my reboot process after flashing new kernel is preventing the install successfully or at somepoint should i be Wiping Cache and data maybe before the reboot? I have tryed Fastboot Continue, Fastboot Reboot, Fastboot Boot New_boot.img , but no matter what or how i reboot the SW3 it continues to boot on old Kernal after flashing new Kernel every time. Am i doing something wrong?
Please Help as User: Zr1 and myself are having same issues at this time. Thankyou in Advance
MotoDave I figured out the problem' You have to check version in normal system boot mode for adb to see the kernel version.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell cat /proc/version
Linux version 3.10.86-15588-g938d5b8 ([email protected]) (gcc version 4.8 (GCC) )
#1 SMP PREEMPT Sun Aug 23 07:42:42 EDT 2015
ZR1
zr1 said:
MotoDave I figured out the problem' You have to check version in normal system boot mode for adb to see the kernel version.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell cat /proc/version
Linux version 3.10.86-15588-g938d5b8 ([email protected]) (gcc version 4.8 (GCC) )
#1 SMP PREEMPT Sun Aug 23 07:42:42 EDT 2015
ZR1
Click to expand...
Click to collapse
Yes!...You are Correct!. Kernel was not seen from Recovery mode. But by connecting USB before booting up watch, i was asked ( during boot) if i allowed ABD Debugging and i selected always allow. After Watch booted i could then check Kernel and it displayed CrPalmers Kernel resulting in Success!!!
Thankyou Zr1 for your Expertise im glad somebody here could help!
Hi all[/FONT]
I really need your help guys
*** Software status: Modified ***
*** Locked ***
*** Security Warning ***
A51_Ul PVT SHIP S-ON
and the rest u guys know, i think
Now i'll tell you what i have tried already
I have Unlock my boot-loader and try to install custom ROM but i can't
I have tried to install RUU by memory card but failed with this msg "device halted due to large image update fail"
What i will do now, i don't know
I really need your help guys plzzz plzzz plzzz plzzzz :crying::crying:
looks like its patched now, no more unlocked bootloader for Pixel XL anymore
I tried this
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
I tried under Pie but it didn't work so I updated to Q still OEM is gray out, this runs fine without any issues
adb shell pm uninstall --user 0 com.android.phone
success
after I boot back with WiFi enabled browsed some websites still nothing is working in OEM, it stays gray out
I tried this too
adb shell /data/local/tmp/dePixel8
*** welcome to dePixel8 v0.3, by beaups! ***
*** if you paid for this, shame on you! ***
*** if you relock your bootloader while ***
*** running unsigned images, you will ***
*** be a SAD PANDA ***
*** DO NOT DO THAT! ***
*** ***
*** let's get started ***
[+] starting
[+] getting there, about 20 more seconds please
[-] it didn't work out this time
[-] after your device reboots, please try again
PS D:\4GB\SM-N910T-4.4.4\Pixel XL\lateast ADB platform-tools>