I recently observed, that my N1 doesn't want to reboot normally. It has basically the same symptomatic than described in this Thread. HBoot is unresponsive since I press the Trackball, reboots only back to HBoot/SafeMode, but in SaveMode everything behaves as expected. the Commands ADB and fastboot are fully functional and I can flash even Roms. The "Workaround" described in that Thread - to trigger and move the trackball - has helped once only, but seems broken now.
To kind of "fix" it I'm thinking of the possibility to REMOVE that SafeMode completely from the Rom. Does anyone know, if this is possible at all? The Rom doesn't matter, and if I have to compile AOSP or Cyanogen or whatever, I'll do whatever needs to get done. Maybe I can just change the behavior from that "SafeMode" in the assumtion, that it is a tiny simple script that justs prevents loading of Apps.
So I basically want to get confirmed, if you think that this is possibnle at all. On top of that, it will be very kind, if someone has some additional hints for me.
Thank you in advance for any response
Related
First off I would like to say that this is one of the best forums I have ever seen as the amount of support and helpful users and creativity put into these phones are staggering. I was going to go to Windows mobile for my next phone but I now doub it with this site or at least maybe I will dual boot.
So I am sure I am asking questions that have already been answered but my problems with the phone (USA G1) are many and the answers to some of the problems are so fragmented that I had at one point 14 tabs open for reference to solve just a few issues. I am 70% noob with the G1. I have had the phone for a year with no major issues just the annoying Force Close that seemed unecessary for the commonality of the app that had problems. Texts were annoying because I could not tell if they had been sent the previous day or recently as service at my home is come and go and my older Verizon phone had envelope information and even said if the person had read it or not so no annoying duplication. However, otherwise it was stable and would last about a day and a half with the double size battery.
Recently, however I had rebooted from the power button prompt and it got stuck (I can't remember on what screen) and figured installing a different ROM and other files would fix the problem. By the way, I had bought the phone rooted and I believe it was using JF 1.42 and a Cyagen mod (forgive my spelling). So I followed step by step from this forum the wiki on the lastest stable Cy ROM. I followed the instructions to the T.
Being new to the software, it was a slow process with a lot of repeating of steps discovering little details that were not mentioned like naming something update instead of update.zip like instructed or adding the .img as an extension. So I had nearly made it and then I came to the DangerSPL and other files to be loaded on the phone in order via fastboot. Despite, several attempts I could not get the skateboarding droids or the rainbow screen to come up so I finally decided to just continue as I had been using Amon-RAs 1.7 update zip feature to follow the instrucions and install the software in order. All was well until I got to flashing the actual ROM which said something about how it said the E: [insert file name here] was not correct so it aborted everytime but it did show some progress on the yellow bar.
Next came the issue of the G1 screen hanging up after the above problem and for some reason I could get to the 1.7 screen but only by holding the button required to access Amon RA longer than usual other wise it would say the build of Amon RA at th ebottom with no commands and the reboot itself or hold it longer and finally get to the Amon RA but it would not load my recovery files as I had made many along the way.
I nearly gave up but then came across this solution which worked by using method 1 at well I am not allowed to pu the websit in here but I am not allowed by the mods. but it is the 4th one down if you google "how to fix a soft brick g1" and the link is titled Unbrick - android-roms - How To: Recover your G1 from a bring ...However, it did get stuck at the rainbow screen as it finally let me do the fastboot and I saw the Androids skateboardig but it hung at the rainbow screen. It was here I noticed that my 32A phone was now a 32B. I took the battery out and powered it up and lo and behold it was asking me to put in my google information and I finally made it to the home screen.
I thought "Yes!". Now, I can try again since it will fastboot now which was what was recommended at the final steps but I was mistaken. I could not searc the market for common apps like wave secure and it frequently said it does not exist. I saw that my terminal app was gone and when I was finally able to download it from the market and my superuser app was gone and the termina would not respond as before to the input of SU.
Then, I noticed my phone's screen would randomly come on and only sometimes go off. When I pressed menu it was as if it the call button was stuck and it would either repeatedly bring up voice dial or call someone. The buton does not appear to be stuck otherwise. When it would briefly stop, acting like the call button was in turbo mode it would give me the option to mount the SD card as I had lost my micro sd card reader but never give me a chance to mount it before the call button interrupted with google dial or calling some number.
I do not believe this to be a hardware issue because as far as I remember the call button worked normally during the steps as it was requently used. So my questions, at the moment, are these:
1. How do I tell if the call button problem is a hardware or software issue?
2. Once I find my card reader and will I be able to use the factory bootloader to go through the updates.
3. Obviously I have derooted my phone (or maybe I can delete the diag from sd card and it will operate as it is derooted), will I be able to reroot my phone by using my backups of nandroid basically leaving me at whatever step I was on to the road of recovery?
4. How do I use my nandroid backup to recover especially if I am stuck with the factory bootloader?
5. I copied my SD card before I did the wipe originally so will I be able to find a .xml from handcent with my texts? (I text myself my mileage for work as with my hours, it is easier than using an app plus it saves space for other apps)? Should I load that backup nandroid first and start over?
6. Is there a quicker way to root like...a program?
7. What is your advice for the future other tha obviously backing up my texts more?
8. When did wave secure start costing money? I think I might have backed up everything a few days before the crash but I have no access to it now.
9. What other key combinations can I later use for the fast boot?
10. When formating the card to fat32 what allocation do you use and do you use quick format?
11. What is lost dir. and why is it empty?
12. In Amon RA 1.7 there are several caches which I cleard all of them when asked to clear the the cache in the wiki directions? Should I clear all of them and what are the seperate caches, espicially the davik one?
I am sure I am missing some question but I will post more as I try to follow your directions or attempt other methods. I apologize for the long, long story but I wanted make sure I did not leave out any detail so this can be resolved ASAP because I am sure I am receiving texts and calls and people are probably thinking I am ignoring them (no one leaves voicemails anymore so how can I know if they called or texted during the phone's sickness). I also apologize if I have broken any forum rules or posted in the wrong section or violated some. Thanks guys in advance. I miss the fat little thing so much.
Oh My god! Sorry but that's too long for me to read, my attention span isn't all that great =p
I will try to help with your questions but I didn't read the whole intro so my answers might be a little redundant.
1.Run "adb logcat" from a cmd prompt on your computer and see if pushing the button registers on the computer
2. um ok??? not a question
3. you will have to re-root but your backups will still be usable after you gain back root
4. boot to recovery (home+power), scroll down to backup and restore, select restore, and select the file
5. I'm not familiar with handcaent so can't offer help there.
6. It's not hard. Downgrade with DREAIMG.nbh to RC29, use update.zip to upgrade to 1.5, install one click root, use it, flash a recovery, and flash a rom.
7. You should write shorter paragraphs =p
8. Again, not familiar with it.
9. HOME + POWER, and BACK + POWER
10. No clue....
11. It's a folder automatically created when you don't unmount your phone before disconectiong the usb. It's useless and you can delete it.
12. When installing a new rom, just wipe everything. It saves you trouble later on.
Hope I helped...
Thanks I will give it a try later today and probably come back with more questions and longer paragraphs
Hey everyone ^^
Hoping I can find some help here, else it'll be another phone consumed by the bricking plague
I recently tried to flash the latest CM from sourceforge, but the flashing process was interrupted (Powercut FFS). So the phone's stuck at the bootscreen. Normally, it'd be a case of rebooting into download mode and retrying, but....
My home key is buggered, it had a disagreement with some rain. Again, normally it'd be fine. Just use ADB to get into recovery/download, but...
The bad flash has made the phone unable to be recognized. Unsure whether it fails before it initializes USB, but it just won't be picked up on either ADB or Odin.
It's not all bad, I can still see the first Galaxy S bootscreen (The first one being the static, unflashey one).
TL;DR: Phone is buggered, unable to use "conventional" methods to access download mode, bootloader is still intact.
Could somebody please give some advice on this situation? It'd really help me out! Not keen on getting a new phone just yet
Cheers,
Morgan ^^
use JIG mate
http://forum.xda-developers.com/showthread.php?t=819551
thanks to TheBeano.
Yeah, I was looking into that. Unfortunately it'd take a few weeks for the parts to get here (No places like RadioShack etc) and this phone needs to be working ASAP (Usual story, right? ). Short of taking a knife to the AC adapter and hoping that I can find a 300K resistor, I'm at a loss as to what to do...
And now, this is even more interesting. Out of curiosity I decided to try to install my phone's drivers manually (For some reason Windows wasn't picking them up). The ADB drivers installed without any problems and I can now issue commands via ADB
The bad news is, well... Apparently most of the system stuff is missing. No /System/Bin directory at all (The only thing in /System is Lost+Found). Which, obviously, is bad. I tried issuing "reboot recovery" and "reboot download" which both worked, except the phone quickly flashed a white/blue line across the screen and restarted.
Is there any way to restore functionality through ADB? Can I push files to the /System/Bin directory (And all other missing things...)? If so, where would I get the files?
I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.
Hello all,
I'll try to be brief, but descriptive.
Months ago I tested out a used S4A in sink... it got wet. I dried it out and it was working mostly fine. Changed the charging port/ribbon cable and worked fine except for the menu button was dead.
Rooted device with Towelroot and was getting ready to try and install custom ROM, why for some reason I deleted Towelroot app and restarted. Phone has since been stuck in Safe mode. I can install apps like safestrap, but can't get to them, being in safe mode.
I've tried flashing a custom recovery, and many factory resets after attempting "try this" and try that's" from forums. Nothing has worked.
I used to have an HTC that had a ROM mounted onto an SD card that I could run from RAM (at least I think thats how it worked), is that possible on this device? or is there any other solution to this?
Thanks in advance for any suggestions.
Solved
Apparently, I didn't clean it enough. I cleaned the contacts a couple times, but is seems that it was not enough. Unit is now operating normally. In addition, through testing everything, I noticed that the menu button on the board wasn't pressing forward towards the face button quite enough. I stuffed something in there to press it forward and now it is working perfectly!
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
x0nar said:
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
Click to expand...
Click to collapse
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
simms22 said:
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
Click to expand...
Click to collapse
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
x0nar said:
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
Click to expand...
Click to collapse
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
zelendel said:
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
Click to expand...
Click to collapse
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
cam30era said:
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Click to expand...
Click to collapse
Unfortunately that is what I believe I'll have to do.
x0nar said:
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
Click to expand...
Click to collapse
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
zelendel said:
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
Click to expand...
Click to collapse
I've dropped Multi ROM completely. The issue sad-fully still persists. I have even deleted Kernel Control Apps and any apps that revolve around Root. I really am not aware of what I should be doing next other than formatting and just hoping nothing worse happens. Also could you name a few apps that could take out logcat even while booting. In a surprising twist of events, now as soon as I hit reboot on the phone, it enters into bootloop and does not return back to normalcy, until connected to a charger or PC via USB. So I guess, I could take a logcat. Thank You again.