To this point I have managed to root and unlock my Captivate with great success. I have also managed to run various ROM's, Cognition, Serendipity, Paragon, etc.
I was using Serendipity 5.3 and the Steam kernel, I tried adding afterburner features and have now gotten stuck. The phone continues to reboot into steam recovery and I can navigate, but always receive "Partition /res/.fake/gingerbread/system could not be mounted! What should I do?"
I can get into download mode very easily by pulling the battery, putting battery back in, holding vol up and down then plugging phone into usb cable. From that point it just hangs plugged in or not, no communication with the pc, I can see the device as an Android UMS composite drive but can't write to the drive. I have tinkered in the console mode from Steam recovery and some of the usual commands will work such df -h to see drives and size, ls shows all the contents on the phone.
I run Linux on both my desktop and laptop, I have Xp in a VM with USB support, it shows as a Nexus device but Odin will not communicate with the device either. I have tried Heimdall, but receive the following.
Claiming interface... Success
Setting up interface... Failed!
I originally used Heimdall when flashing the first time then moved to CWM and never had an issue until I began fooling around with the kernel.
I'm hoping this is a repairable situation, maybe using the console in steam recovery? Just not sure what the commands might be or I may be barking up the wrong tree altogether.
Thanks in advance for any help offered.
I've been trying to unroot my Galaxy Tab 2 10.1 p5113 and go back to stock for the last few days with no success. I have only Linux machines in my house, so I've been trying with heimdall. From the output I get, it seems as it is succesful, but It still has root. After days of reading, this is what I've narrowed it down to.
I downloaded this file.
P5113UECLK7_P5113XARCLK7_XAR.zip
Which is supposed to be the stock firmware.
I extracted it, then got these 2 files.
SS_DL.dll
P5113UECLK7_HOME.tar.md5
Then I removed the md5 file extension and left it with just .tar and extracted that file. I got these files:
recovery.img
boot.img
system.img
hidden.img
cache.img
Sbl.bin
So I put the tablet in download mode and connect it to the Linux machine and this is my output from terminal
[email protected] ~/Downloads/P5113UEBLG2_P5113XARBLG2_XAR/P5113UEBLG2_HOME $ heimdall detect
Device detected
[email protected] ~/Downloads/P5113UEBLG2_P5113XARBLG2_XAR/P5113UEBLG2_HOME $ sudo heimdall flash --RECOVERY recovery.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Then it reboots like normal and I still have root.
I aslo tried transferring the .zip file to the SDCARD and tried to flash from recovery, but I get an error doing that.
Also I saw another way was to download Root_Remover.zip and flash that file from recovery, but it looks as if it flashed but when I reboot it still has root.
Can anyone re-host the P5113UECLK7_P5113XARCLK7_XAR anywhere? I've tried ~100 links and the file no longer exists anywhere on the internet. I'd love to try to fix my soft bricked tablet!
You try sammobile? I just looked and it was there, but, I didn't click download as I'm on company phone right now (data watchers)
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Hi
i am using Huawei G610-U20 since 3 years and it was working fine.
3 weeks before I found that the phone is getting restarted without any reason but with no fixed frequency. sometimes its own, sometimes while connecting to the pc or sometimes when connecting power.
Then I tried to uninstall some apps like bittorrent, whatsapp etc..it shows app uninstalled successfully but after a restart, these apps are back there.
I tried to flash the phone by using MTK Droid Root & Tool and as to begin with ROOT option, when clicking root button, it shows the following error:
--->>> Connect to device <<<---
ERROR file isn't found D:\Tools\Mtk_Droid_Tool_v2.5.3\files\pwn
/system/bin/sh: /data/local/tmp/pwn: not found
ATTENTION! Requests for confirmation on the device screen are possible!
--- ERROR : SU inaccessible
--- Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Then I went through the post and created scatter file. Then start with SP Flash tools, did the following things as mentioned in the thread.
1. Loaded the scatter file
2. Choose path and a ROM file name
3. Determine the ROM_ size by finding out the address after the RECOVERY IN scatter file and provide start address too.
4. Turned off the phone
5. choose Read Back ROM_
then I connect the cable to the pc. after few seconds, it shows the following error
BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL(2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
As they mentioned, I tried to change the USB port and cable but results are same as before.
I notice one thing. Even though I enabled USB debugging, after a restart USB debugging is disabled.
It means whatever things I did before a restart, it reverses after a restart.
Please help me.
raleindia said:
Hi
i am using Huawei G610-U20 since 3 years and it was working fine.
3 weeks before I found that the phone is getting restarted without any reason but with no fixed frequency. sometimes its own, sometimes while connecting to the pc or sometimes when connecting power.
Then I tried to uninstall some apps like bittorrent, whatsapp etc..it shows app uninstalled successfully but after a restart, these apps are back there.
I tried to flash the phone by using MTK Droid Root & Tool and as to begin with ROOT option, when clicking root button, it shows the following error:
--->>> Connect to device <<<---
ERROR file isn't found D:\Tools\Mtk_Droid_Tool_v2.5.3\files\pwn
/system/bin/sh: /data/local/tmp/pwn: not found
ATTENTION! Requests for confirmation on the device screen are possible!
--- ERROR : SU inaccessible
--- Through CWM it is possible to get root on this phone! Look URLs :
http://forum.china-iphone.ru/viewtopic.php?p=502084#p502084
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Then I went through the post and created scatter file. Then start with SP Flash tools, did the following things as mentioned in the thread.
1. Loaded the scatter file
2. Choose path and a ROM file name
3. Determine the ROM_ size by finding out the address after the RECOVERY IN scatter file and provide start address too.
4. Turned off the phone
5. choose Read Back ROM_
then I connect the cable to the pc. after few seconds, it shows the following error
BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL(2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
As they mentioned, I tried to change the USB port and cable but results are same as before.
I notice one thing. Even though I enabled USB debugging, after a restart USB debugging is disabled.
It means whatever things I did before a restart, it reverses after a restart.
Please help me.
Click to expand...
Click to collapse
Hi, Thanks for using XDA assist.
It looks like there is no dedicated forum for your device, however
There is a general forum for android here http://forum.xda-developers.com/android/help where you can try to ask to get expert's help.
Good luck
Hi, a Problem arose using Heimdall to root my phone: Samsung Galaxy SIII, GT-i9305 Build: KTU84P.I9305XXUFNL1.
I am using Heimdall-Suite 1.4.0 from the official website, which should be the newest. The installation is running off a Windows 7 64-bit OS.
First off: most of the things I did, I did according to the Cyanogenmod Guide
I went into advanced settings and checked 'USB-Debugging'
I uninstalled all device drivers from Samsung, and made sure no software was active on windows.
I installed the 'Zadig' Drivers according to the linked guide.
I disabled user account controll as nothing was working, and restarted my PC several times.
When opening Heindall (with admin privileges) i was able to connect to my device, and download the PIT-File. I saved it, selected it in the 'Flash' menu and added the CACHE and RECOVERY files accordingly. When pressing the Start button i get the following message:
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
[...]
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...
I get this Error every time. When using the Command Window most of the time I get the Error message '-7'. The recovery file doesn't load.
I have tried every USB connection on my PC, tried it on a second PC, cleaned my USB-Cable etc...I just can't upload any data to my device.
If any of you can help me with this problem i'd be happy. This is the first device I am trying to root / install a new ROM on.
Best Regards, Alex
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting
The experts there should be able to help you.
Kind regards and good luck
Trafalgar Square
XDA Assist
First let's get the warnings out of the way:
This is a dangerous tool. It can render your device permanently unusable.
If you use it, your warranty will likely be void.
You accept all responsibility for the consequences.
This is not an official ZTE unlock tool. The official ZTE unlock tool is in another thread.
Acknowledgments
Special thanks to @rombdeta for providing the OEM programmer binary. This would not be possible without his help.
What is tuliptool?
This tool allows you to:
Check status of your boot loader
Unlock your boot loader
Lock your boot loader
Install a custom recovery
Install a custom boot image
NOTE WELL
The first rule of intelligent tinkering is to save all the parts.
Always backup your partitions before writing new contents, so that you can get back to where you started.
Never write both boot and recovery in one session. Always make sure that you can boot into the other partition in case something fails.
Locking and unlocking will erase all user data. Make sure you backup first!
The zip includes:
tuliptool for Linux
tuliptool for Win64
tuliptool for Win32
tuliptool for MacOS
Preparation
1. Extract the package.
You will find the binary files listed above. Note: This is a command line utility, so you must open a command prompt to run it.
2a. Setup for Linux
Create a file named /etc/udev/rules.d/99-qcom.rules with this content exactly as shown:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
Ensure your login user is in the plugdev group.
2b. Setup for Win32/Win64
Download zadig.
Connect your device in EDL mode (see below).
Windows will want to install the Qualcomm USB driver. We won't be using it so you can cancel if you wish, but it won't hurt anything.
Run zadig. Find device 05c6:9008 and install the WinUSB driver for it.
Disconnect the device.
2c. Setup for MacOS
No setup should be necessary.
3. Download boot and/or recovery files to flash.
You will find these in other threads in this section.
Connecting in EDL mode
Via adb
This should work for all models, but you need adb access.
adb reboot edl
Via key combo
If you have a US model device (or the aboot from a US model device) you may use the key combo:
Power off and unplug the device.
Hold both volume buttons.
Plug device into your PC.
Wait about 3 seconds and release the buttons.
Note: There will be no feedback on the device -- no lights, no vibration, nothing. The only way to verify that the device is in EDL mode is that device 05c6:9008 is visible on the PC.
Usage: (un)locking
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, unlocking seems to be completely unnecessary. This section is mostly provided for completeness.
tuliptool lock status
tuliptool lock unlock
tuliptool lock lock
Usage: reading boot/recovery
Note command line options have changed
tuliptool read boot
tuliptool read recovery
Usage: writing boot/recovery
Note command line options have changed
tuliptool write boot <filename>/I]
tuliptool write recovery <filename>
So, for example, to write a TWRP image, run:
tuliptool write recovery tulip-twrp-7.1-r1.img.
Multiple operations
This is a "one shot" tool. After performing an operation, it will reset the device with a 5 second countdown. If you wish do perform multiple operations (eg. backup, unlock, flash), simply hold down the volume buttons while the device resets and it should go back to EDL mode.
Download
tuliptool.zip
md5=58f34850005510b51a832d27a6bce607
Common problems
Device not found: first enter EDL mode, then run the tool.
Device is visible in device manager or lspci but cannot be found by the tool: connect directly to the PC, not through a hub.
Windows says bad file descriptor: the WinUSB driver is not installed.
Linux says permission denied: your login user is not in the plugdev group.
Why call it tuliptool?
Tulip is the device "code name" for the Axon 7 Mini (at least the US version).
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Perhaps try running it as administrator? I'm heading home from work and then I'll be taking a shot at this myself.
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Meme Queen said:
first! it's nice to see someone working on the lesser-known devices for once, thanks love!
okay so on that note everything goes perfectly, right up until i try to actually run the tool lol. installing the driver through Zadig does fine, and from everything i can tell, the PC recognizes it. i mean, it's in EDL and everything. what's going wrong? running the tuliptool-win64.exe just opens and closes instantly, and opening a command prompt in the directory just tells me that tuliptool is not a valid command/operation blah blah blah. it's probably something simple but i'm kind of trying to get all over this so :good:
Click to expand...
Click to collapse
tdm said:
I just tried on a Windows 10 virtual machine and it works perfectly.
This is a commandline program so you open a command prompt and type eg:
tuliptool-win64.exe lock status
Click to expand...
Click to collapse
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I guess im stuck waiting for the update.zip because Zadig is refusing to install drivers. no matter what i do it will not install drivers. it keeps telling me "Remote Source Not Allocated: Driver install Aborted"
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Meme Queen said:
so it's gone past that, but now it fails to unlock with an unknown error. checking unlock status after returns "Failed to send programmer: failed to read packet". i have to unplug it and go back into EDL mode, and when i check the lock status, it says unlocked and not tampered. when i try to go ahead with flashing TWRP, it crashes with this:
Sending programmer...Connecting to programmer...log: [email protected] [email protected]
log: [email protected] [email protected]
log: Finished sector address 0
log: Finished sector address 0
log: Finished sector address 0
Writing recovery ...
terminate called after throwing an instance of 'std::runtime_error'
what(): No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Click to expand...
Click to collapse
tdm said:
Hmm, looks like something strange is going on there. I'll take a look tomorrow.
Click to expand...
Click to collapse
thanks! if there's any information you want me to provide, just let me know.
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
pxzei said:
I cannot get my device to boot into EDL mode, everytime I try it gets stuck on the splash screen. Can anyone help?
Click to expand...
Click to collapse
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
MrWhite0429 said:
Ok. Now ive retraced my steps and found that letting the qualcomm drivers install will not allow the WinUSB drivers to install in Windows 7. Once I told Windows update to not install the qualcomm drivers Zadig was able to install drivers successfully. Now that the drivers are installed, Device is in EDL (im assuming this because screen is black but my computer is recognizing the device), I run the Tuliptool and it keeps telling me "Device Not Detected" . I cant seem to get it to find the device but i can see it in Device Manager just fine. And it shows the WinUSB drivers are installed correctly, any insight on to what I may be doing wrong?
Click to expand...
Click to collapse
tdm said:
There won't be any lights or other indication that the phone is on when it's in EDL mode. But you should see the device in device manager, as USB id=05c6:9008. I don't normally run windows so I can't give detailed steps to find that.
You may need to have admin privileges to talk to USB devices, I'm not sure.
Click to expand...
Click to collapse
Device Shows connected and drivers installed under device manager.
Command prompt is being run as so:
Start --> type cmd ---> Right click on Command prompt ---> Run as Administrator
cd C:\users\admin\desktop\tuliptool
C:\users\admin\desktop\tuliptool> tuliptool-win64.exe lock status
Device Not Detected
---------- Post added at 03:59 AM ---------- Previous post was at 03:38 AM ----------
UPDATE:
I found that I had to use a USB 3.0 hub in order to get the phone to be detected.
Once detected I ran commands as followed.
tuliptool-win64.exe lock unlock
(The unlocking procedure said it failed, phone bootlooped three times, then it showed as unlocked when I ran the Lock status command)
tuliptool-win64.exe read boot
(This created the backup-boot.bin file in the directory)
Tuliptool-win64.exe read recovery
(This created a backup-recovery file in the directory)
tuliptool-win64.exe write boot
Its at this point here I get a Runtime Error as well. The entire process comes to a halt.
Thsnks, tried that, but no luck. It's still stuck on the splash screen.
Update: The device is running B09 7.1.1, The charger seems to be ZTE authentic. Single sim variant. If you need more info, let me know.
rombdeta said:
Yeah, try pressing the power button for 10 seconds, until the display turns off, hold down VOL + and enter recovery "power down" and try to enter edl again
Click to expand...
Click to collapse
tdm said:
This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device.
[/B][/COLOR]
Click to expand...
Click to collapse
Awesome you got the tool out, I think I am going to wait for the 'Official' tool so if I ever need to send it in for repair in the next 2 years I can say 'well I used your tool' lol
Can't wait to see the roms @tdm, keep it up and I think the mini is going to get a lot more interesting.
I'd like to get a bloat removed(if any) and more lightweight faster rom on mine, maybe try the latest cyanogenmod or w/e they call it now and AOKP, etc.
New roms without MiFavor would be awesome too and ones that improve performance!
ZTE
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
CRAFTER0302002 said:
@tdm, do you think zte will also be giving the official boot loader unlock soon? If not I will use yours that looks solid, but just thought I would ask first.
Click to expand...
Click to collapse
First post:
"This is not an official ZTE unlock tool. ZTE will likely be providing an official boot loader unlock in the coming few days. You should wait for that if you have any reservations about modifying your device."
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
tdm said:
Okay I've uploaded a new version of the tool with better error handling and better error messages (particularly for the Win64 version). I successfully wrote TWRP using the Win64 version. Please check the OP for the new link and download it again.
@Meme Queen and @MrWhite0429 please try again. I think the problem was that you didn't copy tulip-twrp-7.1.1.img to recovery.bin.
I can modify the tool to take a filename as a parameter if that helps with the confusion.
Edit: Also fixed a typo in the OP which had the wrong filename in the example. This may have been the source of the confusion.
Click to expand...
Click to collapse
as in rename to recovery.bin?
Yes, that.
MrWhite0429 said:
as in rename to recovery.bin?
Click to expand...
Click to collapse