4 OTA 5.0 attempts - 4 Failed installations! Help 😯 - Sony Xperia Z Ultra

So frustrated!
#1 was regular attempt w/device as is
#2 w/factory reset
#3 unrooted
#4 rooted and changed some system files (that I remember that had been modified....a camera mod, volume mod etc)..i thought Factory reset would have done that.
All 4 Failed
At a loss at this point.
Any help appreciated!

I have had a problem with FOTA twice as well. I also unrooted, and did a factory reset. Changed BBS back to a user app before unroot. Both times I got the FOTA it begins to install, gets to maybe 10% (guessing here) and then the Andy with the red triangle pops up with "ERROR!" beneath it. After that I have to boot into recovery and manually reboot.
Hopefully this doesn't hijack your thread, but when I tried to install the update with ADB, it tries to load the update, then ADB cannot see the device anymore.

rockky said:
So frustrated!
#1 was regular attempt w/device as is
#2 w/factory reset
#3 unrooted
#4 rooted and changed some system files (that I remember that had been modified....a camera mod, volume mod etc)..i thought Factory reset would have done that.
All 4 Failed
At a loss at this point.
Any help appreciated!
Click to expand...
Click to collapse
I also am having the same issue. I tried once with root, once without, reset device and even tried removing my sd card. And it still fails. I have never done anything but root my device so im also very confused.

str33tprintz said:
I also am having the same issue. I tried once with root, once without, reset device and even tried removing my sd card. And it still fails. I have never done anything but root my device so im also very confused.
Click to expand...
Click to collapse
The only way may be to revert all the way back to 4.4.2 and start a fresh (watch out for all your data - back it up as this will wipe it probably)

blueether said:
The only way may be to revert all the way back to 4.4.2 and start a fresh (watch out for all your data - back it up as this will wipe it probably)
Click to expand...
Click to collapse
I started to install 4.4.2 with adb in recovery following Doomlord's guide but as soon as I give the install command adb suddenly cannot see my device ?
Adb commands work fine up until that point, I'm throughly confused now. Do I need to unlock my bootloader to do that? I was under the impression that root and unlocked BL were not necessary for that.

I used towelroot to root my phone about a month ago. I read somewhere that the OTA update to Lolipop won't take unless it is absolutely stock. I am nopt the most knowledgeable about these things, so what exactly did using towelroot do that made it impossible to update to Lolipo OTA? How to I fix it so that Lolipop can be flashed to my phone? Thanks!

There's a 4.4.2 flashable zip I saw.
Can that not be flashed from the sdcard?

rockky said:
There's a 4.4.2 flashable zip I saw.
Can that not be flashed from the sdcard?
Click to expand...
Click to collapse
I did read about going back to 4.4.2, but was unable to cohesively follow it. I think that people were having trouble downgrading. Also, would that make my phone totally, absolutely stock? Kind of hijacking the thread, but it is still relevant to the OP's issue. I don't mind spending time on something if I know the outcome will get me to where I want to be. Thanks!

jeraldjunkmail said:
I did read about going back to 4.4.2, but was unable to cohesively follow it. I think that people were having trouble downgrading. Also, would that make my phone totally, absolutely stock? Kind of hijacking the thread, but it is still relevant to the OP's issue. I don't mind spending time on something if I know the outcome will get me to where I want to be. Thanks!
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showpost.php?p=57338156&postcount=97

Related

[Q] please help...

Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...

Data recovery HELP - Bricked phone

Sorry for the duplicated post. I just noticed the other one i posted is in the wrong section and this is the one for the AT&T phones so here it is again.
Hi Guys. Today i rooted my phone for the first time (LG Optimus G e970)
Everything went well, then i uninstalled the bloatware from AT&T and a few of the google apps that i do not use like books or music, and on the next reboot i got my phone bricked with the LG loop and "Security Error" message.
I found some great info on these forums on getting the phone in working condition with the help of this: http://forum.xda-developers.com/show....php?t=2388440
However, before i go ahead and restore the phone's original firmware, i would like to know if there is anyway to recover some of the files. I have some important notes i wish to recover, everything else is on google and the external SD card so im not all lost.
I am able to put the phone in download mode by holding the up and down volume keys and then powering on the phone with the usb cable connected to the PC, but it is not showing as an external disk on the computer. I do have the LG drivers installed tho, the same ones i used to root the phone.
Any ideas?. thanks a lot.
What recovery do you have ? You may be able to mount internal and sd card in recovery and access them on your computer ?
optimusv45 said:
What recovery do you have ? You may be able to mount internal and sd card in recovery and access them on your computer ?
Click to expand...
Click to collapse
Hi thank for the help.
I have no clue about what recovery i have. I never played with the phone before the rooting and removal of the apps, so i believe it should be the "stock" recovery if you wanna call it like that.
axopro said:
Hi thank for the help.
I have no clue about what recovery i have. I never played with the phone before the rooting and removal of the apps, so i believe it should be the "stock" recovery if you wanna call it like that.
Click to expand...
Click to collapse
I don't know what guide you followed to get the root. If you followed this
http://forum.xda-developers.com/showthread.php?t=2450258
You should have twrp. Stock recovery may not be able to mount storages for uses on PCs.
Also I haven't seen the post you included , maybe that's an older post. A lot of people use this to recover their "bricked" phones
http://forum.xda-developers.com/showthread.php?t=2230994
I personally have followed this too.
As long as you have download mode you don't have to worry. However you need to read carefully before processing with teenybins because its something that can actually brick your phone if used wrong.
optimusv45 said:
I don't know what guide you followed to get the root. If you followed this
http://forum.xda-developers.com/showthread.php?t=2450258
You should have twrp. Stock recovery may not be able to mount storages for uses on PCs.
Also I haven't seen the post you included , maybe that's an older post. A lot of people use this to recover their "bricked" phones
http://forum.xda-developers.com/showthread.php?t=2230994
I personally have followed this too.
As long as you have download mode you don't have to worry. However you need to read carefully before processing with teenybins because its something that can actually brick your phone if used wrong.
Click to expand...
Click to collapse
Ok so when i did the rooting i followed that same guide you linked to, but i only did it to the root part. Not the "UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-"
I just wanted the permissions to remove the apps.
So now with the TeenyBin guide.... will that erase the current settings and information on the phone or is it just an attempt to fix the firmware loop?
will the process attempt to restore the google apps missing?
axopro said:
Ok so when i did the rooting i followed that same guide you linked to, but i only did it to the root part. Not the "UNLOCK BOOTLOADER AND INSTALL CUSTOM RECOVERY-"
I just wanted the permissions to remove the apps.
So now with the TeenyBin guide.... will that erase the current settings and information on the phone or is it just an attempt to fix the firmware loop?
will the process attempt to restore the google apps missing?
Click to expand...
Click to collapse
There are different kind of teenybins. They do different things, one giving you a working recovery and updating RPM/TZ, one restoring your phone to complete factory state. You will have to read it to know what I'm saying here. The one that give you twrp and update your partitions may let your data alone but you will most likely still have the existing bootloop. The gapps missing ? The ones you deleted ? If you use the bin that recovers phones to factory state then you will have all the stock apps again.
Quick update.
I was able to recover the phone and the data in it. :good:
I installed the new boot loader with the teenybin instructions and was able to backup the data partition to an SD card.
Anyway, after that i went for a recovery using the stock firmware and LGNPST and now i lost the boot loader with all the neat options, but got the phone working again, and to my surprise, everything was back there including data and applications,. i dont get it but oh well... im back alive.
Ill backup all the important stuff from now on, and then i will keep messing with the phone again LOL. i learned quite a few things today... ill read more from now on before doing more things.
Thanks for all the help.!!
Good nite

[Q] Need some help with bricked 8.9

Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
ok
enjid said:
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
Click to expand...
Click to collapse
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
jimyv said:
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
Click to expand...
Click to collapse
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
?
enjid said:
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
Click to expand...
Click to collapse
.
Safestrap was booting?
jimyv said:
.
Safestrap was booting?
Click to expand...
Click to collapse
Yup. Still is.
?
enjid said:
Yup. Still is.
Click to expand...
Click to collapse
What was your original system version? And which safestrap version?
jimyv said:
What was your original system version? And which safestrap version?
Click to expand...
Click to collapse
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
did
enjid said:
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
Click to expand...
Click to collapse
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
jimyv said:
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
Click to expand...
Click to collapse
Well... thank you. I messed up my backup of stock, so I couldn't just roll back. I thought I had tried flashing a bin, but I looked again and it was something I downloaded from a forum (so either a bad d/l or bad file in general).
Anyway, I did as you suggested with a brand new Amo download and it worked. Thank you for your help and patience.

Hard brick of death

so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Ilikecheese said:
so ive rooted and flashed twrp on here, and everything was good, so i go to install jasmine ROM, and it tells me to erase everything, which i did and i made sure not to check sd_ext or internal storage, and afterwards it erased litterally everything. all my files, so the rom was gone, and i went to recover my back up but that was gone too! now it sits at the lg screen with the light flashing. i can get into system recovery but nothing else. so i cant do the lgflash thing so thats off the table. no download mode or bootloader either. its practically a paperweight but i want to know if any of you guys would know if i can fix this or just send it in.
Click to expand...
Click to collapse
you could try putting the sd in your pc to put the rom back on it, then back and try flashing. if that fails, sounds like its toast.
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Ilikecheese said:
i dont have one to begin with, but do you think if i used a mates phone with an sd card, and just download the rom i was gunna use, then put it in my phone, if that would work? seems like it in theory.
Click to expand...
Click to collapse
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Jewveeski said:
Yes use an sd card download the Rom onto the sd via pc then put it in your phone boot into twrp install via ext-sd you should have no problems
Click to expand...
Click to collapse
thank you so much for the help (; ill let you know if i succeed
I think you will be okay, maybe try LG Flashtool and usb flash back to stock if those don't work.
I got it. Put the Rom in sd and it worked perfect. Whooo
Whew!..congrats.:good:
For some reason I can't flash from recovery menu..failed to mount sd/card, unknown error 150...
Maybe your SD is formatted in a file system twrp doesn't recognize? I had to reformat my 64gb to fat. I used twrp's built-in advanced wipe function to change external SD file system to fat, others have used a pc-based tool from ridgecomp.
You end up with the couple GB maximum individual file size limit, but I just copied my 11c 2.8gb system.img onto it without any trouble.
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
richsapf said:
Augh.. now I can't even root. I rooted via ioroot, then wanted to unroot so I could do the 11C OTA, but could not unroot via the way I practiced using LG flashtool using port 41. For some reason it would just stay at 0%(worked fine before) so I used Simply Unroot..SU said unrooted but I did not look at software status which now reads "modified".
Now I can't adb despite reinstalling lg drivers
I tried these 5 root methods
for Verizon VS985-11C
IOROOT= Phone reboots to a blank screen, pc says "no adb device found and phone does not show any recovery menu, just the android robot on his back with a red triangle.
STUMP= Phone says cant because of a patch?
TOWELROOT="Device not support"
PURPLEDRAKE=Same, no recovery menu despite hard button recovery(I wiped cache and did a factory reset via power button/vol down) That's the ONLY recovery menu I see. It is a different looking menu all white w/ grey boxes. It does not look like a normal recovery menu. So the 11C update must have changed that??
Where or where is my blue and red recovery menu?
ROOTTOOL= Same thing with the adb.
These root attempts are rebooting the phone into recovery when usb attached but then it just shows the robot, and pc then says "no adb device found" So I can't even side load it with command prompt.
Maybe after all this root is resolved, I will work on the sd card..lol..
I can't believe I can't even root and I am flagged as rooted!
Thanks for any help,
Click to expand...
Click to collapse
You might be on the 11C update. Try downgrading (there's a thread in here somewhere) to 10b and you should be solid. I don't know if those numbers are correct, but check your build number.
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
B-Nice_88 said:
I'm having a similar issue. I was rooted and had TWRP installed. Verizon kept prompting to update and I accidentally hit update now. So my guess it's trying to get to the stock recovery and update; however TWRP is installed. How can I flash stock recovery via TWRP? I can't do anything and no matter if I reboot to system it's still redirecting to recovery to update I assume...HELP!!! I can't mount anything either!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And this check this for blocking an OTA: http://forum.xda-developers.com/lg-g3/development/psa-stop-taking-ota-updates-update-t2909412
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
richsapf said:
I'm sorry, I did forget to say that the OTA from 10B to 11C was done because I thought I could just re-root
One odd thing. I am now not rooted, but "modified", so is that why I am able to still edit files on my sd-card. Kit-Kat blocked editing of files. At least I can edit. Bit if I format the card will it affect the edit thing?
Thank you
Gonna try your suggestions above
Click to expand...
Click to collapse
Never ever take an OTA if you're rooted. In the future, just get rid of the notification, and then come here. Better yet - after you root, disable updates entirely.
Also, another reason to not take an OTA is because often times there are anti-rollback code in them, just like there is almost always a root patch. The regular "usb back to stock" and all the current root methods don't work on 11C for that very reason, and you have to use the KDZ method instead. If you jump on an OTA too early and find out there isn't a way to get back to the previous version... you're stuck. That happened to tons of people on one of the Galaxys I heard, and it so happened that the patch was a very good one. I've heard that the people who took that OTA are still stuck with it.
For 11C, there were early reports of those that rooted, but did not Bump or edit the system, got lucky and sometimes kept root after the OTA. Have you used a root checker to confirm you don't have root? None of the root methods are going to work on 11C, but you might still have it. If you don't, or something else is messed up, you'll need to get back to 10B to fix it.
Edit: Also, you're going to want THIS thread, not the other two I posted!
I did unroot before ota.. the only way I could at that time, via simple root. I just wanted to get the OTA out of the way(dont know why)
I used root checker, says no root.. If I go back to 10B I will try KDZ; or can I use the LG flashtool and try again with that using port 41, the 10B .dll, and 10B TOT?
For now I will follow your link and do as instructed..
Thank you laura
richsapf said:
I did unroot before ota.. the only way I could at that time.
Click to expand...
Click to collapse
Did you do anything else when you had root? Change anything in the system at all?
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
richsapf said:
Thank you soo much! It worked. 10B "Official"..
Then ioroot perfect..
Where is the "Thank you" button I read people saying to push??
I do have couple questions. Should I format the sdcard? Its 64gigs(reading 58gigs), new and reads/writes well; But I am back to my original prob. I installed TWRP and it found my deodexed stock10b.zip but in recovery menu it's back to not seeing any zips at all. I don't think that formatting will help that but I can try if you think that might be it.
thank u again
Rich
---------- Post added 11th November 2014 at 12:53 AM ---------- Previous post was 10th November 2014 at 11:59 PM ----------
I forgot to actually answer your question.
No I was very careful to not change any system files. Its beyond my scope, as you can see..
This is such a cool phone. I had a droid 4 for two years and did not root..yah 2 years..because of the Que 0/0 root counter. But with this phone, there's no way I'm not rooting and just would like deodexed because I am under the impression the theming is easier / more flexible. Something about the file system structure being more compressed?
Click to expand...
Click to collapse
Awesome! And yes, the sd card needs to be reformatted as fat32 for TWRP to see it.
Now that you're back on 10B, you can get the 11C update again if you want using this. The 11C OTA already has a rooted, deodexed flashable zip.
I do have that exact Rom/zip on both internal and ext card. Is there a program in particular to format, or just any, and should I format via pc(hook up usb with Windows 7), or is there a good .apk app.
Also, is 64gigs in any way too much.
Could I go up to 128gigs provided I use fat32.
Should the allocation just stay default? It looks like I can go up to around 4 mbs. Is that a cache type thing.
Sorry I am bombarding all these questions. I love learning this stuff. Need a break from studying for comptia 801/802.
Last, where is the thank u button?

5.0.2 upgrade ERROR -- PURE STOCK

I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse

Categories

Resources