Related
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...
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
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.
Hi,
I have an Amazon Fire HD 7(Ariel).
I wanted to get Android 5.2.2 on this and root it so I could get GAPPS and many more.
My Fire was on 4.5.5 so I used this guide to downgrade to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
All went well and I followed all the instructions on the guide. I got root, installed TWRP and now I wanted to install lollipop.
So I followed this guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I went to TWRP, flashed everything and in the end, when I had to reboot to recovery, I accidentally swiped the "Swipe to install SuperSU" prompt.
Now my Fire is stuck on a black screen. It won't do anything when it's connected to a computer except connect/disconnect constantly.
I think it's in a bootloop where the screen does not turn on.
All I see on the few moments it stays connected in Device manager is MT65XX Preloader.
Do I need to get it to fastboot ? Do I need to buy a factory cable ?
What can I do now ?
Trix123 said:
. . .
All went well and I followed all the instructions on the guide. I got root, installed TWRP and now I wanted to install lollipop.
So I followed this guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I went to TWRP, flashed everything and in the end, when I had to reboot to recovery, I accidentally swiped the "Swipe to install SuperSU" prompt.
. . .
What can I do now ?
Click to expand...
Click to collapse
Problem wasn't installing SuperSU, which was correct thing to do. See below.
dardack said:
I bought a used one off eBay. Booted up fine. Side loaded king root. It failed to root. After settings screen was blank flickering. So I rebooted. Same flickering. So booted into recovery and did factory reset. Now it's in boot loop. It gets to upgrading then back to fire logo. Then starting applications then back to logo. Then stays on logo. Been 30 minutes. Tried twice. Any help.
Click to expand...
Click to collapse
Sounds like Amazon OTA updated you at just the wrong time.
If you haven't been following these forums, see this. Sorry to say, you guys are bricked. If you're still under warranty, contact Amazon for replacement.
Hmm. I disabled OTA updates via JMZ FireTools on 4.5.3. That shouldn't have happened.
Well, is there anything I can do as a last resort without replacing it ?
It has been constantly rebooting. It gets recognized as MT65xx preloaded in Device Manager, goes offline and comes back on again ?
I've let the battery drain completely, so what do I do now ?
If you can help me get it into fastboot or adb then I can fix it myself.
-Thanks.
Trix123 said:
Hmm. I disabled OTA updates via JMZ FireTools on 4.5.3. That shouldn't have happened.
Well, is there anything I can do as a last resort without replacing it ?
It has been constantly rebooting. It gets recognized as MT65xx preloaded in Device Manager, goes offline and comes back on again ?
I've let the battery drain completely, so what do I do now ?
If you can help me get it into fastboot or adb then I can fix it myself.
Click to expand...
Click to collapse
You overrode and wiped JMZ's OTA block when you upgraded in TWRP. The best explanation is in the post I linked to above. If you look at other threads you'll see this happened to several people yesterday. You can't get out of the loop, so can't get into fastboot or adb. All you can do is contact Amazon for a replacement for a bootlooping tablet. (If you can't think of a plausible explanation, wait a few days until tablet would get update (which it can't, of course) and blame it on that.)
DoLooper said:
You overrode and wiped JMZ's OTA block when you upgraded in TWRP. The best explanation is in the post I linked to above. If you look at other threads you'll see this happened to several people yesterday. You can't get out of the loop, so can't get into fastboot or adb. All you can do is contact Amazon for a replacement for a bootlooping tablet. (If you can't think of a plausible explanation, wait a few days until tablet would get update (which it can't, of course) and blame it on that.)
Click to expand...
Click to collapse
I contacted Amazon and they will be sending me a replacement.
Is there any way to make this tablet work again ?
That way, I could just cancel the replacement from Amazon and that would save a lot of time.
Thanks.
Help me please )':
Hello i am french sorry for me english
i have identical problem
What would I say in sav amazon for replacement my kindle fire please :l
Thanks you !
Sorry if this is already answered, but I searched around and couldn't find it.
I tried to flash to CM12, but I have too old of a bootloader.
I reverted everything to stock, but I have never been able to get any OTA updates.
I downloaded the 322 update from huawei's site (from her http://consumer.huawei.com/us/support/downloads/detail/index.htm?id=52043) but when I try to install it from my SDCard I get the following error:
oemsbl version list check error!
'E ,write data error
Error:update.app is a invalid package
Error:SD card update failure,SD card update abort!
My end goal is to get on CM12 or some other rom that lets me get rid of all of the stock rom craziness.
Any ideas or can someone point me in a direction?
Thanks in advance!
bot2600 said:
Sorry if this is already answered, but I searched around and couldn't find it.
I tried to flash to CM12, but I have too old of a bootloader.
I reverted everything to stock, but I have never been able to get any OTA updates.
I downloaded the 322 update from huawei's site (from her http://consumer.huawei.com/us/support/downloads/detail/index.htm?id=52043) but when I try to install it from my SDCard I get the following error:
oemsbl version list check error!
'E ,write data error
Error:update.app is a invalid package
Error:SD card update failure,SD card update abort!
My end goal is to get on CM12 or some other rom that lets me get rid of all of the stock rom craziness.
Any ideas or can someone point me in a direction?
Thanks in advance!
Click to expand...
Click to collapse
Does your phone really have B146 or do you have B148 or B126?
You're on the right path. You must first successfully install B322 before you can install CM or any other non-stock ROMs.
Make sure you follow the Huawei B322 upgrade instructions very carefully.
See http://forum.xda-developers.com/asc...icial-b322-available-public-download-t3193929
divineBliss said:
Does your phone really have B146 or do you have B148 or B126?
You're on the right path. You must first successfully install B322 before you can install CM or any other non-stock ROMs.
Make sure you follow the Huawei B322 upgrade instructions very carefully.
See http://forum.xda-developers.com/asc...icial-b322-available-public-download-t3193929
Click to expand...
Click to collapse
Your edit is looking at the same thing I was looking at I had followed those directions but it looks like the issue is that I am on b146. The build number that shows up on my device is MT2-L03V100R001C642B146.
I guess I need to poke around and see if I can get it on B148 first, then try the update again, but B148 might have a prereq of B126
Madness!
Either way it is late, so I might just leave it be until tomorrow and pick back up. Thanks for the help!
Edit:trying to download B148 now, they are both 4.3, so who knows how this is going to go
I know Huawei has files and instructions to go from B322 back down to B148. I don't know anything about B146.
The B322 instructions reference B126 and B148, but no mention of B146.
divineBliss said:
I know Huawei has files and instructions to go from B322 back down to B148. I don't know anything about B146.
The B322 instructions reference B126 and B148, but no mention of B146.
Click to expand...
Click to collapse
Yep, I am downloading B148 and am going to try to install it. If that doesn't work, I will probably follow the soft bricked instructions to force wipe it back to B126 and then roll forward from there.
Good times!
B146 is Consumer Cellular phone. Not stock mate 2.
After all the madness, I hope you are not like some who don't like the new stuff and end up downgrading ... Time for me to zzzzzzz.
divineBliss said:
After all the madness, I hope you are not like some who don't like the new stuff and end up downgrading ... Time for me to zzzzzzz.
Click to expand...
Click to collapse
I was able to successfully install B126, but it is time for zzzz's here too. I doubt I will want to downgrade, my biggest complaint is the alternate default apps that Huawei uses cause some weird behaviors with bluetooth integration. Especially with my car, my headphones and the Pebble. And even if I use the normal apps (music etc) the integration doesnt work at all since their rom doesnt see them as the default system app.
Plus I have used CM on some other devices and always liked it
Moody66 said:
B146 is Consumer Cellular phone. Not stock mate 2.
Click to expand...
Click to collapse
I might have accidentally installed it at some point returning to stock. My phone is on of the sim unlocked phones from Walmart (not the prepaid, just the unlocked).
User error on my part Thanks for the info!
bot2600 said:
I was able to successfully install B126, but it is time for zzzz's here too. I doubt I will want to downgrade, my biggest complaint is the alternate default apps that Huawei uses cause some weird behaviors with bluetooth integration. Especially with my car, my headphones and the Pebble. And even if I use the normal apps (music etc) the integration doesnt work at all since their rom doesnt see them as the default system app.
Plus I have used CM on some other devices and always liked it
Click to expand...
Click to collapse
That awesome.... Should be downhill now.
I suggest you consider skipping CM and install PACROM or Carbon, which are both based on CM. I prefer PACROM. You should also consider Dual Boot / Multiboot - I use it to run multiple ROMs. You could install all three and see which one you like the best.
divineBliss said:
That awesome.... Should be downhill now.
I suggest you consider skipping CM and install PACROM or Carbon, which are both based on CM. I prefer PACROM. You should also consider Dual Boot / Multiboot - I use it to run multiple ROMs. You could install all three and see which one you like the best.
Click to expand...
Click to collapse
Thanks for the suggestion, I will definitely try all three. I am running around all day getting ready for Halloween so it probably won't happen today though, but I agree, things should be relatively straightforward from here
bot2600 said:
Thanks for the suggestion, I will definitely try all three. I am running around all day getting ready for Halloween so it probably won't happen today though, but I agree, things should be relatively straightforward from here
Click to expand...
Click to collapse
I'd personally recommend you install PACROM first ('cause you might like it so much, you won't bother with the other two ) , then once you are comfortable that you have a solid installation, after a few days go install Dual Boot/Multiboot : http://forum.xda-developers.com/ascend-mate2/themes-apps/patcher-multi-boot-t3222899/page1 in order to install some other ROMs.
divineBliss said:
I'd personally recommend you install PACROM first ('cause you might like it so much, you won't bother with the other two ) , then once you are comfortable that you have a solid installation, after a few days go install Dual Boot/Multiboot : http://forum.xda-developers.com/ascend-mate2/themes-apps/patcher-multi-boot-t3222899/page1 in order to install some other ROMs.
Click to expand...
Click to collapse
Thanks, I think I have just hosed it at this point. B126 still works, but it sees no OTA updates and won't take B148, B309 or B322 (guessing on the version numbers I tried). It continues to get the same error. I've reset the phone a couple times, wiped cache etc, but something somewhere makes it sad.
Thanks for the guidance and ideas, but I think the powers that be are telling me to get a new phone. I am trying to decide between the note 5, nexus 6p or wait for the new windows phone (950 xl). I could just buy another MT2L03, but if I am going to spend money on another phone, I might as well get one that I dont have to muck about with to clean up all of the forced apps etc
bot2600 said:
Thanks, I think I have just hosed it at this point. B126 still works, but it sees no OTA updates and won't take B148, B309 or B322 (guessing on the version numbers I tried). It continues to get the same error. I've reset the phone a couple times, wiped cache etc, but something somewhere makes it sad.
Thanks for the guidance and ideas, but I think the powers that be are telling me to get a new phone. I am trying to decide between the note 5, nexus 6p or wait for the new windows phone (950 xl). I could just buy another MT2L03, but if I am going to spend money on another phone, I might as well get one that I dont have to muck about with to clean up all of the forced apps etc
Click to expand...
Click to collapse
You have to go through the CC conversion. You can't just flash a different version to it.
Moody66 said:
You have to go through the CC conversion. You can't just flash a different version to it.
Click to expand...
Click to collapse
Thanks, I know somewhere along the line I must have flashed CC to it when I was restoring it (did a lot of tinkering when I first got it), but I am pretty sure it wasn't originally a CC phone. I picked it up from this link: http://www.walmart.com/ip/HUAWEI-As...M-4G-LTE-Android-Smartphone-Unlocked/42287058 which I read as just being unlocked, not being on any prepaid network.
Like I said earlier, I think it ending up with a CC rom on it somewhere along the way was just user error on my part
bot2600 said:
Thanks, I know somewhere along the line I must have flashed CC to it when I was restoring it (did a lot of tinkering when I first got it), but I am pretty sure it wasn't originally a CC phone. I picked it up from this link: http://www.walmart.com/ip/HUAWEI-As...M-4G-LTE-Android-Smartphone-Unlocked/42287058 which I read as just being unlocked, not being on any prepaid network.
Like I said earlier, I think it ending up with a CC rom on it somewhere along the way was just user error on my part
Click to expand...
Click to collapse
Use Xordos post for repairing a bricked phone. It will get you to b148.
Moody66 said:
Use Xordos post for repairing a bricked phone. It will get you to b148.
Click to expand...
Click to collapse
Ah, I used that post already but grabbed a B126 build instead. I will flip my recovery back and restore to B148 instead, good idea
Don't know what I was thinking at the time to go to B126, but it was really late, so that's my excuse
Edit: I see why I ended up on B126, he says to use the file TWRP_BACKUPS_stock-system-with-root.zip to restore the system partition, that file takes you back to B126, not B148.
Second Edit:I went back to see what files he had in his little area and saw there was a full B148.zip, so I flashed it with TWRP. I might try to update again from there, I assume I can't flash any higher as the B3xx builds the partitions changed, right?
I might have an answer, it looks like this version of the phone might not be supported, though its a bit unclear from the thread, but it does reference the phone that I have.
https://community.gethuawei.com/devices/mate_2/f/2/t/2672
Oh, and it looks like it did come with B146, I think its just time to get a new phone, thank you all for the time you spent though
bot2600 said:
I might have an answer, it looks like this version of the phone might not be supported, though its a bit unclear from the thread, but it does reference the phone that I have.
https://community.gethuawei.com/devices/mate_2/f/2/t/2672
Oh, and it looks like it did come with B146, I think its just time to get a new phone, thank you all for the time you spent though
Click to expand...
Click to collapse
I thought you said you have an MT2-L03 ....... does that not imply it's 16GB flash memory/ROM?
Did you put he B126 recovery back on the phone with your B126 ROM? My phone (non-CC) came out of the box with B148, then I went to B322, then PACROM, then Dual Boot, etc, etc.
Hopefully, you can get this to work ....... even if your heart is sent on a new phone. Then you can sell this one or give it to family, etc, etc .... maybe get some money out of it . Good luck.
divineBliss said:
I thought you said you have an MT2-L03 ....... does that not imply it's 16GB flash memory/ROM?
Did you put he B126 recovery back on the phone with your B126 ROM? My phone (non-CC) came out of the box with B148, then I went to B322, then PACROM, then Dual Boot, etc, etc.
Hopefully, you can get this to work ....... even if your heart is sent on a new phone. Then you can sell this one or give it to family, etc, etc .... maybe get some money out of it . Good luck.
Click to expand...
Click to collapse
Looks like I was wrong, mine is 16 gig, so ignore that link
I am not set on a new phone, but I am set on being done mucking about, I have a couple apps like RSA token things etc that are a pain when I wipe my phones. I am pretty sure I bought mine before B148 came out, but who knows, it all melts together. I write mobile apps for work so I have a bunch of random iphone, android phones and even a couple windows phones lying around, but this one has me so spoiled by its big screen, that I can't imagine going back to anything 5" or smaller, and the wife claimed the 6S plus, so what are you going to do
I might mess around with this a bit more, but Monday fast approaches and it is time to be productive again