yashsingh1/xdaforums huggingface dataset:
[Kindle Fire Q&A, Help & Troubleshooting] SwoRNLeaDejZ:
You should try to change the boot mode to fastboot through adb and then try fastboot reboot recovery to try and get into recovery that way, might work.
[Kindle Fire Q&A, Help & Troubleshooting] thrillseeker:
So if i use adb shell idme bootmode 4002 and then fastboot reboot recovery it will enter in recovery? Will i need to reboot between these two commands?
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
Hi everyone -

I recently acquired a Droid RAZR M that is stuck in a never ending bootloop, no matter what option is chosen during startup. The device is low on battery, but I do have a Motorola Factory Cable that will get the phone recognized in RSD Lite. I was able to flash the latest XML file from here:

http://sbf.droid-developers.org/phone.php?device=8

File used: Blur_Version.98.30.1.XT907.Verizon.en.US

But the device is still boot looping. It hangs on the "M" logo for about 5-10 seconds, then the screen flashes and it restarts. It behaves the same way when I try Normal Startup, Recovery, Factory, or BP tools. Like I said, I am able to get to the AP Fastboot screen and flash XML file successfully.

Is there anything else I can try? Where is the water damage indicator located on this phone?

Thanks in advance for your help.
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
Hit fastboot mode flash system img. Or factory reset from there
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
Thanks for the reply. Could you please explain what you mean?
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
Fastboot mode is where you can flash partions and do quite a bit of things before booting the device, if you have a stock rom. Or something maybe you could flash the system using. Fastboot flash system system.img, or while in fastboot mode try and factory reset, I forget the command for that, googling it could help, are you familiar with fastboot and adb commands or command/terminal?
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
What is your bootloader version?

---------- Post added at 11:57 PM ---------- Previous post was at 11:56 PM ----------

Also are you flashing as root?
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
AP Fastboot Flash Mode (s)

10.9B(*) (sha-1e9f557, 2013-09-26 13:20:55)

eMMC Info: Size 8GB

Device is LOCKED. Status Code: 0

Battery OK

Transfer Mode:

USB Connected

Fastboot Reason: Flash Failure

usb connected
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
And you don't have stock recovery any more
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
The stock recovery should be there, but when I select it from the boot menu, it just boot loops the same way all of the other options do.
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
Try to reflash stock recovery, the moto g did that to. Me when I selected recovery and one there. Was corrupt
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
I just tried the RSD lite process again with RSD lite 6.1.5, and it said successful as always, but the device continues to bootloop.

I also tried mfastboot.exe instead of the normal fastboot, here are my results:

G:\VRZ_XT907_9.8.1Q-94-1_CFC.xml\VRZ_XT907_9.8.1Q-94-1_CFC.xml>mfastboot flash system system.img

sending 'system' (30720 KB)...

OKAY [ 2.358s]

writing 'system'...

OKAY [ 3.774s]

sending 'system' (30720 KB)...

OKAY [ 4.470s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.508s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.527s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.487s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.470s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.477s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.490s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.507s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.480s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.495s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.477s]

writing 'system'...

OKAY [ 1.351s]

sending 'system' (30720 KB)...

OKAY [ 4.511s]

writing 'system'...

OKAY [ 1.355s]

sending 'system' (30720 KB)...

OKAY [ 4.438s]

writing 'system'...

OKAY [ 1.358s]

sending 'system' (30720 KB)...

OKAY [ 4.381s]

writing 'system'...

OKAY [ 1.355s]

sending 'system' (30720 KB)...

OKAY [ 4.461s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.500s]

writing 'system'...

OKAY [ 1.355s]

sending 'system' (30720 KB)...

OKAY [ 4.479s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.491s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.500s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.484s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.479s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.491s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.466s]

writing 'system'...

OKAY [ 1.353s]

sending 'system' (30720 KB)...

OKAY [ 4.468s]

writing 'system'...

OKAY [ 1.352s]

sending 'system' (30720 KB)...

OKAY [ 4.565s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (30720 KB)...

OKAY [ 4.476s]

writing 'system'...

OKAY [ 1.354s]

sending 'system' (25529 KB)...

OKAY [ 4.105s]

writing 'system'...

OKAY [ 3.127s]

finished. total time: 165.159s

Although it says it is finished, the device continues to bootloop endlessly.
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
I just tried flashing the recovery, and it was successful. The device continues to bootloop.

G:\VRZ_XT907_9.8.1Q-94-1_CFC.xml\VRZ_XT907_9.8.1Q-94-1_CFC.xml>mfastboot flash recovery recovery.img

sending 'recovery' (10240 KB)...

OKAY [ 0.800s]

writing 'recovery'...

OKAY [ 3.090s]

finished. total time: 3.890s
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
Does it boot into recovery? Or boitloop
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
When I try to boot into recovery, it continues to bootloop.
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
Now factory reset, install. Each firmware update one after the other. Reset after each one

---------- Post added at 12:41 AM ---------- Previous post was at 12:38 AM ----------

There is a chance that the original owner tried to just update and didnt do it right
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
How can I do a factory reset from the Fastboot screen?
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
fastboot erase userdata

fastboot erase cache

fastboot reboot
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
I was able to wipe userdata and cache using those commands. Then, I flashed the newest XML file using RSD lite. The device is still bootlooping.
[Droid RAZR M Q&A, Help & Troubleshooting] Durteedee:
You flashed all of there in order?
[Droid RAZR M Q&A, Help & Troubleshooting] boostedcx:
Yes, I just went through and performed every step in the XML file using mfastboot. These are these are the steps that I performed:

<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="FB3D9083F1B5890BBF2FA8617D31A70A" />

<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="FB458002D5B1B3430B0519E0F206C361" />

<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="5E1E096A29FB49A955C595B3E7759CA7" />

<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="16813AF63FFBF4044FBF72D75BD47DB1" />

<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="0C3F4FF07D3B5037E17B8EFE5F4C66EE" />

<step operation="flash" partition="tz" filename="tz.mbn" MD5="474F31095C8146D1F86D0E5CE72B878F" />

<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="A40F6AAFA4A581023A2EDA9F23202453" />

<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="3E7F1624D8DDA8C8E4995F99A68B321F" />

<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="0898A1859E77F05B62E2A6D04251E30E" />

<step operation="erase" partition="modemst1" />

<step operation="erase" partition="modemst2" />

<step operation="flash" partition="logo" filename="logo.bin" MD5="506F42184C465D9CD8BB2BD27DB77F1A" />

<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="66AD59B88203992915EAF476C9E17E58" />

<step operation="flash" partition="boot" filename="boot.img" MD5="624AD56D21BE40E2C62F2D8666C1A3DA" />

<step operation="flash" partition="recovery" filename="recovery.img" MD5="A51ACEFFB3DE7BB9259F345AF8E5ABB6" />

<step operation="flash" partition="cdrom" filename="cdrom" MD5="8C578BC3308036F86BF30BA802E488DF" />

<step operation="flash" partition="system" filename="system.img" MD5="AFF82B543EF8E558892AA67D4909C067" />

<step operation="erase" partition="tombstones" />

<step operation="erase" partition="cache" />

<step operation="erase" partition="userdata" />

After each step, I wiped userdata, wiped cache, and reboot-bootloader. Unfortunately, the device is still bootlooping and will not boot to recovery.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ipedrorodrigo:
first of all I would like to apologize for my English is bad (I'm from Guatemala)

The problem I have is I have a t959 Galaxy S 4G with a motherboard of a galaxy s i9000

when I try to boot the phone, will not start, no nothing

charge only when the cell is left in a circle around and suddenly goes

the phone worked fine but one day to another no longer worked

I appreciate you help me revive, Thanks

I leave photos to look better
[Galaxy S I9000 Q&A, Help & Troubleshooting] Gokulbalram:
Does it boot into Download Mode?
[Galaxy S 5 Themes and Apps] Djimmy:
What you need to activate

Smart scroll in Quick Settings and lighting effect​

* SM-G900F STOCK ROOT

* Permissive mode

install Sqlite editor, Open

(1)in Apps found settings storage (marched right down the list) selected.

(2)Open settings.db

(3)selected system.

(4) now search [notification_panel_default_active_app_list ] Selected and add SmartScroll; and SAVE.

In [notification_panel_active_app_list_for_reset] add SmartScroll; Save and REBOOT. View My screenshot

(5) Open Sqlite editor , Selected Recent > Settings.db> system. Search [lockscreen_ripple_effect] Édit the value to 2 , SAVE and wait 30 seconds. then press power to turn.turn on ! restart removes the effect of unlocking.

On this thread Download Sqlite editor apk

http://xdaforums.com/showthread.php?t=2698651
[Galaxy S 5 Themes and Apps] Richcar:
I get this error when I try to open settings db.
[Galaxy S 5 Themes and Apps] BLuFeNiX:
You didn't post an error.
[Galaxy S 5 Themes and Apps] Djimmy:
It did not error! settings.db is open without error. if you have SE FOR ANDROID PERMISSIVE. it was said to!
[Galaxy S 5 Themes and Apps] lilflip21:
I just enabled airwake and it's working great on my 900P Thanks!
[Galaxy S 5 Themes and Apps] txr33:
You can access the air wake up toggle in accessibilty settings so no need to edit the database for it and can be toggled on/off anytime

Sent From AllianceROM S5
[Galaxy S 5 Themes and Apps] Djimmy:
ah yes it was true well hidden, I will replace it in the day
[Galaxy S 5 Themes and Apps] Goldie:
Is that not a paid app youre giving away in the OP?
[Galaxy S 5 Themes and Apps] Djimmy:
no I did not pay I had another post. problem with it? it's true I asked if I could share but I thought he had no worries. . ?
[Galaxy S 5 Themes and Apps] Goldie:
You cant give away apps that are paid on playstore here
[Galaxy S 5 Themes and Apps] Djimmy:
yes I imagine. but hey I did not know it was a paid app. because it not visible in my playstore. and yes even if I am in a French department in the Indian Ocean google severely restricted the playstore. ok I'll take
[Galaxy S III Q&A, Help & Troubleshooting] frictionbuster:
I'm sorry if this has been posted already. Can't seem to find any thread.

The thing is I updated my s3 from 4.0.4 to 4.3 directly via Odin.

And now I'm getting an "Emergency calls only" error.

I tried reading every thread. If there is someone who would help me??

Please.

Thanks.
[Galaxy S III Q&A, Help & Troubleshooting] shivadow:
Can you see your imei etc in about phone?
[Galaxy S III Q&A, Help & Troubleshooting] frictionbuster:
Yes. The IMEI and serial number are intact.

When I call on that number, I can hear a ring.

But phone doesn't notify!
[Galaxy S III Q&A, Help & Troubleshooting] shivadow:
Have you cleared the cache (and dalvik if rooted)?.

Factory reset?.
[Galaxy S III Q&A, Help & Troubleshooting] frictionbuster:
Yes. I tried data, cache, dalvik wipes.

Nothing helps.

Will going back to ics help?

I have the efs backup. But it's v1
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
Usual reason a phone is on old firmware is the efs had been badly repaired and won't work with v2 firmwares.
[Galaxy S III Q&A, Help & Troubleshooting] faroukaoun:
hi

1- install cwm with odin http://www.mediafire.com/download/ni3zs ... it.org.rar. just take recovery-cwmtouch-6.0.3.2-GTI9300.tar

2- put the patched files in your sd http://hpics.li/12e3bf8 / here's the link https://drive.google.com/folderview?id= ... GkzOUowMG8

4-rebootin recovery mode and install patched modem first then patched kernel and reboot system now
[LG Optimus 3D] itsmemario:
Heya,

I just flashed PACMAN 22.1.0 to my p920. I flashed the Radio App by defcomb via CWM and it worked. So far so great ! :)

Now I wonder if I shall install the "lenovo Super Camera" or wait for the "Google Camera" app and/or if the PACMAN ROM would be influenced by these camera apps in a bad way.

Same question for the ACiD Audio Engine. Would I run into problems flashing it into PACMAN via CWM on my p920, as it has its own audio settings already ?
[Android Q&A, Help & Troubleshooting] HackAttack37:
Okay, basically I used Teamwin and superuser to root my Dell Streak 7 with this tutorial:

watch?v=u302zKspk2E

^put the YouTube url before this, apparently I have to make 10 posts before posting links (THANKS A LOT)

It worked, but now I have a serious problem. When I open the command prompt and everything, I type adb devices and there's no problem, the device is detected and all is good. But after typing

adb shell

$su

#

when I type:

#adb devices

Error: device not found

I'm trying to make /system writable long enough to add my own files in, but I can't do that without superuser mode!

Anyone have a problem like this?

Specs: Windows 8 64-bit on a Dell Streak 7 [Teamwin + Superuser]
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
It detects your device in adb. When you are in adb shell, that is the same as running a Terminal app on the phone. It's not going to see an adb device because it IS the device. Just skip the adb devices while in shell and continue.
[Android Q&A, Help & Troubleshooting] HackAttack37:
Okay, so just typing "sysrw" should work for making the system writable once in adb shell su?
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
Have to mount the system with this command in adb shell:

mount -t yaffs2 /dev/block/mtdblock6 /system

What exactly are you trying to do? Seems like it might be easier with a file explorer that has root access. With that you can mount the system, copy stuff in, change the permissions and reboot. Works for a lot of things on most devices, but depends on the ultimate goal.
[Android Q&A, Help & Troubleshooting] Lgrootnoob:
mind the guy above. When you are at the # prompt. You use this code to remount /system, (you should have busybox installed).

busybox mount -o remount,rw /system
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
The command I posted is specifically for the Dell Streak 7 from their forums. The generic one might work, but I always find specific answers to be best.
[Android Q&A, Help & Troubleshooting] Lgrootnoob:
Alright, fair enough.
[Fairphone 1] ShadeChar:
hey guys

I'm completely desperate. Here's what happened the last two days:

Yesterday my Fairphone suddenly became very slowly and then wouldn't boot no more. Since then every time I try to start my phone, I get the message "process system doesn't react" or something like that. The only thing thats working is the recovery mode.

Today I wanted to make a complete backup so that I can make a hard reset afterwards. But then I had to realize, that the recovery mode isn't able (or I'm not able to see how) to make a backup on an external sd card but only on the internal storage (which is also called sd card which confused me about an hour).

The problem now is that I have a backup but I can't get it on my computer or on my external sd card and so it will be deleted too if I make a hard reset.

I searched the internet for hours and found out, that it is possible to somehow remote control the phone via adb. I read that the phone has to be in "usb debugging mode". I can just put my phone into adb sideload mode or however its called by choosing "update with adb" in the recovery menu.

Is this the reason why my "adb pull" command isn't working? It just says "error: closed". Or is it because I haven't wrote right the path of the backup file? (I used: /mnt/sdcard/userdata_20130801_134656.backup)

Please help me! I have tried so much already, my brain is sizzling:silly:

I'm working on a Mac and have installed sdk.

Thanks in advance!!!

------------------------------------------------------------------------------------------------------------------------------------------------------------

EDIT:

Just to close this topic and maybe help other people with the same issue:

I finally managed to pull the /data folder using adb. What I didn't know was that the backup file (and all pictures, videos, music and so on too) is stored on the internal sd card which isn't affected by the factory reset in the recovery menu. What I also found out was that the backup file (that I had created during the "bootloop" or whatever it was) was corrupted. So the backup logically broke my FP again after I restored from it.

So the solution, as mentioned above, was to pull the /data folder which contains all important user data such as wifi passwords, contacts, messages and so on

I hope it helps

peace

SC
[HTC One S] ilbarone87:
​

INTRODUCTION​

Here we are for our beloved device AOSPA 4+.Our device is full supported by AOSPA - Legacy Team and have OTA. Changelogs

INSTRUCTIONS

1a. Make a backup

1b. If coming from another rom do a full wipe

2. Install rom (mirror) , then GAPPS

3. Wipe cache and dalvik-cache

4. Reboot and enjoy :).

IMPORTANT

​

For those who have problem installing the rom, you have to update the TWRP version due to CyanogenMod modifications. See this tutorial for further information and download the new recovery. http://wiki.cyanogenmod.org/w/HTC_fstab_updates​

Thanks & Credit

AOSPA-Legacy, CyanogenMod

DISCLAIMER

I'm not responsible to any damage, earthquake, bleeding from nose or pregnancy you cause to your device.

LINKS

PA's Website & Changlelogs: https://plus.google.com/u/0/107979589566958860409/posts

AOSPA-Legacy Github: www.github.com/AOSPA

XDA:DevDB Information

Paranoid Android 4+, ROM for the HTC One S

Contributors

ilbarone87

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Hboot 2.15

Based On: AOSPA

Version Information

Status: Stable

Current Beta Version: AOSPA 4.4 RC2

Created 2014-05-03

Last Updated 2014-06-17
[HTC One S] ilbarone87:
Reserved
[HTC One S] ilbarone87:
Service
[HTC One S] ilbarone87:
Uploading ;)

5 min to go
[HTC One S] cannondaleV2000:
nice work. hope you can get it official. goan have to check this out
[HTC One S] leald:
Make a 2.16 version? ;)
[HTC One S] ilbarone87:
Sorry no.

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] _kevn_:
Very smooth so far! And quick/snappy! Thank you very much for this!

Good luck! I hope you get added to the official AOPSA legacy list soon!

OT...

I'm still trying to get my comp. set up to try my hands at building this but it's tough to find the time to fix issues with setting up my environment and other weird things I've run into... 3 children doesn't make it any easier lol. So I really do appreciate it!

transmitted via skynet
[HTC One S] ilbarone87:
Ehehe I understand, I started trying to build since 6 months ago, but I think the most important is that they put the AOSPA LEGACY online.

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] MICH_**:
I am always getting "FAILED" with TWRP 2.7.0.0 :confused:
[HTC One S] ilbarone87:
Please read the OP
[HTC One S] MICH_**:
There isn`t "Paranoid Settings" in the settings app? why?
[HTC One S] ilbarone87:
Ther is no more "Paranoid Setting" in 4+ versions. PA devs decide to rewrite the entire code of PA and implement feature in a less invasive way.

At this time there are two principal features of PA(it has more but they are minor, like QS menu): PIE and Peek.

To activate the first one you have to set "Immersive Mode", for Peek go at the bottom of dispaly settings and you will find it.
[HTC One S] Finnit0:
I guess that this Thread gives an good overview and explanations about the settings.

Running the 03/05 since 1 day and its working flawless. No reboots or freezes. though torch is not working yet.
[HTC One S] MICH_**:
oh... i din´t know that. Thanks! :)

What about Halo? Will Halo be implemented in future in this rom? Or is Hover integrated in the current buid? :o
[HTC One S] ilbarone87:
Halo doesn't exists anymore, now there is Hover. Still Hover is not public so we have to wait until it gets public or i get support. In this moment i'm struggling with my rude fundaments in developing to get the support from official AOSPA-Legacy. Finger-crossed.
[HTC One S] zubeedubs:
understanding that being unofficial you cant get hold of hover due to the source not being released as of yet, i was just wondering if PEEK is already implemented in this rom??
[HTC One S] ilbarone87:
Just read two post above

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] zubeedubs:
sorry i dont know why but only saw PIE... ma bad!!! :cyclops:
[HTC One S] ilbarone87:
Great news guys!!!! We get support and now our device is official!:victory:

For those who use the rom as daily driver the official build will appear as soon as is ready in the OTA (don't now when). After it will appear I update the OP with goo.im link.

Hype for Hover.
[HTC One S] Rapier:
I don't use Chrome but I'll install and let you know right away. Which Chrome version normal or beta?

Sent from nowhere over the air...
[HTC One S] ilbarone87:
No difference, I tried either and same problem was present

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] Rapier:
I could search from Chrome address bar fine. No FCs.

Sent from nowhere over the air...
[HTC One S] ilbarone87:
Did you flash dirty or Clean? Ota or mirror?

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] Rapier:
Clean install from mirror site. I usually don't use OTA since I edit my build.prop file every time before flashing

Sent from nowhere over the air...
[HTC One S] ilbarone87:
Could you try to search a site and then click on the chrome hint? I had FC with this operation, if I simply search something don't FC.

Inviato dal mio One S utilizzando Tapatalk
[HTC One S] Rapier:
Yes, I have FCs if I do like this

Sent from nowhere over the air...
[HTC One S] _kevn_:
Sorry [MENTION=1045770]Rapier[/MENTION], quoted the wrong response

[MENTION=5044468]ilbarone87[/MENTION]

"Chrome has stopped" for me as well when searching like this. Dirty flash Ota.

transmitted via skynet
[HTC One S] Rantrave07:
dirty flashed it. seems ok and no bugs up to now. :)
[HTC One S] Finnit0:
dirty flashed it and until now didn't have a single reboot! Very good. Way better than the tow builds before. Chrome fced at the beginning but now after deleting data and one reboot everything is fine!
[HTC One S] elias.acab:
same here, i just type in website address...boom..it crashes on me
[HTC One S] ilbarone87:
The bug is solved, the fix will be in next build. Keep strong. ?

Inviato dal mio One S utilizzando Tapatalk