Database Info

HELP! HELP!

hi, i have a samsung intercept from vm. I used a SuperOneClick to delete some stock apps and somethings wrong my on-screen keyboard is completely gone and i keep getting this message saying something about the android process has unexpectedly ended please try again and some times it wont stop coming up and wont let me do anything. i deleted stock email app, some of the virgin mobile stuff I'm new to this as you can tell. please help and thank you

"the process com.google.process.gapps has stopped unexpectedly. please try again."

Rom and Recovery
I am assuming your phone is rooted so can you please tell me what ROM and recovery you are running?

its not rooted any more i used a temporary root i believe its on the stock rom i tried factory reset but it still the same without the apps and the missing keyboard, thanks for your reply

Adb?
jefe1026 said:
"the process com.google.process.gapps has stopped unexpectedly. please try again."
Click to expand...
Click to collapse
This tells me you basically deleted some system applications that support the Google applications like Gmail, Calendar, etc. Not a good thing lol. Next time when you are deleting "bloatware," don't delete anything that starts with com.google or com.system. These are the packages that help run android and google applications.
Incidently, Do you know what adb is? If so, have you ever used it?

ive seen adb when i ran superoneclick im tryin to learn all this i use to have an iphone and hackin that is pie compared to this cause there is so many android phones

Try Factory Reset
jefe1026 said:
ive seen adb when i ran superoneclick im tryin to learn all this i use to have an iphone and hackin that is pie compared to this cause there is so many android phones
Click to expand...
Click to collapse
Don't worry, the initial rooting process is the hardest part. After that, it only gets easier. Then you can put on whatever custom ROM you want and trust me, its awesome!
Anyway, I don't think you need to use adb juuust yet. Did you try to get to recovery mode yet and try to factory reset the phone?
To get to recovery mode on your Samsung Intercept, you hold, all these buttons at the same time, for a few seconds:
Volume Down, Call, and End buttons.
This will either bring you to recovery mode or have an option for recovery mode. Once there, there will be a setting to factory reset your phone. It will say something along the lines of "Wipe Data/Factory Reset" It won't delete anything on your SD card but wipes out all your apps and restores it to when you first used it.

yea i did that and the stuffs still missing : / im tryng to use the sw update to re install stock 2.1 but i keep getting "cannot open .bin file"

I had that problem too. What i did is connect my phone with samsung kies and that restored evrything back for me.
May that not help, try to flash it back with original firmware using odin
just search on this forum
This is the site that contains evry firmware of evry samsung phone:
samfirmware.com
you only have to register

i dont see my phone in the android section

I'm not having any luck with this... nothing seems to work

Don't Give Up!
jefe1026 said:
I'm not having any luck with this... nothing seems to work
Click to expand...
Click to collapse
Don't fret. You haven't bricked your phone yet.
Ok. I checked to see if any forum or site was hosting the original signed zip of the OS that came with your phone and I couldn't find any.
I have an idea though. Not sure if it might work but theoretically it should. Although your phone WAS rooted (aka. temporary root), its not anymore which means you don't have any custom firmware and are running stock.
IF you updated your phone to 2.2 froyo with the official update, then it should completely replace the OS and not only reverse the damage but upgrade it as well.
So you take the phone, put it into "Recovery Mode," and then use adb to push this zip (link below) on to the ROOT OF THE SDCARD. not anywhere else!
then in the recovery, select the "flash/update zip" option and select the new zip.
In theory, this should work. Cannot be sure so tread with caution!
Here is the link:
http://02ee24b.netsolhost.com/downloads/crowder/update.zip
This is the full article that explains how to root your phone after:
http://www.crawfordium.com/blog/?p=22
Best of Luck!!

Thanks I'll try it out

I got this "E:Error in /sdcard/update.zip (Status 7) Installation aborted. I tried formatting the sdcard and redoing it but i got same message again I also tried going into superoneclick and hitting unroot and it says its unrooted but i still get the (status 7) message :/

and the sw upgrade says cannont open .bin file

This might work!
I was reading through some Samsung Intercept forums for you and this looks promising:
http://forum.sdx-developers.com/int...e-to-froyo-2-2-with-no-baseband-modification/
Go through the first three steps and flash the stock 2.1 on to your phone and it should be restored to basic regular Android 2.1. It IS sprint's stock 2.1 for intercept not Virgin Mobile's but its ok because it doesn't replace Virgin Mobile's Baseband so its fine. Instead of seeing the Virgin Mobile boot up screen, it will show you a sprint boot up screen. No biggie.
Try it and tell me how it goes. remember to follow instructions carefully and to the tee.

OK NOW IM ON SPRINT 2.1 and my number works and now im going to try upgrading to 2.2 show i try doing it over the air or just do it manually?

i just did it manually now im going to try to root it

now how do i get superuser and all that good stuff with the roms i dont like the slapstick 1.4

[Completed] HTC Vivid won't boot, possibly after build.prop change

Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.

Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.

jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.

Thread closed.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

[Completed] i8190 S3 mini / soft-bricked / twrp is being a persistent %@$%$!

hi, S3 Mini i8190, this has me banging my head in the wall for past 18 hours after trying a dozen roms / stock / custom / various recoveries and the pit files.
A.) Initially, the phone wasn't rooting with the norms so i had to install a prerooted rom. Anyway, since it was the an almost look-alike of stock, i wanted to move to CM 12. So, for that i had to install twrp, now even after being rooted, the odin wasn't able to flash the recovery. So, i chose the twrp app and there i messed up, i thought it would be the latest version which it wasn't it was a 2.6....version which doesn't support the f2fs so i knew i have to get a newer version of the twrp, since then i have been trying to fix this but i can't, so much so i tried stock pit files all over the internet and i get error on all of them "Complete(Write) operation failed."
Every recovery / rom which can be flashed using odin, flashes "successfully".
1.) rom loads up but it stays in soft-brick. (doesn't progresses from the boot anim)
2.) recovery shows to have successfully flashed, but on the boot; no matter which recovery i put in, it always goes to the same version of twrp that was initially installed by the app.
I forgot to mention, it asked if the right place to flash is an area of the internal memory...mmc...something...and i was furious and i selected it; i guess thats where it all messed up.
i tried pit files, roms, recoveries, stock, custom, adb push, adb sideload, various versions of odin and all.
B.) the real reason for changing to a custom rom was; the phone was able to connect to pc in download mode/recovery without a difficulty; however within rom, it was only on charging mode. So i guess there is something wrong from earlier on.
now i'm sure there's no memory bricked since writing happens easily. I probably have written the recovery somewhere like within the cache partition that it never gets deleted and no matter what i flash, it always open up twrp of the same version.
Pit isn't flashing. Can i repartition / format the entire memory someway? *nand flash etc didn't work within odin too. same error as that of pit files.
Please guide, i don't want to lose this phone, i just bought a new battery.
should i also make this post within the s3-mini section?

Hello
Thank you for using XDA Assist.
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I invite you to post over your request in the below forum as our team of experts there should be able to help you:
Galaxy S III Mini Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
hi, S3 Mini i8190, this has me banging my head in the wall for past 18 hours after trying a dozen roms / stock / custom / various recoveries and the pit files.
A.) Initially, the phone wasn't rooting with the norms so i had to install a prerooted rom. Anyway, since it was the an almost look-alike of stock, i wanted to move to CM 12. So, for that i had to install twrp, now even after being rooted, the odin wasn't able to flash the recovery. So, i chose the twrp app and there i messed up, i thought it would be the latest version which it wasn't it was a 2.6....version which doesn't support the f2fs so i knew i have to get a newer version of the twrp, since then i have been trying to fix this but i can't, so much so i tried stock pit files all over the internet and i get error on all of them "Complete(Write) operation failed."
Every recovery / rom which can be flashed using odin, flashes "successfully".
1.) rom loads up but it stays in soft-brick. (doesn't progresses from the boot anim)
2.) recovery shows to have successfully flashed, but on the boot; no matter which recovery i put in, it always goes to the same version of twrp that was initially installed by the app.
I forgot to mention, it asked if the right place to flash is an area of the internal memory...mmc...something...and i was furious and i selected it; i guess thats where it all messed up.
i tried pit files, roms, recoveries, stock, custom, adb push, adb sideload, various versions of odin and all.
B.) the real reason for changing to a custom rom was; the phone was able to connect to pc in download mode/recovery without a difficulty; however within rom, it was only on charging mode. So i guess there is something wrong from earlier on.
now i'm sure there's no memory bricked since writing happens easily. I probably have written the recovery somewhere like within the cache partition that it never gets deleted and no matter what i flash, it always open up twrp of the same version.
Pit isn't flashing. Can i repartition / format the entire memory someway? *nand flash etc didn't work within odin too. same error as that of pit files.
Please guide, i don't want to lose this phone, i just bought a new battery.
should i also make this post within the s3-mini section?
Click to expand...
Click to collapse

Question Soft Bricked my SM-G998B ... any suggestions on how to get out of it?

I was trying to root my phone using Magisk but something went wrong during the final step, (was stuck on prism.img for +30 minutes)
Now, all I see is "An error has occurred while updating the device software" and at the top there is a red message "DN_FAIL_BLOCK_CUSTOM_BIN_OEM"
I have tried various reboot options to get back into download mode with no joy.
Even Smartswitch is not listing an "emergency recovery" option.
Any suggestion(s) as what I could do next?
Many thanks

Ok, I got it sorted
download the latest Odin
download the latest firmware for your phone + region
unpack it all somewhere
copy and then rename the CSC file to remove the .md5 extension
That will allow you to "unzip it" and inside it there is a pit file.
Open Odin and set the path of all the md5 files, except for the last one, (USERDATA).
On the PIT tab set the path of the file you extracted earlier.
Plug the phone in
Start
And it should reboot fine.
You phone was wiped, you will need to reinstall everything
Before messing around with your phone ...
Make sure you know what firmware you are using
Make sure you know your country code.
Hope this helps someone...

Hey siminfrance,
I noticed in restoring your phone you have to download firmware for a specific region. Does the region specific bloatware come back? I need the bloatware back
Thank you

dangercl0se said:
Hey siminfrance,
I noticed in restoring your phone you have to download firmware for a specific region. Does the region specific bloatware come back? I need the bloatware back
Thank you
Click to expand...
Click to collapse
Yeah, it has all the Samsung bloatware.
Not sure about all the countries, but in mine there is only one provider specific app and it gets downloaded automatically as soon as you first start the phone.
Make sure you get the correct Android version, (I got 12 in my case).