So after exhausting all options, I turn to the experts for help. I have a friend in the UK, who wanted to downgrade his Galaxy s5 g900f 5.0 to 4.4. He's familiar enough with basic odin/recovery use, but only vaguely.
He wanred to downgrade, so I had him flash TWRP 2.8.7.0 via Odin. All went well. I then had him make a full back up, boot, system, data etc. He has no sd card, so after the back up I had him move his entire internal storage (except the back up) to his pc. Then we downloaded OmegaDroid v13 (4.4) for the g900f. Flashing went as expected to start, did full wipe, flashed the zip (aroma installer). The two options for kernel choice with this ROM or stock kernel or Omega kernel. Flashing with stock kernel sends the phone into an infinite bootloop, flashing with the omega kernel never boots at all (black screen with blue led on, I had him leave it like this for an hour to make sure). So I told him to restore his back up until we can find another 4.4 to try. Well restore fails every time.
No problem, I thought, we can mount usb or use adb sideload. So I had him download CM 11. Had him boot to recovery and mount usb while connected to pc. The box wont check, just no response. So I got him to download adb and drivers, had him verify his isntall. The problem here is adb devices lists no device. Odin however can communicate with it.
Am I missing something. Is there a way to turn on USB debugging from twrp or the terminal in twrp? Or is there an odin flashable rooted 4.4 rom available for the g900f that anyone is aware of. My google searches have come up with no answers to these. 4.4 roms in general for this device are few and far between. Ive told him he may have no choice but to go and get a sd card, as this would make life much easier, but it still bothers me that adb cant see the device at all, yet odin can.
Thanks for help in advance.
Related
I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?
Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?
untamed1 said:
I have a G2 from Verizon (VS980).
It was running KitKat 4.4.2 stock rooted.
I run a Nandroid backup using TWRP.
I flashed the Resurrection Remix ROM.
On restart I entered a boot loop.
Turned off, rebooted into TWRP recovery, did a complete swipe (system, cache, dalvik and data).
Tried restoring from Nandroid backup and could not find any backup files (perhaps I don't know where to look but all folders appear empty).
Tried rebooting into download mode and got stuck at installing some drivers (could take 10 minutes) with nothing happening.
Screen says Rooted and I am guessing that could be the issue. I don't know how to proceed.
Can someone help please?
Click to expand...
Click to collapse
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.
RETRObruzzin said:
I ran in to that problem when trying to go from a G3 rom to Lollipop. My solution was this:
1. Boot in to TWRP
2. Plug phone in to computer (pc should recognize it; sometimes it wouldn't and I had to mount then unmount /system partition from TWRP
3. Drag and drop a Kit Kat based rom (and GAAPS if need be) from your computer on to the root of your device
4. Flash from there
Let me know if you have any issues with that. I did manage to lose everything saved on my device which led me to a valuable lesson learned, that being: once you back up the device in TWRP, be sure to transfer that backup to your PC in case you mistakenly wipe the device clean later.
Click to expand...
Click to collapse
Retobuzzing, thank you for the quick response. Thanks also for your last recommendation, gotta do that too next time.
I have actually found my solution reading in a post that I should try entering download mode by pressing both volume keys together while you connect the micro usb connector. That worked even though the screen gives you no feedback except for the led turning red (kind of scary at first :fingers-crossed.
After doing that I was able to follow the directions in the article titled: "How to unbrick LG G2 with stock firmware" at the Androidcure.com site.
The phone was restored to the original stock conditions and later I was able to update it to software version 26A.
Note to Forum Moderators: You can close this tread if desired. Thanks.
Yes I am!
Snuzzo said:
Download another 4.4.2 based ROM. I'm assuming you are attempting to flash a lollipop 5.0.2 ROM. Is that the case?
Click to expand...
Click to collapse
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?
untamed1 said:
Your assumption is right on the money.:good:
Do you have a suggestion on a better lollipop ROM for the G2?
Any idea on could have caused the boot loop after flashing Resurrection remix?
Click to expand...
Click to collapse
Only 1 assumption. Didnt downdate back to 12b bootloader/modem.
So, yesterday i tried to install Euphoria OS on my phone, but in all of a sudden, the /cache partition corrupted, i was dumb enough and deleted it via TWRP, making my phone fall into the QPST status.
After fixing it, i proceeded and reflashed KitKat, but the phone only shows 8GB instead of 16GB, so i tried to fix this by flashing TWRP, everything went well, until i upgraded to Lollipop again.
It always bootloops no matter what i do, i really need my phone with my 16GB of storage back, it isn't a Hardware failure since the QPST diagnosis didn't say anything about mobo failures.
I can mount all the partitions, i can wipe it all, i can boot into bootloader and recovery, i can do basically everything but booting the system.
Any light on this? it either happens after i flash TWRP or after i try to root it.
Im running Android 5.1.1 stock.
List of tutorials i have tried (In order): http://forum.xda-developers.com/nexus-4/general/wip-unbricking-nexus-4-using-qpst-t2208289
http://forum.xda-developers.com/nex...unbrick-n4-t2347060/post43164157#post43164157
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Don't you dare tell me to reflash the ROM again, this is the first thing i have done, i did this 20 times already and it never worked. It isn't a ROM problem. It is a partition problem somewhere.
Fixed, had to use LGNPST to reflash JB 4.4.2, then upgraded to a ZIP version of the Lollipop ROM, then flashed the stock one.
I'm having the same problem with my Nexus 4. I read also about LGNPST, but I remember something about flashing the Optimus G cache partition I believe, then manipulating one of the prop files afterwards in order to get your 16gigs back. The problem is that all of the files needed to do this flash are attached to a stupid downloader site and so its full of pop up windows and adware from what I've seen. I can't get mine to boot into system, or bootloader, or recovery, etc. The device will not finish looping for debugging to be enabled, and even trying to boot into download mode is not happening. I've tried all I know to do, especially considering fastboot and adb both utilizeusb debugging. I really am baffled. Any root kits I've tried also don't work so far. Help please.
I have a SGH-I337M S4 via Koodo in Canada. I've spent 15 hours on this so far and am now really confused.
History: I installed Cyanogenmod a couple years ago. Recently wanted to change from that so I decided to install stock first via SamMobile for SGH-I337M Koodo. I downloaded 5.0.1 from here sammobile
I had it installed fine and then went to root, so I used Odin, enabled USB debugging - and installed CF Auto Root. That worked.
Then I went to install Clockwork Recovery mod and it errored out and I don't recall exactly what happened but now I'm stuck with the yellow exclamation point saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
In the TOP LEFT of screen is says:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL: LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled
1) I tried to do emergency recovery through KIES but my phone isn't being recognized in Kies.
2) I uninstalled Samsung USB drivers and tried just KIES alone
3) I tried just USB drivers with flashing stock firmware via Odin in download mode - it errors out and says no partition found or says FAIL in red.
I've read a lot but i'm not that technical when it comes to this.. not sure what to do at this point. I can get into download mode but I can't get anything to work.
Is the phone ruined??
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
audit13 said:
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
Click to expand...
Click to collapse
Hi Audit,
Thank you for the reply. I was able to try the original USB cable now and loaded the stock Koodo firmware through Odin and it worked flawlessly. Once loaded and rebooted, it went right to the homescreen and skipped past all the normal setup stages, so I assume something on the phone was there already but just corrupted on a bad upgrade.
Never again using an older USB cable.
Whew, that was a learning lesson. Now I'd like to:
1) re-root again
2) Install custom recovery (clockwork?)
3) Install the marshmallow OS via Broken I believe.
I will keep the thread posted for others who need help and for my own reference.
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
audit13 said:
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
Click to expand...
Click to collapse
I did not know that. I thought I required root first and then had to install a custom ROM. Interesting.
Ok, so the plan then is to find twrp for my phone model and install that first... I'll search and try to do that now.
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
audit13 said:
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
Click to expand...
Click to collapse
Done. I used the latest one for the tar and I have v2.8.4.0 right now. I held volume up and power and it went to Teamwin with a bunch of options. Install/wipe/backup/restore/mount/settings/advacned/reboot
On the TWRP website it says: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
1) I'm not sure what it means by typing that. I'd like to keep TWRP as I install my custom rom. I have the custom rom on an external SD card along with GApps. Should I insert the sd card and then boot to recovery, wipe all data and install from zip on sd card? Is that correct?
2) How do I keep TWRP from not getting overwritten?
Thanks so much for the help. Really appreciate it after a weekend of terror.
I backed up the EFS portion and it wrote it to the internal storage of the phone I believe... data/TWRP something. I did not have my external card in when I did that. Is that the correct way and how would I access that backup if I needed to?
Sorry for the questions. Trying to learn without running in circles.
After I backed up the EFS it also asked me to install SuperSU and I did that - then it rebooted automatically.
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
audit13 said:
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
Click to expand...
Click to collapse
I'm not sure if I can post links due to the new account, but the latest files for me are found on dl.twrp.me/jfltecan/ and the only tar image is twrp-2.8.4.0-jfltecan.tar
I will have to go over your other comments on my own to see the functionality. As of now, this is what I have:
1) Stock firmware
2) TWRP installed
3) TWRP asked if I wanted to root (I said yes, figuring that's what you meant)
4) TWRP installed SuperSu and rebooted
5) I downloaded Root Checker and it verified root.
I did just test it by powering off phone and then booting into recovery. Teamwin came up - so I assume that it's all working correctly and the stock ROM did not overwrite anything?
Questions:
1) Now I can boot into recovery mode and install the custom ROM via a zip file on sdcard?
2) Do I install GApps via recovery mode after I install a custom ROM?
3) Should I wipe/format before installing and if so, which one - "Advanced" or "Format" buttons?
I did a factory reset via TWRP then installed the custom ROM. Seems to be working quite well. Maybe I will try it a couple times in order to get the hang of it.
In order to determine that TWRP is the default recovery - it should load when I go into recovery mode correct?
If the phone boots to twrp once, it should not revert to stock recovery in the future.
Is there a stable ROM for a S4 i337m that is newer? I'm having some trouble finding a solid list that is known to work. I don't want to install a wrong version and mess up. I did try the "broken" ROM but 50% of time when someone phones me, they can't hear me speaking so I'm going to have to go back to stock firmware for now.
You could try ROMs made for the 9505 and i337.
Hello,
I am having some problems since today i flashed the su binaries over my completely new lineageos install. (a14.4, fully wiped before).
it was stuck during boot at the android logo(let it boot for half an hour, multiple times, no progress). so naturally i wanted to boot to recovery, though it would not boot into recovery with any imaginable key combo.
so i went into bootloader mode (which, in my case, is jsut download mode, no fastboot whatsoever, and yes, i checked fastboot devices, (also adb), nothing to be found there)
next, knowing i had no other choide at that moment, i flashed a stock rom, via download mode. worked so far.
stock rom was running (ics), bootloader was still download mode only, and recovery was now stock android rec.
my next step was flashing a custom rom, since this was the most important thing to get to working then.
via adb sideload i fashed lineageos, once again. was working fine, so recovery next. but nothing worked.
included with lineageos is root access, so i enabled all the stuff, incl. adb, on my phone. but adb sideload always spit out errors (code 7 or 255) on rec install (twrp 2.8.something touch.zip) [some error about /tmp/update.zip] trying cwm resulted in the same thing, like did flashing gapps.
pushing the files to the internal memory (/sdcard) did not help, since 'flash from sdcard' resulted in an empty sdcard folder with no files to install (in recovery. in the file explorer while running the os, the files where there)
then i tried rashr (not sure exactly which app it was) to install rec. it said everything worked fine, trying to install cwm. so i rebooted
and nothing worked. the rom would not boot anymore (again, stuck at android logo) since the stock recovery only allows for adb access in form of sideload, no push whatsoever, and sideload did not let me install the os via zip, it was back to flashing a stock rom once again.
so i did that again (this time lolipop)
this is where i am now:
the rom boots perfectly, like does the kinda stock recovery, but again: no files in the sdcard path within the rec menu, though i pushed them there, and they appear there in the file manager.
i installed root, for those neat apps, that maybe one would work, but they need root and the stock rom does not know how to give those rights to apps, no option found for this whatsoever.
also, download mode is gone. (still no fastboot)
when i try to boot the bootloader, i just goes on to usual os boot (key combo and adb reboot bootloader result in the same thing)
recovery is still working, but pretty useless still. when i try to sideload a file, it quits with failed verification of the file. which is no surprise to me, since it shows the message halfway through the send process (observed from the adb terminal on my pc, never gets even close to 100% before the message appears on the phone which also cuts the connection therefore the file send process.)
i have absolutely no idea what the hell will get this working again. i dont really care about the download mode, but what i really need is a custom recovery to finally work, so i can install all of my stuff again.
does anyone have any idea on what i could try next?
hopefully yours,
azyrael
SOLVED
so i noticed for root apps i need to install supersu (or something like this) to give root access to apps if there is no native way within the rom to do this stuff.
install supersu and found out i somehow had no root access at all. tried ioroot etc, did not work
so i installed a stock jb android rom, rooted the device via ioroot, install recovery via autorec, and it finally worked!
this took me only two days.
thx xda for providing all of the tools i needed for this <3
kinda unsolved
so, it got recovery to work. installation of lineageos also worked perfectly., though this bricks my device.
no matter what i wipe, installing a custom rom will stop it from booting. this could only be fixed by installing a stock rom again, which also reverses root and install a stock recovery. since i only need root and the rec for installing a custom rom, which does not work anymore, i wont bother with this anymore. i have abosutely no idea whatsoever, and tried everything even barely coming to my mind.
still open for suggestions, but the stock rom will have to suffice for now.
Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
eldeecko said:
Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
Click to expand...
Click to collapse
I was lucky one with August firmware. Problem solved, can be closed.