Dear all,
I am asking for the solutions to solve this issue.
The device goes into bootloop after updating to 5.0.2.
It was known that the device has not enable OEM Unlock through development options. (and cannot get into setting page at this moment.)
Therefore, i cannot unlock the device by using
"fastboot oem unlock" in the fastboot mode of the device.
I have tried wipe data and perform factory reset in recovery mode.
but the device still get into bootloop.
May i ask for any possible solution for flashing back stock rom?
I'm in the same situation. I believe the only solution is to return the device for "repair".
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
GrillMouster said:
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
Click to expand...
Click to collapse
I am having the same problem. I tried wiping the cache from recovery as well as doing a full reset, and still stuck. HTC is suggesting sending them the device.
FWIW, I am locked/unrooted and running stock.
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
penguinolog said:
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
Click to expand...
Click to collapse
Were you able to fix it? I'm having the same problem, I just can't believe it's not possible to unlock the bootloader any other way.
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
cobyman7035 said:
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
Click to expand...
Click to collapse
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
cam30era said:
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
Click to expand...
Click to collapse
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
That's good news. Glad to hear it.
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
Simply switching "Enable OEM unlock" doesn't void your warranty, and it covers your butt in case something happens.
Related
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
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
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
octagonPerfectionist said:
what version of android to you currently have installed? is it 5.0.1 or 5.0.2? also, i'm guessing the reason it's not updating is because you have a custom recovery installed. if you flash the stock recovery again it should be able to update. i could help you out with that but it's a bit of a long process for a beginner haha. you can check by booting into fastboot by pressing and holding power + volume down while it's shut down until the fastboot screen shows, then scroll down to recovery with the volume keys and click on it with the power key. if you have twrp or something installed it'll show a splash screen then give you a gui but if it's the stock recovery it'll be an android mascot laying down with a warning sign above it.
Click to expand...
Click to collapse
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
livinginavacuum said:
It's 5.0.2. I have stock recovery and already tried the option "wipe data/factor reset" which still doesn't allow for me to update OTA.
What should I try next?
Click to expand...
Click to collapse
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
download this: https://android.googleapis.com/packa...L.5cb0c625.zip
install ADB: https://developer.android.com/sdk/index.html (scroll down and download SDK tools only)
and sideload it by following these instructions: http://www.androidcentral.com/how-ma...r-nexus#slide2
note that these instructions were assuming you are on a mac, instead of doing a ./fastboot or ./adb command just type fastboot or adb, no need for the ./
also, you're sideloading the OTA, not flashing the factory image so don't unlock the bootloader and skip the part that talks about flashing the factory images. also iirc once you see the recovery screen with the error looking message, you should press volume-up first then power to bring up the menu? i remember running into a bit of a snag there when i did this last since it says to do it the other way around. anyway hopefully this will update it. if not, you're probably gonna have to flash the factory images, which would need an unlocked bootloader. SO, in case if you do need to unlock the bootloader (which will wipe the device), be absolutely sure to flip that little switch in developer options that allows OEM unlock, otherwise you might be left with a bricked device.
Click to expand...
Click to collapse
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
livinginavacuum said:
Hey guys, I have an unlocked Nexus 9 and updating to 5.1 OTA isn't possible (as most of you probably already know). I have no idea what I am doing and only unlocked it because RootJunky had some automated program that basically did it for me. Now I'm stuck trying to figure out how to update manually...
My simple question is how do I revert back to a version (locked?) that will allow me to update via OTA and not have to deal with this going forward? Idiot-proof responses are most welcome.
Click to expand...
Click to collapse
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
octagonPerfectionist said:
well the OTA is currently rolling out in stages so most people won't be getting it quite yet the normal way. if you wanted it sooner, you could try sideloading it. it's a bit of a pain but it works just as well as just waiting for the OTA to show up by itself. lemme just copy & paste something i typed out the other day in another thread:
you could also flash the factory image but this way is honestly a bit easier and gives the same result. i've never been able to get the .bat file to actually automate it properly before haha
Click to expand...
Click to collapse
Your first and third link don't seem to work.
doitright said:
You don't need to ota to update.
Read the instructions here;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Easier said than done for someone who has no clue. Is there a good youtube video?
livinginavacuum said:
Your first and third link don't seem to work.
Click to expand...
Click to collapse
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
octagonPerfectionist said:
sorry about that, here's the first link again. the forum must have truncated it because it was too long: https://goo.gl/CkF7J6
here's the third one with a link shortener too, for some reason the forum won't let me post the long version: http://goo.gl/XevxkJ
Click to expand...
Click to collapse
First one doesn't work! LOL. I'm sure it's not you.
livinginavacuum said:
First one doesn't work! LOL. I'm sure it's not you.
Click to expand...
Click to collapse
haha fml apparently google doesn't like links to the ota zip well anyway just google "nexus 9 ota zip" and it's pretty easy to find.
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
I dont own a Z3V however i own a Z3, i haven't experienced boot loop on the Z3, however i have with previous Xperia Devices i solved the issue by installing Flashtool and downloading my stock FTF file.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Whoever told you that you can install these doesn't know the z3v. It's a different phone from any other z3 and can't take those custom Rom.
Your best solution is to try the tft install as described in the downgrade section of the root thread. That would bring you back to a stock Verizon.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Sorry I did not check your PM much earlier to prevent you from doing this. Whoever did tell you about flashing a custom rom sure does owe you another phone. You have to wait until Verizon brings out the Lollipop rom, but until then, you have to somehow flash back to the original rom that came with. 4.4.4 is enjoyable enough as it is, just the lack of volte is what's the wait for on the Lollipop rom.
A rep told me today that when the Z4v, there's sure likely a quick follow up on releasing the update since they may as well base it off of it. And that's hoping if the new one even gets VoLTE...
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Seannnn said:
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Click to expand...
Click to collapse
to connect in flashmode you need to hold volume down and connect the phone to the pc with a usb cable
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
It's a good thing you were fortunate enough to have it replaced with no charge. Now don't make that same mistake again and wait like the rest of us. At least you confirmed for sure that flashing an incompatible ROM is death of the phone. lol
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
yes you can... simply exclude warranty on non OEM code... very simple to solve....
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
That is why the Z3v has a hash code on the phone that shows when you root it and can't be flashed over so they know if it has been rooted even if you flash back to the correct firmware. "Settings>About phone>Status" You send it in they charge you full price.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
Uh, VZW says it is about the "network", not bad flashes on phones. So which is it?
If VZW wasn't so anal about rooting Sony lets you root in a foolproof way, failed rooting is VZW's fault if it happens.
Any one got the solution.... my phone not working
shashikiran said:
Any one got the solution.... my phone not working
Click to expand...
Click to collapse
What did you do this time?
no recovery mode
GigaSPX said:
What did you do this time?
Click to expand...
Click to collapse
flashed flashable prerooted.zip file and not even getting recovery mode, no charging symbol, only can access fastboot mode. continiously rebooting with vibration. no display
My Z3v is rooted and is working just fine, except the annoying ads I get on my quick charge screen, now.
Anyway... I assume you haven't tried to use the Sony/Verizon Software Upgrade Assistant? It comes on your phone to install to your PC and lets you upgrade (probably never gonna get an upgrade) and factory your phone over USB. Not sure if you can download it, or if it only comes on the phone as a separate partition to install from. Can't hurt to try.
I got a new Motherboard and daughterboard in my HDX Apollo. I was able to get TWRP on it, but it keeps saying i dont appear to have root. I tried installing the latest supersu but it apparently didnt work. Anyway, i have realized that i just keep getting myself into trouble playing with root. All i want is to get my 3rd gen back to 4.5.5.1 fire os and wait for the fire os 5 update for it(hopefully) Any help on how i can do that? Ive tried downloading the latest Kindle update for apollo, renaming the .bin to update.zip and transferring it over and installing it but it never boots further than the 'kindle' screen.
Thanks for your help, sorry to be a pain
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
Click to expand...
Click to collapse
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Sent from my SM-G920V using XDA-Developers mobile app
mhuck0625 said:
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Click to expand...
Click to collapse
mhuck0625 said:
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Click to expand...
Click to collapse
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Davey126 said:
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Click to expand...
Click to collapse
I installed TWRP using the method instructed here: http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
When i want to get to TWRP i press and hold Power + Vol UP until it rebootes into the Teamwin screen and TWRP. It is version 2.8.7.0 now(the instructions got 2.8.5.0 installed then i upgraded)
I dont remember what the graphic looked like when booting into TWRP but i know it said TeamWin. I can check when i get it charged back up enough to turn on. Ive had it sitting unplugged for days and the battery ran dead. I hope this is enough info to help get me pointed in the right direction. Thanks!
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Click to expand...
Click to collapse
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Cl4ncy said:
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Click to expand...
Click to collapse
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
mhuck0625 said:
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Click to expand...
Click to collapse
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Davey126 said:
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Click to expand...
Click to collapse
Ok, so i will need root to install ROMs then? How do i solve my problem unlocking the bootloader?
mhuck0625 said:
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
Click to expand...
Click to collapse
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Sent from my SM-G920V using XDA-Developers mobile app
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
mhuck0625 said:
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Click to expand...
Click to collapse
mhuck0625 said:
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
Click to expand...
Click to collapse
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Davey126 said:
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Click to expand...
Click to collapse
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
mhuck0625 said:
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
Click to expand...
Click to collapse
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Davey126 said:
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Click to expand...
Click to collapse
You have no idea how much i appreciate the help!
I look forward to hearing what you come up with!!
I would be happy just going straight back to full fire os - Stock EVERYTHING and not even worrying about running another OS. I just want to have a usable tablet again!