Affichage des articles dont le libellé est loop. Afficher tous les articles
Affichage des articles dont le libellé est loop. Afficher tous les articles

jeudi 27 mars 2014

[Q] G2 stuck in an installation loop that started while updating to KitKat topic




I am stuck in an installation loop that started while updating to KitKat.

I was happy with my LG G2 (T-mobile, D801G), but wanted to use root apps. So, I rooted and installed TWRP, but did not flash a custom rom.

Tuesday when I woke up there was a message saying I could download KitKat. After installing my last system update I lost root, so just had to unroot and re-root – took me about 15 minutes. So, I decided to go ahead and install KitKat.

It downloaded and began to install, but got stuck in a loop. The LG logo flashes for 5 seconds, the little droid pops up with his stomach spinning and the message “Installing system updates” but shows for only about ½-second. Then the screen goes black for 2 seconds and it starts again.

I can get it into the factory reset screen, but when I say yes-yes, it puts up the message :
Error: Boot certification verify
341120

341170
341220 Secure booting error!
341270 Cause: boot certification verify
341320
341370


Then it sits in a black, but not quite off screen until I hold down the power button to turn it off. When I turn it back on, it shows the logo, then the droid showing the message ‘Erasing…’ for a full second, then switches to the ½-second ‘installing system updates’ loop.
It will go into download mode. When I connect it to the LG flash tool ‘Up Test’ it says all firmware is up-to-date.

I tried this: http://forum.xda-developers.com/show....php?t=2582142 but I couldn’t get Ubuntu 12.04 to install gdisk. Then I noticed that
ls /dev/sd*
returned the same values whether my phone was plugged in in download mode or unplugged completely. The values were
/dev/sda, /dev/sda1, /dev/sda2, /dev/sda3, /dev/sda4.

I tried the next step anyway
gdisk -l /dev/sdb
and got the error saying gdisk was not found, but I could install it with… etc. I tried to install it, but it wouldn’t work.

This is the second phone I’ve rooted – I had my HTC Sensation rooted for years, and flashed many ROMs. I hadn’t played much with the G2 because I liked it just the way it was – but had to have some rooted apps. I also have an HP Touchpad running Cyanogenmod. My experience with Linux is limited. So I’m just one step up from a noob.

Any advice would be appreciated! I bought a go phone so that I can take my time and fix my G2 right. :-/





mercredi 26 mars 2014

[Q] Shutdown loop topic




I've already ask this question on sonymobile forum, but have no result. Trying to post it here.

I upgrade my Z1 to 4.4.2 and get the next issue.
When I switch off my phone with long press power button -> "swich off phone", its successfully shutting down but after 5-10 sec. show startup SONY logo then swich off display then show logo again and so on endlessly...
It was very unexpectedly, when I swich off Z1 and put it into pocket, after cuple of days I found it totally discharged. I cant make phone alive with wall charger and only 2-3 hours on USB charger can reanimate Z1.
I was try everything what I read no docs and forums, reflash with SUS and sony PCC, flash different versions of FTF via flashtool, boot on safe mode etc, but nothing helps :(

Is there software problem with shutdown loop or problem with battery controller or something else? How can I fix it? Any considerations?

P.S. Small "force shutdown" button or Power+VolUp combination sometimes helps to shutdown phone.





[Q] Stuck in boot loop please help topic




While flashing a new rom, something happened and now I'm stuck in bootloop. I can access hboot/fastboot and the computer does recognize the phone when hooked up via usb. I've tried running an RUU, but I got an error message stating I was installing the wrong one. I can't seem to find any RUU's that will download completely. Can anyone please help me save this phone? My wife is going to kill me if I can't get it working. I'm not that familiar with running cmd prompts, so if you could walk me through it, or send me to a youtube video, I would be greatly appreciated.

I was running TWRP 2.6.0, and the issue occured when I tried flashing to 2.6.3 and then tried installing 4.4 kit kat. The more I messed with it, the worse it got. I had backed up the phone and used it several times to reflash it to the back up, but finally, it gave out too. Now I have no recovery and no clue where to begin. I just want this thing back to stock. Here is what I've working with:

M7_WLS PVT SHIP S-ON RH
HBOOT - 1.56.0000
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Jan 23 2014,22:11:35.0





Reboot Loop! topic




Hello,
I have the HTC One (m7) HBOOT 1.56.0000.
I rooted my phone yesterday and flashed The Android 4.4 KitKat Google Play Edition ROM for Sense- Based HTC Ones(getandroidstuff com/install-android-4-3-htc-one-google-play-edition-rom/. Now, I am in a reboot loop. I have already cleared the Dalvik Cache.
Please Help!!





mardi 25 mars 2014

[Q] Boot Loop - Have I tried Everything?!? topic




Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.

This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.

Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.

Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
  • Anything else I should try before giving up?

  • Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?

  • If custom ROM is last chance, is there a really solid one running 4.3 and Sense?


THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...





someone please help. Asus memo pad 7 hd stuck in boot loop topic




i rooted my tablet successfully about a week ago. then tried to apply a skin i found on tablet market. it shut off rightt away and now wont boot past the loading cirle screen. i cas n get into recovery but every thing on this site ive read about & tried has not worked. either it doesnt show files i put on sd card. oe'er the file leads to an empty folder if it does show up. when connected to
the computer it has an exclamation point & says drivers have concluded. but wont show any files on tablet at all. to top everything off i forgot to take the sd card out before taking the back off and it broke the mount. now i got it to read it a couple times after putting paper behind the sd card.... but it hasnt always worked. someone please .help me save my memo paD??!"!





lundi 24 mars 2014

Help with Boot loop asap topic




Hi! i was installin the new rom update from 10.4.B.0.569 to 10.4.1.B.0.101 and now my phone is locked on Boot loop. a cannot access CWM it boots to sony logo over and over again. I have tried to do the power+volum up, and flash the FTF again. several times. can anny one plz help me. I'm about to give up and buy a new phone.

Sorry for my bad grammar but i'm from norway.

This is on a Xperia z c6603





[Q] Help with boot loop topic




Hi! i was installin the new rom update from 10.4.B.0.569 to 10.4.1.B.0.101 and now my phone is locked on Boot loop. a cannot access CWM it boots to sony logo over and over again. I have tried to do the power+volum up, and flash the FTF again. several times. can anny one plz help me. I'm about to give up and buy a new phone.

Sorry for my bad grammar but i'm from norway.





[Q] Samsung infinite loop! NO Download or CWM! please help! topic




Hi guys,

I have messed up problem and I'm hoping that you could help me out!

The situations is as follows: My samsung I9300 is stuck in a infinte boot loop, showing only the ''Samsung Galasy SIII GT-I9300'' image and than it restarts again with the same image. I tried odin, but my pc can't recognize that s3 is on. Also odin cant detect my phone due to the boot loop I think. Furthermore, i can only get into download mode, but when i press the volume button up after I gett the warning sign, the phone starts rebooting again! I am completely out of ideas. What do i need to do now? Also, what does this problem mean? I hope you can help me out

Thanks in advance





dimanche 23 mars 2014

[Q] samsung s4 clone boot loop problem topic




really need help for my s4 problem

rooted by framaroot
when i install cf3d it will be hang on booting..
and ill go to technichan to solve it but nothing happens..
ill try to read your forum and ill join to help my problem..
my phone is

device name: galaxy s4
model number: GT-19500
andriod version: 4.4.4
baseband version: 19500XXUAMDE
kernel version: 3.4.5
whl@server3#1
thu dec 5 21:22:09 cst 2013
build number: JDQ39.19500XXUAMDE
software version: v92.04


when i connect to pc the driver read as
F: Linux File-Cd gadget Usb Device
G: Linux File-Cd gadget Usb Device

?Other Device
?CDC serial

i cant open that driver..

how do i back my s4 running like new as i buy?!!

please help me for my problem thank you





loop topic




for i in (10**p for p in range(3, 8)):
print(i)





mercredi 19 mars 2014

Stuck in boot loop after flashing CM7 topic




Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...





mardi 18 mars 2014

[Q] Boot Loop Problem topic




I was trying to root my Galaxy Note 3 and when it went to restart it only goes tot he Samsung Galaxy Note 3 splash screen with the following at the top:

Recovery Booting....
Recovery is not SEANDROID enforcing
Set warranty bit : recovery

Then it powers off and does this again. I continually cycles through this screen. I have tried to power on in download mode to flash a stock firmware to it but it will not open in download mode.





lundi 17 mars 2014

stuck in boot loop after viper install topic




istalled viper 2.0now my phone stickes on the htc screenim unlocked
hboot 1.73
ine got access still to custom recovery twrp its an att htc one x + and it was on 4.2 sense 5 before running viper any help would be appreciated
i just want to go back to 4.2 instead of esing with anything else this is way out of my range





Boot Loop after Editing Build.Prop topic




Hi guys,

I made the WiFi change to the build.prop to try and fix the Wifi passwords issue. I had to change permissions to write and forgot to change it back (I realize this now... lol). I have the backup on my computer and I have access to TWRP (running stock D803 ROM).

Is there a way to flash this file back other that flashing the ROM? Or should I just flash the stock D803 ROM? I want to avoid losing my data.

What is the best way?





[Q] Loop Device Kernel topic




Hi, I am trying to run Kali Linux on my Nexus 5 via Complete Linux Installer. I have root and busybox and everything like that but I do not believe I am running a kernel with loop device compatibility which is required to run the linux alongside android. I am wondering if there are any kernels which currently support this for the Nexus 5.
Thanks.





mercredi 12 mars 2014

[Q] My phone is stuck in boot loop xperia ion topic




my fone was stuck in boot loop so i let it die and i charged it and after get the red led after a while sony logo would come on and the fone wud keep resetting then it stops and then does it again some mins after...could somebody help me plz





mardi 11 mars 2014

[Q] LG G2 ATT D800 stuck in boot loop topic




I recently got an lg g2 and rooted it, but it would never boot into recovery mode correctly. Well one night i was trying different chargers because it kept saying it was charging and would vibrate and say it was charging again, i woke up and the screen was lit but wasnt booting. I tried to restart it, no affect, tried to recover it, when it does this it goes into the blank screen again and does nothing, it also wont go into download mode. when plugging into the computer around 15 drives pop up and say they need formatting and it says that is is some qual disk drive and wont install any drivers. tried adb and the phone isnt recognized. am I SOL? What else can i try. One disk drive mounts and has a folder named image.

Short version
-wont boot
-no download mode
-recovery does nothing
-computer does not recognize as phone
-comes up with 15 disk drives that needs to be formatted
-one has a folder named image with stuff in it
-adb wont recognize phone
-tried the lg recovery tool and b/c no download mode it will not read the phone (tried to force install the drivers of the phone to see if it would work to no prevail)

Help :crying:





lundi 10 mars 2014

[Q] No OS in bootloader and stuck in boot loop with every ROM topic




Hey Guys,

I was using my HTC One as normal until 2 days ago when the phone froze up while receiving a call.
I was running SlimKat 4.4 stable 3 ROM and it was running fine until then
I thought a quick reboot of the phone would fix it but all I got was a black screen with the soft buttons at the bottom turning on and off when I pressed the power button as if the phone was acting normally

With this I tried to reflash the ROM through CWM but it wouldn't mount the data properly and couldn't follow usual flashing procedures
I proceeded to try flashing TWRP and flash the ROM from there but still nothing
I then accidentally completely wiped the phone of everything and lost the OS
I then had to sideboot a ROM but got stuck on a bootloop

For the past 2 days I've been going through endless threads and couldn't find anything to fix this.
Everytime I flash a ROM it just goes into bootloop after the "HTC Quietly Brilliant" screen
I've tried flashing ROMs through both TWRP and CWM but all of them do the same thing.
The ROMs I've tried are: Android Revolution HD 36.1, Venom, Slimkat and Liquid

The closest I've got to the phone working as normal is Liquid.
With Liquid the phone bootloops once or twice then boots normally however there is no sound output and cannot make calls.

Also my phone is *tampered* and *Unlocked* with Hboot 1.54 as well as S-On as Rumrunner and firewater couldnt S-Off.

I hope you guys can help!
Thanks in advance





samedi 8 mars 2014

[Q] HTC One in Recovery Loop topic




So today I attempted to install CyanogenMod, and everything was going smoothly right up to when I actually tried to flash the rom. I flashed the international rom instead of the AT&T and after that I was stuck in Team Win Recovery mode. Now every time I turn off and then on my phone, it goes through the htc one screen, then it turns black, and then it goes again in htc one screen but now with the words entering recovery mode in pink letters. I'm not sure if it was me flashing the wrong rom or if it's because it was on android 4.4.
I hope that makes sense.