To start, I am trying to flash TeamWin Recovery to my S5 with Heimdall in order to install CM12 nightlies. I've been told elsewhere that I should try executing print-pit before actually flashing the recovery in order to test if things work instead of having the actual flash fail and brick the device. However, no matter what I try I can't get it to work. I am running Windows 8.1 Pro x64 with libusb0 drivers installed from Zadig. Below is the output of "heimdall print-pit --verbose":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried switching USB cables, USB ports, reinstalling drivers, reinstalling Heimdall, wiping /cache, and rebooting. Does this mean that I can't flash? Has anyone else found a solution to this problem?
recalculated said:
To start, I am trying to flash TeamWin Recovery to my S5 with Heimdall in order to install CM12 nightlies. I've been told elsewhere that I should try executing print-pit before actually flashing the recovery in order to test if things work instead of having the actual flash fail and brick the device. However, no matter what I try I can't get it to work. I am running Windows 8.1 Pro x64 with libusb0 drivers installed from Zadig. Below is the output of "heimdall print-pit --verbose":
I've tried switching USB cables, USB ports, reinstalling drivers, reinstalling Heimdall, wiping /cache, and rebooting. Does this mean that I can't flash? Has anyone else found a solution to this problem?
Click to expand...
Click to collapse
Last time I checked, which has been awhile, heimdall did not work properly for the s5. Unless something has changed you should stick with Odin. A few of the stock packages have pit files included, so if you need one they are around and I think oa6 has one too.
Hello
Related
Hi there!
I bricked my p920 a week ago while trying to flash the ported 3D-ICS rom from xbsall. I don't really know what I did wrong, but somehow I destroyed my bootloader.
However, using the "p920 resurrection guide" (http://forum.xda-developers.com/showthread.php?t=1942836), I was able to boot my phone again and to restore my nandroid backup, so that I'm back to stock-GB now (rooted, CWM installed).
Everything works fine, except that my phone does not find any network and has no IMEI anymore (yes, I know, these two symptoms are connected )
I tried to recover my IMEI using this guide here (http://forum.xda-developers.com/showthread.php?t=1734330), but I always get stuck at point 9 of the instructions (trying to type in the original IMEI using Tutty).
So far, everything goes according to the guide. I connected Tutty with my phone using COM-port 3 (the only port available in Tutty) and when I type "AT" in Tutty, the expected "OK" comes as a response.
But when I try to type "at%imei", the only response I get is "ERROR" and no dummy-IMEI shows up.
By accident I also typed "atimei" one time, the response I got was "56000 56000 OK".
...later today I'll add a screenshot with my latest Tutty-session...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, what am I doing wrong? So far I tried all that with two different Win7(64bit) PCs and via a virtual PC running on WinXP (32bit). All drivers for my phone, Omap and Infineon are installed (Edit: at my last try yesterday, the Infineon-driver didn't seem to work. After starting CP-download mode my PC gave an error, stating it wasn't able to install drivers.)
I also tried to use Putty and Hyperterminal instead of Tutty, but with the exact same results.
Any ideas?
Bye
a noob with an O3D
I was in the same boat as you but i flashed v10k kdz file with lg b2capp and my Imei was restored.
Hope this helps
Sent from my LG-P920 using xda app-developers app
Yup..just flash kdz file and your problem will gone
Use This Tuts
Fixed it!
Good news!
I fixed my problem.
Thanks for your suggestions about flashing a kdz, but I fixed it another way, because I wasn't able to find a functional download link for any kdz-file. o,O
So here is my solution:
I think my problem was, that I backed up my system with my original nandroid-backup too early.
I repeated the whole "resurrection guide"-procedure and let the V21E stock OS installed, in this OS I had no problems fixing my IMEI using Tutty,
Afterwards I then just booted into CWM and flashed my nandroid-backup from before this whole s**t.
I thank all of you on this wonderful forum, special thanks to all the devs for their life-saving guides!
Hi Guys,
I have a problem with my ZTE v967s, if you have any advice, I would really appreciate it!.
How did the problem appear:
1. My phone gave me an error that I have insufficient memory (apps had just few hundred MB, 1 GB was "Missing") so I assumed that it is probably a log file which was soaring and cutting my memory)Phone also had problem to start, I had to restart it few times will the android loaded properly (I assumed it was from the insufficient memory)
2. I have tried following:
a. Factory reset -> it didn’t work, It just restarted to phone.
b. Recovery mode - I wasn’t able to get in to it by holding "Vol+" + "Power" (I should have CWM installed, I did it when I had the phone new together with Max Flavor ROM.
c. I tried following tutorial http://kumaravel-s.blogspot.com/2013/09/storage-space-running-out.html (basically deleted data/log_other_mode)
After the deletion of data/log_other_mode, my phone doesn’t load at all. I either freeze on ZTE logo or it gives me error "encryption unsuccessful reset android" (button reset doesn’t react), lately, it just gives me the ZTE logo
What I tried to solve the problem:
Downloaded SPFlashTool backup ROM from Carliv (http://forum.xda-developers.com/showthread.php?t=2393986 ) and I tried to flash it in to my ZTE using SP Flash Tool. First 2 steps (red, purple) went ok, the third one (yellow) freezes on 0% and eventually it gives me error "BROM ERROR : S_DA_SDMMC_WRITE_FAILED (3149)"
Screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same error when I flash whole ROM or just Recovery.
Drivers should be ok, I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2206421
Have somebody had this problem? Do you have some advice what might help?
Thank you!
munky02
Try spflash tool on different pc with windows xp
Dovahpig said:
Try spflash tool on different pc with windows xp
Click to expand...
Click to collapse
I have tried it, the problem persists. Do you have any other ideas?
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
hey, i've been trying to root 920P (S6 Sprint) for whole week now, i've tried everything i found, tried to flash few versions of TWRP, failed at 99%, tried to root directly with CF-Auto root and it fails mid-flash, tried multiple versions of odin, still same results :|
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it's really weird, I've succesfully flashed 920F (International) without any problem multiple times. I can flash stock rom so it's not hardware's fault. Am i missing some simple newbie step?
{FIXED}
i was missing newbie step like i suspected xDD i forgot to enable oem unlock
what is the solution ?
i have the same problem. what is the solution ?
aLwaYs7Online said:
{FIXED}
i was missing newbie step like i suspected xDD i forgot to enable oem unlock
Click to expand...
Click to collapse
my device is sm920A . it is at&t . i cannot find oem unlocker
Possible Solution to Odin "failed" messaged whilst flashing
Warm greetings to all.
I have previously encountered this problem before, ive tried clearing the cache and formatting with still no luck
Eventually I wanted to try something, I loaded my software I wanted to flash on a USB.
I then used an OTG adapter to connect the usb to my phone. I then booted into the recovery ( I have TWRP) and chose install from external storage. To my surprise it worked.
NOTE: I am not sure if this method will work on stock recoveries. Also if you have an external hard drive it works as well
Also note. My S6 is an international version i believe G925F
Wishing you all the best of luck if I was not able to help
sazid311 said:
my device is sm920A . it is at&t . i cannot find oem unlocker
Click to expand...
Click to collapse
did you enable developer settings?
Yes
Dear Community!
I have an SM-G930F in a very hard situation I dont know what else I can do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I installed a Pixelexperience ROM to my S7, worked pretty well, no issues (Rebooted many times, without any issue*)
*One time the battery drained and it turned off so I plugged it into a charger and it went to the TWRP loading screen.
I can hardly go into the Odin (Download) mode, but the problem is:
Windows gives me an error saying "A request for the USB device descriptor failed (Code: 43)"
The error was there since the Pixelexperience OS was installed (Even when the phone was on!)
I tried everything what possible to try to reinstall the stock firm, or just boot into the pixelexperience, but I think this is the end for the phone.
What I tried:
Cable:
- Tried 5 different cables, tested each other with other devices, everyone is working, but not with my Samsung
PC:
- Tried with 4 different PC running Windows 10/11
- Tried with USB 3.0-2.0
- Tried with, and without Samsung drivers installed
Phone:
- Ofc, tried to force reboot with volume down+ power button (Same thing, booting into TWRP)
- Let it drain overnight. Last thing I tried to do, but sadly no change.. If I turn on a charger, it boots into TWRP, not even to the "offline" charging screen.
If anyone can help me to cure this stupid problem, I would be very thankful.
Or maybe this is the end?
The partition has probably been corrupted. Don't ask me why, there can be many reasons. If you can turn on the phone in download mode then try uploading the stock ROM with Odin.
ze7zez said:
The partition has probably been corrupted. Don't ask me why, there can be many reasons. If you can turn on the phone in download mode then try uploading the stock ROM with Odin.
Click to expand...
Click to collapse
This is the sad part, because with 4 different pc with 5 different cables not recognise my phone as an USB device (Code:43) You can read it in the post. :\