Database Info

[SOLVED]Stuck on JB samsung logo and CWM logo

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Been running the deodexed UCMC1 with stock kernel until i got my replacement batteries today.
Turns out they had a different model # (EB585157VK, SERIAL AAaD702QS/5-B 2013.07.02) and were slightly thinner then the stock battery (the seller had a skyrocket one pictured on ebay).
Anyway they seem like legit OEM.
I get all stupid and exited to have new batteries and instead of powering off the phone from the menu i just pull out the stock battery and insert the new one. :highfive: (cynical mental highfive)
Phone is now stuck at above samsung logo and cwm only goes as far as the logo and version number, no menu no nothing.
I've read about the same problem someone had with an S3 mini here.
Will odin help me?

Maybe, have you pulled the battery, let it sit for a few minutes and put the old battery in?
Edit, this might be of interest http://forum.xda-developers.com/showthread.php?p=42749682

jd1639 said:
Maybe, have you pulled the battery, let it sit for a few minutes and put the old battery in?
Edit, this might be of interest http://forum.xda-developers.com/showthread.php?p=42749682
Click to expand...
Click to collapse
Yes, it didn't help.
I've tried flashing the Rogers JB rom and an old CWM in odin.
The old CWM worked but doesn't find the internal SD. When I mount the USB from CWM to PC the internal SD is shown in windows explorer but it's grayed out while the external SD is accesible like it is in CWM.
I tried flashing CWM touch 6.0.3.3 from inside old CWM and it flashed fine but it stops booting at the CWM logo again..
The Rogers rom flashes the glowing samsung logo and the screen turns black..

lingowistico said:
Yes, it didn't help.
I've tried flashing the Rogers JB rom and an old CWM in odin.
The old CWM worked but doesn't find the internal SD. When I mount the USB from CWM to PC the internal SD is shown in windows explorer but it's grayed out while the external SD is accesible like it is in CWM.
I tried flashing CWM touch 6.0.3.3 from inside old CWM and it flashed fine but it stops booting at the CWM logo again..
The Rogers rom flashes the glowing samsung logo and the screen turns black..
Click to expand...
Click to collapse
Mohan had a zip that restored the pre-load partition. You might give that a try.

all this because you pulled out battery while phone was on, sh*t, ive done it many times w/out issues but wont be doing it anymore
did you try booting with the old battery
when you flashed firmware w/odin did you reset/wipe b4 booting into rom
try flashing twrp w/odin then reset/wipe b4 booting into rom

jd1639 said:
Mohan had a zip that restored the pre-load partition. You might give that a try.
Click to expand...
Click to collapse
Thanks i will. Do you know if it's possible to swap the internal sd for another one?

vincom said:
all this because you pulled out battery while phone was on, sh*t, ive done it many times w/out issues but wont be doing it anymore
did you try booting with the old battery
when you flashed firmware w/odin did you reset/wipe b4 booting into rom
try flashing twrp w/odin then reset/wipe b4 booting into rom
Click to expand...
Click to collapse
Old battery didn't help.. After odin I didn't wipe b4 boot :silly:
I'll try TWRP too.

lingowistico said:
Thanks i will. Do you know if it's possible to swap the internal sd for another one?
Click to expand...
Click to collapse
Afaik, the internal is soldered on.

jd1639 said:
Afaik, the internal is soldered on.
Click to expand...
Click to collapse
It's fine though, old CWM 5xxx shows install zip from SD and install zip from internal SD and it's the opposite in new CWM. So it turns out SD is fine, phew Problem is i think it looks for backups only on external so i can't access my backup.
mohans preload fixer didn't help.
I'll try TWRP now.

Wipe in old CWM didn't help but it did in TWRP!!! Thank you Vincom i bow to you in gratitude. :highfive::laugh:
It said it couldn't find E:\android..but formatting went fine.
Booted up to Rogers JB but gallery and phone crashes in background of welcome wizard.
But i flashed the preload fix in between all of this.. so it was probably because of that.
Flashed Rogers JB from Odin again and now it works!
Next time I will turn phone

Good to hear you got it working again

lingowistico said:
Wipe in old CWM didn't help but it did in TWRP!!! Thank you Vincom i bow to you in gratitude. :highfive::laugh:
It said it couldn't find E:\android..but formatting went fine.
Booted up to Rogers JB but gallery and phone crashes in background of welcome wizard.
But i flashed the preload fix in between all of this.. so it was probably because of that.
Flashed Rogers JB from Odin again and now it works!
Next time I will turn phone
Click to expand...
Click to collapse
when flashing stock and having boot up problems and such, resetting and wiping the caches with stock recovery usually solves it 99% of the time

[MOD][TEST] ART WhatsApp Fix 4.4

I happened on this post whilst trying to get some SystemUI.apk mods to take on ART:
http://forum.xda-developers.com/showthread.php?p=47604251#post47604251
I tried the modified libart.so file by @cernekee on my Moto X VZW Dev Ed (because a working phone needs to be broken fixed) and it seems to work. I've made a flashable file to remove the leftover WhatsApp parts and flash the new libart.so if you'd like to give it a go.
Steps to install:
1. Switch to ART. (You need to have stock SystemUI.apk and SystemUI.odex - see attached).
2. Flash zip in recovery
3. DO NOT WIPE DALVIK/CACHE
4. Reboot and profit reinstall WhatsApp from Play Store if needed.
As usual, make a backup first and please don't flash this if you are uncomfortable fixing a bootlooped phone!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you screw up and wipe dalvik/cache, just flash the stock libart.so zip (attached) reboot then reflash the Mod.

Will this work on the brazilian firmware?

No clue. But this is a Nexus 5 libart.so and it's working on a Vzw Moto X so it most likely should. This isn't something I'd try with a locked bootloader though.

Just tried here and it's working perfeclty! Thank you!
I didn't even have to reinstall Whatsapp.
One question though: what happens if I try to wipe cache one day? Will it bootloop the phone?

MaKTaiL said:
Just tried here and it's working perfeclty! Thank you!
I didn't even have to reinstall Whatsapp.
One question though: what happens if I try to wipe cache one day? Will it bootloop the phone?
Click to expand...
Click to collapse
Yes but the fix is easy:
Hold power button (shut off) > boot to fastboot > boot to recovery > flash the stock libart.so > reboot > flash nexus 5 libart.so > reboot.
It has happened to me once so far lol.

question
i dont understand what do i have to flash , moto x libart, moto x stock libart , o systm ui odex ... can i help me a bit plx

bastianvy said:
i dont understand what do i have to flash , moto x libart, moto x stock libart , o systm ui odex ... can i help me a bit plx
Click to expand...
Click to collapse
Do you have root and custom recovery?

chaoslimits said:
Do you have root and custom recovery?
Click to expand...
Click to collapse
yes i do

bastianvy said:
yes i do
Click to expand...
Click to collapse
OK.
Make a backup of your phone.
Download all 3 zip files.
Enable ART if you have not done so already
Reboot and let Android optimize itself. Whatsapp should crash at this point.
Reboot into recovery and Flash Moto X_ART_Libart.so.zip
Do NOT wipe cache/dalvik and reboot.:fingers-crossed:
If your phone boots fine, launch Whatsapp. :victory:
If your phone boots but you have no status or notification bar, flash SystemUI_VZW_Odex_Stock.zip; a mod is breaking SystemUI.apk.
If your phone does not boot (most likely because you wiped cache/dalvik), shut it down (hold power button). Then boot into recovery via fastboot and flash Moto X_ART_Libart_Stock.so.zip.

chaoslimits said:
OK.
Make a backup of your phone.
Download all 3 zip files.
Enable ART if you have not done so already
Reboot and let Android optimize itself. Whatsapp should crash at this point.
Reboot into recovery and Flash Moto X_ART_Libart.so.zip
Do NOT wipe cache/dalvik and reboot.:fingers-crossed:
If your phone boots fine, launch Whatsapp. :victory:
If your phone boots but you have no status or notification bar, flash SystemUI_VZW_Odex_Stock.zip; a mod is breaking SystemUI.apk.
If your phone does not boot (most likely because you wiped cache/dalvik), shut it down (hold power button). Then boot into recovery via fastboot and flash Moto X_ART_Libart_Stock.so.zip.
Click to expand...
Click to collapse
thanks ^^, i will let u know how it goes to me, (sorry for my bad english)

is there a whatsapp fix for ART without flashing this file via recovery?
i've only root permissions on my 4.4 AT&T

P910iii said:
is there a whatsapp fix for ART without flashing this file via recovery?
i've only root permissions on my 4.4 AT&T
Click to expand...
Click to collapse
I would strongly advise against touching anything in /system/lib without having a backup via recovery. Don't do it.
Edit: It's especially dangerous if you mistakenly wipe dalvik/cache.

Thank you, i'll wait 4.4.2

Is there any way to flash this on a stock recovery or by any other means? I have 4.4 with stock recovery, SlapMyMoto root and MotoWPNoMo.

dicarli said:
Is there any way to flash this on a stock recovery or by any other means? I have 4.4 with stock recovery, SlapMyMoto root and MotoWPNoMo.
Click to expand...
Click to collapse
The new version of Whatsapp supports ART i guess.... Try it once...

Soft-- Bricked after Phone Died, Please Help.

Ive looked through all the bricked threads and elsewhere and nothing seems to match my problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
S-off. As you can see its been awhile since I have messed with my phone so forgive me. I found something that had what I needed and was stable(until now) and stuck with it.
So I connected my phone to a friends charger and it wasnt charging and it died. I got it charged and booted it up and it ran fine for about 2 minutes then apps started stopping and it rebooted, it now does this over and over. I tried the battery reset. The last apps to crash are always google play services related so I tried to flash a gaaps zip in hboot.I tried uninstalling/deleting those apps, it still crashes. I tried to wipe and restore/install in twrp recovery(which it usually says is successful). Ive tried flashing RUUs in hboot they stop after the first reboot and boot normally instead of back to hboot. It wont connect to adb(I may have done something wrong there). But whatever I do it boots up exactly how it was before. If I delete/uninstall anything it comes back, if I add something anywhere other than the external sd it disappears.
Please help I cant afford a new phone right now.
Update: Without an sd card in the phone it wont reboot but all other things are the same, apps still crash, still cant do anything to recover.
Update: I tried another sd card and it prevents the reboot, but still wont flash anything in the bootloader.
Update: I formatted my sd card and it doesn't reboot with it in now, atleast not automatically, it reboots when certain apps are opened or randomly after a long period. Apps still crash and still no luck with any flashing or recovery. I tried clearing all app caches with titanium, no change.
I think the internal and system partitions may be corrupted and stuck as is after reboot, the weird thing is I can delete things or add things and the changes stay until reboot, then its back to its original state, is that possible?

Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x

piyushkohli97 said:
Did you rename the RUU file to OP6BIMG.zip before placing it in sd card? And since you are s on u should use the RUU from this thread - http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
And if u think there is a problem with partitions download a 4.4.x ruu flash it on ur phone then boot into recovery and reset all data in phone. Remember in stock recovery u need to press vol and mayb power at same time(just press dont hold them to long).
You can flash the recovery from bootloader also, but remember it should be 4.4.x
Click to expand...
Click to collapse
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.

Kane5581 said:
Im s-off usinf twrp 2.7 something. Ruu flash starts but at first reboot it just boots normally instead of back to the bootloader. I've flashed roms, ruus, nandroids, from both the bootloader and recovery nothing sticks. The phonereboots to identical to how it was dec6 no matter what I do, flashes, wipes, installs, deletions, everything goes back how it was after reboot.
Click to expand...
Click to collapse
So u keep the ruu or flash some ROM after that?
Have you tried different RUUs?
I also recommend flashing the firmware for whichever Android version you are using.
Try firmware from this link http://forum.xda-developers.com/verizon-htc-one-m8/development/wip-4-17-605-9-stock-resources-firmware-t3196906
Flash firmware after RUU flashing.
I recommend the latest ruu if you flash it u will not need to flash firmware.
In previous post I told you to reset your phone from stock recovery did you try that?

Bricked S7 - Imei lost

I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

darkalez said:
Click to expand...
Click to collapse
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?

MAX 404 said:
Hi
Is not clear but can you get into download mode.....how did you flashed TWRP?
Click to expand...
Click to collapse
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp

darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)

darkalez said:
Hi... I can get into download mode... I installed the recovery in download mode few months ago and 1 hour ago I flashed the last version of twrp
Click to expand...
Click to collapse
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?

darkalez said:
I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
Click to expand...
Click to collapse
DroidHackeR said:
1)According to you if you can successfully boot into download mode then why can't you restore stock firmware using odin? Which type of errors odin showing? Always flash latest stock firmware using odin i.e. if nougat 7.0 is latest for you then flash latest 7.0 or if 6.0.1 is latest then flash it
2)Follow proper odin flashing guide with latest odin,Samsung usb drivers installed on pc and use original Samsung usb to connect your phone into main usb port
3)One more thing have you taken backup of your previous rom which had imei before flashing that specific rom? If not then you did a great mistake..If you have that backup then restore it
4)From twrp>mount>uncheck mount system partition read only (If you are facing can't mount system/data error)
Click to expand...
Click to collapse
MAX 404 said:
Hi
Same questions as above post
Did you try flashing with Odin?
How did you flash with Odin , what files did you use , what errors did you get?
Click to expand...
Click to collapse
Looks like OP has tried ODIN already

/data is likely encrypted, so it's not surprising that it doesn't mount, but it looks like you may have corrupted your EFS somehow. This is actually really REALLY bad. The EFS is device unique and by design irrecoverable. Previous Samsungs could regenerate it if you wiped it from recovery and then flashed stock with Odin, but AFAIK this hasn't worked since the S5. If you decide to wipe it make sure you dd your existing partition first, but if that doesn't fix it you may need to take it to a service centre and pay for a repair
Always backup the EFS first before flashing ROMs

flashing stock won't fix IMEI. Looks EFS is broken.
Try to find some1 with box.

*Detection* said:
Looks like OP has tried ODIN already
Click to expand...
Click to collapse
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did

MAX 404 said:
Hi mate
Error he showed was from recovery (TWRP) not Odin and he said he flashed TWRP from download........
That is why i was asking....what exactly he did
Click to expand...
Click to collapse
BTW, to address that error he needs to format data. But backup his stuff 1st.

starche_old said:
BTW, to address that error he needs to format data. But backup his stuff 1st.
Click to expand...
Click to collapse
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)

MAX 404 said:
Hi mate
That is clear , but not his information on what he want to do ( or has done) , format data is only necessary is you want to use the Data partition from within TWRP like flashing a custom rom from there, coping files , or backing-up data ( nandroid) to it otherwise is unnecessary ( if on a stock rom)
Click to expand...
Click to collapse
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.

starche_old said:
agreed. But in order to give access to TWRP he have to format those partitions by TWRP.
for IMEI - he need to find some1 with z3x or similar box, who knows how to fix IMEI properly.
Click to expand...
Click to collapse
Hi
No really , as long as you dont use the data partition with TWRP is not necessary , check their thread , that step is no longer listed on the OP
1 In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2 Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
3 Extract Odin_3.12.3.zip to your computer.
4 Install Samsung Mobile Phone Drivers for Odin to find your device.
5 Download a .tar image of TWRP for herolte.
6 Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + v[Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
7 Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
8 Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
9 At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
10 If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
11 Go to [Reboot] -> [System].
12 Wait 2-5 minutes for your device to finish setting itself up
As i said in stock ROM , custom roms may vary
Regarding IMEI you are totally right if he does not have a EFS back up

Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.

starche_old said:
Agreed.
But if you need to use TWRP in any way, like root your device, flash custom ROM (otherwise, why you need TWRP at all - to start with ), then you need to wipe data. Just recently rooted s7 - everything stays the same.
Click to expand...
Click to collapse
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.

As I SAID I can't flash stock firmware with odin, because of efs folder problem.... I already tried it.
I haven't got a rom installed on my s7 and I can't flash any, it'll not boot.
I gived it to a local shop.... I wait for his reply

darkalez said:
I opened today a thread because my s7 Exy wasn't booting. after few hours of charging it did it... it booted up.
Months ago I installed a bad rom and I lost my imei. I haven't got a backup. The problem now is... that my phone's bricked and I can't restore it with odin, because any action that I do end with the error "unable to mount /efs folder".
I flashed the last twrp recovery and now the problem is that it says that it's unable to mount data and efs folder whenever I try to flash a rom. Right now no rom's booting. I can't flash roms, and I can't unbrick it with odin.
That happened then flashing a custom a rom.....
I'm getting mad, any help will be appreciated
Click to expand...
Click to collapse
Try this guide to repair your efs.
Might be worth looking into re-partitioning here
If you can get into download mode, then there is always hope! Please excuse me if I missed any info, didn't read through the whole thread. Good luck! :good:

MAX 404 said:
I guess we are a little bit off-topic here........sorry everyone
You can do everything you want with TWRP without formatting the Data Partition as long as you do not use the data partition for it , lets say you want to flash a mod.....you can but you have to place the mode in you external SDcard.....then flash , do a nandroid also possible but to your external SDcard, same applies to root(zip) , place file in the externalSD and flashing it is possible , you can not use the internalSD card with TWRP as long as is encrypted if you decide you want to use the data partition then you have to format, this makes sense if you care for the encryption feature of Samsung in stock firmware
With custom roms it makes no sense to have it encrypted as it does not work and the rom can not read it.
Click to expand...
Click to collapse
Agreed.
And sorry everyone for off-topic

@darkalez: Since you have TWRP, you can flash other ROMs without any problem. I guess there are .ZIP files with stock ROM, although that won't reflash the recovery.
Why do you want to flash stock? If it's just to use that ROM, then do so via TWRP. Else you are in loss.

[cofface] [3.1.1-0]Twrp recovery for Huawei Nova2

Hi guys,
I made the TWRP from TeamWin official sources for Huawei Nova2 . You can download the img and flash it from fastboot.
Bootloader unlocked required!
Installation:
Unlock bootloader (skip if you have already unlocked it)
Reboot into fastboot mode
Flash using
Code:
HTML:
fastboot flash recovery cofface_pic_al00_recovery_en.img
Reboot
Download:
AndroidFileHost
Bugs:
When device is encrypted you can't see the files into recovery
Let me know if there are others
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc:fingers-crossed:
PAYPAL DONATION LINK
email:[email protected]

Unfortunately It is not working!
After flashing your file there is still the Huawei EMUI Bootloader and no TWRP. Bootloader was unlocked before. Fastboot was working fine.
Any idea?

Problem with Google GAPPS
Hi,
Thank you for your tuto and your ROM
I have bought my nova 2 in china.
Do you know how to install GAPPS. I have tried different version (stock, pico,.. ) but it's no use.
Do you know if I have to change the region first ?
Is it ok with your ROM ?
Regards

Perfect
Perfect, thank you!

Not working
Hello,
TWRP ist not working for me, I still have the EMUI bootloader after flash and reboot.
Boot into TWRP Recovery ("fastboot boot cofface_pic_al00_recovery_en.img") is aborted with:
"FAILED (remote: Command not allowed)"
Is there anything I've done wrong?
Thx!

dr.luther.1517 said:
Perfect, thank you!
Click to expand...
Click to collapse
did it work with your Nova 2?

i have got a demo device ( from germany ). Can some one upload his OEM info for a normal device ?
And yeah... it works

Success
Works very well, Thanks !
But ... while playing with it I lost the stock ROM for my Huawei Nova 2.
Since there is no download source available, could anybody share a stock ROM backup so I could restore using Twrp ?
Thanks !

My Nova 2 (PIC-LX9C432) automatically encrypts the disk after the first run, and then TWRP is unable to read /data partition nor do nandroid backups as a result. Can someone guide on how to disable encryption or get TWRP to decrypt data.
I read elsewhere that newer versions of TWRP are able to decrypt if you set a password / screen lock.

WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034

jusma said:
WARNING!!!! DO NOT FLASH THIS RECOVERY
Ideally cofface should remove this thread as flashing this recovery causes harm and no good. This TWRP port does not detect nor decrypt encryption on the 'data' partition and hence you will not be able to root your device nor take a nandroid backup.
What's worse, you will loose your recovery partition and will not be able to flash any other stock Nova 2 firmware updates.
If you have not yet flashed recovery and have the stock, please do a backup of your stock recovery and upload for the benefit of those who have lost it because of this recovery. See this thread...
https://forum.xda-developers.com/nova-2/help/help-restore-stock-recovery-t3741034
Click to expand...
Click to collapse
Perhaps you could get some tips from nova (1) thread there we had the same problems. But so long we have a working twrp with backup possibility.

Hi, i used this Twrp, but did not notice the error mesaje when i "create" a back up for all my data, then when deleting some things, i went off the road and ended deleting the complete operative system, and know i dont seem to be able to find a room for my phone is a huawei p10selfie(in my country) or huawei nova 2 plus (in the rest of the world) model BAC-L03, sry if i dont use the correct words, since english is not my native lenguaje

I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?

iamramanlmc said:
I was installing this twrp in Nova 2i and it get bricked ...I can only open TWRP which is just usless i can't flash anything from TWRP coz TWRP is not able to mount anything .Bootloader won't start and even my pc can't detect my phone. Any hope ?
Click to expand...
Click to collapse
Nova 2i is Mate 10 Lite! https://forum.xda-developers.com/ma...e--roms-kernels-recoveries--other-development

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}