Related
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
with flashtool impossible to rollback . and impossible to flash kdz 6.0... a lot of people with this issue
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
gregor.eesmaa said:
Somehow I managed to make adb recognize the device and provide me with logcat access. I posted the contents on pastebin: pasteb in.com/64RZ3SgJ
Edit: Problem solved. Description in 1st post.
Click to expand...
Click to collapse
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
rotoko said:
Could you write clear, detailed procedure ...
well thank you
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
I have the same problem, I do not know how to go back
Click to expand...
Click to collapse
There you go. Can't do any better as I am not an expert in how Android precisely works at this level.
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
leegreggs said:
have followed what you ahd done i.e try adb reboot recovery and can net get adb to find device
will try again later as not very well learned in android
uk h815
Click to expand...
Click to collapse
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
gregor.eesmaa said:
Perhaps you should try running the command: "adb devices" to see whether it has connected until it has (just run it multiple times). Otherwise, are you experiencing same symptoms as me? Did you also overwrite the system with V10 files? I'm thinking that the time window was caused by the system attempting to read some media profiles while starting all the other processes behind.
Click to expand...
Click to collapse
No I've decided to go back to my LG g2 till either flashtool gets updated or till a tot & dll comes out
gregor.eesmaa said:
Hello!
I attempted to modify some system files (overwriting mine with LG v10 ones supplied in this thread: http://forum.xda-developers.com/g4/themes-apps/help-bringing-lg-v10s-camera-to-g4-t3223371) and my device ended up not going past the first boot screen (where the "Bootloader unlocked!" message appears).
Some facts:
- I have the H815 variant
- I have tried the drivers that come with LG Bridge and some others found on this forum.
- I have (officially) unlocked my bootloader, voiding my warranty
- The device gets stuck on the first boot screen (the one with text "Bootloader unlocked!"), led starts pulsing blue a second later.
- Logcat from boot is located at: pasteb in.com/64RZ3SgJ
- I have TWRP, but the press combination ( vol-down + power-button key, release for 1 sec, press them again) to boot into it doesn't work.
- I had Android 6.0 installed using the zip flashing method from recovery - with root.
- It does get past the first boot screen when I connect the micro-usb cable and it figures it has enough juice to turn on itself, but doesn't get past the boot animation then.
- I can access Download mode
- I tried flashing H81520A_00.kdz with LG Flash Tool 2014 (both normal and CSE mode), but it says: "Required info cannot be found. Contact the system administrator". Device doesn't react.
- I tried flashing older Europe Open H81510D.kdz with LG Flash Tool 2014, but it says: "Upgrade stopped due to an error." and wants me to try again (which didn't help). This message comes after a few seconds of attempting an upgrade to which my phone actually reacts - some text changes in download mode log box.
- (I did use LG Flash Tool 2014 in CDMA - DIAG mode)
- I tried using LG Update Recovery tool in LG Bridge. A similar error appeared making me retry the process, which doesn't work as well.
- Running any fastboot command yields in message: "< waiting for device >"
Please provide me with assistance as I've found other people with similar errors as well (even though their devices aren't bricked yet)
Edit 1: I discovered I had a short time window of ADB access after booting. I used the command "adb reboot recovery" and got into recovery mode. Will try to reflash system files.
Edit 2: Problem solved. Android booted up normally after reflashing the files. Gosh this was nerve-racking. Somebody should make a tutorial out of this.
Edit 3:
I was asked to write a more clear procedure, so here's my attempt. It is better than nothing. Again I suggest someone try to write a better explanation and verify that it works on other devices as well.
1. Have adb installed on your computer
2. Have the necessary drivers installed on your computer. I think I used these: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
3. Have your phone turned completely off.
4. Test if adb works from the console, using the following command: "adb version"; if it doesn't google for how to add adb to system environment path.
5. Connect the computer and the device using a micro-usb cable. The device should detect that it is being charged and turn itself on, thinking that it has enough battery to do so. If it doesn't, do so yourself.
6. While the device is booting, you have (at least I had) a short time period while your device listens for commands. In console type the following command: "adb reboot recovery" (try this from immediately after the device starts booting until it works, if it doesn't try again). This should reboot your into recovery mode.
7. If you do not have system flashables on your device, google how to sideload zip files. Get them here: http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-images-kdz-t3232282. Flash them (I flashed all, just in case, but system might be enough).
8. After flashing, you (if coming from any other rom) should clear data and cache as well.
9. Reboot the device and it should be working.
Click to expand...
Click to collapse
:crying::crying: i forget to enable usb debugging, now my pc can not connect to phone under downloadmode. And i can not use adb to let it reboot bootloader.
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
rav0r said:
I think my dev is bricked for good. I used twrp and was not careful and wiped system. Now I cannot get into fastboot anymore and recovery does not work. It never shows up on USB. If I enter recovery, select yes to delete, it does nothing, just reboots with LG logo..
Click to expand...
Click to collapse
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
AndHD2 said:
I'm having the same problem. I wiped the device ready to install a new Rom and TWRP crashed. No adb or fastboot and it only loads onto the LG flash screen. There must be a way to do it as it's software problem, not hardware problem. How do they get the software onto the handset when first made, that's what I need I feel.
Click to expand...
Click to collapse
Same here, only a software issue. I cannot boot to download mode, and my device is locked.
Hi,
Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled.
This tutorial works for Beta Android O bootloop too.
You will need:
ADB + drivers installed: https://forum.xda-developers.com/showthread.php?t=2588979
Nexus toolkit: DL.- http://www.wugfresh.com/nrt/
STOCK image archive, older than you have now - https://developers.google.com/android/images#bullhead
Latest OTA image archive : https://developers.google.com/android/ota#bullhead
-------------------
Extract stock image (NOT OTA)
install Nexus toolkit and restart your phone in Bootloader mode
connect phone to pc.
In nexus toolkit click on : advanced utilities > launch
look at: fastboot flash
screen: https://postimg.org/image/kkk9h92oz/
click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache.
Copy downloaded OTA ROM archive in ADB folder.
reboot in recovery
now select apply update from adb.
open ADB
flash latest OTA package via command : adb sideload <packagename>.zip
I hope, this tutorial is useful for you, if yes, please hit thanks button.
And sorry for my english.
GREAT!!! Saved my phone. Thank you very much!
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Ins1d3r said:
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
Click to expand...
Click to collapse
You not need usb debugging enabled in system.
Communication with pc is working in fastboot and recovery.
Redmi Note 3 - Tapatalk
any idea how to do it in mac?
What do you mean with: "Copy downloaded OTA ROM archive in ADB folder."
Just sideloading doesn't work.
ADB cant find my 5x...
Thank you OP for this i am need of help and it appears your solution has found me. Im on holiday atm and my nexus 5x just got the dreaded bootloop! Alll i see is the spinning colors for android logo after pin code is inputted.
Im very anxious to backup my photos of my son and family, so want to ask is this method safe? I dont want to risk losing data.. i can get into recovery mode and my phone is boot locked and not rooted, so can someone also tell me if adb backup will allow me to backup my pictures and video reliably? I will do a full backup and then try and flash the OTA.
serving: 'bullhead.zip' (~47%) * failed to read command: No error , what im doing wrong ?
ok succeed after dozen attempts , phone booted to main desktop work for like 5 mins and then frozen , looks like it went back to bootlooping ;(
Hi guys, same situation, since yesterday I could boot with a bit of effort (like waiting 15 minutes of bootloop) but now the 5x doesn't boot at all and so neither in recovery. My phone is locked and never modded so I will send in warranty when I will be back home ( 10 days). So now I would like to fix it to use it at least in this week, but how can I do if I can't boot in recovery?
I can just boot in the bootloader so use fastboot command...if I unlock the bootloader I will get the little lock in the bottom part of the screen, when I will lock it to send it to LG will it disappear?
How exactly is this toolkit's fastboot flashing supposed to work if you have a locked bootloader?
How is using this toolkit any different from running the "flash-all.bat" that's included with factory images?
This did nothing at least in my case.
I get the feeling that the flash operations are failing and the toolkit just disregards this.
Cannot enter recovery
I completed the first step in fastboot but when i try to enter recovery it goes to bootloop again....what should i do?
Nope, not working. Rebooting again and again. Issue not resolved. Please help!
Hi I need help,
what do i choose when i click 'system' tab?
[/QUOTE]
rockhardy said:
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Click to expand...
Click to collapse
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
jcfortunato said:
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
Click to expand...
Click to collapse
It's been a while since I tried it. But as far as I remember it was due to phone not being in recovery mode. I hold the power button until the phone screen went off. And while holding the power button I instantly pressed volume down button to bring back the fastboot mode and then recovery mode.
i'm sorry but i don't see my latest build (currently running on 7.1.2)
i've tried using 'any build', it said that i have to choose one of the build listed :/
thank you
-----
edit
found them!
but it says that my OTA is out ouf date
I downloaded the latest one though (August)
where did I go wrong? :/
Anyone still doing this ha? I've just run into this issue with my wife's phone, and there are things on there she needs..
The ones with issue with the big cores causing bootloops, use this guide to unlock device then proceed with following guide
https://forum.xda-developers.com/showthread.php?t=3641199
Sent from my Nexus 5X using Tapatalk
Hello, I've done all the procedure until reboot recovery, but I've didn't find the button for select apply update from adb in NRT.
Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...
oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .
Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?
TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work
in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?
Hi all! It took me a lot of time to finally being able to root this tablet. It's old, slow and practically unusable, but with some tricks it can be made much, much better. I'm going to explain what you need to do to root this tablet, and in case of brick (which happened to me many, many times) how to unbrick it. I even got to a point where I could not even boot into recovery mode, and only fastboot was working, that was scary, but I managed to get out. Every single file I will use will be bundled in a ZIP you can download, and I'll try to make sure this link stays up, because there's nothing more frustrating than wanting to make these things in the future only to find out the link is dead, along with all your hopes. Before we begin, a little disclaimer:
Code:
#You, and only you are responsible for everything that you do or happens to your tablet.
#If you screw up, I have a number of backups to help you recover, but if that's not enough don't point a finger at me.
#I will not be babysitting anybody to help restore their tablet or recover lost data.
#This process WILL wipe all of your data, do a backup before beggining.
#YOU HAVE BEEN WARNED!
1. ENABLING USB DEBUGGING
This is a very basic step, but it's needed if you want to even begin to do this. You'll need to go to "Settings -> About Phone". There, look for a line that says "Compilation Number" (or something like that) and tap it multiple times. You will see a message pop up saying "You are now a developer" (I wish it was that easy). Go back to the settings screen, you will see a new option appeared called "USB Debugging". Enable it, and make sure "Developer Options" are enabled too at the very top of the screen. Now, connect the tablet to your computer. You will see a message pop up asking for permission, tap "Always allow from this computer" and press "Allow".
That's it for this step.
2. SETTING UP ADB TOOLS AND MAKING SURE THEY WORK
Now that we have USB debugging enabled, and we have allowed our PC to access the tablet, we can begin setting up ADB. The required files are attached in the zip.
Extract the "platform-tools" folder and move it somewhere nice. Then open it, hold shift and right click in a white space and select the option "Open command window here". CMD will pop up, now type:
Code:
adb devices
It will probably say something about a server followed by a list of attached devices. If you see a serial number there, then great! ADB is working as it should. If not, make sure the tablet is connected, that USB Debugging is on, and if all else fails, try with another cable.
Now for the juicy part.
3. UNLOCKING THE BOOTLOADER
We will have to unlock the bootloader if we want to do anything here. Here's what to do. Type:
Code:
adb reboot fastboot
Wait until the tablet reboots into fastboot. Once there type:
Code:
fastboot oem unlock
fastboot oem unlock confirm
This should unlock the bootloader.
NOTE: This method of unlocking is reported to not work anymore, but I listed it anyway just in case, as it doesn't hurt to try. If this is not working for you, don't panic, it's normal, use the following code instead:
Code:
fastboot oem asus-go
fastboot oem asus-go confirm
This should work, and the bootloader should be unlocked now.
4. INSTALLING THE REQUIRED FIRMWARE
Now, your tablet may or may not have the required firmware for the procedure, but just in case we will flash one that's sure to work. If you followed along, you should be in fastboot mode right now. Type:
Code:
fastboot reboot
Your tablet should boot as normal, without any changes (unless the first bootloader unlock method worked for you, in which case it probably wiped all of your data). Now we can access ADB once again, so type:
Code:
adb reboot recovery
The tablet will reboot into recovery mode and you should see an image of wasted android with an open belly (if you don't see this it doesn't matter). You should see a list of options with blue text, you must use the volume keys to navigate this menu. If you don't see any options, press any volume key and they should appear. If instead of getting into recovery mode, the tablet just turned off, then go to the "Fixing recovery" section.
In this menu, you must select "Wipe data/factory reset". This will, obviously, wipe all of your data. Once that finishes, select the "Install update through ADB" option. Once that's done, make sure the "updated_firmware.zip" file is in the same directory as the "adb.exe" file, then type:
Code:
adb sideload updated_firmware.zip
This will install the firmware, it will take about 20 mins. Once finished, reboot the device. You may think it got bricked at this point, fear not, the first boot really takes this long (about 10 mins).
Once everything is done, the device should boot up and everything should be exactly as it was when you took it out of the box, meaning, it doesn't even remember your wifi password. Do a quick (but proper) set up and enable USB Debugging again, make sure to allow the PC again (and check the "always allow" box). Also, scroll down a bit more in the developer options section and look for one that says "Verify apps installed through USB" or something of that kind. Make sure it's unchecked. Now, we gotta install root.
5. ROOTING
The all holy root, finally here. Type this into the terminal:
Code:
adb reboot fastboot
You should be familiar with this process by now. Once in fastboot mode, type:
Code:
fastboot boot root.img
Once finished, reboot. You should boot up as a rooted user, hooray! Only one final step, we gotta give ourselves some means to control this new power, that's where the SuperSU app comes into play.
6. INSTALLING SUPERSU
Apparently, not every single SuperSU apk file works... but lucky for you, I managed to scout and bundle one that does, so use that one. Make sure the apk file is in the same folder as "adb.exe" (as with all of the previous files) and type:
Code:
adb install supersu-2-82.apk
Leave it a few mins, and you should see a "success!" message when it's finished. Open the SuperSU app and it will tell you that you need to update the binaries. Say yes to that, and when asked wether to do a "Normal" update or "TWRP" update, select normal. It should be successful and prompt you to reboot, do so.
That's about it, you now have root access in the ASUS ZenPad C 7.0.
NOTE: Every single attempt I made to make the SuperSU app a system app resulted in the app crashing and I needed to reinstall it again, do as you please.
Why would you even want to do this you might ask? Well, I personally used this to make a few tweaks with Kernel Auditor and L Speed, two apps that will let you customize the performance of the machine to its maximum... sacrificing battery of course. You can search online for the best configuration for you for these apps. With the right tweaks, it transforms from **** to usable, and you need root for all of this.
As a quick note, you might notice that the SuperSU pop up that prompts you wether to grant or deny root access to an app is delayed, that's just how life is with this machine, it's slow. As a tip, when an app is trying to acquire root access, go back to the home screen and open the SuperSU app, then go back to the app you were trying to give it access to, it should appear quicked that way. Sometimes it's so slow that the app says I don't have root, only to have the pop up appear 10 seconds later. Now... to a final chapter.
7. UNBRICKING
This would be the end of the story if nothing went wrong, you have a rooted tablet and you can now do whatever you want with it, but that's not how life is. **** happens, things can go wrong, and when they do, you better have a backup plan. I don't know how to get back your ex, but I know how you can unbrick your tablet if that should happen. Follow these steps if you want to recover this machine...
Code:
#This process will wipe all data, but you shouldn't care about that since you can't access it anyway.
So, if the tablet doesn't turn on and gets stuck at the boot up screen, what can we do? Well, let it sit at the boot up screen for a few mins, and then type in the terminal:
Code:
adb devices
If it's recognized, then type:
Code:
adb reboot recovery
If it's not recognized, press the power button and the volume down key until the tablet turns off. Once that happens, press the power button and the volume down key, when the logo appears, let go of the power button and keep the volume down key pressed, that should boot the tablet into recovery mode. If you got into recovery mode, skip to 7.2
7.1 FIXING RECOVERY MODE
Sometimes, (it happened to me), recovery mode is broken.... it just doesn't appear, no matter what you do you can't get into it. To fix this, we gotta flash it again. We gotta enter fastboot mode. One option is to boot up the device until it gets stucked and wait a few mins, then adb should be able to recognize it and you type:
Code:
adb reboot fastboot
If that's not the case, turn the tablet off and press power and volume up, that should get you to fastboot. Once there type:
Code:
fastboot devices
And the tablet should appear there, if it doesn't... well it better do. I don't really know what to do if it doesn't appear there, but there shouldn't be a reason for it not to. I guess you can try to enter fastboot once again, with the tabler connected from the beggining or something like that, let's just assume it does, and if it doesn't then I'm sorry to tell you that's homework you will have to do.
Once here, we must format the cache and the data partition, for that type the following:
Code:
fastboot format cache
fastboot format userdata
Now, we need to get the recovery files, grab them from the zip I gave you. The files in question are "recovery.bin" and "vrl.bin". We will start with vrl. Once the two formats are finished, type:
Code:
fastboot flash vrl vrl.bin
Followed by:
Code:
fastboot flash recovery recovery.bin
Once that's done, press the power button and volume down keys until the tablet turns off. Then, press them again until the logo appears, and when that happens let go of the power button, that should get you (finally) into recovery.
7.2 UNBRICKING (FOR REAL THIS TIME)
Well, now that everybody is on the same page, and we could get to recovery mode, it's time to repeat some steps really... Follow the procedure from step 4 onwards (from the part that tells you to go to recovery). So, wipe data and apply that damn zip with sideload, the tablet should work now.
That's all I have to offer guys. I'm not a developer, I'm just a guy with a bunch of free time on his hands, so I was able to gather all of this information and (most importantly) files so you can root and fix this god damn tablet. Until the next one!
FINAL NOTE: In the files I included, there's a TWRP.img file. This is the TWRP custom recovery. As far as I know, this version should work with this tablet, but I was unable to flash it and make it work. IF YOU WANT TO TRY THIS DO SO AT YOUR OWN RISK, IT'S HIGHLY PROBABLE THAT THIS WILL RESULT IN BRICKING YOUR TABLET AND BREAKING THE STOCK RECOVERY, IN WICH CASE YOU WILL NEED TO FOLLOW THE STEPS STATED IN THIS GUIDE.
I couldn't upload the files as an attachment directly... sorry.
The "updated_firmware.zip" file is added as a separate download because it's a bigger file, and I prefer to let people decide if they even want it in the first place.
updated_firmware.zip
Everything else
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
neghvar said:
None of the 8 drivers from Intel or Google detect the device in fastboot mode. I tried fixing this tablet years ago and had the fastboot drivers. As far as I know I have the same ones. These all loaded with no problem, but I could never get ADB Device to detect it in fastboot mode
Google: Android ADB Interface | Android Bootloader Interface | Android Composite ADB Interface
Intel: Android ADB Interface | Android Bootloader Interface | Intel AndroidADB Interface | Intel Android Bootloader Interface | Intel Android Composite ADB Interface
Click to expand...
Click to collapse
Make sure you enable usb debugging, no driver will work without that enabled.
tralph3 said:
Make sure you enable usb debugging, no driver will work without that enabled.
Click to expand...
Click to collapse
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
neghvar said:
Not possible. This hangs during boot up or I can enter fast boot mode. It has been like this for years. Basically a soft brick. I tried to fix this years ago as stated above, but having seen this latest post about it, I decided to try again. But this time, I cannot find a fastboot driver that shows the device as attached when I run ADB devices
Click to expand...
Click to collapse
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
tralph3 said:
Be aware that when in fastboot mode, adb devices never lists anything, you must use "fastboot devices"
Click to expand...
Click to collapse
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
neghvar said:
Yep! That's where I was messing up. Thank you.
And the tablet is now working. Thank you very much.
One last question though. I tried to install the twrp.img file included in the pack
fastboot flash recovery TWRP.img
Here is what I got
Sending 'recovery' (26588 KB) (bootloader) Ready to receive: 0x019f7000 size of data
OKAY [ 0.741s]
Writing 'recovery' (bootloader) Flashing partition: recovery
FAILED (remote: ' Download image size is large than partition size')
fastboot: error: Command failed
How do I get around this if the image file is too large?
Click to expand...
Click to collapse
Yeah I never could get around it either. I never could install a custom recovery on this tablet, it just wasn't made for it. But hey, root is cool.
Work?
Still working?
jerryspring said:
Still working?
Click to expand...
Click to collapse
Why wouldn't it? This tablet ain't gonna change. Everything should work no problem.
Hi, any custom rom for this device to make it useful ?
It is in my drawer for more than 2 years and I just do not know what with it
Also how to play with settings in root mode so I can make it faster ?
Hey folks,
I recently followed this guide and a couple of issues.
First, I had expected all my data to be gone, which is fine. But it wasn't. I seemed to have gotten all the way through without it being reformatted, and this makes me suspect I never really achieved all the goals.
One thing I should note, in recovery boot, I had to use the volume button to select a source. No big deal, but it had not worked until I guessed I needed to do that.
Oh, and another thing is I had to install the driver package, and then after, once it was rebooted into fastboot, manually guide the device manager to select from list.
It seems after complete shutdown and then a fresh bootup, my SuperSU software was gone. So, is this only a tethered root boot? Is there a completely untethered?
After rebooting again, it seems my device will not complete booting, but I will give it some more time. I may have bricked it, though I have no idea how lol. All I did was enable USB debugging again and issued the reboot command.
I know this is an old guide, and probably long forgotten by most participants, but I recently got one of these tablets online, open box but new or like new, for around $20, and I would like to get it rooted because otherwise, it is extremely sluggish and the battery drains very fast. I read online it is google play services at fault, but I do not know for sure.
Anyway, if anyone has any updated info or alternative method to achieve full root access untethered, please advise. Unless this guide is that, in which case I just need to try again. Just out of curiosity, what is the TWRP.img for?
hey, i have a completely stock 9 pro, i was texting someone and sending them pictures from the night but while i was doing that the phone suddenly crashed to the lock screen over and over again. so i just hard rebooted it since it was completely unresponsive and just crashing on the lock screen and now it will not even boot up it just shows the oneplus log and a field to put in a password and after entering the password its looking to format the phone and probably factory reset the whole device i was hoping that there would be some way to use adb to get my photos back since i didnt get a chance to save or send them and it would be a real bummer if they were gone. not enough to pay 1000s of dollar but enough that i would spend time playing with adb to recover them. im very familiar with commandline and adb but i dont know of a way to get in without unlocking the bootloader first.... any help would be very much appreciated.
Can you manage to boot into fastboot and try some things there?
Setup platform tools (let me know if you do not have it setup) and then boot into fastboot. Connect your device to your computer and try out the following commands :
fastboot getvar current-slot
If this outputs something like :
current-slot: b
Then run the following command :
fastboot --set-active=a
otherwise, run the following command :
fastboot --set-active=b
After this is done, reboot your device by running :
fastboot reboot
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
I never set bios or lockscreen passwords, or encrypt data drives. You are the one most likely to be locked out, sometimes through no fault of your own. People will steal these devices regardless if they're locked or not; physical security is the only type of security that works.
wjcrabtree said:
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
Click to expand...
Click to collapse
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
ekin_strops said:
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
Click to expand...
Click to collapse
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
You can't do a factory reset from there?
It's rare but a SEU can corrupt any part of the flash memory. It causes no physical damage but the altered memory cells will need reset.
I think the best way to recover is MSM tool for youre specific model phone.
My phone power off by it self after watching a video on a received link with whatsapp.
Nothing workt beside MSM. I factory reset, downgrade rom. flash-reflash rom's.
MSM wipe all in youre phone.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Thank you so much!!
Sorry for the slow reply, but I haven't had time to deal with the problem because of work. I'll be looking into this today.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Ho Lee Sheet! I finally got around to dedicating serious time to working on this.
I had to jack-around with it quite a bit to get Windows 11 to load the proper drivers so that the phone would be recognized, but: BOOM! BACK IN BUSINESS!
Thank you so much for the guidance.