Rooted Stock with Xposed
Attempted stock rom via Kies
Emergency reset
Download completes of N910PVPU1ANK2_N910PSPT1ANK2_N910PVPU1ANK2_HOME.tar.md5
Install if it starts gets between 12-16% before stalling.
ODIN attempt to install will overwrite recovery and start transferring system then stall then complete
Complete(Write) operation failed
I am able to flash TWRP
I am unable to mount \system when I attempt to wipe the device
I am able to install CM12
Tried ODIN 3.07 3.09 and 3.10 and many usb cables
I am testing another machine with ODIN however drivers are failing at the moment and windows is failing to recognize the device.
Not sure alternative options I may have.
Now it seems if I am in downloading both pc's report
USB device not recognized
with each cable
Going to try and load smoothkat onto my sd and flash
Related
Hello,
I have a samsung galaxy pro tab 8.4 i have managed to get twrp recovery on it and flashed it with cm11 custom rom. How would i go back to the stock rom that it came with?
Also with the custom rom the multie button that shuts down apps,( bottom left) doest work as another option in some apps if you keep you finger on it. Is there away round this to work on custom rom?
Download odin and kies. (if you haven't already) install kies to get the drivers and then odin
Download the firmware from here http://www.sammobile.com/firmwares/3/?download=25801
Unzip the update file on the same folder as Odin.
Reboot in download mode: press volume down, home and power buttons at the same time. Then connect the device
On Odin now the ID:COM section should be either yellow or blue. Also, the “added” message must be displayed.
If not, you need to close Odin, unplug the USB cord, reinstall the drivers on the computer and start the update process from the beginning.
After resolving the issues, from Odin you need to select “PDA”.
Then pick the update file from desktop. and click start
You can unplug the USB cable and reboot your tablet when on Odin the “pass” message will be displayed and when the ID:COM section will be green.
If odin gets stuck reinstall drivers and try again. Also, if you bootloop wipe data and cache in recovery.
@mackenzie121
Hamza Murad said:
Download odin and kies. (if you haven't already) install kies to get the drivers and then odin
If odin gets stuck reinstall drivers and try again. Also, if you bootloop wipe data and cache in recovery.
@mackenzie121
Click to expand...
Click to collapse
Or you can try also change your Odin on another version.
I'm wanting to install Cyanogenmod 12 on my old rooted I8150 with 32Gb SD card, but I'm having problems.
I installed USB drivers onto my Windows XP OK, and then downloaded Odin v3.09 and Clockworkmod 6.0.5.4.
With the I8150 in recovery, Odin shows blue on 0:Com4 and the phone shows "Downloading do not turn off"
Odin finds the Clockworkmod tar file ok.
I press Start in Odin, and it shows "SetUpConnection'", but nothing happens. It stays until I unplug the USB or the battery, when it shows FAIL
Any advice would be welcome.
Is there an alternative way to instakk without a PC, eg by putting the files directly on the SD card?
pintosal said:
I'm wanting to install Cyanogenmod 12 on my old rooted I8150 with 32Gb SD card, but I'm having problems.
I installed USB drivers onto my Windows XP OK, and then downloaded Odin v3.09 and Clockworkmod 6.0.5.4.
With the I8150 in recovery, Odin shows blue on 0:Com4 and the phone shows "Downloading do not turn off"
Odin finds the Clockworkmod tar file ok.
I press Start in Odin, and it shows "SetUpConnection'", but nothing happens. It stays until I unplug the USB or the battery, when it shows FAIL
Any advice would be welcome.
Is there an alternative way to instakk without a PC, eg by putting the files directly on the SD card?
Click to expand...
Click to collapse
You can try to download clockworkmod on your sd card to flash from stock recovery, then copy the cyanogenmod and gapps and install them simply.Search on the forum how to flash recovery from the stock one.After, watch the install tutorial from every custom rom.
I wrote this guide.....
http://forum.xda-developers.com/showthread.php?t=1941028
It gives instructions for flashing CWM with a terminal emulator command.....no need for a PC.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Hi
is it possible to use recovery mode rather than Odin?
For eg
1/ save samsung stock rom on sd card
2/ boot phone into recovery mode
3/ select install and point to the sd card file location and install?
I've installed kies to get the usb drivers, made sure its not running, run odin 3.09, used a good quality cable, but not exact one phone came with (still hunting around for it). But Odin can not recognise the phone.
try diffetent version of odin and enter download mode
NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.
So, I've wanted to root my Galaxy Tab S 10.5 SM-T815 (6.0.1) which didn't go quite as planned. I ended up in a boot loop.
After reading forums Ive thought it should be best reinstalling a stock rom to my device.
In Download mode I got kies working, It downloaded the software, but the installing process seems to tuck at 2-3%, tried it 3 times.
So the last time I've copied the rom files from Kies's temp folder and tried Odin. Unfortunately looks like it has the same problem.
I load in the 4 files, and hit start. Everything looks fine, untin I get stuck at system.img
Then nothing happens, the green bar under "system" goes like 1mm, and stops.
If I reboot I get an error saying software upgrade failed and I should connect the device to Kies for recovery.
I'd like to ask for some advice if you can help me, thanks.
Figured it out
So I was at the failed upgrade screen.
Then I took out the sd card ( don't know if mattered) and via Odin I succesfully installed the rom.
I am having close to the same problem. Got the message to connect to Kies. Gets to the installing screen and after 3 hours still at 0%. Try ODIN and it shows:
<ID:0/018> NAND Write Start!!
<ID:0/018> boot.img
<ID:0/018> recovery.img
and then just sits there. No process line no nothing.
I can get to the ODIN mode, but cannot get to recovery mode.
Any thoughts on what to try next?
Not sure what corrected my issue. Downloaded Android Studio to try and get to recovery by ADB (not sure if that is possible from ODIN mode) and noticed it installed an android driver. Tried ODIN again and this time it took.