Related
Help plsssssssss
lin453889100 said:
Help plsssssssss
Click to expand...
Click to collapse
I have a motor x developer ed, but after flashed a rom, i tried to reboot the system, it gets stuck at white warning page
lin453889100 said:
I have a motor x developer ed, but after flashed a rom, i tried to reboot the system, it gets stuck at white warning page
Click to expand...
Click to collapse
Reboot into recovery by turning phone off and holding down the power button and volume down for about 5 sec. Choose recovery and install backup. If you didn't make a backup (shame on you). You will have to fxz the firmware and you will have a fresh new phone but will lose ALL data including pics and music etc.
bigv5150 said:
Reboot into recovery by turning phone off and holding down the power button and volume down for about 5 sec. Choose recovery and install backup. If you didn't make a backup (shame on you). You will have to fxz the firmware and you will have a fresh new phone but will lose ALL data including pics and music etc.
Click to expand...
Click to collapse
thx for your help, can you tell me more details about fxz the firmware?
Help plsssssssssssss
HELP!!!!
http://forum.xda-developers.com/showpost.php?p=46327689&postcount=1
Or
http://forum.xda-developers.com/moto-x/development/kit-restore-moto-x-to-stock-rsd-lite-t2560571
Or
Get RSD from http://ted.servepics.com/razrm/ & the XML from http://sbf.droid-developers.org/
---------- Post added at 01:32 AM ---------- Previous post was at 01:21 AM ----------
More on RSD lite
http://forum.xda-developers.com/showthread.php?t=2176753
Did you try wiping cache and factory reset in recovery
Sent from my XT1053 using XDA Free mobile app
Follow the links suggested above. Return to stock. The same version you are on now. Don't flash a different version.
Then I suggest respectfully that you read the stickies at the top of general section and learn a bit more before attempting more flashing.
The more you learn and understand.... The easier things will be and the less trouble you will have. Also might save you from bricking your phone doing something you shouldn't.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
Also you can use fastboot to return to stock. Read this guide, and there's a return to stock section for you.
http://forum.xda-developers.com/showthread.php?t=2603358
kj2112 said:
Follow the links suggested above. Return to stock. The same version you are on now. Don't flash a different version.
Then I suggest respectfully that you read the stickies at the top of general section and learn a bit more before attempting more flashing.
The more you learn and understand.... The easier things will be and the less trouble you will have. Also might save you from bricking your phone doing something you shouldn't.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
Also you can use fastboot to return to stock. Read this guide, and there's a return to stock section for you.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
+1 I always say it's great having an unlocked phone but learn how to fix it before you screw it up. Read everything you can trust me it will make it so much easier in the long run.
Hey,
I have a Moto X Play running stock 6.0.1, no root, no twrp and with the bootloader locked. So I have unlocked it, installed twrp and super su. So when I've finished installing super su, i've rebooted the phone and it's stuck at WARNING BOOTLOADER LOCKED. OK, I guess this may be a soft brick. I can get into twrp.
Shall I for example download cyanogenmod through the pc and flash it with twrp?
Thank you
_mikelanda said:
Hey,
I have a Moto X Play running stock 6.0.1, no root, no twrp and with the bootloader locked. So I have unlocked it, installed twrp and super su. So when I've finished installing super su, i've rebooted the phone and it's stuck at WARNING BOOTLOADER LOCKED. OK, I guess this may be a soft brick. I can get into twrp.
Shall I for example download cyanogenmod through the pc and flash it with twrp?
Thank you
Click to expand...
Click to collapse
flash UPDATE-SuperSU-v2.65-20151226141550.
had the same problem and the supersu 2.65 solved it.
kamalshetty90 said:
flash UPDATE-SuperSU-v2.65-20151226141550.
had the same problem and the supersu 2.65 solved it.
Click to expand...
Click to collapse
Thanks Sir
kamalshetty90 said:
flash UPDATE-SuperSU-v2.65-20151226141550.
had the same problem and the supersu 2.65 solved it.
Click to expand...
Click to collapse
Any other ideas? I tried it but my phone still at bootloader logo.
edwart said:
Any other ideas? I tried it but my phone still at bootloader logo.
Click to expand...
Click to collapse
Last i tried the latest super user worked for me.
But now i am using moto g5s plus. Sorry if this didn't help.
Xperia sp First root, flash and... crash!
Hi all,
at last I got my first root.... Warranty was ended on my Xperia SP so I decided to give a chance to Lollipop.
Started with root (veeery smooth, towelroot and superSU), then CWM to have a good parachute, and after all, CM12 (plus googleApps and a couple more fixes found in this site).
Let's say... almost eveerything ok when I realized that a CM 12.1 was issued and wanted to give a chance to this too.
And now the real troubles started, mainly because of CWM.
The phone didn't boot anymore in recovery mode, so I even wasn't able to recover my backup, trying to reinstall CWM, the batch stated that version was unknown. So, it deleted the existing files.
I was able to reinstall them modifying a line checking version (added || IS_CM12)
This was the only way to take back my deart recovery menu.
But seems it waqsn't a good idea.... bricked. Jumping up&down the net to pick back the previous release of android via Flashtool, at last seems I found it.
Of course, as soon as restored, I'll try again, nut I think that there's a basilar problem: CMW is not done to work with CM12, is it? And if so, which other solutions will I have, should I need again a recover or a new version?
Thank you all for reading till here
Cheers
Raff
Use TWRP from now on no matter what ROM you use.
Install Rashr from here: https://mega.nz/#!lxVHjBZR!24FtZk7h8vp07TML489hujJsTYOzUzGWXLoDwWlEHMw
Then flash recovery from here: http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230
I prefer philz touch
So both of you prefer other than CWM? Just askling since almost all update tutorials moention CWM as the first option...
Thank you!
Actually yeah!
and CWM is outdated, it can be used with JB/KK I guess, but almost all Lollipop devs recommend using TWRP/Philz.
Bootloader unlocked?
How could I check if bootloader is already unlocked since it's one of the prereqs for TWRP?
I verified that unlock is allowed, but before going ahead asking Sony the code, maybe it's useless? It's already rooted...
Thanks guys!
Raf3000 said:
How could I check if bootloader is already unlocked since it's one of the prereqs for TWRP?
I verified that unlock is allowed, but before going ahead asking Sony the code, maybe it's useless? It's already rooted...
Thanks guys!
Click to expand...
Click to collapse
Why would it be useless?
Go ahead and ask for the code,
and it should say something like "Bootloader unlocked: Yes" or "Bootloader Unlock: Done" on the service menu after you unlock it.
and don't forget to backup TA Partition before Unlocking.
Zenith said:
Why would it be useless?
Click to expand...
Click to collapse
I'm sorry, I didn't explain, I mean IF the phone is already unlocked it's useless asking the code.
From service menu -> configuration -> rooting status I have Bootolader Unlock allowed: yes
and don't forget to backup TA Partition before Unlocking.
Click to expand...
Click to collapse
Ok... How could I backup it if I still don't have TWRP installed?
Sorry if silly questions...
Thanks
"Bootloader Unlock allowed: yes" means that your bootloader is still locked, and you can unlock it if you want.
..and about TA Backup, read this thread: http://forum.xda-developers.com/showthread.php?t=2292598
and it's okay, everyone is a noob at the beginning
Hit thanks if I helped!
I did it!
Great! Unlocked and TA backupped. Now, TWRP.
Now, I know, I'm going to be boring... to be honest I'd like the graphics of Sony, but I'd like to upgrade to 5 too, so, I could proceed with CM12.1, and I'll have 5.1.1 but not "Sony style", or I could try smthg like customized ROM (don't remember the name, should retrieve my browsing history) based on CM12.1 but keeping Xperia Z series style...
What's your advice?
Thanks a lot
uhm... no... no TWRP...
rashr says that flash went ok, but when I ask to restart in recovery, it rtats as usual. And I can't see TWRP logo in the home page of rashr...
If you want Xperia styled appearance and a stable ROM,
Try any CM12.1 based ROM like AICP and use Xperia Z4 Theme
or 'StryFlex' if you want Sony's Official Xperia Lollipop UI, but it's not 100% stable yet, so I'd suggest you to use AICP.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
Raf3000 said:
uhm... no... no TWRP...
rashr says that flash went ok, but when I ask to restart in recovery, it rtats as usual. And I can't see TWRP logo in the home page of rashr...
Click to expand...
Click to collapse
did you install Rashr from playstore? or from the link I posted?
Zenith said:
If you want Xperia styled appearance and a stable ROM,
Try any CM12.1 based ROM like AICP and use Xperia Z4 Theme
or 'StryFlex' if you want Sony's Official Xperia Lollipop UI, but it's not 100% stable yet, so I'd suggest you to use AICP.
Click to expand...
Click to collapse
I agree, I prefer more stable so I think I'll go with the first option
did you install Rashr from playstore? or from the link I posted?
Click to expand...
Click to collapse
Actually, no, I used playstore. Removed and installed the link's one. Flash took some seconds more, it seemed a real flash, but at reboot notihing changed, non recovery boot.
But... I can see a fraction of second before the logo Sony a kind of menu, I can imagine it's TWRP, but I don't understand why it doesn't stop there...
Raf3000 said:
I agree, I prefer more stable so I think I'll go with the first option
Actually, no, I used playstore. Removed and installed the link's one. Flash took some seconds more, it seemed a real flash, but at reboot notihing changed, non recovery boot.
But... I can see a fraction of second before the logo Sony a kind of menu, I can imagine it's TWRP, but I don't understand why it doesn't stop there...
Click to expand...
Click to collapse
When you see the sony logo, or watch the LED light up, press volume down button to Enter TWRP.
and try a few times if you can't get into it the first time.
Zenith said:
When you see the sony logo, or watch the LED light up, press volume down button to Enter TWRP.
and try a few times if you can't get into it the first time.
Click to expand...
Click to collapse
Ok, I'll try, strange is that I donwloaded "quick boot" exactly to avoid this rush against the time, and reboot in recovery mode has this behaviour. I'll try in simple way now.
Raf3000 said:
Ok, I'll try, strange is that I donwloaded "quick boot" exactly to avoid this rush against the time, and reboot in recovery mode has this behaviour. I'll try in simple way now.
Click to expand...
Click to collapse
Whichever suits you
Do a full wipe and flash tangerine after flashing the ROM,
Don't reboot before flashing tangerine as you'll be stuck with the Cyanogen recovery.
Zenith said:
Whichever suits you
Do a full wipe and flash tangerine after flashing the ROM,
Don't reboot before flashing tangerine as you'll be stuck with the Cyanogen recovery.
Click to expand...
Click to collapse
Nope... I'm still stuck at recovery point, I cannot access, I can't stop the boot... i hate it!!
You're stuck in a bootloop?
---------- Post added at 02:12 AM ---------- Previous post was at 02:02 AM ----------
Raf3000 said:
Nope... I'm still stuck at recovery point, I cannot access, I can't stop the boot... i hate it!!
Click to expand...
Click to collapse
If you're stuck in a bootloop, then turn off your phone (using the button on the back)
Download and flash this via 'fastboot mode' on Flashtool,
Your phone won't boot, but you'll be able to get in recovery by pressing the vol down.
and if your phone doesn't have much charge left, then leave it on charge for sometime after flashing the .elf file.
Nono thank's God.
I'm stuck because I can't update, since I have no chance to access the recovery menu: it brings me directly to original phone. No Rashr (store or linked), no dd ... nothing seems to work for recovery. I'm afraid that if I'll execute the batch for CWM_SP_4.4.1 it will work, but I'll be again at the very bad point of 2 days ago after flashed...
Raf3000 said:
Nono thank's God.
I'm stuck because I can't update, since I have no chance to access the recovery menu: it brings me directly to original phone. No Rashr (store or linked), no dd ... nothing seems to work for recovery. I'm afraid that if I'll execute the batch for CWM_SP_4.4.1 it will work, but I'll be again at the very bad point of 2 days ago after flashed...
Click to expand...
Click to collapse
That will work too, and I think that will be easier for you to install and enter recovery.
Install that, reboot, press vol. down button when you see the fourth light (probably blue).
I was trying to fix my google play "no connection error" but it didn't work so i just reset my phone as a last resort to try and fix this problem. It restarted in recovery mode i thought this was just a procedure and i just hit reboot -> system. it rebooted again into recovery mode i checked if there were any wtuck volume rockers but there aren't any help?
(FYI: one plus 3T: Rooted)
(FYI: link to what i used to try and fix my google play store:https: //forum.xda-developers.com/showthread.php?t=2273994)
What recovery are you running? Stock or TWRP?
bealer said:
What recovery are you running? Stock or TWRP?
Click to expand...
Click to collapse
TWRP
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
bealer said:
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
Click to expand...
Click to collapse
already did that but still brings me back into TWRP
TrappleV3 said:
already did that but still brings me back into TWRP
Click to expand...
Click to collapse
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Droid-2 said:
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Click to expand...
Click to collapse
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
TrappleV3 said:
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
mximer said:
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Thank You.
Issue has been resolved. OP is my little cousin who's been messing around a bit too frantically [emoji14]
I restored his device with the unbrick tool by Haris K., all's peachy again. There are still some issues with TWRP for 3T, doesn't run nearly as smooth as on the OPO. It completely failed to restore any working system (both from backup or from reflashing). Sideloading seemingly worked, but rebooted to recovery again, adb push only resulted in errors. Are there any tweaked TWRP releases that can do better?
Cooked with Resurrected bacon!
Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.
elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.
Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.
elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.
I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method
houston we have a problem...
5 bucks for any good idea!
I have an old xt1068 (titan) that after an (official) update it becames a small brick... (it was stock, no modded bootloader or whatevere, just stock!)
today I decided to give it a chance but then only thing I reach is the bootloader
whatever thing (official retail firmware) I try to flash it doesn't work...
so I unlocked the bootloader with success to give a try a custom rom but suddenly I get a issue...
I can't install latest twrp (I tried also a couple of older ones), I can only boot trough (latest) twrp but whatever rom I install I get error7
I noticed that when it reboots the content (/sdcard /data and /system) is untouched even if from shell I can remount rw... it seems that I can delete but in reality I don't delete anything
I tried almost everything... if I try to re-stock upon reboot I reach the dead android robot
the device is an xt1068, bootloader 48.87 (30.06.2016), unlocked (status code 3)
any (good) ideas?
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
HiR3x said:
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
Click to expand...
Click to collapse
no way... I tried but nothing changes... it seems that partitions are read-only
anyway I'm not able to flash twrp (no error it just doesn't install), I can only boot twrp but again nothing changes, I tried soon after booting twrp to gain root trought supersu/magisk, all works without error but upon reboot partitions aren't touched at all
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
I am glad to hear that it helped you to resolve your problem
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
mandar91 said:
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
Click to expand...
Click to collapse
Already commented a liked.
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
How come!
How can it happen. It is Moto G 2?
suiller said:
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
Click to expand...
Click to collapse
ni6hant said:
How can it happen. It is Moto G 2?
Click to expand...
Click to collapse
this is what I see from bootloader...