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.
Related
Hey guys, I have a weird issue. I recently (re)aquired a MyTouch 3G Slide after selling my old one. The other I rooted back when rooting was still super-hard. I bought it the day it came out, and had CyanogenMod7 running beautifully and everything.
The "new" mytouch 3g slide I aquired was factory reset (s-on) on 2.1. I tried to update to 2.2, but HTCs website doesnt seem to have the files anymore. So I rooted it using UniversalAndroot. I tried to run RomManager to flash recovery, but as you know, it no longer supports 2.1 and below, so that sucked.
I found an old version on here, flashed it as update.zip, and everything was good.
Now that I'm rooted I flash CyanogenMod7 and GAPPS. Everything installs fine, except GAPPS didn't. So I reboot into recovery, and I see it's stock again. Hmmm, strange. I install update.zip again, recovery comes back, I flash GAPPS again, this time only the market installs. Fine with me.
I reboot into recovery to make a back-up after installing everything. Strange...stock recovery AGAIN. Install update.zip, everything is fine, create my backup, reboot and I update CWM through RomManager, everything's good. Reboot into recovery. STOCK RECOVERY AGAIN.
It seems the only way to get into CWM is to flash update.zip (luckily only takes a few seconds), but is there anyway to make it stick? I had to force update SuperUser as well, and a few other things.
So my question is, if I downgrade to stock 2.2 from HTC, root, then reupgrade to Cyanogenmod 7, would all my issues be fixed?
Update.zip will NOT change the recovery; it will only allow you to use the custom recovery for that certain time. You must obtain the recovery image(recovery.img) and then boot into fastboot(press vol-down+power, then press power) and, on your computer, move the recovery.img to the same directory as fastboot and then, still on your computer, type fastboot flash recovery recovery.img, and there you go
Hi awesome XDA dudes
I've searched the forums, and even posted in the basic QA section to no avail. I may have just missed it somewhere, but here is the issue.
Tablet will work fine in Lightspeed 4.8 ROM. No issue there. But, when I try to get into the recovery (power and volume down) I get "booting recovery kernel image," forever.
I recently changed from the Clockwork to TWRP recovery and that is when the recovery function would no longer load.
How can I get back to Clockwork or smililar so that I can put a different ROM on my tab?
Thanks in advance!
Tom
Fixed this problem, only to find another.
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
SOLVED !!
tfbielawski said:
So, since my tablet would still function normally (aside from recovery) I downloaded the Acer Recovery Installer App. And this did what everything else failed to do. It installed Clockwork Mod and I was actually able to get into the recovery. Whew!
So I went to install Flex shockwave ROM but the install froze at the Aroma 2.56 stage...forever. Tried again unsuccessfully and gave up. I did properly wipe and format beforehand. I then tried installing CM10 Rom, same exact problem.
So, I used Acer Recovery installer and loaded the TWRP recovery. Here is where things get interesting. I booted into recovery, wiped data and caches, and tried to install the aforementioned ROMs. Each time, Aroma installer worked fine and I was presented with all the install options, all the bells and whistles. After completing my selections, I was prompted to reboot.....
And each time the tablet hangs on the Acer spalsh screen.
So now my problem is reversed. I have access to recovery, but no ROM. :crying:
Click to expand...
Click to collapse
Ok, so I had a working ROM but my recovery was fried. So, using Acer Recovery Installer I was able to get a working recovery going.
Then the next problem was that I could not get CM10 to install. When I realized I needed to flash the bootloader (and yes fellow noobs this is different than the recovery) I was unsuccessful.
I tried the automated route using the Blackthund3r app, but the process would just hang at Entering bootloader.
I tried the manual NVFlash route provided by Dibbs and it would get past this point and then hang.
So Dibbs (thanks dude) helped me out via email and suggested I download babsector.rar
After I extracted the rar file, I saw the A501 A.bat file and flashed it. This provided me with hope as it flashed the tablet and the screen atcually read "PASS." But, I wasn't done yet as I still could not install CM10. So, back to APX mode and back into the babsector rar folder. I flashed the Tab with A501 B.bat and followed that immediately with flashing the v8.bat file. In the V8.bet file I chose the Thor 1.7.3 recovery (as suggested by Dibbs and others) and WOOHOOO.....PASS on the tablet again.
Feeling ever more confident, I booted into recovery and flashed the CM10 Rom....SUCCESS!!!!!!!!!!!!!!!
If you are having trouble....don't give up. Thanks again for the help to Dibbs and OKAstro!!
I've never had problems like this and I've been flashing custom roms and recovery since HTC G1 days. Maybe you chaps can enlighten me a bit.
I can boot into all partitions of my device just fine, regular system, recovery, bootloader all okay. My daily rom (Vanir), however, has been getting a little bogged down lately so I'm trying to do an update.
I transferred my rom and gapps files to the sdcard and boot into twrp 2.6.3.1 to update, but lo and behold, the files are now missing. All my other files are there, just not the rom or the gapps. Not too worried yet, I'll just use the sideload method instead.
Start up sideload and watch it transfer over the new rom (MIUI at this point, and I factory reset before hand). From the cmd line I can see it going over just fine and the device seems to be accepting it as well. It gets to 100% and starts a quick error free install on the device, but when I reboot, nothing has been changed and I'm back in Vanir. Okay...I'll update the recovery and see if a new one works.
So I boot into the fastboot to update the recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.7.0.0-grouper.img
Looks good, no error messages, cmd line shows it has been written, so I reboot into my new recovery, only its not new, its still twrp 2.6.3.1 and everything still doesn't work.
Long story long, I also tried installing CWM instead of TWRP -- didn't work, using adb push to move the files and that didn't work, and every time I seem to just lose the zip files after a reboot or update attempt. In fact, when I boot back into Vanir, all my regular files are there, but even though I haven't removed them none of the rom or gapps zips are anywhere. I am sure they have successfully transferred multiple times, but they never seem to make it through a boot sequence.
At this point I'm stuck, and wondering about my boot partitions being messed up. Any help you can provide is much appreciated.
Update, with new information.
I tried to do a complete wipe a la the guide that's stickied in this forum, and it's led me to a bit of new information. It seems that my bootloader is repeatedly failing to update from version 3.23 every time giving either the "InvalidState" error, or when I use older bootloaders that are supposed to work like the JWR66V bootloader mention in this post, it doesn't say "InvalidState" but still fails just the same with a blank where it would say "InvalidState".
I've also realized that none of my changes to my tablet are persisting through a boot sequence. If I download a new app, it is gone upon restarting. In fact, every time I power it up, it downloads the same 3 app updates to the device. Perhaps that can help narrow the problem down a little bit? Sounds like a data wipe is happening every time, but only for changes since I began to try to update the tablet a few days ago, all my files from before the update attempt are never removed or altered at all.
Lastly, according to Rom Manager, I have both TWRP and ClockworkMod as recovery. Actually, that makes me think it might be a boot.img issue. If anyone has any ideas at all, I am open to try any of them at this point. Thanks for reading and for your suggestions in advance!
CM Installation Problems
I posted this last night on the CM forums and have had one responder but thought this might reach a wider audience. I'm copying and pasting the OP and I'll try to include as much info as possible.
Hi,
I'm fairly new to flashing etc. New as in this was the first time I tried it. I'm fairly tech savvy, I just haven't flashed a custom rom before.
I followed all the instructions on the CM wiki for the S5 (AU).
Long story short, every step in those instructions worked perfectly once I accounted for my own errors or misunderstandings. Flashed the TWRP recovery just fine. There were problems with ADB not working when the phone was in recovery mode (discovered it's something to do with win 8 and above) so I just rebooted into stock rom (where ADB worked) and used adb push to copy the files to sdcard. Everything went swimmingly until the actual CM installation. I followed the instructions and did the factory reset, went to install and the installation took something like 10 mins before I started to wonder how long it was meant to take. Little bit of googling got me more worried, after about 20 I pulled the battery, back into recovery and went into Wipe again. Cleared Dalvik, cache, system all manually and then did the factory reset option on top of that just to be thorough. Installation is still taking forever. It's currently been around 20 minutes. Some posts I've read say rooting is required but that installation article specifically says rooting is neither required nor recommended. I've no idea where to turn now. I can't use ADB to copy a stock firmware back on as it doesn't work in recovery mode, nor can I try the klte or kltedev versions (don't think they're meant for this model anyway). It's just stuck on "flashing file 1 of 1" - the last thing in the log is "Patching system image unconditionally..." I'm running windows 10, not that that should make any difference.
Any help would be hugely appreciated.
Update: After about 40 mins I pulled battery again and thought I'd try booting normally and seeing what it does. Just sits at "Samsung Galaxy S5" splash screen.
TL;DR/Extra info:
Galaxy S5 G900I (AU) Vodafone
Was running Lollipop 5.0 as per Vodafone OTA update
Using instructions on the CM wiki page for the GS5 (AU) I flashed TWRP using Heimdall with no errors. ADB would not work in download/recovery (couldn't see device) so booted phone into stock ROM and used ADB push to copy the CM file to sdcard root. Note: I don't have an sd card, it's internal storage. Rebooted into recovery, tried to flash CM, it sat on installation screen for about 20 mins. Tried 3 times, leaving it for 40 mins, still nothing. Stock OS has been wiped so I can't get back into that, and because ADB doesn't work I can't reflash recovery from scratch, can't copy a new download of CM on, can't copy the stock ROM to flash. ADB Sideload just tries to run and fails. Currently trying to get ADB working. Running Win 10, device stopped showing up in device manager or Zadig at this point. Restarted PC, ran Zadig again, it saw device, reinstalled driver, now shows up in device manager under USB Devices as MSM8960 (so not under Portable Devices as it once did). Note: the safely remove icon in system tray showed "Galaxy S5 (Phone name)" before I ran Zadig again, now it shows MSM8960.
Help
Reflashed TWRP with Heimdall. Didn't change a thing.
After the biggest headache of my life I got ADB working in TWRP. Had to modify the .inf of the google usb driver that the SDK installs and add the hardware ID of the device in recovery mode. Apparently the ID changes when in recovery so the driver doesn't recognise it anymore. Success!
I downloaded the nightly from 30/09, renamed it update.zip so the filename was simpler, pushed it with ADB to sdcard and am now trying to install it. So far same issue, but at least I can push files to the phone now. It definitely seems to be an issue with the install process.
Update: Still same issue. New zip, new build, reflashed recovery and still hangs on install. Would trying ClockWorkMod be worth it rather than TWRP?
When sideloading the ROM and viewing command prompt on the PC everything works fine until it hits 90% and then it stops suddenly and stays there. During the TWRP factory reset it also says unable to mount system several times if that's any help
I've now tried flashing Philz Touch and given that a go. Factory reset/wiping seemed to run with less of a hitch but still exactly the same deal, gets to "patching system unconditionally" when installing CM and just sits there, progress bar doesn't even fill up a bit. I'm stumped.
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.