Develop Bugs

Note II LTE stuck on bootloader

Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?

GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help

Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.

dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.

GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.

[Q] Question about RUU

Hi All,
I have a VZW Htc One M8, and I have been playing with it when have gotten the chance recently. I have installed/flashed an RUU before to correct an issue I ran into (trying to take an OTA) and everything went smoothly. As I said I took the OTA, but kept the RUU from the previous time I used it (first mistake). I am s off so I am hoping that is going to save me here.... This brings me to my problem.
I was trying to flash Viper Rom, but at the end of the setup I kept getting a popup saying setup has stopped, and I was unable to see a homescreen, but the phone was working. I decided to revert back to stock using the old RUU (be gentle) and it loaded and I hit yes to begin. About 10 second in it stopped and wanted me to reboot... I was in the middle of doing something else when it happened so I rebooted back to the bootloader and my OS line was in red. I then went back to recovery and restored my very recently created backup of my stock rom, which worked. I then went back to the boot loader to look at what was in red more closely and it is now blank. It says OS but then nothing after.
I have since gotten the new RUU that I should have used, but it seem to hang on the last part of the loading (put in on my external sd card) and my phone works... but the boot take forever and the VZW logo doesn't come up anymore. It almost seem like the phone boots fine but the HTC ONE logo stays until the phone screen turns off and when I hit the power button to turn the screen back on the phone is booted. My question is... should I 1) try the old RUU again and then take the ota since I am s off I have seen that technically it should work. 2) let the phone sit at the loading of the newer RUU and see what happens (I haven't tried seeing if the old RUU will load yet) or 3) count my blessings and deal with a non completely broken phone?
I realize I made a few errors while doing this, but I am hoping that s off will allow me to correct the problem. Any help would be greatly appreciated.

Issue should be resolved
Sorry to everyone that read this... I didn't make it all the way through the thread where I found the new RUU, and the thread tells how to resolve the problem with not loading all the way. I am going to try the fix after work.
Edit 1: problem resolved... I am an idiot

[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

LG G3 (Resolved Bootloop Problem Upon Installing Andriod Update) (ANDRIOD 6.0.0)

Good After Noon,
Recently LG Released a new android update, (6.0.0) The phone will send you a prompt that says. "ANDRIOD UPDATE 6.0.0"
Before I get into explaining this major issue I'm going to give you guys a run through on what android updates go through before it finally reaches your device.
Lets begin. The update is developed by android, then this update has to go through several inspections before it can be sent off to the service providers.
Once the update passes all of its required inspections it is sent out to each phone brand, HTC, SAMSUNG, LG, & so on and so forth, once the phone brands receives
the update, they edit the released android update to fit there devices expectations. Once each phone brand completes editions, then they send the updates to each service provider
that sells there phone brand, that's a lot of sending.
Now the major issue!
Hopefully you have read everything mentioned above to help you understand the cause of the Bootloop.
The way you could tell if the bootloop issue was caused by the update is if the bootloop started occurring shortly after updating to 6.0.0, & if your reading this because you are experiencing bootloop issues at this moment after doing the update then try this method to see if the phone will completely boot, Just simply plug you phone into the wall charger, now once you do this if the LG G3 comes out of bootloop and boots up normally then the culprit was the update, now to be sure if the update was the culprit, just simply unplug your LG G3 from the charger, now if it goes back into a non-stop bootloop. the Update was your culprit!
The reason this bootloop happened is because the android update 6.0.0 had a major corrupted file, how did this corrupted file end up in the update, well it's pretty simple, once the update was sent to the phone brand (LG) they went in and edited the update to there likings and at some point in that process they miscoded a file or wrote over a file which in result caused the phone to bootloop, Which tells me that the file that was miscoded or wrote over could have possibly been the file that prompts the phone to boot up, the boot up process takes the most power usage then any other process a phone is able to do, which means the phone will pull power from the battery until all files have been successfully complete, if the file is corrupted then the phone will boot until it receives the corrupted file then it will shut down and keep repeating that process, then the battery gets a memory and all it know to do is boot reboot boot reboot, which is known as bootloop. the way to fix this problem is to order a replacement battery, then the phone will boot normally. just be sure before putting the new battery in, plug the phone in the wall while still using the bad battery, backup all of your, and do a factory reset, this will put the phone back to normal and it will delete the corrupted file, the phone will work perfect. I put money on it.

Lg G3 Stuck in Recover Loop After Android Update Error

Okay, So let me start from the beginning so I'm certain I'm being descriptive enough.
The other night my G3's wifi stopped working. When I went to turn it on in settings it would turn itself back off. Which I thought was strange. So, I assumed it was a software issue so I backed up any important items and factory reset my phone last night. That went over fine. Wifi worked again, all was good. Until, it said it needed an Android Software Update. I hit "update" and allowed it to do its thing. About halfway through the update the phone said "error." With an icon of the Android bot with a hazard triangle sticking out from it. I let it be for a bit and nothing happened. So in my impatience I took the battery out and put it back in and tried to restart the phone. This is where the issue occurs. The phone keeps booting to recovery mode. I'm not savvy at all with Android so I don't know if these mean anything but it says "Android System Recovery <3e> LRX21Y" The phone has had zero modifications done to it. I would really appreciate any help or any tutorials that could save the phone until my g6 preorder comes in.
Thanks!
Kyle

Your phone failed the update for some weird reasons and is now stuck. I'm afraid you'll need to restore stock Android using LG Flash tools and KDZ files to your device. It will get your phone working, but you'll lose your data in the process.
You can try mounting the phone from recovery or download mode and see if you can access your data and backup the data. You can also try the recovery option without downloading wnloaing a KDZ first.
You can fins tutorials around the forum, in the general section usually.