yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] dhruvraj:
No I think notepad++ does that by default. What you need to see is that it didnt give any assert error, tried to install for a while .. and then gave the error : installation aborted

Secondly, I'm getting errors in every single ROM out here. Now trying the GB rom .. will post the results, and thanks for assisting so far mate

Dhruv
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] dhruvraj:
Update! Cyanogenmod 7.2 installed OK. So gingerbread is installing

Is it because of RecoverX then? Because while installing RecoverX it asks which version of xperia mini do you want - and I use android 2.3.4 - could it be the recovery not letting JB or ICS install then? Its 5.0.2.8 or something the one that I have

Pl let me know what to do next. cheers
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] pitchblack5691:
Notepad doesn't change eol to Unix by default. After installing a prerooted kernel you don't have to use recovery x . after all that's the point in a preroot kernel! It comes with root and CWM recovery in built! Now what? Start flashing Roms, kernels and start exploring the infinite possibilities of android! :thumbup:

and hit the thanks button, it's more appreciated than typing thanks :D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
For ICS or JB you don't need recoverx, if you use a custom kernel you can just flash the kernel and it has cwm inbuilt.

1. Just push the FXP cm10 zip for your device to sd card, flash the boot.img,

2. boot in cwm,

3. backup,

4. wipe data/factory reset,

5. install zip from sd card,

6. (if you want install the google apps=gapps) :good:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] dhruvraj:
Problem was with CWM ... once I installed a GB custom ROM, the recovery was flashed to 6.0 something automatically

Every single ROM I tried to install after has worked flawlessly.

I have an xperia Mini, and it just doesnt work though, so I'm opening another thread on the overheating issue (which doesnt get solved no matter what you do)

thanks
[HTC Sensation] mama_mia:
Hi,

I've sent my HTC Sensation to warranty after returning the phone the its original state.

HTC sent back the device saying that the bootloader is unlocked and the device is not covered with warranty because of that.

I checked the bootloader and it sais "Unlocked", but I'm shore it was locked when I give them the phone.

I think they figured that the booloader was unlocked before and they unlocked again to prove it.

What I want to know is if there is some way that I can know the date when the booloader was installed, like the day when the files were created on the phone memory or something like that.

Just to prove them that were them who unlocked the bootloader.

Does someone can help me on that??

HTC wants me to pay 170€, which is almost the value of whole phone, just to repair the front facing camera.

I hope someone can help me...

Thank you!!
[HTC Sensation] realsis:
Man, I wish I could help! I just wanted to say I think that's awful that they unlocked the bootloader! Especially when you knew good and well you locked it before! I would try to dispute it and write a letter, although it probably wouldn't do any good. That's so dirty on there part! It makes me sick the things they get away with! Hopefully some one knows of a way to find out when it was done. This way you can catch them in there B.S. I wish you luck and hopefully you can find the date or something to prove them wrong! Best wishes

Sent from my HTC Sensation
[HTC Sensation] mama_mia:
Thank you!

I hope someone knows how to do it.

I already sent letters to Vodafone, national communications authority and to the department of quality.

I'm waiting now...
[Galaxy S I9000 Q&A, Help & Troubleshooting] sime973:
After instaling ClockworkMod v6.0.1.3, I can't chose any item with Home button, I can't reboot system, I have to replace the batery to reboot the phone, and phone is booting again in ClockworkMod.

Any solution or this the end of my phone (gt-i 9001)

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] xsenman:
Flash CWM 6.0.1.4 with AriesVe.ops on odin 4.43 and if still cannot boot Flash i9001 Bootloader with AriesVe.ops, download in My Android Collections
[Nexus 7 Q&A, Help & Troubleshooting] digixmax:
According to this IBT Blog, restoring to stock ROM is

mandatory

for receiving the upcoming OTA update to 4.2.

Does any one know if this is true, as the last OTA update to 4.1.2 automatically launched and completed just fine on my N7 in its rooted state?
[Nexus 7 Q&A, Help & Troubleshooting] nyijedi:
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
[Nexus 7 Q&A, Help & Troubleshooting] Bcroc:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?

If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good :)
[Nexus 7 Q&A, Help & Troubleshooting] nyijedi:
I haven't messed around with modifying the UI, but I have replaced and disabled system apps in the past, and that stops the OTA from installing (it will download the OTA, but the install will fail). I suspect it's possible that the same thing will happen with a modified UI, but I'm not 100% sure. What is the process for modifying the UI? Did you replace certain files? If so, hopefully you saved the original versions and can revert back to the originals.
[Nexus 7 Q&A, Help & Troubleshooting] ontoptherock:
Can you keep us updated here if you decide to try and install the OTA update while in tablet UI? i would be interested as well if it will update
[Nexus 7 Q&A, Help & Troubleshooting] nba1341:
If all you did was change the dpi then yes it wont matter your build.prop is going to be overwritten anyways
[Nexus 7 Q&A, Help & Troubleshooting] Bcroc:
Of course, but I think I will wait the update before doing anything, that's just more convenient:)

---------- Post added at 07:16 AM ---------- Previous post was at 07:15 AM ----------

No, I don't wan to replace anything, only modify the build.prop to have a different density setting.
[Nexus 7 Q&A, Help & Troubleshooting] digixmax:
I do know the difference between Stock ROM vs. Stock ROM + Rooted -- but I had just read the IBT blog too fast and plus I implicitly assume that folks who use custom ROM would just wait until their particular custom ROM rolls onto 4.2 base, to realize that folks with custom ROM is the target audience of the IBT blog.
[Nexus 7 Q&A, Help & Troubleshooting] Heisenberg420:
So its safe to update via ota if your on stock rooted? Ive seen people saying its fine but on my old atrix I was warned it would brick my device.
[Nexus 7 Q&A, Help & Troubleshooting] digixmax:
My N7 went through the last update just fine (other than getting un-rooted).
[Motorola Droid Bionic] briankey:
Well I did it again. I emailed moto tech support about boot loader unlocking. This time, Maureen tells me Motorola is in the process of unlocking Motorola devices and the list is growing. So one of these days the bionic may be on it.
[Motorola Droid Bionic] Stories:
The Moto devices that are developer's editions have a bootloader unlock option. The rest of us on consumer devices basically have no shot, particularly on Verizon. Maybe if we were on another carrier (eg. Verizon's GS3 is locked whereas the other carriers' GS3 is not).
[Motorola Droid Bionic] projektorboy:
I'd consider my odds of winning the lottery better than Moto finally unlocking the OMAP4430 siblings.

I FXZ'd my Bionic to 6.7.246 and then tried the fastboot oem get_unlock_data command on it, and the bootloader didn't understand the command, unfortunately.

I'm going to check again when the Bionic gets JB.
[Motorola Droid Bionic] SubVirus:
yeah i find it hard to believe they're just going to give us an open sourced version of the OEM... From what i understand from the first few months with my Bionic. The part we need is not software; if you look on the back of your bionic with the back cover off, you'll see a number of fuses. These are what separate developer phones from normal ones. We'd have to take it to Verizon to have them flash the unlock tool. So i hope this isn't just a partial unlock disguised as a software patch to allow a few more abilities with our bootloaders. This is just my understanding of reading 4 or 5 forums on bootloader unlocks and the problems people have run into. The fuses prevent certain areas from being flashed. This is just another part of my skepticism. not to mention MOT has not exactly been to their word anyways...

I agree with your final statement. maybe during the JB upgrade we'll see an unlock process. one can only hope.
[Samsung Galaxy Nexus] Syriochan:
Hi there, i opened this thread because i'm desperately trying to find a ROM/kernel which meets my needs.

I'm looking for:

Stability; Bugfree; Battery; Audio; these are my primary objectives (i'd like to have some customization option but i don't care as long as i have those)

I've tried so far:

Stock ROM with Franco.Kernel + LOUDERmod: PRO: Fantastic Battery

BAD: It had some bugs (WiFi disconnecting and then stuck into a loop searching for AP reboot needed) and the volume did not increase; So i flashed another rom right away.

Minco v4: PRO: Fantastic Battery life, fantastic audio

BAD: Same bug as the franco.Kernel, audio stop working while listen to music or youtube or other stuff while the 3,5mm jack is connected (tested on another galaxy nexus with different headphones same problem)

Codename Android: PRO: Fantastic Battery life, nice audio, quite stable, nice features.

BAD: Same bug on WiFi as the previous ones, after 2 weeks apps were crashing randomly so i got sick of the WiFi problem and flashed another rom;

Paranoid Android: PRO: Nice Battery life, nice audio, stable, very good features;

BAD: First ROM without the damned WiFi bug, a nice rom indeed. There are some bugs though and the "Per APP color" System slowed my nexus a lot. I kept it 'till a week ago when i flashed a cyano nightly

Cyanogen MOD: PRO: nice audio, stable, bug free, so much features that i'm still discovering things after a week.

BAD: Battery life. I need it for work.

I need some advices. I need a ROM (or the stock with a kernel) that i can keep for long times... the stock rom is nice, but battery life and audio suck.
[Samsung Galaxy Nexus] t1.8matt:
I've had little to no problems with Air Kernel Weeklys, Glados v2.1 is also a very good kernel. I've had problems with Franco, Zen Kernel, Tuna and Nyan. Air Kernel is my daily driver, gonna give Ink a try. No roms are trouble free, I'm on a VZW Nexus and have had good luck with Alien rom, Factory 2.2 and now Atom.
[Samsung Galaxy Nexus] Syriochan:
Thanks for the advices, i think INK will be my first try because i'm italian myself, if i get any problems i'll update this post with my experience :D
[Samsung Galaxy Nexus] t1.8matt:
Yeah, I tried ink last night with atom ROM and it didn't boot.
[Samsung Galaxy Nexus] rickbosch:
Team EOS.

Flash the latest from here http://goo.im/devs/teameos/roms/eos3/nightlies/maguro/ and Gapps. Best experience I've had. it's unique, and smooth as you like. I get a whole day's normal use out of the battery as well (on 3G during the day at work).
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] Dark-Master:
Hello XDA

It's been a while living with this problem on my 7.7. The first time it occurs. It just snapped and never turn on no matter what I did. This included hold the power buttons with or without the two buttons combination. Leave it being charged and do it again. Leave it alone for an hour and try again. There was no luck. Within hours, I try turning my 7.7 on again. KABOOM!!! the splash screen got its greetings on me. :D

That was like 2 months ago. But that's just when all these things started. Now I cannot restart my Tab. When I choose to restart, it will just turn off. And the same behavior comes and greets me again. This is so frustrating. :rolleyes: I'm getting a grip now. I plugged my wall charger in and I can see the charging sign on my 7.7"(it is not being charged sometimes, no response at all). And it won't just start!!! I tried all combinations available. It will just turn itself off and show me the charging sign again! And yeah... sometimes it doesn't respond at all. Have to wait like 5 to 10 minutes to get a charging sign to show up. And with some of luck, sometimes it just starts! LOL And this is how I'm using my Tab now. Just wait for my lucks and turn it on again!

This happens to me every time I restart my 7.7. I tried flash many stock ROMs with Odin, tried some custom ROMs(YES, I have to try all those methods I mentioned above every time I restart within the progress of flashing the ROMS). No LUCK. This still is haunting me. I don't know what to do anymore. -___________-

Could it be a hardware failure? Can I try something more myself? Should I just hand it over to Samsung?

:eek:

Thank you,

Putthabut N.
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] edan1979:
you better got for RMA... i think that might be a hardware failure...
[Galaxy Tab 7.7 Q&A, Help & Troubleshooting] Dark-Master:
It's still under my 1 year warranty time....:good:
[Galaxy S III Q&A, Help & Troubleshooting] snoopyhb2:
I have had this phone since August. when the phone had ICS I rooted it. Recently I upgraded to Jelly Bean and everything was working fine Since Friday it went dead. the only thing that works is download mode. I can't even get the phone to turn on.

Can someone help with this issue???
[Galaxy S III Q&A, Help & Troubleshooting] monil.verma:
Your phone is probably bricked. There are many tutorials on how to unbrick your phone. You can follow them.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Download mode and flash stock rom via Odin .

Or return to a service centre .

jje
[Kindle Fire Q&A, Help & Troubleshooting] mpbrown18:
I have a friend that has a kindle with an invalid serial number, if I planned to root and install jellybean would this cause issues with the play store?

Or is it even possible?
[Kindle Fire Q&A, Help & Troubleshooting] Ixthusdan:
The serial number is only important to Amazon. Play store should be fine.
[T-Mobile, Samsung Galaxy SIII] liljoka166:
i have looked all over xda and i can not find a answer im hopeing my xda family can help, i know about flashing have done it for years, i have the gs3 t999 from tmobile and i live in a bad tmobile area and my only cell signal is tmobiles wifi calling, so my question is if i flash to another tmobile gs3 rom will i still have wifi calling or is that just available on stock ics?
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Just on stock-based T-mobile ROMs.
[T-Mobile, Samsung Galaxy SIII] liljoka166:
I was afraid of that. Any way to port out that feature and flash via cwm?
[T-Mobile, Samsung Galaxy SIII] x1tyme:
Im afraid not right now. There a bounty thread to rise money for development or hack to none stock rom.
[T-Mobile, Samsung Galaxy SIII] princeasi:
Check with some custom roms, because some devs includes the T Mobile WiFi calling into their roms.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
You forgot to mention those custom ROMs are stock-based ROMs. Just trying to be clear and not confuse the OP.
[T-Mobile, Samsung Galaxy SIII] princeasi:
True!

I'm Just Sayin!
[Nexus 4 Q&A, Help & Troubleshooting] EdZ:
The Qualcomm Website, LG website (for the Optimus G), Google's Nexus 4 website, nor any reviews I've found thus far, have mentioned exactly what audio/video the Snapdragon s4 Pro supports in regard to hardware acceleration. There's the basic 'h.264 support' listed, but no mention of which profile (probably High), and what level (e.g. 4.0, 4.1). High Profile Level 4.1, for example, would be the minimum for playback of unmodified Blu Ray video. Then there's things like Hi10p support, container support, etc.

Can someone with Qualcomm dev access ferret out the actual video & audio codec and container hardware acceleration support for the S4 Pro?
[Samsung Galaxy Nexus] kvizii:
Excuse my complete noobishness, but can someone help me root my Galaxy Nexus but still get OTA updates from Google? I found multiple sources from here and a video from QBKing77 but nothing answer my question completely. I would be really grateful if someone with experience could help me by give me step by step instructions.

Thank you.
[Samsung Galaxy Nexus] alexye:
Rooting your phone does not disable OTA updates.
[Samsung Galaxy Nexus] eqjunkie829:
Why would you want ota if you rooted? Just flash a rooted version of the updated rom when it's released.
[Samsung Galaxy Nexus] kvizii:
I want to root just for two or three apps that require root access and still get updates from Google. I want the process: root -> get OTA update -> root again etc...
[Samsung Galaxy Nexus] The_other_ray:
That's what I do. I don't flash ROMS, just use a few apps that require root. Install OTA Root Keeper from the play store to retain root. Run the app before installing any updates to preserve root. Then when you receive an OTA, install the update then run OTA Root keeper again to get your root back. Worked for me on Verizon Galaxy Nexus coming from 4.0.4 to 4.1.1.
[Samsung Galaxy Nexus] kvizii:
That is what I'm looking for! Can you explain to me step by step how did you did that? It would be great if you help me. :)
[Samsung Galaxy Nexus] Jubakuba:
Use the guide in my sig or stickied at the top of this forum.

Only change would be fastboot boot recovery cwm.img rather than flash.
[Samsung Galaxy Nexus] suprakarma:
Just root the phone, and don't flash any custom recovery, then download supercurio's OTA root keeper app from the playstore, to backup your root then enable root with the same app after you receive OTA
[Samsung Galaxy Nexus] kvizii:
Sorry for replying this late, thanks for the advice, but can you explain to me the steps that I need to use with the GNexus toolkit to root like you did? Thanks
[Samsung Galaxy Nexus] Pirateghost:
Don't use the toolkit?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] anotherxdauser:
Why not?

The toolkit is SUPER easy.

Open the tool kit and the DOS window guides you through what to do, by typing numbers or letters to get the desired option. I can post the guide on when to boot in recovery mode and what the phone will do but as for the Toolkit, it's self helping. Just install it, run it and follow the on-screen instructions.

I do exactly the same as what you want successfully; I have a completely stock Nexus, but it's rooted for the use of some apps. The OTA update tells me when there is an update, I install then simply root again. I'd rather not have an app to keep root as that will be yet another app to clog up my phone's app drawer.

A lot of the custom roms aren't to my taste so I am happy to keep the stock experience :)

Will post again the steps when I am on my home PC.
[Samsung Galaxy Nexus] Pirateghost:
simply because the toolkit is an excuse not to learn the FUNDAMENTALS of owning a nexus device.

what happens when something goes wrong? do you know what the toolkit is doing behind the scenes? most of the toolkit users DONT. there are more than enough 'HALP!1!1 I BriKt mah PhoneZ!1!!oneone' to prove this is the case....

if you understand what its actually doing, you understand how useless it truly is...
[Samsung Galaxy Nexus] anotherxdauser:
Well, for starters the "fundamentals of owning a nexus device" don't include rooting at all. I know many people who use Nexus devices un-rooted and are fine.

Plus, I'm more than happy not learning too much about it as I'd rather spend my time eating cake.

Remember, not everyone here is in to tweaking settings, trying different radios, resetting their phone every 5 mins to test yet another ROM.

Some people are more than happy with the stock experience but just want root. The toolkit makes that simple.

Secondly, if the toolkit was doing things behind the scenes, I'm sure someone would have found that out and reported by now.

Thirdly, how do you know custom ROMs aren't doing the same thing? They are far more likely to be able to phone home without the owner knowing.

Fourthly, I personally tried rooting the manual way but the one line help of "just type this" I got never really worked with my phone.

Fifth, I've used the toolkit on my own phone and my partners many times, I've seen nothing bad, no bricking.

Don't see why you're so against something which makes life a lot easier for people who aren't too sure how to root the manual way?
[Samsung Galaxy Nexus] Pirateghost:
And yet another person who fails at grasping why XDA exists....

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] anotherxdauser:
Actually, I do. I understand why XDA exists but I also understand the multi-uses it really has.

Not everyone who comes here has a desire to mess with their phones all the time...

If you're not a fan of the toolkit, why not flame the developer?

Here's a short guide on what the OP wanted to do.

1) Make sure phone is up to date. Make a note of your software version - probably 4.1.2 or 4.2 and build number (mine is JZO54K)

2) Turn on USB Debugging (Settings > Developer Options > USB Debugging)

3) Shut down the phone

4) Start in Bootloader (power button + vol up + vol down)

5) Run the Galaxy Nexus toolkit

This is where we use the toolkit. Read the info and select your build number. The windows will guide you through what options you have. If you want to root only, choose that option. Go through the menus and type YES to begin.

6) Phone will restart

7) After ~160 seconds, ToolKit will restart to Bootloader

8) Phone will restart

9) Toolkit will finish rooting by pushing the files to the phone.

10) Phone will restart back to Bootloader

11) Finish - Confirm in ToolKit

See pictures for further info.
[Samsung Galaxy Nexus] Khizar:
the toolkit also exists on xda..
[Samsung Galaxy Nexus] Pirateghost:
So does the person that thought I was saying the toolkit did something malicious... I never said any such thing.

Toolkits are pointless. It takes longer to learn the toolkit than it does the three commands needed to unlock and root a nexus. That's my ****ing point, yet this guy is going on about how easy the toolkit is to use. If it's so ****ing easy, why did you have to provide screenshots and instructions?

XDA-spoonfeeders.com

I miss XDA

Sent from my Galaxy Nexus

**edit**

i cannot believe that someone would actually think its NOT beneficial to understand the process, and rely solely on a toolkit...its amazing to think that there are people so wrapped up in their own little minds, that they refuse to take the time to learn to do things the right way and understand what they are doing to their device.

what happens when joe user, who only knows the toolkit, flashes a mod on his phone that was NOT intended for his phone/build/rom version, and he bootloops? he jumps on xda and posts a thread. HALP I JACKED MAH PHONE!!! how do i fix it with the toolkit?

please, for the love of tech, LEARN what it is you are doing. do us all a favor and help spread the KNOWLEDGE and stop with the damn toolkit. this website is designed for you to learn, not follow a damn prompt/menu to get instant gratification.
[Samsung Galaxy Nexus] TomBall718:
Don't use a toolkit. Learn commands yourself and you won't have to worry about what a toolkit is or isn't installing.