Database Users

Help! Softbricked N7, no OS installed

Did something very silly when trying to convert to F2FS and flash a new ROM. I managed to root my N7 and was following instructions here;
http://forum.xda-developers.com/showthread.php?t=2678140
to convert to F2FS. Only problem was, I was having a lot of trouble getting my computer to connect reliably. Sometimes it would work and sometimes it wouldn't. Anyway, I managed to push the FormatPartitions.zip and flashed it in TWRP. Stupidly, I figured I would flash the partitions zip first then push and flash the ROM and Gapps. Dumb mistake. Thinking now, I realise that I have converted the file system to F2FS without a ROM to work on it.
I can boot to either TWRP or fastboot mode, but thats about it. I have found plenty of information stating that to overcome this, I just need to flash back to stock, but the thing is, neither Windows or Wugs toolkit recognises that I have the Nexus connected. So I'm unable to push any files to my N7 to get around this.
When I'm in TWRP and I reboot, it says No OS installed. I attempted to change the file system back to EXT4 in TWRP, but that didn't seem to do anything.
Have I stuffed it compeltely? If not, how do I fix it?

Sorry about my earlier freakout. I managed to get it sorted. As is nearly always the case, it just took patience and a lot of reading.
It seems to be booting into my custom ROM (SlimKat) now, although it is taking a very long time. I'll be patient this time, hopefully all is well.

WiFi fix after restore to 5.1.1

I finally was able to fix my wifi issue. I have been unable to flash anything from my windows 10 laptop to my phone. Adb and fastboot worked fine except for the flash command? I reloaded all the drivers on numerous occasions just to make sure and also manually loaded them even thought the drivers are digitally signed and windows is happy. Still have not figured that one out yet. I tried the one step firmware batch file from http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833. I put the NON-HLOS.bin, nowarning.bin and the stock kernal, v4tk-kernel-uber-alias-V6.img in the same folder as the extracted, Auto Flash Firmware script and ran the autoflashfirmware. bat file. To my surprise it worked. I still have the unlocked bootloader warning, I can live with that, however I now have my wifi back....Yea.... Thanks to all the people who devote hours setting up tools that help noobs like myself..... History,,, tried to root 6.0 MM on new XT1575 after bootloader unlock and twrp recovery. Soft brick because I did not read enough. Restore back to 5.1.1.. Lost Wifi until now.......

panic attack stuck in twrp after ota

Guys please dont flame me i am having a pannic attack and cant think strait. i rooted and flashed twrp with moto g5 plus tool kit, then later used ex kernel, then got update ota notioce...i knew it wouldnt work but was suprised it downloaded and propt to restart..so i did thinking it would say no you cant.. instead stuck in twrp like there is no os! please help. I dont know how to reflash the stock os, my backup didnt work when i restored it, and besides that after trying to restore i ended up wipin g and formatu=ing data and looso=ing it now anyway. i am shaking help please

I have just tried to flash lineage zip and it said succesful but when rebooting it goes strait back to twrp, have i lost my boot img ? what can i possiblu do, i am concerned if i download the 1.6 gig stock rom file from g5 plus kits "factory rom kit" it wont be the propper rom for my region "australia" or wont even have a modem..what can i do.. god why dont i stillhave any xanax

when trying to flash stock rom with toolkit the log says bootloader slot suffix not found and bad key

So i finally drank enough scotch to calm down, and realized the "errors" were not actually preventing the stock rom from flashing... and i now have not only a working rom but a baseband..so my reccomendation goes out to anyone panicked to just flash the downloaded stock rom found in the links of the moto g5 plus toolkit

Never,take otas with custom recovery , the solution is flash whole rom

djzero86 said:
Never,take otas with custom recovery , the solution is flash whole rom
Click to expand...
Click to collapse
Yes.. I truly thought there would be a "wah wah wah" notice being rooted.. But it went straight in to it. Just didn't know where any stock rocks were and wasn't prepared.. And ended in a hyperventilating mess. At least I now have the files

Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...

djzero86 said:
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
Click to expand...
Click to collapse
true! My last phone I felt secure and that it was completely unbrickable all because I had all the necessary rescue files and backups. And I had learned from every previous disaster. Thank you for your kind words friend.

Can't get fastboot to recognize device
So I'm kind of in the same boat as you were. I unlocked the bootlader and rooted the phone before giving it to my wife. During that whole process, fastboot had no problems recognizing the phone (obviously). Then my wife tried to update via the OTA which got her stuck in TWRP. I'd like to reflash the stock ROM, but the problem I have is that TWRP won't just flash the zip file ("invalid zip file format"), and I can't use fastboot to do commands line by line since "fastboot devices" doesn't show my phone anymore. I was able to get her going on a custom ROM for now, but I'd like to put her back on the stock ROM so we won't encounter this problem again. I've reinstalled the Motorola driver several times, but no luck. ADB has no problems recognizing the phone when in TWRP recovery. One thing that happened recently was a big update to Windows 10, but I'm not sure if that is the reason for my fastboot issues.
Any advice would be appreciated.

Just a follow up, I tried uninstalling/reinstalling the Motorola driver and ADB on the original computer, but for some reason it still won't "see" the phone in fastboot. I was able to install ADB/Fastboot and the Motorola driver on a separate computer (also Windows 10) to get fastboot to recognize the phone so I could issue commands to reinstall the stock firmware. I noticed, though, that the following commands FAILED when I entered them:
fastboot erase customize
fastboot erase clogo
I'm not sure what those were for, but the phone seems to be working fine on the stock firmware now.

Stuck in Bootloop no OS, please help.

Hi guys,
I have been reading similar threads and trying to find a solution but could not find what could help and ran into other issues. Hope someone can help me fix this.
I was trying to flash a custom ROM. had the device unlocked and installed twrp using adb.
It was a mistake to not back up. I tried to flash the firmware + extendedUI rom + magisk. Only magisk gave some error.
tried to reboot and got stuck in bootloop. Entered Twrp tried to do it again so wiped data,system,cache and then realised my folder with the rom disapeared. So now no OS and not sure what to do.
I was trying to use adb sideload to push the new zips on the device but the sideload just disconnects at 8% Understood that might drivers might be at fault. . Been trying to find and update drivers and might have done some mistakes there, as chose to update unknown device automatically with device manager and now it disappeared as well.
I read about recovering with Miflashtool but got confused whether thats the right way.
I would prefer to install a custom rom like the ExtendedUI or AOSPextended.

FuzzEdgar said:
Hi guys,
I have been reading similar threads and trying to find a solution but could not find what could help and ran into other issues. Hope someone can help me fix this.
I was trying to flash a custom ROM. had the device unlocked and installed twrp using adb.
It was a mistake to not back up. I tried to flash the firmware + extendedUI rom + magisk. Only magisk gave some error.
tried to reboot and got stuck in bootloop. Entered Twrp tried to do it again so wiped data,system,cache and then realised my folder with the rom disapeared. So now no OS and not sure what to do.
I was trying to use adb sideload to push the new zips on the device but the sideload just disconnects at 8% Understood that might drivers might be at fault. . Been trying to find and update drivers and might have done some mistakes there, as chose to update unknown device automatically with device manager and now it disappeared as well.
I read about recovering with Miflashtool but got confused whether thats the right way.
I would prefer to install a custom rom like the ExtendedUI or AOSPextended.
Click to expand...
Click to collapse
The zip files are to big to push them through adb sideload.
Just connect the cellphone to the pc while in twrp and mount otg

Soft brick on oneplus 6T after version upgrade from Lineage OS

Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.

Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?

state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.

Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback

Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?

Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.

Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help

once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.

zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.

I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?

zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device

How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help

zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?