Bit of a Pickle. - Huawei Ascend Mate 2

Hi XDA. I'm in a bit of a Pickle. I think I thrashed my HAM 2.
Recently I upgraded to B309 (Lollipop). After that, I flashed CM12. And I went back to Lollipop because of battery issues.
Lollipop was buggy, and music kept stopping at random moments, so I decided to restore 4.3 using TWRP. Everything seemed normal, but my internal storage wouldn't mount. I couldn't take pictures because of "insufficient space", but I could download apps just fine. So after trying to get my internal storage back (unsuccessfully), I decided to restore Lollipop. (B309) And now Wi - Fi won't turn on. Then I tried flashing CM12, but the Wi - Fi issue was still there.
Please help. I love my HAM2 too much.

Since Lollipop has one partition less than JB, so when you downgrade using twrp instead of official 2 pkg flash, you will miss one partition.
Anyway, have you tried factory reset after you restored to lollipop again?

Wasn't a wipe supposed to be performed prior to flashing or am I misremembering?

yaso202 said:
Hi XDA. I'm in a bit of a Pickle. I think I thrashed my HAM 2.
Recently I upgraded to B309 (Lollipop). After that, I flashed CM12. And I went back to Lollipop because of battery issues.
Lollipop was buggy, and music kept stopping at random moments, so I decided to restore 4.3 using TWRP. Everything seemed normal, but my internal storage wouldn't mount. I couldn't take pictures because of "insufficient space", but I could download apps just fine. So after trying to get my internal storage back (unsuccessfully), I decided to restore Lollipop. (B309) And now Wi - Fi won't turn on. Then I tried flashing CM12, but the Wi - Fi issue was still there.
Please help. I love my HAM2 too much.
Click to expand...
Click to collapse
Use factory recovery and run the 4.3 downgrade from huawei.

xordos said:
Since Lollipop has one partition less than JB, so when you downgrade using twrp instead of official 2 pkg flash, you will miss one partition.
Anyway, have you tried factory reset after you restored to lollipop again?
Click to expand...
Click to collapse
Yes. Factory reset, but I guess I'm still missing one partition, as you say. Will try downgrading using stock recovery, maybe that will help.

Moody66 said:
Use factory recovery and run the 4.3 downgrade from huawei.
Click to expand...
Click to collapse
Downgraded from 5.1 LP to 4.3 JB using Huawei's way of downgrading. (UPDATE.APP) Seemed to work, but it still doesn't want to mount internal storage. I can install apps, but I can't take photos.

yaso202 said:
Downgraded from 5.1 LP to 4.3 JB using Huawei's way of downgrading. (UPDATE.APP) Seemed to work, but it still doesn't want to mount internal storage. I can install apps, but I can't take photos.
Click to expand...
Click to collapse
Change default save location for camera to external SD. Seemslike there was a place in settings to also change default location of storage. I remember having an issue and changing it then changing it back and it worked. Other than that formatting it is only thing else i can think of.
Well I did find this.
http://forum.xda-developers.com/ascend-mate2/help/mount-internal-storage-downgrade-to-4-3-t3186659
And
http://forum.xda-developers.com/showthread.php?t=2354029

I got access to my storage after running "restorecon -v -R /data/media" this command line through the terminal in twrp. My suggestion, run the cmd, restore from an update.app file for b309 with the vol + & vol - power button combo, and then there's instructions on gethuawei for the official downgrade to 4.3
Maybe this will help.

I'll try doing that in a couple of days. Installed CM12 for now, runs like a dream.
Sent from my Ascend Mate 2 using XDA Free mobile app

yaso202 said:
I'll try doing that in a couple of days. Installed CM12 for now, runs like a dream.
Sent from my Ascend Mate 2 using XDA Free mobile app
Click to expand...
Click to collapse
Its nice. Battery life isn't as great. Next release should solve a lot of that.Ines actually better than stock now. But I am running wakelocks blockers.

Related

[Q] Cannot Install new ROM, Status 7 error

So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?

Getting "com.android.phone has stopped working error" cm11 official vs985

I have just recently tried to install the official cm11 images for my g3. They worked fine. Then, when I installed gel x-posed settings and activated it, I would get said error. It would pop up again and again. This would lead me to reflash my ROM. Then, I do not know what happened, when I would flash a ROM, I would get the error from the start. I eventually fixed this error. But then, when I tried to upgrade the nightly, I got the error again. So I flashed the ROM again, and let it sit. After a little while of perfection, the error came back up!
Here's what I have tried:
-reflashing the boot.IMG (unzipped)
-clearing cache (recovery)
-clearing Sim tool cache/data (said they were non existent when trying)
-reflashing stock, then reflashing cm11
I really want cm11 on my g3, but with these issues, I don't know whether I can now.
Any help would be appreciated!
Sent from my Nexus 7 using XDA Free mobile app
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list: https://itvends.com/gapps/
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
mwest316 said:
CM Nightlies are working perfect for me with no errors. Here is the process I went through:
I am still using TWRP 2.8.0 which is the version I installed when I originally Bumped! my phone.
I downloaded CM and Gapps to root of my internal SD storage
I chose to Wipe in TWRP
I chose Advance Wipe
I picked every option except for Internal Storage and External SD Card/Storage
I then Wiped
Out of habit, I do this 3 times (don't ask why, I just do it from when I had older android devices)
I then go back to wipe main screen and slide to do the standard wipe, 3 times
Yes, this is probably overkill!
I then go to install in TWRP
I install CM, then I install gapps (using the gapps that are on this list:
Yes, the date of those gapps are a little older, but that is what worked for me per OP'S instructions
I went through setup of my phone, fixing APN, Setting WIFI to USA, signing into Google after first loading into Rom instead of signing into Google on first bootup. Did a reboot
Installed Xposed, and the modules needed, reboot
I never received any error
I have done 3 nightly updates so far, as of 11/30. I am sure 12/1 will be ready in an hour or so.
I always click on about phone, download said update and let the process do its thing automatically, walk away and the phone is ready to use
Still no errors whatsoever. In fact, this has been the first version of AOSP I have used for the G3 with 0 errors. It is perfect, for me - No issues.
Hope that helps.
Click to expand...
Click to collapse
I did everything exactly as you did, including the 3 wipes, also out of habit. I too however, get the same error with the latest nightly. It starts popping up as I try to add my Gmail account at the initial setup. Previously, the 'unofficial' builds did not do this to me. This is the only rom that does this, I have tried them all out. I have yet to try to flash a different gapps package to see if that makes a difference. Apparently I dont get the data issues with cm12, but get phone issues with cm11.
I'm a bit relieved to see I'm not the only one having this problem. Been updating every night to see if maybe it's fixed, but I still get the same error. Didn't happen on the first nightly I flashed, though. It lol seems to be happening at random for me. Sometimes I'll set my phone down for a couple hours, working perfectly fine. Then I pick it up to check something and I suddenly start getting that error. I've tried every "solution" I find and none of them work for me. Even thought it was an issue with reading my sim card because when I get the error, it shows that my sim card isn't being read. But I still get it when I take it out. A normal factory reset doesn't fix it either. I have to do a complete data format to remove the error.
I found a quick little fix where i make a backup earlier in the day and just restore it whenever I start getting the error, but it's still very annoying.
Same issue
Hey bros,
Same thing here. It's a baseband radio issue. Notice in settings under About Phone it says 'Baseband Version: Unknown'. Either TWRP is flashing over our baseband (not likely, calls and texts can be made before the error message attacks come), or CM11 has some issue on certain builds with reading our SIM cards. I think having an official 10B or 11C flashable baseband radio to install at the time of the ROM install will fix this problem. Waiting on CM to patch the code will take too long. Let me know if you find one of these basebands or can find out how to extract it (from file manager or somewhere?) as I have not been able to find this info on XDA or anywhere.
EDIT: I FIXED IT
I'm a new member, and XDA won't allow me to post links..... look in the OP for JasmineROM (all credit to author for posting this 11C modem and fabulous stock LG debloated ROM) under downloads, you'll find the 11C modem. Download it.
1. Place 11C modem.zip on external or internal, whichever you want. I prefer external.
In TWRP:
2. Backup, unless youre livin' life on the edge.
3. Wipe it all except for external (or internal, if you prefer to flash from your internal storage)
4. Add to Install zip que in order:
a) latest CM11 nightly
b) 11C modem found in JasmineROM OP of main thread
c) GAPPs of your choice (I like nano PA GAPPs, and just install whatever else i want after)
5. FLASH
6. profit
7. PHAP
I have heard the 10B radio works great too. holler back and post results between the 2 stock radios for VS985.
Please hit thanks, as I am new and want to be helpful, where possible. Please share this so others know that we can overcome this nonsense.
CM11!!! Phappin' so hard right now!
Got it again.... totally blowed right now. maybe reconfig APN to match VZW and it will work?
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
8pscott said:
Thanks for all the responses, it currently seems that the problem is cm11. I will probably wait for a stable build. For now, I'm using an unofficial cm12 ROM. Thanks for all the help!
Sent from my LG-VS985 using XDA Free mobile app
Click to expand...
Click to collapse
Are you using that PA GAPPs package that's in alpha? I think i'm going to give up and go to 12 too... I do know that the first official nightly of CM11 doesn't give me any errors, but Trebuchet is so buggy it won't take widgets. Had to download Nova
It makes me cry. My phone lasted through the night. Woke up at around 7 and it was fine. Went back to sleep and woke up at around 8:30 and I was crushed to see the problem happening again. There doesn't seem to actually be anything thy triggers it. :/
Yeah I think I'm gonna just try out cm12 and see how that goes.
Double check to make sure the phone isn't running in art. That fixed my problems! Xposed and art do not work together!![emoji2]
Im getting the same error on my phone usually a few says after using any of the nightlies. When i go to make a phone call it gives me the force close and doesnt stop. Ive since moved back to stock hoping someone had more info on the issue. My phone was not using Art but I did have xposed installed.

[Q&A] [ROM] Empty [VZW] Galaxy v3.8 [I545VRUFNK1] 12/19

Q&A for [ROM] Empty [VZW] Galaxy v3.8 [I545VRUFNK1] 12/19
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Empty [VZW] Galaxy v3.8 [I545VRUFNK1] 12/19. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Rooting fnk1
So this might be a silly question but after upgrading to 4.4.2 via samsung kies, I can't find a root method that will work for VRUFNK1.... I tried towelroot but it doesn't support my device. If I want to try this rom out how do I go about rooting my S4 VZW?
question for wtfchuck about empty vzw galaxy
after you did the Alternative Custom ROM Method: to update to NK1 and flash ss, super su etc, did you immediately flash the custom rom or did you let the system boot and reboot into safestrap and then flash empty galaxy?
thanks
Brian
reliant_turbo said:
after you did the Alternative Custom ROM Method: to update to NK1 and flash ss, super su etc, did you immediately flash the custom rom or did you let the system boot and reboot into safestrap and then flash empty galaxy?
thanks
Brian
Click to expand...
Click to collapse
Nevermind. I allowed the phone to reboot and i got a bunch of "Backup Assistant Has Stopped" errors. Apparently my data backup had something in there that was causing this error.
I went back to safestrap, wiped, flashed empty galaxy, flashed modules and booted into empty galaxy with no issues. apps are installing as we speak.
Brian
rotate_on_home
I couldn't get rotate_on_home.zip to work. I flashed it in safestrap.
Any tricks/tips/setup info for this?
Brian
** [ROM] Empty [VZW] Galaxy v3.92 [I545VRUFNK1] 1/2** system cannot be backed up
System cannot be backed up via Safestrap after installing empty galaxy v3.92. Safestrap always says "backup complete failed" (in red letters). Did full update to I545VRUFNK1 via directions on this page http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufnk1-4-4-2-12-1-2014-t2959613. Tried both methods, odin only method and safestrap method. Both worked ok and I am able to back up system via safestrap from here. However as soon as I install empty galaxy v3.92, whether doing a factory reset (via normal recovery or safestrap) or advanced wipe via safestrap or no wipe at all I lose abiltiy to backup system. Tried both Safestrap-JFLTE-3.72-kk-B01 and Safestrap-I545-3.75-KitKat-A03.
I spent hours trying to solve this and got nowhere. I can back up system on stock I545VRUFNK1 no problem but as soon as I install empty galaxy v3.92 via any type of wipe or no wipe at all I can no longer backup system. I can confirm I am on baseband I545VRUFNK1, Android Version 4.4.2 and using I545_NK1_Modules. I have tried every option under the sun seems the problem lies with empty galaxy v3.92.
** [ROM] Empty [VZW] Galaxy v3.92 [I545VRUFNK1] 1/2** system cannot be backed up
Fixed??!!
Went for a ride into the city this afternoon, listened to some Bluetooth music, changed theme in supersu, set correct time zone in safestrap
No major changes made
Decided to give it another go after like 8 hours of trying to solve this yesterday. System (and data) backs up ok now.
From what I have read in the General section for this device, you need to do the temporary kernel downgrade method to root NK1 with towelroot. ..
Sent from my SCH-I545 using XDA Free mobile app
Yeah I did just that. Used I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar via odin to upgrade to NK1 (came from CarHD 32.1S v2 NG6-NCx STOCK so unable to get OTA update). Once I update to NK1 use odin to flash I545_NC5_Stock_Kernel, run towelroot, then use odin to flash I545_NK1_Stock_Kernel. Then install supersu.
Honestly I don't know how I fixed it. My best guess is somehow having the wrong time zone in safestrap somehow caused a problem backing up system. All I know is now I can back up system ok (data too).
Thanks for the help anyway...still worth giving a thumbs up!
phone issue when connecting bluetooth during call
i have an issue that ive found. when i accept a call and then connect my bluetooth headset, com.android.phone crashes and i cant hear anything in my bluetooth headset. i can still talk on the phone and sometimes it switches to speaker. i cant hang up either even if i click phone again.
i managed to recreate it and recorded a logcat with catlog but i dont really know what everything is doing in there or if i caused it with an app conflict.
normally i have my bluetooth headset connected first and then make a call and thats fine. i just switched to this rom last friday or saturday and i dont think i connected the headset during a call since then.
thanks.
I am a bit confused over what is the purpose of the empty galaxy rom. Does it actually free up any space on the internal storage? My S4 seems to have about as much free space as running a full stock rom. What are the actual advantages of running the empty galaxy rom versus a full stock rom?
I love the work on this rom and enjoy running it. I am just curious as to why my S4 only has 6.5 gb free on the internal storage when I barely have any apps installed.
beavis5706 said:
I am a bit confused over what is the purpose of the empty galaxy rom. Does it actually free up any space on the internal storage? My S4 seems to have about as much free space as running a full stock rom. What are the actual advantages of running the empty galaxy rom versus a full stock rom?
I love the work on this rom and enjoy running it. I am just curious as to why my S4 only has 6.5 gb free on the internal storage when I barely have any apps installed.
Click to expand...
Click to collapse
The current size of this rom is less than 1 gig. Current stock 4.4.2 is approx 2.6 gig so there is 1.5 gig saved... UNLESS...you are keeping stock rom in Stock slot and employing slot-1 for custom rom which means you have approx 3.5 gig in just rom. I run EVG in Stock slot leaving other slots empty and have 101 USER apps on phone w/ 6.5 gig left on internal SD.
Nk1 modules
Where can I download Nk1 modules?
thank you
I just wanted to thank you for this rom. It works great, and is the only one I've had zero problems installing. Are you going to be developing one for the lollipop update once it's released? Perhaps one that can be installed with safestrap so that we don't have to do the ota update and lose root access?
Problems with GPS and Keyboard.
Hi I'm still new to flashing roms and such. But I have a Verizon S4 with a FRESH INSTALL of NK1 Towel rooted with Safestrap v3.75, I've attempted to install your rom to my phone and it goes through fine. I have flashed the NK1 Modules. However my GPS is locked on PowerSaving, I can not switch to accurate. Also when I attempt to switch to SwiftType (Keyboard) it prompts me that it may collect data, I ok that and it goes back to Samsung Keyboard. How can I override these? I am having issues with "EGR_TWUI_321". Thanks for your help. If you need more information let me know what you need and I'll try to reply promptly.
So just out of curiosity I wiped my system and started over from a base NK1 then I went through the steps of rooting and Safestrap, but I installed the 3-4-15 version this time. And the above issues are not present. However I really dislike this one when compared to the newest one when it comes to theme and customizing. It's also not as bloat free as the other one. I still have Amazon music and NFL and even VZTones.... Any idea why the newest one is breaking the GPS and the Keyboard? I really want to run that one again =(
MuddyCupz said:
Where can I download Nk1 modules?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95832962473396366
armyofsquirrels said:
Hi I'm still new to flashing roms and such. But I have a Verizon S4 with a FRESH INSTALL of NK1 Towel rooted with Safestrap v3.75, I've attempted to install your rom to my phone and it goes through fine. I have flashed the NK1 Modules. However my GPS is locked on PowerSaving, I can not switch to accurate. Also when I attempt to switch to SwiftType (Keyboard) it prompts me that it may collect data, I ok that and it goes back to Samsung Keyboard. How can I override these? I am having issues with "EGR_TWUI_321". Thanks for your help. If you need more information let me know what you need and I'll try to reply promptly.
So just out of curiosity I wiped my system and started over from a base NK1 then I went through the steps of rooting and Safestrap, but I installed the 3-4-15 version this time. And the above issues are not present. However I really dislike this one when compared to the newest one when it comes to theme and customizing. It's also not as bloat free as the other one. I still have Amazon music and NFL and even VZTones.... Any idea why the newest one is breaking the GPS and the Keyboard? I really want to run that one again =(
Click to expand...
Click to collapse
It sounds like you either done a dirty flash or your system didn't get wiped properly.
That or those apps are being restored from the Play Store. I could be wrong but I don't believe any of those apps are even in the rom.
Maybe a factory reset (full wipe) and a clean install would solve your issues.
sent from a Galaxy S4 far far away.
gadget! said:
It sounds like you either done a dirty flash or your system didn't get wiped properly.
That or those apps are being restored from the Play Store. I could be wrong but I don't believe any of those apps are even in the rom.
Maybe a factory reset (full wipe) and a clean install would solve your issues.
sent from a Galaxy S4 far far away.
Click to expand...
Click to collapse
Thanks I'll try starting over from base and seeing what happens and I'll update you. Towel is the app used to root the NK1 firmware, safestrap is the app that we who are stuck on Verizon with a locked bootloader have to use to flash roms. SwiftKey is a keyboard app from the play store. Or where you talking about my second flash with the 3-14-15?
armyofsquirrels said:
Thanks I'll try starting over from base and seeing what happens and I'll update you. Towel is the app used to root the NK1 firmware, safestrap is the app that we who are stuck on Verizon with a locked bootloader have to use to flash roms. SwiftKey is a keyboard app from the play store. Or where you talking about my second flash with the 3-14-15?
Click to expand...
Click to collapse
I know what all of those are, I was referring to your statement about the bloatware...
armyofsquirrels said:
I still have Amazon music and NFL and even VZTones...
Click to expand...
Click to collapse
gadget! said:
I know what all of those are, I was referring to your statement about the bloatware...
Click to expand...
Click to collapse
Gotcha. I thought it was weird too still have them too. I just reinstalled the newest version this morning. Everything seems to be working now. Not sure what happened since it was the only Rom I installed.

Back to 4.4.4 from Lollipop

For anybody that wants to go back to 4.4.4 from 5.0 I can confirm it works great, I just flashed back with Odin. The 4.4.4 firmware is at sammobile right below the lollipop firmware. The 4.4.4 flash put it into a bootloop to which I then factory reset and it started up perfectly with none of the completely unusable issues I was having.
Bummed out that I can't use lollipop for the time being, but more than relieved that I have a usable phone again, I thought it was toast.Lollipop made my phone worthless, literally couldn't do anything, major bootloops and constant crashes.
I made another thread about it here
http://forum.xda-developers.com/verizon-galaxy-note-3/help/reboots-lollipop-t3090421
You should retry the upgrade, it's faster and more stable. You just had a corrupted file or something, if you really want the best is worth a try. It's 40% faster. There was just something wrong with your install.
Did you do a factory reset when you upgraded? A lot of Note 4 users who upgraded had similar issues which a factory reset corrected.
I took the upgrade and found it to be faster and more reliable as well. Still fingers crossed for a root exploit. At least we know if an exploit ever happens for 4.4.4 then we can downgrade to get it. Good to know!
Oh really? I thought we couldn't roll back after taking 5.0. I am having a hard time a stable host to download 4.4.4
Can someone help me out with this? <confused>
@ lost perfections:
Success! The 4.4.4 firmware took forever to download but worth it! Thank for this!
KruseLudsMobile said:
You should retry the upgrade, it's faster and more stable. You just had a corrupted file or something, if you really want the best is worth a try. It's 40% faster. There was just something wrong with your install.
Click to expand...
Click to collapse
Trust me I really wanted it and tried all the usual steps. I think something is wrong with my phones hardware that works mostly ok on this version. I actually stayed on an old version for a very long time, I rooted "root de la vega" and took one ota using the supersu option to keep root when using an ota. The next update after that would not work for me, I would have had to wipe and odin to update, so I held off thinking I wasn't missing anything. Till about a week or less after 4.4.4 came out then my phone started crashing the moment I received or made a call. I hadn't gotten any new apps or anything like that but just in case I factory reset to see if it fixed with no luck. So I finally upgraded via odin, no root now, but miraculously my phone could make calls again. I am giving you this essay because I have a feeling this issue is related. It seems it's my phones hardware that is messed up and i'm just lucky that 4.4.4 works at all. I still have issues every couple days where I make or receive a call and hear nothing, with a reboot needed to fix, that is confirmed still after a fresh install of 4.4.4 after all the 5.0 stuff I tried. Anyways thats why I think it's my phone. I wish I had an extended warranty so I could just update and make a claim.
As for everything I tried in the update, I took the ota, which was literally unusable by anybodys standard, I could use the phone for about 5-20ish seconds before it would crash, turning the sound to mute would help, but still crash at a couple minutes of use. I downloaded the firmware and flashed via Odin, same exact issues, changed nothing. Did several factory resets between all these steps. I kind of walked through the process on that thread I posted in the OP.
After making this thread I did try it one last time and flashed via odin, knowing that I had a workable fix, but same exact thing again. If they release another update I'll try then, but looks like I'm stuck till then at least.
Reilly1812 said:
Did you do a factory reset when you upgraded? A lot of Note 4 users who upgraded had similar issues which a factory reset corrected.
Click to expand...
Click to collapse
Yeah I did anything and everything I could, no luck. I think my phone itself is the problem.
sameog said:
@ lost perfections:
Success! The 4.4.4 firmware took forever to download but worth it! Thank for this!
Click to expand...
Click to collapse
Awesome, glad it helped. I'm SO glad they didn't block the ability to do this, I'd have been out a phone if they had.
LostPerfections said:
Awesome, glad it helped. I'm SO glad they didn't block the ability to do this, I'd have been out a phone if they had.
Click to expand...
Click to collapse
Can you be more specific? There are two firmware versions that are 4.4.4-NJ6 and NK1. I assume you used NK1? I'm a newb and sort of know how to use Odin/download mode. What version of Odin did you use?
I want to rollback to the previous build until they sort out the radio issues. My phone was fine on NK1 but on lollipop it drops LTE indoors frequently. Aside from the radio issue, lollipop runs great. I factory reset after the update, didn't make a difference.
YayNote said:
Can you be more specific? There are two firmware versions that are 4.4.4-NJ6 and NK1. I assume you used NK1? I'm a newb and sort of know how to use Odin/download mode. What version of Odin did you use?
I want to rollback to the previous build until they sort out the radio issues. My phone was fine on NK1 but on lollipop it drops LTE indoors frequently. Aside from the radio issue, lollipop runs great. I factory reset after the update, didn't make a difference.
Click to expand...
Click to collapse
You can use any radio with any rom. Just flash the modem file via flash app or Odin.
thornev said:
You can use any radio with any rom. Just flash the modem file via flash app or Odin.
Click to expand...
Click to collapse
Are you certain I can use a KitKat radio on lollipop? Verizon Note 3. If so, I'll do that right now.
Sent from my SM-N900V using XDA Free mobile app
YayNote said:
Are you certain I can use a KitKat radio on lollipop? Verizon Note 3. If so, I'll do that right now.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
I haven't done it, but I have mixed radios and roms before for example kitkat radio with JB rom.
Well, I'd still rather 4.4.4.. it's too bad. When I have strong LTE it's amazing. Did this speedtest today - kilobytes per sec. Incredible.
Sent from my SM-N900V using XDA Free mobile app
YayNote said:
Well, I'd still rather 4.4.4.. it's too bad. When I have strong LTE it's amazing. Did this speedtest today - kilobytes per sec. Incredible.
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
No matter what....once you go to lollipop, you can NOT go back to any earlier version.
Sent from my Note 3 via Tapatalk
Doesn't the OP state that you can revert back?
YayNote said:
Can you be more specific? There are two firmware versions that are 4.4.4-NJ6 and NK1. I assume you used NK1? I'm a newb and sort of know how to use Odin/download mode. What version of Odin did you use?.
Click to expand...
Click to collapse
Yep. The OP did. Hell that's the title of the topic and there's two confirmed posters that did it successfully. I only wanted to know if they flashed NJ6 or NK1 and what build of Odin they used..
YayNote said:
Yep. The OP did. Hell that's the title of the topic and there's two confirmed posters that did it successfully. I only wanted to know if they flashed NJ6 or NK1 and what build of Odin they used..
Click to expand...
Click to collapse
Okay, to anyone whose interested: I used Odin 3.09 & NK1 (most current VZW build of 4.4.4) and it worked. Phone went into a bootloop, started recovery did a factory reset an it's back to normal.
Lollipop ran fine on my phone-probably because I reset it as soon as I updated...BUT, my data signal was halved. I get a weak LTE signal at work and by weak I mean 1 or 2 bars 105-115DB at best. Old brick building and I work in the basement. On lollipop, it wouldn't hold onto LTE anymore. It'd flip between 1x/3g..usually settling on 3G. Voice was unaffected. Hopefully they sort this out but this sort of signal performance (especially when it was fine on KK) is unacceptable.
Rolling back to NK1 has solved that. Thanks to the OP!
I can also confirm that flashing 4.4.4 NK1 from 5.0.0 OB6 works.
Tried it myself, but after I got done playing with it I went back to 5.0.0 OB6 afterwards.
I didn't look to see if it kept the 5.0.0 radio when downgrading to 4.4.4, but it kept the 5.0.0 boot loader.
I did not test the radio (as I didn't have a usable sim card at the time.)
Also, don't try to run URDLV on the 4.4.4 firmware before flashing, it will not boot (even with a factory reset.)
But I didn't try to flash a modified 4.4.4 firmware after 4.4.4 was already on there.
so just so I understand there's no root for 4.4.4 or 5.0 but it's possible to go back to 4.4.4 from 5.0 ?

Twrp doesn't restore my backup - error 255

I was using miui 8 the past month and wanted to try something new. So I flashed.a MM.Rom, CM13 from this forum. I did a system backup before. I am using twrp 3022.
After trying the Rom i decided to restore my miui backup, but when i try that I get an error saying:
extractTarFork() process ended with ERROR=255
I tried it several times but i always get this error after 85-87% of the restoring progress.
Is it because one rom is based on LP and one on MM? I never changed the twrp 3022.
I've read somewhere that it can be because of not having enough space but it's a system backup, so doesn't it mean, that it restores the whole system and data i had on that phone?
Please help
Edit
Restoring the cm backup works but the miui dies not work
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate ?
Jordan Jacob said:
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate
Click to expand...
Click to collapse
The Lollipop Rom?
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Jordan Jacob said:
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Click to expand...
Click to collapse
ok thanks i will try it
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
gasperoni said:
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
Click to expand...
Click to collapse
Did you wipe the data partition or did you format it? Try doing the latter ...
First i wiped cache+dalvik+data+system, everything but intern storage. I thought that must be enough. My last chance was wiping internal storage as well. I tried that and now it works. It really seems that it was a problem of space. I want to go back to a CM13 based Rom, when it's getting more stable.
Glad to hear your problem solved..
Jordan Jacob said:
Glad to hear your problem solved..
Click to expand...
Click to collapse
thanks bro, me too :good:
I've had this problem too - exact same error message, with the last two versions of TWRP.
I originally made a backup of my Nexus 7 2012 3G (Tilapia) with the modified KOT49H ROM installed, with TWRP (3.0.2.0, I think). I installed one of the Lollipop ROMs (I forget which) then restored that KOT49H based backup with no problem. Then I tried a different Lollipop ROM (Resurrection Remix, something) then tried to restore the same KOT49H based backup as before, and got this error.
I went from there to the Nougat ROM I'm currently using - an AOSP one by AndDiSa, and made a backup of that installation shortly after. After making some changes, I tried to restore that backup and got the same error (see OP).
I deleted as much stuff as I reasonably could, updated TWRP to 3.1.0.0 via fastboot and tried the restore again - same error. Also, my tablet then wouldn't boot, though that might be an unrelated problem. I took the battery out, which possibly I didn't need to, put it back, and noticed it was charging. It eventually booted, and seemed to have restored the backup, though I cant' be sure. Since it was the same ROM, it's possible all it restored was the data partition.
My main question is, if this is related to free storage, just how much is needed, to be able to restore a backup? I don't see wiping internal storage as much of a solution, on the Nexus 7, because there isn't a microSD slot, so that's the only place I can put the backup I'm trying to restore.
Hello. Can you please give me the twrp nvram backup or just the protect_f.img and protect_s. Thank you
Had same error, went back to old twrp ,all problems fixed
Steveromingagain said:
Had same error, went back to old twrp ,all problems fixed
Click to expand...
Click to collapse
what version TWRP to fixed problems ? i use TWRP version 3.0.2.2 always Error...

Categories

Resources