Database Users

[Q] I need help with the latest OTA

Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Could someone help me? It's really just the constant "You have an update" that is bugging me. I don't think anything fun happens in this latest OTA. Hopefully this is the last OTA for me as I want the predicted new Nexus come December!! And it would be great to get a Nexus phone I can actually get OTA updates for without issue!!
I haven't backed my data up in a while, I probably should do that too. (Also, regaining root after a flash, anyone have a reliable method for that? And for tethering on T-Mobile.)

thehyecircus said:
Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Click to expand...
Click to collapse
In case:
a. the bootloader is unlocked and you can start Nexus 4/7 in fastboot mode
b. N4/7 is connected to a PC
c. you can get response from N4/7 with a command in a Dosbox: fastboot devices
You could flash the update manually.
Download the required factory image and the Nexus Root Toolkit (NRT) of Wugfresh.
Install NRT and extract the required factory image in a directory of your choice.
In that directory you need the files: fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll
Copy those files from the NRT.
From the extracted factory image you need the required zip file extracted from the factory image.
Example Nexus 4: image-occam-ktu84p.zip
Connect the phone to USB. Use NRT to put the phone in fastboot mode.
Open the above directory in a dosbox as administrator.
Type the required command to update.
For N4: fastboot update image-occam-ktu8p.zip
Remark 1.
After that root is gone. Reroot with the NRT of wugfresh.
Remark 2, flashing the radio.
When you extract the factory image for N4 there is also an update image for the radio.
You can flash the N4 with: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
But on my N4 the LTE tricks does not work. For LTE you need an older version of the radio image.
Remark 3.
I used this manually method to avoid the hassle of backup and restore.

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.

I upgraded to Nougat Manually and it half worked :S

So I followed a tutorial online to install Android Nougat 7.0 on my Huawei P9 lite. Once I was in TWRP I realised I was supposed to install two update files from two different .zip files. Trouble is I only had the one update on my phone at the time. I didn't want to exit TWRP at that stage because I already installed one of the update files.
When I booted my phone after the update, it all seemed to be working with 7.0 installed. Then I noticed my internet data wasn't working outside of wifi, and my bluetooth isn't turning on. The rest seems to be running fine other than those two things.
I rely a lot on bluetooth and internet on the go. I need it back, does anyone know what I could do, outside of factory reset?
Thanks

factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting

Coolyou said:
factory reset wouldn't help, you need to reflash update.zip and data_full.zip AT SAME TIME without rebooting
Click to expand...
Click to collapse
Okay, I realised that just now. Trouble is I am having trouble booting into TWRP now. I just get "your device has been unlocked and can't be trusted." with an orange web link.
For some reason my phone says in the settings that I'm still on android 4.3 although the ui and functionality is 7.0. Also, the EMUI is 2.0. I don't know how I got TWRP working before but I think there's a conflict due to it half being 7.0 so recover won't boot. I have tried loads of tutorials online but none of the rocovery.img or twrp.img files are working.

have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.

jackvdbuk said:
have the exact same problem, on android 4.3 and stuck.
from what i understand to dload a working stock rom, you need to have the correct oem info that matches the recovery stock rom. i cant flash any OEMinfo as i cant get root from revolution recovery.
no access to Data partition either.
no other recovery's to install as its the only one for nougat.
So i need help for this issue too.
Click to expand...
Click to collapse
I fixed it! It was more simple than I realised. I used the dload folder method; Placing the update.app into a folder called 'dload' on an sdcard. Then holding power, both volume buttons to initiate the update.
Thanks for your help guys!!

HELP! No wifi! :(

So basically I unrooted my device using the script that someone had uploaded on here and it worked perfectly, the only thing that didn't was the wifi modem! I have had this issue when I rooted the device but lost my steps I did to fix my xt1575. I have tried to flash files individually and researched the error and have found its because the bootloader may have been relocked but it isn't. And in developer settings OEM unlocking is ticked and USB debugging is ticked. I tried to rerun the script with same results. If anybody who has had an issue could help me that would be greatly appreciated! :good:

Reflas the erase modem1 and 2 commands and the HLOS command too. No need to flash the rest of the files. If you need more help or this is not clear enough let me know.
Sent from my SM-T715 using XDA-Developers Legacy app

The "script" you used is likely really old. The original way if rooting this device was by writing a pre-patched boot image, well, that works great until the radios change, which they have a couple times.
You can probably get this working by flashing an old modem image and firmware, but you are just getting more and more mixed up in versions.
The right way to fix this is restore your pre-root backup, or flash the matching unmodified boot image with fastboot, and then rooting properly.

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.