Database Develop

HONEYCOMBE-- 07-July-2011-- With GPS fix

If you like that I'm doing this, then a thanks is cool, PLEASE DONATE, TIME OR MONEY BUT GIVE SOMETHING TO THESE DEVS!
http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
New - No more partition editing required!
HC16JUN2011
HD Video
-Changelog
Like with any rom, YOU MUST WIPE CACHE, SYSTEM AND DATA, this rom especially, the is a pre alpha and has issues with cache, if you don't clear your info every time you will run into problems. I also clear Dalvik Cache and Battery Stats.
Old info on how to partition
STEP 1 – You need the new NVFlash click here for the unpartitioned onces(may need these)
NVflash edit- pretty simple you need to change the android fastboot full, you'll find that file towards the top of the nvflash folder or you can download my premade ones: (BUT I DIDN'T FORCE YOU TO DOWNLOAD THESE, IF YOU BRICK YOUR DEVICE BY USING THESE THEN YOU BRICKED IT NOT ME, YOU HAVE BEEN WARNED)
Sorry about the mega upload, working on getting my server up, also CWM is untested, it had some problems but I believe that was due to file size.
Clockwork Mod folder
Stock Recovery Folder
The section your looking for looks like this
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=209715200 <---(here is the money)
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=system.img
minus the arrow and the here is the money you'll find the size listed as 209715200, you need to change that to 536870912, once you save go to here to setup your APX drivers and prepare to flash according to the link
STEP 1.1 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY Download Here
Make a copy of your nvflash folder, I name it PIXEL QI CW Mod
STEP 1.2 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY
Thank you darknao
Quick & Dirty method :
Extract the recovery.img from the clockwork.zip, and copy it to the nvflash folder(replace the original one).
Step 2
You need then to put your device into force recovery mode, so turn off your device, then power it on while holding the power + the volume down button till a orange and a yellow lite light up.
Step 3
Run the download.bat file described in the nvflash or unbrick your adam thread - now you can change the file name of the rom to update.zip and flash freely!

Reserved for other usage

Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.

Amon Darthir said:
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Click to expand...
Click to collapse
Gapps are included however this build didn't have them, they had alot of problems with the sync feature, but in theory you should be able to use the latest gingerbread gapps, I will test that right now.
-OK I tested it out, the google setup frooze up on me, after restarting I was able to get into the initial setup, but I have the wifi only model, so I'm going to look into the gapp issue, see if I can find a way around.
-Tried a couple more copies of gapps including a HC edit for the nook sdk HC-- I would press more into this but with the rate of the updates I think its kinda pointless, for now Im going to adb push the market and see what I can get working, hopefully not in-vain since MrGuy and DJSteve move so fast with the updates.

after you use nvflash it will start to boot.. (this would be before flashing update zip) so should I power it down while its booting that first time in order to reboot to recovery and flash the zip?

I do but you don't have to if you use clockwork mod, it doesn't really matter, since you will be building your Dalvik cache once you install your rom.

$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script

jakobdroid said:
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
Click to expand...
Click to collapse
what operating system do you have? Is your adam in apx mode, and did you edit the android fastboot already? is it still a .bat file

osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?

jakobdroid said:
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
Click to expand...
Click to collapse
APX is the force recovery, the drivers are included with the NVflash, you must put your device into force recovery, with your device off you press volume down + power till you get your two lights to light up by the power cord, it'll be red and yellow, this is force recovery mode, I am using CW with it and I have listed above how to flash the CW with the increased partition. If you can't figure it out I will be adding the NVflash files with CW mode and non CW mode with the partition edits tonight. I will be turning the change log into a FAQ as well.

Just flashed the ROM and it is awesome. I was just wondering how to get a file managers working. I can't see my sd card. But otherwise, its amazing that honeycomb is up so fast.

okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?

jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
I'm downloading the file now, working on military lines so its slow to download but that way I can get a better idea of whats going on, also whats your operating system.

jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Sounds like you're using linux like me. Are you on ubuntu. Cause I tried and tried and even with chmod and sudo and still got the same error. Consider this post though from: http://notioninkhacks.com/forums/viewtopic.php?f=90&t=1651&start=30
Hey gibson, thanks heaps for that! Actually, yourncomment before asking which folder I was in did it. Very strange, I had to run the commands from 2 folders above the extracted one, then symlink all the other files into the folder I was running from. Will post more later for people who run into similar issues, likely over at the unbricking thread. For now I've got a dualboot setup, and am running a minimal natty rootstock. I tried using the full omap4 image (ubuntu's default arm), but could only get it booting with lots of errors and no gui. Will be aiming to install the netbook desktop (unity 2d) in the next few days.
Re the post above, rayman's boot image already includes the kernel, so it's not needed in the rootstock command. Re the other options, probably will work, but remember rootstock is limited in what you can build... I.e., unless you have heaps of physical ram, you will probably only be able to build a few packages. Head over to xda, and the ubuntu on adam thread there for more info. We have experimented a lot with rootstock builds, and some of that might be useful.
Has anyone tried raymans boot.img with a natty rootstock? Did it work, and has anyone gotten a 2d unity gui up and running? My minimal natty rootstock boots fine, though I notice a few errors. Not sure if they are problematic or not. In any case, the build I made seems to be missing some important wireless tools, so I will likely rebuild it again with them in it soon. Am I likely to run into any problems using rayman's boot image, and steveh's kernel, with a natty build? Happy to post up my work if I get anything decent. Cheers.

osx 10.6.6, thank you!

jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Also consider this: http://forum.xda-developers.com/archive/index.php/t-895388.html

Saved me some time thank you...

daiuton said:
Saved me some time thank you...
Click to expand...
Click to collapse
Don't know if the problem is solved yet but that doesn't take away from this honeycomb coolness. So happy to have so much use out of this Adam. Thanks.

that really didnt help, thanks though. i guess i will instal ubuntu in parallels and give it a shot...

Two problems here:
-How can i mount the adam with the computer? To move next updates and update in the next releases
-There is any gapps working (market,etc...)?

Installation Aborted [status 0]

I keep on getting this error when trying to flash a custom ROM into my phone. Is there a way to manually apply the ROM?
I tried booting into recovery then conecting my phone through usb and running the following commands through cmd: "adb push update.zip /sdcard/update.zip". then it tells me if I want to push "update.zipj", but once I press enter it gives me, "error: device not found"
Here's the cmd log:
Code:
C:\Users\Admin>cd\
C:\>cd\android\android-sdk\tools
C:\Android\android-sdk\tools>adb devices
List of devices attached
000000000000 recovery
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zip
protocol failure
C:\Android\android-sdk\tools>
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zipj
error: device not found
C:\Android\android-sdk\tools>
Am I doing the manual flashing corrrectly? I figured manually flashing the ROM would stop the error from coming up. Could someone either show me or point me in the right direction on how to fix this error and/or possibly how to manually flash the ROM in detail. I've already searched and I keep seeing threads with people asking for similar problems but with no real answer.
any help is appreciated.

1. adb push does not flash a ROM - just copies the file to the SD card
2. Looks like you are in recovery and you cannot push a file, unless you mount the SD card in recovery
Not sure what you mean "manually apply the ROM". ROM flash has to be manual, there's nothing automatic about it.
And, if you had really searched... I am sure you would have found atleast 10 references on how to flash a ROM.
Anyways, here's a link that will give you enough information to just about do anything with your CDMA Hero: http://forum.xda-developers.com/showthread.php?t=1063843. BTW, this is a sticky right at the top of where you posted this question...

BOOM. lol. Also the status 0 is an improper mount command, or you have a bad version of busybox. What zip were you trying to flash out if curiosity? And are you rooted, if so how did you do it?

What I meant when I said "manually" I meant to do it through command prompt instead of Rom manager or through recovery. And I was mainly searching for a fix for the status error I was getting. Which there is no info about that in the link you posted, however it does help with flashing my Rom through command prompt. :]
@il duce It's called "nfx speedy kingdom". I've been using the salsa builds in the development section, but I came across this Rom and it says it has everything working including Bluetooth so I wanted to test it out. Ill try using the tutorial on flashing roms without an sdcard and see if it works.

1. By the looks of it, adb is not recognizing your device... so, first and foremost you will have to setup everything properly for adb to connect
2. Even if adb recognizes the device, to the best of my knowledge, you cannot flash anything through adb, you must have confused it with fastboot. And, that too is possible only if you have engineering spl

One of the links from the thread you linked to show how to push the rom to system/data and use cmd to flash it from there, but the rom I'm trying to flash is over 300mb so it doesn't fit :/
I guess I'll try contacting the dev and see if he knows of a solution, might be that the file isn't correctly packed or signed?
edit: flashing using RA recovery it gives me the following:
Code:
E:Missing file:
system/lib/libvoAMRWBDec.so
E:Verification failed
Installation aborted
Does that mean it's the ROM that's corrupted?

Dude wtf... thats an evo rom.

Also, andy is correct 100%. Cease and desist before you bork your phone.

o_o he has it under heroc roms.
http://sprint.hero.ptyork.com/?cat=1
Edit: Sorry everyone for the questions, I just pm'd nfinitefx and he cleared out everything for me.

Android 4.2.1 (JOP40D) for Nexus 7

Android 4.2.1 (JOP40D) for Nexus 7 Wifi and 3G+
Manual Update Available [Updated]​
Install:
Those with a custom recovery can just download the zip below, move it to their device, and flash away. If you're running stock recovery, substituting only the zip file name in Step 2.
Just after users began reporting that your Google Nexus N7 device were receiving an update to Android 4.2 Jelly Bean (build JOP40C, to be precise), it looks like the manual update package is available for download. As could be expected, this coincides almost perfectly with the launch of Google's newest additions to the Nexus family – the Nexus 4 and 10.
For those ready to download and install manually, the process is easy. If you have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual. Those with stock recovery should keep the file on their computer, and just follow a few easy instructions:
Disclaimer: I'm not responsible in case of brick of your device - proceed at your own risk.​
Step 1.
- Reboot your Google Nexus 7, holding the Volume Up and Volume Down buttons while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, press Volume Up and the Power button together, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
- Connect your Google N7 to your computer with a USB cable.
- Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
- Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the JOP40C zip file you've downloaded.
Type in the following:
For the Nexus 7 "NAKASI"
Code:
adb sideload 659e6288b87d.signed_nakasi_JOP40D_from_JOP40C.659e6288.zip
For the Nexus7 3G+ "NAKASIG
Code:
adb sideload 65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
- Reboot and enjoy! You are now running Android 4.2.1 on your Nexus

I modified my OP and put online the updates for both versions of Nexus 7

Hello
The link for the wifi N7 is broken I think

My N7 is rooted, stock rom, cwm recovery, voodoo ota rootkeeper, supersu. I d/l the update from Droid Life and copied it from my computer to the N7 internal storage. Booted into cwm recovery, chose to install zip from sdcard, chose the d/l'd file from the /0 folder (filename 659e6288b....zip), chose to reboot system, answered 'Yes' to preventing flashing stock recovery, answered 'Yes' to keeping root. All is good. Still have root and cwm recovery.

Foggy79 said:
Hello
The link for the wifi N7 is broken I think
Click to expand...
Click to collapse
I have the same issue.
Sent from my Nexus 7 using xda app-developers app

Will this wipe my data, let me know so I can make a backup, thanks
Sent from my Nexus 7 using xda premium

OP Why you don't post oficial Google link directly from Google servers? Also here is a thread already http://forum.xda-developers.com/showthread.php?t=1745781 and in instruction its better to explain how to open cmd Window/cmd prompt in a folder "ctrl+right click" in an empty space where your zip is and (select open cmd here).
Sent from my SPH-D710 using Tapatalk 2

philos64 said:
Install:
Those with a custom recovery can just download the zip below, move it to their device, and flash away. If you're running stock recovery, substituting only the zip file name in Step 2.
Click to expand...
Click to collapse
Link is Broken above...... but I worked out it is here
http://www.androidfilehost.com/?fid=9390202682628636802
What do I need to do if I have custom recovery but am still on 4.1.2?
Thanks

Try to flash this with TWRP 2.3.2.1 but got error Status 7, same with CWM 6.0.1.0, tried to google what's going on but I can find none, can someone help me with this ?

mr_gem said:
Try to flash this with TWRP 2.3.2.1 but got error Status 7, same with CWM 6.0.1.0, tried to google what's going on but I can find none, can someone help me with this ?
Click to expand...
Click to collapse
I had this problem with the first 4.2 update and now the same again with 4.2.1.
Last time I had to put the bootloader back to stock (drastic) to get the update,.
sideload doesnt work either.
Motorola Atrix (AOKP JB)
Nexus 7 (Stock)
Past life:
HTC Desire HD reboot loop overheating.
Nokia N900 micro usb port loose.

Omar04 said:
OP Why you don't post oficial Google link directly from Google servers? Also here is a thread already http://forum.xda-developers.com/showthread.php?t=1745781
Click to expand...
Click to collapse
Because it's my choice, and if you don't use it, don't use it :silly:
and if you read this thread, have you got some instructions for install it? NO
Have you find one link from Google servers ? Not yet - at 03.15 PM - 29 Nov 2012
Omar04 said:
and in instruction its better to explain how to open cmd Window/cmd prompt in a folder "ctrl+right click" in an empty space
Click to expand...
Click to collapse
I surprised that you don't know how to use the command lines,
And if you think about the new users , they can read a lot of guide which explain how use the command lines. It's one of the basic of installations under Android
and it's not the usefulness of this post !!!
Omar04 said:
where your zip is and (select open cmd here).
Click to expand...
Click to collapse
And if you click to "DOWNLOAD LINK" you will see that you can download the files
With a lot of pleasure

The download link for the Nexus 7 wifi aka "NAKASI" is repaired

Downloaded update from official Google link, flashed in CWM Recovery, kept bootloader, kept root. All is well.

Help Help PLEASE
OK I did everything and the update worked for JOP40C. I`m running stock so no rooting.
Then I wanted to upgrade to JOP40D.
I got to just after the little green android with the exclamation mark on it. I then held the Power button and the Up button. Instead of getting the next menu it just died on me. :crying:
So what now?

I went through this project step by step and was just about to flash manually when the OTA symbol magically appeared in my bar.
Oh well... I guess I'll take the easy way this time.

St1ck33 said:
Downloaded update from official Google link, flashed in CWM Recovery, kept bootloader, kept root. All is well.
Click to expand...
Click to collapse
Sounds good for you :good:
AfrikaansAndroid said:
OK I did everything and the update worked for JOP40C. I`m running stock so no rooting.
Then I wanted to upgrade to JOP40D.
I got to just after the little green android with the exclamation mark on it. I then held the Power button and the Up button. Instead of getting the next menu it just died on me. :crying:
So what now?
Click to expand...
Click to collapse
- If you're running stock recovery, substituting only the zip file name in Step 2.
Step 2.
- Connect your Google N7 to your computer with a USB cable.
- Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
- Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the JOP40C zip file you've downloaded.
type this line command for N7 3G:
Code:
adb sideload 65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
for N7 wifi only go to OP..
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update
and reboot for finish
PMOttawa said:
I went through this project step by step and was just about to flash manually when the OTA symbol magically appeared in my bar.
Oh well... I guess I'll take the easy way this time.
Click to expand...
Click to collapse
Use the update by OTA...let's go

Running 4.2, rooted, CWM latest recovery (forget version). I had previously done the clear data from one of the Google apps and succesfully got my 4.2 from 4.1.2 OTA - CWM handled it just fine. I didn't want to take any chances doing that again, I downloaded this file, flashed in CWM, rebooted and all seems fine. Still have root, still have swype, still have cerberus.
Thanks OP!
Edit: Due to the new /0/ emulated sdcard for multiple users, I copied the zip file to my sdcard through windows - but CWM couldn't see it. I had to navigate to /0/ and then CWM could see it. Just a heads up.

Thread will be closed
Code:
[B][COLOR="Red"][CENTER][SIZE="4"]This thread will be closed very shortly because it's now useless.
"Developers Google"website has released updates ;)
I will deleted all download links.[/SIZE][/CENTER][/COLOR][/B]

philos64 said:
Code:
[B][COLOR="Red"][CENTER][SIZE="4"]This thread will be closed very shortly because it's now useless.
"Developers Google"website has released updates ;)
I will deleted all download links.[/SIZE][/CENTER][/COLOR][/B]
Click to expand...
Click to collapse
Edit: NM there's a thread linking to all OTA updates. you can delete this post.

Sorry, but your post is useless too
I have contacted Mods for close this thread

[Q] [TWRP]Bootloops, can't mount to Windows to put new ROM or saved backup onto phone

My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?

rougegoat said:
My current situation is as follows:
ROM on it is bad and bootloops
Storage was wiped for a pure clean install
TWRP 2.5.0 doesn't seem to have any method to mount while in Recovery
As a result, I cannot boot it up to add the good files and I cannot mount it in Recovery to add the good files
I am at work and as such cannot use ADB.
If I can get it to mount, I can copy over the known good backups or just a known good ROM I can flash. There just doesn't seem to be any way to get it to mount in Windows 7 or 8. Does anyone have any suggestions?
Click to expand...
Click to collapse
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out

wranglerray said:
Your only option now is to run the Stock ruu and return to stock. Theres plenty of threads on this forum that describe the procedure. You should never wipe the storage just for this reason. its much easier and less time consuming to flash a nandroid backup than having to revert back to stock via the ruu. Good luck and I hope everything works out
Click to expand...
Click to collapse
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?

rougegoat said:
I managed to find a machine I have sufficient privileges on for ADB. I can now push files to it. Do you know off hand what the path needed for TWRP backups is?
Click to expand...
Click to collapse
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions

wranglerray said:
should be /mnt/sdcard0/twrp/backups
but you wiped storage. Can you boot into fastboot? if so you can run the fastboot command
fastboot flash nameofrom.zip
you'll have to place the rom zip in the same directory as fastboot but fastboot should interrogate the zip file and flash the correct partitions
Click to expand...
Click to collapse
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.

rougegoat said:
I can get there. The issue is the one zip I have on hand doesn't seem to like being pushed that way. Rather than sit through a gig download I was just going to push a backup of stock I have on hand into the proper folder. At the very least I'd attempt it while downloading a stock+root rom.
Click to expand...
Click to collapse
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS

wranglerray said:
ok the correct path according to my phone's file system is /sdcard/TWRP/BACKUPS
if those files don't exsist you can create them from adb shell
mk dir sdcard
cd sdcard
mk dir TWRP
cd TWRP
mk dir BACKUPS
exit out of adb shell by issuing the command exit
the
adb push nameofbackup.win /sdcard/TWRP/BACKUPS
Click to expand...
Click to collapse
Giving it a shot now.

Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2

wranglerray said:
Sorry my syntax was off it's mkdir without a space
Sent from my HTCONE using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
(Edit) Success getting it to be usable again. Now to start from scratch. (/edit)

rougegoat said:
No worries, I'm versed enough commandline wise to know what you were getting at. Unfortunately it seems that random number path for the device chunk has changed since I did my backup(probably because of my wiping and being an overall idiot). The stock+root zip of a rom finished downloading though, so I'm flashing that now. Hopefully that ends this ordeal.
Click to expand...
Click to collapse
good luck! post your results i'd be interested in knowing how it ends up.

Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
---------- Post added at 09:57 PM ---------- Previous post was at 09:51 PM ----------
cburch85 said:
Hey rogue.... went through this same problem about four days ago, almost blew my brains out because I thought I would have to smash my phone and return it through the best buy protection plan. Anyways... the ONLY way to fix your problem is to use the Sprint HTC One RUU. Boot your phone into fastboot usb mode and run the RUU. Takes about 10-15 minutes, and will have you COMPLETELY back to stock. From there, you need to start from scratch unlocking and installing the recovery. ViperRom is the only rom that won't bug out your sprint phone atm. Also be sure you relocked your phone before you run the RUU. I'm super busy atm and can't go find the RUU links, but google it and i'm sure you can find it. If not, i'll get you the links later if you pm me. Peace bro and good luck.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2250904
I know another person suggested this earlier, but failed to mention that sideloading once you're caught in this loop won't work. Run the RUU, unlock, and flash ViperRom.

Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.

Rooted HTC one, no os, don't know how to push rom
I accidently wiped my os while putting a new rom on. I am INCREDIBLY inexperienced with this and really had no business fooling around with it. Regardless, I have the HTC One rooted with TWRP but cant get the new rom on to the phone. I'm on a mac and android file transfer is not recognizing my phone. Any help anyone could give would be great.

Try putting the rom on a usb stick and using an otg cable then mount it under twrp and flash from there?
Sent from my HTC One using xda app-developers app

Good Info
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
Thanks for the Info

[How-To] Install Oreo OTA! [T-Mobile]

*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files

There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.

Screenies
Here you go

Installation went smooth. thanks for the OTA.

now towait for the root and all will be set

wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.

Making a test twrp real quick

Damn...thanks for your work

joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk

Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!

can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff

where's the TWRP, so only use a fastboot flash boot image.zip?

joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!

@jhofseth please write me on hagnouts

please message me on hangouts people who want to help [email protected]

When you brick and have to go to a leaked 8.0 image

Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.

Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?