Database Develop

Not Booting! - stuck at splash. Please Help

Hi,
My roger's dream decided to stop working today (i've only had it for like a week). It's rooted, but I haven't done anything major to it. It was running stably for a couple of days after rooting it so I'm fairly confident that it's unrelated.
I wasn't doing much at the time, messing with Klaxon i believe, but it randomly shut off and now whenever it tries to boot, it gets stuck at the splash screen (just playing it over and over).
I've tried booting in safe mode (w/ Home button) and it won't come up. That's about all i know how to do. can anyone help me out with this?
Thanks so much, i'm in a state of crisis right now.

Yea just wipe the phone, reapply the update.zip and it should be good. If that fails. You may need to backup your sd card, wipe that, redo it and put just the apps and apps-private folder back in and link it. (Unless your rom automates that for you)
You can also try in the recovery console from cy the alt-x to terminal, then type fix_permissions and do a fix ext filesystems. That may restore you as well.

Does pressing Power + camera key get you into the fastboot screen?

[HELP] Power/End, Call, Menu, Home and Back Buttons not Working on G1

So, this didn't happen until the other day, but suddenly, my Power/End, Call, Menu, Home and Back buttons aren't working on my G1. The only way I could get the phone to power up was to plug it into a USB, and then place the battery in to force a boot. I can't reset anything, leave screens, accept calls, or do anything really because of this issue, and it's debilitating.
Before you tell me to search, I'll tell you that I've already searched multiple times. I know the rules of the forums, and I wouldn't have created a new thread if the issue had already been solved by a previous thread. However, if I missed a thread that could help, rather than saying "SEARCH FOR CHRIST'S SAKE", I'd appreciate a link.
Thanks, guys. XDA has always been useful to me, and I really just want a solution, since the G1 has been the best phone I've ever had.
If it matters, I'm using Cyanogen 4.1.11.1, with the 2.6.29.6-cm41 kernel. I'd upgrade, but I can't, since my home button isn't working.

Try wiping, enter terminal or use adb shell "reboot recovery" to enter the reboot screen. Once you have wiped or reflashed, use "reboot"

I can't wipe or flash, because I need the home button.

I know, to enter recovery without using the home button user adb shell reboot recovery

Yes, but how do I wipe from there? When I select wipe, it asks me to press the home button.

Oh my you really seem to have dug yourself into a hole here... not good. Hmm. Try wiping from the Settings on your phone, there is a factory reset on there.

"No reset was performed because the System Clear service was not available."
Is there a way to wipe from the console, or adb shell?

electrolemon said:
"No reset was performed because the System Clear service was not available."
Is there a way to wipe from the console, or adb shell?
Click to expand...
Click to collapse
Now thats a right proper one mate..anyway how do you tuen her on if the button doesnt work?

You can use fastboot to clear your data partition (userdata). But this doesn't sound like a software issue if the buttons aren't even working within recovery/bootloader, it sounds more like a hardware issue. I would take it up with T-Mobile or HTC.

I was able to turn it on by plugging in the battery while it was plugged in via USB, but now that doesn't even work. I have a feeling that I just wiped the entire system, as I can only access the fastboot, and when I try to boot normally, I just get stuck at the white G1 screen. So it seems I have two issues now. Any solutions for either? Unfortunately, my G1 is 5 days out of warranty, too.

If you can access fastboot, then you can flash RC29 and start from the beginning again or you can flash a nandroid backup that you can get from your sdcard to your PC.

Any idea how to flash a nandroid backup or downgrade to RC29 if I don't have working power, home, menu, or call buttons? Like, is there a guide?

Nobody has any solution that doesn't require me to get a replacement phone? I'm willing to pay for a solution. I'm in dire need of this phone. I hate the Blackberry Curve so much.

electrolemon said:
Nobody has any solution that doesn't require me to get a replacement phone? I'm willing to pay for a solution. I'm in dire need of this phone. I hate the Blackberry Curve so much.
Click to expand...
Click to collapse
I think your phone is pretty shot. Even if you do manage to get into a ROM, it seems unlikely that your buttons will come back to life. Without being able to use the home or back buttons, you'll be stuck in whatever application you opened until you restart your phone.
If you want to try it out, you can flash an old nandroid backup by first, copying system.img, data.img, and boot.img from the nandroid folder and pasting it in the same folder as your fastboot. Then, boot into the bootloader and type:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
fastboot reboot
which will restore the nandroid backup.

SOLUTION
I found a fix for this problem on another Android forum, essentially you install "Anycut" from the markey and create a shortcut to the "setup wizard", I had a three setup wizards, the third one worked for me and ran all the way through the phone setup, the others just exited as soon as I selected SKIP. It works, prior to that my HOME, MENU and CALL buttons were not working. I think that a faulty update.zip must have caused permission issues with the software, I had installed some new fonts and straight after I lost the buttons!
http://androidforums.com/updates-cupcakes/4884-can-fixed.html

[solved]bootloader won't let me update

So usually I've read this is a matter of the wrong spl, or unsigned files, or other things that don't seem to be my problem. I've searched for days now and would LOVE some help.
I'm downgrading for a warranty return because my touchscreen doesn't work. I try to follow the directions found in several threads but I get hung up at the same spot.
When flashing the dreaimg.nbh file in the stock bootloader, bootloader starts, checks, then I get to the screen that asks you to press power to flash, or action to cancel. No buttons on this screen do anything. Not the "3 finger solute" to reboot, not power, not action, nothing. Just no response. And yes, I waited, and waited.
I think I've tried about every combination of everything I can think of, but please, your suggestions mean a lot to me.
The only thing I can think of, is that maybe the updated radio isn't compatible with RC29, and the phone knows this somehow and won't let me flash RC29 with my current radio? Does that make any sense? Do I need to flash an old radio, then the dreaimg.nbh?
Thanks!
(anybody wanna tell me how to get a screenshot from the bootloader and I'd be glad to show it, but it's just the standard screen)

I say try! ahaha
Same thing happened to me with the touchscreen lol.
I just flashed the old image didn't even bother to update or anything and just sent it in.
And I didn't get charged for voiding the warranty.

And no the new radio is compatible with RC29 I've used my friends phone when we were rooting it and he had the new radio.

Thanks for that, if I can't figure it out, I guess I'll try the warranty. I'm still going to work on it though, I can't imagine that someone hasn't had an unresponsive bootloader before though, and know how to fix it.
I've always done things the retard way, but I've spent the last week learning ALOT. I've got adb and fastboot setup, is there a way to flash the nbh file via fastboot or adb, bypassing the bootloader?
And FYI for others, with the nonworking touchscreen you can't "press the droid" after a factory reset. SDK, and androidscreencast fixed that, you can see your screen on your computer and use your mouse to click!
http://code.google.com/p/androidscreencast/
I also just got droid explorer, which lets you do lots of things with a GUI, including invoke androidscreencast, man that would've been easier a week ago! At least now I am able to use the phone as I had to disable the wipe unlock, and touch the droid to recover from a wipe!
I imagine this would be perfect for people with broken screens as well!

the .NBH includes EVERYTHING but an SPL... it rewrites Radio, splash1 system and usrdata...... if you cant press the action button, first try re-flashing the SPL, then try cleaning out your trackball
the action button is the trackball BTW...

Thanks for those tips. But I've done that and it still doesn't work. Even tried downloading the spl from a variety of sources, and doing a checksum to make sure it's not corrupted. And the trackball works in every other application. Basically, the stock bootloader just won't respond to any command (action to cancel, power to update, 3 buttons to reboot, nothing). It DOES recognize the .nbh, which is a step further than most bootloader fail threads I see.
Is it possible to flash an nbh file using fastboot or adb? I've figured out how to do update.zips this way, but not .nbh. I'd still have a custom bootloader, but everything else would be stock.
Thanks again everyone!

So if anybody can help, maybe this bit is useful too, I get no response from the hard spl either. Example, it is my understanding that the standard hard spl screen (with no .nbh file on card it dislplays phone radio info at top, serial0/10, 3 android skaters at bottom) that screen I should be able to press call+power+menu to reboot, right? I get nothing, and thought I should. This spl won't flash the nbh either, I guess because it won't register the "press power to contine".
1. Any ideas? My keys work when in standard usage and in recovery, why won't they work in any of the spls?
2. still wondering if/how I can fastboot the dreaimg.nbh file?

Make it unbootable (don't brick it - just wipe your current ROM and recovery partition) and restore to stock G1 SPL and if they say anything about "It won't boot" blame it on shipping.
Have you tried updating with a engineering SPL? I don't know if that would have any difference. Also, is your sdcard still partitioned? I think it has to be all fat32 or a goldcard (no idea where a goldcard actually come in on G1).

Brilliant! I bet it is the partitioning! I now remember that I thought about that for a minute, but tried other things. I'll try a fresh, all fat32 partitioning and give that a shot. Otherwise, good call on just deleting the partitions.
(actually excited to have something hopeful to try for a change!)

Solved!
Cheers to you R3s!
If anybody else finds themselves with an unresponsive bootloader, make sure your sdcard is not partitioned.
For the step by step folks who may be wanted to return a G1 to stock, in my case for a warranty return because the touchscreen doesn't work:
put the stock 1 G card in a card reader, popped it in the usb drive of a winxp system, my computer, right click on drive, format (not quick) fat32.
copied over stock spl renamed as update.zip
copied over DREAIMG.nbh
unmount sd card
pop into g1
home+power to get into recovery
apply update.zip
reboot
wipe
reboot + hold camera button
power button to apply
wait, this time I got the status bar immediately
action button to restart when prompted
reboots to spl
3 finger salute to reboot (call+end+menu)
BAM, back to the android to press the button to start
(and fully stuck there now since I don't have a touchscreen, my daughter called me crazy for being so happy, she asked if I fixed it and I said no I broke it!)
So there ya go, anybody else has this problem, reformatting the sdcard isn't enough, you have to remove the partitions.

[Q] cynamod v5 & v6 lock up at the boot screen logo (not the G1 logo)

Hello.
I've followed the wiki to install a cyna firmware onto my G1, but except for one time, it just locks up at the boot logo (android thingy for v6, the color thingy on v5). You know, what gets displayed after the G1.
And I haven't found anything about that, just about if it locks up at the G1.
The first time it didn't lock up, but the apps were erroring up, and after a reboot, it started locking at the boot thingy (sorry, don't know what to call it).
This is the process I used:
flash the dream rom (rc29)
hit enter twice on default screen, type in telnetd, hit enter
download telnet, use it to flash Ramen's thingy, RA-dreamv1.7.0
reboot after it installs, and boot into it.
use it to install the radio for t-mobile
reboot
install danger spl
reboot
install cynamod & tiny google apps
reboot
lockup on the boot graphics
I've done this a few times, use the thing to clear caches and even usb fastboot to clear the system.
Mistakes I've made along the way:
Was given the EB1 rom instead of the CMv6 rom at first. That never made it past the G1 logo, figured it out quick, and was able to boot into recovery and recover.
I also once forgot to do the google apps till after I rebooted the cynamod v6. I haven't done a usb fastboot system wipe though since that.
I'm currently without internet, cept my cell phone, and since I haven't found the tmobile current rom to flash, i'm stuck waiting for an update on the rc29 before I can use easytether (can't install most apps on rc29) to get my laptop online. Of course, i can use my G1 browser then, but as most of you know, it sort of sucks for using the internet for forums and stuff. =)
Anyways, i'd appreciate any help, or links on how to fix my problem.
Oh ya, it says nothing about formatting my SD card or anything, so I haven't.
I don't care really if I have v5 or v6 on my phone, I currently want to do unrestricted tethering till my internet at home gets back on (3rd of Nov). I use my phone for phone calls, and calender, and reading ebooks, but thats about it.
thanks in advance for any help

nyder said:
Hello.
Oh ya, it says nothing about formatting my SD card or anything, so I haven't.
Click to expand...
Click to collapse
Did you ever have ext partition on your SD card (apps2sd)? If so, this is your problem. As a rule, you always need to wipe everything (including sdcard) when going between Rom versions (i.e. 1.6 to 2.2, etc.)
Good luck.

borodin1 said:
Did you ever have ext partition on your SD card (apps2sd)? If so, this is your problem. As a rule, you always need to wipe everything (including sdcard) when going between Rom versions (i.e. 1.6 to 2.2, etc.)
Good luck.
Click to expand...
Click to collapse
No, I didn't.
I thought something like that needed to be done, but I don't recall seeing it on the instructions.
Thank you very much, I'll get that fixed.
Yes, that fixed it. Thanks very much for the help.

Soft brick help. Twrp installed Android won't boot custom rom

I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.

Malistoff said:
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Click to expand...
Click to collapse
Also how important is f. Reset time? I don't totally understand it. Next.. What about having the roms and files I flash on internal memory instead of sd. I'm not sure if I can access the Internal storage. But if I can does that help. Also I cannot access Android at all.. I can either access download mode or recovery. I have been using an external battery charger to charge my battery as well. Due to it doesn't read the charge... But! It did read a charge just fine when I had cm 12.1 working.

I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first

w8wca said:
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
Click to expand...
Click to collapse
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.

Malistoff said:
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Click to expand...
Click to collapse
Reactivation is unlocked. Also I wouldn't be able to change any setting in the phone.. As the phone does not boot into Android. I was just lucky enough to have usb debugging active before this all happened

I am not sure what that is for
But every time I have done a flash it works if you use the steps I had there. (Not really questions)
Sorry I do not have anymore ideas.
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
Are you booting your phone into download mode before you use ODIN?
(I know it's proly a dumb question but just in case)

Yes I am in download mode when using odin.

Malistoff said:
Yes I am in download mode when using odin.
Click to expand...
Click to collapse
Just now I did another full wipe and wipe of cache, davik, system, internal memory and had a successful install of cm12. 1 with gapps.. Everything installed.. Clicked reboot and the phone never came back on. I will try your idea next. I have not tried an idea where I use twrp to wipe everything and reboot into download then do stock rom via odin. If the phone does boot into download from twrp recovery I will try this one time with auto reboot and f. Reset time checked.. If it fails I will try it again with f. Reset time unchecked. I am currently not by my laptop to try this so it will have to be much later in the day.

To boot into download mode: Power off Note 4, hit all 3 of these at the same time until it wakes and vibrates - Power Button, Home Button and Volume Down

I know how to do that lol. I know I'm a junior member. But I'm somewhat intermediate. So cm12. 1 has booted.. However it didn't from a reboot of a flash.. I just took a while shot.. And powered the phone on.. And it booted.. I'm pretty sure in going to run into the problem again.

OK - Well you never know!
I am only a senior member 'cause I am older than Dirt!

Lol. I'm oldish. And trust me this lucky catch I got.. Is temporarily. There is still boot issues. I fear when the phone goes off or is turned off that it won't come on. I do not have a sim card in the phone at the moment which means I can download helpful apps. Like supersu. .. But so far I was able to check settings and get what I can prepared. Also if like to keep this thread open as a log or research tool.

Alright so I like the rom sit most the day.. With minimal to no use.. Most of the day it was fine.. At one point I took a picture and it did as it should.. I cleared all open tabs.. Took another picture and I got a error saying camera wasn't connected.. Finally the phone froze up and rebooted.. And the Camera worked.. Gave it another rest.. Came back to it checked the camera and it was fine.. I put it away for like 10mins then decided to check recording. When I did the phone was not responding to turning back on from sleep mode. Now for as long as I can remember even before this initial issue started.. I was having thr same problems with the phone not coming back on from when in sleep mode.. I dunno what the cause is or hoe to approach it to fix it.

First attempt was to put it to a charger... Registered no charge.. So I removed the battery.. Gave it a few mins.. Pushed down power button.. No response. Something is off with the boot menu.. Like the boot img. File

And finally it's back on.. Normal boot.. I didn't boot from download menu or recovery.. But in all honesty I'm 100% sure this will just happen again.. It seems to happen when I put the phone in the charger.. Then take it out and play with it.. For now in going to let it sit till the battery is in caution. Then charge it. I still have not added the Sim and loaded apps.. I feel that will be a overload of cpu and will most certainly freeze up and crash the phone

Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?

Malistoff said:
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Click to expand...
Click to collapse
Might be stupid I know, but try wiping clean your SD card (back up a copy on your pc first) as well when you factory wipe and make sure that after that, you only add the files you need for recovery. Start up the phone after reset. To get a backup, if you're synced through google, you'll get everything back. If not, only copy your backup from titanium back into your SD card.
I went through a very similar situation last week. Long story short, it seemed the SD card had copied files which would interfere with the system.
Curious, did it happen after marshmallow update?
And did you try to downgrade back to previous lollipop version?

I assume it was Marsh that I was trying to Ota too. I was unable to boot successfully after that first try, so I honestly don't know.. I'm going to try your SD card idea. .. But once all that's done. Are you wanting me to redo a full rom install like through and wipe system, Davik etc etx? Or like wipe everything and start from like odin installing a recovery and so forth?

I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.

Malistoff said:
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Click to expand...
Click to collapse
Well even if you format and you put the SD card back in with all previous files, same might happen.
When you format, just wipe all. Then if you want to downgrade, you need to have the previous version bootloader and baseband FIRST prior to putting the firmware ROM.
A simple (restore) wipe would just keep you at current version. And you can't easily downgrade the easy way from marsh to lollipop. Believe me, I learned the hard way
Flash through ODIN