Database Info

[4.4.4][ktu84p]STOCK Rooted with busybox for tilapia[6/19/14]

It is cooked from the Google stock image for tilpia and is NOT deodexed
This is the first time i am posting a ROM on XDA.
Been cooking ROM's for a while for my old Samsung devices.
The whole reason for this thread is to have a flashable zip for any Nexus 7(2012) 3g user who wishes to stay stock.
I have tested it on my Nexus 7, if anyone has any issues do let me and please bear with me as im not a developer and just sharing what i personally use.
Will try and help with what ever i can.​
************** For some Reason the boot logo does not show up, dont worry, wait for sometime, the ROM will boot up***********
Note:
1. Works with multirom.
2. Odexed for my personal use, if anyone wishes to de-odex it, do let me know.
3. This includes the stock kernel. I also tested the latest stable mkernel which is for 4.4.2 and works fine.(works with the new kitkat 4.4.4 too)
Screenshot attached
Downloads:
4.4.4:
tilapia.v2
Mirror
Radio for 4.4.4
md5 for Radio: 64920d406852d92b478c3ab17383ecce
4.4.3:
tilapia.v1
md5 : 5c4d3b47274000cf6d5326d14ab7cc81
Click to expand...
Click to collapse
Installation:
1. Reboot to recovery
2. Do a factory reset.
3. Go to advanced wipe settings and select system, dalvik and cache and format them.
4. Flash Rom
First boot takes time, wait patiently. There wont be any boot animation, so wait on that black screen for sometime
Profit :good:
Click to expand...
Click to collapse
credits: @JustArchi

Let me know guys if there is any issue. Im little busy this weekend, will take little time to add things like Advanced reboot menu, battery % and debloat.

phanitej said:
Let me know guys if there is any issue. Im little busy this weekend, will take little time to add things like Advanced reboot menu, battery % and debloat.
Click to expand...
Click to collapse
Hi, Can I flash this over 4.4 [KRT16O]? Please advise. Thanks.

gwong76 said:
Hi, Can I flash this over 4.4 [KRT16O]? Please advise. Thanks.
Click to expand...
Click to collapse
Update your bootloader and radio first. And clean flash is recommended though there are not much of changes from 4.4.2 but as you mentioned you are using 4.4 clean wipe and installing is preferred.

thank you very much! stock rocks! :good::good:
PS: root & bbox?

Thanks alot
Hi!
First of all - thanks for your clean/xposed ROM.
I only have one question. Would it still be possible to send SMS from my Tilapia-tablet (Nexus 7-2012/3G) after flashing your ROM?
BTW : @RomerGG - The threads' header should already have answered your question...
Regards,
Roy

roygaard said:
Hi!
First of all - thanks for your clean/xposed ROM.
I only have one question. Would it still be possible to send SMS from my Tilapia-tablet (Nexus 7-2012/3G) after flashing your ROM?
BTW : @RomerGG - The threads' header should already have answered your question...
Regards,
Roy
Click to expand...
Click to collapse
Haven't tried that. Unfortunately i have a pure data plan, so my provider restricts sms by default. And i cant take out the sim and replace as i was once trying to break open my sim slot and take out the sim, during that crazy struggle i guess i broke that sim holder. so once the sim comes out, i have to struggle a lot to get the network back on by replacing it
Edit: dont think hangouts will give the sms sending option by any chance. So try with a third party app and let us know

Thanks for the stock rooted rom. FYI, I had flashed CF SuperSU v1.99r4 and also MKernel a67, looks okay so far. I'm updating the Google apps from Play store now. Once done, I'll be installing TB to restore my apps.
One word of caution to those flashing this rom. Note that there seems to be no bootanimation, so don't be mistaken that the rom is not working. Give it time to boot up. :good:
Edit:
One thing I noticed strange is in TB, System ROM is showing 670MB (8.45 MB free). Before this, I was on 4.4.2 stock rooted, before I manually flashed boot.img and system.img. It was showing same results, but 9.XX MB free. Is this correct? I vaguely remembered that it should be almost 900 plus MB. Can anyone confirm?

phanitej said:
Update your bootloader and radio first. And clean flash is recommended though there are not much of changes from 4.4.2 but as you mentioned you are using 4.4 clean wipe and installing is preferred.
Click to expand...
Click to collapse
Sorry for this stupid question. How can I updated these .img files ?

Thank you for this work!! I had the slimkat, I did a wipe recovery and then I installed. Where is the menu button?
Art is not activated?

apinun_po said:
Sorry for this stupid question. How can I updated these .img files ?
Click to expand...
Click to collapse
To flash them you need to enable USB debugging and then reboot to bootloader. Here use the following fastboot commands.
For Updating bootloader:
fastboot flash bootloader name_of_the_bootloader_file.img
For radio:
fastboot flash radio name_of_the_radio_file.img
If you want a detailed instruction, go here and follow Method 2.

sbarrett said:
Thank you for this work!! I had the slimkat, I did a wipe recovery and then I installed. Where is the menu button?
Art is not activated?
Click to expand...
Click to collapse
It is the same file as the one google pushes for Nexus 7 device. So what ever is present in the original stock image, will be there.
Menu button is only active in apps that give it by default, there is an xposed module which can activate menu button in every app.
For ART, not sure why google misses the option to switch to ART every time on Nexus 7 devices. Will check and see how to add that option.

phanitej said:
To flash them you need to enable USB debugging
Click to expand...
Click to collapse
Thank you very much.

Kitkat 4.4.4 is out and the stock rooted version is tested and :good:uploaded.

One quick question my all friend here. 4.4.4 still dalvik or run as ART
Sent from my GT-I9205 using Tapatalk

yusopa said:
One quick question my all friend here. 4.4.4 still dalvik or run as ART
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
It is dalvik. Google does not seem to want including ART for the nexus 7. Read somewhere on google forums that it might be a hardware issue cos of which they are not including it.

flashing aborted
Version tilapia2 flashing aborted, version tilapia 1 ok. Do you know where is the problem? Using the latest version of the recovery v6.0.4.3.

Good work! I maintain BSZKitKat for grouper (ODEX and DEODEX). Awesome job getting right in front of the 4.4.4 update!
---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------
phanitej said:
It is dalvik. Google does not seem to want including ART for the nexus 7. Read somewhere on google forums that it might be a hardware issue cos of which they are not including it.
Click to expand...
Click to collapse
Correct - we lack sufficient space on the /system partition for the binaries required for switching to ART

Cant' flash this rom, i get an error and the message FAILED.
I'm using TWRP recovery 2.7.

Can we have a flashable zip please?
It is much easier to deal with!
Thanks

[Q&A] ★☆[ROM][4.4.3] NuSenseSIX | Sense 6.0 | 2.21.605.2 | m8vzw

Q&A for ★☆[ROM][4.4.3] NuSenseSIX | Sense 6.0 | 2.21.605.2 | m8vzw
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

issues
HTC Dot view crashes when adding a new theme, OK GOOGLE detection from any screen not working, infact its not even letting me calliberate by saying OK GOOGLE 3 times.

udmerchant said:
HTC Dot view crashes when adding a new theme, OK GOOGLE detection from any screen not working, infact its not even letting me calliberate by saying OK GOOGLE 3 times.
Click to expand...
Click to collapse
I have no means of testing Dot View.
OK Google works fine for me and so does the calibration.
Did you do a full wipe prior to flashing the rom?
Did you restore apps or data?
Logcat for Dot View?

udmerchant said:
HTC Dot view crashes when adding a new theme, OK GOOGLE detection from any screen not working, infact its not even letting me calliberate by saying OK GOOGLE 3 times.
Click to expand...
Click to collapse
Just tried it...worked for me as well as ok Google and calibration.
santod040 said:
I have no means of testing Dot View.
OK Google works fine for me and so does the calibration.
Did you do a full wipe prior to flashing the rom?
Did you restore apps or data?
Logcat for Dot View?
Click to expand...
Click to collapse
See above ? Also, I have a dot view case. Pretty fancy gimmick, but hopefully in future iterations will be cool.

Haha, totally had the same HTC flash screen for half a hour. Totally forgot to flash the boot.img for 4.4.4 when I did the firmware... That took care of everything

Screen wont turn on after flashing 4.0.1
It is my first time trying NuSenseSIX. I updated the firmware and flashed the ROM to my Verizon One M8 but now the screen won't turn on, but as I press the volume buttons, I hear the sounds and I can somehow turn the flashlight on.
The problem is that I can't get it to turn off so I can enter recovery!
I think the problem might be the "Fast Boot" option which I can uncheck since the screen won't show anything. Any input will be deeply appreciated.

Raneto said:
It is my first time trying NuSenseSIX. I updated the firmware and flashed the ROM to my Verizon One M8 but now the screen won't turn on, but as I press the volume buttons, I hear the sounds and I can somehow turn the flashlight on.
The problem is that I can't get it to turn off so I can enter recovery!
Click to expand...
Click to collapse
Hold Power and Vol Up till it reboots, then power vol down

jsaxon2 said:
Hold Power and Vol Up till it reboots, then power vol down
Click to expand...
Click to collapse
I am trying exactly that, but when I hold Power + vol down after it reboot, it simply takes a screenshot(I hear the sound) and doesn't do anything else evend if I keep pressing the buttons for over a minute.
Is there a specific time I should start pressing Power+Vol Down when it reboots?
Finally did it...I needed to press Pwr+VolDwn exactly when it was about to restart.

Raneto said:
I am trying exactly that, but when I hold Power + vol down after it reboot, it simply takes a screenshot(I hear the sound) and doesn't do anything else evend if I keep pressing the buttons for over a minute.
Is there a specific time I should start pressing Power+Vol Down when it reboots?
Finally did it...I needed to press Pwr+VolDwn exactly when it was about to restart.
Click to expand...
Click to collapse
Did you get the Rom to install? Everything good to go?

Quick question: ready to install 4.4.4 but need to know the following? Install by pc or by twrp? Do I need to update firmware or radio first? Then a clean install means wipe in what order by twrp?

crazysane said:
Quick question: ready to install 4.4.4 but need to know the following? Install by pc or by twrp? Do I need to update firmware or radio first? Then a clean install means wipe in what order by twrp?
Click to expand...
Click to collapse
U would use TWRP to flash Rom. And update to new firmware first. If u haven't do a backup of ur current setup/Rom ur on. Then wipe. I go into advance as well and select data,cache,dalvik cache,and system.
Sent from my Insanely powered M8 using Tapatalk

crazysane said:
Quick question: ready to install 4.4.4 but need to know the following? Install by pc or by twrp? Do I need to update firmware or radio first? Then a clean install means wipe in what order by twrp?
Click to expand...
Click to collapse
If you install v4.2 you should be able to install normally through twrp. Yes, update firmware, factory reset in twrp. Dalvik cache, cache, system, data, etc. Don't wipe internal sd or external sd.
Edit: didn't see your post Holla420

HOOKEDONDROID said:
If you install v4.2 you should be able to install normally through twrp. Yes, update firmware, factory reset in twrp. Dalvik cache, cache, system, data, etc. Don't wipe internal sd or external sd.
Edit: didn't see your post Holla420
Click to expand...
Click to collapse
I cannot seem to get the firmware to flash using TWRP. Is it supposed to be this hard? I have installed the new ROM just not the firmware yet. I have downloaded it and checked the md5 which shows it passed. Please tell me what I may be doing wrong? the file name is 3.28.605.4-firmware.zip.
Just want to have this correct before proceeding further.

crazysane said:
I cannot seem to get the firmware to flash using TWRP. Is it supposed to be this hard? I have installed the new ROM just not the firmware yet. I have downloaded it and checked the md5 which shows it passed. Please tell me what I may be doing wrong? the file name is 3.28.605.4-firmware.zip.
Just want to have this correct before proceeding further.
Click to expand...
Click to collapse
You don't update firmware through TWRP. Save the file to your external sd card and rename.
SD CARD METHOD DIRECTIONS
Download 4.4.3 firmware
Rename file to 0P6BIMG(zero at the start)
Place file on root of SD card*
Reboot to bootloader an click hboot it will auto detect file
Follow the prompts an you will be updated*
Then reboot to boot loader either by holding power+volume down or through the Rom. Select hboot and the update should start. Follow the instructions and you should be good to go

NuSense 4.4.4
Flawless!
Also applied the HK mod from another thread and everything works perfectly.
Thanks, Santod!

Hello everyone. just stared put your Rom. everything seems to be fine, but. Blink can`t get to show my location to display weather. In the setting of location included. Can not find my city of Lviv. how it can be cured?

Go into the weather app and add your city. You should be able to find it or select " current location" it found Lviv when I just searched for it.

I'm sorry, but I could not make friends with your Rom not one keyboard
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
HOOKEDONDROID said:
Go into the weather app and add your city. You should be able to find it or select " current location" it found Lviv when I just searched for it.
Click to expand...
Click to collapse
with etoy problem I figured Wipe helped. but with the keyboard hand, make friends and it could not

publ said:
I'm sorry, but I could not make friends with your Rom not one keyboard
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
with etoy problem I figured Wipe helped. but with the keyboard hand, make friends and it could not
Click to expand...
Click to collapse
Keyboards zip is in post 2 if that helps...for more languages.

wifi still doesnt work
I am on 4.4.4 reflashed the firmware, but certain roms dont work. I am on the latest liquid smooth and wifi does work on this rom, any other ideas?
Thanks

com.android.systemui has stopped

I get the following error:
Unfortunately the process com.android.systemui has stopped
The error just keeps repeating if I press OK.
What I did to get this error was:
Backup current ROM using TWRP
Flash a Lollipop ROM (that didn't work)
Restore my backup
and now I'm screwed
I've read somewhere about Italians having this issue and that it had to do with low battery level. I have now recharged my phone to 95% but still no dice And my phone is running US English (though I'm in Denmark).
I'm running CM11 M11.
Can anyone help?

Clean flash.
Transmitted via Bacon

timmaaa said:
Clean flash
Click to expand...
Click to collapse
And how would I do that if I cannot transfer zip files to my phone?
And would I be able to restore my backup afterwards?

You didn't say anything about not being able to transfer zips to your phone, but I'm assuming you mean while booted into Android because of the persistent error. TWRP 2.8.x has MTP enabled so if you connect your phone to your PC while booted into that recovery you can copy a zip across to flash. And no, you can't restore your backup afterwards, the whole point of a clean flash is that it's a clean flash, completely fresh. Plus, restoring a backup after flashing a ROM would overwrite the ROM you just flashed, making it a pointless exercise. Plus, the backup that you have is obviously corrupt and that's what's causing your problem.
In short: download a ROM zip (and gapps), flash the latest TWRP to your phone (if you don't already have it), copy the zips to your phone, perform a full wipe (system, data, cache, dalvik cache), flash the ROM + gapps, reboot and start fresh.
Transmitted via Bacon

The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.

I'm kind of thinking that it's my TWRP that has some issue. I've tried restoring 3 or 4 different backups and they all come up with the same error.
I'll update my TWRP when I get home and hopefully get a bit further...

Gamm86 said:
The only backup you should be restoring using TiBu after flashing a ROM are user apps, and certainly not system apps. Restoring system apps will cause problems in 99.9% of all cases.
Click to expand...
Click to collapse
He's talking about a nandroid backup, not a TiBu backup.
Transmitted via Bacon

timmaaa said:
He's talking about a nandroid backup, not a TiBu backup
Click to expand...
Click to collapse
I know, just talking about restoring backups in general after flashing a ROM.
Hence why I said "The only backup you should be restoring..."
EDIT* misread the OP. My posts were indeed a bit out of context...

Did a clean install - no dice
Then did an install without gapps and then I get to the initial setup where I have to choose language. And then it reboots - over and over. It completely bypasses any indication that there is a SIM card in the phone.
When trying to restore my previous backups I also go straight to my home screen bypassing SIM unlock and phone unlock.
Any other suggestions?

Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471

Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Either that or this automated tool:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon

Gamm86 said:
Have you tried step 8 from the following thread: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life

kroogar said:
Nope. But I'm going to now Stay tuned...
Well... it's a different bootanim than CM11 - first indication that something has happened
But then Reboot from the language selection screen
I guess I'm coming to an end in terms of my phones life
Click to expand...
Click to collapse
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Transmitted via Bacon

Hmm, sounds like a hardware issue to me if you can't even get passed the welcome setup without your phone rebooting... Especially after a FULL factory reset.
Does the reboot start as soon as you touch the screen? This might indicate some kind of malfunction between hardware and drivers.
Raise a ticket on the OnePlus website and request for an RMA. You might also want to file a Paypal claim to speed things up.

timmaaa said:
Not necessarily. Do you have any signal whatsoever? Can you navigate to Settings/About Phone and see your IMEI? Don't post it here but let me know if it's still showing up.
Click to expand...
Click to collapse
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Okay - breakthrough: I downloaded the package from this post: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Ran all 3 ONEPLUS ONE - x.bat and now it has prompted me to unlock my sim card. Got through to wifi so I have higher hopes this time around Will see how it goes...

kroogar said:
I can't navigate as I'm blocked by the error message. I do know my IMEI from my Google dashboard though.
I'm still puzzled by the fact that it doesn't recognize my SIM card at all.
Click to expand...
Click to collapse
Whether you know your IMEI or not isn't the point, it's whether it's still present on your device that matters. There have been cases where the IMEI simply disappears (along with your baseband) and having no signal is a consequence of that. I hope you made a backup of your EFS at some point because it's looking like this is what's happened.
Have you tried the automated tool I linked to a few posts back?
Transmitted via Bacon

timmaaa said:
Have you tried the automated tool I linked to a few posts back?
Click to expand...
Click to collapse
Se my updated previous post

kroogar said:
Se my updated previous post
Click to expand...
Click to collapse
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Transmitted via Bacon

timmaaa said:
Ok, so you're all good now? You have mobile signal? You can see your baseband version and IMEI in the settings menu?
Click to expand...
Click to collapse
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.

kroogar said:
Yes I see it and I can send and receive text messages.
Now I'm going to try to restore one of my previous backups again
Thanks a ton for all the help to the both of you. If I could I'd /dcc you a cold one.
Click to expand...
Click to collapse
Be careful, I firmly believe it's a backup that caused this problem, and you might not be so lucky next time. I'd seriously suggest just clean flashing now or you could be inviting the devil to your doorstep.
Transmitted via Bacon

Microphone issue with Oneplus one

I have a oneplus one that I just returned to stock using the method in this thread: http://forum.xda-developers.com/onep...stock-t2826541
Problem is that at some point, while it was rooted, I used this method to make my phone microphone work (changing the build.prop file): https://forums.oneplus.net/threads/f...-issue.284449/
If I had remembered that I'd done that, I might have just left the phone alone. So, now that I'm back to stock and unrooted, my microphone doesn't work and I can't use the above method to make it so. Is there a solution out there I can use without going back to root?
My exact problem with the mic is that when I talk into the phone, the person on the other end can't hear me but I can hear myself (echo) in my earpiece. I can hear the person on the other end fine. If I switch to speaker phone I still have the same issue. Any help would be appreciated.

You'll need to go root again. Lucky this isn't too hard especially if you maintained a custom recovery. If not, then you will have to use adb. Or bacon root toolkit (the easy way).
Sent from my A0001 using Tapatalk

Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.

anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
You can use KingRoot to root without custom recovery. After changing the values you can then unroot it to get future OTA updates

anonymous93 said:
Not really what I wanted to hear, but I guess I gotta do what I gotta do. How can I tell if I maintained a custom recovery or not? I don't think I did.
And can I root without installing a custom recovery or custom rom? All the guides I've found so far talk about all these steps and unlocking the bootloader.
Click to expand...
Click to collapse
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk

Elius2676 said:
Just boot into recovery (power off then power on pressing volume down+power) and see what you get.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I got Cyanogen Recovery. Options are "reboot system now", "Apply update", "factory reset", and "advanced".

So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.

anonymous93 said:
So I used the baconroot toolkit to unlock the bootloader. Then rooted it with a custom recovery. My phone is now stuck in the bootloop. I can boot into TWRP, which I know is a good thing. Just not sure what to do next now to fix it. I'm doing some searching on the forums, but if someone can point me in the right direction, it would be appreciated.
Click to expand...
Click to collapse
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk

Elius2676 said:
Recovering from this will require fastboot magic. The bacon root toolkit should've already gotten your drivers all setup. Now search the web for how to push and install files from your computer in fastboot mode.
Sent from my A0001 using Tapatalk
---------- Post added at 01:03 PM ---------- Previous post was at 01:02 PM ----------
Oh, you can boot into TWRP! Nevermind, just follow the steps to a clean install of your ROM (which one is it, btw?)
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?

anonymous93 said:
Clean install of my ROM from TWRP is good because I failed to mention that I can't get into fastboot mode. The ROM I had was the factory image from this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
What steps do I take to do a clean install of that?
Click to expand...
Click to collapse
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk

Elius2676 said:
I'm assuming you've tried to follow the steps given in the link you just sent?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yes and no. Turns out I was actually able to boot my phone into fastboot mode. So I did that, used the baconroot toolkit option of "flash stock + unroot" and I was back to the start. My device now has an unlocked bootloader, but I think I have issues with the tamper bit. When I get my device info the "Device tampered" is set to "false" and the "device unlocked" is set to "true". I know they should both be true, but I can't for the life of me figure out how to use the zip file to change the tamper bit. I did it before, but I'm just not figuring it out this time. I hate doing this stuff.
I think once the tamper bit is correct I should be able to go back to baconroot to root and reinstall the custom recovery.
Update: I finally figured this out, now rooting with bacon root, hoping it works.

I'm all set, now to make the adjustments so my microphone works. Thanks to everyone that helped!

So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.

anonymous93 said:
So, I forgot that one of the reasons I unrooted was because I couldn't update and I was tired of getting notices that there was an update and not being able to execute it.
So I now have cyanogen OS version 12.1 and I have a notice for an incremental update. I made sure that "update cm recovery" was unchecked so that I didn't lose root, hit the update button and I got the error message "error executing updater binary in zip '@/cache/recovery/block.map' "
From what I could find it looks like I need to download and flash the update rather than using the OTA updates. Is that correct? Can I update to 13 or 14 or are there issues with those roms? where do I go to get these downloads? when I flash updates does it wipe my phone? will I have to reinstall all my apps and settings?
I really dislike doing this stuff. I can do it, but I hate it. any very clear step by step instructions would be GREATLY appreciated.
Click to expand...
Click to collapse
So sounds like you just wiped everything and your phone is back to stock now, but I'm getting the impression you still have a custom recovery or modified system partition and the OTA updates don't like that. So yes, you'll need to flash updates in your recovery. It's not as bad as it sounds.
And about Android versions available to you, the stock COS (which might actually say "CM..." when you check your Android version in "about phone" in settings - confusing, I know) can normally receive the OTA updates (except in the cases mentioned above) or you can get the official updates online in zip form and flash them yourself (even with the stock recovery -which I'm pretty sure you have still, unless one of your methods to fix the phone installed a custom one like TWRP or CWM). The other ROM/OS options you have are about as plentiful as the stars in the heavens (since android is open source). I personally like to stick with CM especially since they do what they do very well and they have a particular interest in there OnePlus One. They just released CM 14 nightlies (which basically means it's the latest version of the OS, bugs and all, built every day). Though, to be honest, this CM 14 nightly is ridiculously stable for a freshly released nightly. At this point, though, cyanogen hasn't implemented a fair number of their customizations that are in their previous versions. So if you want the best complete CM experience right now, go with CM 13.
And to answer your question, updates like the ones that are OTA, don't wipe your data or storage. However, if you switch from COS to CM, you'll have to clean install and that will lose your data at the least (your internal storage can usually be kept between ROMs if you've got a custom recovery).
Sorry, in throwing a lot at you right now. Probably just created more questions than answers...
Sent from my A0001 using Tapatalk

Thanks for your help and the explanations. When you talk about COS vs. CM is that Cyanogen OS vs. Cyanogen Mod?
I was able to root and I have TWRP installed. In about phone it says "Cyanogen OS version" is "12.1-yog4pas1n0". That's the Cyanogen OS correct?
Where do I go to download the update for 13 (whatever matches what I already have) and is there a guide for doing that? I'm reading about updating to 13 and everything I see (so far) states that the update has to happen with stock recovery. Is there an option to run the update with TWRP?

Wait a minute... If I unroot but keep the bootloader unlocked then it won't wipe my phone and I'll be able to take the ota updates right? What about the change I made to the build.prop file for my phones microphone? Will that get wiped if I unroot? That's the big question.
Nevermind about unrooting. After some searches it seems that a full unroot would require a rest which would delete the mod I made for the microphone. I found that supersu can "unroot", but it's not actually a fill unroot which means that I still probably wouldn't be able to do the ota updates.

Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk

Elius2676 said:
Maybe I need to gain a better understanding of your original problem... But I think that there are plenty of ROMs out there that have addressed microphone issues with the OnePlus One (I think a lot of the problems come from it having 2 noise cancelling mics). Not 100% sure if cyanogen ever implemented a fix for the mic in later updates - probably a good thing to look into. Otherwise, look into alternative ROMs. I personally don't have issues with the latest CyanogenMod nightlies, but it almost seems like there are differences between OnePlus ones (inconsistency in the manufacturing process, perhaps).
Oh, and yes when I say COS and CM, they are cyanogen OS and CyanogenMod, respectively.
Sent from my A0001 using Tapatalk
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
And if you don't want to use something potentially as unstable as a nightly, CyanogenMod also has snapshots that are more like monthly, stable versions.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?

anonymous93 said:
I'm pretty sure my problem is related to the 2 noise cancelling mics issue. It works great with the build.prop changes. Once I get an update installed on my phone I'll have to see how the microphone works.
So if I want to go to cyanogenmod 13, I would have to wipe my device and install that OS. When I do a backup in twrp, can I restore that backup (i.e., all my apps & settings) once the new os is installed? Or does that option restore the old OS?
Click to expand...
Click to collapse
A backup in TWRP (or nandroid backup) is like a perfect picture of what you phone was running just before you booted it into recovery. So when you restore one of them, it is like the phone steps back in time to when you made the backup, restoring the system (read: OS), data (read: apps), and cache.
In other words, you do a backup so that you always have something you can restore if you break your phone/have boot loops or what have you when flashing new ROMs.
If you go from COS to CM, it will require a clean install which means you will need to setup your phone the way you like it again. That being said, there is an app called Titanium backup that doesn't work the same as a nandroid, but can backup your apps and data and is capable of restoring them from one ROM to the next. It's not always perfect, but it can do a lot.
I personally have just chosen to embrace the chance of needing to start fresh every once in a while. I use Nova launcher and I have a Kustom LWP, both of which I made backups of in their respective app settings. I save those backups and whatever else I want to internal storage and I just don't wipe that partition in TWRP. To be safe, I also keep backups in the cloud. Everything else I just download again from the play store and setup the way I like.
Sent from my A0001 using Tapatalk

Well, its looking more and more like I might go to cm. Once I do that will I still have to wipe my phone to flash updates? Or will I still have to do that for updates every once in a while?

HELP! i deleted my OS

Alright here goes
I wanted to do a factory reset to my shield k1
But i did it in twrp instead of settings
So i accidentaly selected everything and deleted it
Including android :crying:
So i need help
If someone could show me how to
Install the stock android for the k1
Id appreciste it
I tried installing lineage 14.1 but it wouldnt work i
Dont know why :update: i did get it to work there were lines of code needed to be deleted in the zip:
I tried opening fastboot on my laptop and it closes and
Opens just command prompt
Also before i deleted os the usb debugging was turned on just so you know
If anyone can help me atleast get lineage to work that would be awesome
Also please dont link to tutorials ive read them all
And i guess i need to be baby fed the information
Plz help me!

Just download the factory image from Nvidia and boot into fastboot.
Sent from my iPhone using Tapatalk

djkinetic said:
Just download the factory image from Nvidia and boot into fastboot.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I might be able to talk tech but im sorry
Could you please elaborate

Fastboot closes right up because ur are double clicking on it... U should open a command prompt by open file explorer where fastboot.exe and the factory image (stock rom from nvidia) is located on ur pc, press right mouse click and SHIFT at the same time. On the drop down menu choose: open command prompt here. And there u go, u have a command prompt that will recognise the fastboot and the name of the files.
Now put ur shield in fastboot mode, plug it to ur pc.
Now start the commands from a tutorial to go back to stock for the shield tablet.
And lastly... If u dont know how to go back to stock (aka use fastboot), u shouldn't try flashing roms or even use twrp... IMO.

Iceek1 said:
Alright here goes
I wanted to do a factory reset to my shield k1
But i did it in twrp instead of settings
So i accidentaly selected everything and deleted it
Including android :crying:
Click to expand...
Click to collapse
You've made a number of basic mistakes that were completely avoidable. For your benefit, it's time to learn some lessons (the hard way in this case) before proceeding:
Wiping everything in TWRP was not a complete "accident". You deliberately (probably carelessly) ignored the message in TWRP "Wipe" section which tells you the default wipe is the only wipe you need most of the time. It says this for a reason. The default wipe (data, cache and Dalvik) is all you need for a "factory reset" in 99% of cases, and keeps the OS intact.
So you went into the "Advanced" wipe options. Again, it's called "Advanced" for a reason. This term implies that you shouldn't be messing with these options, unless you have some "advanced" knowledge, and know exactly what you are doing. You shouldn't be wiping anything, if you don't understand what it is, or what the consequences will be.
Another basic best practice: always make a TWRP "nandroid" backup before messing with anything. If you did that, you would have a backup of the stock ROM to easily revert to. It's the first thing I do after flashing TWRP. Now, if you truly wiped "everything" in TWRP, that would include internal storage and SD card, which would means your TWRP backups are also gone. But all the reason, to follow the advice I gave in the previous paragraph.
Iceek1 said:
I tried installing lineage 14.1 but it wouldnt work i
Dont know why
Click to expand...
Click to collapse
Neither do we. At least not without any detailed info. Don't just say "it didn't work", as that doesn't tell is anything. This is almost certainly pilot error, and easily fixable. Provided you give us some info. How far did you get flashing Lineage? Did it flash successfully, or not? If not, what were the error messages? If it flashed successfully, then exactly what happened next? Stuck rebooting on logo screen, or it booted but apps force closed?
Did you flash a gapps package right after flashing Lineage (which is required)?
What version number TWRP?
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
Iceek1 said:
I tried opening fastboot on my laptop and it closes and
Opens just command prompt
Click to expand...
Click to collapse
If you don't know how to use fastboot, how did you unlock the bootloader and flash TWRP?
---------- Post added at 11:01 AM ---------- Previous post was at 11:00 AM ----------
C4SCA said:
And lastly... If u dont know how to go back to stock (aka use fastboot), u shouldn't try flashing roms or even use twrp... IMO.
Click to expand...
Click to collapse
I agree 100%.
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
Iceek1 said:
I might be able to talk tech but im sorry
Could you please elaborate
Click to expand...
Click to collapse
If you search NVIDIA's Download Center, you will find the recovery image for this device, which includes instructions on how to install it.

redpoint73 said:
at first i did teh recomended wipe but i wanted the sd card wiped too
So i went back in and checked everything not knowing that would delete os and i didnt see a warning message saying it would
And i got lineage to work i had to unzip and delete the assert lines of code
And ive had people do the fastboot for me but i have gone back and twrp and rooted bye myself
For some reason when i go to shift and right click the window for command prompt doesnt work
Im sure i can figure that out though
Thx
Click to expand...
Click to collapse

C4SCA said:
i have rooted and twrp on my own before i just guess i am not good with fastboot?
Click to expand...
Click to collapse

Iceek1 said:
So i went back in and checked everything not knowing that would delete os and i didnt see a warning message saying it would
Click to expand...
Click to collapse
You need a warning message telling you that wiping system . . . would wipe the system?
Makers of TWRP assume that anyone using TWRP has some basic knowledge and would take some care before wiping things, especially in the "Advanced" section. And that even if you had no OS, you know how to restore it.
Iceek1 said:
And ive had people do the fastboot for me but i have gone back and twrp and rooted bye myself
Click to expand...
Click to collapse
Yeah, you should stop doing stuff like that. Shortcutting the process by letting other folks do the work for you, got you were you are.
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Iceek1 said:
For some reason when i go to shift and right click the window for command prompt doesnt work
Click to expand...
Click to collapse
Hover the mouse cursor over the window that contains fastboot.exe. Shift+ Right click. You should see a pulldown menus appear. You should see an open "Open command prompt here".
What about this doesn't work?

(Redpoint73;75492581You need a warning message telling you that wiping system . . . would wipe the system?)
Oye mate theres no reason to be a jerk
(Yeah, you should stop doing stuff like that. Shortcutting the process by letting other folks do the work for you, got you were you are.)
I tryed following tutorials i just didnt understand
And theres no reason to be a jerk about it
(Hover the mouse cursor over the window that contains fastboot.exe. Shift+ Right click. You should see a pulldown menus appear. You should see an open "Open command prompt here".
What about this doesn't work?)
Its not just me its happened too,i had to open up run go to directory and shell and rename something k mate