Related
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart
First let me say that I am 51, not a techie and only smart enough to start a conversation about my phone but not intelligent to keep it going.
I have had an i317 ATT Note 2 for a good many years. Some time back ( about a year ago ) I was reading pretty steady about rooting my phone and installing a custom ROM. Well.....reading a lot and becoming constipated with information is about as far as I got. Sad, yes I know...but that's really it. It was SO overwhelming for me that I called it quits. Somehow I managed to gain SuperSU ( if that's right ) status and my phone said I had "root access". However, I never installed a custom ROM. It was about this time I found , if I have this term right, Wanam xposed and or xposed installer. IF, this is correct, what ever it was allowed me to really tweek a lot of settings on my phone so much so that I told my wife I just didn't have it in me to ROOT, but could ust this new app to change a lot of "stuff" and I'd be ok with that. Well, as time went by I stopped fooling with it, found a few things I liked changed the way I had them and just left it alone. I'm not a gamer, not a techie, although I've read a lot of definitions, some stuff just don't "click" with me. There was about 4-5 times back that year ago that I did what ever it was that made me think I bricked my phone. so much so that I thought I was going to literally throw up, I was really that sick inside. Well, it was nothing more than reading many many different posts on forums and not knowing what I was doing, that I somehow used Odin to get is back where I could use it. A major problem was not understanding what I actually did nor even knowing how to repeat it without again, just stumbling upon it.
So, with all this time having passed......the other day a message popped up on my phone saying "UPDATE AVAILABLE" or what ever it was....either way I KNOW I seen the word UPDATE. It said click here ot begin update or click here to update at a later time. I wasn't so much thinking to myself, DONT UPDATE because you'll screw everything up.....I was simply declining because I didn't want to be bothered. Certainly I'd forgotten or never given it any thought about the possibility that I'd end up in a mess. Like I said, I had ROOT ACCESS....just never installed a ROM so I may not have even thought an update would have done anything negative. Well, later in the day ( about 7 days ago now ) I hit UPDATE and my Note 2 that I absolutely LOVE is now turning on, goes to the black Galaxy Note II screen, then the swirling circle and gets stuck and locks up every time at the ATT logo that looks like a globe.
I have read and read as many things as possible on my end......so much so that after about 2-3 hours each setting I end up with a headache, am frustrated and deflated until I walk away. I don't know the correct terminology to express every step I've taken but will share with you all what I can at this time.
I can do both 3 button press methods....power, home and vol down...then press up I think for download mode. I can also press power, home and vol up which takes me into the mode that shows the little Android dude who lays down like he's having repairs done. I will add here that while in that mode, I've literally clicked on EVERY SINGLE choice in every single mode/ screen or what ever it's called. I've cleared, reset, recovered and scrolled through every choice and hit every button available......and as many times that I've plugged in, used many many different forms of Odin and countless files with the .tar files...I've also clicked on everything I can to see if anything changes.
Believe me, as frustrated as it is reading what to you seems like gibberish, it's equally as hard reliving it again and again. I've already put in 3.5 hours tonight and NOW am typing this to you kind people to see what hope there is and if I can understand it if something is shared with me.
I've downloaded Odin 307, Odin 3_v3.10.6, 4.3 Param_tz, Odin 185...honestly about 3-4 more Odins and gone back after I have downloaded and unzipped so many that I've been baffled only to delete them after literally going through the process ( following XDA steps by steps......AND PASSING EACH TIME!! ) only to not have crap when I'm finished. I've even unzipped CF AutoRoot MD5 file this last time just hoping to pull something out of thin air.
It's no joke when I tell you I've followed more steps on the XDA site and countless other sites...totally by the book and have had 100% negative results. It's not that I've got this endless list of contacts that I can't live without. It's not that I've got 344 fresh work pics of jobs I've completed or even pics of jobs to estimate for work, it's just that it sucks so bad to be in a position of not having this phone that I totally love so much. It's not loaded with games and I don't do anything really intelligent on or with it. But it is very important to me, I'm a creature of habit and over the years have really become attached to it. My wife and oldest son have just upgraded our plan to include him with a data package for a smart phone and with it they received new phones. It's been about 2 months ago and I told my with, I DON'T WANT A NEW PHONE!! I LOVE MY PHONE!! I still do, I'm just stuck and obviously not sharp enough to get out of this one without asking for help.
It's been reset, restored, erased, you name it. I've had the battery in and out, sim cards in and out, pushed every button 10 times in combination with other buttons, read and read, followed every step for downloading, unzipping, using multiple Odin files new and old.....just everything. I can't access kernals or other important data you may ask for because I can't get out of the start up logo....I thing it's called bootloop?
Man I'm really jammed up and would be forever grateful if someone could shed some light on this situation. I know I may have gone way overboard with everything that's been loaded, pressed, wiped etc, but I've exhausted everything I could think before asking for help.
I can't even count the number of times that I've entered Odin with a .tar file and it's gone through every part of it's deal only to end saying PASS!! ...usually within 2:02 to 2:12. The CF Auto file was :08 and said PASSED!!
Frantic, frustrated and fully prepared to beat myself with a stick
I need simple simple guys. I HATE to be a bother, but I'm stuck and know that you all are good people who fun a respectful forum and are courteous with one another. So here I am. Any help please?
I would like to add that I've not simply popped onto this forum and asked a repeated question before having read many other posts involving much of the same issues. I am a foretravel motorcoach owner and am on a forum very similar to this one where there are noobies and those of you who have a great deal of knowledge that share so others may have a pleasant experience. Honestly enough, I'd rather take my whole coach apart ( I'm no diesel mechanic nor have air system knowledge ) and rebuild it blind folded, rather than have problems with my cell phone. I have read all of the posts from those who have the i317 att note 2 as I do. I've walked ( confusingly ) through all the directions that have been given to them. I wish I knew the language better but have to admit that I struggle. Imagine each time reading a helpful post for a similar problem, going back into my downloads and deleting everything on my PC and then downloading the next set of steps involved in helping the next person with similar issues. Each time I download, unzip, reconnect, run through Odin and pass...only to find that I'm no further ahead and have no understanding why things work for other people but not for me. I had hoped that I'd have had a reply that would be an "AH HA!" moment. But I've not gotten even one comment. I'm doing the best I can to communicate and reading a lot on my end to muster my way into understanding. I've made a mistake and am paying for it dearly from having hit UPDATE. I just wish I had some way of knowing why nothing seems to be working.
Okay....
Deep breath....and here we go..
The Odin flashes you are attempting....are failing due too your updated bootloader....(the one you received when you took the official update)..
Nothing you can do about the bootloader now as it can't be reverted....but that's okay....
Here's the plan...
Load up odin 3.0.7 and download the UCUCNJ1 rooted rom from the link below...http://forum.xda-developers.com/showthread.php?t=2973448
Boot the device into download mode and flash the above file...
If the device begins boot....pull the battery and put the phone into download mode ....and flash the same file again...
Once complete...allow the phone to boot and it should start normally...
If it does....then power off and boot into your stock recovery and wipe data then cache and boot again...
You should then have a rooted stock....UCUCNJ1 build...
The reason this works is because your rom image that you flashed does not contain a bootloader image....
Once you are back up and running....you'll need supersu....(the thread explains this in the first post)...
The process to get you going is pretty simple....you just need the right file to flash...
Read that first post....as everything you need is there....g
I'm really not sure if I'm replying to this post correctly as I've seen 2 options so if I'm not doing this please someone, correct me.
I'm a chimney servicing professional in Northern Michigan and right now is "GO" time for the next 4 months. I leave early mornings and return late evenings like now. Being without my phone is a really struggle and inconvenient.
So let me explain what's happened since you replied with suggestions for me. Just before your post came to me I had been reading on this forum for someone with the same phone as mine to power, volume down and home...then volume up to go into download mode. I could not only do that but could also use the feature of power, volume up and home for what ever that feature is for......as of NOW...I can only access download mode. Any other method of buttons turns on the phone and it is locked up in the black screen with Samsung Note 2....and that's completely it. Before it would at least cycle through a couple screens before locking up at the ATT globe logo.
So, just before your post came through I had read to go into download mode and then use Odin 3v1.85 to load this file Kies_home_i317_att_i317ucali2_i317att_original4.1.1
I have not used a Kies file before and the only experience I'd had with Kies was not favorable in the past for a completely different topic. So anyways, I did this again, just before your suggestion was posted and IT WORKED!!! I was pretty thrilled. It was late and for the few minutes I had gone through the phone to see what was and wasn't there it kept wanting to update. I did not do it. Finally I called it a night and early in the morning ( yesterday ) I took the phone with me to work. Although the features were slim because I'd not downloaded any previous apps, it was working.
After reading your post with the suggestion I thought as long as it's working, I'll check later to see what I could do about updating or rooting & installing a rom....which I've not done before. Well, last night while shaving and having the phone on the counter, I glanced down and it went into UPDATE mode all by it self. I tried to stop it but buttons were useless. So, all day again I've been without a phone and now the only thing the phone will do is power up with the power button and get stuck in the black screen with Samsung Note 2....that's it! Or, I can power, home and volume down, then up to enter download mode. I have since gone back to the Odin 3v1.85 and ran the same Kies file I mentioned above. The thing was...in the past I was going into different versiona of Odin and attempting to download files and it would do SOMETHING...then say pass...but nothing really happened. Doing what I'd mentioned above...the phone would log into Odin 1.85 and download the Kies file....only now it was taking 5+ minutes and working...or should I say "worked once" instead of taking only 2 minutes in the other Odin modes.
So, now I've completely charged 2 different batteries, and tried it a couple times just before commenting about what's happened.
So, now what??
Do I go back and attempt the directions you offered in your reply to me earlier or now and I heading in a different direction all together?
Just to let it be known, I'm not a "gotta have the newest and latest, greatest program" guy. I'd like to have a rooted and backed up phone and like to have a rom that has great battery life, allows me some cool features but mostly just have the access. I read a lot about different roms in the past and just couldnt pull the trigger on one.
I say this to mention that I'm not sure if I am successful in getting this thing back in action and am going to drop a file in the PDA slot of what ever Odin version I use....do I ALSO add to what ever unzipped file other commands like a root file or rom file ...or some sort of back up file? I thought I'd read where you added what ever you were loading the phone with was to be all added to that same PDA line together.
Gosh, I sure do appreciate any other suggestions to get this back and running.
I WILL NOT ATTEMPT ANYTHING before hearing back back. Just help me please...Thanks in advance
Use my information in the post that I wrote and you'll succeed...
Flashing the rom front the link I provided will repair the problem...
Use PDA slot for the file and don't change any other Odin settings...
It'll work....g
Ok, just now I followed each step and was really excited to know I'd be back up and running.
I still cannot get into the power/ volume up/ home button mode to wipe cache. It will not go there. As soon as I press those buttons it immediately goes into "stuck" mode on black screen with the Samsung Galaxy Note 2 logo.
I can turn on and get into download mode obviously with those buttons only volume down...then up. I tried with battery in and passed, I tried taking battery out as you directed when it tried to boot and it passed. I then ran it another time thinking I'd read someplace that someone repeated a flash process and after 3 attempts and all passing using Odin 307 it's been consistently stuck on the screen mentioned above.
I can't tell you how much I appreciate your time and will do as recommended at the times advice is given instead of doing my own mindless and unknowing thing.
What suggestions might there be now? I'm really hoping that since it will turn "on" that it's NOT bricked. I won't be able to handle it.
Much appreciated and very thankful
Please advise
Sandelman1
have now deleted all odin and repair files on my pc. Reset new odin 3.07 and redownloaded the files mentioned from the link above. I STILL have nothing but being stuck in the Samsung Galaxy Note 2 screen. I've ran the exact same process you mentioned this morning, I've tried different fresh charged battery and also different usb ports.
OMG do I ever need help. It's really very much greatly appreciated. Is there other ideas or more hope.
I'm all ears and eager to follow what ever direction is next
Samdelman1
sandelman1 said:
have now deleted all odin and repair files on my pc. Reset new odin 3.07 and redownloaded the files mentioned from the link above. I STILL have nothing but being stuck in the Samsung Galaxy Note 2 screen. I've ran the exact same process you mentioned this morning, I've tried different fresh charged battery and also different usb ports.
OMG do I ever need help. It's really very much greatly appreciated. Is there other ideas or more hope.
I'm all ears and eager to follow what ever direction is next
Samdelman1
Click to expand...
Click to collapse
Sounds like you are close.
First off which bootloader are you on? Pre-4.3 and post-4.3
Also I wrote up a guide
http://forum.xda-developers.com/showthread.php?t=2618447
This gets you out of most jams. But first please reply back with version of bootloader.
First I really appreciate your reply as with any of you veterans who are in the know. To answer your question, I'm not sure , as sad as that it. Here's what I can tell you though. The few days ago when G helped me and my phone came on for a day or two, I went into the "device info" and this is what I found.
Android 4.1.1
Baseband Version i317ucalj2 ( that L J part at the end may not have been read correctly, but that's what I wrote down ) hope that isn't a problem
Kernel 3.0.31 - 215878
[email protected]#1
SMP preempt thru oct 4
16:14:05 kst 2012
Build # JR003C.i317UCALJ2
I REALLY hope this helps you help me.
If the info I offered is personal information that I'm best not to share with the internet PLEASE let me know and I'll edit it out. I would expect to be dealing with decent folks here so should be no worries. But still let me know if it should be confidential.
Ok, that's all I can share with you since I'm not able to enter into any of the "wipe cache" mode or that department in general.
Looking forward to hearing what you have to share.
Thanks again in advance. I'm very grateful.
Sandelman1
Ok, so I went to the link you posted and before doing anything at all, I read into 15 pages of it to make sure I wasn't missing anything important to my specific install. Once I realized I only needed pages 1-2 or 3 I began. First I deleted everything off my desktop that had to do with previous odin, att and the like. Next I downloaded te odin 3.07 and joined (free) the Sam site download you recommended and waited until what seemed like forever to download.
Once that was done I reread pages one and two and focused on what to do in the event of freeze up and which option I may need to choose should I lock up in one of the two possible options.
So here's what happened. First time I downloaded the kies file......it went to RESET as you mentioned and seemed to hang up....the Samsung Galaxy Note 2 black screen came on and froze. I "thought" it was done and pulled the back off the phone and removed the battery but it was still froze. I then unplugged the original Samsung USB and the screen went black. I waited for several seconds and reinstalled the battery. ( now in prayer mode ) I hit volume up, home and power.......it went back to black screen, Samsung Galaxy Note 2 and stayed there.
THEN!! I seen my PC in odin mode say PASS. I thought hmmmmm, did I unplug to fast? So I pulled the battery, reinstalled, hit vol down, home and power...then vol up and plugged the phone back in with original cord. I opened odin 3.07 and clicked on the link same as before. This time I let it run until it was at the RESET screen ...then I waited......then I waited thinking certainly it's not doing anything...then it popped up PASS!
I thought COOL, I'm in now. So it went to black screen Samsung Galaxy Note 2 and hung up. I reread from there to remove battery ( unplugging the cord at this point again of course ). I counted to about 15 slowly and reinstalled the battery and hit vol up, home and power........same crap again, how frustrating. So I'm still sticking on black screen Samsung Galaxy Note 2 screen and that's where I'm at now.
I was hoping that since things were so similar between what I had going on and the link or thread you had posted, I would save time and follow the directions.
I've not spent about 2.5 hours at my PC and have to go to work for a few hours. Hopefully this will help you better know how to direct me with what I've shared with you about my phone specifics and the fact that I've already followed steps from your thread.
I'll check back in a while to see what other thoughts are going to move me forward.
Once again, I say thanks for any time you or others may spend in helping me.
Sandelman1
OMGOSH!!!
I've not got the time at the moment to share all the amazing info and things that have transpired since my last post, but I will.
Hey, quick question....seriously. How would a person donate to someone whos helped with the issues some of us experience....what's the process?
And on that same topic....what is customary or an appropriate amount?
I searched the forum looking for help because I don't have funds to buy another phone at this time but at the same time I seen it posted someplace that it's a nice gesture to "buy a guy a beer" if they've helped you. I'd like to buy myself a beer.....but I think it's been around 12-13 years now since I enjoyed my last one. In my world I though everyone around me was an A-hole.....lol...come to find out it was ME who was the A-hole. Who'd a think it,lol.
So if someone could share the how to and what's a "kind gesture" I'd really appreciate it.
Cant wait to share just how "baller status" I feel right now with what I've been able to do with ya'lls help. ( not only did this come together today but I replaced an entire engine and trans in my jeep wrangler last night before getting back on this forum.
I want to take time now to get into it but will wait becuase I've updated and would like to know about backup, storage, and root access.
Later folks...I'll be hack tonight
Sandelman1
Good evening,
I have read many threads on recovering this particular model of Note 4 from the dreaded Qualcomm 9008 brick. I am only making "another" thread because of the unique nature of the device I have.
A fellow US Veteran has asked me to try everything possible to recover the photo's off of this device. Some of these are the last photo's of his grandmother before she passed. That is the only reason I am possibly going against the rules of XDA and post another brick thread...
Recovering the device is secondary to recovering the user data off of the device...
Here is the story as I was told.
User was having some sluggish issues and called Sprint support.
Sprint Support had him "push button combos" until the phone stuck at a "Do not turn power off or remove battery" screen appeared.
Sprint Support then convinced user to pull battery out.
Device no longer powers on, nor does it show any signs of life when put on a charger.
This all happened about 7 months ago, since then the device sat in a drawer until I asked him if I could see it. I plugged it into my laptop holding vol+/- and it immediately registered as a 9008 device (I had the qualcomm drivers installed from troubleshooting my LS996).
I believe the device did NOT have usb debugging enabled and was NOT rooted before this. So I am requesting some instruction and maybe a little hand holding so I can try to recover his pictures and I know he and his family will be incredibly grateful to have these pictures back...
Here is all I have done so far.
I've tried all the button combos+usb combos. I can only get vol+/- + usb to work
I've tried this after freezing in a deep freezer for 10min, 20min, up to 4 hours.
I cannot see the device in Odin at all, however I can see it with UAT 2.0.2 as well as in QFIL and QPST. I can also see it in CDMA Workshop as well as CDMADEVTOOLS.
I have NOT tried pushing anything to it, only to read it. I do have the original simcard with it.
I thank any and everyone willing to assist me in advance.
Koncrete
I've been running the latest update on the d2q Note 10 welcome it's a n975u1, and I've been running ice box as my device owner as well as revenant and also use a box to keep my apps under control, very conscientiously I must add.
Ever since the last update was ready to be installed I was trying to put it off because I was hoping to get off on one of those new routing techniques that keep telling me that I can't update my system Os or I won't be able to get it done, so I kept putting it off, but with each day my system kept getting more and more strained and suddenly just begin going into a straight boot loop going from the startup screen with the Android name printed across the screen and then saying it was booted and has been reset and then immediately going straight back to that Opening screen with the Android logo on it and repeatedly doing it until I catch it at the right time to Power It Off. My question is is there any way that I am going to be able to get around having to do a factory reset on this device or does anybody have any other suggestions that may circumvent this tedious measure at this point? I've been routinely wiping system cache, make sure I got all my backups ready to go during the periods of time that it doesn't go into bootloop,(which seems to be usually once a day for a few hours it will operate just perfectly until just suddenly shuts off with no warning signs). I was also able to get onto the Verizon update app via ADB download mode and they ran a scan on it and determined that they could fix my device if I were to leave it plugged in and allow them to do it. Theresa in the process of the repair that they said needs to be done. They didn't say what this repair would consist of, so I have no idea what is the real issue here. I've been trying to get as many system debugging reports as I can pick up along the way from various apps that record crashes and such but not sure really how to process that information to be able to determine what exactly the issue is. I'm at my wit's end and just about to point to just go for it the factory reset as much as I hate to do that! I think that I have Extreme Complex post-traumatic factory reset disorder and would do just about anything to avoid having to go through this again! If anybody has any advice I would very much appreciate it and I hope I'm posting in the right for him because all these Note 10 forms get kind of confusing when you got all the various processors and countries and all the other factors that you have to where to figure out where you're supposed to be asking a question here! LOL sorry, thanks!
Power management apps and launchers can boot loop you fast... so I learned
I get good run times with no power management on my stock N10+, but it's heavily optimized and I am using a package disabler.
To fix it you'll need to edit the offending apk(s) out of the boot sequence. I haven't a clue how to do that. The power management app is the most likely suspect though.