yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Q&A, Help & Troubleshooting] rain91x:
Hi

I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.

Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...

These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...

I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)

Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?

edit: http://xdaforums.com/showthread.php?p=13754274#post13754274

or

http://xdaforums.com/showthread.php?t=1035139
[Atrix 4G Q&A, Help & Troubleshooting] Alonleibo:
looks promising... did you try it?

I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".

should I just except the fact that I have to get a new phone?

should I send it to Motorola?
[Atrix 4G Q&A, Help & Troubleshooting] rain91x:
I try it later, but i dont know now SD card. I hope, that it is a correctable bug.

edit: i tryd it, but still not good. Other solutions?
[Atrix 4G Q&A, Help & Troubleshooting] thejamoz:
I have the same problem (wifi error, bt does not open). I guess it is a hardware problem but when I installed TopSmart rom (coming from Neutrino) they worked for 10 minutes then they crashed again. If it is a software problem (but i dont think so) there must be the answer that everyone's looking for. I hope it ends up as a software problem.

Sent from my Motorola Atrix 4G
[Atrix 4G Q&A, Help & Troubleshooting] MdX MaxX:
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).

This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.

I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
[Atrix 4G Q&A, Help & Troubleshooting] rain91x:
It is frequent bug on Android phones. (wifi - error)

https://www.google.hu/#hl=hu&gs_nf=1&tok=EBl1OHx7E49rfa9s8zPj_A&cp=13&gs_id=1f&xhr=t&q=android+wifi+error&pf=p&output=search&sclient=psy-ab&oq=android+wifi+&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=aee7b1a090091e6a&biw=1680&bih=949
[Atrix 4G Q&A, Help & Troubleshooting] Alonleibo:
I did turn it off... eventually.

but my phone still crashes... at the same frequency...

*added alogcat files of 2 of the crashes... if anybody can understand it... :)
[Samsung Epic 4G Touch] slick_rick:
Epic Touch Blog: Temporary Stock FF18 from emmc

Utility for CM9 Epic Touch

This is a temporary ROM that boots Samsung's Ice Cream Sandwich FF18 firmware entirely from emmc without making any changes to the ROM currently installed on your phone. When you reboot, you return to recovery where you can re-flash the ROM to return to CM9. This temporary ROM is useful for several purposes.

Update Profile

Update PRL

Sprint Activation

Dial codes and diagnostic mode

QBKing77's video is on the EL29 temp boot but instructions should be almost exactly the same except just use the included kernel/recovery that comes with the CM9 rom instead of the directbootCWM kernel!

[YOUTUBE]Rdx-kIxpitg[/YOUTUBE]​

Thanks to nubecoder, chris41g, noobnl and mkasick for making this possible!
[Samsung Epic 4G Touch] Dulanic:
Nice. I use the old version all the time.
[Samsung Epic 4G Touch] kozmo2k4:
I've tried this twice today, downloaded all files, checked md5's, unzipped folder, copied files and folder to Internal sdcard, followed Qbking77's video to the "T" and just getting a reboot to CMR 5.0.2.7, never to the temp ROM.

I'm currently on AOSP JellyBean, was just trying to get GPS fixed; came from BlueKuban.

Gotta run out, will re-do the whole thing tonight, again.... Third time is a charm?
[Samsung Epic 4G Touch] slick_rick:
Only for CM9 at the moment.
[Samsung Epic 4G Touch] times_infinity:
AFAIK, sbrissen's kernel doesn't have kexec support.
[Samsung Epic 4G Touch] kozmo2k4:
Would the other, older version (EL29) work with AOSP?
[Samsung Epic 4G Touch] coiledwire:
Any advantage to using this ff18 temp rom versus the older el29 version?

Edit: if I use the older direct boot cmw and el29 temp rom, then I can use it on both cm9 and jb/cm10?

Sent from my SPH-D710
[Samsung Epic 4G Touch] john9:
nice work will try .Thanks
[Samsung Epic 4G Touch] revamper:
Is it possible to get root access on this?
[Samsung Epic 4G Touch] kozmo2k4:
Just wanted to update : the older version, the EL29 and directboot v3 does work with AOSP Jelly Bean!

Sent from JellyBean gTablet using Tapatalk 2
[Samsung Epic 4G Touch] slick_rick:
Root access on the temp ROM?
[Samsung Epic 4G Touch] calisro:
el29 works for me but the newer one doesn't reboot into the temp rom like the older one. when I run the bootzip it runs but never causes cwm to reboot to the zimage.... I'm on CM9 NIGHTLY
[Samsung Epic 4G Touch] calisro:
anyone on a cm nightly got ff18 to work??? the old one works but not the new one.
[Samsung Epic 4G Touch] slick_rick:
Hmm that's strange. The recent nightlies should have a kexec enabled recovery/kernel.
[Samsung Epic 4G Touch] calisro:
doesnt seem to be the rom. i can boot el29 just fine still.
[Samsung Epic 4G Touch] slick_rick:
Which nightly are you on?
[Samsung Epic 4G Touch] calisro:
shabby's 8-30 release
[Samsung Epic 4G Touch] slick_rick:
They upgrading to this ROM

http://chris41g.devphone.org/EpicTouch/CM9/cm-9-20120829-EXPERIMENTAL-d710-VroomVroom.zip and then try the temp boot
[Samsung Epic 4G Touch] ColdCircuitCash:
Can anyone here confirm that the FF18 temp rom can be used with CM10/AOSP JB? Or do I HAVE to use the el29 temp rom?

Sub question...would I have to flash to CM9 to use either?
[Samsung Epic 4G Touch] KCs2k:
FF18 did not work for me on the Jelly Bean AOSP A5 build. The EL29 and direct CWM boot did.
[Samsung Epic 4G Touch] calisro:
Ok... This finally worked for me but you MUST use CWM 6.* rather than CMW 5.*. If you are on CM9 use its own default recovery and it will work just fine.
[Samsung Epic 4G Touch] dblock3nine:
FF18 one didn't work for me, I had to use the EL29 version but that one worked like a charm. Thanks for the great work sir
[Samsung Epic 4G Touch] adma84:
On latest beta 1 (stock) and this also won't work for me. Bummer!
[Samsung Epic 4G Touch] slick_rick:
Really? I just tried it and it worked perfectly fine. Hmmm.
[Samsung Epic 4G Touch] calisro:
didn't work for me on beta 1. I remembr chris saying kexec needed to be fixed on latest kernel.
[Samsung Epic 4G Touch] rocket321:
Just tried on Beta1 with FF18 - not working here either - never reboots. Tried it multiple times including re-loading beta1 first and rebooting recovery.

I think I might have had the files in /sdcard/multiboot/multiboot - so I can't say for sure it wasn't user error in my case.
[Samsung Epic 4G Touch] Mattix724:
I also could not get it to boot with the beta.

What I did to try booting.

Currently running CM10

Mobile Odin to the CWM5 EL29 direct boot

Flashed CM9 beta 1

Flashed FF18.zip from the multiboot folder

Install from sdcard was complete

Did not reboot into temp FF18.
[Samsung Epic 4G Touch] calisro:
wait for chris to fix kexec or use el29 temp rom instead for now.
[Samsung Epic 4G Touch] xda-todd:
Failure now with both EL29 and FF18

Strange thing. I'm on beta 1 and am unable to use either version of multiboot (el29 or ff18), whereas before I could.

With EL29, I get an error as follows:

-- Installing: /sdcard/multiboot/EL29/boot_EL29.zip

Finding update package...

Opening update package...

Installing update...

E:Error in /sdcard/multiboot/EL29/boot_EL29.zip (Status 0)

Installation aborted.​

With FF18, it seems to install fine but never reboots. Same problem that others are reporting.

Note that I've used the EL29 method many times in the past with no problems. I tried recopying the multiboot folder from the TAR again just in case it had gotten corrupted, but no success.

After attempting either version, the phone reboots into beta 1 without any problem.
[Samsung Epic 4G Touch] calisro:
are you using mobile odin (or pc odin) to flash the directbootcwm then rebooting into the flashed cwm before trying to 'boot_EL29.zip'?
[Samsung Epic 4G Touch] slick_rick:
If you want to use this temp boot, flash the directbootCWM and then flash the tempff18 rom. Once done with temp rom, reboot back to recovery and just re flash CM9 rom. Do this for now til chris41g can make a quick stand alone kexec kernel.
[Samsung Epic 4G Touch] calisro:
I do not believe the directbootCWM will boot ff18 at all. Users will need to use directbootCWM and EL29 until kexec kernel is addressed.
[Samsung Epic 4G Touch] aleph23:
Just fyi, I booted into el29 temp yesterday and had to flash one of Chris's kernels and reboot recovery before i could flash back to cm. So you may want to make sure you have a kernel you're able to flash before trying el29 again just in case you get the same status seven error from the cm flash.

I believe this was caused by cwm trying to verify device name.
[Samsung Epic 4G Touch] slick_rick:
Re flashing your CM9 rom installs a new kernel.
[Samsung Epic 4G Touch] TerryMathews:
Yes, it does. The update script in cm9 beta 1 won't assert properly on the cwm included in the directboot kernel.

Also, is running with no sd card going to be fixed?
[Samsung Epic 4G Touch] calisro:
you wouldn't want your sdcard yo mount. um corruption? ;) its meant for temporary use to update prl, profile, etc
[Samsung Epic 4G Touch] lunchboxVA:
is there one of these temporary stock boots for cm10?
[Samsung Epic 4G Touch] calisro:
same link I posted above. follow the directions.
[Samsung Epic 4G Touch] groovedexter:
I might be doing something wrong, but from what I can tell this doesn't work with CM9 B1 following the directions in the blog post. http://e4gtcm.blogspot.com/2012/08/temporary-stock-ff18-from-emmc.html

In CWM it just gives "install from sdcard complete" when trying to flash multiboot > FF18 > boot_FF18.zip.

I then used ODIN to flash back to CWM Directboot and it gave the same "install from sdcard complete."

I downloaded the EL29 temporary stock rom and it worked well, but I'm having issues with it updating the PRL in CDMA DFS, going to try QPST and see how it goes.

Edit: Tried a new PRL file and it worked wonders in DFS.
[Samsung Epic 4G Touch] carole6m:
Worked on the latest nightly build. Couldn't get it to work on Beta1 though.
[Samsung Epic 4G Touch] CollinsB:
Ics modem working?

What if I am on a Jellybean AOSP rom (dirty unicorn) with an FL24 modem. and i wanted to use this to update prl/profile? would this work? I would think the prl update would brick﻿ it because I am on FL24 modem while on stock el29, would it?
[Samsung Epic 4G Touch] bilgerryan:
Probably not a good idea, you should keep a nandroid of TouchWiz on your sd.
[Samsung Epic 4G Touch] CollinsB:
thanks for the reply! though if i decide to go to AOSP, how would i restore my nandriod backup so that i can update PRL/Profile, dont i need to be on the same TW kernal (agat) that i backed up with? And you cant be on AOSP with a TW kernel...
[Samsung Epic 4G Touch] bilgerryan:
Use Garwynn's v0.4.1 kernel to make the Backup it uses the same recovery as AOSP, that's how I always did it, haven't been on AOSP in a little bit.
[Samsung Epic 4G Touch] CollinsB:
Oh thats really good to know, thanks :)

though it occurred to me that I am already on a jellybean GB27 rom, so i couldnt nandriod restore and update PRL/Profile because using AOSP i will have to be on an ICS modem anyway. I guess i just need to odin back to a stock ics rom, and flash dirty unicorn from there so i wont have to update prl/profile after i flash, and will have working data.

thanks!
[Samsung Epic 4G Touch] bilgerryan:
No, flash the ICS Modem and update PRL/Profile, you won't have data but you can still update them. Then you restore your AOSP nandroid and done.
[Samsung Epic 4G Touch] CollinsB:
Oh... r u sure that updating prl/profile while on a TW jellybean rom with a ICS modem is safe? I know that when i first flashed jellyverse (v.2.0) I was still on a ICS modem (the JB modem aborted.) But i tried updating PRl/profile with ICS modem and I softbricked. I had to odin to restore.

Is this because i was on an ICS modem? Or maybe becuase i didnt have a custom recovery at the time or could it just have been the rom? (I just tried updating PRL/profile while on JB modem (on jellyverse 3.0) and it worked fine, so if it was the rom, i guess it had been fixed.)

(sorry to be a pain)
[Samsung Epic 4G Touch] bilgerryan:
I've done it tons of times, stock and custom kernels

Team Rejectz
[Samsung Epic 4G Touch] CollinsB:
great, thanks so much! when I decided to flash dirty unicorn ill try this out. Wost case scenario, the prl/profile update softbricks it and i will just have to nandrestore or odin to recover. :)
[Thunderbolt General] recDNA:
I've been trying to follow the liquid densensed 36 thread over in android development but there is quite a bit of info there to digest. I am very grateful to jester for all the work he put into this rom so I don't want to write anything in the thread that could be construed as disrespectful to his work....so I decided to post this thread in general tbolt.

Could someone post what does NOT work in this rom?

If there is a fix for it could you post that too?

I realize most if not all flaws are due to the original leak having bugs so I'm not knocking anybody - just the opposite....but whatever the reason could you post the bugs here? That way users can make an informed choice about whether to flash. I know the prevailing sentiment is just nandroid then try it but some of us really like to know up front.

Thanks for participating....and triple thanks to jester for all his work!
[Thunderbolt General] disconnecktie:
Jesters version is the only one I could get to boot at all. All of the others fc my phone to death. I've ran it since he posted it and I haven't had any issues with it all. The worst thing about it is the battery life and the lag. Other than that its not to shabby.
[Thunderbolt General] recDNA:
So every single ics feature works?
[Thunderbolt General] disconnecktie:
As far as I can tell. The only thing I haven't tested is Bluetooth.
[Thunderbolt General] Dodouble:
Likewise I've tried everything but Bluetooth.
[Thunderbolt General] bustedukulele:
Bluetooth doesn't work. It reboots the phone. I've also had problems with WiFi tethering. It's a very solid ROM though. But as you've said the problems from the original leak still exist. Mostly the poor battery life bothers people.

But I'm sure jester is working on this thing. Dude is a beast.
[Thunderbolt General] recDNA:
Ah. Bluetooth is sometimg I do need. That helps.

Thanks!
[Thunderbolt General] zx12dak:
Bluetooth works with the .19 radio... I have no WiFi tethering and when you plug into the computer its a pita to get it to hook up as disk drive. Other then that it all works pretty darn well.
[Thunderbolt General] trapperjohn:
Hi,

Just want to clear up some things.

I experienced the problem with bluetooth rebooting the phone and through testing if you install the .19 radio, then the rebooting stops. Since I did this no more reboots. Also I use the bluetooth and it does work correctly and pairs quickly also.

I will also mention that when I installed the new leak that came out a few days ago that it would cause random reboots but with the radio I mentioned no reboot at all.

As to the lag and battery life I also was surprised how bad each was until..... Yes there is a fix....

There is a script that you run and then reboot the phone and since then lag is reduced drastically and battery life is much better than before of course it's as good as you will get till we get custom kernels (shout out to imoseyon!).

I hope this helps you out if so hit thanks....

Thanks,

Bryan
[Thunderbolt General] disconnecktie:
IMO may not make a kernel for us. We will see when source drops for the kernel.
[Thunderbolt General] recDNA:
Bryan, let me say again at risk of repeating my op. I am VERY GRATEFUL to Jester and give him props galore for all the development he has been doing here. I don't think any developer has contributed as much to tbolt users for a long, long time.

This thread is merely meant to clarify what works, what doesn't work, and any potential fixes. His thread has grown so long and so many issues have been discussed it is hard to filter out the most critical info. I hope this thread helps with that.
[Thunderbolt General] trapperjohn:
Hi,

Sorry that line about spjester was not directed at you sorry about that.

I do appreciate this thread. I was just mentioning him since I just feel he hasn't gotten enough recognition.

I edited the post.

Again sorry for the confusion.

I hope the post did help you though.

Thanks,

Bryan
[Thunderbolt General] recDNA:
Oh ya, your post was great and I thanked you right away. I just wanted to be sure everyone knew this wasn't a trash em thread....just the opposite!
[Thunderbolt General] pryorda:
...

Exchange Syncing isnt working, Batteryl life is getting worse.
[Thunderbolt General] isaidso:
I assume you are referring to the kernelizer? Ive been searching for the specifics for this but only know that I need to downgrade busybox and then run the script. What script should I run? Thanks for the help!
[Thunderbolt General] donnyp1:
Bluetooth works pairing with my lg soundbar
[Thunderbolt General] AZSALUKI:
There's actually an even more recent radio. Its here in the development section of the tbolt forms. I think the thread is called "ics combo radio." One radio was fixing Bluetooth but giving people wifi issues and another radio was fixing wifi but giving reboots with bt. This radio is the .19 cdma radio, along with the leaked ICS radio for lte. I'm on it now and it fixed my data issue. With every other radio I tried, I had to toggle off/on data whenever I switched from 3g to 4g. I also had a couple revolts here and there. Fingers crossed, but so far so good with the "combo radio."
[Thunderbolt General] k9cop:
I was running kernel 1.4 for some reason. Flashing this rom brought back my gps and I haven't had any data drop so far. Liquid ftw.
[Thunderbolt General] eldiablo2us:
This from is the best one based on the leak. I still get data drops. So maybe I'll try the combo radio. People have been saying that it fixes their data drops.
[HTC One X] max-halmat:
hey, i bought the phone one month ago but the Proximity Sensor is not working at home it only works under the sun , pleas help to fix it

the screen is not gone black during call at home and the red sensor is still working after the call
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mitchellvii:
Just attempted to sync my S-Notes with Evernote. It says they have synced correctly.

However, when I open the Evernote app nothing is showing up and there is a message at the bottom left stating that syncing has failed. I tried adding a folder directly to Evernote from within the app and it crashed.

Any ideas?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mitchellvii:
Hmmm, ok well the syncing is showing up on my laptop version of Evernote but not my tablet version. odd.

Also, apparently it is syncing them as .snb files which Evernote apparently cannot display. What am doing wrong here? Why is it exporting my S-Notes to Evernote in an unreadable format?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] AndroidAble:
I would consider dropping OneNote and moving to Evernote if you could get me the anser to that. I tried the same thing, but it does me no good to have my notes synced to Evernote if I cannot open them on my PC and see them on my evernote app on the tablet.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mitchellvii:
From what I have been reading online S-Notes created using the Note appear perfectly within Evernote. I am assuming those notes have the same file format and extension. Weird wonder what the issue is.

I can't seem to find a thing online discussing the SGN10 and Evernote.

** Same thing with Google Docs. It doesn't recognize the file extension and can't display the content.

I am trying to figure out why Samsung wants us to sync our notes to two services which cannot read the format?????
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mitchellvii:
No one else is having Evernote issues? As far as I can tell Evernote doesn't recognize the snb file extension and won't display s notes content. This is very odd since s note recommends syncing with something that has no idea what it is.

I've seen videos of people syncing their Note with Evernote and it works fine.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jeggen:
I'm having the same issue. Just testing out the Galaxy Note 10.1 to see how it fits into my workflow and wondering if I can happily replace the keyboard/shell design of my Transformer. Part of that is notes sync which I was trilled to see but I cannot open them in Evernote. Anyone know how to open one of these snb files in Evernote?
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mitchellvii:
Unfortunately not possible. You can store them in Evernote and use that to sync with other devices which support .snb but you cannot view them. Have no idea why Samsung chose the very obscure .snb standard for Snotes. This makes Dropbox a better solution because youc an sync using DropSync for the Market.

My guess is that Samsung is forching us to own other Samsung devices which can read their very specialized .snb files.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jeggen:
Bummer. Are there any S-pen enabled note applications that can sync to Evernote (or via Dropsync) and open on the PC? I know I can always export them, but would prefer a solution that can regularly update notes as I write them for easy reference rather than exporting each time I make changes/additions.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] AndroidAble:
I would also like that solution.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] pb1379:
Sync: Had that for a day, too, on both the Talley and phone, looks like something was broken somewhere. Works again now.

snb: these are basically zip files with JPEG pictures for each page and some additional info in xml files. Rename to .zip and open as usual. Of course, this doesn't give you notebooks, but the info is there, and you could even make pdfs of them.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] mitchellvii:
If you are going to do all that you may as well just save .PDF copies from Snotes.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] pb1379:
Lol. True. Wasn't thought as a work solution, but a disaster recovery, e.g. in case of a lost phone/tablet. You can then still get at your notes, until you have snote available again, without having to export each note after each change...

Sent from my XT910 usiI ng Tapatalk 2
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] RbbCHan:
as disaster backup i recommend Samsung Kies Smemo and Snote backup. Works perfectly and is fully restorable if you need it.

I do this once a week.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] samuelong87:
I guess that's the same case for Asus and their supernote. It's also in snb format and I tried copying the file into my Note10.1. It apparently is encrypted or something. Requires a password :(

the whole GALAXY to NOTE about...counting down from 10 to 1.
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] jchammerpants:
I have been getting the 'sync failed' message since at least yesterday (hadn't paid attention to it before then). Was there a fix for that, or did it work itself out?

JC