Develop Bugs

[Q]How to flash 1.29.401.11 after having installed CWM? [Solved]

EDIT: What the frick! -.- I fond the answer only seconds after posting this in a thread labeled something entirely different. Oh well. For anyone else looking for the answer to this, my below assumption is correct, aside from having to lock the bootloader again.
More detailed description in this thread.
Original post below:
--------------------
Right, so I rooted and installed CWM on my phone to get rid of that incessantly annoying menu-bar. However, only days after, HTC decided that they'd release an OTA to fix a number of things (internal storage space, for one).
Now, if I've understood this right, there is absolutely no way for me to install the OTA, since I've completely replaced the stock recovery. So what I've gathered from different threads, guides and god knows, is this:
- I need to fastboot write the old recovery back
- Lock my bootloader
- Let the phone update
- Unlock
- Install CWM again
Am I correct? For I am assuming that it's not simply as easy as to flash the new RUU ROM with CWM, since CWM can't access radio, for instance.

MoonshineFox said:
EDIT: What the frick! -.- I fond the answer only seconds after posting this in a thread labeled something entirely different. Oh well. For anyone else looking for the answer to this, my below assumption is correct, aside from having to lock the bootloader again.
More detailed description in this thread.
Original post below:
--------------------
Right, so I rooted and installed CWM on my phone to get rid of that incessantly annoying menu-bar. However, only days after, HTC decided that they'd release an OTA to fix a number of things (internal storage space, for one).
Now, if I've understood this right, there is absolutely no way for me to install the OTA, since I've completely replaced the stock recovery. So what I've gathered from different threads, guides and god knows, is this:
- I need to fastboot write the old recovery back
- Lock my bootloader
- Let the phone update
- Unlock
- Install CWM again
Am I correct? For I am assuming that it's not simply as easy as to flash the new RUU ROM with CWM, since CWM can't access radio, for instance.
Click to expand...
Click to collapse
Where to find the old stock recovery back?

phonixloo said:
Where to find the old stock recovery back?
Click to expand...
Click to collapse
You'll find it in the thread I linked.

Or if you want,
1. Do a CWM backup
2. Relock
3. Perform RUU install
4. Unlock
5. Install CWM
6. Restore CWM backup
7 (optional). wipe cache and Dalvik cache
I use this method as your OTA method means losing root and CWM as Unlocking it after the OTA will erase your data partitions.

jonshipman said:
Or if you want,
1. Do a CWM backup
2. Relock
3. Perform RUU install
4. Unlock
5. Install CWM
6. Restore CWM backup
7 (optional). wipe cache and Dalvik cache
I use this method as your OTA method means losing root and CWM as Unlocking it after the OTA will erase your data partitions.
Click to expand...
Click to collapse
Yeah, I didn't actually need to lock the bootloader. It wasn't necessary. Flash old recovery, install OTA, reflash CWM, make sure root works, if not, reflash SU.
I ended up having to factory reset on the unlock again. Bad move

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

Trying to get back into ROMs, need assistance on flashing, unlocking, & rooting

So I use to be familiar with flashing, unlocking, & rooting my Droid 2 Global, & my Nexus 7. And while I did successfully temp-root my note 4 a while ago, I have since fallen out of the whole procedure and have a plain old stock 'n locked note 4 that I would like to Flash EmotionOS on it.
I remember bits and pieces, but not the correct order and how exactly I flash a ROM to my note 4, would anyone be able to give me a few pointers on what order I need to do what in, and possibly what the best method(s) would be so that I can flash EmotionOS onto my note 4?
I am using this XDA guide as my current reference for EmotionOS
Thank you in advance

ChapDaddy65 said:
So I use to be familiar with flashing, unlocking, & rooting my Droid 2 Global, & my Nexus 7. And while I did successfully temp-root my note 4 a while ago, I have since fallen out of the whole procedure and have a plain old stock 'n locked note 4 that I would like to Flash EmotionOS on it.
I remember bits and pieces, but not the correct order and how exactly I flash a ROM to my note 4, would anyone be able to give me a few pointers on what order I need to do what in, and possibly what the best method(s) would be so that I can flash EmotionOS onto my note 4?
I am using this XDA guide as my current reference for EmotionOS
Thank you in advance
Click to expand...
Click to collapse
First, you'll need to root your device on stock 5.1.1 BPA1, this guide is fairly easy to follow. Then you'll need to upgrade to 6.0.1 CPD1 and root that too, using this guide. Then you'll need to flash the partial CPJ2 firmware also found here, before you can then flash EmotionOS.

Rooting the note 4 is a lot more work. I loved my note 3 and being able to do it with an app. "Towelroot" it made life so simple. Lol.
Sent from my SM-N910V using Tapatalk

quinciebee said:
First, you'll need to root your device on stock 5.1.1 BPA1, this guide is fairly easy to follow. Then you'll need to upgrade to 6.0.1 CPD1 and root that too, using this guide. Then you'll need to flash the partial CPJ2 firmware also found here, before you can then flash EmotionOS.
Click to expand...
Click to collapse
I'm on 5.0.1
Looks like I need to update..
Its just so time consuming its a daunting task.
I'm happy for now but may take a peek at emotion.
Nope, I'm not signing up for issues. The first page talks of re boots, no SMS service, no phone service I'll stick with the sure thing my phone is working I'll be at sometimes laggy but that's probably an overload issue with my apps
Sent from my SM-N910V using Tapatalk

quinciebee said:
First, you'll need to root your device on stock 5.1.1 BPA1, this guide is fairly easy to follow. Then you'll need to upgrade to 6.0.1 CPD1 and root that too, using this guide. Then you'll need to flash the partial CPJ2 firmware also found here, before you can then flash EmotionOS.
Click to expand...
Click to collapse
If I'm already on 6.0.1 stock, do I still need to downgrade & root to 5.1.1, just to upgrade back to 6.0.1 & root?

ChapDaddy65 said:
If I'm already on 6.0.1 stock, do I still need to downgrade & root to 5.1.1, just to upgrade back to 6.0.1 & root?
Click to expand...
Click to collapse
Yes you do.

ChapDaddy65 said:
If I'm already on 6.0.1 stock, do I still need to downgrade & root to 5.1.1, just to upgrade back to 6.0.1 & root?
Click to expand...
Click to collapse
That's exactly what you need to do, it's tedious, I know, but very worth it

ok, so I was able to load 5.1.1, root w/KingoRoot, enable dev mode, install TWRP 3.0.2, & reload 5.1.1, but now I'm stuck in a bootloop.
when I first loaded 5.1.1 stock w/o TWRP, I was able to get out of the bootloop by wiping the system and cache and it loaded fine, but now when I try to wipe the cache with TWRP it gets stuck in the bootloop.
How do I get out of the loop with TWRP?

ChapDaddy65 said:
ok, so I was able to load 5.1.1, root w/KingoRoot, enable dev mode, install TWRP 3.0.2, & reload 5.1.1, but now I'm stuck in a bootloop.
when I first loaded 5.1.1 stock w/o TWRP, I was able to get out of the bootloop by wiping the system and cache and it loaded fine, but now when I try to wipe the cache with TWRP it gets stuck in the bootloop.
How do I get out of the loop with TWRP?
Click to expand...
Click to collapse
Pull the battery and SD card, wait for like 30 seconds, then put only the battery back in. Boot into TWRP, pop the SD card back in, use the Advanced Wipe to wipe the SD card and cache, then reboot. If you don't want to wipe your SD, then don't put it back in.

quinciebee said:
Pull the battery and SD card, wait for like 30 seconds, then put only the battery back in. Boot into TWRP, pop the SD card back in, use the Advanced Wipe to wipe the SD card and cache, then reboot. If you don't want to wipe your SD, then don't put it back in.
Click to expand...
Click to collapse
just did all that, and still looping

ChapDaddy65 said:
just did all that, and still looping
Click to expand...
Click to collapse
Follow this guide, beginning at Phase 4.

okay, I think I may have lost root after the 5.1.1 reload, in that case I'll start over.
Is there a simple way to get the recovery.tar file so I can remove TWRP, or is there an alternative method without having to remove TWRP?

ChapDaddy65 said:
okay, I think I may have lost root after the 5.1.1 reload, in that case I'll start over.
Is there a simple way to get the recovery.tar file so I can remove TWRP, or is there an alternative method without having to remove TWRP?
Click to expand...
Click to collapse
Flashing the systemonlyN910V-5.1.1.tar should help you keep TWRP.

quinciebee said:
Flashing the systemonlyN910V-5.1.1.tar should help you keep TWRP.
Click to expand...
Click to collapse
well currently TWRP is what is preventing me from booting the phone, I didnt know if there was an alternate method to "re-doing" the guide without having to start from the very beginning. So long as I have TWRP installed, I can't seem to progress past the second bootloop.
Also Kies 3 is telling me it no longer supports the note 4 because of SmartSwitch (which is not currently installed on my PC) being capable of managing my note 4 now. Not really a huge deal now that I'm downloading the stock 5.1.1 from SamMobile, but that notice struck me as odd that Kies wont touch my note 4, even before all this happened.

ChapDaddy65 said:
just did all that, and still looping
Click to expand...
Click to collapse
TWRP doesn't format the sd properly. Pull the sd and do a diskpart on windows to clean it

ziggy71 said:
TWRP doesn't format the sd properly. Pull the sd and do a diskpart on windows to clean it
Click to expand...
Click to collapse
I dont have anything special on my SD card currently, would it be okay to just pull the SD for the whole process?

ChapDaddy65 said:
I dont have anything special on my SD card currently, would it be okay to just pull the SD for the whole process?
Click to expand...
Click to collapse
No, you need a sd in for the bootloader unlock process. Wipe it, unlock, wipe it, unlock. And wipe it with diskpart. TWRP doesn't properly wipe the card, and will result in a bootloop.

So after multiple attempts and flashes trying to get past bootlooping at the same point, I'm going to take a break from installing emotionOS for a bit, mainly because I havent been able to use wifi now for some reason. at this point im more concerned about getting wifi back.
I've tried flashing numerous times to 5.1.1, factory reset and wiping cache, and after I get my phone back to normal, I try turning on WiFi in the settings and it stalls, it waits for about 5 minutes and then shuts back off, never actually enabling wifi. Please Advise?

Hi guys..!
I'm wondering if this thread is to help about my issue. Please, let me talk about it: I have a samsung note4 sm-n910v in soft brick condition (I think), and was trying to flash it with Odin by 3 different ways: 1- flashing stock firmware 5.0.1 (N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.tar), 2- flashing with factory binary file (COMBINATION_VZW_FA44_N910VVRU2APB1_VZW2APB1_2932719_REV00_user_mid_noship_MULTI_CERT.tar), and 3- flashing with partial firmware (N910VVRU2BOF1_PartialFirmware.tar). For by 3 ways, my phone is stuck (I can not access to call or text messages). If needs more details, please, let me know. Please, could anybody help me? I'm stuck in explained situation.
Good news update about my issue..! I did a good flashing by Odin few hours ago, just with a repair firmware file for my N910V Note4..!
If somebody has same issue or similar I think him/her could use it to resolve too. Thanks to xda user Trex888 who published the next link to download correct file for my phone: http://www.tsar3000.com/Joomla/inde...ader-csc-pit-files&catid=55:samsung&Itemid=82
Complete thread link is: https://forum.xda-developers.com/note-4/help/software-update-failed-sm910v-t3498246
P.D.: Sorry for my writed english, and thanks a lot again to Trex888..!

Help with system partition reinstall HTC M8

Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS I hope I left everything else intact..
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
mount failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
Package expects build fingerprint of htc/htc_europe/htc_m8:5.0.1./LRX22C/448934. 13:user/release-keys...
Click to expand...
Click to collapse
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
My bootloader is unlocked atm and S-on...
Is it possible to recover the os in any way?
------
After trying to flash like 5 roms flashing InsertCoin worked somehow...

Qitsch said:
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS
Click to expand...
Click to collapse
Why did you flash such an old version TWRP? That one is from about 3 years ago, and will cause lots of problems!
Couple simple rules to live by, when modding these phones:
1) Do not wipe things in TWRP willy-nilly, without knowing what they are, or what the result will be. The option to wipe "system" is in the Advance wipe section. It's called "Advanced" for a reason. That alone would have been a warning to be careful, and not mess with things, unless you know what you are doing. It also clearly says in TWRP wipe screen, that most of the time, the default wipe (cache, Dalvik/ART and data) is all you ever need. It says that for a reason.
2) Right after you install TWRP, and before messing around with anything, you should make a TWRP backup of your current stock ROM. Definitely do that, before trying to flash root, ROMs, or any other mods. That way, if anything goes wrong (or you simply screw up, and wipe system) you have a backup, that you can easily restore.
Qitsch said:
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
Click to expand...
Click to collapse
In general, you should never flash a file named "OTA" unless you know exactly what you are doing. The requirements for an OTA on this device are steep:
a) Must currently have the version number directly before the OTA number (you can't skip or flash the same number OTA)
b) Must have stock recovery installed (not TWRP)
c) Must match your version (CID, MID). Do you have the Euro version? You never stated this info.
Qitsch said:
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
Click to expand...
Click to collapse
This RUU is only for the US Developer's Edition version M8. Will not work on any other version.
Even if you had the US Dev Ed (which is unlikely) this RUU would require the firmware being flashed, before the RUU will install (thus, Error 155).
In short, it seems like you are just guessing at solutions. Not a good idea.

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.