yashsingh1/xdaforums huggingface dataset:
[Milestone 2 General] jakkokko:
hi all, that what was happen: (really sorry for weak English)

i was in CM10 work good with some troubles like restarting sometimes even i do wipe data many times

then i try to do that http://xdaforums.com/showthread.php?t=948887 to use my milestone internal memory as external SD card the phone become very slow,

i reboot it still buggy i restart in both moto recovery and CM10 recovery and do wipe cache and full wipe data

then i re-install CM10 here the phone start restarting when it come to get the home screen

i remove the battery for 30 minute then i try to start the phone

and after the moto logo i have black screen only with light and the PC detect it like in boot-loader mod (RSD lite detect it)

so i do flash it with this version

(M2L_U6_4.5.2_5127_R01_SIGNED_US1MILA2GBRETLAB125LA003.0R_STABLE45LAMILETRETLA_P005_A028_M001_HWp2a_Service1FF.sbf)

witch i use to flash my phone with it and after successfully complete the problem is the same

i do many time flash with RSD and many time wipe data and factory reset but the same problem always present

i can get boot-loader mod + recovery mode i do flash i try many other version but the phone still wont start always after moto logo i have the black screen bootloader mode with light

then when i plug my phone to charge not USB without starting it i see the battery charging in screen but when i try to start it nothing happen the same problem

after moto logo black screen

pleased help i'm really in a big trouble
[Milestone 2 General] jakkokko:
No solution for me pleased :(
[Milestone 2 General] jakkokko:
Help help help !!!!!!!!!!!!!
[Milestone 2 General] jakkokko:
is the problem not clear?!! PLEASED any HELP
[Milestone 2 General] jakkokko:
here is a video explaining my problem

http://www.youtube.com/watch?v=KHIZlyt6y94
[Milestone 2 General] jakkokko:
any help pleased
[Milestone 2 General] lulli1:
AW: help black-screen boot-loader mod

have you tried to do a full wipe in stock recovery?

press power & x for some seconds. when you see the exclemation mark press vol plus and minus at the same time.

then do a factory reset. this will wipe all data. after that your ms2 will boot the flashed stock rom, hopefully...

plaese give feedback after trying...

edit: i saw in your video that you still have the froyo kernel. here you have to press the @ sign, when you see the exclemationmark...
[Nexus 4 Q&A, Help & Troubleshooting] spences10:
Hi, I have a 8GB Nexus 4 I have just flashed the factory images onto it to do a factory reset and it seems to be bootlooping

Anyone else done this know how long it should take? Didn't take long on the Galaxy Nexus to bootup after flashing factory images
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
Reboot into recovery and factory reset and wipe cache.
[Nexus 4 Q&A, Help & Troubleshooting] spences10:
Ok, so get into fastboot using the hardware keys flash a custom recovery factory reset and wipe cache?

Will give it a try, thanks
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
Nope don't flash a custom recovery. Boot into the bootloader. Scroll to recovery using the volume buttons and press power to enter.

When you are there press volume up and power to open the menu. Then wipe cache and reset.

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] spences10:
Ok that did it \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/ \o/

Thank you :)
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
No problem. Not really sure why that is needed. It must be a bug with the bootloader not wiping data and cache correctly.
[Nexus 4 Q&A, Help & Troubleshooting] daddioj:
People should really learn fastboot commands. it really helps especially times like these.

I completely wipe my phone using fastboot only then using the format command on each partition. the phone will then wipe itself after a reboot. after flashing new images of course. not saying you ^^ just saying for people in general who don't know any of them
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
The problem is for some reason the fastboot erase command and -w sometimes isn't formating userdata properly and causing bootloops.

There have been a lot of reports. Check efrants return to stock sticky.
[Nexus 4 Q&A, Help & Troubleshooting] daddioj:
hmm its been working well for me

I'll do it all manually

I think the erase command actually kills the partition. and the format command will ready the area for data. correct me if I am wrong?

but i'll use the "erase" command first for all partitions. then i'll format them

fastboot format system

fastboot format cache

fastboot format userdata

then i'll go ahead and flash all the image files. then once I reboot the phone actually does a factory reset on its own.

but I know what you mean. I read that as well. but this method ^^^ has been working for me.
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
You're probably right.

I'm pretty sure with "fastboot flash userdata" it will rebuild the partition properly.

But possibly the reason people are running into issues is when using the command "fastboot erase cache" This was never a problem with the galaxy nexus but for some reason it might be for the N4.

Others have claimed bootloops when using "fastboot -w update" which shouldn't be happening. That makes me think its a bootloader bug.
[Nexus 4 Q&A, Help & Troubleshooting] spences10:
Thanks both for this, but bookmarked the thread now in case it happens again. I know better now :D
[Samsung Galaxy Nexus] modern_messiah:
Hi all,

Sorry if this has been discussed previously. I did search but couldn't find anything...then again I suck at using search. Anyway, I updated my galaxy nexus to 4.2 using the GNex software and everything ran beautifully for a good month. In the last week however I keep getting a notification saying the 4.2 update is available and that I should install it. I can't cancel it and I can't remove it from my notifications bar. Out of frustration I installed it but this did nothing - it just sat on the lock screen and my phone wouldn't boot anymore so I had to reinstall the original 4.2 ROM I had.

This did remove the notification for a few days but now its back. I don't need or want it so what gives? If this has been dealt with elsewhere a link would be fantastic.

Thanks :)
[Samsung Galaxy Nexus] brunnen153:
How big us the update? If it's under 1mb, then it's the 4.2.1 update.

If it's the 4.2.1 update, then it really shouldn't make your phone bootloop.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] Khizar:
download fotakill.. push it to system/app. install it, then reboot
[Samsung Galaxy Nexus] madd0g:
Or rename otacerts.zip from /system/etc/security to something else.
[Samsung Galaxy Nexus] modern_messiah:
Well it is under 1mb so it must be 4.2.1, however before I try those other suggestions here is what I get when I try to install the update:

It then churns along for a bit and then says:

Then when I reboot it just sits on the google logo indefinitely. The only way to fix it is to reboot into recovery mode and reinstall 4.2.0, which thankfully does not wipe everything.

Any clues?
[Samsung Galaxy Nexus] madd0g:
How about you try downloading the 4.2.1 OTA zip and flashing manually in CWM ?
[Samsung Galaxy Nexus] modern_messiah:
Yeah I will probably have to try that. Need to find the link first.
[Samsung Galaxy Nexus] Khizar:
Takju OTA

Yakju OTA
[Samsung Galaxy Nexus] modern_messiah:
Thanks....I installed this one. Hopefully it does the trick. It did take a few days for the update to reappear last time so if nothing pops up after a week I'll know it's fixed.

Still keen to know what happened though...no loss of sleep if I never find out :)
[Samsung Galaxy Nexus] madd0g:
Maybe there was an error in the downloaded OTA zip and it constantly failed the verification.
[Asus Transformer TF700] sbdags:
You can flash this straight over CleanROM 2.3 to 3.x or Asus Jelly Bean stock without a wipe if you want to test it – but it is a very good idea to wipe Cache and Dalvik Cache. You must be unlocked and have a custom recovery (TWRP/CWM) to flash this from the internal or external sdcard.

Don't forget to do a Nandroid Backup first and give the ROM 5 mins to stabilise!

This Rom is based off the latest Asus Infinity 10.4.4.23 WW full release. It will work on any locale infinity.The main thing I can see they have changed is the camera libraries. Other than that is looks pretty much the same as the previous release.

•	Rom is ODEXed as Asus have done it

•	SuperSU binary and apk included to give root access

•	Busybox installed

•	init.d support

•	unsecured stock kernel

There are no other mods – please don’t ask for theming, changes or performance boosts. Those will come with CleanROM Inheritance v3.0 :)

DOWNLOADS

Asus Stock 10.4.4.23 Odex Full Resumable Mirror 1

Asus Stock 10.4.4.23 Odex Full Mirror 2

MD5 Sum: 9c797920d0c0f8fcbb7a2f23d2f2beb7

Thanks to surdu_petru, buhohitr and of course Scott (scrosler) for advising me along the right path – thanks guys!

Have fun!

Darren
[Asus Transformer TF700] sbdags:
Reserved! :D
[Asus Transformer TF700] willjohnson:
So is this actually the .23 firmware also? As in we could install this from your current Clean Rom Inheritence and use it to upgrade to .23 instead of downloading the update file from Asus and flashing it, rerooting and all? Cause that would be so much easier than going with Asus' file and starting from stock with data wipes and all.
[Asus Transformer TF700] buhohitr:
Yes, as stated in the OP, this rom is almost stock with a few minor tweaks. The performance is exactly like the Asus rom you download from Asus. The only nice thing about this is it PRE-ROOTED, (if you use Asus stock rom you have to re root again), other than that nothing else is useful at the moment. Its performance is no where near Cleanrom 2.7.2.
[Asus Transformer TF700] sbdags:
It is based off the WW version but to be honest you could flash it on any SKU as the only difference between the two is the name in the build.prop file. It will work fine on a US device.

This file does not update the bootloader. So update from ics to jb from the Asus website by unzipping their file and flashing in twrp. You will lose your custom recovery so be prepared to flash it back from a pc using fastboot.
[Asus Transformer TF700] kwk_kwk:
Please help with flashing

Does someone can pour the lihgt what kind of tool should I use to flash this Asus Stock 10.4.4.23 Odex CWM or TWRP. And it would be very informative to get steps for flashing by flashboot method.

I can see lot of files in ROM zip, but flashboot use only one. I completely confused.
[Asus Transformer TF700] sbdags:
You should use a custom recovery like TWRP or CWM to flash this. Not sure what you are talking about with fastboot? Why would you want to flash a ROM via fastboot? This is the Asus stock ROM slightly modded as explained in the first post.

Good luck and Merry Christmas! :fingers-crossed:
[Nexus 10 General] Stanley_Cooper:
Hi all was just reading this forum tonight using the xda app when suddenly the screen started flickering. At first I though it was an issue with the app but the screen kept on going black for a split second until the display totally disappeared and went black.

I then tried to switch it back on for which it didn't do anything. At the time I had around a quarter of battery life left, plugged the charger in and left it for a few minutes until it finally kicked into life but the battery was dead.

Does anyone think I have a faulty nexus?

I have also noticed once when I had switched the display off left it for an hour, came back and the back of the tablet was hot plus the battery was nearly flat.

Stan.
[Nexus 10 General] atg284:
That happened on my original one the picking it up after a while and its hot part. Found out it was an appl apparently freaking out in circles. I looked in battery stats for what was drawing all the power and I forced stopped it. Can't remember which app it was though :/

Oh and it never happened again (week)
[Nexus 10 General] boominski:
Android can get a bit screwy with reading the battery life. I had this problem on my Nexus 7 (fizzling out at around 35% battery). The issue was resolved by fully charging the device (and leaving it charging for around 2 hours after it reached 100% to be absolutely sure the battery was full - you might want to leave this longer for a N10 since the battery takes longer to charge) - and then doing a full factory reset. No problems since.
[Nexus 10 General] Stanley_Cooper:
Thanks all, I will keep an eye on this one. Only had the tablet for a week so wasn't expecting it to flip out like this!

Stan..
[Nexus 10 General] Richieboy67:
You might also try a battery configuration app.. Charge the battery to full and run the configuration app.

Changes are your battery was not as full a was showing. Could also have been an app draining too
[Nexus 10 General] Stanley_Cooper:
Ok, well fully charged up the device overnight three days ago. Haven't been using the tablet alot over the weekend only to use this morning. i noticed the battery hadn't changed percentage at all since yesterday and was on 48%, I only had a few apps running, facebook, mail and browser only to find again the screen started flickering like mad and then it went dead. It is currently charging up again for which I will leave it for a while.

I will have a look for that battery configuration app but if this happens for the third time I think I will speak with Google about this as it shouldn't be doing this!

Stan..
[Galaxy S II Q&A, Help & Troubleshooting] gonvilleandcaius:
Hey guys,

Could you explain to me in an accessible way, why the exynos source code is so important for the development of custom roms?

We have a multitude of rooms already, how were they build? If no official sources are available, are custom roms in any way inferior to Samsung stock android (eg lacking hardware video acceleration, heavier battery drain, non-functioning ports/radio, etc. )

Does the code have to be released periodically in a best case scenario by Samsung, ie. with any major android or firmware update, or is it a one-time thing?

And finally, can devs do something with the source code that was recently released by Samsung?

You probably will instantly recognise that I have no programming background, so apologies in advance if this sounds stupid

:)
[Galaxy S II Q&A, Help & Troubleshooting] iamanoopmk:
A simple way to understand is this..

Just how with every new update of windows you need updated drivers to get the graphics card, audio etc working same way we need certain drivers for the chips inside the phone. Since these are designed by Samsung they control the right to not allow others to know the design of these chips. That's why they won't make it open source instead release these drivers so that custom ROM builders can use it.

Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
[Galaxy S II Q&A, Help & Troubleshooting] gonvilleandcaius:
Thanks- this really helps. So that means we have the official and fully functional drivers in CM9, but only through workarounds can the devs get them to work in, for example, Jelly bean based CM10?
[Galaxy S II Q&A, Help & Troubleshooting] iamanoopmk:
They are doing the exact same thing in CM10 and CM10.1

They have used old ones and some fixes to compensate. That is why CM10 is smooth but not as much as original JB
[Samsung Galaxy Nexus] Mayakarenina:
Please help! I've bought 3 different products and none of them are working. I have a Samsung galaxy Nexus (Canadian network), a non-mhl tv, and I can't seem to get it to work. I bought the Samsung adapter, but it's not powering up the phone, and the picture isn't coming up at all. The tv recognizes the phone, but nothing is showing up. Any advice?
[Samsung Galaxy Nexus] cyberon:
My only advice is to connect to the charger first and then to the phone because the adapter needs to be powered.
[Samsung Galaxy Nexus] jeetS:
If you have the adapter for the sIII then it doesnt work.

You need the old school adapter not the newer ones.

someone may correct me on this but i think the old one is 5pin and the new one is 11...
[Samsung Galaxy Nexus] klusek1985:
As it has been already said, first of all you need compatible adapter. I use and recommend Samsung EPL-3FHUBEGSTD model.

After that, the power suply must be connected all the time. Then plug all of that to the TV box and it should work.
[Sony Tablet S] boxer29:
Just updated to new version

Smooth new gui
[Sony Tablet S] gambiting:
Downloading right now. They added quite a lot of new features,but it's no jelly bean though.
[Sony Tablet S] Divine_Madcat:
Thread moved go the correct board. Development is only for software development by users.. Commercial rom releases belong in general.
[HTC Sensation] dariodisgusto:
Hi!

On my phone I have venom rom until yesterday work very good ;), but today, when i installed one kernel via venom hub, my phone on restart keep bootloop :(

I can access to 4ext recovery, I try to wipe all, to reistall rom, to install another rom but nothing, is always bootloop :(

How can I fix that problem?? Please help meeee

Thx to all

Dario
[HTC Sensation] rzr86:
S-ON or S-OFF?

if you are S-ON enable smartflash from recovery and then flash the rom

otherwise flash the boot.img of the rom manually

see here http://xdaforums.com/showthread.php?t=1631861 (extra 1 step)
[HTC Sensation] dariodisgusto:
Sorry, the phone is S-OFF :(
[HTC Sensation] dariodisgusto:
When i enter to 4ext, it says "4EXT smartflash is currently set to update your boot partition on next system start.

Is this wanted or should it be removed?

Remove smartflash? YES or NOT
[HTC Sensation] rzr86:
ok let's do this

from 4ext recovery go

tools

format all partitions except sdcard

then flash the rom

if that doesn't work too follow the second option in my previous post(flashing boot.img manually)

but in any case don't enable smartflash because you are S-OFF
[HTC Sensation] dariodisgusto:
I try to format all and then install the rom but not fix the problem, now I try with boot.img (but what is boot.img? where I found this file?)

Thx
[HTC Sensation] rzr86:
open the rom.zip and you will see the boot.img

extract it and place it in the folder where you have adb and fastboot files

check in settings from your device if you have usb debugging enable

boot your device into bootloader

connect it to pc(it will say fastboot usb)

now in the white space of the folder do shift + right click and choose open command window

then do these commands

fastboot flash boot boot.img

fastboot reboot

then see if it will boot up

best wishes
[HTC Sensation] dariodisgusto:
When I launch command: "fastboot flash boot boot.img" I have this message;

"sending 'boot' (4904 KB) ...OKAY

writing 'boot' ...FAILED (remote; not allowed)

finished. total time 1.467s"

What is this?
[HTC Sensation] rzr86:
maybe it requires to have htc drivers installed

do you have them?
[HTC Sensation] Jonny:
You need the juopunut hboot to allow fastboot flash commands.

The easiest option is disable SmartFlash in 4EXT
[HTC Sensation] dariodisgusto:
I installed "HTCDriver3.0.0.007" is it right? Then I disable smartflash from 4ext but I ave the same error!

Please helpppp
[HTC Sensation] rzr86:
what is your hboot version?

maybe you need the juopunut hboot as Jonny suggaested

i can't think something else right now:(
[HTC Sensation] dariodisgusto:
I have that HBOOT:
[HTC Sensation] rzr86:
probably then you need the juopunut hboot as Jonny suggested before which is also unlocked and you can perform commands
[HTC Sensation] dariodisgusto:
but now it is easier to return to the stock version? Because I saw that joupunut hboot is not very easy to do :(
[HTC Sensation] rzr86:
i think the only thing you have to do is to follow the instructions where are mentioning at the top of the site

where did you see of returning to the stock version?
[HTC Sensation] ganeshp:
nahh ..you are already SOFF ...no need to do wire trick again ..

you just need to flash juopunutbear HBOOT ..its as simple as flashing custom recovery from fastboot ..thats all

check troubleshoot point #3 from my soff guide(link in my signature) ...the easiest way to flash juopunutbear hboot is given there
[Sony Xperia P, U, Sola, Go] TomNilson:
Hi,

I love to play games on my phones, but there arent any very good apps the the xperia go, thats why i'm asking why there isnt any modern combat game for the xperia go?? It allways tell me, that its not compitable on my device, althlough the go has a dual-core processor, and modern combat 3 was even available for the xperia ray, but why not for go??? Can i somehow get it with root???
[Nexus 7 General] nikotank:
Just got it today after returning my TF700. Have to say, pretty nice, besides the undetection unless using MTP protocol.

Cheers, and discuss?
[Nexus 7 General] khaytsus:
@nikotank Cool, didn't realize this was twitter
[Nexus 7 General] Groid:
If connecting to the pc is your problem, it is almost certainly an issue of drivers on the windows side.
[Nexus 7 General] nikotank:
Sorry to express my joy of a new android toy...

@Groid yeah I didn't know the issue. Tried multiple driver sources to no avail until reading someone's luck with MTP and voila! Like a charm. Strange, indeed.
[Nexus 7 General] plasmamax1:
Lol. I got my new N7 today as well.
[Nexus 7 General] mchief298:
At least he didn't post in the development thread..

OT: About time. xD Kinda confused on why you traded your TF700 in for a Nexus 7.. I would do the opposite...
[Nexus 7 General] phonic:
And you think that required you to make a new thread about it? I'm glad you are happy, but that doesn't mean anyone else gives a crap.
[Nexus 7 General] marksterbate:
The tf700 is trash, much happier on tf300
[Nexus 7 General] Divine_Madcat:
As noted, this is not twitter.

While we appreciate your enthusiasm, this site would be flooded in an hour if every happy owner posted that they were happy...
[Nexus 7 Q&A, Help & Troubleshooting] jonny68:
http://www.7dayshop.com/7dayshop-al...lcnMrRW1haWwmdXRtX2NvbnRlbnQ9TUVNT1JZK0NBUkRT

I'm wondering if something like this would possibly work with OTG cable and stickmount pro and a micro sd card so I won't have to go through the time consuming process of uploading my music to Dropbox via otg cable/external HDD /stickmount pro /Nexus 7 to my Galaxy S3 (OTG cable and external HDD won't work on Galaxy S3) I'm on a mission to get this sorted somehow, any assistance/recommendations would be great.
[Nexus 7 Q&A, Help & Troubleshooting] jonny68:
.....................
[Nexus 7 Q&A, Help & Troubleshooting] jonny68:
Anyone?