ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Paisley Pirate said:
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Click to expand...
Click to collapse
For those wondering about updating to B180.....
See this post and links in it for how we updated before if the phone was already unlocked bootloader/rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
reloaded 170 full version on and it worked fine. Need to clean it up, as it threw the bloat back on - but didn't lose anything. Unfortunately, between 2 jobs, and moving (working on new house now, move in a couple weeks, then work on old house to sell it) I'm not seeing much time in my future to play with it much.
Is B180 rootable?
I imagine like the other version so far, it should be.
Ad86shwks said:
Is B180 rootable?
Click to expand...
Click to collapse
I have B170 installed. But I have it debloated, rooted, and custom recovery on it. I want to update to B180. Anyway someone can make it a standalone update? Like B170?
im waiting on the files from someone and i will release a b180 stock update as well as update my rom to b180 once i get the b180 files
b180 uploaded stock preroot atm will do full stock soon b180
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
hi5five said:
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
Click to expand...
Click to collapse
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Did you previously have B170, then used your zip to update to B180?
madvane20 said:
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Click to expand...
Click to collapse
i flashed b170 stock then flashed my b180 stock if wifi is broke i can redo it but it worked on mine just let me know
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
Click to expand...
Click to collapse
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Thanks for that detail. I wonder which partitions aside from the boot partition get modified after rooting that then breaks OTA from working.
dabadguycr said:
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Click to expand...
Click to collapse
---------- Post added at 10:50 PM ---------- Previous post was at 10:35 PM ----------
I don't think there's any way to put your phone back to the state where an OTA will work - at least nothing we currently have on the XDA forums here that I've seen.
You could always try what you wrote below - I expect OTA will fail. If it fails, you could flash B180 - which I believe is unrooted from what I recall @clsA writing about his method to flash B180 in the B170/B180 thread by @madvane20 - but please double check on that before doing it since you want to be able to remain unrooted.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Click to expand...
Click to collapse
hi thanks for this advice buy my device does not have this directory or files. I am in the same boat on 170 slim and fast, got AT&T update and now in force reboot update and fail loop. i really want to find a way to make it stop force rebooting? surely something i can do in twrp terminal. any advice? but alas I might just have to reflash.
make sure u mount system in twrp that folder and file should be there and make sure to clear cache like the other post said
Related
Has anyone figured out how to apply this update on a rooted device running "official" ROM? For me the update downloads and reboots to recovery (twrp in my case). The update is not applied.
Thoughts?
tmknight said:
Has anyone figured out how to apply this update on a rooted device running "official" ROM? For me the update downloads and reboots to recovery (twrp in my case). The update is not applied.
Thoughts?
Click to expand...
Click to collapse
you need stock recovery, also i think (not completely sure about this) you have to unroot and maybe even relock your bootloader in order to apply the update.
reaper90 said:
you need stock recovery, also i think (not completely sure about this) you have to unroot and maybe even relock your bootloader in order to apply the update.
Click to expand...
Click to collapse
My phone is completely stock and I still can't download this update. Maybe because I live in Europe... This is awful.
R.Petrov said:
My phone is completely stock and I still can't download this update. Maybe because I live in Europe... This is awful.
Click to expand...
Click to collapse
you said, you've got TWRP recovery installed, so your phone's bootloader is definitely unlocked and you've got a custom recovery installed. The update only works if /system partition is completely stock, you've got stock recovery and your bootloader is (re-)locked.
if anything doesn't match your phones CID, the update won't install.
I did not say that. tmknight did.
I have this phone with an AT&T IMEI from China, but the ROM is not from AT&T, I guess its the Erupean version or somenthing... it came unlocked for any GSM company and thats why i bought it... I also know that the bootloades is locked.
I cant update it with the official AT&T ROM cause it does not find it... Im stuck in its Android 4.1.1 slow version, and I see many bugs on it.
Can anyone help me? PLEAAAASSSEEEEE!!!!
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin
Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
I've been thinking about reversing the CM12 install so I can play with the B320 or B321 updates. The problem is, I'm not certain of the reversal process. Do I have this right?
flash B148 via the dload method
FLash B309 via the dload method
Flash the B320 via the dload method
I'm sure I must be missing interim steps. Could someone list out the necessary steps?
After flashing stock recovery. Flash 309. Don't really need 148.
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Bill R said:
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Click to expand...
Click to collapse
B148 is the rom itself. Recovery can be stock. Or twrp.
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
robertbarber said:
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
Click to expand...
Click to collapse
Yep.
Ok, now I understand. I went through three pages and could not find a download for the stock recovery. Is there a link?
Never mind. Found the stock recovery here:
http://forum.xda-developers.com/showpost.php?p=55617080&postcount=7
Then remembered I had made a backup prior to loading CM so it should be at least 309. I'll still have to flash the stock recovery to get from B309 to B320 correct?
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
xordos said:
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
Click to expand...
Click to collapse
That's what I ended up doing. TWRP restore to B309 then flashed the stock recovery, then flashed B320. I haven't registered my EMIE number yet as I'm not sure if I'm going to stay with the stock lollipop.
One interesting note; when I flashed B320, I had to facotroy reset 3 times because every time when it came to restoring my apps, it would, like, time out and flash past it. The fourth time I was ready for it.
I had previously flashed my G5 to Lineage/Mokee to allow the phone to pickup software updates.... I don't actually mind the stock ROM, rooted and debloated, but I also want to pick up software updates (and I don't mind needing to re-run SuperSU after each update).
Any recommendations? OR should I just get onto Lineage/Mokee again?
I'm same as you.. Stock rooted.. I'm just going to update through LG Bridge when and if the time comes
BahnStormer said:
I had previously flashed my G5 to Lineage/Mokee to allow the phone to pickup software updates.... I don't actually mind the stock ROM, rooted and debloated, but I also want to pick up software updates (and I don't mind needing to re-run SuperSU after each update).
Any recommendations? OR should I just get onto Lineage/Mokee again?
Click to expand...
Click to collapse
I just download the update zip, upload on the phone and flash with TWRP. Then flash superSU (which is sitting on my SDcard anyway) and I'm good to go. 10 min. max.
ebisa said:
I just download the update zip, upload on the phone and flash with TWRP. Then flash superSU (which is sitting on my SDcard anyway) and I'm good to go. 10 min. max.
Click to expand...
Click to collapse
@ebisa - that sounds like what I'm after, but where do you get the update.zip files?
BahnStormer said:
@ebisa - that sounds like what I'm after, but where do you get the update.zip files?
Click to expand...
Click to collapse
well, I get them from here - the forum. Nice people upload them, lol. The last one I've got is this.
Do mind that I'm on H850 and this rom is for this variant of the G5 only.