Hello there.. I normally don't have a problem figuring out what to do but I'm totally stuck here. I have a Sprint Galaxy S4 SPHL720T. I was rooted and running a custom ROM. I was having issues with the wifi so I decided to flash back to GPE 5.0.1 here from the xda forums. I am running twrp v2.8.4.0. I made a backup and wiped system/data/cache and dalvik. I went to install JFLTE-GPE-20150303 (LRX22C) from ultimarom.com via here at XDA. It said zip is corrupt. So i redownloaded on my PC and transferred it to my sd card. Still said corrupt. So I downloaded a different ROM on my PC and moved to SD. Still said corrupt. I tried to flash a GAPPS package and it worked but no ROMS I tried would. I tried to install my latest backup through recovery. It said MD5 doesn't match. If I hit reboot in twrp it prompts to install superuser because the phone doesn't appear to be rooted. If I hit that it runs the script for about 2 seconds then reboots. It won't boot into the OS as there is no OS and if I reboot into recovery it still gives me the "install su" prompt at the reboot screen. So then I hooked up into ODIN and download mode and flashed "CF-Auto-Root-jflterefreshspr-jflterefreshspr-sphl720t.tar.md5" and "openrecovery-twrp-2.8.4.0-jfltespr.tar". Still having the same issues. I have no idea what to do at this point. Any help would be GREATLY appreciated as I need my phone for work and play .
Thanks,
Aaron
Related
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).
Good morning,
as always when using a Samsung device, pretty much nothing seems to work for me. I was on stock rom, flashed TWRP via Odin, but it would just reboot from boot to recovery screen to the stock ROM (yes I unchecked auto reboot, took the battery out and booted straight into recovery, but still it would boot up the stock ROM after saying 'recovery' in blue text). So I used CF Auto Root to gain root access and flashed TWRP via the Manager app, I'm surprised this whole procedure worked out, but I was finally able to enter the recovery. I proceeded to flash CM13, the unofficial optimized build. However, I could not install GApps because the Stock gapps were too large for my system partition. So I tried to download nano GApps via the AOSP browser, only to find out that it force closes when downloading any file. After that I booted to TWRP wiped and flashed the official jfltexx CM13 nightly obtained via the CM updater. Still force closing AOSP browser on any download. Great - so I just figured I'd boot up recovery again, mount USB and transfer the gapps from my computer. But guess what? The recovery somehow disappeared it seems. When booting to recovery, it is again rebooting to boot to the ROM. Therefore I started up Odin to flash TWRP 2.8.6 tar - still the same behaviour.
TLDR; Do you recommend another bootloader? Since this one does not seem to like custom recoveries. Or should I try CWM? Any help appreciated. Thank you in advance!
CWM is outdated. You will have even more problems with it.
Regarding the browser force close. You have to give the browser storage permissions. Afterwards it will not force close anymore when downloading. The permission prompt will not automatically show up. You have to do it manually.
As for your TWRP issue, I don't really know what to say. I've never had problems. Although, I'm on XXUHOB8 bootloader and baseband.
Try TWRP 2.8.7.X. I am currently using 2.8.7.2 with F2FS support by AntaresOne. The official TWRP is only at version 2.8.7.0 I think.
GDReaper said:
CWM is outdated. You will have even more problems with it.
Regarding the browser force close. You have to give the browser storage permissions. Afterwards it will not force close anymore when downloading. The permission prompt will not automatically show up. You have to do it manually.
As for your TWRP issue, I don't really know what to say. I've never had problems. Although, I'm on XXUHOB8 bootloader and baseband.
Try TWRP 2.8.7.X. I am currently using 2.8.7.2 with F2FS support by AntaresOne. The official TWRP is only at version 2.8.7.0 I think.
Click to expand...
Click to collapse
Ah okay, thank you! I just flashed HOJ4 bootloader and modem, still can't boot TWRP 2.8.6.0. I'd like to try the AntaresOne 2.8.7.2, but don't know how to flash it using Odin since it's in zip format. Just unpacking it and creating a tar of the files crashes Odin :c. Thank you!
Never mind, just flashed TWRP 2.8.7.0 img using Rashr, so far the recovery has not yet vanished.
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
EDIT:
Please delete thread. There is an issue with my SD card resulting in files being corrupted. Massive losses. I was able to successfully install ROM by uploading files to Internal Storage
Hello,
I have been attempting to flash AryaMod : http://forum.xda-developers.com/galaxy-note-3/development/rom-aryamod-v1-3-tw-lollipop-5-1-1-t3326976/post67619860#post67619860
on my SM-N900W8. From the stock rom, I rooted it using CF-Auto-Root, then installed TWRP.
After downloading and putting all the necessary files on my SD Card, I attempted to install this but TWRP kept giving me file errors "Error: Secure Check Fail : aboot" when attempting to install anything, the kernel, the rom, the bootloader and modem, etc. Nothing was working.
I read that TWRP isn't very good with Aroma stuff and I should be using CWM, so I attempted to install that. Everytime I installed CWM, it would say it is going into recovery, then restart the phone, over and over..
Figured that I needed to just do a fresh install. I get a new Stock Lollipop 5.0 DOH1 from Kies, reroot with CF-Auto-Root, then install CWM from ROM Manager. Same thing, recovery bootloops.
Is there a way to fix either CWM or to get Aryamod to work with TWRP? Is the CF-Auto-Root breaking the recovery install since it installs through recovery as well?
At this point I've spent an entire day trying to get Aryamod with no luck. What the heck am I doing wrong?
Hello,
I'm trying to install a custom rom on my note 4.
I rooted successfully, and installed TWRP through flashify.
First issue I ran into is that the phone got stuck in a bootloop after installing TWRP. All fine I said, it's cool since I want to flash a ROM anyway.
I downloaded the ROM for my device, and after I clicked factory reset and tried installing the ROM, I got the error
Code:
unmount of /system failed; so such volume
I looked around online, some posts said that it's fine, the ROM will install anyways, but that's not the case. The ROM didn't install (the process is finishing way too quickly), and I'm still stuck at bootloops.
I'm running TWRP 3.0.2.0 (newest version), android 5.1.1, on my note 4 N910H.
I have access to TWRP and to download mode, and I can move files between the PC and my phone using an external memory card.
PLEASE HELP ME :crying: