yashsingh1/xdaforums huggingface dataset:
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] prokennexusa:
Kindle Fire First Aide Revision 4.1.53-Beta for Windows - Permission Denied SOLVED

field3d,

Please follow these steps to solve you problem.

Step 1: Download and Install Kindle Fire First Aide via the instructions - do not forget to add the PATH statement of C:\KFFirstAide

Step 2: Plug the Kindle Fire into USB, BE SURE the Kindle is powered OFF. Then select Option 16 wait until the software instructs you to turn on the Kindle Fire.

Step 3: If that method fails try Option 15 to boot the Kindle into Fastboot

Step 4: Once you are in Fastboot use our software to restore the Kindle - Option 7

Step 5: That is it, you may use our tool to install Google Play Store and Google Apps

We solve the Permission denied issue and the build.prop edit issues - here it is hot off the presses at 23:53 on 02/22/2013.

Rev 4.1.53 Change Log:

1. Fixed Permission Denied Problem

2. Changed the timing on Option 21

3. Streamline code - processes at a faster rate of speed

4. Changed Enable OTA to Selective Enable

5. Found double quotes with the build.prop lines, this caused the build.prop edits to fail.

6. Removed the Symbolic Link to Temp after every install

*****Kindle Fire First Aide Revision 4.1.53-Beta RunMe 02/22/13 at 23:53 for Microsoft Windows*****

Kindle Fire First Aide Revision 4.1.53-Beta for Windows Universal Package: KFFirstAide.zip (Ubuntu One)

Kindle Fire First Aide Revision 4.1.53-Beta for Windows 32-bit Version: KFFirstAide32.zip (Ubuntu One)

Kindle Fire First Aide Revision 4.1.53-Beta for Windows 64-bit Version: KFFirstAide64.zip (Ubuntu One)

Make sure you are running the latest version of Java SE Development Kit 7u15
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] field3d:
Thank you Thepooch

Thank you Thepooch you saved my life KFHD_SRT_v2.1 worked like a charm!!!!!!!! all with your directions. Thank you for the time you wasted wit me. This forum is great just friendly and amazing people.

Thank you prokennexusa now I´m rooted I´ll proceed to install google apps.
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] TigerG8:
kfhd srt 2.1

I can't find that file anywhere! i've tried downloading from the link, which takes me to the google docs download page, but it always comes back with a communication error about 3% into the download. would you, thepooch, or anyone, be able to send this file to me?
[8.9" Kindle Fire HD Q&A, Help & Troubleshooting] galearned:
Kindle Fire First Aide requires ADB for restore?

Prokennexusa:

There seems to be a problem with using kindle fire first aide to Restore a kindle fire if not already rooted?

Steps 15 or 16 gets the tablet into fastboot

To restore, go to step 7

Step 7 part way down warns the user that this operation will fail if not rooted?

Seems that if the user has messed up the tablet and it is not rooted, the user cannot restore the system image unless the root note is incorrect.

The next problem is that if a tablet is not in ADB mode, root cannot be achieved?

All of the instructions seem to use only ADB to root the tablet.

I noticed that root many android uses only ADB commands to root.

It looks like KFHD_SRT_v2.1 will restore the system image with root which is good ( will have to try it to see).

What happens if the boot or bootloader is broken?

Is there an image that puts all of the partitions back? (Boot, Bootloader, Recovery and system images)

I found a nice post listing KFHD8.9.restore.zip from soupmagnet which restores all images but, is a linux script and may also need root to complete.
[Nexus 7 Q&A, Help & Troubleshooting] ehcool:
So My Nexus 7 is simple Stock android 4.2.1 with root and i go to update to 4.2.2 and i get a error (The red triangle one)

Can anybody help i hear there are others with this same problem but yet to find somebody with a solution, do you think i should unroot and relock the nexus and try and update again or just reflash back to stock image
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
That screen sounds a bit like the stock recovery, not a custom recovery as one would expect with a rooted device. Please explain.

The error that occurred is given in the recovery log file - /cache/recovery/recovery.log

Please report what the error was. If you actually have root in the ROM you should be able to view this file.

No need to relock your boot loader - that is unrelated and relocking it only complicates things.

One more thing - OTAs are not designed to be robust in the face of and arbitrarily reconfigured ROM. It is unreasonable to expect that they will work correctly on a rooted device. They are meant for 100% stock devices, PERIOD. While you may not remember explicitly changing something, if you gave root privilege to an app, that app might have changed things which cause the problem that occurs. On this forum, there have been claims that Stickmount, Beats Audio, and even Titanium Backup can cause these sorts of problems.
[Nexus 7 Q&A, Help & Troubleshooting] MatthiasSchuetze:
And how do you fix this? I have the same problem. I guess you need a different file then the OTA one. Where do you get this file?

Thanks!
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Ummm... you are forcing me to guess about your situation. You are rooted, but also do not have a custom recovery installed?

What error message do you find in the /cache/recovery/recovery.log file? Please do not simply say "Status 7", report the FULL ERROR message.

As I said, the OTAs are meant to be used with pure stock ROMs, not customized/rooted ROMs. There do not exist an infinite array of OTA file variations corresponding to a fix for the exact problem you are experiencing, unless you were to create one for yourself by unpacking the OTA zip file and hand-editing the META-INF/com/google/android/updater-script file to skip over the problem you are experiencing.

And if you did that, you would certainly need to use a custom recovery to install it, as doing the operation described above would break the signing of the OTA package, so the stock recovery would refuse to install it.

The other alternative which allows you to use the unmodified OTA is to "fix up" a customized ROM by manually replacing all files that were removed or altered with their original stock versions. This process seems almost as ridiculous as the scenario described above, as now you are purposely breaking the modifications performed by root-aware apps (Stickmount? Beats Audio? Titanium Backup?)

The amount of effort this whole process will take is variable depending on how much stuff has been changed since you rooted. When the OTA performs it's checks prior to beginning it's patching operations, it halts on the first check which fails. Which might mean that you will need to iterate several to many times the process of:

- run the OTA, look at the error in /recovery/log/recovery.log

- hand patch the file involved

- re-run the OTA.

Doing the above can be problematic if you have changed multiple framework files - if you replace stuff one file at a time it is possible to wedge the OS because of dependency issues.

The only good news here is that because the OTA runs all it's checks before it patches anything, it is safe to run it as many times as you can tolerate. (On tilapia devices, though there is evidence that using custom recoveries is almost never a good idea if you want the radio firmware to be updated correctly).

A wholly better idea is to simply start over. Make a full Nandroid backup of your current ROM. If you want, you can also experiment with backup/restore apps like Titanium Backup and/or Carbon.. Then you install a pure stock ROM from the Google Factory images, and begin re-customizing all over again, as if you had just bought the tablet.

If you don't like the result, restore your Nandroid backup. That's what backups are for.**

good luck

** its a good idea to get copies of your Nandroid backups off of the device, as there are various ways that the entire /data partition can get wiped - including the psuedo-SD card containing all your precious backups. You've been warned.
[Nexus 7 Q&A, Help & Troubleshooting] MatthiasSchuetze:
First of all. Thanks for the quick response. Secondly, I get this error on both my nexus devices. The Galaxy Nexus and the Nexus 7. Though I don't know if it is exactly the same error - it is very similar (with the android guy on its back and the red triangle). I have a picture of the error message that comes up on the Galaxy Nexus. Both devices have an unlocked bootloader and a custom recovery. The Nexus 7 is deffinitely rooted with the Galaxy Nexus I'm not sure - I thought so but Titanium Backup doesn't let me backup anything and I don't have a custom ROM running on the phone.

So if I understood you correctly I should go back to the stock recovery and unroot it as well and then try it again?!

Why is the picture that I attached not showing?

This is the error message:

ClockworkMod Recovery v6.0.1.9

E: Invalid command argument

Finding update package...

Opening update package...

Verifying update package...

E: failed to verify whole-file signature

E: signature verification failed

Installation update...

Verifying current system...

assert failed: apply_patch_check("/system/build.

prop". "THEN A WHOLE LOT OF NUMBERS AND LETTERS")

E: Error in /cache/07501b11ad3b.signed-yakyu-JDQ3

9-from-JOP40D.07501b11.zip

(Status 7)

Installation aborted.

I rechecked it for the Nexus 7. The message is slightly different:

assert failed: apply_patch_check ("/system/lib/libSR_A

udioIn.so", "THEN THE NUMBERS AND LETTERS AGAIN")

E: Error in /cache/6ece895ecb23.signed-nakasi-JDQ39-fr

om-JOP40D. 6ece895e.zip

(Status 7)

Installation aborted.

Now, it does show (the picture). Nice. :)
[Nexus 7 Q&A, Help & Troubleshooting] AndDiSa:
On both devices the files do not match the expectations (assert failed), i.e those files are not the original ones the OTA is expecting -> You need to re-apply the original files to your ROM before you can apply the OTA or you need to do flash the 4.2.2 system manually, which probably might be the easier solution.
[LG Optimus 3D] kalamake:
My phone is stuck on jellybam. I flashed with smartflash original v10 and same file with flashtool. Official update went thru and still when i power it on jellybam starts. Also tried bootv21e, first time it shows recovery and then back to jellybam. I have backup of rom but it has md5 error

Maybe fastboot to upload something somewhere? Quite noob on how android works.

It was xbsa404 bin&fls.

And how to get original bootloader or what ever it is when press vol+ and plug usb cable?
[LG Optimus 3D] omgomg:
Wrong section.

At least bother reading where you post at.
[LG Optimus 3D] kalamake:
Rom problem, so what would be better?
[LG Optimus 3D] kidkoala_uk:
Try the general section for starters.
[LG Optimus 3D] kalamake:
Does anyone got how to begning restoring system?
[Fascinate Q&A, Help & Troubleshooting] fawzisaeed:
why internet cant support in cyanogenmod10.2? in samsung fascinate roms nightly 21/2/2013 android4.2.2?

in my country yemen with company yemenmobile(cdma) and in other phone like galaxy s3 and prava support internet

the information for yemen mobile is:

<apn carrier="yemen mobile" numeric="42103" mcc="421" mnc="03" apn="#777" user="ymobile" server="" password="ymobile" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="" />

please help me for this problem

thanks for any person
[Fascinate Q&A, Help & Troubleshooting] bbrad:
First of all its CyanogenMod 10.1 and I can you rewrite that I couldn't understand half of that
[Fascinate Q&A, Help & Troubleshooting] hhp_211:
You could try this :::

First open Voice Dialer...say "Open apns"...select it.

Add the information...capitalization matters...

Click: save,,, then

Click: Yemen Mobile
[Fascinate Q&A, Help & Troubleshooting] fawzisaeed:
SORY CYANOGENMOD 10.1

MR: BBRAD ISAY

WHY 3G(EVEDO) NOT WORK IN MY COUNTRY YEMEN BUT WHEN CHANGE ROMSTHE 3G (EVEDO) IS WORK GOOD.

WHERES THE PROBLEM IN THIS CYANOGENMOD

MR:hhp_211

ICANT UNDERSTAND THIS Add the information...capitalization matters

THE APN FOR MY COUNTRY IS:

<apn carrier="yemen mobile" numeric="42103" mcc="421" mnc="03" apn="#777" user="ymobile" server="" password="ymobile" proxy="" port="" mmsproxy="" mmsport="" mmsprotocol="null" mmsc="" type="" />

CAN ANY PERSON MACK FOR ME APN-CONF.XML FOR PUT IN MY PHONE

HELP ME PLZ IAM TIRED
[Fascinate Q&A, Help & Troubleshooting] fawzisaeed:
any person help me
[Fascinate Q&A, Help & Troubleshooting] hhp_211:
View attachment 1765842

here is a basic file for you.

it may or may not work properly, but I figured you can try it.

you will need to change the name of the file to read only

apns-conf.xml

and not

apns-conf.xml.txt

.
[Fascinate Q&A, Help & Troubleshooting] fawzisaeed:
thanks but not work

can eny roms support arabic language like cyanogenmod?
[Fascinate Q&A, Help & Troubleshooting] bbrad:
Dude no offense to your language but please use Google translate we don't understand what your asking speak it in English if you want 3g use the apns hpp gave you there's nothing more we can do we gave you everything to get your 3g working
[Fascinate Q&A, Help & Troubleshooting] fawzisaeed:
I want to run the Internet in either 3G mobile or any other Internet

Internet in the official English version Ergonomics I was in this versionrom(cyanogenmod10.1) does not function at all

I hope that the idea has arrived

Did anyone find the help in any way

Thank you in advance
[Fascinate Q&A, Help & Troubleshooting] bbrad:
Did you try hpps apns?
[Fascinate Q&A, Help & Troubleshooting] fawzisaeed:
yes iam try more time but not work
[HTC Desire S] MarshFlower:
Hii everyone, sorry for the stupid question, i'm still a noob. Will anyone port ubuntuOS on saga?

Sorry for bad english. :(
[HTC Desire S] asgardr:
http://xdaforums.com/showthread.php?t=1256949

Good luck;)
[HTC Desire S] MarshFlower:
ahahah no, i mean ubuntu touch. I don't know how tell it
[HTC Desire S] Moscow_97:
It's even demo for nexus 4. Canonical uploaded it for devs. Just tested for 20 mins and restored back to jelly bean
[HTC Desire S] MarshFlower:
Thank a lot
[HTC Desire S] Fredericosilva:
Porting Guide
[HTC Desire S] Fredericosilva:
Saga is on "Work in Progress" List! :)
[HTC Desire S] amidabuddha:
Hmm I am really curious who is this guy johnas. Any ideas?

Sent from my HTC Desire S
[HTC Desire S] Fredericosilva:
I have no idea. But Im curious too.

EDIT: https://github.com/gh1234
[HTC Desire S] MarshFlower:
Thank for info. Im curious like u
[HTC Desire S] amidabuddha:
Ok, not from "ours" :) let's see what he will bring

EDIT: I have sent him an e-mail offering my and this forum assistance so I hope if he gets troubles we can speed up the process :)

EDIT2: I see Flinny is already working with him so I think this is going to end good
[HTC Desire S] Husky34:
R: [Q] UbuntuOS

I think we all love Flinny :D
[HTC Desire S] MarshFlower:
I love him so much ahahaha
[HTC Desire S] hellnest:
What a good news. Its mean I will keep this phone for one more year lolz
[HTC Desire S] gh1234:
Hi folks, I'm that Jonas guy ;). I thought I should come over here to report what I'm actually working on.

Well I don't work with Flinny, I just forked the Andromadus stuff which needed to be changed to my repo (I hope the Andromadus team is okay with this), to be found here: github/phablet-saga/android (I'm unable to post outside links to prevent spam)

You can already build Ubuntu Touch from that repo (I finally got the build blocking merge bugs fixed today at like.. 4 am :D) but it won't even boot. I'm currently debugging stuff and will report back here if there are any news.
[HTC Desire S] amidabuddha:
Hi!

It is great that you have found us :good:

Good luck with the build !
[HTC Desire S] MarshFlower:
Good luck!
[HTC Desire S] El Aero:
Hi everyone!

I'm trying to port Ubuntu Touch to HTC Desire S (saga). When I build the image and command

it crashes with this:

What does it mean? What should I do to fix it? Please help.
[HTC Desire S] amidabuddha:
Well open the /build/core/main.mk file and add the missing endif at line 682

Sent from my HTC Desire S
[HTC Desire S] gh1234:
Okay, 1st thing: why do you run this as root? I mean that is a really bad idea as the makefiles can run stuff as root, too in your case.

2nd: Did you init your environment with my repo or is it something else? If its something else we might need the mk file to help you.
[HTC Desire S] hellnest:
Welcome to community my friend :)
[HTC Desire S] El Aero:
When I run without root:

So I just tryed to run it as root. To tell the truth, I'm absolute noob in Ubuntu - I installed it to port Touch=)

I used drivers and kernel from Andromadus. Also attached main.mk file to this post, so you maybe could see what's wrong.
[HTC Desire S] gh1234:
Did you run "repo init" as root? Seems to be the case. You can fix it by running (as root again):

Which will give your user the needed rights for the directory.
[HTC Desire S] El Aero:
Thanx!

But I still don't know what to do with
[HTC Desire S] sciepy:
Can you put a "endef" after line 683 in your file and see if it works?

Should then look like this:

define add-required-deps
$(1): $(2)
endef

Would like to help porting Ubuntu, but right now I'm not even able to build cm10.1 for saga, will play around with that a bit first (currently getting some weird build errors...). Good luck to you :)
[HTC Desire S] gh1234:
Okay guys first testbuild...

This is so alpha that there is actually no need to test it (I found numerous bugs myself) but I guess some of you might be curious...

No sound

somewhat laggy and some parts are scaled wrong (the keyboard is half off screen and stuff like this)

no wifi I guess

it's quite hard to do touch gestures as the left/right boarder seem to be too small, to do left/right swipe you mostly have to touch the lower screen area (the button area), swipe left/right but keep your finger on the black screen border and finally swipe back in :D or simply experiment how to do this best.

No camera

I think phone calls actually work (but makes no sense without sound) - However you can send / receive SMS

There are many things left that I didn't test yet. I will focus on scaling issues and sound now :)

First things first, one problem with Desire S device is, that the eemc memory is far beyond specs minimum requirements are "4-8GB eMMC + SD" which means that the standard install process won't work. So the disadvantage for the user is, that the prebuild userlevel packages simply won't install successfully. However there is a workaround using the sdcard to store some tmp files (I have a patched image for you, and might implement a script fetching + patching dailies later) which leads to the first requirement:

Be sure that there is at least one gb of free space on your sdcard!

Do a backup! And be sure that there is still 1gb left ;)

Download the two zip images I will provide below.

I don't know which hboot is required... sorry but I use the latest one and it works.

I'm pretty sure this will not work with MDDI panel.

Installation:

flash the two zip files (you should start with the phablet-saga* file)

If you are htcdev unlocked you need to flash boot.img via fastboot

reboot system and hope that it actually works

Good luck :D

I will make a dedicated post when I have access to some areas on XDA (I cant even post links yet so you have to fix this link yourself):

hxxp://share.cascaded-web.com/phablet-saga/alpha/2013-03-04_20-15/
[HTC Desire S] jugg1es:
@ gh1234 pm a mod or fallen Spartan and ask if you can make a dev thread for this, its not unheard of but is rare.

“To live is the rarest thing in the world. Most people exist, that is all.”

― Oscar Wilde
[HTC Desire S] El Aero:
It worked, but then crashed with something else)) Anyway, thank you for help! Good luck to you as well!:)

---------- Post added at 12:58 AM ---------- Previous post was at 12:10 AM ----------

flashed Ubuntu Touch. Everything is slow and almost nothing works, but I'm pretty much impressed! Great work! Realy look forward to seeing more stable biulds!
[HTC Desire S] El Aero:
First impressions:) see photos attached
[HTC Desire S] Jedioscuro:
R: [Q] UbuntuOS

Can't wait to flash it as soon as it will become more usable!
[HTC Desire S] hisname:
OMG! it boots!!! :eek::eek::eek:can't believe my DS is capable of running this!

Sent from my supercharged :tank:
[HTC Desire S] PVL_93_RU:
Very poorly though
[HTC Desire S] kibril:
Wi-Fi For Ubuntu Touch

Can u use opensource driver for wi-fi card? It must be brcmfmac (http://linuxwireless.org/en/users/Drivers/brcm80211)...
[HTC Desire S] hisname:
that's why it's called an alpha release

Sent from my supercharged :tank:
[HTC Desire S] gh1234:
Exactly what I said... There are some issues with openGL if you have a look at logcat so the performance will increase when these are fixed.

I will have a look at that wifi driver but I guess I know how to fix the current issue. Don't even know which driver is used by Andromadus kernel... I will have a look as soon as I'm at home guys.

Further there is a launchpad bug to get support to support small eemc #1145984 feel free to mark yourself as affected.

https://bugs.launchpad.net/touch-preview-images/+bug/1145984

I will not pm a mod to get access to dev section as it does not seem to be too hard to make 10 posts ;) but thanks for advise.
[HTC Desire S] svicenty:
Which phones is this compatible with
[HTC Desire S] gh1234:
Have a look at this list: https://wiki.ubuntu.com/Touch/Devices
[HTC Desire S] nikhilpatil:
Great effort gh1234 :) Looking forward to a beta release!
[HTC Desire S] PVL_93_RU:
I guess even the official GNex Ubuntu build is far from being beta, let alone the DS port
[HTC Desire S] El Aero:
Seems like you've uploaded a new build. Any changes?:o
[HTC Desire S] NVardan:
Great news. Will try it ASAP.

Tried to download the phablet.zip. I get this message:

"Forbidden

You don't have permission to access /phablet-saga/alpha/2013-03-09_00-58/phablet-saga-20130308-UNOFFICIAL-saga.zip on this server."
[HTC Desire S] El Aero:
Same thing there...can't download
[HTC Desire S] PVL_93_RU:
Maybe it's not a release version?
[HTC Desire S] gh1234:
Sorry guys, I wanted to get this out earlier today but after installing the uploaded version my phone didn't boot. I should not have done a repo sync before building this version as my testbuild worked (which has been overwritten in the build process :D) -.-

I am trying to get this one out asap, the new build would have had wlan support.

I will get this one fixed and I guess I'm able to create a dev thread. (Won't take too long I guess)

BTW I created an automatic patch tool for ubuntu daily builds https://github.com/phablet-saga/patch-daily just run the run.sh file. And if you are lucky todays daily will boot :)

Sorry for the confusion.
[HTC Desire S] PVL_93_RU:
Do you have a page where we could see the changelogs for new builds other than the Github?
[HTC Desire S] gh1234:
I will have a changelog in the dev thread as of the next release :)

EDIT: Okay I will need some time to get the new build out. Current builds do not boot (Segault while loading the UI) I am not sure if this is related to a faulty daily build or if there is something wrong on driver/kernel side. The new kernel/driver build works with the daily I published last time, however the browser does not work even though wifi does, (ssh works + apt-get and stuff is working pretty well). I will upload this driver/kernel build as soon as I get a recent daily image running on the phone.
[HTC Desire S] NVardan:
Looks like there is a new build out there. Will try as soon, as you update the wiki page(to know if it's usable or not). ;)
[HTC Desire S] El Aero:
No saga image is there, only quantal preinstalled
[HTC Desire S] NVardan:
I was going to school, so I didn't check all the directories.The only thing I've noticed, was that there was a new upload. ;)