Database Develop

[Q] Forgot .pit file in Odin...now stuck

Well, I got a bit cocky after previously flashing a T-Mo Tab and didn't carefully (re) read the directions (I know...dumb..dumb...dumb).
Anyhoo, I rooted a factory AT&T Tab that was running Froyo, I verified the bootloader was not locked with the downloaded .apk..and began flashing BG stock (en route to Overcome) with only the PDA and Phone files selected....no .pit and not repartition checked.
The load went to about 90% then Odin "stopped unexpectedly". The device is currently stuck on the download screen showing the stuck progress bar. I am keeping it like this to drain the battery.
I have to confess that I actually did this same thing once before (on a unit that was returnable). I have only NOW determined that it is almost certainly the lack of the .pit that is causing this. I know from this previous experience that if I force the unit to power down...it will do nothing..no restore...no download. Therefore, I am keeping it in this state to drain the battery quicker.
I found another poster on the forum that has the ability to "un brick", but I am hoping that after the battery drains I can get to the download screen and Odin again.
Anyone have any thoughts? Am I likely to recover after the battery drains? Time will tell I guess...but I am anxious!
Thanks much...
p

Sorry...obviously I was flashing GB (GingerBread) stock.
TIA...p

If its in download mode doesn't ODIN recognise it? If so, just reflash with all the necessary files...
If you drain battery you might not get it working again. There have been people with problems like this....

Odin "sees" it as evidenced by yellow in COM port...but upon attempt to flash it fails to connect - load never starts.
Thanks for your reply anyway.

1st post, w00t!
Mine did something similar. After multiple attempts at getting Odin to connect, it finally did. I basically had to put it into download mode 5ish times. Pressed the 'reset' button in Odin a few times, unhooked it from the USB cable a few times.
I wish I could be more specific, but I don't remember the exact process, sorry . What I can tell you is that I was able to charge it over night by just leaving it plugged in and from what I could tell, it was powered off.
Best of luck mang!

Thanks for the note.
I wish I COULD put the device back into download mode.
Completed dead now....
Looking at un-bricking options (Samsung, private party, etc..)

PM sent...

Upgraded to v10e, lost root, please help getting it back

Hi all,
I'm pretty much a noob here, though I'm trying to read and figure out what I've done wrong.
I was on v10c and had rooted my O2x using superoneclick, easy-peasy. Had SU going, and TiBackup. Backed up my files to Dropbox, decided to go ahead with the LG update, not realizing it would remove my root.
I had frozen a bunch of apps with TiBackup, and those seem to still be frozen, so that's all good. Everything is mostly working well, except I can only move some apps to SD, some just say it's full, even though there's 3gb free. Oh well, it seems to fix it if I un/reinstall, but I'm not so short of space that it's a big deal.
The annoying thing is that SU keeps popping up saying I'm out of date and of course I can't update it without root and I can no longer use TiBackup. I've tried using Superoneclick again but it thinks I'm still rooted. So I tried un-rooting it, but that didn't do anything as when I rebooted and went back in, Superoneclick still thinks I'm rooted.
Any ideas? Also, please explain it as though I'm dumb, cause for these purposes, I kinda am.
TIA
Oliver
btw, at the mo, I have no interest in custom ROMs or whatnot, just want to be able to backup & restore stuff.

I rebooted my computer, rebooted the phone, plugged it in and tried to un-root it again. This didn't get any popups, though I did get a 'FAILED' message at the bottom of the superoneclick message window, can't remember which operation. Nonetheless, I took it as a positive. Rebooted the phone again.
Now it's stuck in a reboot loop! Ffuuuuu.....!!!!
The battery is low, so I'm going to put it on the charger for a while and see if it decides it wants to boot later.
So for THIS problem, I've read that you should take out the sim and battery for a while and try booting it later, correct? If no go, then do a factory reset?
So if I DO a factory reset, what are the correct steps to root the device afterwards? I assume a factory reset just puts Android v2.2.2 back on but doesn't touch the firmware, so it'll stay at v10e, correct? I figure I'll just have to run Superoneclick once and then I should be good to go, right?
Thanks again,
Oliver
This mucking with my phone scares the bejeebus outta me - I always figure I'm gonna brick it. But it's worth it if I can disable the awful Car Home, F-Secure and the horrible FB/TWitter/Myspace crap that LG cripples the phone with.

Just factory reset phone and then root using superoneclick...if that doesnt work, load custom rom, topogigi would be nearest to stock
Sent from my LG-P990 using XDA App

Okay, I tried to reset it by holding VOL- and then turning the phone on. It says 'S/W UPGRADE Please wait while upgrading' but it appears to be frozen there as it's been sitting on that screen (while plugged in to power) for about 20 minutes.
Any suggestions? Is it safe to pull the battery and try again? Should I have done VOL+ and HOME and then powered it on?
I'm starting to worry here.

I think our phone is unbrickable. I have even tryed to repartition it (failed) and I still managed to fix it. You can follow this guide for going back to stock and then you can upgrade to 10E with lg tool and then do the root. the guide is in greek and i translated it with google translate. Original page here http://www.myphone.gr/forum/showthread.php?t=300529
How to return to the Stock Rom LG 2X
Caution: The perierchomena of internal sd will be erased.
Go here and download the Greece / Italy Firmware.
Download drivers and smartflash here.
Run the SmartFlashTool_P990.exe from PC
Close the phone, remove battery, connect the phone and hold down the Volume down (Here we should see a message "software update" and "COM port" in smartflash will be filled automatically after install the drivers if needed)
Select the "ROM Copy D / L"
Check that the "Normal Mode" is selected
Check that the "Erase CAL" is NOT selected
Press the button "browse" next to "AP Bin:" and choose the (BIN) file
Press the button "browse" next to "CP Bin:" and choose the (FLS) file
Press "Start" and wait to complete the flasharisma
Thanks to Jastonas
These I have tried without any problems, but I have to say:
NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE Pathe ...

Thanks very much for that, orlox.
I did end up getting it working. I don't know what S/W upgrade was all about, but I decided to pull the battery and try a reset again. This time it worked, in no time flat.
Here's the weird thing.
I set it all up from scratch, and when I plugged it in to root it again, Superoneclick said it was already rooted, did I want to go ahead anyway. I said no, then downloaded Superuser - sure enough, rooted. WTF?
Weird, but I'm not going to argue. Everything's working and it's working well. I don't know what app it is, but the more I install, the slower it gets. Not awful slow, but noticeable. A "fresh" phone always feels so snappy. I don't do all that much, but I put on GO launcher, a bunch of apps. I only use 3 home screens. I have the GO FBwidget, APW Calendar, Typoclock and Fancy widget forecast (4x1). Then I've just got some app shortcuts and that's it. It's not laggy. Just..... not quite as snappy as it was before I installed everything. Perhaps I should just can all the widgets? But then wouldn't I just have an iphone?
Anyway, thanks to those who responded.
For those interested, it is still on v2.2.2 and v10e.

if you dont use a2dp bluetooth and fm radio go for cyanogenmod. Youll see a HUGE speed improvment

just go for v20e if in case its still slow, or even Cyanogen. As for me, same thing and same scenario happened, did a factory reset and that's it, its fixed. As for slow performance in v10e, removed most LG apps except SNS and App Adviser and its all good even on the stock LG Launcher

Giga Bricked Note.

Today, my Note got extremely bricked, that I could not believe a phone like that could get so easily blown up.
I get this "Firmware update encountered an issue. Please select recovery in Kies and try again." message while it's rebooting every second.
I got this by making a huge mistake, using the re-partition option with the included .pit file, thinking it would factory-wipe the phone before downgrading... well, it didn't. Now, I can't barely access Download Mode or recovery because of, what I assume, low battery. It's charging now and it doesn't look like it. It reboots itself every 5 sec while it's plugged in. Before that, I used the JB leak and began to hate it because of it's damn instability. I wanted the stable, stock, ICS that came with it. I never had any problems like that on Xperia S.
Hell, even Odin can't ****ing save it because of the reboot-problem. I begin to think that, for the first time ever, I have to send this pile of **** back to Samsung and get a new one by saying, Kies ****ed up my phone.
Is there a solution that DOES NOT INVOLVE A DAMN USB JIG for this phone?

If you got the error in kies you could have followed the kies emergency firmware recovery option. Reflashing with a pit file is only for when you have triggered the emmc brick bug is my understanding. Look for the thread with the unbricking guides and hope for best. If not then it looks like service centre...........
Sent from my GT-N7000 using xda app-developers app

LinixAndroid said:
.. I could not believe a phone like that could get so easily blown up.
I got this by making a huge mistake, using the re-partition option with the included .pit file...
Click to expand...
Click to collapse
Did you really read and combine this two sentences? Sometimes people should read the warnings (here about the reasons why NOT to use a pit) and follow them.
But first of all you should recharge the battery outside your device. When you're sure it's "reloaded" try download mode again and install a prerooted Stock Rom (like GB LC1 3-part) and check if you can install and after reboot into a stable device again.
Maybe it isn't so bad forever only for a few hours.

ThaiDai said:
Did you really read and combine this two sentences? Sometimes people should read the warnings (here about the reasons why NOT to use a pit) and follow them.
But first of all you should recharge the battery outside your device. When you're sure it's "reloaded" try download mode again and install a prerooted Stock Rom (like GB LC1 3-part) and check if you can install and after reboot into a stable device again.
Maybe it isn't so bad forever only for a few hours.
Click to expand...
Click to collapse
Wait, I have to charge it outside the phone? What kind of charger only charges the battery outside the phone?

just find someone with the same phone in your neighbourhood and charge in another phone...that's the easiest way..

I have flashed my note multiple times now and it never crossed my mind to use a .Pit file..
By the way, have you thought of leaving the battery out for a few minutes? I got that Firmware issue message before because the power went out while I was flashing my phone from my PC.. Then I just left it out for a few minutes and was able to boot back into dowload mode again

After the emmc brickbug:
The custom pit file may work but trust me after a few moths you going crazy with your phone... it freezes randomly on every rom and wont charge randomly. When you wake up.. phone frozen and battery is on 0% ... i lived 2 weeks with this then i gave it to samsung and they changed the mainboard for free now im happy

Help! Stock Note 3 BRICKED, cant recover. Expert needed.

I have an AT&T Note 3. I was rooted using the KINGO app, but returned my phone to stock several weeks ago and the rom shows official and the knox count is 0. I am running the stock AT&T Note 3 Android 4.3
The other day, an official AT&T android update was pushed to my phone. The update bricked my phone and now I am unsure if I can even recover what was on my phone...or at the very least get it running again. For now, I am without a phone.
When I can get the phone to power up, the phone attempts to "Recovery Booting" (this is displayed in blue letters in the top left corner with the galaxy Note 3 Logo in the middle). It tries to install this AT&T update following the recovery wording when powering it on normally and when using Volume UP/Home/Power . The update progresses towards 100% then "completes" sometimes, but then the screen goes black and the phone does not start back up. I have to remove the battery for a period of time and replace to get the phone to do anything
I can get the phone to go into download mode (Volume down/Home/power), but my phone did not have USB debugging turned on the last time I was able to access the options, so it is not recognized by kies/odin, etc!
Even though their update caused the problem, AT&T wont help me (over the phone or at the store) as my phone is over a year old...their solution is to buy a new phone and plan as they say they can't do anything to fix the phone.
ANY HELP WOULD BE GREATLY APPRECIATED!

Can you get into recovery?..if so try to factory reset then maby you will be able to power up get to developer options and turn on debug so you can use odin...other option..I have heard of some doing this..go to Bestbuy Samsung counter..ask them if they have the odin tool. If they do they may be able to get you up and running.
FIREKAT V11/S5-V1

Don't worry bro.
Just follow this post to put your phone back to stock and get it rooted again. My phone used to brick and I went through it.
Follow the steps carefully, and you'll get your phone back.
http://forum.xda-developers.com/showthread.php?t=2559715

[HELP!] I changed some of my system files and i can't turn my phone on!

Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page1

AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. For the best available help, I'm going to move your question to your device's Q&A forum. Good luck!

AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option (...)
Click to expand...
Click to collapse
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745

cyker31 said:
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
Click to expand...
Click to collapse
Hey! Thanks a lot for the advice, ill try to do what you said, although im not sure how to use fastboot. Ill tell you if it worked.