hey guys.
initially when i tried to install 4.1.2 it kept giving errors so i found (on xda i believe) a modded zip that didnt do the google checks and it installed.
however, now that i try to install 4.2, firstly with the official update that it offered automatically and when that failed with a zip, all i get is the android on his back and a red exclamation. i believe that means i dont have the CWM installed anymore that i am sure i needed when i flashed 4.1.2 (i definitely didnt use my PC to do that update)
do i have to install CWM again? can it be done without ADB as i havent used it very much at all and not for a long time.
thanks
anyone?
the reason the question is different to some others and warrants a seperate thread is that the bootloader is already unlocked and the device is rooted yet i dont have CWM to flash the manual way.
whether auto update or manual it brings up the android with red exclamation mark.
Related
I got my nexus 7 wifi onlu (4.1) and it shows an update available of 4.2.
I just want to save my Wifi Data Traffic ... So wished to update manually ....
googled and found solutions ...
http://www.androidauthority.com/how...nexus-7-and-nexus-10-to-android-4-2-2-156784/
but the recover mode method confused me , i thought it need adb .... is the above link specifies an update rather than a complete ROM flashing
So my question is this
1.
can i update using the Downloaded Zip using recovery mode in nexus?
2.
The link i gt my net has two different size one
http://r2---sn-o3o-itqe.c.android.c....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (47mb)
https://dl.google.com/dl/android/aosp/nakasi-jdq39-factory-c317339e.tgz (275 Mb)
Why the File size differs ? is the first one an Update Zip and second One a complete ROM ?
3. Do i need adb installed to update from recovery ?
I dont wanna root and install CMW now ... will try later ... im using a DEFY for last 2 years and flashing many ROMS ...so i know basic android terminologies ... thanks in advance ... please reply ...
For a pure stock device with a locked bootloader, the only upgrade path is via OTA file bundle if you insist on keeping the bootloader locked. The large (complete) factory images can only be used with fastboot and an unlocked bootloader.
To do the OTA manually, rather than via automatic WiFi download , I recall that the stock recovery no longer has a "update.zip" menu choice, but instead has a menu choice for ADB sideload*. This implies that you need to get ADB working ahead of time to manually apply the OTA.
You are correct about the two file types - the smaller one is a differential patch set (OTA), and the larger a complete factory ROM for use with fastboot as mentioned above.
Because the OTAs are patch sets they are tightly matched to the version of software on your tablet... and you said something vague about your current software version. For instance, you mentioned the OTA file
6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
... but said that you have "4.1"
4.1.2 would be JZO54K, not JOP40D (which is 4.2.1; JDQ39 is 4.2.2)
So, please state your exact software version number you currently have - and the version you want to go to. And have a look at the OTA thread
*might depend on which version of stock software you have on the tablet.
thanks ....... i dnt have nexus 7 with me now (my wife took it for some office works)and so cant verify the version .... But i remember its 4.1 and it no updates was done after i gt it ....
and thanks for pointing the mistake that 47mb zip was for 4.2.1 to 4.2.2 and not for 4.1 to 4.2.
i got http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JZO54K.da55f917.zip link from XDA Link ...
Now tell me can i use this file ??
i cant directly Update using recovery menu .... ???
and i need to unlock bootloader to use ADB ??
bftb0 said:
For a pure stock device with a locked bootloader, the only upgrade path is via OTA file bundle if you insist on keeping the bootloader locked. The large (complete) factory images can only be used with fastboot and an unlocked bootloader.
To do the OTA manually, rather than via automatic WiFi download , I recall that the stock recovery no longer has a "update.zip" menu choice, but instead has a menu choice for ADB sideload*. This implies that you need to get ADB working ahead of time to manually apply the OTA.
You are correct about the two file types - the smaller one is a differential patch set (OTA), and the larger a complete factory ROM for use with fastboot as mentioned above.
Because the OTAs are patch sets they are tightly matched to the version of software on your tablet... and you said something vague about your current software version. For instance, you mentioned the OTA file
6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
... but said that you have "4.1"
4.1.2 would be JZO54K, not JOP40D (which is 4.2.1; JDQ39 is 4.2.2)
So, please state your exact software version number you currently have - and the version you want to go to. And have a look at the OTA thread
*might depend on which version of stock software you have on the tablet.
Click to expand...
Click to collapse
v2dare said:
thanks ....... i dnt have nexus 7 and so cant verify the version .... But i remember its 4.1 and it no updates was done after i gt it ....
Click to expand...
Click to collapse
The EXACT version is needed in order to choose the correct OTA file, there have been five different versions of "4.1" for nakasi. See here.
v2dare said:
i got http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JZO54K.da55f917.zip link from XDA Link ...
Now tell me can i use this file ??
Click to expand...
Click to collapse
Only if you have JZO54K on your tablet. As I noted, there was more than one version of "4.1"
v2dare said:
i cant directly Update using recovery menu .... ???
Click to expand...
Click to collapse
Depends on what version you have.
v2dare said:
and i need to unlock bootloader to use ADB ??
Click to expand...
Click to collapse
No. You only need to unlock the bootloader in order to flash partitions or boot arbitrary images with fastboot. ADB sideload does not need an unlocked bootloader.
I can't help further until you know the exact version number. (I'm going to bed now anyways)
gudnyt :victory: will update after getting the exact version..
i updated nexus from 4.1.1 to 4.2.2 when i gt wifi in my office ....
Now should i clear data and dalvinik cache for better performance ??
You can update to 4.2.2 with fast boot... Don't need root or a custom recovery to do that
Press thanks if I helped ~ Nexus7/Stock4.2.2/MKernel
v2dare said:
i updated nexus from 4.1.1 to 4.2.2 when i gt wifi in my office ....
Now should i clear data and dalvinik cache for better performance ??
Click to expand...
Click to collapse
4.1.1 = one of JRO03C, JRO03D, or JRO03S (but not JZO54K). How did you use the tablet for so long without getting the update already? (Perhaps you just ignored the update messages?)
Clearing the dalvik cache probably won't change anything, but certainly can not hurt. On the other hand though, wiping /data is essentially the same thing as a "factory reset".
(To be clear, "factory reset" in Android-speak does not mean "return to the original firmware" - it means instead "wipe away all traces of user customization".)
good luck
Like i said i gt nexus 7 last week only and while using wifi i noticed some lag in internet speed ... then i checked OS version and found its updating in background....
So i stopped update by clearing the cache and didnt checked for "update available" thereafter as i know it will again start updating the OS....
now gt a Wifi connection, downloaded the 102mb patch and now its 4.2.2
bftb0 said:
4.1.1 = one of JRO03C, JRO03D, or JRO03S (but not JZO54K). How did you use the tablet for so long without getting the update already? (Perhaps you just ignored the update messages?)
Clearing the dalvik cache probably won't change anything, but certainly can not hurt. On the other hand though, wiping /data is essentially the same thing as a "factory reset".
(To be clear, "factory reset" in Android-speak does not mean "return to the original firmware" - it means instead "wipe away all traces of user customization".)
good luck
Click to expand...
Click to collapse
I have a Nexus 7 (Wi-Fi only) stuck on 4.1.1. Build is JRO03S. I got this as a gift for XMas and haven't been able to update it at all OTA. It's stock. I'm able to download the 4.2.2 update just fine, but the problem comes when I'm installing the update. The progress bar gets to about 20-25%, then it stops; this is signified with the android mascot falling down dead with a red exclamation triangle popping out of it's opened chest. Help?
Same problem
anorton02 said:
I have a Nexus 7 (Wi-Fi only) stuck on 4.1.1. Build is JRO03S. I got this as a gift for XMas and haven't been able to update it at all OTA. It's stock. I'm able to download the 4.2.2 update just fine, but the problem comes when I'm installing the update. The progress bar gets to about 20-25%, then it stops; this is signified with the android mascot falling down dead with a red exclamation triangle popping out of it's opened chest. Help?
Click to expand...
Click to collapse
I've got the same problem as this guy. My nexus has been "trying" to update for well over a year and nothing has worked. I cant find much info on the problem outside of suggestions to clear the cache and do the reset but that doesnt help....
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
richdaley said:
Hi All,
I picked up a Defy MB525 on ebay, mostlly to mess with but I need to use it as my daily driver for a while because I am buying a house and my money is tied up for that.
Anyway, it arrived with stock unrooted t-mobile froyo which I am sure you will all agree is unacceptable so i used framroot to root it and installed sndinit 2.3 and followed the instructions in the general section for installing KitKat. I followed the instructions including the note to update the phone to CM10 first which went fine. At one point, I had it running CM10.1 fine but when I installed KitKat, the phone got stuck at the boot screen. The instructions say that it is normal for it to take a long time and you will think you are stuck but I let it sit more than an hour. At that point I thought I was soft bricked so I went back and used RSD Lite to install the t-mobile eclair SBF on it, which is the only one I can find. All links to the Froyo SBF I can find are broken.
That is where I am stuck. When I try to install sndinit, I get no blue light on reboot and on the older versions and I get an SD mount error in the recovery.
I think the probably I am having are related to not having the Froyo firmware installed but when I try to install it the regular way, the phone reboots and I get the triangle with an exclamation point. As I said, I can't find the Froyo SBF. The links I can find are broken and I don't think it is listed here, which is where I found the eclair sbf:
http://sbf.droid-developers.org/phone.php?device=27
My questions are:
Does anyone know where to find the most recent t-mobile sbf file? Do you think that is my problem? If not, what is?
Click to expand...
Click to collapse
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
richdaley said:
I figured this out if anybody needs to know. I had to do a full system reset then restore the eclair sbf so that the phone is in the exact state it was in out of the box. Then the OTA install worked fine. I am still working on getting KitKat installed. It seems like I need to find the right combination of recovery and rom to get 10.1 installed.
Click to expand...
Click to collapse
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
hotdog125 said:
To install KK, root, 2ndinit, then go to recovery and flash this and reboot - http://d-h.st/dWr. Then after reboot, go back to recovery (don't go back to the system). Then flash this - http://d-h.st/dz8 and immediately flash KK and gapps.
Click to expand...
Click to collapse
Beautiful. It worked perfectly.
Phone: Koodo Moto G running Motorola Android 4.3
Computer OS: WinXP sp3.
I've been reading threads/discussions for a few days now, researching before I jumped into rooting my new Moto G. Finally I chose to use the first method outlined by @paulobrien here.
This gave me root but wouldn't allow for superuser installation for properly monitoring/regulating root access. I tried multiple times with different methods and still just couldn't get superuser to install. So I tried the second recommended method.
Everything seemed to be fine as I went down the list until I followed these instructions:
Code:
Run the command 'adb-windows sideload supersu.motog.zip'. You'll notice the installation complete on your phone.
I got nothing. Repeatedly. Whether I used native ADB or his packaged version. Finally, noticing that @paulobrien had earlier stated that Motorola had messed up their recovery and that menu items weren't what they seemed, I started to experiment. Here's what I found in the recovery menu:
Code:
wipe cache partition
Actually gives you the option to install zip files from the sdcard. Duh.
Whether Motorola are really kinda inept/rushed, or if it's meant to sorta discourage people from playing with the phone's innards is anyone's guess. Whatever the reason, I copied supersu.motog.zip from my r1-motog-modifiedrecoveryroot folder - kindly supplied by @paulobrien - and boom! I have a properly installed and functioning superuser.
@ofaring Did you manage to flash CWM on Telus SW? I am unable to flash boot/recover/system that didn't come in Telus package, and I really need to. If I manage to flash CWM I can just flasch CyanogenMod and be done with it. Please help!
Flintberg said:
@ofaring Did you manage to flash CWM on Telus SW? I am unable to flash boot/recover/system that didn't come in Telus package, and I really need to. If I manage to flash CWM I can just flasch CyanogenMod and be done with it. Please help!
Click to expand...
Click to collapse
Hi Flintberg,
Yes...and no. I haven't had the time to fully investigate the current situation yet. Short answer (all I have time for right now)...I have succeeded in getting CyanogenMod, rooting, and different stock ROMs running on Android 4.3. So far, I haven't been able to properly accomplish any of that on 4.4. (Except for rooting) Trouble is, the battery indicator is wildly inaccurate with CyanogenMod installed from stock Telus Android 4.3. The trouble seems to be in the recovery image, which isn't functioning correctly in 4.4. I have to run for now. More details later.
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
Hey guys. I'm not sure if this is the right section for me to post this so sorry in advance if it's not.
So I have Android 5.1 version with TWRP and I keep getting the notification that the 5.1.1 update has been downloaded, but whenever I try to install it, it just goes to TWRP recovery and nothing happens. I've tried installing it from "install" and tapping on the update.zip file, but I get errors. Basically what I figured I should do is just update to 5.1.1 and use Nexus Root Toolkit to root the device again (I think I've done it like this with past updates, but I might have been using CWM). So what I want to do is to have a rooted device with the latest official Android version released for it (or a custom one if it'll make it faster) but as you probably already guessed, I'm a bit lost here and I'm not sure what to do in order to achieve that.
Btw The bootloader has been unlocked a long time ago if this helps in any way with this particular issue.
Any help would be greatly appreciated.