Develop Bugs

Problems With GNex

Hi all, I have some problems on my gnex.
This happens because I think I have deleted some system files.
1st problem: when I install a rom at the first boot the phone gives me this error: "the application speech engine Google has locked in an unusual way"
2nd problem: when I open camera or gallery the phone gives me this error: "no external storage available"
3rd problem: sometimes the phone gives me the error: "youtube application has locked in an unusual way"
Ok...there are too much problems...just a question now: I want to reset ALL my gnex, I want to delete ALL the files there are in it. I can't do it flashing a new rom or formatting system from recovery. How can I do?
Thanks!

need more details
Without some more details on what ROM you are having these issues with, which recovery you're using, ... it's kind of difficult to help out... That aside, when you flash a new ROM, be sure to first do a full wipe through the recovery. I've flashed my phones numerous times over the years and every single time I had a problem at first boot it was because I didn't do the full wipe. Also, carefully read the instructions posted on the first (and second & third if any) thread, usually the dev explains carefully which steps are necessary to succeed.

Gunthy` said:
Without some more details on what ROM you are having these issues with, which recovery you're using, ... it's kind of difficult to help out... That aside, when you flash a new ROM, be sure to first do a full wipe through the recovery. I've flashed my phones numerous times over the years and every single time I had a problem at first boot it was because I didn't do the full wipe. Also, carefully read the instructions posted on the first (and second & third if any) thread, usually the dev explains carefully which steps are necessary to succeed.
Click to expand...
Click to collapse
I have these problems with all roms, recovery cwm non touch and i always do a wipe before flashing roms
Now I just want to know how to delete every file in my phone and come back to original

Frenix27 said:
I have these problems with all roms, recovery cwm non touch and i always do a wipe before flashing roms
Now I just want to know how to delete every file in my phone and come back to original
Click to expand...
Click to collapse
That's odd... Maybe something wrong with the device itself in that case... To go back to stock, the easiest way by far is the GNex Toolkit. It has an option to download the Google image & lets you easily flash it.

Gunthy` said:
That's odd... Maybe something wrong with the device itself in that case... To go back to stock, the easiest way by far is the GNex Toolkit. It has an option to download the Google image & lets you easily flash it.
Click to expand...
Click to collapse
And via gnex toolkit, with this option, all system files will be deleted?

Frenix27 said:
And via gnex toolkit, with this option, all system files will be deleted?
Click to expand...
Click to collapse
Well that depends what you mean by that... What it will do is flash the stock ROM that is made by Google onto your device. It will replace the current installed system with the stock one. It will be like when you first got the phone, with the default ICS installed. Obviously a device without a system installed on it would be useless, unless you're looking for a new expensive paper weight of course .
If you still have the same problems after that, I'd recommend returning it to the shop you got it from for a repair/refund. Don't forget to re-lock it though if you decide to go that way .

The problem is that with root explorer i see two folder about storage: sdcard and storage>sdcard0. I think i have deleted some files in these folders. Is there a way to reset their files?

/sdcard & /storage/sdcard0 both refer to the same, namely the internal memory. No way to recover deleted data though. What exactly did you delete??

Frenix27 said:
The problem is that with root explorer i see two folder about storage: sdcard and storage>sdcard0. I think i have deleted some files in these folders. Is there a way to reset their files?
Click to expand...
Click to collapse
Flashing the stock image will return all your files to factory. You don't need to delete anything.
Sent from my LGL55C using Tapatalk 2

Gunthy` said:
That's odd... Maybe something wrong with the device itself in that case... To go back to stock, the easiest way by far is the GNex Toolkit. It has an option to download the Google image & lets you easily flash it.
Click to expand...
Click to collapse
Use odin or fastboot. Kits are easier but i trust fastboot above all. And do a backup before flashing anything...tag way can restore. Then factory wipe, then format cache, then go to advanced and format dalvik, THEN flash the ROM
Android is upgrading...

JediNinjafication said:
Use odin or fastboot. Kits are easier but i trust fastboot above all. And do a backup before flashing anything...tag way can restore. Then factory wipe, then format cache, then go to advanced and format dalvik, THEN flash the ROM
Android is upgrading...
Click to expand...
Click to collapse
The toolkit uses fastboot... It just presents you with scripted menus and composes the correct command depending on your choices. Makes it a lot easier to get stuff done without having to remember all the different commands .

Are you sure? So i have to flash the stock image?

Without more info on what exactly you deleted it's hard to say. Flashing stock should work for restoring the phone though .

Gunthy` said:
The toolkit uses fastboot... It just presents you with scripted menus and composes the correct command depending on your choices. Makes it a lot easier to get stuff done without having to remember all the different commands .
Click to expand...
Click to collapse
Ahhh. I dunno, I like it. And I usually watch a qbking77 video while I do it.
Android is upgrading...

JediNinjafication said:
Ahhh. I dunno, I like it. And I usually watch a qbking77 video while I do it.
Android is upgrading...
Click to expand...
Click to collapse
Ok so the last question: i remember i had imm76i when i bought the phone. I have to flash that? Where can I find?

Just use the toolkit I linked to earlier. You can make it download the latest google stock image and flash that one.

Gunthy` said:
Just use the toolkit I linked to earlier. You can make it download the latest google stock image and flash that one.
Click to expand...
Click to collapse
ok ty

[Q] Boot loop + Blue LED Flashing on rooted device

Hey everyone so I took my phone out of my pocket and it was stuck in a boot loop. I tried taking the battery out, volume up + power + home, volume down + power + home but nothing. I've tried booting it also without a battery.
I have Quantum running on my phone, and have never had any problems. The occasional restart but now my phone won't even get to the home screen. I get just a boot loop with normal sounds, and then my LED begins to flash. Then it just loops again ..
Don't really know what to do.
UPDATE: Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.

DELETED - irrelevant information.

StoneyJSG said:
DELETED
Click to expand...
Click to collapse
Why ?

Rovon said:
Why ?
Click to expand...
Click to collapse
Will your computer detect it if connected? (Odin, Heimdall, adb)

dawgdoc said:
Will your computer detect it if connected? (Odin, Heimdall, adb)
Click to expand...
Click to collapse
Yes computer is detecting it with Odin.

Rovon said:
Yes computer is detecting it with Odin.
Click to expand...
Click to collapse
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.

dawgdoc said:
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
Click to expand...
Click to collapse
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"

Rovon said:
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
Click to expand...
Click to collapse
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.

Rovon said:
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
Click to expand...
Click to collapse
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.

jason2678 said:
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
Click to expand...
Click to collapse
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.

Rovon said:
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
Click to expand...
Click to collapse
So I keep getting a bunch of errors with TWR. I tried installing AOKP but got stuck at a boot screen again, and after trying to wipe my phone I get an error message saying "Failed". Now I'm trying install Quantum again but get an error message saying "Zip file is corrupt". T__T
Going to try another rom..
Update: I've tried Quantum again and it finally installed but now I'm stuck in a bootloop again. This is so frustrating ...

It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.

dawgdoc said:
It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
Click to expand...
Click to collapse
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything

Rovon said:
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
Click to expand...
Click to collapse
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.

dawgdoc said:
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
Click to expand...
Click to collapse
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.

Rovon said:
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
Click to expand...
Click to collapse
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.

jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"

jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
mrrocketdog said:
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Hmm .. that command didn't seem to pull anything up for me.

Rovon said:
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
Hmm .. that command didn't seem to pull anything up for me.
Click to expand...
Click to collapse
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.

jason2678 said:
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
Click to expand...
Click to collapse
Alright I'm downloading this now. Assuming this works, should I do an OTA update then root or am I safe to root the device from odin as soon as this bootloader is installed?

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
​So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
​I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.

You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.

Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.

If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?

mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.

tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?

mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.

Stuck with Twrp booting

Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!

Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".

Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse

Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?

lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?

I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.

stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs

blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.

Blank App?

I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.

@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..

NewbRooter89 said:
I have a blank App in my app drawer since I flashed my custom ROM and now they're 3 of them. When I tap on the app info it says I need a broader app to view it. I included a screenshot. Anyone know what these are?
Also, my phone keeps randomly rebooting.
Click to expand...
Click to collapse
if you flashed anything other than lineage you deserve what you are getting

flash713 said:
@newbrooster89
Looks like apps left from maybe a backup of whatever launcher you were using on your previous setup. Shows the partial icons but not the whole app because they are not installed now. That's what it appears to be. I use nova prime and, I can hold down (long press) an icon and it gives me options and one is playstore and you can select that and it takes you to play store to the app. See if you can long press and maybe select "search" or something that will take you to the app. If not just swipe em off your screen. Its nothing to be worried about. Just something from a past launcher backup/restore.
Edit/added:
Explain how you installed? What rom, what gapps package... What did you wipe in twrp recovery?
I always wipe data and system and cache unless whoever made the rom states not to in their op. (original post) Ex: Lineage 17 The dev says to only wipe data in twrp so that's what I do... otherwise I wipe data, system, cache flash rom, flash twrp installer zip reboot system. Then I boot back into twrp and install gapps and magisk zip for root and reboot system. That's my usual method for installing a rom.
I recommend a factory reset either through your phones settings or fastboot or twrp. See if that stops your reboots ..
Click to expand...
Click to collapse
I just ended up deleting everything and flashing a whole new ROM. I was on Lineage 17 but kept having so many bugs that I decided to try a different one. Thanks for the advice though.

sudoxd said:
if you flashed anything other than lineage you deserve what you are getting
Click to expand...
Click to collapse
That's what I was using and I had so many bugs and issues with it.

NewbRooter89 said:
That's what I was using and I had so many bugs and issues with it.
Click to expand...
Click to collapse
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.

flash713 said:
Then something was wrong on your end because lineage 17 is very close to being flawless. I've used it several times and always worked great for me.
Flash latest factory image & let it wipe (fastboot -w) at the end don't remove the fastboot -w in the script, if you did. I know many people do that ...
Boot twrp and Wipe data, flash lineage 17 w/gapps
Flash twrp installer (I use 3313) reboot system ...
Boot twrp, flash magisk root zip reboot system.
That's how I've always installed lineage and works great. Sounds like you had something interfering with it. Maybe residue from a past install or something but it was most definitely user error. Reflash factory image and wipe data and install it and it will be close to flawless. If not get logs and post them on lineage thread and someone there can tell you exactly what's going on. 11/30 build is not buggy.
Click to expand...
Click to collapse
you dont even need to flash the factory image, will work fine flashing from whatever they have now

sudoxd said:
you dont even need to flash the factory image, will work fine flashing from whatever they have now
Click to expand...
Click to collapse
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.

flash713 said:
That's correct you don't have to flash factory image but that's what I would do. There's always more than one way to do something.
Click to expand...
Click to collapse
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom

sudoxd said:
yes but why? just sounds like wasted time to me, our lives are short remember. that time could be spent with friends and family but no here you are flashing factory image before rom
Click to expand...
Click to collapse
But I love to flash factory image. Jkjk. ?? The reason I had initially posted that on my comment was because I thought if anything wasn't right on his setup it would square it away or if something was left from another past install on sdcard it would clear it all up. Sure a format data in twrp will do same I just thought of that as an easy thing to say that had a zero % chance of being misunderstood. And what if he was on 9.0? ? That's just how I thought at that moment when I commented that. I know Lineage 17 build for Marlin is damn near flawless. I've been using it off and on since it came out. I see you are the dev who makes that kernel. Saw your link to your work. I remember you from long ago (i used to have another user name but had my account deleted a while back) on some Nexus device everyone and their mom owned. Maybe the 5 or 5x or the Gnex idk but I remember your kernel because it was bad ass.

It probably was something on my end. This is the first phone I've rooted with the A/B slots. I also did it through adb sideload because I was having issues with TWRP. I was also stuck in a bootloop when I installed it. Maybe I'll give it another shot. I did really like having Android 10 and my battery life was much better with lineage.