Dear all,
I am pretty sure "I am doing it wrong", but first let me explain what I am about to do:
My SGS2 (i9100)is basically only a watch since 3 years and lying around. So no problem if it's wasted...
I am about to get a Vacuum cleaner roboter and I want to use the App on my old SGS2 in a Guest network at home.
Therefore I try to update the OS on my phone in order to start the APP (which is not possible yet).
Problem:
My SGS2 is rooted and running CM 10.2-20131214 (It couldn't be updated before, always giving me errors so I left it with CM 10).
Now I would like to try to install TWRP in order to install a LineageOS on it (preferably the Version 16).
USB Debugging is activated and Root access is given to Apps and ADB. OEM Bootloader unlock option is not given (I guess because my phone is already rooted?).
- ADB is installed.
- I installed the most up to date Samsung USB driver and the phone shows up in the device manager.
- Odin 3.12.4_4 installed (also tried with 3.09)
I can start the bootloader via CMD and when I want to "fastboot flash recovery twrp.img" it stays in the "Waiting for device" line...
When trying to install TWRP with Odin it gives me a FAIL when using the only twrp.img.tar I could find on the internet so far...
Now I read something about an IsoRec compatible kernel and that I would have to repartion space on my card using "lanchon-repit-20170115-system=1.5G-data=max-sdcard=min+wipe-preload=min+wipe-i91000" (Lanchon repit) in order to install LineageOS (via TWRP I guess).
I have to admit I am a little confused on how to proceed going forward...
Can one of you give me some advice or link to a comprehensible guide on how to install that OS on the SGS2?
I can imagine that the problem with installing TWRP is my very outdated kernel version 3.0.64-CM-g9d16c8a from December 2013...
//edit: So I tried with ODIN <3.09, no change of situation.
I recognized that via console "adb devices" does list my device when operating in CM 10, but when I send "adb reboot bootloader" and it reboots (no mather if manually or via the command) "adb devices" doesn't list the phone anymore, although it is recognized in the device manager under "Modems -> SAMSUNG Mobile USB Modem" and "USB Controller -> SAMSUNG Mobile USB CDC Composite Device" ...
Related
I have a rooted Google Nexus 10 tablet with Clockwork Mod and Android 4.4.2. The Google USB driver worked fine on my Windows 7 laptop and I was able to use adb to push files to my tablet. I foolishly let the automatic 4.4.3 OTA download and install. Now, my tablet is stuck in bootloop AND Windows has completely forgotten my Google USB driver and thus adb can't see the tablet, so I can't transfer over the 4.4.3 image or flash in Clockwork Mod via sideload. Yes, Clockwork Mod works great and I can boot into recovery mode. I've seen a thousand postings that all talk about stuff you do from Android like enabling USB debugging, etc, but this is all worthless when you can't boot Android. In retrospect, I wish I had kept a backup image on my SD card. So three questions:
1. How can I get the update image onto my tablet, either by sideload or adb push?
2. Is the factory image (4.4.3 (KTU84L) ) correct or since I'm rooted, am I supposed to use a modified one?
3. Would the manual update method be as simple as copying over the factory OTA to my SD Card ahead of time, booting into recovery mode and flashing?
Thanks in advance to anyone who can help.
Well, no response from anybody. I just saw this on another post: "Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT. "
This is very informative. I just wonder if "adb devices" ever shows anything if you're in recovery mode. I wonder also if the Windows 7 driver is supposed to work. I have a feeling this driver is based on communicating with Android itself, so of course it won't work. So maybe fastboot is the way to go? That's what I'll try next.
fastboot
This looks relevant - it has a ton of fastboot commands:
http://forum.xda-developers.com/showthread.php?t=2024259&page=3
Hello,
I am having a big issue with my Sony Xperia Z2 Tablet. I tried to install a new rom on it and I am stuck in the recovery step.
I achieved to unlock the phone, install the fastboot drivers and flash the boot of my device. I can access to the CWM-based Recovery v6.0.5.1 menu but I just can't put the new rom in my /sdcard/xx directory.
I've tried to use the "adb push cm-11-....-windy.zip /sdcard/0/" command line, but I receive the message: "error: device not found".
I then check the command "adb devices" and indeed the device is not listed even though the device is connected. I then tried to reboot the device (after wiping the data/factory reset, cache partition and dalvyk cache, but my tab is not rebooting on anything. I have nothing but the wave background. Once the device got at that stage, the "adb devices" commande shows the following message: CB51xxxxxx unauthorized. It looks like I have a driver problem or something similar, but I tried to install different drivers and nothing worked so far.
So from there, I am lost, I can't boot my system with the original rom and I can't transfer any new rom in the memory to install a new one.
I would appreciate it a lot if anyone could give me some leads on how I could transfer the new rom on my device or at least recover the original sony firmware so that I can use my tablet again.
Thank you for your answers and time
P.S. I also tried the slideloader option, but since it seems to work on the adb program, it's not working either.
Solved
¨Djyinks said:
Hello,
I am having a big issue with my Sony Xperia Z2 Tablet. I tried to install a new rom on it and I am stuck in the recovery step.
I achieved to unlock the phone, install the fastboot drivers and flash the boot of my device. I can access to the CWM-based Recovery v6.0.5.1 menu but I just can't put the new rom in my /sdcard/xx directory.
I've tried to use the "adb push cm-11-....-windy.zip /sdcard/0/" command line, but I receive the message: "error: device not found".
I then check the command "adb devices" and indeed the device is not listed even though the device is connected. I then tried to reboot the device (after wiping the data/factory reset, cache partition and dalvyk cache, but my tab is not rebooting on anything. I have nothing but the wave background. Once the device got at that stage, the "adb devices" commande shows the following message: CB51xxxxxx unauthorized. It looks like I have a driver problem or something similar, but I tried to install different drivers and nothing worked so far.
So from there, I am lost, I can't boot my system with the original rom and I can't transfer any new rom in the memory to install a new one.
I would appreciate it a lot if anyone could give me some leads on how I could transfer the new rom on my device or at least recover the original sony firmware so that I can use my tablet again.
Thank you for your answers and time
P.S. I also tried the slideloader option, but since it seems to work on the adb program, it's not working either.
Click to expand...
Click to collapse
I found a solution, I flashed my tablet with flashtool and a working ftf file. Then I could have my tablet running the original sony rom and finally I could transfer the cyanogen rom into the tab. Everything is running fine now.
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
syedzakiabidi said:
`Dear Admin,
Hi my Name is Zaki.... i am using HTC Rezound which i purchased in U.A.E
After installing whatsapp i got continious restart problem so i downloaded stock firmware of ICS version. all was good but by mistake i clear internal storage in fastboot mode. and after that i am unable to get into TWRP Recovery mode, it is showing phone with with arrow circle and after few second it converted into phone with triangle (attached screens 2 and 3) please explain me with links how to get TWRP again. and the links for TWRP versions i am not sure which is ok.
Please Reply.
Click to expand...
Click to collapse
You can't access TWRP because you over-wrote it with the factory RUU firmware image, it isn't there anymore...
Download TWRP image from TWRP official site at https://dl.twrp.me/vigor/ or Flyhalf's build at http://forum.xda-developers.com/showthread.php?t=1902381
Either one is good... then start fastboot, connect usb and flash recovery with the command:
fastboot flash recovery <path/filename of TWRP IMG file>
give it a minute or so, reboot into Hboot and start TWRP.
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
youdoofus said:
im having a similar issue but my computer always says waiting for device in command prompt. I have all the drivers installed and the phone says "usb fastboot" or "fastboot usb" (cant recall what order those 2 words are in LoL)
Click to expand...
Click to collapse
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
acejavelin said:
You probably have a driver issue then... Install HTC Sync, connect the phone, then disconnect it, remove HTC Sync and it should work. If that doesn't work, try a different USB port.
Honestly, I switched to Linux a long time ago... I don't have driver issues. If you were running Linux, even a live or USB key distro, you would access it easily.
Click to expand...
Click to collapse
fair point, and i do have ubuntu (of differing flavor dates) on 3 of my machines, so i might just do that. Thanks!! Ill also try the goofy htcsynch (which i forgot about, as im a Sammy guy now) Thanks again!!
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
N200 on OOS 12, can't seem to possibly ever enter fastboot mode. Whenever I try I get some screen with the only options as wipe device, reboot, power off and 'fastboot devices' on my computer no longer shows the phone. Also there is no longer an 'advanced reboot' option in OOS12 so I can't go that route either. Please help so I don't have to bin this thing
Looks like you're in recovery mode. Remember that you have to shut down your phone and hold both volume buttons and the power button while it's unplugged to enter fastboot mode. Alternatively, you can use the "adb reboot bootloader" command while your phone's booted up.
Also, you can't install LineageOS from OxygenOS 12 right now. You need to downgrade to the last version of OxygenOS 11 before installing a custom rom.
Hi, thank you for responding! I've dug in further and what's going on is the driver doesn't work in Windows in fastboot mode, only in ADB does the driver work so I am sort of stuck. I downloaded the OOS 11 zip but I can't figure out how to install it now, I don't have a 'System Update' area in settings that will let me apply the local zip. My update screen just says 'you are up to date' and gives no option to apply a local update. Any idea how to get to the local update setting to apply the OOS 11 zip? Thanks again!
EDIT: I've found a couple of applications that restore the 'local update' feature but now it either says verification failed (My Application2 app) or else the local update file is not shown (OPLocalUpdate_For_Android12.apk). I downloaded this file and put it in the root of the internal storage but it's not working:
NordOxygen_14.I.25_OTA_0250_all_2201171943_downgrade_347e133266814951.zip
Is this the right downgrade file? I have an N200 global. Thanks!
Edit 2: I'm now back on OOS 11! Yahoo! I used the guide here:
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Back to my original issue though, I seem to be having driver issues with fastboot mode. I've tried a few USB ports & cords to no avail, do you have any thoughts on troubleshooting a fastboot problem? The device shows normally when plugged into Windows but when I do 'adb reboot bootloader' and the handset enters fastboot mode then I lose the driver and instead the device shows up under 'Other devices' as 'Android' with a yellow exclamation point. I tried installing OnePlus_USB_Drivers_Setup.exe but that didn't do anything, do you think I should boot Windows with driver signing disabled and try again?
You can usually force the OnePlus fastboot driver to install. I don't remember the exact steps, but I think that you have to right click on "Android" in Other devices, select Update Driver, select "Browse my computer for driver software", select "Let me pick from a list of device drivers on my computer", select the Android related category, and select Android Bootloader Interface. Accept all warnings.
If that doesn't work, you could also try the universal ADB driver, as that's what LineageOS recommends.
You probably don't need to disable driver signing.
Thank you for the replies, I was able to get the driver installed and I installed lineageOS per the offficial doc. Unfortunately I seem to have bricked the phone as it's stuck in fastboot mode and won't boot into recovery anymore
What I did was from here:
Install LineageOS on dre | LineageOS Wiki
wiki.lineageos.org
a) fastboot oem unlock
b) boot into custom lineageos recovery via fastboot - fastboot flash boot lineage-19.1-20221116-recovery-dre.img
c) sideload in copy-partitions-20220613-signed.zip
d) install lineageos
Any idea how to get recovery working again?
EDIT: I think I should specify this is an UNLOCKED N200 not a T-mobile one so I think the MSM tool doesn't apply
EDIT 2: I got it booted into LineageOS but now Wifi won't turn on, oh what a night of drama!!!
EDIT 3: I fixed that now too, I'm all set! Thank you!!!