Long story short, I wanted to root my new galaxy victory 4G LTE from Sprint and put a custom rom on it. Followed rooting guides and that worked fine. Then I went to find a rom that would work and all I found was victorious, which I was so eager to try I didn't even think to read that part that said VM only. Got stuck in a boot loop. That's where I made the real mistake and decided to try a rom for another galaxy model, a custom s3 rom. Ever since that my touchscreen has been unresponsive, soft buttons and hard buttons work though. Using ODIN I've tried to restore to stock, I've used KIES to try to update, and everything has worked as far as I could want it to, but nothing restored touchscreen functionality. I am able to get into the hard button guided recovery menu and download mode, but have been unable to get anything touch based to work, and cannot find a CM non touch recovery that will work with this phone.
I've noticed that there have been threads created with this issue, however the solution, when there has been one, is device specific. So far that I have been able to tell no one has done this exact thing and solved it over the web with this phone.
If anyone can be of help, that would be great. I don't want to take it into a repair store or a sprint store and see what can be done to fix it if at all possible to do it myself.
bump
bump #2
Sph-l300 galaxy victory- touch screen unresponsive after cwm flash
As you very well know, there is not a whole lot of information on this problem. However I can suggest how to get CWM working on your STOCK or ROOT SPH-L300
Fix 1
oudhitsquad.com/android/Samsung/SPH-L300/Mod/recovery/CWMR-v6.0.2.8-Victory.zip(CWM zip file)
oudhitsquad.com/android/Samsung/SPH-L300/Mod/recovery/TWRP-2.4.3.0-Victory.zip
Put your phone into download mode by holding volume down+power then pressing volume up when prompted
Open Odin and click the PDA box and navigate to twrp.zip file and flash, reboot into recovery.
(I REALIZE THE SCREEN DOES NOT WORK, TWRP GIVES YOU ROOT BY DEFAULT SO JUST LEAVE IT PLUGGED IN AND....)
Extract the image from the CWM zip into c:\platform-tools
-Run a command prompt-
adb push recovery.img /sdcard/
adb shell
su
cd sdcard
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
After its finished writing hit ctrl-c to exit shell
adb reboot recovery
You now have the option to write any zip via CWM (Which uses buttons so no need for touch)
USEFUL LINKS -
dropbox.com/s/cchlft5ko44pe3z/build-prop-restore.zip (Flashing this returns your build prop to stock settings)
oudhitsquad.com/android/?dir=Samsung/SPH-L300/ (The #1 source for anything SPH-L300)
Godspeed, let me know what happens.
Related
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
Short story, there's no "ethernet" option when I connect my G3 to my PC, and I can't get ADB to work (just says device offline).
Long story:
Had the G3 rooted with TWRP recovery, stock ROM. Made the horrible mistake of allowing the OTA update to run (I wasn't quite awake yet when the message came through).
This of course got me into the recovery bootloop which I fixed with the Flash2FixStuckRecovery zip.
However, at some point TWRP disappeared and I can only get to the stock recovery now. So....in an attempt to get TWRP installed, I'm trying to get ADB to recognize the phone and I can't get it working. The only two options I have on the phone when connecting via USB is MTP and PTP.
I've tried changing to PTP before hooking up the USB cable, then connecting, switching, killing adp, restarting adb, switching, etc etc. No good. All I get is "device offline".
The phone still has root, but I've got to get a recovery on here somehow. I'm having some other issues with root explorer not being able to read anything on the SDcard so I want to wipe everything and flash a new ROM.
Anyone have any ideas on what I can do to get this thing working?
Maybe (no guaranty):
Extract the twrp 2.8.2.0 .img and put it on your phone, as discussed in this post: http://forum.xda-developers.com/showthread.php?p=57338272
Install Terminal Emulator.
Launch TE
Input the series of commands in the twrp OP starting with SU (you did say you have root -- hopefully SU). On the last command, just input "reboot recovery", leave out the "adb".
(Alternately, at the end just exit out, do a restart, and install 4-way Boot from Play Store. I use that app often to go from my regular system to Recovery, or to power-off rapidly -- pretty handy.)
With any luck, you should now have twrp 2.8.2.0 installed. At that point you can flash a 10b boot, system, and modem set of .img (use autoprime`s flash2Boot, flash2Modem, flash2System, and the .img files that bweN diorD links to in a post in the General area: http://forum.xda-developers.com/showthread.php?p=57360121 ).
You should then be at a 10b rooted phone, with twrp 2.8.2. Your choice what to do next, but I'd recommend using a file manager to rename the /system/app LGDMSClient files, so you won't get future OTA.
As I said, no guaranty, but the steps make sense to me. I've used TE interchangeably with ADB multiple times to install stuff.
Good luck!
Thanks for that.
Manually doing it in terminal emulator likely would have worked, but that link got me the idea to use flashify which I ended up doing and it did work.
Now just working on the rest of the repair.
Thanks again
Cool, I thought about flashify, skipped it only because I saw mixed reports on it being used with installing twrp.
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
ganiman said:
A while back, Amazon automatically pushed an update to my kid's Fire HD 6. Since then, the device will boot up and then it just freezes. The screen stays on the device is unresponsive. I am able to get in to recovery on the device, and that all seems to work fine, but booting in to Android is useless because it just locks and you cannot do anything with it.
I have been trying to go through this forum to see what my options are for sideloading another firmware or TWRP or anything like that.. and the posts here are not entirely helpful (for me at least). I'm used to going in to recovery and flashing some zip files to install TWRP, Cyanogenmod or GAPPS or anything like that... but the instructions I see for installing TWRP and the like do not seem to be the traditional methods. From what I think I am seeing, to install TWRP you need shell access to the tablet and then you can use dd to write TWRP to the correct storage space.
What are my options for doing things through recovery with adb? Or can I load an old firmware and then go from there? Any help is appreciated - would really love to get CM12 on this thing in the end if I could.
Click to expand...
Click to collapse
Your understanding of TWRP is right. Basically, we dd the twrp image with OS 4.5.3 bootloaders (the only bootloaders that will boot unsigned recovery) and then before leaving TWRP flash back (almost) current bootloaders and recovery.
You should be able to adb-sideload the OS 5.1.2 update to fix the freeze. Was device rooted before it updated? Do you know what OS it was on? If you have adb access while device is frozen, run these commands for current OS info:
adb shell getprop ro.build.version.fireos
adb shell getprop ro.build.version.number
No CM12 available. Mostly-working CM11 is here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138
BTW, I assume you tried wiping cache and/or factory reset in recovery. If not, I'd do that first.
Hello folks,
I tried following a root/flash tutorial online. This was my first experience. I have a Samsung Galaxy S5 SM-G900w (canadian version). I was running Marshmallow stock.
Rooted phone using Odin.
The tutorial called for recovery using Philz recovery, but it seemed it was outdated or updated, so I tried using Cyanogenmode Recovery.
After rebooting, I used what I believed to be close enough to the next step: Wipe data and erase everything option.
After that, I did not have a 'install from sd card' sort of option and ended up with a reboot of the phone.
At this point, I have option for ODIN or recovery mode. I can point to the SD card or adb.
Each time I try to point to a ROM using SD card option it fails to validate the signature and I cannot complete it. I have tried using different ROMs to no avail.
When I power on the phone normally I get the Samsung Galaxy S5 screen powered by Android with the following in top-left corner of the screen, yellow font.
"Set Waranty Bit: kernel"
By all means I am a newb here.
Would anybody mind lending a hand to get me headed in the right direction? Would like to try using a Cyanogen mod 13 ROM to start.
Kind Regards,
Lonely without a phone
side note: It would be nice to know what I may have done wrong and where to go from here.
Few things that you can try:
Use adb while in recovery to push a rom zip to the internal storage.
Switch to TWRP (preferred recovery for most phones any more)
Make sure the rom zips you are downloading are not corrupted by checking the md5.
I'd personally go with TWRP. I've modded 100s of phones and that's my go to as long as there is a stable version for the phone. https://dl.twrp.me/klte/ I'd use the newest tar file to flash in Download Mode if you are using Marshmallow roms. It also features a file manager that you can transfer zips from SD to internal, if need be. If you want to push files to internal, you can use this: http://forum.xda-developers.com/showthread.php?t=2317790. Put the zip in the folder, open the commands prompt and have phone plugged in recovery mode. Check connection by using the command: adb devices then push file by: adb push nameofrom.zip /sdcard/ Note - you might need to reboot recovery if it does not show up in the root of the intenal storage after successfully pushed to the phone right away.
Hard to say exactly what happened without knowing which versions of the roms and recovery you are trying.
Update
es0tericcha0s said:
Few things that you can try:
Use adb while in recovery to push a rom zip to the internal storage.
Switch to TWRP (preferred recovery for most phones any more)
Make sure the rom zips you are downloading are not corrupted by checking the md5.
I'd personally go with TWRP. I've modded 100s of phones and that's my go to as long as there is a stable version for the phone. https://dl.twrp.me/klte/ I'd use the newest tar file to flash in Download Mode if you are using Marshmallow roms. It also features a file manager that you can transfer zips from SD to internal, if need be. If you want to push files to internal, you can use this: http://forum.xda-developers.com/showthread.php?t=2317790. Put the zip in the folder, open the commands prompt and have phone plugged in recovery mode. Check connection by using the command: adb devices then push file by: adb push nameofrom.zip /sdcard/ Note - you might need to reboot recovery if it does not show up in the root of the intenal storage after successfully pushed to the phone right away.
Hard to say exactly what happened without knowing which versions of the roms and recovery you are trying.
Click to expand...
Click to collapse
Hey es0tericcha0s,
Thanks so much for your help. I focused on switching up the recovery img. I used TWRP and it was SOOOOOO much better/easier, so thank you.
After that, the roms were able to show up and be applied and everything was smooth.
You da man.
You're welcome. I love TWRP. ?