Database Info

I need an easier guide...

To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...

I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though

I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.

DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate

My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...

DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt

I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?

DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have

How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?

DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium

I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"

DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium

You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone

DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium

If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?

DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium

Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/

DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium

Is there perhaps any way to perform a ROM backup with ADB?

DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium

Root canvas 2 running on ics

WELL WITHOUT WASTING MUCH OF THE TIME IN RAMBLING LET US SIMPLY START THE TUTORIAL:HOW TO ROOT CANVAS 2 RUNNING ON / WITH ICS......WHICH IS AS SIMPLE AS PLAYING SNAKE AND LADDER.
ROOTING.....
first of all enable USB DEBUGGING in your phone.
now connect your phone to your pc.
slide down the notification bar and select'touch for other options'.
now select MEDIA DEVICE option from that menu.
THEN DOWNLOAD bin4ry rooting tool from here..
extract it to any folder and open that folder.
now open runme.bat file from there.
it looks like a green coloured command prompt.
now just press 1 and hit enter.
then it will take about 1-2 mins as it is coping files to your phone.
(during this process your phone may reboot several times.)
THEN AFTER SOME TIME YOU WILL SEE THAT YOUR PHONES SCREEN HAS LIT UP.
IT WILL ASK YOU TO ENTER ENCRYPTION PASSWORD AND THEN FULL RESTORE YOUR PHONE.
IF YOU HAVEN'T SET UP ANY ENCRYPTION PASSWORD THEN JUST SELECT FULL RESTORE.
then after completing the process it will say press any key to continue.
now close this tool and switch on your phone.
you will find an app named superuser in your phone phone.
INSTALLING CLOCKWORK RECOVERY.
DOWNLOAD CLOCKWORK MOD RECOVERY FROM HERE.
put that downloaded recovery file (image) in the root of your sd card i.e. outside any folders otherwise mobile uncle tools won't detect it.
install an app named mobile uncle tools. YOU CAN DOWNLOAD IT FROM HERE.
open it and select recovery update option.
it will look for recovery file in your phone and display the result.
from there click on the recovery file and then select yes.
this will flash clockwork recovery in your phone.
And with dis u r done wid al d procedure..
Cill out
Hit thanx if i helped

Link of bin4ry rooting tool- www.mediafire.com/?wadbxnnxa8kf4b4
Hit thx if i helped

Link of cwm recovery (already renamed to recovery.img)
www.mediafire.com/download/ued9c4iqn6cr086/recovery.img

Good one.
Thx...:thumbup:

Please help..
Hello Jatin, I have followed all the above steps carefully but still I'm unable to root my device. Please refer the following screenshots and help me as early as possible. Thanks in advance.

CM Punk said:
Hello Jatin, I have followed all the above steps carefully but still I'm unable to root my device. Please refer the following screenshots and help me as early as possible. Thanks in advance.
Click to expand...
Click to collapse
First thing that please do not quote the whole post especially the main one....as it simply makes the thread ugly.
when you ask any question in a particular thread it is obvious that you will be asking question related to that only...:cyclops:
AND REGARDING THE ERROR.....IT LOOKS AS THERE ARE MORE THAN ONE EMULATORS RUNNING AND IT IS GIVING ERROR BECAUSE OF IT.
DISCONNECT ALL OTHER REMOVABLE DEVICES CONNECTED WITH YOUR PC...
HAVE YOU FOLLOWED ALL THE STEPS AS DESCRIBED IN THE THREAD? AND DOWNLOADED ALL THE FILES FROM THIS THREAD ONLY??IF NOT SIMPLY DOWNLOAD THEM FROM HERE AND PLS FOLLOW ALL THE STEPS STRICTLY AS GIVEN IN THE POST..
TRY AND REPORT.
BEST OF LUCK.:good:

[email protected] said:
First thing that please do not quote the whole post especially the main one....as it simply makes the thread ugly.
when you ask any question in a particular thread it is obvious that you will be asking question related to that only...:cyclops:
AND REGARDING THE ERROR.....IT LOOKS AS THERE ARE MORE THAN ONE EMULATORS RUNNING AND IT IS GIVING ERROR BECAUSE OF IT.
DISCONNECT ALL OTHER REMOVABLE DEVICES CONNECTED WITH YOUR PC...
HAVE YOU FOLLOWED ALL THE STEPS AS DESCRIBED IN THE THREAD? AND DOWNLOADED ALL THE FILES FROM THIS THREAD ONLY??IF NOT SIMPLY DOWNLOAD THEM FROM HERE AND PLS FOLLOW ALL THE STEPS STRICTLY AS GIVEN IN THE POST..
TRY AND REPORT.
BEST OF LUCK.:good:
Click to expand...
Click to collapse
Thanks for the quick response.
What does more than one emulator means?
I don't have any other removable device connected to my pc, and yes, I downloaded all the files from this thread only. What else can I do? Where am I missing out?

CM Punk said:
Thanks for the quick response.
What does more than one emulator means?
I don't have any other removable device connected to my pc, and yes, I downloaded all the files from this thread only. What else can I do? Where am I missing out?
Click to expand...
Click to collapse
Emulator is a hardware or software used for duplication of behavior of main system to host system.
In short your pc is main system here and device is emulated system.
I think you should than turn on usb debugging and set device as media storage and try.
IF YOU ARE STILL UNABLE TO ROOT THEN TELL ME AND I HAVE ANOTHER METHOD FOR YOU.:beer: cheers.

[email protected] said:
Emulator is a hardware or software used for duplication of behavior of main system to host system.
In short your pc is main system here and device is emulated system.
I think you should than turn on usb debugging and set device as media storage and try.
IF YOU ARE STILL UNABLE TO ROOT THEN TELL ME AND I HAVE ANOTHER METHOD FOR YOU.:beer: cheers.
Click to expand...
Click to collapse
I was trying with usb debugging all the way through with media storage as default but still no success. What's the other method?

CM Punk said:
I was trying with usb debugging all the way through with media storage as default but still no success. What's the other method?
Click to expand...
Click to collapse
No just on usb debugging
And are you trying to run it as administrator?
Sent from my C1604 using XDA Premium 4 mobile app

icoolguy1995 said:
No just on usb debugging
And are you trying to run it as administrator?
Sent from my C1604 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. I'm doing exactly as mentioned above.I even tried it on another os of windows 7 and another laptop too, but to no avail.

CM Punk said:
Nope. I'm doing exactly as mentioned above.I even tried it on another os of windows 7 and another laptop too, but to no avail.
Click to expand...
Click to collapse
So here comes the second method.
FIRST DOWNLOAD THE FOLLOWING FILES:
1.Sp flash tools
link: http://db.tt/3JhQmUWh
Password of sp flash [email protected]
2.recovery image
link: www.mediafire.com/download/2j9rlu41ksnz83z/recovery.zip
3.superuser binaries
link: download.chainfire.eu/310/SuperSU-v1.04.zip
Extract sp flash tools and recovery.zip to get recovery.img( .img is the file type)
open sp flash tools(run as administrator)
.
click on scatter loading option and browse for the file in that folder
where you have extracted flash tools.you will find a text file...select it.
now a list of files will be shown in the flash tools
check RECOVERY file
now select RECOVERY FILE by single clicking on it
browse for the location where u have placed the downloaded recovery image and select the extracted recovery image.
NOTE-IF YOU FIND ALL THE FILES INCLUDING RECOVERY FILE ALSO SELECTED THEN MAKE SURE TO DESELECT ALL EXCEPT RECOVERY.
NOW SWITCH OFF YOUR PHONE AND REMOVE THE BATTERY
now click on download option in flash tools.....
connect your phone in 'BATTERY REMOVED' state
wait till the process completes....
after the process has been completed it will show DOWNLOAD OK
close sp flash tools and disconnect ur fone from ur pc and put the battery back.
WITH THIS U HAVE FLASHED CLOCKWORK RECOVERY ON YOUR CANVAS 2.
place the superuser.zip file in your phone's sd card(prefferably internal)
but do not extract it.
now BOOT INTO CLOCKWORK RECOVERY MODE by holding power key+vol.up key+vol.down key.
select install zip from sd card
then choose zip from internal sd card(if you have placed it in internal sd or otherwise select choose zip from sd card)
select the above placed zip and flash it.....
go back and reboot system
AFTER REBOOTING YOU WILL FIND A SUPERUSER APP IN YOUR PHONE
THIS MEANS THAT YOUR PHONE HAS BEEN ROOTED
Hit thx...it wont cost u

[email protected] said:
So here comes the second method.
FIRST DOWNLOAD THE FOLLOWING FILES:
1.Sp flash tools
link: http://db.tt/3JhQmUWh
Password of sp flash [email protected]
2.recovery image
link: www.mediafire.com/download/2j9rlu41ksnz83z/recovery.zip
3.superuser binaries
link: download.chainfire.eu/310/SuperSU-v1.04.zip
Extract sp flash tools and recovery.zip to get recovery.img( .img is the file type)
open sp flash tools(run as administrator)
.
click on scatter loading option and browse for the file in that folder
where you have extracted flash tools.you will find a text file...select it.
now a list of files will be shown in the flash tools
check RECOVERY file
now select RECOVERY FILE by single clicking on it
browse for the location where u have placed the downloaded recovery image and select the extracted recovery image.
NOTE-IF YOU FIND ALL THE FILES INCLUDING RECOVERY FILE ALSO SELECTED THEN MAKE SURE TO DESELECT ALL EXCEPT RECOVERY.
NOW SWITCH OFF YOUR PHONE AND REMOVE THE BATTERY
now click on download option in flash tools.....
connect your phone in 'BATTERY REMOVED' state
wait till the process completes....
after the process has been completed it will show DOWNLOAD OK
close sp flash tools and disconnect ur fone from ur pc and put the battery back.
WITH THIS U HAVE FLASHED CLOCKWORK RECOVERY ON YOUR CANVAS 2.
place the superuser.zip file in your phone's sd card(prefferably internal)
but do not extract it.
now BOOT INTO CLOCKWORK RECOVERY MODE by holding power key+vol.up key+vol.down key.
select install zip from sd card
then choose zip from internal sd card(if you have placed it in internal sd or otherwise select choose zip from sd card)
select the above placed zip and flash it.....
go back and reboot system
AFTER REBOOTING YOU WILL FIND A SUPERUSER APP IN YOUR PHONE
THIS MEANS THAT YOUR PHONE HAS BEEN ROOTED
Hit thx...it wont cost u
Click to expand...
Click to collapse
I'm stuck at the point where I'm supposed to click the download option in the flash tool coz nothing is happening after that. A dialogue box pops up which reads "Not all images are correctly loaded which may cause boot up issue! Do you still want to go on downloading anyway?" And when I'm clicking on Yes, the download progress is remaining unmoved at 0%. plz help. Screenshot included.
EDIT : Looks like this method is for jellybean. I'm using stock ics.

I prefer you use binary4u method i think you are getting these error because when you were rooting a another device was connected or try to as admin
Sent from my C1604 using XDA Premium 4 mobile app

icoolguy1995 said:
I prefer you use binary4u method i think you are getting these error because when you were rooting a another device was connected or try to as admin
Sent from my C1604 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ya i also thought that this could be the reason but he told me that only one device is connected...that why i asked him to follow the method of rooting jellybean because it also works on ics.

CM Punk said:
I'm stuck at the point where I'm supposed to click the download option in the flash tool coz nothing is happening after that. A dialogue box pops up which reads "Not all images are correctly loaded which may cause boot up issue! Do you still want to go on downloading anyway?" And when I'm clicking on Yes, the download progress is remaining unmoved at 0%. plz help. Screenshot included.
EDIT : Looks like this method is for jellybean. I'm using stock ics.
Click to expand...
Click to collapse
YOUR PROBLEM IS SIMPLY THIS THAT PRE- LOADER DRIVERS FOR YOUR PHONE ARE NOT PROPERLY INSTALLED IN YOUR PC. That's why sp flash tools is unable to connect to your phone and flash recovery.and so there is no progress.
TO INSTALL PROPER DRIVERS GO TO THIS THREAD.
Link: http://forum.xda-developers.com/showthread.php?t=2370906
And i know that the method i suggested is to root jellybean but it works fine on ics also ( but you cannot root jellybean via ics method)
**After installing proper drivers try again the above mentioned method and it should work.
And regarding that message... it will always come because all the images required to flash a new firmware are not properly loaded.
Ignore it because you are after all not flashing a whole new firmware but simply recovery in your phone.
Best if luck.

[email protected] said:
YOUR PROBLEM IS SIMPLY THIS THAT PRE- LOADER DRIVERS FOR YOUR PHONE ARE NOT PROPERLY INSTALLED IN YOUR PC. That's why sp flash tools is unable to connect to your phone and flash recovery.and so there is no progress.
TO INSTALL PROPER DRIVERS GO TO THIS THREAD.
Link: http://forum.xda-developers.com/showthread.php?t=2370906
And i know that the method i suggested is to root jellybean but it works fine on ics also ( but you cannot root jellybean via ics method)
**After installing proper drivers try again the above mentioned method and it should work.
And regarding that message... it will always come because all the images required to flash a new firmware are not properly loaded.
Ignore it because you are after all not flashing a whole new firmware but simply recovery in your phone.
Best if luck.
Click to expand...
Click to collapse
I have already been into that link since even I thought that I'm having driver issues but my device is included under adb in device manager and when I tried to update the drivers, it said that the best drivers are already installed.
I'm lost in a limbo, don't know what to do.

CM Punk said:
I have already been into that link since even I thought that I'm having driver issues but my device is included under adb in device manager and when I tried to update the drivers, it said that the best drivers are already installed.
I'm lost in a limbo, don't know what to do.
Click to expand...
Click to collapse
Did you tried to run as admin

icoolguy1995 said:
Did you tried to run as admin
Click to expand...
Click to collapse
Yes.

CM Punk said:
Yes.
Click to expand...
Click to collapse
Ok My last suggestion.
Remove all the connected device(dongles, bluetooth device) from your comp except your mobile with Usb debugging on.
restart your comp.
now place it in C drive(just for caution) or if it was on C drive move it to another drive.
Now try to root if it doesn't root.
Try frameroot.
---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------
icoolguy1995 said:
Ok My last suggestion.
Remove all the connected device(dongles, bluetooth device) from your comp except your mobile with Usb debugging on.
restart your comp.
now place it in C drive(just for caution) or if it was on C drive move it to another drive.
Now try to root if it doesn't root.
Try frameroot.
Click to expand...
Click to collapse
Another suggestion if the above method does not work.
Try with a different port or with different cable.

[Q] Motorola XT319, Deleted Stock Launcher,USB Debugging not enabled

Hi
I have a Motorola XT319 (GB 2.3.5) China ROM . I rooted it & removed stock launcher & most chinese app, flashed Gapps etc. Then yesterday I did a factory reset. After that phone boots normally & I get signal & notification bars, screen lock, can receive calls etc. But as there is no launcher I cant do any further. There is no gapps in stock rom. USB debugging is disabled so can't push anything through adb.
I can boot into stock recovery & see the option of apply update from SD card & other options as well.
Please suggest is there any way to recover from this. Or any help to find a SBF & flashing it.

singh.r said:
Hi
I have a Motorola XT319 (GB 2.3.5) China ROM . I rooted it & removed stock launcher & most chinese app, flashed Gapps etc. Then yesterday I did a factory reset. After that phone boots normally & I get signal & notification bars, screen lock, can receive calls etc. But as there is no launcher I cant do any further. There is no gapps in stock rom. USB debugging is disabled so can't push anything through adb.
I can boot into stock recovery & see the option of apply update from SD card & other options as well.
Please suggest is there any way to recover from this. Or any help to find a SBF & flashing it.
Click to expand...
Click to collapse
Hello Singh, I am also thinking about buying this phone. I am not a pro but as a fellow member I would suggest you to kindly paste your queries to the following threads, they are more related to the topic.
http://forum.xda-developers.com/showthread.php?t=1218506
http://forum.xda-developers.com/showthread.php?t=2281815
Hope you'll get your answer there. All the best.

Thanks, I did SBF
nightcrawler218 said:
Hello Singh, I am also thinking about buying this phone. I am not a pro but as a fellow member I would suggest you to kindly paste your queries to the following threads, they are more related to the topic.
http://forum.xda-developers.com/showthread.php?t=1218506
http://forum.xda-developers.com/showthread.php?t=2281815
Hope you'll get your answer there. All the best.
Click to expand...
Click to collapse
Thanks for looking into it. I had already gone through that & even posted a reply.
But I wanted to ask a question so I posted a fresh question under general.
Finally I SBF'd it.

how to install Gapps
Mr. Singh , I rooted motorola xt319 and removed unwanted bloatwares.I tried to install many Gapps packages in recovery mode.Every time it says incorrect or corrupted package.Please help me to install at least google play store.Thanks

kgnrizwan said:
Mr. Singh , I rooted motorola xt319 and removed unwanted bloatwares.I tried to install many Gapps packages in recovery mode.Every time it says incorrect or corrupted package.Please help me to install at least google play store.Thanks
Click to expand...
Click to collapse
You can not install gapps in recovery mode, u need to push it with adb.
Don't try many just use below one & push it.
http://goo.im/gapps/gapps-gb-20110828-signed.zip

adb command
When I typed "adb install gapps-gb-20110828-signed.zip" and hit enter ,it says "gapps-gb-20110828-signed.zip" does not contain androidmanifest.xml
rm failled for ...................no such file or directory.
please help me by providing steps to install gapps.
Thanks and Regards

kgnrizwan said:
When I typed "adb install gapps-gb-20110828-signed.zip" and hit enter ,it says "gapps-gb-20110828-signed.zip" does not contain androidmanifest.xml
rm failled for ...................no such file or directory.
please help me by providing steps to install gapps.
Thanks and Regards
Click to expand...
Click to collapse
Extract the zip file & copy system folder where your adb.exe is located
adb push system /system
* HIT Thanks if it helps you*

[SOLVED] Wiko Rainbow Jam seems hard to root: I'm looking for help

Hi all,
I have a Wiko Rainbow Jam (which is provided with the stock rom "Wiko Rainbow Jam version 8", Android Lollipop 5.1 and the latest updates from Wiko), is about a week that I attempt to root my phone, but I am unable to do this operation, since I am totally unable to mount the /system as RW, and furthermore the bootloader is locked.
Firstly I found this method which consist to write/flash the TWRP custom recovery in place of the original one:
Root method 1
(sorry for the Google Translate link, but I cannot find the same how-to in English)
Which seems similar to this how-to
http://forum.xda-developers.com/showpost.php?p=63803008&postcount=5
But seems that these two methods will wipe/erase everything on my phone, and I would avoid this risk.
I also read that by flashing another custom recovery I will be unable to install updates from Wiko.
Then I tried this method using adb which is more simple:
https://f-droid.org/forums/topic/tutorial-how-to-root-an-android-device/
But when I launch the "adb root" command, all that I get is "adbd cannot run as root in production builds"; so I attempted various workarounds to "fix" adb, but all unsuccesfully.
I have to mention the fact that I have some skills in using Linux and the shell commands: maybe there would be a way to place the "su" binary on my Phone using Linux on my computer, by logging on the phone as root user, by acquiring the needed privileges?
Any help/suggestion/hints would be very appreciate! :good:
Kind regards.

I have a mtk6580 phone and also had the root issues, for a while I used kingroot, which rooted fine but I didnt trust it. Then I used supersume to get rid of kingroot which seemed to work but again, wasnt 100% it was all gone. Followed a similar guide to your first link which wasnt working. What worked for me was:
Download the twrp recovery .img file
rename it to recovery.img
open SPflash tools
add your own scatter file from your stock rom
deselect all the boxes except recovery
double click the recovery address box and find the renamed recovery.img
click download
plug your turned off phone in,
let it flash.
reboot into recovery
select reboot system
TWRP will tell you its not rooted and ask to install superSU
swipe for yes
reboot and you are rooted.
NO DATA LOSS

Thank you for this detailed how-to! However, for me, nor kingroot, kingoroot, framaroot and no other apk worked on my phone, so I will attempt to try your method, but first I have some questions:
1): On my phone, under SETTINGS > DEVELOPER OPTIONS, I can see the option “OEM unlocking”: I have to enable this option to permit the flashing of the TWRP img?
2): Is ok to download TWRP from here? dl.twrp.me/i9300/twrp-2.8.6.1-i9300.tar.html
3): "add your own scatter file from your stock rom":
where I can get/grab such file?
4): "TWRP will tell you its not rooted and ask to install superSU":
so TWRP is already provided with the SuperSU utility?
5): To be sure to avoid any risk, here I have a backup of my phone, which was done using "adb backup -apk -shared -all"; in case of emergency I will be able to restore my phone using this backup?
Many thanks for your attention! :good:

Mister_Dave said:
3): "add your own scatter file from your stock rom":
where I can get/grab such file?
Click to expand...
Click to collapse
Ok, seems that such file was available in the first link:
s000.tinyupload.com/download.php?file_id=53888272183191245346&t=5388827218319124534686744
is called MT6580_Android_scatter.txt , can you take a look and tell me if is ok?
Many thanks!

1) cant hurt to turn it on, however the phone will be flashed whilst turned off so dont know if its needed, but Im sure I wouldve enabled it.
2) and 3) I dont know what your exact model number etc.. is for your phone, so the twrp you would have to find and check yourself, go here: http://www.needrom.com/category/others/u-v-w-x-y-z/brands-w/wiko/ and you can try to get a twrp from there, and definetely get a stock rom. Use the scatterfile from an 'SP TOOLS FLASHABLE STOCK/UPDATE ROM'
4) yes
5) I dont know, I dont use adb and wouldnt like to say its OK. You can use this: https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en which will make a TWRP or CWM backup of your entire phone which you can then flash in TWRP or CWM once they are flashed, or get all the data from the backup. I would advise to find this out before trying though, just in case. I personally didnt lose any data, flashed twrp in SPtools, took 5 seconds, rebooted, added SU, rebooted, took 2 minutes and everything was still there.
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
it has to be a scatter file from your exact model of phone, as everything has to match, partitions, nvram...etc... loads of things that can go wrong if the scatter is wrong

robneymcplum said:
2) and 3) I dont know what your exact model number etc.. is for your phone, so the twrp you would have to find and check yourself, go here: http://www.needrom.com/category/others/u-v-w-x-y-z/brands-w/wiko/ and you can try to get a twrp from there, and definetely get a stock rom. Use the scatterfile from an 'SP TOOLS FLASHABLE STOCK/UPDATE ROM'
Click to expand...
Click to collapse
I went there, but my model is not listed.. As I stated in the subject is a Wiko Rainbow Jam: if i search for Rainbow Jam is such link, no model is displayed..
it has to be a scatter file from your exact model of phone, as everything has to match, partitions, nvram...etc... loads of things that can go wrong if the scatter is wrong
Click to expand...
Click to collapse
I got the scatter file in the first link "Root method 1", where there is the how-to for my exact model.

ah right, in that case, its OK

robneymcplum said:
ah right, in that case, its OK
Click to expand...
Click to collapse
Ok: it was painless differently from what I thought: now, following your advice (I used the TWRP and the scatter file from the first link) my phone is nicely provided with the root access
EDIT: was necessary to activate the “OEM unlocking” option under SETTINGS > DEVELOPER OPTION, without this option activated, I was unable to flash the TWRP recovery img.
Many thanks!
p.s: If a moderator see this post, feel free to add [RESOLVED] to the title of this thread, since I cannot edit the title.

Glad it worked lots of guides I saw also made it excessively complicated, this way took you what? 2 minutes? And am guessing all your data is safe and untouched.

robneymcplum said:
Glad it worked lots of guides I saw also made it excessively complicated, this way took you what? 2 minutes? And am guessing all your data is safe and untouched.
Click to expand...
Click to collapse
Yeah, it took about 2 minutes, just the time to figure out that I needed the USB OTG cable with an usb mouse and to browse to the UPDATE-SuperSU-v2.76.zip file (as I said I used the TWRP posted in the first link, which doesn't work with the touch screen).
I want to say thank you again for your friendly assistance!
EDIT: Yes: all my data is safe and untouched!

Like:good:

SOLVED: Installed Magisk and now Bootlooping

I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?

JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snoping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT: Just saw help thread, Ill post there.
EDIT 2: I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
If you've already factory reset, I'd just download the factory images and flash those to start fresh. In the future, you could either use the magisk uninstaller to clear out magisk files, or you could mount magisk in recovery and delete the module causing issues.

jsauder2 said:
If you've already factory reset, I'd just download the factory images and flash those to start fresh. In the future, you could either use the magisk uninstaller to clear out magisk files, or you could mount magisk in recovery and delete the module causing issues.
Click to expand...
Click to collapse
Tried flashing new image and its keeps failing. Im using this Pixel 2XL guide.
I keep getting this:

JJT211 said:
Tried flashing new image and its keeps failing. Im using this Pixel 2XL guide.
I keep getting this:
Click to expand...
Click to collapse
You need the latest Platform Tools. Happened to me last night after I messed up installing TWRP and had to install factory images.

Its still not working. Let me summarize exactly what ive done.
I think im installing the platform tools correctly.
According to guide (windows) I just open command line and type:
adb --version
fastboot --version
That means Platform tools have been installed.
I then take the unzip the new factory image and place it inside the Platforms tools folder. I then navigate to the factory image folder from command line and type:
flash-all
I then get:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
followed by a failed message

So do yall think im bricked? Can anyone confirm what I've done above is correct?

Idk bro. I doubt it's bricked. I had adb and fastboot installed for years but they weren't the newest version. This was giving me the errors you are receiving. You're screenshot from earlier is exactly where and when I would get the error. Download the official Platform Tools from Androids site. I'm sorry this is happening

JJT211 said:
So do yall think im bricked? Can anyone confirm what I've done above is correct?
Click to expand...
Click to collapse
Very doubtful you're bricked. Try downloading the newest platform tools from Google's page if you haven't already. If it still doesn't work, I would try flashing the pieces individually through fastboot instead of using the flash-all command

Thanks for the swift replies talk.
Yea I grabbed the most recent version Platform tools from Google.
When you say flash individually vs flash all, what do you mean? Can you provide an example?

I dont know if you have done this already and I remember doing this with my og Pixel. The firmware has to be extracted from the zip (which I see you did already) and shown in pic1. Then there is a second zip inside that has to be extracted as well (pic2) and all of those files placed in the platform tools folder then you should be able to flash all. It will start to flash then pause for a min or two and look like there is something wrong but, then it should continue and reflash your phone.
JJT211 said:
Thanks for the swift replies talk.
Yea I grabbed the most recent version Platform tools from Google.
When you say flash individually vs flash all, what do you mean? Can you provide an example?
Click to expand...
Click to collapse

arodey said:
Idk bro. I doubt it's bricked. I had adb and fastboot installed for years but they weren't the newest version. This was giving me the errors you are receiving. You're screenshot from earlier is exactly where and when I would get the error. Download the official Platform Tools from Androids site. I'm sorry this is happening
Click to expand...
Click to collapse
Thanks man, I think my problem is close to this.
My previous laptop had an old version of Minimal ADB on it from a while back. I tried updating that, and still no luck. So I grabbed my work laptop that has never had any Android SDK stuff on it. I then downloaded most current Platform tools from Google. Using the same guide above, I installed both adb and fastboot. From the platform tools directory, it would recognize my phone when using 'adb devices' command and I could also reboot to bootloader using 'adb reboot bootloader' command. I then unzipped and copied factory image to same Platform tools folder. I moved to image directory and tried 'flash-all' command it could not recognize the command. See below
Code:
C:\Users\Me\Desktop\platform-tools\crosshatch-pd1a.180720.031>flash-all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
To me that says that fastboot is not installed. But I definitely installed it.
Code:
C:\Users\Me\Desktop\platform-tools>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\Users\Me\Desktop\platform-tools\fastboot.exe
C:\Users\Me\Desktop\platform-tools>adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as C:\Users\Me\Desktop\platform-tools\adb.exe
Is there something Im doing wrong??

I don t know why but when I got my Pixel 3 I had to use Windows 10 Power Shell and fastboot commands were recognized. Min fastboot would not show fastboot commands but only ADB commands as operable.
JJT211 said:
Thanks man, I think my problem is close to this.
My previous laptop had an old version of Minimal ADB on it from a while back. I tried updating that, and still no luck. So I grabbed my work laptop that has never had any Android SDK stuff on it. I then downloaded most current Platform tools from Google. Using the same guide above, I installed both adb and fastboot. From the platform tools directory, it would recognize my phone when using 'adb devices' command and I could also reboot to bootloader using 'adb reboot bootloader' command. I then unzipped and copied factory image to same Platform tools folder. I moved to image directory and tried 'flash-all' command it could not recognize the command. See below
Code:
C:\Users\Me\Desktop\platform-tools\crosshatch-pd1a.180720.031>flash-all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
To me that says that fastboot is not installed. But I definitely installed it.
Code:
C:\Users\Me\Desktop\platform-tools>fastboot --version
fastboot version 28.0.1-4986621
Installed as C:\Users\Me\Desktop\platform-tools\fastboot.exe
C:\Users\Me\Desktop\platform-tools>adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Installed as C:\Users\Me\Desktop\platform-tools\adb.exe
Is there something Im doing wrong??
Click to expand...
Click to collapse

Archangel said:
I dont know if you have done this already and I remember doing this with my og Pixel. The firmware has to be extracted from the zip (which I see you did already) and shown in pic1. Then there is a second zip inside that has to be extracted as well (pic2) and all of those files placed in the platform tools folder then you should be able to flash all. It will start to flash then pause for a min or two and look like there is something wrong but, then it should continue and reflash your phone.
Click to expand...
Click to collapse
IT WORKED!!
So not only do you need to extract that 2nd zip file into same directory but apparently you also need to keep that 2nd original zip file in there as later on during the install, the script tells it to extract it. It wont work without that original zip.
Thanks everyone!!

Awesome brother glad you got it working!
JJT211 said:
IT WORKED!!
So not only do you need to extract that 2nd .zip file into same directory but apparently you also need to keep that original .zip file in there as later on during the install, the script tells it to extract. It wont work without that original zip.
Thanks everyone!!
Click to expand...
Click to collapse

Good work man!!!

Been a while since I used magisk. Does Google Pay still work if bootloader is unlocked and magisk enabled?
Sent from my Pixel 3 XL using Tapatalk

bigdave79 said:
Been a while since I used magisk. Does Google Pay still work if bootloader is unlocked and magisk enabled?
Click to expand...
Click to collapse
Yes.

JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
I had to RMA mine it did the exact same thing

JJT211 said:
I havent rooted in quite a while and am new to Magisk. I installed Magisk and all was fine during initial boot. I was snooping around in the app and tried to install a systemless Greenify app. I installed app and rebooted and now im bootlooping
Now after a few boots, I get a message from Android recovery stating:
"Cant load Android system. Your data may be corrupt. IF you continue to get this message, you may have to perform a factory data reset and erase all user data stored on this device" And it gives me the option to factory reset.
Should I factory reset or boot into TWRP and flash new factory image?? Is there a way for me to avoid factory resetting? Its not the biggest deal in the world if I lose my data but I would like to avoid it if possible.
Any help would be greatly appreciated.
EDIT : I got impatient and factory reset my phone. It reset but does not recognize my sim card nor can it see any wifi networks. The settings will not come up at all either. I am however able to boot into TWRP. What should I do from here?
Click to expand...
Click to collapse
Flash Factory image . I had the same thing after messing some magisk modules.