The phone has unlockable bootloader and I only have low mobile data and was wondering if there's a way to rip the stock recovery to port twrp over.
When I get wifi tomorrow, I'll try using PC king root while the phone is in fastboot mode.
Kingoroot will get to 100 but fail, kingroot pc version would just give me Chinese letters and do nothing.
Can anyone list anyother root exploits I might I can try on this phone? I tried the Android version of kingroot , but that just gives me the request device and I can't bypass it.
Root u673c
... has anyone been able to root the U673C version 6.0.1, if so, guide me through it, thanks!
we need to somehow extract the stock recovery.img to port twrp over.
Rooted boot image for u673c
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
tdawgg777 said:
I have finally rooted this phone. Here is the rooted boot.img uploaded to MediaFire.
https://www.mediafire.com/download/r6hs4x6mju18j01
Its rooted with Magisk 17.1
Unlock bootloader rename file to boot.img and flash with fastboot.
Click to expand...
Click to collapse
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
DB225 said:
Awesome! SO is it possible to get more detailed instructions. It's been a few years since i've dont this stuff. My old brain's memory isn't so good.
Click to expand...
Click to collapse
Some instructions would be nice, Does not work I can get boot.img to install but it will only boot into stock recovery
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Thank you !
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
does anyone have twrp backup or copy firmware.I wipe internel by accident cant flash u673c no os,thanks sean
---------- Post added at 04:40 AM ---------- Previous post was at 04:32 AM ----------
does anyone have backup or copy firmware u673c cause screwed up wiped internel memory,sean
derwoodbones said:
I just wanted to thank you, I am disabled and dont have alot of income, This phone is my lefeline, I now have it rooted running Magisk 18.0 and TWRP is installed and seems to be working fine, However I would like to ask this. There is an pain in the ass app that seems to be part of the last firmware update this phone had, ( io.appservice.module ) ( Found in data/appi.service.module-1/base.apk
This Kunt sorry for the language, If you uninstall it it is back with every reboot ?
I can disable it to solve the problem but I would like it gone, Any thoughts ?
Click to expand...
Click to collapse
I would just disable the app... just in case there is an update for the phone in future... if you remove the app the update will fail but if its disabled you can just enable it take update and then disable it again... also disable the stock gallery and install a third party one from the playstore... the stock gallery app will through all sorts of ads at you full screen ads as well.
I used titainium backup to disable all apps I didn't want... bit you can use what ever app you want. You can disable most apps in the apps info but not all apps.
I just use the phone as a backup and don't know where it is right now but when I come accross it I'll post all the apps I disabled here.
I healthfully thank you
---------- Post added at 04:00 AM ---------- Previous post was at 03:59 AM ----------
I fully thank you
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
tdawgg777 said:
In developer options click allow OEM unlocking then boot to fastboot mode and use fastboot to unlock bootloader and flash the rooted kernel.
Rename file to boot.img
Unlock bootloader: fastboot oem unlock
Flash kernel: fastboot flash boot boot.img
twrp is not included...
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
Here is the twrp that I used and so far seems to work fine.
https://forum.xda-developers.com/showpost.php?p=78089109&postcount=283
Thank Rortiz2 for building it.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
If you are having trouble booting system after installing twrp try wiping data and cache.
The no verity zip should not be needed since kernel was patched with magisk... but if still Having issues booting system try flashing the no verity zip... you can search for it here on xda
Click to expand...
Click to collapse
smuskat said:
Thanks for the info!
In your post, you wrote, "then boot to fastboot mode".
Kindly explain how that is done on this phone. After spending hours, I can't figure it out.
Thanks again!
Click to expand...
Click to collapse
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
I appreciate your reply.
But I need some more assistance, please:
I've rooted many devices, flashed custom ROM's, Custom recoveries, etc, but I'm completely stuck now with this phone.
I tried "Power and Vol Down"....nothing.
I tried "Power and Vol Up"...and for a split second I see the Android robot on its back...but after that split second, I'm in the stock recovery menu.
One of the stock recovery menu choices is to reboot into Bootloader. When I try that, the phone reboots; but to the best of my knowledge, does not get into Bootloader mode.
I have installed ADB on my PC. When I type "ADB devices", I see my phone listed. But when I type "adb reboot bootloader", it reboots, but not into Bootloader.
I have USB debugging enabled, I have authorized my PC, and in Developer options, I have enabled the "Unlock Bootloader" option.
My Googling results have not yielded useful info.
I'm stuck.....
I hope that someone with experience with this particular device can please tell me what I'm doing wrong.
Thank you!
tdawgg777 said:
I'm sorry I can remember the button combo... From phone off press and hold vol down and power release power and keep holding vol down... I think fast boot mode is an all black screen or it just has umx logo, can't remember exactly... when you have a fast hooky cmd window open type fastboot devices to see if your phone is connected... if it is not try holding vol up instead of vol down when turning phone on... if vol up don't work try holding both vol buttons. Before this can be done make sure usb debugging is enabled in developer options and authorize your pc when prompted... alternately after you have adb authorized you could use adb cmd "adb reboot bootloader"
If you ned help with adb/fastboot do a quick google search you will find plenty of info and instructions
Click to expand...
Click to collapse
hope it helps
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Liberator Elite said:
for me command "Fastboot Continue" would make it continue to load, it did take a while....
if it continues the loop then something went wrong. as i got the infinite bootscreen 1st try.
i just reinstalled the boot image a 2nd time and it worked here's the CRC-32 Hash "a483081b"
Click to expand...
Click to collapse
More Info
smuskat said:
Not sure what you mean. You wrote " command "Fastboot Continue" would make it continue to load" Do you mean from the PC command prompt? Do you mean from the phone's recovery menu?
You also wrote " i got the infinite bootscreen 1st try"
I don't know what you mean by "infinite bootscreen"......
Sorry I'm having trouble....ty!
Click to expand...
Click to collapse
Sent ya PM
Smuskat
Hope That Helps.
I Got Magisk, Xposed & Even A Custom Bootscreen With Sound on Mine.
Okay. Got it all done, mostly thanks to Liberator Elite. And just so that no one else should ever be as stuck as I was, please allow me to clarify what actually worked:
I kept on attempting to put the phone into Fastboot mode or Bootloader mode. I could enter the stock recovery, choose to boot into Bootloader, but it wasn't working--or so I thought. All I would see upon reboot was a screen that was black, with the words "UMX" (Ultimate Mobile Xperience??? or whatever...)
However, Liberator Elite called to my attention that that screen WAS THE BOOTLOADER screen. I typed "Fastboot Devices" from the command prompt, and there was my phone! I then was able to flash over the boot.img file, and the TWRP posted here, and from TWRP, I was able to install Magisk.
For some of you, this is all simple--thanks for not laughing.
And to the entire community, thanks for being such a great resource! All done--thanks to you guys. Much appreciated!!!
Related
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Please, could someone write a good step-by-step newb-friendly manual on how to get the Jelly Bean on this tab? I am seriously considering throwing this thing out of the window right now as I spent the whole evening trying to get this working with no results.
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
oh_delay said:
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
Click to expand...
Click to collapse
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
oh_delay said:
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Click to expand...
Click to collapse
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
AW: Recovery doesn't boot! Help!allready
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
feraay said:
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Click to expand...
Click to collapse
Well, yeah, apparently. I have stock 4.0.4 installed.
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
What exactly should I do? IDK what that means, "Fastboot flash recovery recovery.img
fastboot reboot recovery".
As I said, I am almost a complete newb in this.
pruano said:
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
Click to expand...
Click to collapse
I did adb reboot recovery, and it booted the stock recovery. Maybe I should use another recovery image? I used the one linked in the CM's instructions.
Ok, so basically what happens now is I flash recovery.tar.md5 through Odin, then it reboots in OS and I reboot it to recovery through terminal. The recovery says 'Android system recovery <3e>', so I assume it's the stock one?
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Ok i figured out how to use fastboot command. Still I don't understand, which recovery.img should I flash? I don't have this file, at least not in an .img format, it's format is .tar.md5
So I guess my next question is, where can I get recovery in .img format?
OK, so I figured this out.
I downloaded the recovery.img for the Galaxy Tab 10.1 from the official CWM site (NOT 10.1v, cause they don't have it for this version. It worked fine).
then I loaded in bootloader, used ./fastboot boot <path to downloaded recovery.img>, I just dragged the img to terminal window.
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
So yeah, thank you for your posts and thoughts, you helped me figure this out.
oh_delay said:
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
Click to expand...
Click to collapse
Yes, if you use "fastboot boot [recovery image]" instead of "fastboot flash recovery [recovery image]", you can boot to a custom recovery like CWM without flashing.
oh_delay said:
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
Click to expand...
Click to collapse
Fastboot only accepts .img files, Odin only accepts tar.md5 files; however, tar.md5 files are just archive files, if you rename the file to remove the .md5 extension and use a program like 7-zip which can read .tar files, you will find one or more .img files inside, which you can extract for use with fastboot.
oh_delay said:
So yeah, thank you for your posts and thoughts, you helped me figure this out.
Click to expand...
Click to collapse
Great that you managed on your own (even with some tips), best way to learn.
---------- Post added at 12:12 PM ---------- Previous post was at 12:07 PM ----------
oh_delay said:
Well, yeah, apparently. I have stock 4.0.4 installed.
Click to expand...
Click to collapse
Its the last stock release for this tablet.
---------- Post added at 12:45 PM ---------- Previous post was at 12:12 PM ----------
oh_delay said:
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
Click to expand...
Click to collapse
One last thing: those instructions do not include adding root, as indeed you can use most of the functionality of Cyanogen without root (and possibly exposing your device to malware).
However many useful functions and apps DO require root; to check if you have root, either install this app, or do "adb shell" + "adb su", which should change the prompt from a $ to a #
For root the best way is probably to flash both zip files (ARM version) with CWM at this point (so you get the latest version); dont forget to hit the "Fix Permissions" CWM option afterwards to prevent any potential problems.
AW: Recovery doesn't boot! Help!
Noo dont take 10.1 recovery take the recovery from droidbasement.com
P3 7100 only this
And do this
Adb reboot bootloader
If not work press power and volume +
Or may
power and volume -
Should Boot into bootloader click not in download modus for Odin just take the other icon and Connect to PC
Fastboot flash recovery recovery.img
Thats all
Gesendet von meinem HTC One X mit Tapatalk 2
A lot of people are asking which recovery they need to install with the un-locked bootloader.
This is compatible with all L9 variants that have unlocked bootloaders.
Here is the original link.
https://plus.google.com/app/basic/stream/z13pxhrrjv3sjtoe423wjzkagyveej4wa04
I have attached the image.
Here are the instructions:
1.) Follow instructions in first post from this thread: http://forum.xda-developers.com/showthread.php?t=2119090
2.) Flash CWM with this command: `fastboot flash recovery recovery-clockwork-6.0.2.9-p760.img`
Click to expand...
Click to collapse
3.) Pull battery and re-install.
4.) press "Vol-Up + Home + Power" till recovery is loaded.
kevev said:
A lot of people are asking which recovery they need to install with the un-locked bootloader.
This is compatible with all L9 variants that have unlocked bootloaders.
Here is the original link.
https://plus.google.com/app/basic/stream/z13pxhrrjv3sjtoe423wjzkagyveej4wa04
I have attached the image.
Here are the original instructions:
Code:
Unlocking the LG Optimus L9
The L9's (p760) update to Jellybean from LG started rolling out today. It has a ton of new stuff for people who are interested in keeping the stock ROM,
and another new thing that's of interest to us: the bootloader is now unlockable.
How?
Step 1 - After installing the JB update (I don't know if there are any leaks, but it so avoid them. The real update is out),
make sure you have a SIM in your phone and let it stay on for at least 30 continuous minutes. This is important!.
If you skip this step, you may end up with a permanently locked device.
Step 2 - Enable USB debugging in the developer options, and run " adb reboot oem-unlock " from your PC.
Step 3 - You'll land at a confirmation screen like the one in the first photo of this post. Read it, and follow the instructions there.
Step 4 - If your device unlocked, you'll be in fastboot mode. The phone will helpfully tell you about it (Second photo). Congratulations,
your bootloader is unlocked and your L9 can run unsigned boot images.
Step 5 (optional) - While you're at it, stay in fastboot mode and flash CWM from http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.2.9-p760.img
with " fastboot flash recovery recovery-clockwork-6.0.2.9-p760.img "
Click to expand...
Click to collapse
how can i enter fast boot after unlock it and power it down
altvolt74 said:
how can i enter fast boot after unlock it and power it down
Click to expand...
Click to collapse
I re-wrote the instructions. Try it and let me know if it works.
kevev said:
I re-wrote the instructions. Try it and let me know if it works.
Click to expand...
Click to collapse
ok i had it now im unable to flash recovery on top of the old one no metter what i do...any advice?
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
btw im usin P769 and for enter recovery is power bling lights then press down?
---------- Post added at 08:58 PM ---------- Previous post was at 08:40 PM ----------
for some reson i had to recovery dont know how but tha man
altvolt74 said:
ok i had it now im unable to flash recovery on top of the old one no metter what i do...any advice?
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
btw im usin P769 and for enter recovery is power bling lights then press down?
---------- Post added at 08:58 PM ---------- Previous post was at 08:40 PM ----------
for some reson i had to recovery dont know how but tha man
Click to expand...
Click to collapse
You should be able to flash it over stock recovery. Don't flash the recovery for locked bootlaoder. I don't think it works when bootloader is unlocked.
After flashing pull battery and re-install. Press "Vol-Up + Home + Power" till recovery is loaded.
So I unlocked my blog and I am trying to flash recovery I use prada I got the point where it says put the battery in after 5 seconds then it says pull sub cable and plug in when I get LG screen. I get mirror image of LG with fast-food ov in the corner I. At this point I try to flash recovery but when try to boot to recognize very it's not working am I missing something here.
I flashed 20b unlocked bl flashed back to 10g rooted fixed touch screen stuck on trying to install recovery
Sent from my LG-P769 using xda app-developers app
[2in1GUIDE][JB] Unlock Bootloader and FASTER Root L9 Method
I personally used the touch cwm image in cmahendra's guide. Works well, im still mirrored.
If you have unlocked bootloader and root ( that's a must) it is much easier to use Nandroid Manager (free from market) to flash any compatibile recovery image (6.0.3.1 is the newest touch version or non-touch) just from the phone from *.img file . I've tested it took 2-3 min .
i installed all the fastboot drivers ..still when my phone is in fastboot mode ..it simply doesnt recognize the device..it shows a error stating the usb device attached has malfunctioned and doesnt recognizes it. :crying: I have installed android sdk ....please help searched in google and running out of option ...guys help me out....i really want to root my first and the best android phone again :crying:
does it work...
which model no. do u have..
will it work for p765 v20a
Sent from my LG-P765 using Tapatalk 2
My phone is only restart system after adb reboot oem-unlock .... what I do wrong ?
after installing the recovery, how do I access it? is there any specific "turn on" + KEY combination?
thx
rodrigian said:
after installing the recovery, how do I access it? is there any specific "turn on" + KEY combination?
thx
Click to expand...
Click to collapse
Easiest way is to pass adb command from command prompt. ADB reboot recovery or you can use ROM manager to boot into recovery. If you absolutely need to boot with key combo. Hold vol up + home button and power button when phone vibrates release power it should boot into recovery
Sent from my LG-P769 using xda premium
Tablechair said:
Easiest way is to pass adb command from command prompt. ADB reboot recovery or you can use ROM manager to boot into recovery. If you absolutely need to boot with key combo. Hold vol up + home button and power button when phone vibrates release power it should boot into recovery
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
thanks!
Dear All.
Sorry for my English.
Please help to fix the issue with my Nexus9.
Problem: when I Power On the device- it is show Fastboot screen. I can enter HBOOT->Recovery->device go to TWRP screen.
I don't have any backups to restore.
Please advise:
-how can i flash device normally via TWRP (no sense stock ROM or rooted)? I just want my device normally work (with/without root no sense).
My device is locked bootloader
Thank you all in prompt
You can't flash stock from TWRP.
You will need to flash the latest factory image for your device.
Link to wifi model images scroll up for LTE.
Google "How to manually flash nexus factory images".
Locked
corkiejp said:
You can't flash stock from TWRP.
You will need to flash the latest factory image for your device.
Link to wifi model images[/URL] scroll up for LTE.
Google "How to manually flash nexus factory images".
Click to expand...
Click to collapse
Thank you fo answering!
My device has locked bootloader. And I can't unlock through Developer Options as device go to Fastboot screen directly after power on.
Please help
Dmitry1983 said:
Thank you fo answering!
My device has locked bootloader. And I can't unlock through Developer Options as device go to Fastboot screen directly after power on.
Please help
Click to expand...
Click to collapse
How the hell are you locked, if you have TWRP recovery on the Device?
Have you tried a factory reset?
How did the device get into this state? After OTA process?
Doubt if it will work but you could try sideloading the Android N OTA.
---------- Post added at 01:15 PM ---------- Previous post was at 12:59 PM ----------
Have you tried "fastboot oem unlock", depending on how you relocked your device, that command might still be enabled in developer options.
Someone else suggested a solution in the other thread you posted in.
corkiejp said:
How the hell are you locked, if you have TWRP recovery on the Device?
Have you tried a factory reset?
How did the device get into this state? After OTA process?
Doubt if it will work but you could try sideloading the Android N OTA.
---------- Post added at 01:15 PM ---------- Previous post was at 12:59 PM ----------
Have you tried "fastboot oem unlock", depending on how you relocked your device, that command might still be enabled in developer options.
Someone else suggested a solution in the other thread you posted in.
Click to expand...
Click to collapse
My brother try to root the device.
During flashing something go wrong.
So now
I tryed Factory Reset - it shows This is development device not intended for production use, hten TWRP start, shows errors "Unable to mount data.." and return to fastboot screen
Maybe some hope for you .........
If indeed you have TWRP recovery installed, and your system + data partition are not corrupted/deleted.
You maybe able to set OEM Unlock flag with a flash able script.
Get Nexus BootUnlocker script
Nexus BootUnlocker script (GN, N4, N5, N6, N7 '13, N9, N10)
I don't know about everyone else but sometimes I find I've rebooted into the bootloader only to realize I've forgotten to unlock it in segv11's excellent BootUnlocker App beforehand. Well, I decided to make a BootUnlocker Script for my Galaxy Nexus so I could just boot to recovery quickly, unlock, then adb reboot-bootloader (or use my Reboot To Bootloader script below) to get back without having to fully boot the OS to make the change. Also extremely useful in the case you aren't able to boot. As with the app there is no data loss like there would be with fastboot, allowing you to relock for safety. Originally posted in the GN EDIFY Scripting thread. Modified for the newer Nexus devices and combined into a single Nexus BootUnlocker zip with tamperbit reset support added using information from the BootUnlocker App Dev thread. For newer devices using Factory Reset Protection (N6+N9), the BootUnlocker Script can't directly toggle the lockstate due to new security tokens, but it does now toggle the ability to use "fastboot oem unlock" without needing a booted device.
Click to expand...
Click to collapse
If the script works, issue "fastboot oem unlock" in fastboot mode.
Note: The above script will only work from a custom recovery such as TWRP.
Hi there,
I'm pretty new to zip flashing, but after the installation I regretted and wanted it removed. Before that I had made an entire backup, which I then restored and since then my phone has not been able to boot.
I've tried to boot into recovery mode but without any luck. It's stuck on the OnePlus logo.
I can get it in Fastboot though but that's about it and the normal power on results in bootloop.
I've been reading many topics about this but in all cases it's crucial that you've enabled USB Debugging which is quite the task since I'm not able to boot it up.
Hope you guys can help me since I don't have any spare phone at the moment.
P.S. I'm on OP X with OxygenOS.
EDIT: Solved
MattBooze said:
Hi there,
I'm pretty new to zip flashing, but after the installation I regretted and wanted it removed. Before that I had made an entire backup, which I then restored and since then my phone has not been able to boot.
I've tried to boot into recovery mode but without any luck. It's stuck on the OnePlus logo.
I can get it in Fastboot though but that's about it and the normal power on results in bootloop.
I've been reading many topics about this but in all cases it's crucial that you've enabled USB Debugging which is quite the task since I'm not able to boot it up.
Hope you guys can help me since I don't have any spare phone at the moment.
P.S. I'm on OP X with OxygenOS.
EDIT: Solved
Click to expand...
Click to collapse
Hi there, can u help me solve this problem..i have the same problem as yours..Now i dont know what to do..i have tried the mega unbrick but no luck at all still the same issues stuck at the boot logo and reboot itself..i need your help fast..contact me at [email protected] Email me there..please
Basically this is how it goes: You have to have an unlocked bootloader or else it will more than likely not boot into a tampered system. Unlocking the bootloader is simple on this phone and does not void the warranty, but to do so you have to have enabled "OEM unlock" in the developer settings which from the sounds of it you didn't. I'm going to cut and paste some of my response I've sent to other people here:
The first thing you're going to need to do is to flash the stock Recovery from OnePlus. Ypu will flash it the same way you flashed TWRP (if you did) with Fastboot. If you haven't done that and need me to explain it I will, I'll be here all day. Download the recovery here: https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
Next, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/ . Flash that with the stock recovery and then do a Factory Data Reset. You will not lose pictures, music, whatever. You won't lose the backup you made either. We just need it to boot into OOS so you can turn on the unlock option.
Reboot the phone. It might take a while. Once you're into the device everything should be working as normal. Go to Settings -> About Phone. Scroll down and tap the "Build Number" until it says you've enabled Developer settings. Go to Settings -> Developer and turn on OEM Unlock. Now you can boot back into Fastboot, and from your computer use the command "fastboot oem unlock" as simple as that and it will unlock the bootloader. Now if you'd like you can safely reflash the TWRP recovery and you should be able to restore your backup.
---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
husandroid said:
Hi there, can u help me solve this problem..i have the same problem as yours..Now i dont know what to do..i have tried the mega unbrick but no luck at all still the same issues stuck at the boot logo and reboot itself..i need your help fast..contact me at [email protected] Email me there..please
Click to expand...
Click to collapse
I'm not using email but you can read my reply above if you're having the same problem.
I get;
FAILED (remote: dtb not found) when I try to boot, any suggestions?
o.maille said:
I get;
FAILED (remote: dtb not found) when I try to boot, any suggestions?
Click to expand...
Click to collapse
Just reboot manually dude.
o.maille said:
I get;
FAILED (remote: dtb not found) when I try to boot, any suggestions?
Click to expand...
Click to collapse
Which version of oos u were in? If u were in oos 3.1.x u should flash marshmellow stock recovery... Thn u ll nvr never get dtb not found issue
Im having the same issue, but when i try to flash the recovery, it just says "cannot load (filename)". How do i fix this?
Edit: Fixed!
when you update to 3.1.0 twrp recovery is not compactible with the new recovery partition so you need to flash opxstock 3.1.0 recovery so that you will be able to flash android lollipop version of the opx and reroot and install twrp.
the proccess is really simple
1)go to settings about phone and enable developer options by tapping build number 10 times.
2)enable adb and oem unlocking
3)go to the folder you have adb and fastboot installed
4)Place the downloaded recovery file there(the one FROM THIS THREAD!)
5)type 'adb reboot bootloader'
Phone will reboot to bootloader
6)type 'fastboot flash recovery recovery.img'(or the name you gave for the recovery with '.img' at the end)
7)type 'fastboot boot recovery.img'
8)flash update.zip (the 2.1.1 version)If you cannot find the link to the file comment bellow
9)flash the update.zip via stock recovery.
10)your phone is back to stock now and you are able to flash twrp recovery and root your phone now.
Please hit thanks if i helped
EDIT:Unzip the recovery file fist
Post this in General Section
Sorry I can't find the link to update.zip
Please post the update.zip file
adb doesn't recognize my phone anymore, now that I want to try it again with the file from this forum. And it seems to be stuck in fastboot mode.
What should I do?
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
brii_22 said:
adb doesn't recognize my phone anymore, now that I want to try it again with the file from this forum. And it seems to be stuck in fastboot mode.
What should I do?
Click to expand...
Click to collapse
Okay I found it.
Type in adb 'fastboot devices'
it wil recognise your phone
Then 'fastboot reboot'
And my phone works again, and I guess I can just restart the proces now
(replied to myself in case someone else has this problem )
GerasxD said:
when you update to 3.1.0 twrp recovery is not compactible with the new recovery partition so you need to flash opxstock 3.1.0 recovery so that you will be able to flash android lollipop version of the opx and reroot and install twrp.
the proccess is really simple
1)go to settings about phone and enable developer options by tapping build number 10 times.
2)enable adb and oem unlocking
3)go to the folder you have adb and fastboot installed
4)Place the downloaded recovery file there(the one FROM THIS THREAD!)
5)type 'adb reboot bootloader'
Phone will reboot to bootloader
6)type 'fastboot flash recovery recovery.img'(or the name you gave for the recovery with '.img' at the end)
7)type 'fastboot boot recovery.img'
8)flash update.zip (the 2.1.1 version)If you cannot find the link to the file comment bellow
9)flash the update.zip via stock recovery.
10)your phone is back to stock now and you are able to flash twrp recovery and root your phone now.
Please hit thanks if i helped
EDIT:Unzip the recovery file fist
Click to expand...
Click to collapse
many have ask and cannot find the update.zip 2.1.1, where are you?
Hi, It's not working for me.
I still get the same error message: `FAILED (remote: dtb not found)` when I try to boot into recovery.
I would really appreciate some help here
Thanks anyway. I'll keep searching.
---------- Post added at 04:46 AM ---------- Previous post was at 03:51 AM ----------
guiohm said:
Hi, It's not working for me.
I still get the same error message: `FAILED (remote: dtb not found)` when I try to boot into recovery.
I would really appreciate some help here
Thanks anyway. I'll keep searching.
Click to expand...
Click to collapse
Ok, I solved my problem. I had to revert to an older TWRP. I just didn't know that the new updated TWRP is not backward compatible (that's bad) and I couldn't find an older one until I stumbled upon this thread: http://forum.xda-developers.com/showpost.php?p=69170103&postcount=45
guiohm : Thank you SO MUCH ! I searched this solution for hours. I can't tell you how grateful I am.
THANK YOU!
brii_22 said:
adb doesn't recognize my phone anymore, now that I want to try it again with the file from this forum. And it seems to be stuck in fastboot mode.
What should I do?
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
Okay I found it.
Type in adb 'fastboot devices'
it wil recognise your phone
Then 'fastboot reboot'
And my phone works again, and I guess I can just restart the proces now
(replied to myself in case someone else has this problem )
Click to expand...
Click to collapse
Thank you so much! I had the same problem and had no idea what to do.
FingolfinTheEldar said:
Sorry I can't find the link to update.zip
Click to expand...
Click to collapse
You can find it in the One Plus Website for the one plus x. it the rom
Official one okay?
Is it also ok, to take the official twrp 3.1.1-1-onyx from the twrp website?
Thanks
OPforlife said:
Is it also ok, to take the official twrp 3.1.1-1-onyx from the twrp website?
Thanks
Click to expand...
Click to collapse
Not at all. The point is to flash an old offcieal recovery, then OOS 3 to update bootloader.
If you already are on the new bootloader no need to do that.
if you're not, BLupdater.
If already try to flash something not compatible, you may haave to run the Mega unbrick Guide.
Same isse with E1001
I had the same issue "remote: dtb not found" when trying to use recent (3+) versions of TWRP on my E1001 One Plus X. I ended up discovering that only an old version of TWRP (2.8.7) would boot on the device. Here is the version I used successfully on One Plus X E1001 (white): twrp-2.8.7.0-6.0-onyx.img. I cannot post a link to it as the forum is preventing new users to publish external links but I have it if needed.