yashsingh1/xdaforums huggingface dataset:
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Okay, trying to get Hellybean working... but am stuck!

Thank you to everyone providing a reply so far. Please keep the suggestions coming. :highfive:

I am trying to install the recommended Hellybean 4.2, and am stuck.

The phone was stock Gingerbread, and then I installed the GeeWiz 4.4 ROM on it. Had some lagging and crashing, so now I'm trying to get Hellybean 4.2 on it, per recommendations of others.

So I downloaded the latest Hellybean 4.2 from the hellybean website. I then booted into recovery, and selected Update from Zip and and tried to install the Hellybean zip. I get a Status 7 error. Some sites said to try it 3 times. I tried it 5 times. No dice.

I can't find a Hellybean 4.2 Fascinate thread on XDA, so details are sparse. Am I blind? :(

Am I correct in understanding that Hellybean 4.2 includes the devil kernel? Or do I need to ODIN a different kernel first?

I installed ROM Manager to get the latest CWM Recovery, but it says the Fascinate is an "unknown device". There is no CWM Recovery installation file for the Fascinate listed on the Clockworkmod website. UGH! :crying:

Can anyone help? I can follow step by step instructions real well. :good:
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Progress Update

I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:

Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.

Help! :(
[Fascinate Q&A, Help & Troubleshooting] skepticmisfit:
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)

1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)

2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://xdaforums.com/showthread.php?t=1238070

3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears

4. wipe data and cache

5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)

6. reboot

7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.

if any of my guide didn't help, just follow the thread i linked in step 2. it's a good comprehensive guide.

also never flash anything with ROM Manager, it's useless for this phone because the version of CWM on ROM Manager is really old. i've bricked my phone when trying it.
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Getting closer!

Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops:).

So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).

I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.

The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.

Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
[Fascinate Q&A, Help & Troubleshooting] skepticmisfit:
wipe data before installing helly. also i've never bothered with build.prop in Hellybean. it only references to EI20 for Voodoo Sound drivers. EI20 is the stock build for.. i believe the US Cellular Mezmerize (aka not the Verizon Fascinate). so don't screw with it :p

yes stock radio is good. EH03 is a good radio but if you want you can flash EC09, based off of a leak of GB. some people have good luck with it, i used to but i like EH03.

so.. i'm not sure if you can boot the phone into helly bean. it sounds like you were getting a lot of "status 7" errors, which i didn't ever get while trying to use helly. this may or may not be caused by the sd card. try a different card if possible. if you're bricked at this point just start over from EH03.

also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Good advice!

Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck :confused:, could you guide me to a source for it? Thanks!
[Fascinate Q&A, Help & Troubleshooting] skepticmisfit:
here you go: http://andromirror.com/file/1386

good luck!
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Sooooo close...

Thank you for the helly link!

Followed instructions, and successfully got it to helly!:good:

But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.

Any thoughts/ideas/solutions? Thanks!
[Fascinate Q&A, Help & Troubleshooting] hhp_211:
cache...

give us what the recovery version number is.

Is it the red touch recovery (that is what is included with hellybean)

gapps...

bad download maybe, it does happen...

get and verify the md5 yourself with an app

for windows

or an android one

like this one

are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip

its what you need to start with,, and then after you sign in to your account,, it will check to see what needs to be updated.

.
[Fascinate Q&A, Help & Troubleshooting] TC93:
I tried the cm10 mentioned here. It does seem very nice. It appears to have more features than Geewiz also, along with a lot more ringtones.
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Information

Thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?

I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
It's the blue CWM, forgot to mention that...
[Fascinate Q&A, Help & Troubleshooting] skepticmisfit:
whoa you're not supposed to have blue recovery after flashing a 4.x ROM (or MTD as we call it).

go to step 4 in this guide: http://xdaforums.com/showthread.php?t=1238070

you're going to have to reflash EH03 in Odin before doing anything because your recovery is borked.
[Fascinate Q&A, Help & Troubleshooting] rockpaperlizard:
Got it!!

Finally got helly onto a phone! Ended up starting all over, and then just flashing to helly since had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:

Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
[Fascinate Q&A, Help & Troubleshooting] skepticmisfit:
that's weird that 3-finger into recovery is broken for you.. it wasn't for me. but whatever, as long as it works :D
[Nexus 7 (2013) Q&A] zeroxia:
Hi.

The connection is:

Nexus 7 2013 --> SlimPort (SP1002) --> HDMI Cable --> Dell UltraSharp U2414H LCD display.

There is a 3.5mm audio plug jacket on the U2414H and I plugged a stereo speaker into it to play the sound.

The first time I connected the device to the monitor, there was a message flashed over on the display, saying something like "Unsupported audio format". Then there was no sound at all.

Then I unplugged the slimport from N7 and plugged it back, there was sound, but at full volume. Volume adjustment on the device is not possible, it is either muted or full amplitude. Another weird thing, the limit is only effective on the "media volume", "notification volume" has adjustable steps as usual, but the notification sound is played from the tablet. Furthermore, volume slider triggerred by pressing volume buttons reflects this "two-step" correctly: the slider is either on the left or the right. While the slider in Settings -> Sound -> Volume for media has several stops, but all non-zero stops have the same volume amplitude, that is equal to full volume.

If I replace the device with LG G2, all is working well.

At first I thought it might be some compatibility issue between SlimPort and the Dell monitor. Then I replaced the monitor with a normal LCD TV set, still the same syndrome with Nexus 7 2013. So I think the problem probably resides in the tablet or the SlimPort adapter. There is also a thread in Nexus 5 forum describing the same problem: Slimport has only 2 volume settings

The Nexus 7 2013 is stock 4.4 system, rooted, with several Xposed modules activated (GravityBox, App Settings, Per App Hacking, Youtube AdAway). The problem persists after I disable all the modules.

The SlimPort model number is SP1002, I see there is now a SP1003, maybe it's an improved revision over SP1002?
[Nexus 5 Q&A, Help & Troubleshooting] cicciolon082:
I'm trying the Youtube app on my Nexus 5 (version 5.3.32) and it definitely really sucks.

Videos (HD and SD) suffer of frame dropping and sometimes (for example when you listen to a song) there are some punctual audio distorsions (metallic peaks) while playing.

I compared the same music video on a Samsung Galaxy S2 and the difference is embarassing...

Any news/solutions?

As a workaround, i'm using Google Chrome on Nexus 5 for Youtube and it's so much better than the app.....
[Nexus 5 Q&A, Help & Troubleshooting] 3DSammy:
I replaced the Google YouTube app with an alternative called Viral. I even removed the YouTube apk and only have an issue with the Flowly app. Viral includes features that Google ignores such as background audio playback and full control over the UI theme colors. It actually had floating video windows before Google added that feature.
[Nexus 5 Q&A, Help & Troubleshooting] cicciolon082:
It's not accettable that Gapps are not working good on a Nexus device! :(
[Nexus 5 Q&A, Help & Troubleshooting] 072665995:
correct me if I'm wrong but aren't GApps are just supposed to be a collection of Google Apps and is separate from Nexus devices.

With regards to your original comment, the Youtube App is the same for everyone isn't it?
[Nexus 5 Q&A, Help & Troubleshooting] bblzd:
I experience no such issues with the stock YouTube app on WiFi or data. I always have HQ or HD selected.
[Nexus 5 Q&A, Help & Troubleshooting] xXghostXx313:
Does anyone else YouTube app take seconds to launch?
[Nexus 5 Q&A, Help & Troubleshooting] danial.aw:
Yep it takes a few seconds to open but I've noticed that's on all phone
[Nexus 5 Q&A, Help & Troubleshooting] daudster:
Stuttering problem could be due to WiFi optimization. Disable it from advanced WiFi setting.
[Nexus 5 Q&A, Help & Troubleshooting] hawktalon:
Everyone has the same gapps

I thought everyone on the same version of android should have the same version of gapps? Also, there is surely going to be delay when opening apps unless your phone runs on SSD? Well, that would be so cool LOL
[Nexus 5 Q&A, Help & Troubleshooting] gee2012:
Well i`am running stock/no root and i never xperienced any issues as discribed by some users on YouTube, not on wifi and 3G.
[Nexus 5 Q&A, Help & Troubleshooting] jball:
Am sure that the ROM and Kernel I'm on makes little difference but just in case the image shows what my daily driver is.

Not one problem with the YouTube app from the playstore for me.if a video sucks its cause of the person who made it
[Nexus 5 Q&A, Help & Troubleshooting] cicciolon082:
No way...i compared the same video on Nexus 5 and Galaxy S2....
[Nexus 5 Q&A, Help & Troubleshooting] cicciolon082:
I'll try to disable all the battery saving optimizations for wi-fi...
[Nexus 5 Q&A, Help & Troubleshooting] cicciolon082:
Yes...but Google works directly on Nexus...they could guarantee that at least on Nexus devices they are ok!!!
[Nexus 5 Q&A, Help & Troubleshooting] Staggerlee66:
Mine was updated today. Have a look at the store. Utube is famous for stuttering though. Don't think they give it the server power, size, or wotnot, it needs. .
[Nexus 5 Q&A, Help & Troubleshooting] bb709394:
To clarify: you are experiencing stuttering problems after you updated to the newest version of the YouTube app?
[Android Q&A, Help & Troubleshooting] tulik23:
Hi

i have bought my fiesta with a dvd console + GPS and BT

when i play the DVD on drive i can only ear the sound

is there any way to unlock it ?

(without touching the wires )

AR-PRIMA-BC6-U1-256-V1.76

D52F-1RH7-DH-E11V1.09

???
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] byte9:
So, I installed TWRP 2.7 on my GS4 via mobile terminal. My device had the radio updated to MLD from [MENTION=1224620]rockrat[/MENTION](which i thought was not effecting my recovery options how he extracted it) --upon updating to TWRP 2.7 i rebooted into recovery and got the "Software Not Supported by AT&T" locked bootloader message.

I have tried flashing .tar recoveries in Odin-- it fails auth

I have tried using mobile terminal to go back to older recoveries and all i end up with is the same not supported by AT&T.

Have i now fu#ked myself out of using a recovery besides Safestrap? I have a custom kernel on board, I have 4.4.2 and root is fine. I just _think_ from what I've read that I'm now trapped on a Galaxy with no recovery boat.

Crowd-- please say It ain't so
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Red_81:
I think you forgot to flash loki again. Unless your recovery auto-loki, I believe you have to flash loki every time you flash something in recovery.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ozziedog:
If your firmware is MDB or MDL check out the post by dees_troy "TWRP 2.6.0 Recovery" in the development section and read the last couple of pages. This may help you. Good luck.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] byte9:
Thanks guys, I figured it out. TWRP team a) doesn't have a gs4 b) forgot to f'n Loki the recovery. c)I had never in all my flashing known the recovery sector needed Loki, also I was stumped because In using terminal emulator I thought if was reverting to a previous build but for some reason it wasn't. d)Flashify came in and saved the day.
[General Questions and Answers] elvisamy:
i had found a cheater goophone website--goophone.cc, which couldn't support paypal payment, only supports credit card payment. besides, its' credit card payment page also couldn't support HTTPS, it is a cheater website which steal the informations of the customer credit card.
[General Questions and Answers] N'ayam Amarsh'e:
No Dude It's 100% Safe and it's the original goophone website.... Don't worry you can see the review

http://www.webutations.org/go/review/goophone.cc

...
[General Questions and Answers] malboroman:
goofhone.cc

the site is closed.bad place to shop...
[General Questions and Answers] knreddy:
Goophone I5S is not at all reliable

Obs on Goophone.cc phone Goophoner i5s

i) access to debugging is already provided

ii) Already Rooted

iii) Apk can be installed directly

iv) PdaNetA4150.exe installs adb drivers (If & when required)

v) very useful application "easy touch" got pre installed & but "back" is not working

vi) Others: I have recieved it in recycleable box instead of premimum box shown in website, headphones are supplied without box , mic cover little bit opened at joint.total cost $159 phone cost + $29 shipping to India, customes Rs 1039.55 (=$16.5 with lower side Billing of $71+shipping $20)

Problems:

i) Carrier issue (Sim detects Carrier) but no signal level as it can't be registered as the factory given IMIE no is not valid / black listed by India etc.

ii) Call volume level is very low at max volume point,

iii) very poor build quality of head phones

iv) speaker quacks at high volume,

v) camera low light quality is very poor

vi) camera auto focus makes mechanical sound

Vii) It is not catch carrier signal, while other phone shows full signal level (why unknown biggest problem) or atleast antenna is of low quality.

viii) Lot of work to be done to get Google play store / maps to work (as OS is highly cutomised & not from AOSP)

iX) only 1200mAmp battery against specified 1500 ma

x) Before sale they used to respond within 24 hrs, after reporting above problems they are not responding, i.e they do not honor their warranty.

x) By the time it rached me goophone.cc was blacklisted by google for almost one month

from the above all most all the parts are poor quality except metal body.

Unless experiment your money , do not purchase these unreliable chinese (not like proven chinese brands Lenovo or huawei etc)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] hasanin.xaidi:
Hello Friends, how you guys are doing...???

Hey i just wanted to know my AT&T S4 phone is unlocked and Rooted.... If i install any custom rom would it remains Carrier Unlocked?

Waiting for your kind responses... Thank you
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Yes, it'll remain unlocked

Sent from my SAMSUNG-SGH-I727
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] mdurvesh:
Hi,

Sorry but just wanted to confirm if I unlock my phone on 4.3 MK3 with RegionLockAway-v1.3.apk and go on 4.4 stock will it remain unlocked ?

Thanks
[Android Q&A, Help & Troubleshooting] GlebVoronin:
Hi there, i have a problem after Google+ update. When i'm trying to set a contact profile picture i have an error "Unable to save photo edits". And then it seems that app loops, if i push back and choose other photo, i see previous one and same error. If i uninstall Google+ Updates it works fine, but after update it brakes again

Problem with: Nexus 5, Nexus 7 LTE, Motorola Moto G GPE
[Android Q&A, Help & Troubleshooting] Primokorn:
Have a look at the bottom of this thread: http://xdaforums.com/showthread.php?t=2568431
[Android Q&A, Help & Troubleshooting] GlebVoronin:
There is no gallery app on moto g gpe
[8125, K-JAM, P4300, MDA Vario Software Upgrading] garymeg:
:idea: Is there any chance of somebody giving a step by step tutorial of how to create your own custom rom installer

Like how to build say o2uk extended rom with TMOusa windows 2.24 rom and say TMOuk radio rom? (example) :idea:

Please if so could you post any/all software neaded to create this rom installer?

Many thanks

:?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] moghisi101:
Summiter? Could you help us on this? I would like to customise the extended ROM of my nbf file before flashing.

Thanks
[8125, K-JAM, P4300, MDA Vario Software Upgrading] summiter:
Everything you need to know is held within the various forums here. This isn't meant to be a non-answer, it's just that the resources are here (it's how I learned), and you have to be willing to expend the effort involved in finding and understanding.

I get several PMs a day from folks asking for a tutorial or lessons and whatnot. My response is always the same - read the forums. My intention is not to deflect the requests or hoard useful information. If you don't take the time to fully understand how all the pieces work, you risk seriously wrecking your device, and others if you share your custom ROMs.

That said, here's a simplified overview of the process:

-Extract the various ROM components from the nk.nbf using the typhoon tool version 5

-Modify the extended ROM component, which is a FAT filesystem image, using Winimage or similar

-If desired, extract the OS portion of ROM using mamaich's imgfs tools, and modify. When finished, use the same tools to update the OS portion of the ROM

-Pack everything back up with nb2nbf

Inside an nk.nbf is 7 components:

Extended ROM

OS

IPL (part of bootloader)

SPL (part of bootloader)

Splash screen

HTC Logo (normally uses the same image as the splash)

GSM radio code
[8125, K-JAM, P4300, MDA Vario Software Upgrading] ikkoku:
re: splash screen, is it possible to change after flashing? Summiter, I love your ROMs but the only thing that bothers me is the Cingular splash screen. Everything else is perfect...
[8125, K-JAM, P4300, MDA Vario Software Upgrading] kyphur:
Summiter, could you please post the nb2nbf tool? I have googled and searhed xda to no avail.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] hellacopterous:
the nk2nbf tool is on the ftp, at least that's where i got it.

also, in order to get the actual rom form the RUU (rom update utility), just change the extension to .zip and let winrar open it. from there you can grab the actual rom to pick apart
[8125, K-JAM, P4300, MDA Vario Software Upgrading] kyphur:
Where? I have been looking and can't seem to find it. That is the only tool I am missing.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] raven2000:
What is the format of HTC Logo and Splash Screen? I mean is it jpg file or what?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] summiter:
Look in the Tornado directory.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] moghisi101:
Hey Summiter. Using those typhoon tools I get errors when trying to reencode the nbf. It seems the headers or something are different? What am I doing wrong?

If you would be so kind to tell us what to search for in the forums that would be greatly appreciated.

Thanks
[8125, K-JAM, P4300, MDA Vario Software Upgrading] garymeg:
Any Chance of posting links to the programs neaded i can't seem to find any of them
[8125, K-JAM, P4300, MDA Vario Software Upgrading] moghisi101:
they are all in the Wiki under Typhoon section

what we need is a link to the thread that tells you how to use them. I can't find it
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cybiker123:
files needed

ftp://wiki.xda-developers.com/Wizard/DumpROM/

the tools needed are right here in the zip file create_nknbf.zip and it even has fairly simple instructions on how to use it and also when running the typho tool you must do it in a command prompt window although if i need to tell you this then you probably shouldn't be changing your rom and messing with the components inside of it anyway
[8125, K-JAM, P4300, MDA Vario Software Upgrading] cybiker123:
hey summiter quick question i know how to mod everything i can see for the most part but how do you change a registry value previous to installation do you simply create a cab file and add it to the extended rom changing the value and if so what do you use to create the cab file

thanx,

Craig
[8125, K-JAM, P4300, MDA Vario Software Upgrading] moghisi101:
yea, just create the CAB and add to extended ROM. I have a question also. When re-encoding your nbf, there are modules for gsm, os, spl, ipl. Where are commands for extended ROM, htc logo, and splash?

I also get the following error when re-encoding:

read 00000800 for ipl from ipl.nb

no 1.00 at 0xc in IPL image

read 000c0000 for spl from spl.nb

spl image: 00180000 bytes

no BOOTLOAD at 0x2004 in SPL image

I am worried that if I use these SPL.nb and IPL.nb with nb2nbf that I will destroy the bootloader

Any Help?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] summiter:
Using a cab file to modify the reg is the easiest method. You can get into modifying the .hv files in the OS ROM but that gets pretty invovled.