yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] Cozume:
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.

And I don't have a backup, but do I really need one if I can flash the factory images?
[G2 Q&A, Help & Troubleshooting] Tyberius777:
Okay so here are the steps I've done so far.

1. My phone is rooted and verified rooted with Root Checker Basic and have Super Su installed to grant super user privileges and Rom Manager is listed as being granted super user.

2. I've installed Rom Manager

3. I've selected Recovery Setup, Install Or Update Recovery for ClockworkMod Recovery, and selected LG G2 vs980 Verizon.

4. It asks me if I want to flash the "touch" version but I leave No selected and proceed to Flash ClockworkMod Recovery.

5. After it downloads (I paid the 1.99 to download it instead of manually doing it to support the devs) and flashes it says "Successfully flashed ClockworkMod recovery!".

6. It then asks me if I want to upgrade to touch recovery which I decline.

7. I then go to "Backup Current Rom" and then click okay for the backup name.

8. The phone then reboots, shows the lg logo, then stops at an android laying down with an exlamation mark coming out of his chest.

9. If I just let it sit there without rebooting it will auto reboot after a minute or so. after the phone reboots and I check the clockworkmod folder there is no backup file (of course because it never happened)

Any ideas as to where I'm going wrong? Do I need to buy the touch version for this to work or is there a painless free way to do this that I'm not aware of?
[G2 Q&A, Help & Troubleshooting] tdevaughn:
Rom manager is the problem. It doesnt work on this phone. Use flashify or freegee to install recovery. Personally see no need for rom manager ?
[G2 Q&A, Help & Troubleshooting] Tyberius777:
Ah I see, okay so I went ahead and installed Freegee for $1. On the orange and green screen it has the options to "Backup EFS", "Restore EFS", "Restore all backups", "CWM 6.0.4.6", "CWM 6.0.4.7", and "TWRP 2.6.3.3".

Is "Backup EFS" the same option that ROM Manager had to "Backup a complete image of my phone"?

If so does it just save one simple file that can be used to restore the phone should I mess it up while messing with the phone?
[G2 Q&A, Help & Troubleshooting] freebee269:
backup efs doesnt back up the image of your phone. this is drive partition info needed in case you corrupt a partition. it will save an efs zip file that can be used in recovery.
[G2 Q&A, Help & Troubleshooting] tdevaughn:
Efs is a file of important data about your phone, similar to bios on a computer.

To back up you're rom and data you boot into recovery and use the backup option inside the recovery
[G2 Q&A, Help & Troubleshooting] aronline:
I also install ROM Manager for my D802 and I also tried to Back up the ROM. Then after reboot display not working. Only showing some white and blue lines on black background. Please help to solve this.
[Galaxy S III Q&A, Help & Troubleshooting] Mamoun14:
Hi,

I attempted to root my friend SIII using odin as usual, unfortunately it failed and I'm stuck with "an error while upgrading the firmware". Apparently the download mode shows that the phone is SGH-i747, while I'm pretty sure before the phone was bricked that the about phone screen showed that it's the international (GT-I9300) variant. Now I'm not even sure what stock firmware to re-install. note that behind the battery the model is shown to be GT-I9300 too.

Is there a way to verify the model number while the phone is soft bricked? I wish I thought of checking of how much RAM at least this phone had before rooting it but unfortunately I just thought the about phone screen is enough.
[Galaxy S III Q&A, Help & Troubleshooting] jonty_t2:
As far as I know gt-i9300 is internationl version of s3
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
You've used the wrong file, if the label says i9300 then files for the i747 will brick it. You can try flashing a full i9300 stock rom, but I wouldn't hold out much hope.
[Moto G Q&A, Help & Troubleshooting] bdsr:
Hello guys!

I bought a Moto G XT1033 because was cheaper, but I use only one sim card.

I want to be, if anybody know how disable or hide the second sim card icon in the notification bar.

I tried commenting the line persist.multisim.config=dsds in the build.prop file, the icon hide in the task manager, the sim card manager hide, but any sim card dont work, and them I uncomment the line and both sim card work again.

Thanks

PS: Sorry for my poor english.
[Moto G Q&A, Help & Troubleshooting] invictussevenfold:
just flash retail GB ota 4.4.2, only work single sim, acctually this way changed your moto g dual sim to moto g single sim
[Moto G Q&A, Help & Troubleshooting] ffosilva:
After erasing this line, flash fsg.mbn from single sim firmware (not USA) and erase modemst1 and modemst2 partitions. Will work. =)
[Sony Xperia M] stm999999999:
[SOLVED]

Hi!

Is there a way to root the actual firmware 15.1.C.2.9? framaroot 1.9.1 (install superSU, Gandalf) gives me a "Success, ..." and then a reboot. But nothing happens to root.

EDIT: Forgot to enable USB-Debugging before.
[Sony Xperia M] giridhargp:
You need to do it severel times, how did you get that FW
[Sony Xperia M] stm999999999:
it worked fine with one time run of framaroot - if usb debugging enabled :cyclops:

And I got the fw via PC Companion.
[Sony Xperia M] kirev:
Cydia Impactor. Google for details for Xperia M
[Sony Xperia M] giridhargp:
But it doesn't showing any update
[Sony Xperia M] dunc4n88:
I think it's a typo meant to be 15.1.C.2.8
[Sony Xperia M] kirev:
https://www.google.com/search?q=cyd...google&sourceid=chrome-mobile&espv=1&ie=UTF-8
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] NerroEx:
I downloaded some stupid app that could mess with the GPU, and it said it was going to install files, (yes it needed root) and then I think it said there might be a black screen, and to reflash it again or something, and now my screen boots on, and stays black. If i hold the power button to turn it off, it turns back on itself, shows the Note 10.1 2014 edition logo, and stays black... PLEASE SOMEONE HELP PLEASE PLEASE :crying:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] benni_1994:
Try downloading a stock Rom for your device and flash it via Odin in download mode (volume down + power button) .

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] NerroEx:
Well, I went to a website with Stock FIRMWARE, if thats the same thing... IDK if youll be able to provide links here, but one will be much appreciated please...
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] benni_1994:
Please let us know your Model Number ( P600 =wifi only variant / P605 = lte variant)

Gesendet von meinem SM-P600 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] NerroEx:
Yes, I have the wifi ONLY SM-P600
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] benni_1994:
http://xdaforums.com/showthread.php?t=2618509

Here you go :) you can find the download in the first post and the instructions in the third post.

Gesendet von meinem SM-P600 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] NerroEx:
its dowloading, and i should have something in an hour, I love you! haha ill report back to say if it worked or didnt
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] NerroEx:
Worked.:cowboy:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] benni_1994:
Good to hear :)

Gesendet von meinem SM-P600 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] bulvine420:
This thread was intense :) was holding on to the edge of my seet to the end.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dionesisjohn:
Unbrick tablet

From your web broswer do a search for stock rom for your tablet, it should be a zip file within that zip file a 1.5 gb file with the extintion at "MD5"

open ODIN and point Odin to the file you downloaded.

Go to your tablet press the volume - and the power at the same time

when prompt press volume +

Contect the tablet to your computer and from press start button

(make sure you have drivers installed on your computer.)
[Miscellaneous Android Development] Restl3ss:
This is a DEV thread, this is not yet working

This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.

Instructions:

1. reboot into cwm / twrp, whichever you use

2. full wipe (do not come with issues if you dirty flashed)

3. install zip.

4. Enjoy!

Download link:

Stock deodexed + rooted + overclocked
[Miscellaneous Android Development] bil4554lel:
problem

Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
[Miscellaneous Android Development] DuceTheTruth:
E signature verification keeps failing
[Miscellaneous Android Development] atmu5fear:
Not sure, haven't tried to install this yet, BUT when in recovery, given you have a custom recovery installed, you shouldn't be trying to "apply update from zip" you should be selecting "install from zip". If you are using a stock recovery, you won't be able to flash a ROM. You need to flash a custom recovery such as twrp or cwm using Odin from a PC.

---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------

I have this old gem of a phone and have been looking forever for a custom ROM. Don't know where you pulled the stock from as I've been trying to dump it off the phone unsuccessfully to mod with Android kitchen. I'll flash this and update with my results :)
[Miscellaneous Android Development] atmu5fear:
I get

E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.

Using CWM 6.0.2.8
[Miscellaneous Android Development] Bibounet:
Hi, i get too the same error. I used CWM 6.0.3.1

What we can do it for help you and stabilize ROM ?
[Miscellaneous Android Development] atmu5fear:
I'm definitely interested in developing a custom ROM for this phone. I bought this phone nearly two years ago, and although I have since upgraded, I seem to always have use it as a back up when my t989 has issues. I know there is a ton of demand for a custom ROM for this phone. I was reading a bunch about META-INF folders and Android kitchen for developing a ROM without having a current base to work with. I'll look into it a bunch more throughout the week, this weekend etc. See if I can get a flashable zip after deodexing and overclocking using the thread the OP of this one used. I read on another forum, after googling "cwm status 255" that this has to do with the updated-binary file in the META-INF folder. The suggestion that worked for the op of that thread was to take the updated-binary file from another flashable zip (for the same phone) and use it to replace the updated-binary file in the zip giving the 255 error. So I took the file from the deodexing zip for this phone and replaced it, not expecting it work, but just to see. Cwm no longer gives the 255 code, but still aborts the installation, with no code given. So it seems this very well could be a start.
[Miscellaneous Android Development] atmu5fear:
Did you pull your META-INF folder from this thread

I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem
[Miscellaneous Android Development] Restl3ss:
That may very well be it, I'm gonna change it and reupload

Check back in a bit. Appreciate the help
[Miscellaneous Android Development] Restl3ss:
I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role
[Miscellaneous Android Development] atmu5fear:
I just threw together a flashable zip of this rom quickly on android kitchen. I used the META-INF folder from the thread I previously linked to. It's been deodexed and rooted, but I didn't bother with the overclock. Once we can get a flashable zip that works, i figure we'll go from there. I'm going to flash it to the phone now, and see if it will complete and boot.

I'm getting a status 0 error code. I'm going to rebuild without converting to edify. Will update
[Miscellaneous Android Development] Bibounet:
Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously ;). ty for your great work.
[Miscellaneous Android Development] atmu5fear:
The overclock is built into the kernel, clocks it from 800mhz to 1000mhz, any one who wants to run it without the higher clock, can just use any CPU control app and set the max to 800.

Without modding the kernel you actually can't overclock past 800mhz using any CPU control app.

---------- Post added at 03:28 AM ---------- Previous post was at 03:20 AM ----------

The Tab 3 runs on intel and the discover runs on ARM.

From everything I can find this is definitely the problem. Although just replacing the binary itself, and rebuilding hasn't seemed to accomplish anything other than no longer giving the error code. Just aborts. I've read your updater-script and none of the ui messages show up or anything from within that script during install.
[Miscellaneous Android Development] atmu5fear:
[MENTION=5378432]Restl3ss[/MENTION] I swapped out the binary from another flashable zip for the same phone, from within the kitchen using your flashable zip. Kept your updater script and other than that the only other change was I zipaligned. I rebuilt it, flashed it. The install doesn't abort, and completed. But none of your ui code from script appears during install, and nothing actually installed to the phone, it just boots straight into recovery. Since I have no idea how to decipher what I'm reading in the binary using notepad++, I'll leave it to your expertise to sort out the rest. I'm only just getting into this developing bit and so far have reached my limit of what I can help you with, as far as getting a base to flash and install successfully. I tried to get a report using adb logcat after it kept booting into recovery but the log remained empty.
[Miscellaneous Android Development] Joel-Tang:
just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)

Installation aborted."
[Miscellaneous Android Development] atmu5fear:
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho :)
[Miscellaneous Android Development] Restl3ss:
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.

if boot flashed successfully you should be able to set your cpu to 1000 mhz
[Miscellaneous Android Development] atmu5fear:
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
[Miscellaneous Android Development] Restl3ss:
the more information you can get me the better, thanks a ton for the help
[Miscellaneous Android Development] Joel-Tang:
Cool. I didn't back up my ROM before trying this. Does anyone know where I can get the original ROM to flash with CWM or ODIN?
[Miscellaneous Android Development] atmu5fear:
Doesn't exist, always back up before flashing. Once we get a working flashable zip I'll be able to convert that to an Odin flashable tar.md5. The best I can do is upload my cwm back up ( I have one that was made after a fresh factory reset, so it's the same as a stock zip or tar, just have to restore it from recovery. I'll try and up it and send u a link tonight
[Miscellaneous Android Development] atmu5fear:
You should consider putting a note on the OP, just saying this is not working yet.

Here's what I pulled from recovery.log. This is after I swapped out the update-binary for one from another phone running the same CPU, then rebuilt it. Nothing else was changed. According to what happens during flash in recovery, you would expect it to have worked. Except it doesn't, the log will probably tell you why. Before I flash I wiped system and data/cache, your script starts after the ADB Sideload. Parition table is included at top. I've tried running it with a few other updater-scripts from other ROM's written a bit differently, and just changed the partition table to match the phone, but same end result. Flash completes without errors, but nothing actually installs.

atmu5fear

Text wouldn't fit so I've just attached the log file. If using linux, text editor should organize it clearly enough, if windows, notepad++

(UNZIP FIRST, .log files are invalid format for attaching to xda)
[Miscellaneous Android Development] atmu5fear:
You can't flash this with CWM, you MUST extract this to the root of your sdcard, and restore it from cwm recovery (it is a back up, just make your it's contents end up in your clockworkmod/backup/ folder on your sd.

http://d-h.st/vOA
[Miscellaneous Android Development] Joel-Tang:
Am I the only that can't get these download links to work? What's the trick? Which download button do I need to push, I tried all of them but get anything but the file. :eek:
[Miscellaneous Android Development] atmu5fear:
If you're on your phone, click the little download button that's black. It will download mobogenie (which I just delete) and the file ur trying to download... pc will just download the file. Use your stock browser if you usually use a third party one
[Miscellaneous Android Development] Joel-Tang:
I managed to get it to work, but Chrome and internet explorer couldn't download the file. I had to use Tor Browser.
[Miscellaneous Android Development] atmu5fear:
Weird, I use chrome, works fine. Internet explorer... well when does anything work with that? Lol. Glad you got it tho
[Miscellaneous Android Development] Restl3ss:
Can someone do me a huge favor?

I need someone to open terminal on their discover and type

dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/system.img

then send me the resulting system image from the phone.

With that I should be able to make an Odin flashable tar.md5 pretty quickly
[Miscellaneous Android Development] atmu5fear:
I managed to get a flashable zip working. I had to rewrite the updater script, which I based off the stock koodo script for 4.0.4 on a galaxy s2x. I used the boot.img from [MENTION=5251250]shifattk[/MENTION]'s GUIDE. I managed to get your zip flashing succesfully using my updater script, but the samsung key board stopped every time I touched it. So i pulled the system folder from my stock running rom, left it odexed. I added root and busybox and removed bloat and added a few lighter apk's. I've uploaded it here http://xdaforums.com/showthread.php?p=50886344. Have a look at the updater script. You should be able to use it (without the personalized ui_print) and flash yours no problem, but i'd be interested to know if your keyboard works. I couldn't so much as sign into my wifi without it crashing. Don't know it it had to do with it being deodexed, or if there was something corrupt in the system folder, or what. I'm going to continue with the custom one I made (deodexing, zipaligning, etc), so I'll keep you posted. Hope you get it sorted out, and again, try using my updater script see what happens :)
[Miscellaneous Android Development] Restl3ss:
Thanks for the good work! Gonna try the updater-script tonight and see what happens. If the Sammy keyboard isn't working I'm not gonna bother to fix it, i'll just replace it with the Google keyboard (which i know for sure works on this device). If working, I'll re-upload and start working on my custom ROM intentions for this device (I have one in mind which I'm gonna call Chronic). cheers
[Miscellaneous Android Development] atmu5fear:
That reminds me, Bluetooth wouldn't turn on either. After keyboard kept crashing I was gonna just send the Swype apk from my t989, but Bluetooth wouldn't start. That's when I decided to use own system folder still odexed. If you are still having problems, I can throw together the stock zip tonight using my script and system folder. Use that as a base, instead of going through the head ache. Obviously the only difference would be that it's odexed. Mines pretty close to stock any way, just swapped the launcher and changed a few apks. I'm going to go for pure custom, it will be called Open Atmosphere. So if we're both going to do the same thing, maybe we could collaborate, or at least contribute to each other's project. PM me and I'll shoot you some contact info.
[Miscellaneous Android Development] atmu5fear:
Three versions of stock ROM's to use as bases for customs, or to recovery your phone after testing goes bad.

http://xdaforums.com/showthread.php?t=2677332
[Miscellaneous Android Development] DuceTheTruth:
black screen of death

I've been researching this phone for a few months now. It has since become my test phone as I now have a GS3...rooted and running various different ROMS....Currently running Slimkat 4.4.2.

My Discover mysteriously died one day while charging. I plugged it into the charger like I normally did everyday after work and a few hours later went to unplug the phone...and I noticed that the screen was frozen.

I hap to pull to the battery to get it to restart. Upon rebooting the phone I got/get the Samsung logo along with the yellow triangle(I was rooted b4 this happened for about a good month)....then the screen goes blank...but you can see it is still lit...although black....and thats it.

I've read somewhere that some think it is a hardware issue. But I find that weird because I can still boot into Download and recovery....Odin still sees the phone also.

But when I try to flash cwm from http://xdaforums.com/showthread.php?t=2201341 everything seems to work until the phone reboots and I get the same issue....

Also, I dont think CWM ever flashed to the phone because I still have the stock recovery.
[Miscellaneous Android Development] atmu5fear:
That definitely sounds hardware related. I would think if it was a software issue cwm would flash from Odin? I haven't had a stock recovery on a phone for a long time, but are you able to restore a back up? I'm wondering if someone could make a back up from their device that you could restore through the stock recovery, but I don't remember if back UPS and restores are even possible with stock recovery
[Miscellaneous Android Development] DuceTheTruth:
For one I'd like to thank you for such a speedy response. And 2....after all these months I've figured out that I'm an idiot...smh

http://xdaforums.com/showthread.php?p=51320664

I fixed it!!!!!!!