Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:
UPDATE :
Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
Anyone??
Related
Hello everyone,
This is my first post on xda and I've read some of the posts etc and I thought it's time to begin to start questions related to my problem. This will be kinda long post and I'll try to give as much as information from my device specs to what I did to my device up to this point so you guys can understand my problem maybe help me or simply you can say its bricked and I can done with it. And last, I'm kind of newbie with android environment.
As you can see from the title my device is 'Reeder a8i Quad tablet' which is currently in Turkey. Device specs are following:
Uses Intel atom bay trail, Android 4.4.4, TF card (similar to sd)
bootloader title says 'droidboot' and for the recovery there is no install from sdcard or something like that.
There is almost little knowledge with the device and official site is not helping ( I guess they don't care at all )
Some Turkish forums actually got some idea about rooting and flashing stock rom. ( Later in 2015-2016 they released 5.1 for the device and that's all ). Forums actually use old how-to's from reeder support with images how the process done for upgrading android system.
First I try to find some ways to root the device but unfortunately my lack of knowledge and almost no guide for root get me stuck in the first time. I had 4.4.4 android and I was looking at ways to root it. My friend used King Root to root an old samsung phone but later he deleted it and suggested me to use it since I couldn't find any other way. I give it a try and use king root and followed instructions and voila! I had root access on my tablet and quickly installed greenify, root browser, uninstall ( for stock applications and especially google apps ) and later I installed superSU with terminal. Now for the fun part. I did give all these apps root access and deleted stock apps including google apps and 1-2 apps that king root installed while rooting. After deleting google apps I screwed up and keep getting crash reports for some of the services. I didn't know what I did to that point for google so I simply wipe data and wishing reverting all the things. After boot, there is king root app, google services again crushing and tablet looked unstable. I installed root checker which gives me that no 'root access' so I opened king root app and it couldn't root with error messages. I installed gapps for 4.4.4 and google services returned normal. Connected my tablet to pc and use king root again to root. Again device is rooted. Installed same apps, deleted king root apps and entire google apps, services, etc from tablet. Now I got no problems with google, successful root and happy face.
After closing my tablet and opened some day I saw that I don't have root access and king root app again no help at all. Again connected pc, app seems unstable with says my device is rooted and sometimes says not rooted. There was something wrong for sure and again wipe data etc. But now I found reeder tablet stock rom from the internet ( website is closed just today! ) including tons of tools and drivers and roms for other devices including mine. It's not actually site just index so you just go in a folder click and download etc. Installed my drivers, I already had android studio so adb fastboot etc but I did download some quick tools for just for this. I remember my device couldn't open so I just did some things from adb and fastboot and after 1 day work it's opened with 4.4.4. But google kept crashing so I understand that I didn't flash a stock rom entirely. Again root with all the apps and I simply use the device for some apps.
Up to this point I want to call part 1 because after this may be 3-4 months passed and about 2 days ago I started to play with tablet again. Now I installed some network tools to play with. Trying to use some MITM or cookie stealing etc. I used tons of apps including kali linux's nethunter tools which I get from their zip file. Obviously some of them not work and some other are. Still my root is unstable one time it says rooted one time says not. So It kept bothered me but now I don't want to use king root tried to search other ways to replace it with supersu. There is a guide here to use a shell script but it didn't worked so I found an app to replace it. It says done but king root app kept crashing and this point is where I called point of no return ( at least for me ) I downloaded king root app to my pc and tried to root it. It says rooted and now reboot etc. After that nothing changed and still the same. Btw, before tried root I used fastboot to try to open bootloader with boot.img from stock rom but I don't know what it actually does so. Again app is crashing there is no root access so I wanted to install stock rom. There is a guideline for 4.4.4-5.1 for my tablet and there is a tool named 'Manufacturing flash tool v6+' from intel. But I need an OTG for that since I don't have one. Flashing tool uses an xml file. Since I have that from stock rom's folder. I thought give it a try but nothing happened and tool supposed to detect my device but it didn't. At that time I could use fastboot and adb without a problem so I assumed tool got some sort of bug and installed again but result were same. I tried to wipe data and reboot but I got recovery screen with '3E' error. I tried to get into recovery screen to use adb and do something. I desperately used fastboot flash boot boot.img, fastboot flash recovery recovery.img and system system.img from 4.4.4 but not only it failed with the error 'end of footer from /tmp/update.zip not 0xFFFF file exists' but somehow corrupt the device rom and now I was stuck with reeder logo with infinite loop. After that I wanted to give that manufacturing flash tool a try again and same result. I did buy an otg cable for tablet and for my phone which screen destroyed couldn't unlock since touch screen almost not working and usb debug is closed to open that phone as well. There are files from reeder help desk to upgrade it to 5.1. I copied those files to tf card and used otg cable on my keyboard. Guide says press ESC key until bot manager is coming up. There is a screen with bot manager including bios settings. Guideline and tools says it's for upgrading bios so I did those steps and now again recovery mode. Opened manufacturing flash tool with my 5.1 xml but no result so I found something under menu to 'Print flash file cmds' used it and it simply bunch of fastboot commands. I opened fastboot and executed all those commands one by one for myself. Eventually some of them are failed with 'fastboot oem unlock' etc. Since it's changed into flashing unlock which both commands give error from tablet 'unknown command' I followed steps. ( At the end of the post I will give the xml commands from manufacturing flash tool ) After that at I used 'fastboot flash esp_update' provided with esp.zip file successfully. After that 'fastboot flash fastboot droid.img' failed. Following with 'fastboot flash boot boot.img' 'fastboot flash recovery recovery.img' 'fastboot -S 200M flash system system.img' all those commands failed and couldn't install the 5.1 manually.
At this point if I wanted to open my device it simply tries to update bios with the same file ( if tf card inserted ) other than that still at recovery with 3E and adb sideload not working with the error I got above 'end of footer from /tmp/update.zip not 0xFFFF file exists'
I know that my post is long and tried to give as much as information as I can. I just hope device is not completely bricked and there is a way to solve this. Any questions about information about device etc you can shoot I try my best to answer. Thank you for people who are reading this to spare their time.
Manufacturing flash tool xml file commands and success or fail after I executed them in DNX mode ( volume up + down + power at the same time )
fastboot flash osloader "I861B1C_1601001_64_20160115\efilinux-userdebug.efi" - success
fastboot boot "I861B1C_1601001_64_20160115\droidboot.img" - success
sleep - failed
fastboot oem enable_oem_unlock - failed
fastboot oem unlock - failed
fastboot oem wipe ESP - success
fastboot oem wipe reserved - success
fastboot oem start_partitioning - can't remember
fastboot flash gpt "I861B1C_1601001_64_20160115\partition.tbl" - success
fastboot oem enable_oem_unlock - failed
fastboot erase system - success
fastboot format cache - success
fastboot format config - success
fastboot format logs - success
fastboot format factory - can't remember
fastboot oem stop_partitioning - failed
fastboot flash ESP "I861B1C_1601001_64_20160115\esp.img" - success ( After this point I assume device is rebooted and opened a screen which is kinda new with big green 'NORMAL BOOT' text )
fastboot erase keystore - success
fastboot oem verified - success
fastboot format data - success
fastboot flash esp_update "I861B1C_1601001_64_20160115\esp.zip" - success
fastboot flash fastboot "I861B1C_1601001_64_20160115\droidboot.img" - failed
fastboot flash boot "I861B1C_1601001_64_20160115\boot.img" - failed
fastboot flash recovery "I861B1C_1601001_64_20160115\recovery.img" - failed
fastboot -S 200M flash system "861B1C_1601001_64_20160115\system.img" - failed
fastboot continue - failed ( it says success but reboot never happened )
Before I begin, I'd like to thank everyone in this forum, you have been a great help with customizing and troubleshooting phones. I'm also going to apologize for the long wall of text. I wanted to be as detailed as I can while I tried doing this on my own. Any help is appreciated!
The problem and what I want to do:
- My old P780 starts throwing out errors about 2 minutes after booting up the phone, about various apps (Notification Center, Process System, google play services, etc.) has stopped or is not responding. Errors pop up at a rate of about 1-2 messages per second, making the phone unusable. Since this starts 2 minutes after boot, I am still able to navigate and change settings for a while.
- I want to restore the phone to a working state with stock ROM or if not asking too much, maybe better TWRP + Custom ROM + SuperSU.
Phone details:
Lenovo P780 8GB, ROW
OS: Android 4.4.2
Build: P780_ROW_8G_S228_150112
BB Chip : MT6589
MS Board. : P780_ROW
IMEI1 : [Hidden for safety and privacy reasons]
IMEI2 : [Hidden for safety and privacy reasons]
Modem Ver. : P780. V24, 2015/0
Bar code : [Hidden for safety and privacy reasons]
Build Time: : Mon Jan 12 16:49
Kernel Ver. : 3.4.67 ([email protected])
MP PREEMPT Mon Jan 12 16:2
Android Ver. : 4.4.2
SW Ver. : ALPS.KK1.MP5.V1
Custom Build Verno. : P780_ROW_
Observations:
- Takes about 5-15 minutes to boot.
- Restoring to factory via settings does not work, it goes thru the motions, but on reboot its back to the home screen, my 4-digit PIN to unlock the device is still there along with the wallpaper, messages from 2015, etc. Only the internal clock appears to have reset to 1/1/2010.
- Setting changes do not appear to survive reboot, including enabling developer mode. They get put back to what ever the setting was.
- This makes enabling developer mode a pain, but is still possible.
- After enabling developer mode and USB Debugging, I can see the phone storage on windows, currently 2.68GB of 5.73GB free. Unable to create, paste, modify or delete files.
- I do not remember if this phone was made in 2014. Some info on phone suggest it is 2015. Not sure if this helps.
What I've tried:
- Successfully installed Windows_10_MTK_VCOM_USB_Preloader_Drivers my windows 10 x64 machine, and ADB
- I can get to developer settings and enable USB debugging, which lets me see the phone via 'adb devices' on an administrative command line on PC, also confirming that the phone drivers are correctly installed.
Code:
C:\Users\arnol\Desktop\P780RestorationSetup>adb devices
List of devices attached
OZ8PQKGMIRY5DMZS device
- I can browse from the command line using 'adb shell' but only as $ and not #. both su and sudo fail to run.
Code:
C:\Users\arnol\Desktop\P780RestorationSetup>adb shell
[email protected]_ROW:/ $ su
[-] Connection to ui timed out
[email protected]_ROW:/ $ sudo
/system/bin/sh: sudo: not found
127|[email protected]_ROW:/ $
- I tried rooting from command line but it fails
Code:
C:\Users\arnol\Desktop\P780RestorationSetup>adb root
adbd cannot run as root in production builds
- Run 'adb reboot-bootloader' reboots the phone into normal mode instead of fastboot.
- Run 'adb reboot recovery' reboots the phone into stock recovery.
- power on + volume up it says "Have been in factory mode..." and some chinese text and some memory test options and phone info. I've added the info to phone details above.
- Running adb while here shows unauthorized.
Code:
C:\Users\arnol\Desktop\P780RestorationSetup>adb devices
List of devices attached
? unauthorized
- Navigating to clear emmc will make it say formating /data, then reboots almost immediately afterwards. No noticable effect.
- power on + volume down it says "Have been in meta mode..." and some chinese text, and nothing else happens. It still shows as unauthorized in adb, and is not found in fastboot.
- Followed the steps in https://forum.xda-developers.com/lenovo-p780/development/lenovo-p780-guide-t2658144 to flash STOCK ROM ROW119 8GB. SP Flash Tool seems to be working but after 15 minutes and 90% done, it gives this error: BROM ERROR: S_CHKSUM_ERROR(1041). Some more research I found said this could be a fatal error, whle others say they got around it by deleting the Checksum.ini file. I deleted the checksum file and re-ran SP Flash Tool. It got to 100% but still give error 1041. Note: I used SP Flash Tool V3.1304.0.sn119 for this step.
- Used SP Flash Tool V5.13.52.200 to format EMMC and run memory test. It now gives BROM ERROR: S_DA_MT_DEDICATED_PATTERN_ERROR (3094). Attempt to flash STOCK ROM ROW119 8GB, it also gives error (1041).
- I tried the steps listed here https://forum.xda-developers.com/lenovo-p780/help/rooting-tutorial-kitkat-t2835605 to install TWRP. It gave "pmt changed for the rom it must be downloaded". Tried editing the scatter file as suggested, but same error. Also tried firmware upgrade button, still no go.
- I am out of ideas at this point. If there's anything I might have missed please let me know. I appreciate the help!
Background Info:
- I'm an IT guy who's very familiar with Windows, and starting to learn how to use Linux.
- Phone was rooted before with KingRoot.
- I remember trying to uninstall a system app, which may be partly or directly the cause of this
- I do not remember what system app it was (did it way back 2015).
- This was my first attempt to mess around with my phone, I was pretty noobish at the time.
- I have since been more careful and successfully flashed custom roms on 2 other phones, an Android One Sprout8 and a Xiaomi Mi5, both now happily running LineageOS 14.1.
- We can skip any steps involving backups. Nothing is needed from the phone (other than to get it working!).
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
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else
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!!!