Thread Closed
Thread Closed
@TheHitMan Thank you so much, this port is perfect! But I think I made a mistake... When, in TWRP, need to flash "no-verity-opt-encrypt.zip" I tryed to flash the lastest (6.0) but it says "FAIL" or something like that...
Long story short, When I turn on the device says "your device has been unlocked and can't be trusted" , "Your device will boot in 5 seconds" (After the 5 seconds the device boot normally)
What can I do to fix that little detail???
WaLt-B.F. said:
@TheHitMan Thank you so much, this port is perfect! But I think I made a mistake... When, in TWRP, need to flash "no-verity-opt-encrypt.zip" I tryed to flash the lastest (6.0) but it says "FAIL" or something like that...
Long story short, When I turn on the device says "your device has been unlocked and can't be trusted" , "Your device will boot in 5 seconds" (After the 5 seconds the device boot normally)
What can I do to fix that little detail???
Click to expand...
Click to collapse
Nothing bad with this warning. Its a bootloader unlock warning.
Officia TWRP is available
shagul said:
Officia TWRP is available
Click to expand...
Click to collapse
No difference, until this build works fine.
Hey bro, can you belive I just do the OTA update with twrp and my phone boot to twrp but not to system???
What can I do??? =\
WaLt-B.F. said:
Hey bro, can you belive I just do the OTA update with twrp and my phone boot to twrp but not to system???
What can I do??? =\
Click to expand...
Click to collapse
Reflash system partition again. First wipe then install.
TheHitMan said:
Reflash system partition again. First wipe then install.
Click to expand...
Click to collapse
I´ve tryed but that doesn´t worked... Long story short, I restarted the phone in flashboot mode, at least in my case i had to install adb bootloader drivers manually, and then use the "flashall.bat" of the stock rom... I was worried...
Thank you!
WaLt-B.F. said:
I´ve tryed but that doesn´t worked... Long story short, I restarted the phone in flashboot mode, at least in my case i had to install adb bootloader drivers manually, and then use the "flashall.bat" of the stock rom... I was worried...
Thank you!
Click to expand...
Click to collapse
You can't install OTA updates with a custom recovery. You need stock recovery to perform OTA update operation.
TheHitMan said:
You can't install OTA updates with a custom recovery. You need stock recovery to perform OTA update operation.
Click to expand...
Click to collapse
Tell me about it xD
I didn´t know that until yesterday, what a noob, lol. Thanks for you help and for answer so soon! :good:
Hi, do u have a version for MT6735 variant?
My device details:
Model: Moto e4 plus
SKU: xt1772
variant: MT6735
i can successfully flash and boot this twrp version, but twrp recognizes my device as codename "woods" (thats moto e4).
Anyway, i tried to install roms for moto e4 "woods" but they all loop the bootloader.
DanielBrownM said:
Hi, do u have a version for MT6735 variant?
My device details:
Model: Moto e4 plus
SKU: xt1772
variant: MT6735
i can successfully flash and boot this twrp version, but twrp recognizes my device as codename "woods" (thats moto e4).
Anyway, i tried to install roms for moto e4 "woods" but they all loop the bootloader.
Click to expand...
Click to collapse
Its "MT6735" the SOC (system-on-chip) not the variant. Do not install moto e4 roms into moto e4 plus you will always ended up with bootloop. Can you please elaborate futher, How it recognize your device as wood ?
Because when i tried to intall the roms, they all returned an error saying: this rom is for nicklaus and this device is woods (not the exact words).
And in twrp home screen, top left of the corner (where usually shows the cpu temperature) says: 3.2.1-opr1-woods
DanielBrownM said:
Because when i tried to intall the roms, they all returned an error saying: this rom is for nicklaus and this device is woods (not the exact words).
And in twrp home screen, top left of the corner (where usually shows the cpu temperature) says: 3.2.1-opr1-woods
Click to expand...
Click to collapse
Thanks for reporting.
I will fix this soon and for now use 3.1.1 build floating around here.
TheHitMan said:
Thanks for reporting.
I will fix this soon and for now use 3.1.1 build floating around here.
Click to expand...
Click to collapse
Thanks but already tried with 3.1.1.
In that version the problem is similar, but instead of woods recognizes the device just as "e4".
DanielBrownM said:
Thanks but already tried with 3.1.1.
In that version the problem is similar, but instead of woods recognizes the device just as "e4".
Click to expand...
Click to collapse
I double check out the 3.1.1 XT1772 thread and no one report about the error you mentioned here.
I have installed v3.1.1 right now, after reading your post, just to be sure.
The output is the next when triting to install roms (dot and aosp) for nicklaus:
Code:
E004: This package is for: nicklaus, e4plus; this device is e4.
DanielBrownM said:
I have installed v3.1.1 right now, after reading your post, just to be sure.
The output is the next when triting to install roms (dot and aosp) for nicklaus:
Code:
E004: This package is for: nicklaus, e4plus; this device is e4.
Click to expand...
Click to collapse
What i have seen from error is not the recovery problem at all. Probably you need to upload META-INF from dotos or aosp rom. It looks like assert command problem.
TheHitMan said:
What i have seen from error is not the recovery problem at all. Probably you need to upload META-INF from dotos or aosp rom. It looks like assert command problem.
Click to expand...
Click to collapse
I just checked updater-script in META-INF file of the rom and probably is assert problem.
When i run ro.product.device in adb the command return this:
Code:
C:\Users\admin>adb shell getprop ro.product.model
Moto E (4) Plus
C:\Users\admin>adb shell getprop ro.product.device
nicklaus_f
C:\Users\admin>adb shell getprop ro.build.product
nicklaus
But, when trying to install the rom in twrp, the return of that command is "wood" for twrp v3.2.1 and "e4" in twrp 3.1.1.
Maybe i should try to delete assert line in updater-script of the rom and install.
----edited---
Actually when i write getprop ro.build.product in twrp terminal returns "woods"
Related
hi
i tried upgrade to hairybeen 2.3 (from an earlier version which is 4.1.1)(its unlocked)
now i get this screen
i tried to flash twrp recovery 2.6 via fastboot
and i get a massage it was flashed ok
is it bricked ?
how can i fix it ?
why the usb icon is missing ?
pre-thank you for helping
EliranB said:
hi
i tried upgrade to hairybeen 2.3 (from an earlier version which is 4.1.1)(its unlocked)
now i get this screen
i tried to flash twrp recovery 2.6 via fastboot
and i get a massage it was flashed ok
is it bricked ?
how can i fix it ?
why the usb icon is missing ?
pre-thank you for helping
Click to expand...
Click to collapse
First of all that message is totally normal in the first screenshot.
The USB icon is missing because in later bootloaders you are instantly in fastboot if you don't select anything.
Now for the problem.... Where did you get that TWRP 2.6 from and what version that you flashed in fastboot...
There are warning all over the Hairybean first post telling you not to flash any other version of twrp on there except what the upgrade puts on because they are not compatible and they will brick you.
If you have flashed a Prime JB TWRP on there you could be in trouble.
Where did you get that TWRP 2.6 from and what version that you flashed in fastboot... from their webpage the 2 in the botom
There are warning all over the Hairybean first post telling you not to flash any other version of twrp on there except what the upgrade puts on because they are not compatible and they will brick you. im sure in 99% it was the jb version
If you have flashed a Prime JB TWRP on there you could be in trouble. so im in trouble now ???
TWRP TF201
EliranB said:
Where did you get that TWRP 2.6 from and what version that you flashed in fastboot... from their webpage the 2 in the botom
There are warning all over the Hairybean first post telling you not to flash any other version of twrp on there except what the upgrade puts on because they are not compatible and they will brick you. im sure in 99% it was the jb version
If you have flashed a Prime JB TWRP on there you could be in trouble.
TWRP TF201
Click to expand...
Click to collapse
You wasn't supposed to use any of them. That is what all the warnings are for.
Can I ask why you flashed it? Compatible 2.6 twrp was included in the bootloader upgrade.
flumpster said:
You wasn't supposed to use any of them. That is what all the warnings are for.
Can I ask why you flashed it? Compatible 2.6 twrp was included in the bootloader upgrade.
Click to expand...
Click to collapse
twrp 2.6 worked for me then i flashed the update of hairybeen & i thought it was stuck after the reboot so i turn it off
then the problem started
so i reflashed the TWRP via fastboot
& now i cant install TWRP or CWM Recovery
its transfering the file successfully but wont load the rck(recovery) mode
so its breaked ? or there is a way to flash something ???
EliranB said:
twrp 2.6 worked for me then i flashed the update of hairybeen & i thought it was stuck after the reboot so i turn it off
then the problem started
so i reflashed the TWRP via fastboot
& now i cant install TWRP or CWM Recovery
its transfering the file successfully but wont load the rck(recovery) mode
so its breaked ? or there is a way to flash something ???
Click to expand...
Click to collapse
Did you restart as the blue line was filling when it was flashing the new partitions ?
flumpster said:
Did you restart as the blue line was filling when it was flashing the new partitions ?
Click to expand...
Click to collapse
the blue line was full
EliranB said:
the blue line was full
Click to expand...
Click to collapse
Yes but you have to wait for it to finish itself and it will restart on its own.
I don't mean to sound nasty but you basically ignored every instruction in the thread.
Your only chance now is to see if the following thread can fix you.. I have a link in it.
http://forum.xda-developers.com/showthread.php?t=2409602
flumpster said:
Yes but you have to wait for it to finish itself and it will restart on its own.
I don't mean to sound nasty but you basically ignored every instruction in the thread.
Your only chance now is to see if the following thread can fix you.. I have a link in it.
http://forum.xda-developers.com/showthread.php?t=2409602
Click to expand...
Click to collapse
i think now i breaked it
i tried the "wipe data" option & now its only in the asus splash screen without fastboot or anything else but asus is unlocked
EliranB said:
i think now i breaked it
i tried the "wipe data" option & now its only in the asus splash screen without fastboot or anything else but asus is unlocked
Click to expand...
Click to collapse
There was nothing in that post I linked you to that says to use that wipe data option mate.
Now I think you are really hard bricked sorry.
i did the mistake
i dont blame you
thank you very much for your help
now i need to replace the motherboard right ??
EliranB said:
i did the mistake
i dont blame you
thank you very much for your help
now i need to replace the motherboard right ??
Click to expand...
Click to collapse
At the moment that is the only option available I am sorry mate unless you made nvflash backups while you was on ICS which I doubt you have.
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!
Hi guys,
Before you say again a topic on a non bricked One Plus X, I would like to let you know that I've checked and try almost all of the tutorial I've seen on xda and one plus forum.
I was on CM14.1 with this ROM : https://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-14-onyx-t3452150
Unfortunately, I made the 25-12-2016 update and it totally broke up the phone..
I download the OnePlus X OxygenOS 3.1.4 on the One Plus website. So I flash it on the stock recovery, it tells me "Install success" then I reboot and it stays on the bootlogo.
For information, I can't access the oem unlock menu if needed, but when I ask the oem device info it says unlocked. The phone is detected by the computer sometimes with unknown device and sometimes correctly with the qualcomm drivers..
I have a back up made from TWRP, I can access the device by the fastboot mode, it seems that all the operations written here worked but it doesn't install or even boot on TWRP..
Thanks for your help guys.
Are you using latest TWRP from website think version 3.0.3?
Exodusche said:
Are you using latest TWRP from website think version 3.0.3?
Click to expand...
Click to collapse
I'm not even using TWRP, since I can't boot on it.. But I tried to flash the twrp-3.0.2-2 from blue spark v41, after the installation via Flashboot, it doesn't boot up on the recovery..
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Exodusche said:
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Click to expand...
Click to collapse
Exactly, the phone is stuck on the one plus logo..
defqon_1 said:
Exactly, the phone is stuck on the one plus logo..
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Divyesh49 said:
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Click to expand...
Click to collapse
Didn't work. I tried to lock and then unlock to be sure but not is stay in false for tempered AND unlocked.
So I don't have any idea on how make android back on my phone.
I just have access to Fastboot mode. No recovery, nothing else..
EDIT : phone is not starting anymore. I try to charge it hoping it just a low battery problem..
You should send it to RMA
Trimis de pe al meu Redmi 3S folosind Tapatalk
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Help Pls
defqon_1 said:
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Click to expand...
Click to collapse
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Fix It!
Exodusche said:
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Click to expand...
Click to collapse
Done! finally i can reinstall stock rom and recovery with drivers by usb.
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Done
defqon_1 said:
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Click to expand...
Click to collapse
Don't worry i have restored my OPX 5 days ago. I used the method of this video: https://youtu.be/R4SVSovw4Jo and files from this thread: https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 , if it can help someone.
I've made TWRP for the Onetouch Idol 3. It should work when you flash it, but using it is still a try at your own risk procedure. Your bootloader must be unlocked ONLY on LP (MM is locked so cant flash on it)to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, adb reboot bootloader
To permanently flash it:
Code:
fastboot -i 0x1bbb flash recovery twrp.img
Update through existing TWRP:
Code:
Flash as image > recovery
The download is up on the AndroidFileHost
Device source:
Kernel
Device
Tester: @Demetris @Alek Dev
XDA:DevDB Information
[RECOVERY] TWRP for Onetouch Idol 3, Tool/Utility for the Alcatel Onetouch Idol 3
Contributors
FireLord
Source Code: https://github.com/omnirom
Version Information
Status: Stable
Created 2017-05-28
Last Updated 2017-05-28
Try to flash this recovery from older TWRP recovery. I don't have problems.
Download the latest TWRP image file (.img) from the download link.
Boot into the TWRP recovery. ( ...
Go to install and find and select the Images button. ( ...
Browse to the image that you downloaded and select it.
Choose recovery and swipe to flash.
You are done!
Little notice, Restarting to recovery won't do. You will have to manually start it to recovery by VolUP+Pow. Especially if you're on 6.0+
Huskied said:
Little notice, Restarting to recovery won't do. You will have to manually start it to recovery by VolUP+Pow. Especially if you're on 6.0+
Click to expand...
Click to collapse
Works just fine here.
Myrage2000 said:
Hey,
I still have some issues flashing this, which is weird considering I can flash other versions of TWRP of this forum.
I'm updating to this version from my current twrp. The flash seems to succeed but then the recovery mode is broke and I got the fastboot mode starting instead...
I also tried to flash it from fastboot, the same issue is happening.
So I finally tried to do a fastboot boot to try it, and I got this error : "dtb not found".
I have a french 6045Y
Update :
According to this video https://www.youtube.com/watch?v=kTdKmceC5xU I should update the bootloader of my phone, which seems a good idea because my 6045Y might have a custom bootloader made by my mobile provider.
Is it possible to update the bootloader of my phone ? Where can I find one ? There's nothing on google
Update 2 :
My bootloader is likely to be old because I never received the MM update, I only have Android 5 (my phone provider is not updating it)
Click to expand...
Click to collapse
Your stock (made by Alcatel) bootloader is different than custom made here by devs. You'll first have to unlock it, push by fastboot commands to the phone custom one, than you can install roms, etc. Try searching the threads here on forum, I done this part 2yrs ago, so I can't recall every step.
Myrage2000 said:
Update 2 :
My bootloader is likely to be old because I never received the MM update, I only have Android 5 (my phone provider is not updating it)
Click to expand...
Click to collapse
I had the same problem. Solved it by flashing the GooGly ROM: https://forum.xda-developers.com/idol-3/development/rom-idol3-6045y-eu5-2-mm-googly-t3519943
Flashing takes a long time but it updates everything. Note that you will lose flashboot and will have to flash things through TWRP from then on.
---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------
@FireLord I made a version with decryption working. Here is the link: https://www.androidfilehost.com/?fid=745425885120738038
Maybe you could mention it in OP for those who want encryption/decryption.
Myrage2000 said:
Thanks !
I made a backup of my aboot to restore flashboot commands (and I hope it won't restore the old bootloader with it x) )
Click to expand...
Click to collapse
Good luck. If the aboot works, I may be interested.
Myrage2000 said:
Hey I'm flashing it at the moment.
I don't know if I'm going to try to restore aboot, because if it fails, I have no way to repair my phone since fastboot commands won't be enable.
And I can't try to flash a new twrp, because if it fails, again I have no way to do something...
I saw a lot of threads for fastboot commands on idol 4.7 6039, but none for idol 5.5 6045
Click to expand...
Click to collapse
Yep, not sure there's a way to get back the fastboot commands. But as long as we have TWRP, then it
s fine.
Myrage2000 said:
Yes !
But I hope we will never have to update TWRP, because if it fails, it fails x)
I saw a new thread with a tool alcatel flasher that works without fastboot commands.
Anyway, ...
Click to expand...
Click to collapse
Should be fine, we can use stuff like rashr to flash from the ROM and TWRP to flash from recovery. As long as we don't change both at once, we should always have at least one to flash the other with!
guiniol said:
Yep, not sure there's a way to get back the fastboot commands. But as long as we have TWRP, then it
s fine.
Click to expand...
Click to collapse
This thread is about getting fastboot back on the 6045:
https://forum.xda-developers.com/idol-3/development/6045-mm-hybrid-bootstack-t3436808
JoeyPPC said:
This thread is about getting fastboot back on the 6045:
https://forum.xda-developers.com/idol-3/development/6045-mm-hybrid-bootstack-t3436808
Click to expand...
Click to collapse
I did try that but couldn't boot the latest LOS14.1 with it. Others have reported success so it may be due to the exact variant.
I have realized that this version of TWRP (3.1.1) doesn´t backup EFS partition but "firmware" partition, what means backup of firmware?
Works great with 6045Y
Thanks you for your work
Hello.
I'm trying to restore a backup (for going back to stock rom coming fro LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7 rom by alecbl.).
That backup was maden with this https://forum.xda-developers.com/id...-2-r5-twrp-t3574214/post73664585#post73664585, but launching 'adb restore Backup_14052017.bak' on command line I get this message in the phone (in TWRP):
command is: 'adbrestore' and there is no value
E:Unable to find file system (first period).
E:Unable to find file system (first period).
E:Unknown restore method for '/system'
E:ADB restore failed
Done processing script file
I'm using TWRP 3.1.0-0 and I've been told to use your version.
The problem is my phone is 6039, while in your download page I see
twrp-3.1.1-idol3.img
for the Alcatel Idol 3 5.5, by FireLord
Does this mean it works only with 6045?
And do you know how I can restore that backup?
ciclolars said:
I have realized that this version of TWRP (3.1.1) doesn´t backup EFS partition but "firmware" partition, what means backup of firmware?
Click to expand...
Click to collapse
Any idea?