Develop Bugs

[Q] Having Issues Upgrading to new OTA

I am having trouble getting the 4.04 update to work, I get to the android, then it lays down with a red exclamation point out of his stomach.
I was running Kang B36 w Franco Milestone
I used option 9 on the toolkit my build toro 4.02
I restored facotry image for my phone via option 8
I reflashed stock recovery via option 10
finally I locked my bootloader via option 11
restarted my phone downloaded the update and now it stays stuck on the Android with the red exclamation out of his stomach halfway thru the update.
anyone know the reason why my phone will not update?
did I screw the Basseband? IMEI? or serial? the same thing happend on my Droid Razr when I modified the Build.prop but I never touched the build.prop on my GNEX.

gfropr said:
I am having trouble getting the 4.04 update to work, I get to the android, then it lays down with a red exclamation point out of his stomach.
I was running Kang B36 w Franco Milestone
I used option 9 on the toolkit my build toro 4.02
I restored facotry image for my phone via option 8
I reflashed stock recovery via option 10
finally I locked my bootloader via option 11
restarted my phone downloaded the update and now it stays stuck on the Android with the red exclamation out of his stomach halfway thru the update.
anyone know the reason why my phone will not update?
did I screw the Basseband? IMEI? or serial? the same thing happend on my Droid Razr when I modified the Build.prop but I never touched the build.prop on my GNEX.
Click to expand...
Click to collapse
1) Don't use a toolkit. You don't know what it is doing exactly, so you don't know where it went wrong.
2) I suspect that there is still something that is not stock. I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that nothing messed up. Once you do that, then you can have a look here for how to use the OTA update file to update.
3) Don't re-lock your bootloader.

Thank you very much I was unaware of the issues with tool kits, I assumed they worked good since they are stickied.
Sent from my DROID RAZR using xda premium

When I boot into recovery from fastboot my android has a red triangle with a exclamation point, do you think my stock recovery is corrupted?

I am having the same exact probem. I am running the stock 4.0.2 that the phone came with. I used a toolkit that was posted in the Development forums to unlock and root the phone. Other than that, its totally stock.
When I do the OTA update, It gets to the dead android with a triangle coming from his stomach,
I have to pull the battery to get the phone booted, and its still on 4.0.2.
Anyone have any suggestions?

gfropr said:
When I boot into recovery from fastboot my android has a red triangle with a exclamation point, do you think my stock recovery is corrupted?
Click to expand...
Click to collapse
What you see IS the stock recovery screen. (To see the menu, you need to press power and volume up together.) However, if you are seeing that screen when you try to install the update, it is because something on your device is not stock, or, it is not the correct version of stock for the update.
The easiest way to flash the update (assuming you are all stock) is to follow one of the methods in the second link I posted.

Did my JB update just get screwed up?

Ok, so i have been patiently waiting for the JB update on my Play store purchased USA GSM GN that I have been using on Tmobile.
I finally get the update while I am at work, cant download since I don't have wifi there. The wait until 5pm was agonizing!
I finally get home, download the update, it asks to restart and install, i click ok.
It reboots into recovery, but I see the andorid guy with the triangle and a red exclamation mark! It stays there for a couple of minutes and then just boots normally into android os without applying the update.
I rebooted manually into recovery to see if I could reproduce the issue and sure enough i get the red exclamation mark.
I held down Volume Up and Power button and it boots into stock recovery (3e) where i cannot find anything to apply and I just wiped cache and data and rebooted.
Of course, now I check for system update and it says system is up to date.
What just happened? I was rooted, but with stock recovery, locked bootloader.
Anybody else have this issue. How do I fix it so that the next time it finds the update i don't have this happen again??
Thanks in advance,
I could just pull my hair out in frustration....

Dude q&a section this is development wrong section
Sent from my Galaxy Nexus using Tapatalk 2

Why is this in development?
Read forum rules
Questions go in Q&A
Thread moved
FNM

You must be 100% stock for the OTA to apply. Correct radio, UI, build.prop, etc.

hmm i was just thinking this could be the reason.
A little while back i had modified the build.prop for removing boot animation (using GN Toolkit).
In fact i have been trying to restore the backup of the build.prop file back, but haven't been able to.
Any ideas on how to restore everything back to stock (i even tried that option of downloading google stock image IMM76D from the toolkit) and flashed it, but I still get the exclamation point when I boot into recovery...

kgdg said:
hmm i was just thinking this could be the reason.
A little while back i had modified the build.prop for removing boot animation (using GN Toolkit).
In fact i have been trying to restore the backup of the build.prop file back, but haven't been able to.
Any ideas on how to restore everything back to stock (i even tried that option of downloading google stock image IMM76D from the toolkit) and flashed it, but I still get the exclamation point when I boot into recovery...
Click to expand...
Click to collapse
That android with the exclamation point is the stock recovery, press volume up and power button at the same time a few times and the recovery menu should pop up
Sent from my Galaxy Nexus using xda premium

Look at the "flash" link in my sig to return to stock, and the "update" link to update to 4.1.1 from 4.0.4.
Sent from my Galaxy Nexus using Tapatalk 2

efrant,
I will follow the instructions on the flash link to go completely stock, I assume that will fix the red exclamation issue.
All i want is to put the device in a state that will be able to download the official JB (and future) updates and install them.
I thought I was already in that position when I got the OTA earlier today and downloaded it, but when i tried to install it, it booted into recovery and gave me that red mark, so I was assuming that the issue is with the (stock) recovery image.
Would that be a correct assumption?

negrobombon,
I understand that and that works and have tried that. But I am trying to understand if this exclamation mark showing up in recovery is the cause for the OTA to not install?
Or is it unrelated? It sounds like it is unrelated as people are saying the exclamation mark just means that it is stock recovery.
That seems to be proven since I followed the link erfant posted to go completely back to stock and after all that, I still have that exclamation mark in the recovery.
It really doesn't matter if I can confirm that is NOT the cause for my OTA to not install.
Now I am completely stock and looks like I will have to wait again for the OTA to show up (I just want to OTA, not apply the update manually as I want to test if this time around, the OTA installs correctly)...

efrant said:
Look at the "flash" link in my sig to return to stock, and the "update" link to update to 4.1.1 from 4.0.4.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
efrant,
I would just like to say, what a fantastic job you did on the steps in that guide.
It's definitely my preferred way of doing it instead of a toolkit blackbox method where you don't know what it is doing and it's great for when it works, but if it doesn't...you have no idea how to troubleshoot and don't know which step it failed on or what the error is.
Now, have to go back to #*#*checkin*#*# to see if that will speed up my OTA (not really sure if that helps at all). It seems like that does the same thing as Settings->About->System Update->Check Now...

[Q] Stuck at boot when updating to KK

Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.

You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app

cvall91 said:
Hello everyone, this is my first post and pretty much a cry for help.
So I'm not new to the whole rooting scene, as I did many things on my old S3, but I'm having a bit of trouble with my note 3.
I had rooted my device about a week after I got it to remove some bloatware. Flashed some ROMs to try out but ended up back on stock firmware which removed root but didn't really care. Tried to update yesterday and got the whole "you're device has been modified" thing. So I rooted again and downloaded xposed installer and that app to fake system to not get that message. Everything seemed fine, got the update and started downloading. Once it finished downloading and tried updating, I got a failed to update message then back to home screen. Went on some forums and read Kies was working for people who had rooted phones. Tested that out and started working. Download went fine, it started updating, all was good. Said update was complete and it was restarting..... Let the fun begin.
About 10 minutes later (I waited this long because I've flashed plenty of ROMs and I know the initial boot can take forever) and it was stuck at Samsung boot logo. On the top left there was a blue message saying "Recovery Rebooting." I restarted again, same thing. Did a battery pull waited a few minutes and still nothing. Wouldn't go into recovery mode, but it did go into download mode. Assumed something was wrong with the recovery so I flashed a custom one. Finally was able to go into recovery so I did factory reset/cache and rebooted. Phone was still stuck at boot logo but this time no blue message. I then found the 4.4.2 KK md5 file online so I flashed that through Odin but same story. Ended up flashing back to stock 4.3 and that's where I'm at now.
Any ideas? Am I stuck without KK forever? The only thing I think there's left to do is go completely stock by removing the Knox counter or whatever that's currently set to 0x1 on my phone. Doing the whole "Triangle away" thing but idk if that'll make a difference.
Sorry for the really long post but I'd prefer to explain everything I've tried so far.
Click to expand...
Click to collapse
I thought rooted phones weren't allowed to update via Kies or OTA.

allenjthomsen said:
You might have had a bad download from the odin.tar.md5 file redownload and flash again i have heard other pwople say they had to flash it 2 times for it to take and once u do the update to 4.4.2 you cannot revert back to 4.3
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I guess I'll try to download it again and see if that works. Do you know if that's through Kies or through manually downloading it then using Odin?
Techngro said:
I thought rooted phones weren't allowed to update via Kies or OTA.
Click to expand...
Click to collapse
Well it seemed to update for me. At least the verification process went through. I used Wanam Xposed and had the fake system status thing checked. Either way something went wrong and didn't finish the updating process and got stuck at boot logo with no recovery options.
The OTA update did not work though. I was able to get the update downloading after Wanam, but once the download finished, the update failed before trying to install. Did not try OTA again though I just went to Kies, then Odin. But all 3 methods failed.

[Q] Rooting Galaxy note 2 with TWRP

Hello,
I had attempted to root my galaxy note 2using mark skippens android tool kit v 1.2.8. The note 2 build ends in MC2. its a sprint L900 phone with 4.1.2 android version. Odin seemed to work ok in loading twerp I got a blue RESET in odin when it finished. So twrp came up on the screen. I couldn't get out of it at first and I thought I had bricked the phone but then I determined by hitting "system" it would reboot. During the reboot, I noted that it said it was 'updating android apps' counting from 1 to 111 in my case for the number on the phone. When I got back into normal mode, I noticed in the messages window that it had a message to "tap to install su to root phone". I have not seen this procedurely anywhere in the root steps. So I don't know if I should just let it do it from the normal android mode or if I have something really wrong. I didn't execute it fearing that I would mess it up further. Although the phone seems to be ok otherwise. So it kind of seems like Odin didn't complete the "all in one" steps as noted in choice 5 where you pick the root procedure in the android toolkit. My question is then is where do I go from here?
thanks

[Q] help - i think my phone is temporary bricked

hi,
so i just got my s6 edge for sprint shipped to me (it wasn't activated to any service when i got it). here is the order of events i took:
1) tried to activate my service, but there was a delay in porting the #
2) while waiting for them to port it, i rooted it, installed twrp and a rom (this was when it was on 5.0.2)
3) they called and said they were ready to port, but the new rom didn't have the activation software in it. so i stalled them and said i would call back. i then reverted back to stock using odin.
4) got the number ported and was fine using the phone at that point.
5) this is where the day turned bad...... i didn't realize that coincidentally today, a new firmware was released to 5.1.1 and the phone auto-updated to it while i wasn't looking
6) i went to go re-root it using the same 5.02 root and now my phone is stuck. it's sitting on the "Samsung Galaxy S6 Edge, Powered by Android" screen and in the top left in red it says "RECOVERY IS NOT SEANDROID ENFORCING"
7) i tried to restore it back to the stock using odin, but it errored in the download mode (i don't remember the error off hand)
i can get into download mode, and that's about it. i had to let the phone's battery die on it's own to turn it off (this phone gets super hot, btw)
so i guess what i need to know is how to restore back to factory default again, now that it thinks it's on 5.1.1. is there any hope?

I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.

bbacon said:
I'm in the same boat as you, I think the only hope is to wait until the firmware is available to download and install it via Odin. Let me know if you've had any luck getting it up and running again. I had to switch back to my old phone for the time being.
Click to expand...
Click to collapse
check this post, download the tar and flash it in odin. it worked for my phone!
http://forum.xda-developers.com/showpost.php?p=61650724&postcount=142
it got me into a recovery image that worked and i was able to factory reset in there. my phone is booting properly now. (after it reboots when done, it took a bit on the first title screen to do anything, just be patient)

Thanks man, that worked great. Although I found out in the process of trying to fix it the past few days, I must have flashed a non-compatible kernel because once it boots the touch screen is unresponsive. I guess I'll have to wait until the firmware download is available after all. Thanks again for the help though