yashsingh1/xdaforums huggingface dataset:
[Galaxy S III General] blind0wl:
Awesome, thank you very much for at least validating I'm not alone!! Sorry about the wrong area for the post. I was going to look at SlimKat this evening until PA got sorted out a bit more.

Cheers
[Asus Transformer TF701] Theaccomplice88:
Has anyone been able to find skins for the keyboard dock? I had one on my tf201, but I haven't been able to find any for the tf701.
[Asus Transformer TF701] sbdags:
I had a skinomi on my tf201 - do they do tf701?
[Asus Transformer TF701] Theaccomplice88:
for the tablet only, not for the dock.
[Droid RAZR M Q&A, Help & Troubleshooting] cpspecial:
Hey all, thanks for looking. I'm rooted on the latest JB ota and every time I try to install KK it stops about halfway through and boots back up notifying me it failed. I don't have any custom ROM installed. In fact, I would prefer to return to complete stock and then do KK but I can't get find an answer as to whether I can fastboot with the latest JB ota. Thanks for any advice in advance.
[Droid RAZR M Q&A, Help & Troubleshooting] samari71:
i have the same problem does yours stop halfway thru installing and then a android with exclamation point appears
[Droid RAZR M Q&A, Help & Troubleshooting] cpspecial:
Yes indeed it does. Exactly the same issue it sounds like.
[Droid RAZR M Q&A, Help & Troubleshooting] xKroniK13x:
32853345 30

You can flash a stock ROM through RSD or FastBoot on any version of xt907. Just turn it off, hold volume down and tap the power button and fastboot will appear. Flash using your favorite method. If you're locked, you can flash an update or the same version of your ROM, but you cannot downgrade.
[Droid RAZR M Q&A, Help & Troubleshooting] jrk190:
I did that, and I still can't get the update to work.
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
root had my update failing too. i just did a restore with RSD and stock JB firmware. took the KK update fine after that.
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
hey please give me the firmware which you flashed?? please give me the link i also have to update to KK but i rooted the phone and the same thing happens it stops. i want to flash a new JB firmware and the firmware i downloaded doesnt seem to load on RSD lite please give me the proper firmware which loads on RSD LITE properly. i need help!!please
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
here ya go!

http://sbf.droid-developers.org/

click on 'Droid Razr M' (XT907). i used the firmware on the bottom.
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
I used the exact sbf but it wont load in rsd lite it says either xml file is wrong and bla bla please help me !! what should i do???
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
did you modify the XML file? read this. you have extract the firmware contents. then modify the XML file. save it (as XML not TXT) and then use that file in RSD.

http://www.andromods.com/tips-trick...oid-razr-m-xt907-stock-original-firmware.html
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
yes i tried but i didnt made sure to save as XML let me do it right now I will let you know btw thanks alot!! please stand by brother i really need to flash this sbf on my phone :P

---------- Post added at 02:14 PM ---------- Previous post was at 02:06 PM ----------

ok so i tried you method i edited the XML file like they said no get var no oem lines still is the same error and i am editing the XML file in zip i didnt extracted may this be the problem??
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
i extracted mine from the zip. easiest way to make sure you save the XML file correctly.
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
thank youu sooooo much!!!! MAN !! you saved me ok the mistake what i was doing was that i was editng the XML file and was puting it in the zip again i wasnt extracting it

let me clear for the folks who are doing mistakes just like me

download your sbf first

extract it in C (prefer C drive always for sbfing)

edit the xml file in the extracted folder

go to rsd lite and load the exact xml file that you extracted earlier (no need to zip it back!!)

and voila :p

special thanks to Chuck Solid made my concept clear

i used this XML its working like a charm

<?xml version="1.0"?>

<flashing>

<header>

<phone_model model="SM_JB_VZW_CFC" />

<software_version version="smq_vzw-user 4.1.2 9.8.1Q-94-1 77 release-keysSM_BP_101032.021.32.80P" />

<interfaces>

<interface name="AP" />

</interfaces>

</header>

<steps interface="AP">

<step operation="oem" var="fb_mode_set" />

<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" />

<step operation="oem" var="fb_mode_clear" />

</steps>

</flashing>
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
right on man! good deal! enjoy the update. i needed (2) reboots of the phone before it settled down but after that it runs smooth like butter.
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
yeah i did it completely flashed new sbf phones is back to factory state now i am gonna go ahed and download the KK update! :D P.S in first boot my phone worked like a charm didnt need to do more reboots. and thank you so much man!!! Thanks alot!! :good::good:

---------- Post added at 03:22 PM ---------- Previous post was at 02:43 PM ----------

now another problem please help man i flashed everything properly and phone seems to work great now i have to update to KK update now when i come in my system updates it says "System updates" is not available without a motorola service account there are 2 options cancel and setup when i press setup nothing happens just a blanks screen with "communicating with server please wait" nothing happens i really need to update it to KK please help me my google account is logged in and still nothing happens its not getting the update.. the update started like a charm before the sbf flash. please help man
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
sounds like the 'motorola services' isn't running. try this: do a 'factory reset' inside 'settings'. when the phone restarts DO NOT set up your google account. agree to the motorola crap but SKIP google sign in. this will make sure nothing is loaded from the playstore. not even your contacts. skip over the verizon contact restore and accounts. then try the update again. that's what i did after RSD. give it a shot.
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
ok so now the service is working but it says check for update is not available at this time.. now what to do? :confused:

---------- Post added at 03:44 PM ---------- Previous post was at 03:41 PM ----------

and i didnt factory reset after doing the RSD i didnt do any resets it just got past through the service thing automatically now its stuck on "Check for update is not available'

i did 3,4 reboots after it got past through the service thingy
[Droid RAZR M Q&A, Help & Troubleshooting] chuck solid:
keep checking. my kid lost his update notification yesterday. he saw it at school but waited to download it till he got home and on wifi. when he got home it kept saying "no updates available" until about 9 o'clock last night. if you can't wait, these guys are playing with a download of the OTA:

http://xdaforums.com/showthread.php?t=2752011
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
thanks alot man i think i will download this OTA or i will wait becuase i am on a slow network it will take about 2 hours for this file to download well thank you so much for your help i really appreciate it :good::good:
[Droid RAZR M Q&A, Help & Troubleshooting] cpspecial:
Hey guys, thanks so much for your responses. I was just unaware that I could RSD, I felt like I read somewhere that once I took the latest JB ota I couldn't RSD at all. Thank you again, I'll report back my findings.
[Droid RAZR M Q&A, Help & Troubleshooting] cpspecial:
Is 98.30 the newest firmware? My current firmware is 98.18.94, so I'm not sure which one to RSD. I can't even find 98.18.94 anywhere. I'm just not wanting to brick my phone haha.
[Droid RAZR M Q&A, Help & Troubleshooting] whizinc:
which firmware you exactly want to flash i guess 98.30 was the latest JB firmware.
[Droid RAZR M Q&A, Help & Troubleshooting] cpspecial:
Yea my phone reads out at 98.18.94 but for some reason I thought that was the latest OTA.
[Android Q&A, Help & Troubleshooting] andreey:
So guys, Im new in this forum.

And just wanted to mention that Im a noob in programming.

I have a little issue with my phone. It is an iOcean X7 Elite with MT6589 progressor.

After getting bored with stock andriod I wanted to test the MIUI os and flashed it to my phone. It worked fine, but i didn't like the the rom that much and wanted to flash back to stock. I downloaded the stock rom for my Phone and flashed it with SP Flashtool. It finished without any error.

But the won't turn on. It wont even show the bootlogo. My PC does not recognize the Phone as a Phone.It says: Unknown USB device.

I have tried installing the drivers and used several flashtools (i case there is a version out there getting the job done).

Im really frustrated.

Last time I had a simmilar problem my phone showed the bootlogo and got stucked. But i got it to work by flashing. Now I have no idea what to do.

I'm already thankful for your help.
[Android Q&A, Help & Troubleshooting] DamienMc:
Was the backup your own?

Try to flash only the preloader, then if that goes thru you can do the full restore again... Come to think about it you might need diff drivers, or maybe meta mode (-vol and power)

I'm not at the computer atm sorry I can't be more help

-D
[Android Q&A, Help & Troubleshooting] andreey:
Well, it always stopps at this point. No matter what i try to flash.

What are diff drivers?

View attachment 2744764
[Android Q&A, Help & Troubleshooting] DamienMc:
Well it's being recognized so it's not a driver issue.

Is that your backup?

Do you have a backup?

Your not getting any errors?
[Android Q&A, Help & Troubleshooting] andreey:
Have no backup.

It just breaks up the process when reaching the 100% of the red bar.

From time to time I get the drivers issue error. Nothing more.
[Android Q&A, Help & Troubleshooting] andreey:
okay guys.

i tried an other stock rom version and now it says:

"BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032)"

Does anybody know what this means?

Thanks a lot for minding.
[Android Q&A, Help & Troubleshooting] kampret06:
I think just do the full flash.

And DO NOT CONNECT your phone until the progress bar have passed the violet colored progress bar.
[One (M7) Q&A, Help & Troubleshooting] Tableuraz:
Hi !

I am currently encountering an issue with my HTC one, it worked well, until I connected it to my computer last night.

Since then, the phone keeps shutting himself down after 1 minute or so.

I've the latest Viper ROM, ICECAVE 5.3 and ElementalX 14.1

I've tried everything I could, I wiped the dalvick and cache partition, re-flashed the kernel, re-flashed ICECAVE, nothing helped.

I can't flash the ROM as I don't have the ZIP on my phone's memory.

What bugs me out is that everything worked fine until I connected it to my computer, it's not logical at all, I did this thousands of times before and did not flash anything new since days.... :confused:
[One (M7) Q&A, Help & Troubleshooting] Tableuraz:
So, after searching around the internet, I found that I could use adb in Recovery, so I pushed the ROM file and flashed it with a total wipe, everything is fine now !

(I had issues regarding adb push and sideload, but it was because drivers issues, I just used an other computer and it worked well !)
[One (M7) Q&A, Help & Troubleshooting] penhoc122:
i flashed miui v5 rom on my phone, but camera not working, someone said he flashed kernelv2 and camera work great
[One (M7) Q&A, Help & Troubleshooting] clay21:
Attached....flash in recovery.
[One (M7) Q&A, Help & Troubleshooting] penhoc122:
kernel

help me ????
[One (M7) Q&A, Help & Troubleshooting] penhoc122:
thank you

it's work great, tks u so much
[One (M7) Q&A, Help & Troubleshooting] toletterese:
I had htc desire it was good phone but i just got a samsung galaxy note II but its so big!

I wanna go and change it tomorrow?

Well? Which smartphone would you reccomend me?
[One (M7) Q&A, Help & Troubleshooting] AvrX:
SGS II
[One (M7) Q&A, Help & Troubleshooting] MistahBungle:
And you're asking here why ? (This thread is going to be closed).
[One (M7) Q&A, Help & Troubleshooting] Stephen:
Thread closed.

Comparison threads are against forum rules.

Ghost
[Sony Xperia L] DJPRMF:
Hello,

So, today i was looking to install Link2SD (for those that don't know: https://play.google.com/store/apps/details?id=com.buak.Link2SD ) in my Xperia L, but i faced many problems. Most of the are becouse i have a locked Bootloader and im stuck with the stock ROM.

One of the requeriments to use the Link2SD is the support to init.d scripts. Most of the custom roms support this, but not the stock one, giving a boot loop.

After looked for a while, i notice that this topic doesn't appears to be here, so lets start creating... :D

Init.d allows execute scripts in the boot. In this guide i will focus in the Link2SD, but this will enable the init.d to ALL the apps and scrips. This works in ANY rom (at least, is supposed to) and also with locked bootloaders.

And after the blablabla, a "legal part":

Disclaimer

: I have tested this in my Xperia L, with a locked bootloaded and the last version of the Sony Stock rom. No problems so far, but im not responsible for

any damage, including data lost, nuclear wars or explosions!

But should be safe. Any problem just comment.

..:: Requirements ::..

- A Xperia L (duh...)

- Root access (use the search)

- A SD Card with some space (8 GB or more is recommended, unless you don't use the sd card).

- Link2SD - https://play.google.com/store/apps/details?id=com.buak.Link2SD

- Init.d Toggler - https://play.google.com/store/apps/details?id=com.broodplank.initdtoggler

..:: Steps ::..

First of all, you need of create a second Partition on the SD Card. I will not go in many details at this point. There are many guides about how to do this (http://xdaforums.com/showthread.php?t=1614700 - ONLY Point 1 to 4 ).

After create the new Partition, restart the system.

Now lets start the magic:

1 - Start (or install and start) the "Init.d Toggler" app.

2 - Just click in the button "Enable Init.d" .

3 - Restart your phone

If everything works fine, good. Now you should have support to the init.d! Yeahhhh :D

Now lets proceed to the Link2SD:

1- Open the Link2SD.

2 - Wait a few seconds and should appear a pop-up to creat the link2sd script, requesting to you select the File System of the second partition. Just do it!

3 - If the pop-up doesn't appear, go to the menu and press "Recreate mount scripts".

Always select the File System that you have used in the second partition. After that, reboot one last time.

And now, if everything works fine, you should have the Link2SD active and working fine!

Any question just let a comment! :)
[Sony Xperia L] DJPRMF:
Hello again,

Ok, so after the publish of the first message, some users appear to report problems with the SD card not being corrected mounted in the Android.

In some SD cards, after create two partitions, the first partition (used for the storage) appears cannot be mounted. Always appears a error about the

SD Card being empty of the filesystem damaged

.

The second partition, used in Link2SD, works fine. Is just the first one.

There is a way to bypass this problem using the NTFS filesystem.

So, first of all, you need a SD card reader in your PC. After that, is just needed to format the first partition (and

ONLY

the first) to NTFS.

Android doesn't handle very well NTFS, so is needed a new app to make it support: Paragon exFAT, NTFS & HFS+ (check the Google Play)

After install the app, just run it. He should mount the new NTFS partition and should now be usuable under the Android system. :)

Problem solved.

yeehhh :laugh::laugh::highfive:

Bug: The only bug that i found with the solution is the camera. Is not possible save photos to the SD card in this way. Only used the internal memory (should be enough for most of the users).
[Sony Xperia L] NothingLikeUs98:
Thankssss!! :)

Thanks a lot!!! Is working!! I've been serching for a solution for weeks!! :) :) :) :) :) :)
[Sony Xperia L] DJPRMF:
Glad that my little guide help you. :)

I spend weeks trying to make Link2SD to work in Xperia L. And i never realize that could be so "easy"...

Hope that help other users also. :)
[Sony Xperia L] EGY falcon:
FAILURE Link2SD package invalid when linking apps

Hi bro.

I got an error when I try to link any app in the internal memory with the SD Card, but the moving option is working well, but I need to link apps that is not movable so I don't lose there widgets.

* I tried to reinstall the app, also I tried to recreate the mount scripts then reboot, but nothing changed.
[Sony Xperia L] DJPRMF:
First, try install only in the phone memory (note that is not in the internal SD card).

Move the app to the phone space (if is not there) and, after that, create the link in Link2SD.
[Sony Xperia L] EGY falcon:
same result :(
[Sony Xperia L] DJPRMF:
I think that is something related with the app/link2SD compatibility, not a error from the smartphone.

This happends in all the apps? And those apps have been instaled from the Google Play?

Also, do you are in Stock rom? Or have installed custom ROM?

Try this:

1- Use "Recreate mount script" and reboot.

2- Use "Relink library files" and "Link dalvik-cache files" in Link2SD and reboot.

3- Use "Market Tools..." - "Market Doctor" for user & system apps.

Also check if USB Debugging is ON.
[Sony Xperia L] Holmes.Sherlock:
Xperia L Bootloop after mounting SD card using Link2SD

I am facing trouble in mounting 2nd partition (ext4) of the SD card using Link2SD in Rooted Xperia L. Like many people have faced. I experienced a Boot-Loop. After taking out the partitioned SD card, fortunately the phone boots fine. Even it boots without any problem with non-partitioned SD card, too.

There is unofficial solution of enabling support for init.d using apps like Init.d Toggler.

But, I find that there already an /etc/init.d directory exists. Inside, there are two scripts, viz. 00stop_ric and 11link2sd.

I failed to find any reference to this problem in the FAQ section of official website.

Should I go for Init.d Toggler solution?

What is causing this problem?

Is 00stop_ric the original mount script of Xperia L?
[Sony Xperia L] Holmes.Sherlock:
There is a minor problem in this solution. If the first partition of SD card is mounted usig Paragon App, it becomes accessible under following locations:

/storage/sdcard1

/ext_card

/mnt/ext_card

/sdcard1

Default System Storage Manager (Settings -> Storage)

Windows PC, when connected via USB cable

BUT, it does NOT get detected as an SD card under "Devices" list of ES File Explorer. It's annoying!
[Sony Xperia L] DJPRMF:
Are you using the stock ROM of the Xperia L?

The init.d scripts are not enable by default. The folder could be there, and also have scripts from others apps, for instance, but they will not work until the init.d support is enabled...

And about the "problem", is something difrent. The solution is intended to allow the use of the Link2SD app, not access by the ES File Explorer.
[Sony Xperia L] Holmes.Sherlock:
Exactly. But, what does Link2SD do so that Xperia runs into Boot-Loop? What I could find is /etc/init.d/11link2sd script. But, can only the presence of a script cause Boot-Loop?
[Sony Xperia L] DJPRMF:
Maybe its something in your end. Link2SD doesn't cause bootloop using the guide that i provide in the first message. At least with the stock rom and locked BL..

It WILL cause boot loop when the init.d isn't work correctly or something else is messing up with it.
[Sony Xperia L] Holmes.Sherlock:
You misunderstood, or may be I wasn't clear enough. Following your guide, it works fine.

But, I find it surprising why it boot-loop-ed initially, i.e. when init.d was disabled. It could fail to mount the partition, that is acceptable. But, how come just the presence of /etc/init.d/11link2sd script make it boot-loop?
[Sony Xperia L] DJPRMF:
Oh.. .:P

I think is becouse the phone doesn't have the init.d support enable by default. The folder is created, but the ROM/kernel doesn't have the support to execute the script...
[Sony Xperia L] Holmes.Sherlock:
Even before trying Link2SD, I had both /etc/init.d and /etc/init.d/00stop_ric script present. There are the leftover from the Getroot method I applied to root my Xperia. So, neither the phone not having init.d support nor the creation of init.d folder can be the cause of boot-loop.

Definitely, either the presence of /etc/init.d/11link2sd script or something else which we are missing (Developer of Link2SD, Akpinar should be able to correctly answer) is/are the cause of boot-loop.
[Sony Xperia L] Holmes.Sherlock:
Those who have installed Link2SD,

Can you check whether the following files are present after installing Link2SD

/etc/install_recovery.sh

/etc/init.d/11link2sd

In case /etc/install_recovery.sh is present, can you post its contents?

Does it create any script other than what I mentioned above to mount partitions?
[Sony Xperia L] Holmes.Sherlock:
Do you really think that not having support for init.d script can cause boot-loop? Shouldn't the script(s) be ignored straightway?
[Sony Xperia L] tomnhinho:
help,i dont understand much!!

im from asia.my eng arenot good at all.can you tell me how can i open app2sd if my phone bootloop again and again?