Develop Bugs

[Q] Herp a derp : what is meant with a custom recovery???

Hey there and really sorry for taking your time with something that problably will be solved within minutes >,<,
I'm trying to flash my One X (with cid : HTC__Y13) with maXimus but it isn't cooperating.
I've come to the part where I'm supposed to install a custom recovery, where I now notice now that I have no Idea what a custom recovery is...
I know, I know... I should have read up more before, but I must be stupid or something cause I can't find it !
//Sincerly
iConfide

iConfide said:
Hey there and really sorry for taking your time with something that problably will be solved within minutes >,<,
I'm trying to flash my One X (with cid : HTC__Y13) with maXimus but it isn't cooperating.
I've come to the part where I'm supposed to install a custom recovery, where I now notice now that I have no Idea what a custom recovery is...
I know, I know... I should have read up more before, but I must be stupid or something cause I can't find it !
//Sincerly
iConfide
Click to expand...
Click to collapse
it is the device meant to flash ROMs...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Use the Net
This will Help u my friend.
www.google.com

It allows you to install roms ...mods ....and if you have s off you can flash kernels from it

matt95 said:
it is the device meant to flash ROMs...
Click to expand...
Click to collapse
Okay, I see. Was abit too worried to just take a chance with the recovery-tool there, thanks there!

iConfide said:
Okay, I see. Was abit too worried to just take a chance with the recovery-tool there, thanks there!
Click to expand...
Click to collapse
Okay, new problem !
Thought I managed to install everything, cause it booted up and so on.
But when I unlock the phone, it's stuck in flight-mode =(!

Some people really should not be trying to flash a phone !!!!!!
Sorry ! :banghead:
Wright down ALL the steps you did ! So we can provide good help .... guessing is no fun !

MarcelHofs said:
Some people really should not be trying to flash a phone !!!!!!
Sorry ! :banghead:
Wright down ALL the steps you did ! So we can provide good help .... guessing is no fun !
Click to expand...
Click to collapse
Yeah, sorry, I thought it would be as easy to flash my One X as it was with my o2x.
I checked the log (kept it open) and I see now that I failed to flash Fastboot KIT V8.5!
I also thought that I (like the old times) should have flashed the rom in the custom recovery, but I see that I should probably have done that in Windows aswell!

Partial correct , you need to flash the rom in recovery and the boot.img that is found in the rom.zip file with fastboot commands from pc to the phone in fastboot mode
And let's be honest, if you have to ask what a custom recovery is afterwards then the homework is not done !

The recovery is kinda like BIOS on Windows. This sentence really cleared up my thoughts.
Sent from my HTC One X using xda app-developers app

superioor said:
The recovery is kinda like BIOS on Windows. This sentence really cleared up my thoughts.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Great explanation!
Will re-use that if ever I need to

MarcelHofs said:
Partial correct , you need to flash the rom in recovery and the boot.img that is found in the rom.zip file with fastboot commands from pc to the phone in fastboot mode
And let's be honest, if you have to ask what a custom recovery is afterwards then the homework is not done !
Click to expand...
Click to collapse
I've found the boot.img and I tried to flash it through fastboot mode, just said Failed: Remote not allowed.
Like I said before about the recovery-thing : wanted to make sure I didn't **** things up (which I evidently did anyways).
And yes, I do understand your point about that the homework haven't been done.
I noticed (and read) the first time you wrote about "some people", I've gotten the point .
Promise that I will read up more!

Is your bootloader still unlocked ? Flashing recovery went oke ?

MarcelHofs said:
Is your bootloader still unlocked ? Flashing recovery went oke ?
Click to expand...
Click to collapse
Home in 1 1/2 hour. Bootloader is still unlocked and cwm is installed. Installed maximus through recovery but as said... can't get the phone out off airplane-mode :<.

Oke uhm the maximum rom is a ICS rom ? Not trying to flash a JB rom did you ?
And if the bootloader is unlocked you should flash the boot.img oke . Hmmm
You did
fastboot flash boot boot.img
With the command in dos prompt ?

MarcelHofs said:
Oke uhm the maximum rom is a ICS rom ? Not trying to flash a JB rom did you ?
And if the bootloader is unlocked you should flash the boot.img oke . Hmmm
You did
fastboot flash boot boot.img
With the command in dos prompt ?
Click to expand...
Click to collapse
maXimus is a JB-rom, yes.
Yes, fastboot flash boot boot.img is the command I used.
EDIT: I missed the point where I was supposed to extract and start a .bat-file, apparently it's been done before and I must have missed out on searching for that for some strange reason...
*snip snip*
Tried updating 8.0.1 to 8.5.0 using the otherwise promising OTA feature.
Unfortunately, it resulted in a complete cluster-f¤ck.
Yes, I did NOT do a full wipe during the update.
Now, I have no cell coverage at all. Airplane Mode is ON, "Closing".... When I go to Settings > About, the software information shows no Baseband version, so no baseband driver installled...(?)
Trying rebooting, entering TWRP recovery, clearing cache, dalvik cache, fixing permissions and rebooting again, but this fixed nothing...
Trying rebooting, entering TWRP recovery, resetting phone, but this fixed nothing...
Another example of ALWAYS having to doing a full wipe when updating customs ROMs, I gues...
Sigh...
I think there is something wrong with the ROM. I made a full whipe (came from ardh 12) and i have the same. No guide selecting network and flightmode is on and no service. I have tried reflashing and making a whipe after flash but still problem.
First i though it was a kernel issue but no boot.img in the rom-file.
*snip snip*
So, yes. I'm a total dimwit =).
Finally solved atleast, thanks alot for the help!

I think you have to flash a ICS rom. What is your hboot number ? Is you're hboot 1.12 then you can not flash a JB rom !
You can find hboot version in the bootloader menu
Try a ics rom and i think you will be fine !
Try this
Put Rom.zip on sd card
Extract boot.img and flash it in fastboot
Enter recovery and wipe/factory reset
Wipe all caches / dalvik cache
And charge the phone full first before going at it again ... might be good to do !
Flash Rom and reboot .... I will bet it boots up fine

Thanks for the help, but the rom is installed... and yes, it is JellyBean =).

[December 6,2013][ROM] [PrimoC] Stock-Rooted Virgin Mobile HBOOT 1.57.0000

View attachment primoc_boot_unsecure.imgPlease excuse my absence. I will not be watching this thread for the time being. Hopefully if you have any questions, they can be answered by using the search option or someone else with this device that happens to check this thread will be kind enough to help.
!#I'M BACK#!​
soon enough we won't need this thread, because we will all be able to RUU lol-Dec 6, 2013
beaups said:
posted on rumrunner.us. should work for both primou and primoc. Note, it is highly recommended (mandatory?) to be on a normal sense-based ICS rom and using an unsecure (preferably stock based) kernel. If you get poor results with other configurations, don't bother asking for help please!
Click to expand...
Click to collapse
S-OFF is here rumrunner.us
Huge thanks to beaups
This rom is probably most compatible with rumrunner
The boot.img inside is unsecure so flash away and GO GET S-OFFED!!!
Here's the unsecure boot.img that I used to achieve s-off.
View attachment primoc_boot_unsecure.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Added init.d support
Added Root Permissions with Chainfire's SuperSu
This ROM was cooked with dsixda's Android Kitchen
Thank you and credit goes out to the both of them.
CLICK HERE TO DOWNLOAD

I have posted this ROM for safetynet/fall-back purposes.
I've noticed fellas posting please help, I forgot/didn't make a backup.
This is for you. Worried and maybe even a little scared that your phone is now a beautiful paper weight.
This ROM is completely stock with added init.d support and root.
It is still odexed, and with stock kernel.( I'm still learning/attempting to build one with extra governors and over clocking abilities ).
Instructions below....

1. Unlock your Bootloader by following the instructions at htcdev
1a. If you've succesfully unlocked your Bootloader, that means you have your fastboot files on your PC and know in general how to use them.
2. Download an openrecovery of your choice. I personally use TeamWinRecoveryProject 2.2.0 without any issues at all. (See the attached File)
3. Place the recovery.img that you have chosen into your fastboot folder.
3a. Change the name of the .img to recovery.img (just easier that way when sending the flash command)
4. Now open a terminal while in the fastboot folder.
4a. On Windows- hold shift+right click the mouse then click open command terminal here.
4b. On Ubuntu- CTRL+ALT+T to open a terninal then cd fastboot.
5.fastboot flash recovery recovery.img​
5a. ^^^^^ Type this into the terminal. ^^^^^
5b. You now have a custom/openrecovery.
6. After the recovery.img is flashed, reboot your Bootloader.
6a. fastboot reboot-bootloader​
7. After booted back into bootloader, use your volume-down button to highlight Recovery.
Now press your Power button to select it.
7a. Now your are in Recovery!
8. Click Wipe, then Cashe, then Dalvick, then Factory Rest, then System.
8a. This will wipe all of your phone nice and clean for a fresh install.
9. Click Home, then Install, and find the ROM.zip, click it, then install. Let it finish installing the click Wipe Cashe/Dalvick.
10. Navigate back to the Home screen and click Reboot, then Bootloader
10a. I hope you have a copy of the ROM.zip on your PC.
11. Open the ROM.zip and copy/extract the boot.img from inside it and place it in your fastboot folder.
12. Open a terminal once again.
13.fastboot flash boot boot.img​
13a. Let it finish.
14. fastboot reboot​
15. Enjoy.
These instructions are for use with TWRP (TeamWinRecoveryProject) They may be different using CWMrecovery (ClockWorkMod).

I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here

lostboybinns said:
I made a backup of my stock rom via twrp. Updated the kernel and installed shpongle. When I tried to go back to my stock via twrp it would not boot due to the kernel. I wonder if that will be the case here
Click to expand...
Click to collapse
u flashed shpongle? that means u are GSM not CDMA so this ROM just simply won't work
as for returning to stock, u can always flash a sense kernel duh

This is for primoc CDMA Virgin Mobile

I just downloaded and flashed to test, everything is working....Just like stock

This should allow me to update my PRL, right?

YUP!

Turns out it was a network fluke?

wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...

russellvone said:
Turns out it was a network fluke?
Click to expand...
Click to collapse
What was a network fluke?

I'll cross reference the updater-script to another one I've used on a different Rom I cooked and have been running for over two weeks..... See if there are any differences between the two.

lilrob1213 said:
What was a network fluke?
Click to expand...
Click to collapse
I was replying to zombiegirl's question about updating her/his PRL

Matt_the_Geek said:
wont flash for me, i get:
"error executing updater binary in zip
and
error flashing zip
going to try a full format of the sd card...
Click to expand...
Click to collapse
Ok I found a difference in the updater-script, the update binaries are identical so that shouldn't be the issue. Problem I have is that I don't have a working computer to fix the updater-script. It won't be until June 26th that I can apply it. Sorry for the inconvenience.
P.S. are you flashing with TWRP?

Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.

Matt_the_Geek said:
Yes sir, TWRP. and no worries, it apparently just isn't your ROM. Angry HTC and jmz's stock ROM both give the same error. even after a full format of the SD. Rhythmic Rom 1.4 works though, and is what I was running. Was trying to return the device to somewhat stock tho as im either going to sell it or let my gf use it, so I was hoping for stable and to have the charge LED and icons working, hopefully.
Click to expand...
Click to collapse
If you downgrade TWRP to 2.3 you should be fine.
Sent from my One V using xda premium

ah, I'm on 2.5, so I'll look into that...

did the downgrade to TWRP 2.3.0.0, still the only thing i can install is Rhythimc Rom, everything else fails to install... unless i just got some really crappy downloads, so i'm off to try to dl the roms again...

Actually, instead I swapped out recoveries for CWM. aaaand it worked.

[Q] Trying to get Cyanogenmod on my Z1 Compact

Hi
I tried to get CM on my new Sony Xperia Z1 Compact, but I wasn't successful. I followed the standard guideline on the CM-Wiki and everything seemed to go well so far, but it doesn't start: I was waiting for about 30 minutes after the final reboot but it still went only in circles at the splash screen
I have tried the experimental from 2014/03/14 and the nightly from 2014/03/26 and 2014/03/27, but unfortunately no success with any of these versions.
I know, it's still a very early version, but I thought, at least I should be able to install it. Has someone already get it working on this device?
Thanks for your help!
Best regards
Matthias

Muetze1707 said:
Hi
I tried to get CM on my new Sony Xperia Z1 Compact, but I wasn't successful. I followed the standard guideline on the CM-Wiki and everything seemed to go well so far, but it doesn't start: I was waiting for about 30 minutes after the final reboot but it still went only in circles at the splash screen
I have tried the experimental from 2014/03/14 and the nightly from 2014/03/26 and 2014/03/27, but unfortunately no success with any of these versions.
I know, it's still a very early version, but I thought, at least I should be able to install it. Has someone already get it working on this device?
Thanks for your help!
Best regards
Matthias
Click to expand...
Click to collapse
Yes I have the nightly installed, plus updating everynight, everything working fine. Is your bootloader unlocked? what recovery you have installed?

{Z1 Compact}[DEVELOPMENT] - CM11 - Android 4.4 - FreeXperia Project

RevokOne said:
Yes I have the nightly installed, plus updating everynight, everything working fine. Is your bootloader unlocked? what recovery you have installed?
Click to expand...
Click to collapse
I followed the standard installation procedure on the CM-Wiki (which I can not link, sorry). And according to the results of fastboot, etc., yes, it should be unlocked. Can I check it somehow?
Recovery is the ClockworkMod Recovery.
Which was the first nighlty built you used for the first installation?

Muetze1707 said:
Can I check it somehow?
Click to expand...
Click to collapse
Did you actually unlock it, if not then it wont be.

XperienceD said:
Did you actually unlock it, if not then it wont be.
Click to expand...
Click to collapse
I just tried to follow the steps of the tutorial again and when I executed the "fastboot -i 0x0fce oem unlock 0x<MyKey>" it said:
Code:
FAILED (remote: Device is already rooted)
So, I would say looks good.
Then I flashed the boot.img again und installed the newest nightly build, but still no success, still only the splash screen.

Muetze1707 said:
Then I flashed the boot.img again und installed the newest nightly build, but still no success, still only the splash screen.
Click to expand...
Click to collapse
Does it say "OKAY" when you flash the boot.img?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That will show if it is or not, if it is then flash the one from this forum and make sure you wipe everything before installing the zip.

XperienceD said:
Does it say "OKAY" when you flash the boot.img?
Click to expand...
Click to collapse
Yes:
Code:
./fastboot_ln -i 0xfce flash boot Z1c_DooMLoRD_AdvStkKernel_FW-681_v03.img
sending 'boot' (12374 KB)...
OKAY [ 0.690s]
writing 'boot'...
OKAY [ 0.823s]
finished. total time: 1.513s
XperienceD said:
That will show if it is or not, if it is then flash the one from this forum and make sure you wipe everything before installing the zip.
Click to expand...
Click to collapse
Which one from this forum do you mean? I tried the one from the thread "[D550X] CWM-Based Recovery 6.0.4.6 + ROOT for Xperia Z1 Compact {KitKat!} [20140320]", but with the same result.
For wiping I do a "wipe data/factory reset", a "wipe cache partition" and a "wipe dalvik cache".

Muetze1707 said:
Which one from this forum do you mean?
Click to expand...
Click to collapse
The ROM and kernel from the first link I posted, the stock kernel wont work with CM. EDIT: Noticed the link above wasn't posted right. - {Z1 Compact}[DEVELOPMENT] - CM11 - Android 4.4 - FreeXperia Project

XperienceD said:
The ROM and kernel from the first link I posted, the stock kernel wont work with CM.
Click to expand...
Click to collapse
Many thanks for your help! Now it's working.

Muetze1707 said:
Many thanks for your help! Now it's working.
Click to expand...
Click to collapse
Hi, I'm experiencing the same problem as you Muetze1007. I followed the guide from cyanogenmod wiki and tried to install a nightly version of official Amami but I get stuck at the Cyanongenmod logo...
I had a look at the topic you linked Xperienced but then I got stuck at the page (I can't post the link, the page with "unrestrict" in its URL)... What am I supposed to download ?

are there some GPU / CPU OC funktion on the CM Kernel?

Leaxius said:
What am I supposed to download ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2685286

XperienceD said:
http://forum.xda-developers.com/showthread.php?t=2685286
Click to expand...
Click to collapse
Thanks XperienceD, I already went there and read everything carefully, went to the unrestrict.li website and then couldn't find an Amami rom...
However when going on the FXPblog I managed to find one (FXP316-cm-11-20140421-UNOFFICIAL-amami.zip) and tried to install it following instructions (fastboot flash boot boot.img, then recovery mode, install from sdcard...).
I am still blocked at the Cyanogenmod loading screen on the boot sequence...
Xperienced I noticed you were talking about a specific kernel, noob question but is it something different from the rom ? (ie the zip file)

Leaxius said:
Xperienced I noticed you were talking about a specific kernel, noob question but is it something different from the rom ? (ie the zip file)
Click to expand...
Click to collapse
Extract the boot.img file to where your fastboot.exe is, run the command you have which will install the kernel then reboot, enter CWM then flash the zip after wiping data and caches and that should be it. Yes, the kernel and ROM are two separate things.

XperienceD said:
Extract the boot.img file to where your fastboot.exe is, run the command you have which will install the kernel then reboot, enter CWM then flash the zip after wiping data and caches and that should be it. Yes, the kernel and ROM are two separate things.
Click to expand...
Click to collapse
Thanks for your help !
I wasn't sure what and where the kernel was (ie, the boot.img file). I've already done that before, it seems I had permission problem to wipe data, which I managed to solve by formatting some folders. It's working now

Leaxius said:
It's working now
Click to expand...
Click to collapse
That's the main thing. :good:

Same problem, exact solution please?
Hi,
Sorry for revisiting this thread but it appears I have the same exact problem as the OP. I followed the instructions on the CM wiki (got the prepackaged rom from FXP, extracted boot.img, unlocked bootloader, flashed boot.img, booted into recovery and selected the zip file to flash to the device. An odd phenomenon occurred when I tried mounting data, this gave me an error. Also, I couldn't seem to choose the zip from SD card but from storage/SD or so...can't remember the exact wording. But after all that I rebooted and it just slowed the alien with the spinning arrow and got stuck there. So for the ones who solved this particular problem, what did you have to do to make it behave? Some ADB commands perhaps? I'd really like this to work because the CM11 ROM is heaps more accessible (meaning blind-friendly) than the stuff Sony ships with the phone by default, something which is useful for me, being fully blind and all.
Thanks in advance for any help you guys can provide,
Zersiax

zersiax said:
Hi,
Sorry for revisiting this thread but it appears I have the same exact problem as the OP. I followed the instructions on the CM wiki (got the prepackaged rom from FXP, extracted boot.img, unlocked bootloader, flashed boot.img, booted into recovery and selected the zip file to flash to the device. An odd phenomenon occurred when I tried mounting data, this gave me an error. Also, I couldn't seem to choose the zip from SD card but from storage/SD or so...can't remember the exact wording. But after all that I rebooted and it just slowed the alien with the spinning arrow and got stuck there. So for the ones who solved this particular problem, what did you have to do to make it behave? Some ADB commands perhaps? I'd really like this to work because the CM11 ROM is heaps more accessible (meaning blind-friendly) than the stuff Sony ships with the phone by default, something which is useful for me, being fully blind and all.
Thanks in advance for any help you guys can provide,
Zersiax
Click to expand...
Click to collapse
I flashed CWM today, got the Rom from here: http://fxpblog.co/cyanogenmod/cyanogenmod-11/
I used fxp323
I had CWM and TWRP installed, but I only used CWM. I like TWRP more but it seems CM is more CWM fixated.
Used linux. Its easy, only installed android-tools (I'm using ubuntu-gnome but with fedora, opensuse or manjaro or debian it should be the same).
Download fxp 323.
Copy the zip to the sdcard of your phone.
Unzip the fxp323 on yor pc. Copy boot.img to inside downloads.
Open the terminal on pc.
code: cd Downloads
adb kill-server
sudo adb start-server
put your phone in fastboot (blue LED) there is nice tool from doomlord for this : https://play.google.com/store/apps/details?id=com.doomlord.xperiareboot&hl=de
connect with usb-cable to pc when the led is blue
fastboot -i 0x0fce getvar version (for verifying your fastboot connection)
sudo fastboot devices (for verifying your fastboot connection)
sudo fastboot -i 0x0fce flash boot boot.img
sudo fastboot -i 0x0fce reboot
now go CWM and flash the fxp323.zip
reboot
CM11 is fine, The only bad thing is That you loose the fm-radio which comes with the sony software. If anybody has an idea how to get it back please tell.

zersiax said:
Hi,
Sorry for revisiting this thread but it appears I have the same exact problem as the OP. I followed the instructions on the CM wiki (got the prepackaged rom from FXP, extracted boot.img, unlocked bootloader, flashed boot.img, booted into recovery and selected the zip file to flash to the device. An odd phenomenon occurred when I tried mounting data, this gave me an error. Also, I couldn't seem to choose the zip from SD card but from storage/SD or so...can't remember the exact wording. But after all that I rebooted and it just slowed the alien with the spinning arrow and got stuck there. So for the ones who solved this particular problem, what did you have to do to make it behave? Some ADB commands perhaps? I'd really like this to work because the CM11 ROM is heaps more accessible (meaning blind-friendly) than the stuff Sony ships with the phone by default, something which is useful for me, being fully blind and all.
Thanks in advance for any help you guys can provide,
Zersiax
Click to expand...
Click to collapse
I think what a lot of people are missing is that after unlocking the bootloader, the device deletes the /data/media (internal storage) partition but doesn't format it. CM11 doesn't format this partition as part of its installation or boot, Sony's ROM does, if this partition is unformatted when the Sony ROM boots it'll format it. So there are two solutions.
1. After unlocking bootloader, boot Sony ROM once, then proceed with the CM11 instructions.
2. After unlocking bootloader and flashing CM11 kernel (boot.img), do a /data and /data/media format, then proceed with the CM11 instructions.

Softbricked OPTUS001 HTCm9

Hey all,
Happy Australia Day over here! Anwyay, I seem to have softbricked my phone when trying to flash the ViperOne ROM. The AROMA installers didn't seem to install the ROM properly? Or that system folder kept unmounting. But now I wiped that portion and am only stuck with the recovery, download and bootloader. I'd put on a TWRP recovery or fastboot/adb a zip into it but it seems that the HTC won't show up on my computer anymore and won't allow me to fastboot flash because it cannot allocate space. I know it does have space because it says so in the TWRP recovery but otherwise it won't mount or allow to write to it. Any help?

Seems like you need s-off.
Sent from my HTC One M9 using Tapatalk

shivadow said:
Seems like you need s-off.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How do I get s-off with no ROM to boot into?

Flash a stock rom and start over. If you are s-on the rom is there, it just cannot boot.
Sent from my HTC One M9 using Tapatalk

shivadow said:
Flash a stock rom and start over. If you are s-on the rom is there, it just cannot boot.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Okay... but how do I reflash? I can't mount the internal storage to a computer to put a zip file in there.

Use an adapter to copy the zip on the Ext Sdcard
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when you are in TWRP , you should be able to copy the zip ...

bzhmobile said:
Use an adapter to copy the zip on the Ext Sdcard
But when you are in TWRP , you should be able to copy the zip ...
Click to expand...
Click to collapse
okay, just tried this. didn't correctly flash the rom and now when i plug my sdcard in the computer, it doesn't appear either. what's going on??

OKAY, I ended up using the fastboot erase function to erase on my PC. Then I used an sdcard to flash a rom that didn't have the AROMA installer (CM12) and it worked. Any reason why AROMA installer is giving me issues?

Aaand installing GApps gives me a error: I don't have a build.prop file. And I can't seem to edit 'Internal Storage' in TWRP. What's going on?!

Strange ,
No problem for me in twrp for the internal storage.
Which version of twrp in your device?

bzhmobile said:
Strange ,
No problem for me in twrp for the internal storage.
Which version of twrp in your device?
Click to expand...
Click to collapse
Hey,
I am running 2.8.6.0. I have flashed the latest TWRP recovery as well but it has the same issues! Just wondering how I can force GApps to install on my phone so I can actually use it now, haha

May it's a problem of Gapps version.
If you can flash the rom there's no reason not to be able to flash the gapps.
Which version is recommended in the OP of the rom?

bzhmobile said:
May it's a problem of Gapps version.
If you can flash the rom there's no reason not to be able to flash the gapps.
Which version is recommended in the OP of the rom?
Click to expand...
Click to collapse
I've just flashed the most recent nightly of CM12 for the HTC M9.

Give me the link of the rom thread , just to have a look...

aysixtyfive said:
I've just flashed the most recent nightly of CM12 for the HTC M9.
Click to expand...
Click to collapse
You mean CM13 ??

gregsarg said:
You mean CM13 ??
Click to expand...
Click to collapse
Yeah, CM13. Sorry!

OKAY, another update.
I'm able to use CyanogenMod to use the phone for it's basic features, like calling and the camera. I can install .apk files from the internet! But I cannot install gapps because there it says there is no ROM installed when I attempt.
Furthermore, my phone comes up as a media device on my computers. I have several and have installed general OEM and HTC drivers and it comes up in device manager as 'hima' but.. will not pick up as a mass storage device no matter what. I'd love to get it to mass storage so I can format it on the COMPUTER and attempt to flash CM13 again.
Any ideas on why the driver is not picking up or will not pick up? Or how to veto some option to force installing of gapps?
Thank yoU!

aysixtyfive said:
OKAY, another update.
I'm able to use CyanogenMod to use the phone for it's basic features, like calling and the camera. I can install .apk files from the internet! But I cannot install gapps because there it says there is no ROM installed when I attempt.
Furthermore, my phone comes up as a media device on my computers. I have several and have installed general OEM and HTC drivers and it comes up in device manager as 'hima' but.. will not pick up as a mass storage device no matter what. I'd love to get it to mass storage so I can format it on the COMPUTER and attempt to flash CM13 again.
Any ideas on why the driver is not picking up or will not pick up? Or how to veto some option to force installing of gapps?
Thank yoU!
Click to expand...
Click to collapse
BUMP! Still needing help with this.

Cannot install OTA update and adb sideload failed

I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk

marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
Click to expand...
Click to collapse
How does your phone show up under device manager?

marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
View attachment 4281534
Click to expand...
Click to collapse
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.

Puddi_Puddin said:
How does your phone show up under device manager?
Click to expand...
Click to collapse
Device Manager lists the device as ONEPLUS A3003

DJBhardwaj said:
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Click to expand...
Click to collapse
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work

demonoid phenomenom said:
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
I am on stock OOS with Marshmallow 6.0.1 and I am trying to update it to OOS 4.1.7 released on august 21st and I got the device just two days ago. I tried updating via OTA and it presented me with signature verification error and while trying to sideload the OTA, I ended up with the error mentioned above.

marmeak7 said:
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
Click to expand...
Click to collapse
Have you tried flashing the full ROM zip file via stock recovery?

DJBhardwaj said:
Have you tried flashing the full ROM zip file via stock recovery?
Click to expand...
Click to collapse
The stock recovery does not have the option to flash zip files or am I not seeing the option?

marmeak7 said:
The stock recovery does not have the option to flash zip files or am I not seeing the option?
Click to expand...
Click to collapse
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.

DJBhardwaj said:
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
Click to expand...
Click to collapse
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus

marmeak7 said:
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
Click to expand...
Click to collapse
Oh.. How about installing TWRP and then flashing the ROM through that?

DJBhardwaj said:
Oh.. How about installing TWRP and then flashing the ROM through that?
Click to expand...
Click to collapse
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help ?

marmeak7 said:
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help
Click to expand...
Click to collapse
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.

DJBhardwaj said:
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
Click to expand...
Click to collapse
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk

demonoid phenomenom said:
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
Exactly, all courtesy of OnePlus. Not all OEM offer this liberty.

Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!

info2shail2010 said:
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
Click to expand...
Click to collapse
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:

marmeak7 said:
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
Click to expand...
Click to collapse
Just in case you run into a brick...?..I did once so I found this thread handy
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

So i encountered this problem a while back, after doing some digging and analyzing adb, i came to the conclusion that adb could only address memory in 32bit on pc, so it couldn't handle the size when sideloading the extracted OS with STOCK recovery. If you want to still do it with stock you will have to do some digging around in forums, i found a software that modded the program to be able to use 64bit memory access. cant give you the link though since it was a while back.