yashsingh1/xdaforums huggingface dataset:
[Xperia Arc Q&A, Help & Troubleshooting] Kico. St:
hi..

i wanted to root and then flash a costum rom on a xperia arc but im not getting root first...i used 2 methods for the locked bootloader the doomlord v1 and the Root_Exploit_OneClick both of these show me errors and the phone cant get root,i turned off every another process in the pc and the antivirus and still nothing...pls help me to root it...it is with locked bootloader..

:)

Edit( i rooted it when i flashed a ready to root stock ics firmware and then with one click root method)
[Xperia Arc Q&A, Help & Troubleshooting] MrModMan:
first of all you cant install a custom ROM with a locked bootloader... and the reason why your not getting a root is that your on .62 firmware and you can only root on .42 firmware... (NOTE: android version 2.3.4)
[Xperia Arc Q&A, Help & Troubleshooting] Kico. St:
i have this version 4.1.b.0.431...what should i do to root with this firmware?
[Xperia Arc Q&A, Help & Troubleshooting] MrModMan:
You have ICS https://www.google.com.au/#hl=en&sc...qf.,cf.osb&fp=c72d84806ae8a6&biw=1366&bih=667 that should help you
[Xperia Arc Q&A, Help & Troubleshooting] link-in:
y the way there are 2 ways to root .431(4.0.4)

1) flash the .431 file and then flash the stock kernel of .562 ftf(i.e flash 4.0.4 and the flash only the kernel of 4.0.3) and then use doomlord one click method

2) flash a ready to root ftf file that already has the compiled things together.

(by the way, why dont you unlock your bootloader? because if anything goes extremely wrong it can only be corrected if you have an unlocked bootloader. and unlcoking bootloader is not risky infact it can be reocked again it will give you more choice to choose from various roms and kernels)

and note these methods work on unlocked bootloaders only.

these threads will help youon locked bootloader

for 4.0.3 http://xdaforums.com/showthread.php?t=1600728

for 4.0.4 http://xdaforums.com/showthread.php?t=1683189
[Xperia Arc Q&A, Help & Troubleshooting] noim:
you can root your phone using This method .
[Nokia Lumia 800] Fisher_9511:
Like most of you (I guess) I forced my Lumia to update to firmware version : 1750.0805.8773.12220 [Everything Everywhere]

A really good update, minor improvements to battery consumption, WiFi Tethering, etc..

But I was expecting to get the new location alert icon, which is not there (not dramatical I know, but it's supposed to come with Tango so it's kinda weird).

Visual Vioce Mail is still not coming back neither (yes I said coming back because I had it when I bought my Lumia and it's gone with updates).

My question are : Is there anyone who got the new location icon ?

Someone have intel about Visual Voice Mail on our Lumias ? I saw yesterday that with WP7.8 it will be country specific and for all with WP8

Thanks

Sources: http://www.theverge.com/2012/3/7/2851184/windows-phone-location-icon-update

http://www.everythingwm.com/small-windows-phone-7-8-versus-windows-phone-8-feature-comparison-leaks/2012/07/09/
[Nokia Lumia 800] apollo15rover:
Location icon still the same; I do have visual voicemail.

I think visual voicemail is also controlled by the carrier. T-Mobile is a very big on that feature, so all their platforms have it ..
[Nokia Lumia 800] Fisher_9511:
Orange France support visual voicemail too, but it disapeared when I first updated my phone through Nokia Care Suite.

And it's activated for my number (which is problematic because I have no more notifications for my voicemails).

I'll try find a way.
[Nokia Lumia 800] Fisher_9511:
I downgraded to a branded FW then applied CAB updates and get back my visual voicemail.

I guess the new icon will be in the next 8779 OS update
[Nokia Lumia 800] Mega Maniac:
Whats New?

So I'm running the latest 8773, much thanks to XDA for that :)

But other than the hotspot what is new, my phone looks distinctly the same, I understand I may be able to run more tasks in the background but is there anything else? Anything I can find on my phone and go 'ah thats neat'?

:D
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jjake47:
Hi

I upgraded my Galaxy note to latest ICS previous month, and since then my battery's lasting about 10 hours max, earlier on Gingerbread, with my kind of use, it used to last about 15-18 hours(including Wi-fi and continuous use on BT headset) or more, now when I use Google latitude(navigation), the phone dies out after a little over 5 hours(earlier this would reduce my battery by say 2 hours or so)

I was thinking I could do a factory reset and check if any unwanted apps might be eating up my battery, but as I read through the forums, word around is that it might brick my phone. I have the following concerns

1. Can I factory reset my galaxy note while on ICS(samsung Official release India)

2. Can I backup my Apps data only(I'd want to reinstall my apps, but save app data to restore later, eg..game progress, etc)

Thanks in advance for the help..:)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aziz981:
I would advice against it. I had the same ics official indian release. I wiped and my phone bricked. Because all official ics kernels are risky. If u want to know search for BrickBug app by chainfire it will check ur chip firmware and will say it is risky or no. If u want to wipe flash an older gb rom via odin, wipe on gb and then do ICS upgrade.

But please dont try wiping in ics kernel. I paid the price and now have to take my phone to service centre as nothing works.

---------- Post added at 04:46 PM ---------- Previous post was at 04:39 PM ----------

I even started a thread regarding. Nothing could save my note

http://xdaforums.com/showthread.php?t=1761647

For more info see this post by chainfire http://xdaforums.com/showthread.php?t=1693704
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dr.ketan:
It is dangeoud to wipe or hard reset data on ICS

you can backup appl + data using Titanium.

Reflash GB ROM

Wipe cahe N data (only on GB)

Reflash ICS

Restore appl + data
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jjake47:
Thanks alot guys...i'd rather wait till my warranty gets over..and then root it(prolly will have JB roms by then)..is there anything else that i might try to clean up my phone..??..i'm pretty sure all this junk is somehow greatly affecting performance...

Thanks again(I was going to reset it tonight)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] alexv396:
Hi. I have polish version of galaxy note 7000 and run xxlpy. And I wanna flash gingerbread back. Can someone tell me which one is best? Thank you.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aziz981:
Check www.samfirmware.com and your regional GB firmware.

I found a version 2.3.6 for you http://www.sammobile.com/firmware/?page=8&view=4233

This should be good. It is LC1

---------- Post added at 11:14 AM ---------- Previous post was at 11:06 AM ----------

You can do few things to clean up the junk.

Trie Root Uninstaller or Titanium to freeze all the bloatwares. These app that samsung puts makes the phone all heavy

You can find the safe removal list here :

https://spreadsheets.google.com/spr...SENVeXlqUm5vV0E&single=true&gid=0&output=html

Also you can take a back up of your app+data of your applications through Titanium Backup.

Then u can easily uninstall or not used games and apps, but can restore the app and your progress later on.

You can use Autorun manager (similar to startup manager on PC) and you can use history eraser to erase all temporary files and cache of applications

Hope that helps..
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] alexv396:
Thank you Aziz 981
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] tonyking:
hi guys

today i replaced my note again and got another on ics version DDLP8 with stock kernel i had reset device from setting-- Backup and reset --- Factory data reset in front of the dealer and nothing happened to my device its working fine and smooth :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aziz981:
If I were you, I wouldnt try that again at home... :eek:

That LP8 screwed me and itself when i resetted..

But you got it replaced... Congrats pal!!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] CONTACTMC:
I am on uk note, stock with no root. I upgraded ota and did a reset straight away. No issues at all. Guess I am lucky.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] jjake47:
I've installed juicedefender for saving my battery in combination with profile scheduler..m back from office and my battery today..upon my usual use...is a little under 70%..that's huge improvement...i think m gonna go for the ultimate version of the app...guess its worth it..(juicedefender)what would u suggest..??
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aziz981:
Havent tried juice defender, i guess whatever juicedefender can do i can do manually. Like i switch off my 3g when in office. It saves a loads of battery. Brightness at minimum.
[HTC Wildfire S] WoefulDerelict:
This is the user support thread for the Wildfire S port of the TeamWin Recovery Project. Go to: Distribution/Development

Frequently Asked Questions​
[HTC Wildfire S] csoulr666:
I have a question.............................are there any bugs???? I'm asking because this was ported before by a fellow member for the WFS but the recovery couldnt format SD-EXT
[HTC Wildfire S] WoefulDerelict:
I don't know...

There are currently no reported issues. I personally haven't had any issues with formatting SD-EXT but, I'm waiting to hear back from other users outside controlled test cases. So far all I've gotten are support desk questions. I'll be sure to assault some of SD cards I have on had and partition/format them.

I chose to compile this as the other available version I found here in the forums has some issues and I needed a good, cleanly compiled recovery for the Wildfire S. I'm also working with a Frankenstein Fender but, modpunk's clean repo and quality Wildfire S ICS port provided a great CM9 base to start with before moving on to the Dream/Sapphire nightmare. I doubt I'll get that to build cleanly without any major issues in under a day.
[HTC Wildfire S] tsalta:
OKay I have question how i can just flash it trought recovery?

I mean now im with recovery 5.xxxx so what i need to do 1st to remove it to begin back to stock recovery and then fallow the steps you mentioned?!

because befor when i flash the revoery 5.xxx was alot more easy than the writen step for touch recovery now
[HTC Wildfire S] csoulr666:
Nice to here that.............will you do more recovery projects like the EXT4 recovery???? Really like it's level of customization
[HTC Wildfire S] WoefulDerelict:
I don't recommend that.

This image file is not designed to be flashed through recovery. It is generally considered poor practice to erase and rewrite an image the system is currently using. I've chosen not to create a easily flashable zip file as this distribution is relatively new and untested and I'd like to avoid as many issues as possible from inexperienced users. Most accomplished users and developers are familiar with the commands and can easily flash the image in seconds.

I believe most modern ClockworkMod Recovery ports include a full featured kernel and the flash_image command. You could run the command while booted into recovery via an adb shell but, I recommend against it. It is easiest to execute flash_image from your current rooted firmware. Simply open a terminal window on the phone or use an ADB shell.
[HTC Wildfire S] WoefulDerelict:
Possibly...

I could possibly be coerced into working with other projects but, I'm unable to find a public repository for 4EXT Recovery so it doesn't seem like the developer is interested in public ports.

Sadly, the format issue does seem to exist and will be on of the first issues on my list. Hopefully I can work with the TWRP team to correct it.
[HTC Wildfire S] Prototyp1981:
Thanks for the update of the TeamWin recovery. I've rebooted but no functioning in the menu. Although this shows me system, power off, recovery, bootloader but not the cell phone rules. Could there still be followed by a further update? Thank you in advance! Sorry for my bad english...
[HTC Wildfire S] WoefulDerelict:
Yes, there will be updates... eventually.

Am I to understand that when you launch TWRP after installing the image that the touch menu isn't responsive? Are those the inital menu options TWRP is displaying for you? Are you using a Marvel device (GSM)? Do you know for which market your device originally shipped?

There will be more updates to tackle the issues listed in the original post and further maintenance after that as the TWRP code evolves. IF I can recruit some MarvelC users I plan to release a version for that board as well. Given the rarity of the MarvelCT I'm not sure I'll ever be able to provide a tested build of TWRP for that board.

I will grab a fresh copy of the image from the distribution server and check it on my device but, aside from the listed issues the software is working just fine on my Marvel.
[HTC Wildfire S] Prototyp1981:
Thanks for your answer! I bought my Wildfire S in Germany and the TWRP 2.1.4 beta0 run 100% stable but will also appear in the menu 2.1.8, the update everything works fine but on reboot the point (bottom right), he shows me correctly, the points system, power off, recovery & boot loader but no function. When I click on it there is not responding to the touch from the Wildfire S. Thank you but for your work!
[HTC Wildfire S] WoefulDerelict:
I'm unable to reproduce this.

So, as I understand it the entries in the Reboot sub-menu are unresponsive on your device. Unfortunately I can not reproduce this error on my own device. When I enter the Reboot sub-menu I am able to select each option and the device responds accordingly. The only possible complaint would be that the Bootloader option takes you into fastboot instead of the top level bootloader.

I would suggest downloading a new copy of the image to your computer and pushing it to your SD card. If your current firmware is rooted and has the native image writing commands please execute the following from a local terminal inside the root of your SD card. I'd suggest an ADB shell for ease of use.

erase_image recovery; flash_image recovery recovery.img

The output should look something like this.

root@android:/sdcard # erase_image recovery; flash_image recovery recovery.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00240000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00340000
mtd: successfully wrote block at b10c00380000
mtd: successfully wrote block at b10c003c0000
mtd: successfully wrote block at b10c00400000
mtd: successfully wrote block at b10c00440000
wrote recovery partition
root@android:/sdcard #

Once it completes try rebooting into recovery and testing them again.
[HTC Wildfire S] Prototyp1981:
WoefulDerelict, please excuse me. The TWRP Reovery 2.1.8 run very stable on my Wildfire S A510e. I had made the following error when I do not have a Rom on my Wildfire S then do not even work the buttons, reboot system, reboot recovery, power off & bootloader . Thanks again for the great job. Thumbs up from me :good:! Everything works very well! Sorry for my english, i hope you understand me :confused:.
[HTC Wildfire S] sorinaugusto:
in attention of WoefulDerelict

Me too I have same issue like here http://xdaforums.com/showpost.php?p=28602310&postcount=11.I have Marvel A510e,whit:

***UNLOCKED***

MARVEL PVT SHIP S-ON RL

HBOOT-1.09.0099

MICROP-0451

RADIO-7.57.39.10M

Feb 8 2012,18;29;31.

GingerBread 2.3.5. firmware 2.26.401.3 kernel 2.6.35.10-gf696f19b htc kernel@and18-2 #1 Tue Apr 10 18:15:52 CST 2012

baseband 47.23e.3038H_7.57.39.10m

version number 2.26.401.3 CL362953 release-keys.

For me not work neither cwm recovery(in fact is working but whit blank screen-I've rooted the phone by blind method and I've made one backup from Rom Manager-I'm not sure if it's complet).I put in the atachament one log file found on cache/recovery maybe helps.

I've pushed recovery without any errrors,from first try,from cmd window.

Root Checker said I'm properly rooted.Many thanks.
[HTC Wildfire S] WoefulDerelict:
Thanks!

Well, I now know that your device claims to have the same unlocked SPL I updated to when HTC made it available and you're using the same version of the radio. The only difference is that my device is S-OFF. I'm still tracking down more details on what was changed in the newer devices so I can target the issue. I apologize as it will likely take me a while to tackle a problem out there in the ether while I'm currently focused on getting 2.2 working but, the new code has lots of changes targeting the formatting/wipe errors.
[HTC Wildfire S] WoefulDerelict:
I believe I understand.

As I understand it that was supposed to be part of a safety feature to keep users from rebooting their phone without any firmware installed. If you update to my latest release you'll notice there is now a confirmation dialogue that interrupts you if you try to reboot without any firmware installed.

Glad you enjoy the work and I hope to deliver something a bit more polished soon. Everyone is working hard to tackle bugs on their ends and I'm assisting where I am able. Trying to rally support for the new WFS hardware that suffers from display issues with custom recoveries and certain ROMs.

For any users suffering from blank display issues or boot loops with custom recovery software you can join the discussion here.
[HTC Wildfire S] king_lud:
I have just installed this but am a bit confused about the following issue:

Does this mean that you cannot do a full nandroid backup in one go? Does it also mean that any recovery operation will need multiple operations?
[HTC Wildfire S] Caro332:
+1...I would also like to know. I use Link2SD so I do have a second partition. If that's the case, how do you perform a nandroid backup of the second partition? I'm not that advanced to know how to do it.

Plus the phone I have right now is one of the newer devices so CWM doesn't work. It has the white HTC screen as sorinaugusto mentioned earlier. Was just wondering if it would still work or not.

Here is some info:

***UNLOCKED***

MARVEL PVT SHIP S-ON RL

HBOOT-1.08.0099

MICROP-0451

RADIO-7.53.39.03M

Nov 28 2011, 19:09:21

Android Version 2.3.5

Kernel Version: 1.6.35.10-ga66971c htc-kernel@ad18-2 #1 Tue Nov 8m07:08:05 CST 2011

Baseband Version: 47.23a.35.3035H_7.53.39.03M

Build Number: 2.13.720.1 CL 197017 Release-Keys

Thanks for all your help
[HTC Wildfire S] king_lud:
Actually I have done a restore since my last post and everything was restored just like it would have been for CWM and I am using link2SD also.

This was a restore from a single backup, again just like you would do in CWM.

The only difference was the lightning speed with which TWRP performed both tasks!

So it's all good!:good:
[HTC Wildfire S] WoefulDerelict:
Yes, in my tests with the current version if you want a complete backup you must backup each partition individually. In my experience even if I select a complete system backup the end result was always a file that contained only /system data as it was the first partition backed up. Backup operations always end in a reboot on my device. I'm not entirely sure what the root of this issue is yet but, it does have higher priority than most the other issues.

I would examine your backup file to see if it contains more than information for /system. It is likely that the file is incomplete and does not contain information from the /data, /cache, sd-ext or any other partition. If they were properly backed up you would see options to restore them delineated by check-boxes.

The current workaround,sadly, is to backup each partition separately. You will have to select only one partition from the list at a time.

Currently there is NO custom recovery that will properly support the fidgety new revision to the Wildfire S. If the official 5.0.2.8 results in a black screen on your device then you will not find any CyanogenMod kernel based software that will work on your phone. All CM GB based projects will result in a black screen and all CM ICS/JB projects will result in your device halting at the initial splash: the green HTC on a white background. I'm still unsure why but, these new devices and the CynanogenMod kernel do not play well together; however, stock kernels play just fine. All custom recoveries are based off CM sources so you won't be able to reliably use any of them. There are some workarounds that will allow you to flash custom software through black screen recoveries as this software still responds to commands it just doesn't work with the display on your phone. These releases of TWRP were built using CyanogenMod ICS sources so they will result in new devices halting at the initial splash as I've already noted in the distribution post in the list of known issues.
[HTC Wildfire S] king_lud:
Thanks for your reply. yes, I did check and indeed all I had backed up was the /system partition and it turned out that it was only that partition I needed to restore, which was lucky!

So to do a full restore, I presume one needs to select all of the separate backups and then swipe to restore, rather than one by one. Is that right?
[HTC Wildfire S] WoefulDerelict:
In v2.2.1.4 one would have to select one partition at a time and back it up. Due to an issue the system would reboot after completing a backup operation on the first selected partition which is usually /system. As the system reboots after completing a single operation no other partitions are backed up and you must select them one at a time. This issue has been resolved in the latest version. The new version works as you stated. You must first select the partitions to backup and then swipe to start the operation. The default options should suit most users; however, you can add your recovery, SD-EXT and enable compression (prepare to wait if you do). The new version is up now and I strongly encourage updating.
[HTC Wildfire S] king_lud:
I have updated and, yes, the issue is fixed! Many thanks!
[HTC Wildfire S] WoefulDerelict:
Q: Is TWRP compatible with ROM Manager?

A: To the best of my knowledge no, currently it is not. ROM Manager and CWM are designed to work together. TWRP has a similar relationship with GooManager. For best results I'd use GooManager with TWRP and ROM Manager with CWMR.

This isn't to say that you can't force things to work together. ROM Manager never checks what is actually in your recovery partition. It instead pulls the information from files it stores on your device. If you install the current, compatible version of CWMR through ROM Manager it will write files that reflect that to the SD Card. You can then manually install any other recovery and ROM Manager will be none the wiser. This can be very effective if you want to use newer, unofficial versions of CWMR with ROM Manager; however, TWRP expects commands passed to it to be formatted differently than those CWMR and ROM Manager use leading to some very unreliable behaviour.
[Xperia Arc Android Development] kes4817:
Great works!

but after flashing this kernel, i cant reboot into recovery. plz check this!
[Xperia Arc Android Development] svanteson:
But you can get into recovery by pressing the home button when booting, right?

I'm not sure but I think I have seen the reboot into recovery problem with the official FXP kernel too. Can someone confirm this?

If so, we have to wait for a fix in upstream.
[Xperia Arc Android Development] Ritmasz:
Rebooting to recovery takes for ever, or just to say it does nothing but stucking in endless loop.

Also could you add intellidemand and some schedulers?

EDIT: it actually rebooted after ~10+mins