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.
Related
Somehow, trying to install TWRP via fastboot, I've soft bricked myself.
I can boot into fastboot mode and that's about it. My bootloader says it's still locked even though I've attempted to unlock it via the fastboot oem unlock command.
So I'm kinda stuck at the fastboot mode screen or the 1+ screen.
Any idea's?
I'm soft bricked too.
Unrooted using KingRoot and then tried to install the 2.1.3 update.
It failed and now I can't get into the system. What should I do? Can I unlock my bootloader in this state?
Try fastboot boot ( name of twrp recovery file).img
Sent from my OnePlus X
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Open cmd prompt in the same folder where you flashed twrp.
Sent from my OnePlus X
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Calvin2394 said:
I'm soft bricked too.
Unrooted using KingRoot and then tried to install the 2.1.3 update.
It failed and now I can't get into the system. What should I do? Can I unlock my bootloader in this state?
Click to expand...
Click to collapse
If you didn't swipe unlock bootloader in developer settings I don't think you can. Also can you get into fastboot?
Sent from my OnePlus X
i have the same exact issue, i didn't select unlock bootloader in development settings
mawells787 said:
Try fastboot boot ( name of twrp recovery file).img
Sent from my OnePlus X
---------- Post added at 12:37 AM ---------- Previous post was at 12:35 AM ----------
Open cmd prompt in the same folder where you flashed twrp.
Sent from my OnePlus X
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
If you didn't swipe unlock bootloader in developer settings I don't think you can. Also can you get into fastboot?
Sent from my OnePlus X
Click to expand...
Click to collapse
Yep, can get into fastboot. Should I first just boot TWRP using fastboot boot, and then
1. Wipe system, 2. Install OTAs?
Edit: Unable to fastboot boot, says Device not unlocked
Edit 2: fastboot oem unlock works! Let's try flashing recovery.
The following procedure will only work if you have a microSD card with adapter for a computer. You need to download the stock rom and save it to the microSD card then place it back into the X.
Ok guys, you should still have stock recovery if twrp didn't flash. Go to this thread http://forum.xda-developers.com/showthread.php?t=3244996
Click the link to download otas, only download the one with this file name ( OnePlusOxygen_14_OTA_003_all_201510241934 ). You can flash this file through stock recovery. It should preserve your data. I personally did this while I still had a locked bootloader.
If you can't do this now, just turn the phone off and leave it charging for a while. Then just try to turn it on, or try to get into recovery.
Sent from my OnePlus X
---------- Post added at 01:03 AM ---------- Previous post was at 01:00 AM ----------
Calvin2394 said:
Yep, can get into fastboot. Should I first just boot TWRP using fastboot boot, and then
1. Wipe system, 2. Install OTAs?
Edit: Unable to fastboot boot, says Device not unlocked
Click to expand...
Click to collapse
Ok well then try to go into recovery the manual way. I believe it's power + volume up.
Sent from my OnePlus X
---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------
Don't wipe anything, unless you have the stock rom readily available.
Sent from my OnePlus X
mawells787 said:
The following procedure will only work if you have a microSD card with adapter for a computer. You need to download the stock rom and save it to the microSD card then place it back into the X.
Ok guys, you should still have stock recovery if twrp didn't flash. Go to this thread http://forum.xda-developers.com/showthread.php?t=3244996
Click the link to download otas, only download the one with this file name ( OnePlusOxygen_14_OTA_003_all_201510241934 ). You can flash this file through stock recovery. It should preserve your data. I personally did this while I still had a locked bootloader.
If you can't do this now, just turn the phone off and leave it charging for a while. Then just try to turn it on, or try to get into recovery.
Sent from my OnePlus X
---------- Post added at 01:03 AM ---------- Previous post was at 01:00 AM ----------
Ok well then try to go into recovery the manual way. I believe it's power + volume up.
Sent from my OnePlus X
---------- Post added at 01:05 AM ---------- Previous post was at 01:03 AM ----------
Don't wipe anything, unless you have the stock rom readily available.
Sent from my OnePlus X
Click to expand...
Click to collapse
Sorry for bothering you, I managed to unlock my bootloader and flash recovery. I'll flash stock OTAs now and it should boot up fine.
Thank you so much for your time
How did you manage to unlock your bootloader? I cannot even get into stock recovery...It's either fastboot or nothing!
joey24z1 said:
How did you manage to unlock your bootloader? I cannot even get into stock recovery...It's either fastboot or nothing!
Click to expand...
Click to collapse
you need fastboot to unlock bootloader not recovery
Yeah, I must have tried the fastboot oem unlock command about 100 times....It just reboots and then sits on the 1+ screen......I'm stumped!
joey24z1 said:
Yeah, I must have tried the fastboot oem unlock command about 100 times....It just reboots and then sits on the 1+ screen......I'm stumped!
Click to expand...
Click to collapse
Bad news. You'll need to do a remote support session with OnePlus to have your phone reflashed with their Qualcomm tool.
Sorry for OT, didn't want to create another thread!
Here's what I did
1. Unlocked the bootloader
2. Flashed eng.stk TWRP recovery
3. Flashed OxygenOS 2.1 OTA 003
4. Flashed OxygenOS 2.1.3 OTA 004 + OTA 005
5. Rooted using SuperSU
6. Installed eng.stk blu_spark kernel
SOMEHOW, I still have my modem and IMEI partitions!
Does that mean I just need to
1. Flash stock ROM
2. Relock bootloader
To reclaim warranty?
Edit: I wiped /system before flashing OxygenOS
Calvin2394 said:
Sorry for OT, didn't want to create another thread!
Here's what I did
1. Unlocked the bootloader
2. Flashed eng.stk TWRP recovery
3. Flashed OxygenOS 2.1 OTA 003
4. Flashed OxygenOS 2.1.3 OTA 004 + OTA 005
5. Rooted using SuperSU
6. Installed eng.stk blu_spark kernel
SOMEHOW, I still have my modem and IMEI partitions!
Does that mean I just need to
1. Flash stock ROM
2. Relock bootloader
To reclaim warranty?
Edit: I wiped /system before flashing OxygenOS
Click to expand...
Click to collapse
Unlocking bootloader or installin super su doesnt voids your op warranty
mohammedtabish said:
Unlocking bootloader or installin super su doesnt voids your op warranty
Click to expand...
Click to collapse
So what does?
Usually when installing a ROM, /system needs to be wiped.
If /system wipe does not lose my IMEI partitions, I could just reflash stock ROM and my warranty is back?
Edit: Are you sure a bootloader unlock doesn't void warranty?
It was true for OPO, same goes for OPX?
Tapatalk'd from my OnePlus X
Calvin2394 said:
So what does?
Usually when installing a ROM, /system needs to be wiped.
If /system wipe does not lose my IMEI partitions, I could just reflash stock ROM and my warranty is back?
Tapatalk'd from my OnePlus X
Click to expand...
Click to collapse
If you hard brick your device or burn your cpu by overlocking or somehow
So what happens you can't unlock your boootloader? When I go into fastboot, enter fastboot oem unlock, the only thing that happens is it reboots and then gets stuck on the logo screen...Any ideas?
joey24z1 said:
So what happens you can't unlock your boootloader? When I go into fastboot, enter fastboot oem unlock, the only thing that happens is it reboots and then gets stuck on the logo screen...Any ideas?
Click to expand...
Click to collapse
Did you checked the option of oem unlocking in developers mode?
Yeah, it was unlocked before I got the bootloop
What does the following command gives ?
Code:
fastboot devices
erwann.jeanneau said:
What does the following command gives ?
Code:
fastboot devices
Click to expand...
Click to collapse
It should supply a string of numbers if your phone is connected in fastboot. If nothing comes up, the adb isn't seeing your phone.
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!
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!!!
after a serious of stupid operations, here is the current state of my nexus 9 lte..
1. no android os is correctly installed, after reboot, it stay on a black screen with google logo.
2. it can be connected to pc and use adb and fastboot.
3. it is oem locked! fastboot oem unlock return error.
since it is locked, I can't use fastboot to flash the factory image, I try adb sideload the full ota img, and it finished without error, but after reboot it still stay on the google logo.
any suggestions? is there anything else I can do?
yitahutu said:
after a serious of stupid operations, here is the current state of my nexus 9 lte..
1. no android os is correctly installed, after reboot, it stay on a black screen with google logo.
2. it can be connected to pc and use adb and fastboot.
3. it is oem locked! fastboot oem unlock return error.
since it is locked, I can't use fastboot to flash the factory image, I try adb sideload the full ota img, and it finished without error, but after reboot it still stay on the google logo.
any suggestions? is there anything else I can do?
Click to expand...
Click to collapse
Do you have twrp installed by any chance? If yes, see if this will help. Good luck.
If stock recovery, sorry dude. I'm not sure.
madbat99 said:
Do you have twrp installed by any chance? If yes, see if this will help. Good luck.
If stock recovery, sorry dude.
Click to expand...
Click to collapse
no twrp, it's stock recovery, looks like game is over!
yitahutu said:
after a serious of stupid operations, here is the current state of my nexus 9 lte..
1. no android os is correctly installed, after reboot, it stay on a black screen with google logo.
2. it can be connected to pc and use adb and fastboot.
3. it is oem locked! fastboot oem unlock return error.
since it is locked, I can't use fastboot to flash the factory image, I try adb sideload the full ota img, and it finished without error, but after reboot it still stay on the google logo.
any suggestions? is there anything else I can do?
Click to expand...
Click to collapse
Can you access stock recovery? If so grab an OTA image (NOT FASTBOOT IMAGE!!! AN OTA IMAGE!!!) and sideload it via adb sideload. Make sure you have adb 1.0.32 installed or above. I needed to do this for my Nexus 9.
---------- Post added at 06:45 AM ---------- Previous post was at 06:43 AM ----------
yitahutu said:
no twrp, it's stock recovery, looks like game is over!
Click to expand...
Click to collapse
Not at all game over, there is never a game over on XDA.
https://developers.google.com/android/ota
Just find the Nexus 9 tab and run "adb sideload [path to ota.zip]" like normal. remember, when you get to stock recovery from HBOOT, hold down power, hit volume up, and release both keys to get to the menu where you can choose to do a "USB update"
Forgot about the ota images. Never used one. I knew there was a way, when people started having this issue I thought I remembered Google making a fix.
Galaxyninja66 said:
Can you access stock recovery? If so grab an OTA image (NOT FASTBOOT IMAGE!!! AN OTA IMAGE!!!) and sideload it via adb sideload. Make sure you have adb 1.0.32 installed or above. I needed to do this for my Nexus 9.
---------- Post added at 06:45 AM ---------- Previous post was at 06:43 AM ----------
Not at all game over, there is never a game over on XDA.
Just find the Nexus 9 tab and run "adb sideload [path to ota.zip]" like normal. remember, when you get to stock recovery from HBOOT, hold down power, hit volume up, and release both keys to get to the menu where you can choose to do a "USB update"
Click to expand...
Click to collapse
as I mentioned in my 1st post, I've already tried the adb sideload method.
yitahutu said:
as I mentioned in my 1st post, I've already tried the adb sideload method.
Click to expand...
Click to collapse
Oh sorry my bad... hmmm that is a thinker. Just keep trying different OTA images, downgrade, upgrade, everything. Do you remember what may have caused this? it may help us figure out what's wrong.
EDIT: Factory reset between each OTA image of course. /data might be wonked.
yitahutu said:
as I mentioned in my 1st post, I've already tried the adb sideload method.
Click to expand...
Click to collapse
Factory reset.
Ninja'd lol. Labs didn't update for me
today, I retry the adb sideload method with a new ota image.
in my previous test, I used the v6.0.1 mmb29x, and today I download and sideloaded the v7.0 nrd91n, this time it worked! now I can reboot and pass the stupid google logo.
yitahutu said:
today, I retry the adb sideload method with a new ota image.
in my previous test, I used the v6.0.1 mmb29x, and today I download and sideloaded the v7.0 nrd91n, this time it worked! now I can reboot and pass the stupid google logo.
Click to expand...
Click to collapse
Nice. Glad to hear
I own an Alcatel 3(5052A) shipped with Android 8.1.0. It has a Mediatek MT6739 chipset. I managed to do fastboot oem unlock to unlock the bootloader and flash the official Resurrection Remix GSI successfully but when I attempt to flash Magisk patched boot image I get a fastboot error.
Code:
FAILED (remote: Only system partition can be flashed)
Does anyone know a method to unlock flashing for the other partitions?
I already tried 'fastboot flashing unlock_critical' to no success.
Thanks.
The same on alcatel 1
Im having the same issue at flashing twrp on alcatel 1 :crying:
Ya, me too, having the same issue. It says " Only system partition can be flashed", what does that even mean??? I've unlocked the bootloader Alcatel 1 & yet I get this error.
Is it something to do with the firmware we're on??
Bythos73 said:
I own an Alcatel 3(5052A) shipped with Android 8.1.0. It has a Mediatek MT6739 chipset. I managed to do fastboot oem unlock to unlock the bootloader and flash the official Resurrection Remix GSI successfully but when I attempt to flash Magisk patched boot image I get a fastboot error.
Does anyone know a method to unlock flashing for the other partitions?
I already tried 'fastboot flashing unlock_critical' to no success.
Thanks.
Click to expand...
Click to collapse
If you have your boot.img file go look up mtk-su (I've used this before it's a really good tool). if you don't already have root access then you can use that and run the following in the root shell:
mtk-su gives you a temp root shell for that session and your free to do as you please with it so hopefully that helps you guys
dd if=/sdcard/boot.img if=/dev/block/<path to boot>
Also if you need to try these both:
fastboot oem unlock_critical
fastboot flashing unlock_critical
And you should be good to go
Ensure you place boot.img under /sdcard or similar to where you'd like to flash
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
dagman5 said:
Im having the same issue at flashing twrp on alcatel 1 :crying:
Click to expand...
Click to collapse
Do the same with what I expla below but do the recovery partition
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
sachb_htc said:
Ya, me too, having the same issue. It says " Only system partition can be flashed", what does that even mean??? I've unlocked the bootloader Alcatel 1 & yet I get this error.
Is it something to do with the firmware we're on??
Click to expand...
Click to collapse
This means even with the bootloader unlocked the OEM has still restricted flashing other partitions. It's a custom implementation they have in place
TheExploitedOne said:
If you have your boot.img file go look up mtk-su (I've used this before it's a really good tool). if you don't already have root access then you can use that and run the following in the root shell:
mtk-su gives you a temp root shell for that session and your free to do as you please with it so hopefully that helps you guys
dd if=/sdcard/boot.img if=/dev/block/<path to boot>
Also if you need to try these both:
fastboot oem unlock_critical
fastboot flashing unlock_critical
And you should be good to go
Ensure you place boot.img under /sdcard or similar to where you'd like to flash
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
Do the same with what I expla below but do the recovery partition
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
This means even with the bootloader unlocked the OEM has still restricted flashing other partitions. It's a custom implementation they have in place
Click to expand...
Click to collapse
But, there are many sources claiming that you can install a custom recovery like "Twrp" on the Alcatel 1.
Sent from my LM-G710 using Tapatalk
sachb_htc said:
But, there are many sources claiming that you can install a custom recovery like "Twrp" on the Alcatel 1.
Click to expand...
Click to collapse
Yes their Bootloader's are able to be unlocked. If that's the case your able to flash a custom recovery because signature verification is disabled in this state. You'd probably have to build the source code to be able to flash if not already available
TheExploitedOne said:
Yes their Bootloader's are able to be unlocked. If that's the case your able to flash a custom recovery because signature verification is disabled in this state. You'd probably have to build the source code to be able to flash if not already available
Click to expand...
Click to collapse
This is one of the site, which claims to have twrp installed on Alcatel 1: https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
sachb_htc said:
This is one of the site, which claims to have twrp installed on Alcatel 1: https://unofficialtwrp.com/twrp-3-3-0-root-alcatel-5033d/
Click to expand...
Click to collapse
Looking at said site it don't seem to be legit
So I found this thread and my long dead hopes of dropping a twrp into my device twitched, I mean after so many road blocks I'm surprised my hopes even budged but anyway here goes.
AOSP v32 android 8.1 installed on my Alcatel 5033A su version so I have root... ish
I can't write anything to the system and it stays there (after moving if it goes it's removed on reboot) and that's if I remount to RW cause otherwise even with root moving anything fails, all along I've been flashing my recovery with flashify and keep breaking recovery only to try fastboot method after realizing I can install a TWRP built for MediaTek MT6739 Chipset but that's how I saw the problem, it seems to be the same I get this error too >only system partition can be flashed<.
fastboot oem unlock_critical
fastboot flashing unlock_critical
Tried these codes and yeah I was able to do the unlock but afterwards I typed
Fastboot flash recovery <path> do you see my suffering T_T do you see cause I see no (-u)
rubbed it in my own face to see if I'd laugh too didn't even realize I typed this like three times without -u
So on reboot I see the start button checked logs on my pc I'm back at square 1 this phone is cursed like someone from the dev team just sat chanting for hours just to make my life miserable.