Database Info

[Need Fast Help Please!] Softbrick? Wiped everything with TWRP (System,Bin,Data)

Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again

Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?

jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse

I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2

jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/

LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok

Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !

[Q] Deleted my OS! | OnePlus One

Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)

BlaHBlaH525 said:
Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
Click to expand...
Click to collapse
Could you post the fastboot and adb commands and results you get from executing them in CMD?

abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
I've been struggling the hole day long with the same problem.
Maybe you could read my thread. : )
Link

abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?

BlaHBlaH525 said:
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
Click to expand...
Click to collapse
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.

abde27 said:
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
Click to expand...
Click to collapse
My phone is listed as
Fastboot Interface (Google USB id)

BlaHBlaH525 said:
My phone is listed as
Fastboot Interface (Google USB id)
Click to expand...
Click to collapse
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?

abde27 said:
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
Click to expand...
Click to collapse
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD

BlaHBlaH525 said:
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
Click to expand...
Click to collapse
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.

abde27 said:
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
Click to expand...
Click to collapse
Yeah I used that guide. And yes, what you stated is true. But another thing is that when I install the ROM, it says No MD5 file, but when I check the zip file, it says that there is a file called md5sum-fastboot.md5, I think that that is what TWRP is saying.

Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon

timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
Click to expand...
Click to collapse
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/

timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
Click to expand...
Click to collapse
BlaHBlaH525 said:
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
Click to expand...
Click to collapse
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1

abde27 said:
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
Click to expand...
Click to collapse
I have the latest version anyways
So, anything else?

Recovery flashable version is the easiest solution.
Transmitted via Bacon

timmaaa said:
Recovery flashable version is the easiest solution.
Transmitted via Bacon
Click to expand...
Click to collapse
Is that what I should do? If so, could you tell me how? Please xD

BlaHBlaH525 said:
Is that what I should do? If so, could you tell me how? Please xD
Click to expand...
Click to collapse
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon

timmaaa said:
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
Click to expand...
Click to collapse
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...

BlaHBlaH525 said:
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
Click to expand...
Click to collapse
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon

timmaaa said:
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
Click to expand...
Click to collapse
The URL is
https://cyngn.com/products/oneplusone/
The name is
cm-11.0-XNPH33R-bacon-signed-fastboot.zip with the MD5 Checksum of 2c5bcbb3230501f2b841b56cac392bcb

[Q] cm11 -> cm12 flashing issues

so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?

ItsDeadEnd said:
so, i recently updated my oneplus one from cm11 to cm12.1 and when cm12 loaded in, i got a repeated message that com.android.phone has stopped and the quick settings bar displayed that i had no sim card in. so i tried reflashing, and the same problem. i redownloaded and reflashed... same problem.
so, i went into twrp and performed a full wipe, thinking that i'd push a new zip using twrp's mount function. the problem is, when i went to mount, no drive appeared on my computer. and when i went to fastboot to flash it manually, fastboot said that 'Image is not a boot image' . the same thing happens whenever i try to re-flash recovery as well. so how can i get an os back on the system if fastboot won't cooperate and twrp is essentially useless?
tldr; no os on oneplus one, fastboot wont flash boot image, twrp mount and twrp adb wont do anything. What do?
Click to expand...
Click to collapse
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?

Heisenberg said:
What's the exact command you're using with fastboot? Are you only attempting to flash the boot.img? If so, why only that?
Click to expand...
Click to collapse
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked

ItsDeadEnd said:
I am using "fastboot flash boot [zip]" i also tried "fastboot update [zip]", neither of which worked
Click to expand...
Click to collapse
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.

Heisenberg said:
You didn't answer my question, why are you giving that command? There are a dozen or so commands that you're meant to give when flashing with fastboot. The only time you use that command is when you're just trying to flash a kernel.
Click to expand...
Click to collapse
what commands would you suggest i do then? because those are the only things i used other than the wipe command

ItsDeadEnd said:
what commands would you suggest i do then? because those are the only things i used other than the wipe command
Click to expand...
Click to collapse
Well it depends on what you're trying to do. As I said, the "fastboot flash boot boot.img" command will only flash a kernel. You really shouldn't be messing around with fastboot if you don't actually know what you're doing, that's how phones get bricked. Go to my guide and follow the instructions in section 8:
http://forum.xda-developers.com/showthread.php?t=2839471

[SOLVED]
apparently sometime between me instlling cm11 and installing cm12, my oem got re-locked. which prevented me from flashing anything new.
i ran:
fastboot oem unlock
and fastboot flash boot boot.img
and voila
help thread for those with the same problem
http://forum.xda-developers.com/show....php?t=2839471
thank you for the help!

Cannot sideload OTA

I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?

km8j said:
I'm trying to go NMF26U from NMF26O (rooted, stock rec) and I have the ~48mb OTA file. I boot to recovery, to go apply update from ADB and attempt to sideload. I get to Step 1/2 and then says error applying update 20 kDownloadState InitializationError and then E:unknown volume for path. Installation aborted. What am I missing?
Click to expand...
Click to collapse
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.

Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices

I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)

TonikJDK said:
Just flash the whole image from Google. Edit the flash all bat file and remove -w from the file so you save your data and apps.
Then reroot.
Click to expand...
Click to collapse
Hmm... Okay I will try this if next method fails. Thanks.
mrZoSo said:
Get the full OTA from here - Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
donslade said:
I had the same issues. Made sure I had the latest ADB/Fastboot executables and correct drivers from Google. Lastly for me I also had to be on a USB2.0 port on my PC since it won't work on a USB3.0 port on my machine.
I ended up doing the full OTA image in the link via ADB. Still rec'd the E:unknown volume error but everything installed correctly and works as expected.
FYI: I have unlocked boot loader but everything else is stock (stock bootloader, stock recovery, stock system, etc.)
Click to expand...
Click to collapse
So did you still adb sideload the Zip? Did that wipe the device?

km8j said:
Hmm... Okay I will try this if next method fails. Thanks.
So did you still adb sideload the Zip? Did that wipe the device?
Click to expand...
Click to collapse
Yes and it did not wipe the device.

Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update

mrZoSo said:
Here's a nice little walkthrough
Pixel: How to Manually Sideload an OTA Update
Click to expand...
Click to collapse
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.

This worked. Thanks all!

TonikJDK said:
That guide says use Minimal Fastboot. That is bad advice. It may work for a sideload, but many of the new fastboot commands are not in it, and it does not support our larger partitions. Or our dual partitions.
So sub the Google versions of fastboot and adb in that guide.
Click to expand...
Click to collapse
True, but the guide was written just for sideloading the OTA, and works at this point.
Moving forward, you can always get the platform tools w/ADB, Fastboot from Google, without having to get the whole SDK or Android Studio.
Latest Platform Tools from Google for Windows

Question Pixel 7 Pro Fastboot "device requires partition vendor_kernel_boot"???

HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....

Update: tried again via PixelFlasher and did not encounter the error so I guess if anyone else hits this issue and sees this post.... just use PixelFlasher(?????) No idea the why or how but seems to be good now.

Sounds like you were trying to flash in Fastboot mode rather than FastbootD.

Tomadock said:
Sounds like you were trying to flash in Fastboot mode rather than FastbootD.
Click to expand...
Click to collapse
Negative. I also thought that might be the issue and attempted it (the actual command it was running, not the entire script again since that would reboot to bootloader again) in FastbootD as well to the same result.

Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
i tried the latest version of "SDK Platform Tools"; it worked for me

Sceleratis said:
HI all,
While attempting to update my Pixel 7 Pro (while retaining root, via the modified factory zip method where you root init_boot.img, then replace it in the factory zip, then run google's provided flash-all script) I've been encountering this issue when flash-all reached its last step of flashing the actual zip with the images via fastboot:
"fastboot: error: device requires partition vendor_kernel_boot which is not known to this version of fastboot"
This happens on both the new firmware as well as with the firmware I flashed through this method previously. New firmware after this causes a boot loop, while performing a flash of the old firmware results in the same error but at least gets me back into the system in the state it was in before attempting to upgrade.
Any idea why this is happening? I've ensured fastboot & adb are both up to date and attempted from both Windows and a Fedora laptop both to the same error. It's worth noting I installed the old (current) firmware previously through the same method successfully (before this) so not sure why it's decided to not work now....
Click to expand...
Click to collapse
Literally error says everything....
You need latest platform tools that supports vendor _kernel_boot partition
Google added vendor kernel boot partition on P7 series that's been supported only on latest platform tools