Database Develop

[SOLVED] Stuck on X - HELP!?

ADDING THE LINK HERE NOW : https://www.dropbox.com/s/it4ji9mlohfgagf/NexusOne-rescue-tools.zip
And please, a THANKS would be great if this helped you.
For some reason the phone one day just didn't boot. Was stuck on X logo.
We have tried alot... can't get into recovery, so flashed custom recovery, both RA and CWM... can't get into any of them, just stuck on X.
The phone was stock, and unrooted.
We managed to unlock bootloader via fastboot and root it.
Tried the PASSIMG.ZIP method - not working.
Any ideas?
.... please? =(
EDIT: Problem solved! Send me a PM if you're in the same seat, and i could send you all the files you need.
Oh, all you need is your FASTBOOT to work, no need for ADB, since it didn't work for me either.
EDIT #2:
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far (2012-02-10) 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
*** PM ME FOR THE LINK TO THE *.ZIP ***
Unzip, open an command promt, and:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
do the commands in that order, and when you are done reboot the phone
and see if it boots.
if NOT: keep on flashing ONLY the boot.img again and again until it
boots. it seems like the boot partition is corrupted and may need alot
of flashing until it works.
i think i flashed like 100 times before it booted. =)
There is also another recovery in that zip... RA's recovery. You can also try that one, no harm done!
Once you get it to boot, you will have FroYo 2.2 installed.
If you got it to boot with recovery.img just let android update to latest (2.3.7?)
If you have RA's recovery, just flash back recovery.img or you wont be able to upgrade to 2.3.7 "the stock way"

Can you boot without sd card?
Maybe Hardware--

rugmankc said:
Can you boot without sd card?
Maybe Hardware--
Click to expand...
Click to collapse
Sorry, no. Not booting when i remove sdcard either.
:/

May be hardware

rugmankc said:
May be hardware
Click to expand...
Click to collapse
How do i find out?
When we searched yesterday (google), we found some ppl who had fixed it, now i can't find those pages again..
So anyone here who knows what to try?

I've been in a similar situation before and just kept fastboot flashing system, recovery, and boot, and eventually I recovered the phone...

I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.

bassmadrigal said:
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
Click to expand...
Click to collapse
Thanks!
But we have tried to fastboot system.img, boot.img and recovery.img
Still stuck on X.
Is that code any different perhaps?
I can't try that now, that's why i ask instead of try it =)

All the commands that I posted are supposed to do is install a custom recovery and then boot into it. From recovery, you need to wipe your device by wiping the /system partition and doing a Factory Reset/Data Wipe. Then install whatever ROM you want to.
I've never tried using fastboot to install the system image, so I can't comment on that at all.

O M G!!!
i actually got the phone up and running!! everything is working now, i'm just too awesome
If anyone is interested, i could find out what i did, and which files i flashed, etc etc.

Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed

Woa, check your PM

Check you inbox buddy! Tack på förhand

mrBira said:
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Click to expand...
Click to collapse
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs

NismoDrift240 said:
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
Click to expand...
Click to collapse
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.

mrBira said:
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
Click to expand...
Click to collapse
That makes perfect sense, I'm the same way. Thanks for getting back to me, here's to hoping I make 15...

same prob.
I sent you a PM, bro. Get back to me as soon as you can! Thanks!

Nexus One recovery boot error
PM sent. Thank you for your assistance.

i would like to know how to you solve the problem

No recovery for unrooted fones
first root ur phone using passimg.img
and fastboot flash bootloard oem unlock etc
and then try to flash a recovery using
fastboot flash recovery recovery.img
then u r done
Thank if it helps u

[Q] Is Moto G safe to root?

Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yea go ahead. Its totally safe to root. No issues or bugs faced till now. Follow this thread : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
I have rooted and flashed TWRP v 2.8.0.1. I am hoping someone compiles a working CWM recovery for our device.

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.

Okay I will, thanks.
Though what's strange is the version number. I went to the official site of TWRP and the version was 2.8.0.0, but on the root thread, the version is 2.8.0.1.

Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit

marcviado said:
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.
Click to expand...
Click to collapse
Yup current TWRP v2.8 has some issues while flashing KK ROMS and taking too much time to clear cache. The device reboots automatically while taking a TWRP system backup.
We need a CWM recovery ASAP :fingers-crossed:
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
Same here.
Thanks a ton I wanted to rollback to the previous version. I didnt have the latest system backup after the OTA update.

KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
No problems with this one right?

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
v2.7 is relatively bugless as compared to v2.8

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
Nope, works as expected

Okay, I need a little help here. I flashed the old twrp via fastboot but then got the mismatched partition size error. Well I thought what the hell, and I selected recovery from the menu, but the problem is that the phone doesn't go into recovery, just reboots. What should I do?
EDIT: I also tried rebooting via recovery when the phone wasn't connected to the laptop. If i press the power button on any of the options - normal powerup, recovery, factory or barcodes - the phone switches off.
EDIT 2: I tried getting into recovery via adb, but all I get is a 'no command' message when the phone reboots. A quick google search showed me that the no command message means that the phone still has the stock recovery. It seems like twrp isn't flashing. Any ideas!?

What rom should i use? for xt1063

I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.

abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case

reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.

abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?

reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.

abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone

reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup

abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link

im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...

abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise

I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.

abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?

reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....

heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.

Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.

Stuck in Fastboot Mode / TWRP without OS

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

Softbricked my Oneplus can still use TWRP

Hey everybody,
I have a problem i kinda did stupid stuff and deleted stuff I should not have deleted my phone got ****ed and I then did a factory reset. The problem now is that I cant sideload the original Oneplus 3t otas through TWRP. Everytime I try it says ERROR: 7. I then tried the fix with removing the version check in META-INF. Now it says Zip file is corrupt. I tried installing a different twrp version and I cant do that either. How can I fix my phone?

Format /system and then try to flash zip; make sure you're using TWRP 3.2.1-0.
You can edit update-binary (or update-script) with WinRAR (if on Windows), I'm not getting errors with it.
Don't forget to make nandroid backups in the future in case you'll be going to mess with the system files

Butziboy said:
Hey everybody,
I have a problem i kinda did stupid stuff and deleted stuff I should not have deleted my phone got ****ed and I then did a factory reset. The problem now is that I cant sideload the original Oneplus 3t otas through TWRP. Everytime I try it says ERROR: 7. I then tried the fix with removing the version check in META-INF. Now it says Zip file is corrupt. I tried installing a different twrp version and I cant do that either. How can I fix my phone?
Click to expand...
Click to collapse
Try to flash the TWRP that you need for Android Oreo just google Oneplus 3T Oreo TWRP and there is a OnePlus Forum Thread where you can find the Link to the TWRP Download i can't post the Link because i'm new here . After you downloaded the Recovery and flashed it download the zip File from the Official OnePlus Website and flash itwith the new TWRP.
I did the same as you and was in a Bootloop and this worked for me.

Butziboy said:
I tried installing a different twrp version and I cant do that either.
Click to expand...
Click to collapse
You didn't state the version of TWRP you were using to begin with, or what the "different' TWRP version you then tried. Always provide these types of details, in you want the proper help.
As already mentioned, using a version TWRP that does not support Oreo, is the common reason for Error 7. Suggest you use the official TWRP version mentioned, above, or blu_spark TWRP 8.61
---------- Post added at 09:16 AM ---------- Previous post was at 09:12 AM ----------
Butziboy said:
I have a problem i kinda did stupid stuff and deleted stuff I should not have deleted my phone got ****ed and I then did a factory reset.
Click to expand...
Click to collapse
Possibly lessons already learned, but always remember (as another mentioned) make a TWRP (nandroid) backup before messing with system files, or deleting things. In fact, making a TWRP backup is one of the first things I do after (unlocking bootloader and) flashing TWRP (before root, or any other mods).
Also, don't go around deleting things in TWRP or any other method, unless you know exactly what the result is going to be, and how to backtrack if needed.
We all make stupid mistakes. The important part is learning from them.