Related
I don't even know what kind of title should be for my problem with CWM.
When booting into CWM phone goes in some weird cwm with white letters
PWRReason: PWR_KEY_PRESS then the modes are listed under neath such:
1. RSD
2. FAST BOOT
etc I don't wont to list them all.
I reflashed cwm and now I do have it but first goes into this weird mode then if I choose android recovery goes to real cwm.
How get rid of this weird mod pre-cwm drivng me nuts, any help appreciated.
dito33 said:
I don't even know what kind of title should be for my problem with CWM.
When booting into CWM phone goes in some weird cwm with white letters
PWRReason: PWR_KEY_PRESS then the modes are listed under neath such:
1. RSD
2. FAST BOOT
etc I don't wont to list them all.
I reflashed cwm and now I do have it but first goes into this weird mode then if I choose android recovery goes to real cwm.
How get rid of this weird mod pre-cwm drivng me nuts, any help appreciated.
Click to expand...
Click to collapse
i'm not entirely sure what you are saying or talking about. i just assume you mean when you start in the bootloader you have to navigate to android recovery in that "menu" to go into the recovery? if so. that's normal.
dito33 said:
I don't even know what kind of title should be for my problem with CWM.
When booting into CWM phone goes in some weird cwm with white letters
PWRReason: PWR_KEY_PRESS then the modes are listed under neath such:
1. RSD
2. FAST BOOT
etc I don't wont to list them all.
I reflashed cwm and now I do have it but first goes into this weird mode then if I choose android recovery goes to real cwm.
How get rid of this weird mod pre-cwm drivng me nuts, any help appreciated.
Click to expand...
Click to collapse
Yeah its the bootloader and there is nothing you can do to change it to my knowledge. But most custom roms come with a power button option to 'boot to recovery' so you will very rarely ever have to see it.
Your boot logo, the motorola dual core startup screen, was erased. Flash another boot logo.
Sent from my MB855 using xda premium
hoslayer13 said:
Your boot logo, the motorola dual core startup screen, was erased. Flash another boot logo.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Yes, I did erase something when got stock I couldn't go back.
Now when normal power still goes to that screen first then to operating system.
So just flashing boot logo would cure this problem? if any links to that appreciated too, meanwhile I look for one, thnaks.
I did it, thank you hoslayer13, big help and it works.
hoslayer13 said:
Your boot logo, the motorola dual core startup screen, was erased. Flash another boot logo.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Gave you a thanks just for your username, it made me laugh
Sent from my Photon 4G via Tapatalk 2
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
U try running the RUU?
Sent from my EVO using XDA
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Gotta do it...
sent from my EVO LTE
See post edit.. : S
naterz said:
Was thinking about trying that. Worried this may brick my secure element : S
Edit: tried the RUU (RUU_JEWEL_CL_ICS_40_Sprint_WWE_1.12.651.2_Radio_1.02.11.0423_2_NV_SPCS_2.28_003_release_257970_signed), got an unknown error. Attempted the error recovery method from RUU but was unable to get to the bootloader screen...****.
Click to expand...
Click to collapse
where did you get the 1.12.651.2
all i can find is 1.12.651.1
shipped-roms.com. I guess i could try the .1 version
when i try to run the .1 ruu, it shows im on 1.12.651.1_R2
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
naterz said:
Just tried the .1 RUU, got error [155]: UKNOWN ERROR again... gonna try the Recover option thru that..
edit* error 155 again after Recovery option success and RUU reflash :'(
edit* I'm not too familiar with ADB, but do you think I could get to my hboot/bootloader screen through it or perhaps Recovery in general?
Click to expand...
Click to collapse
Navigate to your adb tools folder via terminal and type
adb reboot bootloader
tried adb reboot, error device not found : (
ddeecc
naterz said:
Soooo before the flame begins, yes i was stupid to do this so that is covered. Was curious today and never played with the app in question (chainfire 3D) and installed in my LTE. Little did I know this app doesn't work with ICS (so i read?..). Well I installed the driver that came with it and since after initial shutdown from installation, I can only get to my splash screen. I've tried recovery and fastboot combos and neither pass the splash screen >.< Anyone?
Click to expand...
Click to collapse
But you did get to the splash screen and that's a sign of hope..this phone won't even do that. nothing at all screen dead, everything is dead including bootloader. :\
Shutdown the phone and boot into bootloader.
Option 1) do a factory reset and if it doesn't work then,
Option 2) select fastboot then ran Ruu.
Sent from my HTC One X using xda premium
There is no way to boot into bootloader or fastboot, whether through adb or the key combos :S Adb states device not found and the key combos only give me splash then a lightly lit black screen..
Sent from my PC36100 using XDA
Are you positive about not able to boot into bootloader with key combo? Your phone has to pass bootloader before going to the splash screen.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
So you tried booting as instructed as the above link?
Sent from my HTC One X using xda premium
Ive never really pressed the power button a second time after the initial let-off. I'll give it a shot when I get home, but I'm expecting the same results. Just FYI, I DO see the two Orange bars move on the splash screen (upper right) before it goes blank..
Sent from my PC36100 using XDA
Sounds like a case of the looped boot screen
Sent from my HTC One X using xda premium
UPDATE! Phone was completely drained when i got home...plugged into charger, orange light came on! Was able to enter the bootloader through the key combo and successfully entered my TWRP to do a nand restore. Restore went well and am now running again! Brick fixed by draining battery!
Good to hear:good:. brick was fixed by draining battery :what: then why did you need to do a nand restore? Whatever worked for you
why i said it was fixed via drain was that the charge light finally came on after it died and was plugged in, therefore it allowed me to access bootloader which let me into recovery to restore my backed up clean system files. When the nand restore was completed i was actually able to pass my splash screen! : )
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
plaster said:
I know how to put the boot loader into fastboot mode, power on while holding up. Problem is, I can't get it to load. It started after installing the SlickV6 Rom. Anyway, when I attempted to load the bootloader, the phone shows a black screen inof the fastboot usb text. Worst of all, rebooting the phone will only boot back to this black screen. I have to LGPNST back to stock just to get the phone to load.
Edit: Ok, LGPNST Again, rooted, unloacked, then tried to use Quick Boot to boot directly to recovery, and I get the exact same issue. It's almost as if the recovery is corrupted and it's not allowing me to load the booloader. Problem is, if I can't get into fastboot usb mode, or recovery, I can't flash a new recovery. This is awesome.
Click to expand...
Click to collapse
Try redownloading Freegee and rerunning it. After the phone boots up download GooManager, hit menu, and then choose install openrecovery script. Once it downloads and installs, power down the device. Hold volume up + power until you see the LG logo and it goes black with text. Press volume down twice and then power. It should boot into TWRP recovery. Once you make sure it's working you can flash Sk8's CWM recovery, I you want too.
It's the black screen with text that won't load. If I don't unlock the bootloader the phone ignores the button commands. Once I unlock the bootloader, the phone will boot fine, until I attempt to load the bootloader. It just loads a black screen and sits there forever. The phone will never boot past this, even while forcing a reboot by holding power. I'll give your method a shot. Worst that can happen is another LGPNST.
EDIT: Nevermind the above. It's the act of unlocking the boot loader that's actually causing the phone to not boot. After typing the above response, I unlocked via freegee and rebooted, it shows the LG Logo, then just a black screen and it's stuck. Running LGPNST again. I have no idea what could have happened to the booatloader that would cause it to be unable to unlock without bricking my phone.
EDIT 2: Just tried the freegee.bat from the PC. Says the phone has been liberated, but does the exact same thing. I am stumped. I hope I don't have to wait for ATT to release an update so I can run something other than stock.
Sent from my LG-E970 using Tapatalk 2
Looking through the freegee thread, this seems to be a common problem with the newest freegee. Gonna try an older version and see if that's the issue. If not, guess I'm stuck with simple root until I have time to get on irc and see if anyone knows how to fix the corrupted partition.
What firmware u flashing back to with lgnpst? 10o or 11c
Sent from my LG-E970 using xda app-developers app
10o
Sent from my LG-E970 using Tapatalk 2
Root with korean root then 0.5 freegee u should be fine
Sent from my LG-E970 using xda app-developers app
You mean LGPNST with Korean firmware? Never saw Korean root.
Sent from my LG-E970 using Tapatalk 2
I'm at work now but send me a pm or get on irc this evening and we can fix this for ya
Sent from my LG-LS970 using xda app-developers app
Ok, will do. Thanks in advance.
BTW, iamtha1, I tried the Korean Root. It took, but I had the same issue. The only upside to this is that I'm still able to use the phone. It's the stock firmware, but it's not so bad once you freeze the excessive AT&T bloat.
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Salsathe4th said:
I am having the same problem, my battery has been acting weird so i drained it completely, now it wont even boot past the black screen with blue text saying recovery. The power button wont do anything so i just have to hard reboot (power +volume up). It will just boot back into that same screen... I have the sprint version with zvb and not rooted or unlocked. please help
Click to expand...
Click to collapse
Why are you posting here then? Go to the Sprint LGOG forum.
Hi,
I have a Galaxy Nexus with the volume buttons spoilt (not functioning). It is rooted and running on AOKP's 4.4 rom. I accidentally installed the wrong kernel and while panicking, I wiped the data and davlik cache. Now, I am stuck in boot loop. Also, when I plug it into the computer, the phone is UNAUTHORIZED according to adb server.
Is there any way to authorize my phone without booting into the OS itself?
or
Is there a way to boot into bootloader/recovery without authorizing the phone and without using the physical buttons of the phone?
mljh said:
Hi,
I have a Galaxy Nexus with the volume buttons spoilt (not functioning). It is rooted and running on AOKP's 4.4 rom. I accidentally installed the wrong kernel and while panicking, I wiped the data and davlik cache. Now, I am stuck in boot loop. Also, when I plug it into the computer, the phone is UNAUTHORIZED according to adb server.
Is there any way to authorize my phone without booting into the OS itself?
or
Is there a way to boot into bootloader/recovery without authorizing the phone and without using the physical buttons of the phone?
Click to expand...
Click to collapse
Unfortunately given the circumstances you've presented, you'd appear to be stuck like that unless you can get those volume buttons working. Because you can't get to the boot loader and recovery or get the phone to boot and even worse, adb not functioning, you're stuck that way. Unless someone knows something i don't, it's just the way it is.
Sent from my LG-LS980 using xda app-developers app
Critical Detox said:
Unfortunately given the circumstances you've presented, you'd appear to be stuck like that unless you can get those volume buttons working. Because you can't get to the boot loader and recovery or get the phone to boot and even worse, adb not functioning, you're stuck that way. Unless someone knows something i don't, it's just the way it is.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
oh.. sigh.. thanks alot! =)
mljh said:
oh.. sigh.. thanks alot! =)
Click to expand...
Click to collapse
Has anyone solved it out? Got really similiar problem. Stuck in bootloop + hardpressed vol up. Vol Down should work properly tough, but have to admit that problems occured using VOL Down or even power beacause of hardpressed VOL UP. My device (Htc ONE S - s4) is fully rooted, unclocked, etc.)
Is it possible that Bootloader got broke somehow?
Stuck in samsung boot loop
i have samsung galaxy s3 , i have install stock rom by odin but my phone is stuck in samsung boot loop..its not ending up my is also draining
plzz help
meet19 said:
i have samsung galaxy s3 , i have install stock rom by odin but my phone is stuck in samsung boot loop..its not ending up my is also draining
plzz help
Click to expand...
Click to collapse
Hello,
I've just solved problem of my own with it
I enclose my simple solution
http://forum.xda-developers.com/htc...-to-bypass-unauthorized-t2954557#post57153022
Basically once you get to the bootloader everything should be easy
Hello guys. I have this Amaway A725 Tablet which I have rooted a month before. I tried to change the boot animation, which was when my tablet started rebooting and stuck at boot screen. Then I managed to install device drivers for MTK 6572. Then I tried to boot into bootloader using adb reboot-bootloader. My tab switched off and now I cannot even switch it on. I fear that I would have bricked my tablet. Please help me.
Goushique said:
Hello guys. I have this Amaway A725 Tablet which I have rooted a month before. I tried to change the boot animation, which was when my tablet started rebooting and stuck at boot screen. Then I managed to install device drivers for MTK 6572. Then I tried to boot into bootloader using adb reboot-bootloader. My tab switched off and now I cannot even switch it on. I fear that I would have bricked my tablet. Please help me.
Click to expand...
Click to collapse
I don't know the device, but I don't think you can brick a device just by changing the boot animation.
Can you reboot in recovery? If so, do a full wipe
Sent from my GT-I9100 using XDA Free mobile app
totalnoob34 said:
I don't know the device, but I don't think you can brick a device just by changing the boot animation.
Can you reboot in recovery? If so, do a full wipe
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
A factory reset would not affect the boot animation in any way,shape, or form.
OP: You'll have to see if you can find the stock firmware somewhere. Unfortunately, with little to no documentation and not much incentive for manufacturers making cheap android stuff to bother with all that, it could be quite a task.
es0tericcha0s said:
A factory reset would not affect the boot animation in any way,shape, or form.
OP: You'll have to see if you can find the stock firmware somewhere. Unfortunately, with little to no documentation and not much incentive for manufacturers making cheap android stuff to bother with all that, it could be quite a task.
Click to expand...
Click to collapse
Yep I tried factory reset from the Android System Recovery, by pressing the Vol+ and Power Keys. But now I count switch it on by any means and key combinations and I cannot remove the battery because it is irremovable. But if I plug it into my PC Device Manager shows this device "MTK USB Port" connecting and disconnecting. So what do I do?
Found the firmware and downloading it from Amaway.cn website. But what do I do now, how shud I flash it, bcoz my tab wouldn't start up by any means, no recovery, no fastboot, not even showing the charging status. Please guyz I totally depend on u, help me !!!
Folks, tried using the MTk USB Port and Mtk Droid Tools, but how to get the firmware.info or pmt file for it?
BROM ERROR : S_BROM_CMD_STARTCMD_FAIL (2005)
[BROM] Can not pass bootrom start command! Possibly tartget power up too early.
[HINT]:
What do u mean by this???? I used SP Flash Tool v5.1348.00