[help] imei 0 moto g5 xt1671 dual sim - Moto G5 Questions & Answers

Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)

TioNacho said:
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings
(Sorry for the English, I use the google translator)
Click to expand...
Click to collapse
There's a possible fix until the moment you flash persist or restore EFS from another phone to yours.
ONCE AGAIN, DON'T TRY TO FLASH PERSIST OR RESTORE EFS FROM ANOTHER PHONE!!!
Just root your phone using Magisk and execute these commands using adb on your PC/laptop:
Things to note before you start executing commands below:
1. Make sure that USB debugging in your phone is turned on.
2. If everything is set properly and "adb devices" has been executed, u should see popup window about ADB allow on your phone BUT ONLY IN CASE YOU ARE USING ADB ON PC WHICH WASN'T USED FOR ADB YET. Make sure "Always allow from this PC" is checked and click "OK". Re-run command one more time. You should be able to see your device in cmd window now.
3. After "su" command, you have to grant root access to adb shell within 10 seconds.
4. "adb reboot" command will immediately reboot your phone, don't panic.
5. You are doing this at your own risk.
Code:
adb devices
adb shell
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
adb reboot
Commands have been used from this thread: https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147

Good morning!
Look I was able to recover the signal (h +) with that command but not imei. Will not you know other commands that will make him recover or some method? regards

Related

ADB not seeing Evo

Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
thanks. I'll give that a try and reply back
Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work
phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?
chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.
Is USB debugging enabled?
CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!
No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!
I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!
You need to be in the tools directory of the sdk so cmd can find the adb command.

[Q] Temporary Nand Unlock

How do you gain temporary nand unlock? All i wanted to do is copy 2 files into the /system/xbin/bb which doesnt seem to work with root explorer despite super user permission, copy paste just wont work.
Any ideas how to copy paste these 2 files without going to full s-off? Would the adb method work? or any other apk that can do the job?
Thanks in advance for those who can help and any tips is very much appreciated.
In recovery with adb.
TheGhost1233 said:
In recovery with adb.
Click to expand...
Click to collapse
any links to it? a guide perhaps? thanks for the tip.
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
TheGhost1233 said:
Make a nandroid before messing with the system partition.
Then:
Code:
adb remount
adb push <file_name> /system/xbin/bb
This is what i think it is just looking at the basic adb commands, here is some more info about moving stuff to the system partition.
Click to expand...
Click to collapse
btw, how do i get to adb with recovery?
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
TheGhost1233 said:
You do know that adb is part of the android sdk and not some function/app on the phone?
To get adb working (i hope you already installed it) just boot in to recovery, connect the usb cable, and launch adb via command prompt or terminal.
Click to expand...
Click to collapse
many thanks! i will try this tommorow.
Use the update.zip I attached in this thread, you don't need to worry about adb then.
http://forum.xda-developers.com/showthread.php?t=885506&page=2
Sent from my HTC Desire using XDA App
Ghettonine said:
many thanks! i will try this tommorow.
Click to expand...
Click to collapse
Ok I did my best, read alot about adb and followed some tips but I just cant seem to get these things working. I need a DETAILED step by step procedure.
I feel such a noob today, can anyone please help?
Basically, I just wanted to copy "ifconfig" and "route" from "/system/xbin" to "system/xbin/bb" and thats it! Im s-on by the way and dont want a full s-off just to copy paste 2 files.
I tried rebooting in recovery with adb and run some commands on "adb shell", many things came out and I have no idea what it ment.
Well many things came out is not such a great description. So i have no idea if something is wrong or something happened which you did not expect.
Boot again in to recovery and connect adb.
The type "adb devices" this should output something like:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT##########
If this does not happen you don't have a connection and most likely have driver issues (only if you are on windows). If you do get a connection next thing to do is mount the system partition as read/write. To do this type "adb remount".
The output should be "remount succeeded"
Next type "adb shell"
This should give "#" as output .
Since you know where the files are and where you want them to go type "mv /system/xbin/ifconfig /system/xbin/bb" and hit enter, you don't get any conformation about this. Next type "mv /system/xbin/route /system/xbin/bb"
To check if they go moved correctly type " ls /system/xbin/bb", now you should see the files listed.
Next type "exit" to end the adb shell.
Then type "adb reboot".
If this doesn't work you need to give more info about the errors you get or maybe someone else has a better description.
A completly other method is, if you are able to copy the files to your computer, useing the .zip mercianary linked to, just make sure the system/app folder is empty and that you make the system/xbin/bb folder and place the files in there. Then just follow the instructions.

[Q] HTC Desire USB Bricked & Not Rooted [Q]

HTC Desire USB Bricked Without Root​
Hey guys, got a really tricky one for you here...
Some people may have seen a thread I posted the other day about problems that had arisen with my HTC Desire, well I have managed to find out that these problems are being caused by a USB Brick.
As of now I have managed to restore SD Functions however my phone will still not connect to the computer, and the phone won't recieve a network signal from Orange.
I read through this tutorial here and also this one here. My problem is, all the requirements of the fix, my device does not meet. My phone is not rooted, it is running the latest software and has the latest HBoot.
I also found this that looked very promising, however when I tried to log into my Google account on my phone, everytime it said it couldn't make a connection, I left it for a few hours and the same thing, I can't help but think this is due to the USB brick?
I just really need some help, is there anything I can do to restore USB functionality? The phone is being sent to HTC tomorrow, however I can cancel at any point. Please, I know there are so many amazing people on XDA that can help me. Thankyou
*UPDATE* - After using the Fastboot code to enable the SD Card, my Sim Card is now working. I have been able to log into my G-Mail account and download the terminal emulator which is an apparent fix in one of the posts I linked above, however this doesn't work. Please can someone help me
hy did you try to reinstal the software ???? the original os or an upgrade??
en_mih said:
hy did you try to reinstal the software ???? the original os or an upgrade??
Click to expand...
Click to collapse
I have done a factory reset, re-installed the PB99IMG and also flashed an RRU. All the problems persist
Really need help with this guys! E-Mail - [email protected]
jaaystott said:
Really need help with this guys! E-Mail - [email protected]
Click to expand...
Click to collapse
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
leinad said:
Hi.
If I understand well, you have got an USB brick, and your current situation is the following :
No S-OFF hboot, no ROOTED ROM, but SDCard reenabled, thanks to "fastboot oem enableqxdm 0" command in fastboot mode.
I'll try to drive you through the whole process for getting your phone back, since I've already encoutered this situation, and successfully solved it.
First step => Get a 'mtd0.img' file :
Go to "Menu>Settings>About phone>Software information>Kernel version", and write down your ROM version (2.6.32.15, for example)
Then, in fastboot mode, with USB cable connected to your PC, issue the following command
Code:
fastboot getvar cid
You should see your phone's CID, something like 'HTC__022'.
You then go to this site, provide both information 'cid' and 'rom version', and you'll get a 'mtd0.img' file.
Let me know when you've gone through this first step
Click to expand...
Click to collapse
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
HQRaja said:
Hi,
I am very much interested in knowing about the complete procedure. Assuming we have done this first step, how to proceed from here?
Click to expand...
Click to collapse
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
jaaystott said:
I already tried this process, it didn't work, when I did the RageAgainstTheCage command, it said searching for ADB, then something about not being able to find it, then when I restart the terminal and do the final command, it says permission denied -_-
Click to expand...
Click to collapse
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
leinad said:
In order for rageagainstthecage to find adb process, you should tick 'USB debugging' in "Menu>Settings>Applications>Development>"
Click to expand...
Click to collapse
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
jaaystott said:
I could have fixed this myself aswell :| **** i just sent off my HTC Desire 30 seconds ago, no joke, the UPS guy just came and got it
Click to expand...
Click to collapse
:-( (10 characters)
leinad said:
:-( (10 characters)
Click to expand...
Click to collapse
I really appreciate the help you gave me mate, even if I asn't able to fix my device, thankyou for the time.
leinad said:
Next step will aim at flashing this 'mtd0.img' file onto the 'misc' partition.
Since we are S-ON, and the ROM is not rooted, we'll have to get temp root access. To do so, follow the steps below.
1.- Download the two files rageagainstthecage.tgz and flash_image, extract rageagainstthecage-arm5.bin, and copy rageagainstthecage-arm5.bin, flash_image, and the file mtdo.img at the root of your SD using any SD card adapter.
2.-Install 'Terminal Emulator' (free app on the Android Market) on your phone
3.- Issue the following commands from Terminal Emulator
Code:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
This will copy all three files to the right directory on your phone, and give exec rights to the files.
4.- Then run the program rageagainstthecage-arm5.bin from the Terminal Emulator
Code:
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
in order to get temp root access. Be aware that the phone will have some kind of erratic behavior, and will seem to crash.
5.- Quit Terminal Emulator, stop it (Menu>Settings>Applications>Manage applications>Terminal Emulator>Force stop), and relaunch it. You should see a pretty # character, indicating you've got temp root access.
6.- You then issue the following commands, in order to flash the misc partition of your phone with the correct mtd0.img file
Code:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
7.- Reboot your phone, and enjoy !!!
PS : All credits come to Antubis, from the French forum FrAndroid, who posted a very clever tuto in french
Click to expand...
Click to collapse
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
moley10 said:
trying to follow your guide to restore my phone to work again! having trouble though...
i have got to the point of installing terminal emulator but at the point of issuing second cat command it says no such file or directory..
Click to expand...
Click to collapse
I found a way around this, as I was having the same problem. Try This ->
cat /sdcard/rageagainstthecage-arm5.bin > data/data/rageagainstthecage-arm5.bin
Do that for the two other commands that follow that, then follow the instructions as given, that should work.
HQRaja said:
Thanks, will feature your method in a guide at my blog (while giving you and Antubis full credit for it of course). =)
Click to expand...
Click to collapse
Link to your blog? =)
ok, so i did that, no longer got errors.. seemed to work but after reboot still the same, doesnt connect to my pc, and device manager it is still being shown as 'qualcomm cdma technologies msm' in other devices!
is the purpose of those commands to moved the files to certain directory? i can get temp root with visionary to perhaps just move the files in root explorer?
thanks for all the help. its much appreciated!
Hello,
I've got a similar problem but this solutions doesn't work for me, because I cannot create a CID.
Any ideas?
Thanks in advance
hi,
i managed to create files etc and still am stuck with the same problem... searched hi and low for days,
hopefully someone will be able to find us a solution..
You mean creating the mtd from that site? Thats because you need to type the Build Number not the kernel version.

[HOW TO] Root a bootloader-unlocked Xperia Pro MK16a

There is now a MUCH easier way to root ALL Sony Ericsson 2011 phones including the Xperia Pro, making these instructions obsolete. Please see DooMLorD's thread here: http://forum.xda-developers.com/showthread.php?t=1319653
Remember to say thanks to DooMLorD for his awesome work!
However, I'll sill keep the 2 sets of instructions here in case anyone needs them or wants to refer back to them. My ZIPs do have all the drivers needed with good instructions on how to install them after all
My original instructions based on alvaroag's work can be found below, and the instructions via my instructions the Xperia Pro CWM Recovery method can be found on post 50 of this thread.
It's important to note that DooMLorD's tool only works for Windows. You can still use our original method in this post if you're running Linux.
We finally have a method to root the Xperia Pro MK16a (and PROBABLY MK16i) thanks to XDA Member alvaroag!!
This is his method, with the instructions modified by myself for ease of use.
What you need before you begin:
1. A rock hard stomach, because should the very unlikely happen and this brick/damage your phone in some way, I’m not responsible
2. An Unlocked Bootloader
NOTE: Sony offers a totally free, official, and simple method to unlock your bootloader here: http://unlockbootloader.sonyericsson.com/
Should that not work for you, your phone is probably SIM locked from your carrier (FIDO for example does that). You'll need to get the bootloader unlocked remotely from someone who has SETool and the appropriate security USB dongle. THIS COSTS MONEY, as SETool requires that user to pay per use.
Please see this thread for further instructions as it's the method I used personally: http://forum.xda-developers.com/showthread.php?t=1232050
Alejandrissimo was awesome at helping me through it.
3. On the phone itself navigate to the following locations:
a. Settings - applications – Make sure Unknown Sources (first option) is checked
b. Settings – applications – development – Make sure USB Debugging is checked
4. Download this archive. It contains all the files and drivers you will need:
http://www.mediafire.com/?7cz7672da9cxkrd​
Instructions:
1. Extract the archive you downloaded to a folder on your computer. Where doesn’t matter as long as you remember where it is.
2. Navigate to the folder ADB For Dummies (thanks to VanillaTbone for his guide) and install ADB for Dummies.exe
a. This will create a new folder on your C: drive called “android-sdk-windows”
3. Take the file “xperia_pro_root.zip” from the archive you downloaded and extract the contents to C:\android-sdk-windows\platform-tools\
4. Power off the phone and make sure it’s not plugged into anything.
5. Hold down the MENU button and connect the USB cable. A blue light will appear. If a blue light does NOT appear, then your phone can't get into FastBoot, and probably still has the bootloader locked.
a. If Windows asks you to install the drivers, install the driver from the folder “Fastboot Driver” in the archive you downloaded. Should those drivers not work, try the drivers found in "C:\android-sdk-windows\google-usb_driver"
6. Open the “Fastboot” folder in windows explorer (its part of the archive you extracted in step 1. Hold down the shift key and right click on an empty space in the folder window, select Open Command Prompt Here.
7. Type:
fastboot boot recoveryNEO.img​
8. The blue light on the phone will turn off, the screen on the phone will be blank, and the phone will be disconnected from windows, but after a few seconds you will get a Mass Storage & ADB Interface Detected. Note that the phone’s screen will continue to be black for the rest of this process. THIS IS NORMAL, your phone has not been bricked. If you need to stop anywhere along the way, simply unplug the phone from the computer and take your battery out. The phone will return to normal operations, though UNROOTED.
a. Windows will PROBABLY say hardware failed to install. This is fine.
i. Open the start menu, right click on “Computer” and select “Manage”
ii. Select Device Manager on the left side of the Computer Management window that opens.
iii. Look for the unknown piece of hardware. Right click on it and select update/install driver.
iv. Browse your computer, and select the main folder you extracted the archive to way back in step 1 – the drivers are somewhere in there, don’t worry about where, as windows will find them just fine.
9. On your computer navigate to “C:\android-sdk-windows\platform-tools”. Hold down the shift button on your keyboard and Right click on an empty part of the windows, and select “Open Command Window Here”
10. Type "adb shell". If it says "device not found", disconnect the USB cable, remove the battery, and try again from step 6. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
Now you’ll have to run a bunch of commands inside the ADB Shell window (the one with the black background and looks like a DOS window). You can just copy and paste each one from here. Be sure that once you start this step, you continue until the end of these instructions.
mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system​
If it says “/system is not empty” then type:
"rmdir /system/bin" and then run the first mount command again
type "exit"
11. From the DOS window, Run these commands (again copy and paste each one is fine)
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell​
12. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot​
13. The adb shell will terminate. Disconnect the phone from the USB cable, wait for about 15 sec, remove the battery, and then turn it on.
14. From the phone, Open the Market, search for "Busybox" by "Stephen (Stericson)". Install that
15. From the Market, go to My Apps, search for "Superuser" by "ChainsDD" and make sure you're running the latest edition
16. Run the App "Superuser" from your app tray.
- under the settings tab, scroll to the bottom and click SU Binary "tap to check for updates"
17. Run the "Busybox Installer" app. Follow the onscreen instructions - just leave everything at default.
Congratulations! Your device should now be rooted! I personally suggest downloading and installing Titanium Backup to make sure - it will run a root check on startup and notify you if anything is wrong.
Notes:
This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution. - alvaroag​Thanks to VanillaTbone of XDA Developers for his awesome ADB For Dummies guide and app.
http://forum.xda-developers.com/showthread.php?t=502010
And of course thanks to Bin4ry for his NEO recovery image.
And thanks to all the other contributors to this thread for their help, advice, and overall contribution.
And if this thread helped you in some way, Please click THANK YOU to show your appreciation
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rcummings100 said:
Hello
Since there is no Xperia Pro forum I decided to post this here. Hope you can help me.
I recently bought an Xperia Pro MK16a and I have already unlocked the bootloader with setool (thanks to alejandrissimo and his remote unlock abilities). Now I'm searching for a way to root the device.
He and I experimented with it a bit, and we've already tried the recovery hot-boot with recovery.img from Arc, Play, and Neo, but with no luck. Recovery just doesn't boot.
He's guessing it's related to something like a different ramdisk or something like that.
Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk
Edit; ............
Sent from my LT15i using XDA App
taaviu said:
If you bootloader is open you can flash directly "prerooted".img with fastboot? Arc and Neo have this option.
Regards!
Taavi
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess
XperienceD said:
There is a Mini Pro forum. ;-)
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Totally different phone
This is just the "Xperia Pro" - it was released in August. It's the same phone as the Neo, but with a slide out QWERTY keyboard. Model is MK16a (or MK16i for the international one)
Gingerbreak??
Sent from my MT15i using Tapatalk
Alejandrissimo said:
To be able to generate a pre-rooted system.img you need first a rooted phone and this is exactly the problem, how to root it if there is no recovery for MK16
For sure RootXperia.zip will work but for install it the proper recovery is needed first i guess
Click to expand...
Click to collapse
How to do it? Generate prerooted system.img
Thanks!
Sent from my MT15i using Tapatalk
I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards
Bin4ry said:
I think that NEO recovery should work:
http://forum.xda-developers.com/showthread.php?t=1183465
Maybe the keys are wrong mapped, you have to try a little. Just flash RootXperia.zip from Recovery and you are rooted.
Regards
Click to expand...
Click to collapse
That was the first thing I tried, since the Pro should just be a Neo with a keyboard. Unfortunately it doesn't work.
Here's the output:
C:\root-play>fastboot boot recoveryNEO.img
downloading 'boot.img'...
(bootloader) USB download speed was 9336kB/s
OKAY [ 0.517s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.002s]
finished. total time: 0.519s​
The phone is clearly still turned on, but no longer in fastboot mode, and the screen is totally blank, though the backlight is active.
I've tried the same thing with the Arc and Play recovery images and had the same results.
What do you mean by the keys are mapped wrong?
Is this what you're talking about?
http://www.knowyourcell.com/sony-er..._hard_reset_the_sony_ericsson_xperia_pro.html
The instructions on how to get into Recovery on that site are very similar to how to do it on the stock build of my previous phone, the Motorola Milestone. Unfortunately THEY DON'T WORK
I've tried substituting the volume down button with other keys, but with no success. Pretty difficult to guess the right key combination when there's a full qwerty keyboard on here
Is there a way to boot into the standard recovery from ADB or fastboot or something? Possibly from an on-board terminal emulator? A command like "Reboot Recovery" perhaps? Or is that too easy to be possible...
It's ironic that my old Motorola milestone with a totally locked down bootloader proved easier to hack than this phone with it's wide open bootloader
Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards
Bin4ry said:
Well,
i wrote you already in PM. But now here too. The PRO is only released in Canada and some Asien Countrys. Until it is released in Europe i cannot help you, because i need the device for testing.
One thing you can try:
after you fastboot boot and the phone is in blackscreenmode please unplug and replug it to pc.
Now try to adb shell on it. Is this working? If yes please gimme a logcat
Regards
Click to expand...
Click to collapse
Nope, adb shell doesn't work. Shows "error: device not found"
But because I'm new to this (I came from a motorola milestone), I want to make sure I did what you actually asked of me:
- I turned on the phone into fastboot mode (hold down menu, plug in usb cable, get blue light)
- from a command prompt window: fastboot boot recoveryARC.img
(replacing ARC with NEO and PLAY depending on the image I'm trying)
- phone now boots into black screen, no blue light, screen backlight is on
- unplug from computer, plug back in
- from command prompt: adb shell
Are those the instructions you wanted me to follow?
Fastboot works fine. Can I do anything from there? Getvar for example, or something? can I run the command Update and flash the RootXperia.zip file? Or will that not work because it's not signed properly or something similar?
Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards
Bin4ry said:
Via fastboot you cannot flash the zip. Zip needs to be flashed via recovery, because this only contains some files and not whole system!
Click to expand...
Click to collapse
I figured as much. Just hoped I might be wrong.
Bin4ry said:
I'm sorry, you have to wait until i have the device! Only if the adb shell would work i could help you, if even this is not working it's hard to say what's goin wrong. All you can do is sending me the kernel.sin from you firmware. Maybe i can mix something up with this file
Regards
Click to expand...
Click to collapse
Can anyone give me instructions or pointers on how I extract the kernel.sin from my firmware?
Thanks for your continued patience with me. I really do appreciate it.
Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium
datagubben said:
Its funny how all the phones without forum ends up here!
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
It's because they're all so similar, and are based on the same hardware as the Arc.
Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards
Bin4ry said:
Process is simple:
IF you NEVER used UpdateService or PCCompanion BEFORE you unlocked your bootloader then : You need to relock bootloader first (sorry :/)
Then have to use SonyEricsson UpdateService/PC-Companion and tell it to REINSTALL/REPAIR your firmware.
If you used one of the tools before just skip the relock and do this:
After that is done you copy out the two files named:
FILE_XXXXXXXXXXX
FILE_XXXXXXXXXXX
where XXXXXXXXXX are some numbers. This files are located in the subfolder blob_fs inside the UpdateService/PC-Companion directory.
Just copy it on a "safe" place.
After that is done you have to start flashtool go to the "Advanced" Tab -> Decrypt -> then just choose the folder where you copied the files and let flashtool do its work
Afterwards upload the Firmware which is now present as a FTF file, somewhere and post it here (others will be happy to to have the whole MK16a Firmware )
Regards
Click to expand...
Click to collapse
Unfortunately the very first thing I did with the phone was unlock the bootloader. 'Fido' is the only phone company selling the phone, but I'm with 'Rogers'...so I needed to unlock the bootloader in order to actually use the phone as a phone, which was and remains the most important thing to me.
That being said, I'll see if Alejandrissimo can give me a hand with re-locking the bootloader, then I can get the firmware as you instructed, then have him re-unlock the bootloader. I'll just stick my SIM Card back in my old motorola milestone while we work on this so I can still have a working phone.
You're awesome Bin4ry for helping like this
Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.
ratius said:
Maybe I could help with that since I am with Fido and I have a locked bootloader (I haven't touched the phone except adding an ssh key) with my Xperia Pro MK16a. Though I know my way with ssh, I am new with the rooting stuff and Android. If you need some files or something from a locked bootloader I can help with that, just need some simple instructions.
Bin4ry said that files FILE_XXXXXXXXXXX were located under UpdateService/PC-Companion, can I access those via ssh? I have used PCCompanion only once when I got on Windows, but I am always on Ubuntu so I was wondering if I could get those file via scp and if so, where are they?.
Click to expand...
Click to collapse
If you could, that'd be great. I don't especially want to lock my bootloader over again since you have to use SETool to unlock it, which costs money each time you use it (essentially). Not to mention it involves some acrobatics with a paperclip to connect a testpoint inside the phone to a ground!
Unless there's an easier way to lock/unlock now that I've done it once that is...if so, I'm happy to do it.
As for accessing the files Bin4ry is talking about, boot to windows if you can and do it that way. Just follow his instructions to repair your firmware, then go to that folder in windows (it's located in C:\Program Files (x86)\Sony Ericsson\Sony Ericsson PC Companion). At least, that's my understanding.
Hi. Yesterday, I bought a Xperia Pro. Ive spent most of the afternoon and the nigh trying to root it, and I've finally got how to do it. It's a manual method, as there is not an automated one.
There's no need to say I'm not responsible for any damaged or bricked devices(but mine is working ok )
What you need:
1. The Xperia Neo Recovery, by Bin4ry, get it here
2. xperia_pro_root.zip I'm attaching. It contains the files from RootXperia.zip, but without the update.zip-related files, as they are not needed.
3. The Android SDK, with the Google USB Drivers Package.
4. If you've never used your device in fastboot mode, you may also need to follow steps 7 & 8 from SE bootloader unlocking tutorial.
5. [NOT REALLY SURE] Application Debugging & Unknown Sources enabled.
6. [NOT REALLY SURE] Unlocked Bootloader. This is because mine is unlocked, but I don't really know if that is required to boot the recovery image via fastboot.
I'm assuming that you are working on a Windows/Unix terminal, with a working directory where you have recoveryNeo.img, Superuser.apk and su /these two from the zip file I attach), and that fastboot & adb are on the PATH. If some file is not on the working directory, or fastboot/adb are not on the path, use full paths.
Instructions:
1. Disconnect & Power off the phone.
2. Hold down the menu button and connect the USB cable.
(If Windows asks you to install the drivers, install the driver from ANDROIDSDK\extras\google\usb_driver folder).
3. Run "fastboot boot recoveryNeo.img". The fastboot device will be disconnected, but after a few seconds you will get a Mass Storage & ADB Interface Detected.
4. Run "adb shell". If it says "device not found", disconnect, remove the battery, and try again from step 1. Also, try changing the USb port on your CPU. I'm not really sure about this, but I had to do it twice.
5. Run "mount -t yaffs2 -o rw,relatime /dev/block/mtdblock0 /system" from the adb terminal. If it says /system is not empty. run "rmdir /system/bin" and then run mount again.
6. type "exit"
7. Run :
adb push Superuser.apk /system/app/Superuser.apk
adb push su /system/bin/su
adb shell
8. From the adb shell, run:
chmod 0644 /system/app/Superuser.apk
chown 0 /system/bin/su
chgrp 0 /system/bin/su
chmod 6755 /system/bin/su
ln -s /system/bin/su /system/xbin/su
cd
umount /system
reboot
9. The adb shell will terminate. Disconnect the phone, wait for ~15 sec, remove the battery, and then turn it on.
10. Your device should now be rooted.
Notes:
1. When booting with recoveryNeo.img, the screen will keep blank. That's normal(I think).
2. This may seem to be a complicated method, but, as we will have to wait some weeks for an automated or simpler method, I think making writing an automated tool for this method is not worth the effort. But maybe, if no automated method appears in some weeks, I write one myself as a comunity contribution.
Hope this is usefull for you.

Stuck in bootloop but has very important files.

The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Z91 said:
The bootloop started very randomly one day and my phone kept restarting and the battery became very hot.(I was asleep so I noticed this after I woke up). I had already switched to an iphone but I was using the moto g for music and stuff like that. I was able to boot once and then the storage suddenly got full and the bootloop started again. So, I just removed the battery and left it. I have a whatsapp backup on it that has some very important data which I need at the moment. The phone is stock without root or cwm. Usb debugging was on, I don't know if that helps though. I really need to recover just that one backup file. I went through quite a few threads and didn't find anything that could help me. Is there any way to recover it. I don't mind if the process is tedious.
Click to expand...
Click to collapse
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
sharjeel.019 said:
I guess you can pull files from your phone via ADB commands. Can you get into recovery mode?
Click to expand...
Click to collapse
I can get into recovery but adb only works in sideload so I can't do stuff like adb pull, etc.
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
TheFixItMan said:
If your bootloader is unlocked you can flash twrp and then pull files via adb or by mtp (drag and drop files to pc)
If your bootloader is locked there's nothing you can do
Note adb doesn't work in stock recovery
Click to expand...
Click to collapse
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Z91 said:
I haven't unlocked the bootloader so I'm assuming it's locked. Is there no way around it?
Click to expand...
Click to collapse
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
TheFixItMan said:
No - unlocking the bootloader requires a data wipe
Technically if adb debugging is enabled your phone might boot enough for adb to become available but it might only be for a few seconds before it restarts
You'll keep having to type
adb devices
And see if you get a device listed but the chances of it being available long enough for you to pull anything is pretty much zero
Click to expand...
Click to collapse
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Z91 said:
Ohh, I don't remember exactly where but while researching I had read that it's possible to stop the phone at that boot stage. Is something like that doable?
Click to expand...
Click to collapse
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
TheFixItMan said:
Found this it may help
Create a script and run it when adb is available on the device - usually sometime after boot logo
Windows version batch script eg run.bat
Code:
@ECHO off
cd /d %~dp0
echo.
echo Waiting for device…
adb wait-for-device
echo.
adb -d shell stop
adb pull (put directory location here)
Linux Version script eg run.sh
Code:
#!/system/bin/sh
echo " "
echo "Wating for device..."
./adb wait-for-device
echo " "
./adb -d shell stop
./adb pull (location of directory here)
Click to expand...
Click to collapse
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Z91 said:
So, I tried this. Bu I realized soon that adb devices was recognizing the device during the boot. SO, the scrip couldn't work I guess. Do I have to do something so that the phone gets recognized during boot.
Click to expand...
Click to collapse
If your phone doesn't reach the stage where adb is enabled there's nothing you can do

Categories

Resources