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.
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
I literally ****ed up. No OS, No Recovery. My only hope is flashing from fastboot with my extracted images from update.app.
I just wanted to root my phone. I completely followed the step in this thread https://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162 aside from just flashing TWRP 3.1.0.0 because TWRP 3.0.2.0 wont work for me. Well it was working for me and when I tried to flash the SuperSU.zip it says "unable to mount /data" so i'd do my research and to fix that i need to change file system to fat and format, then changed it back to ext4 and format. It fixed the issue but i was not aware that it will wipe my os. So I have no backup for ready. I'm down to no os but i have twrp. I wanted to make my own flashable zip rom that i extracted from update.app. The flashable zip that I worked does not working. The META-INF,system.img,boot.img then archived to zip file then flash it. I'm so ****ed up i tried to directly flash the images in TWRP. Flashed the boot.img to boot partition, and flash recovery.img to recovery partition. And when i tried to flash the system.img in oeminfo,boot, and recovery partition. The file size is big and it does not work that way. So in short i flashed the stock recovery.img over my TWRP. And that's ****ed up. My only hope is flashing the images via fastboot but my fastboot cant detect my device. I'm stuck at 2 boots only. The Huawei eRecovery ( i tried to download latest version and recovery via wifi but the package wont download) and Rescue Mode. Thankk youu in advance for helping me. I would appreciate it so lot! Help me
Fastboot flash system system.img
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Amaan007 said:
Fastboot flash system system.img
Click to expand...
Click to collapse
Do u have huawei y6 II
Amaan007 said:
Fastboot flash system system.img
---------- Post added at 08:30 PM ---------- Previous post was at 08:28 PM ----------
Do u have huawei y6 II
Click to expand...
Click to collapse
I am using Huawei Y6 II (CAM-L21). Thank you for reply But yes I am trying to use adb and fastboot command but my computer can't recognize it. I mean when I plugged it in my computer it does not show anything and when I'm trying to enter the command (adb devices) It only shows
"* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached"
I think it might have to do something in the twrp recovery. When my twrp recovery is working it shows my device and my laptop can recognize it. When I accidentally wipe my recovery it does not show anymore. One thing I found out that It recognize my device when I'm looking into device manager. It shows in Portable Device and something F:/
Thaank youu for noticing me
Valkenburgh Margin said:
I am using Huawei Y6 II (CAM-L21). Thank you for reply But yes I am trying to use adb and fastboot command but my computer can't recognize it. I mean when I plugged it in my computer it does not show anything and when I'm trying to enter the command (adb devices) It only shows
"* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached"
I think it might have to do something in the twrp recovery. When my twrp recovery is working it shows my device and my laptop can recognize it. When I accidentally wipe my recovery it does not show anymore. One thing I found out that It recognize my device when I'm looking into device manager. It shows in Portable Device and something F:/
Thaank youu for noticing me
Click to expand...
Click to collapse
Go to fastboot and type fasboot devices and tell me the outcome
---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------
Amaan007 said:
Go to fastboot and type fasboot devices and tell me the outcome
Click to expand...
Click to collapse
https://forum.xda-developers.com/ho...m-unofficial-lineageos-14-1-honor-4c-t3591305
Flash this with sdcard its compatible with ur phone or move the zip file with USB or put in ur sdcard and flash it with twrp hit thanks if it helped
Amaan007 said:
Go to fastboot and type fasboot devices and tell me the outcome
---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------
https://forum.xda-developers.com/ho...m-unofficial-lineageos-14-1-honor-4c-t3591305
Flash this with sdcard its compatible with ur phone or move the zip file with USB or put in ur sdcard and flash it with twrp hit thanks if it helped
Click to expand...
Click to collapse
In fastboot it does not show in listed device.
I would love to flash that rom but I have no custom recovery like twrp Is it possible to flash it with update package?
Valkenburgh Margin said:
In fastboot it does not show in listed device.
I would love to flash that rom but I have no custom recovery like twrp Is it possible to flash it with update package?
Click to expand...
Click to collapse
https://www.facebook.com/amaandip.singh
talk to me on fb
https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
here is a updater for fastboot
Just asking what tool are u using
Amaan007 said:
https://www.facebook.com/amaandip.singh
talk to me on fb
https://drive.google.com/open?id=0B0MKgCbUM0itNVB1elljU2NPR0k
here is a updater for fastboot
Just asking what tool are u using
Click to expand...
Click to collapse
THAAANKSS TO THIS MAN! He completely taught me things and assisted me. Cheers for you man! How to close this thread? My
Huawei Y6II is completely fixed and rooted! Thanks xda
@matt4321 plz close this thread
Thread closed
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!!!
Hi there,
New here so thanks in advance for any help you guys could provide.
I need to root my Honor 9 for Android Development purposes so I tried to unlock the bootloader to install a TWRP.
(following this thread : https://forum.xda-developers.com/honor-9/how-to/how-to-root-honor-9-stf-l09c432b360a-t3778110)
When it comes to the "adb reboot recovery_ramdisk", it loads to that error message :
Error Mode
Attention!
Please update system again
Error!
Func no: 11 recovery image
Error no: 2 (load failed!)
Any clues of what i'm doing wrong and how I can get rid of that error message...?
(The goral is to root the phone using that Magisk thing everyone's talking about )
Thanks a lot!
still need help ?
oslo83 said:
still need help ?
Click to expand...
Click to collapse
Hi Oslo83!
Yup, still need help. I don't understand what i'have done wrong :/
Phone is still booting in normal mode ?
You got this error screen only when bootinng to recovery ?
Do you still have access ro bootloader ?
---------- Post added at 12:09 ---------- Previous post was at 12:09 ----------
-ro +to
phone is still booting, no probs with that, and I still have access to bootloader yup.
i get the error message when i boot into recovery with adb reboot recovery_ramdisk
if i boot into nrecovery by pressing the buttons, i have the default honor recovery appearing.
What firmware version and region are you on ?
8.0.0.xxx (Cyyy) ?
Recovery mode is 'recovery_ramdisk'...
You should boot in twrp 0.3 when booting into recovery, as you flashed it, if you typed the right command...
recovery and erecovery are 2 differents mode on differents partition.
oslo83 said:
What firmware version and region are you on ?
8.0.0.xxx (Cyyy) ?
Recovery mode is 'recovery_ramdisk'...
You should boot in twrp 0.3 when booting into recovery, as you flashed it, if you typed the right command...
recovery and erecovery are 2 differents mode on differents partition.
Click to expand...
Click to collapse
Version : 8.0.0.364
Region: C432
Well, as i said, i followed the thread step by step and yet, still no twrp.
Thing is, if I want to flash it again with adb (in case of something went wrong during flash?), well, i get a "FAILED" error
it wont flash with adb, but with fastboot it will...
I really think you messed the command you previously typed. Can you post them ?
You'll have to
Code:
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
again then to boot to recovery mode.
---------- Post added at 12:57 ---------- Previous post was at 12:56 ----------
Fant0hm said:
well, i get a "FAILED" error
Click to expand...
Click to collapse
Post the whole error output...
well, first, i connect the phone with usb debug and OEM enabled.
i do
Code:
adb reboot bootloader
wich give me the "fastboot&rescue mode" with phone unlocked and FRP unlock in red
then i do
Code:
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
and it tells me :
Code:
target didn't report max-dowload-size
sending 'recovery_ramdisk' (0KB)...
FAILED (command write failed 'No error))
finished. total time : 0.016s
You're stf-twrp-zxz-0.3.img is wrong or not i' your working folder. Download it again.
---------- Post added at 13:45 ---------- Previous post was at 13:45 ----------
-you're +your -i' +in
Oh! it worked!
Problem apparently wasn't the .img but the "Minimal adb and fastboot"
I downloaded sdk platform tools on my home personnal computer and managed to install twrp (plus, buttons and flash work correctly, yay!)
So, problem solved i guess.
Thanks a lot for your time, Oslo!
I'm using Minimal adb and fastboot without any problem.
oslo83 said:
I'm using Minimal adb and fastboot without any problem.
Click to expand...
Click to collapse
well, i don't know what else it could be. used the same files, the same commands...
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.