Hi - There seems to be a problem with the length of time it currently takes the Arc to boot up.
I'd like to see what boot times you're all getting.
Please post specific times. NO APPROXIMATIONS PLEASE time from the Vibrate to the launcher first appearing on screen.
Also post the following facts.
Branded - [Yes/ No] and state Brand [Orange/ Vodafone/ etc]
ROM - Eg 3.0.A.2.184
Rooted - Yes/ No
Bootloader Unlocked - Yes/ No
Launcher - Stock/ LPP/ Go etc..
Boot time - xMins ySecs
I'll kick it off...
Branded - No
ROM - 3.0.A.2.184
Rooted - Yes
Bootloader Unlocked - Yes
Launcher - Stock
Boot time - 2Mins 18 Secs
Branded - No
ROM - 3.0.A.2.181
Rooted - Yes
Bootloader Unlocked - No
Launcher - Stock
Time 46 seconds from Vibrate to the Pin Entry Screen
Who can do it better ?^^
YESSS!! I broke the record!!!
Branded - No
ROM - 3.0.A.2.181
Rooted - Yes
Bootloader Unlocked - Yes
Launcher - Stock
Time: 2' 31"
Really don't know what's goin' on here because sometimes it takes less than a minute to turn on! (The time measure is between the vibrations, when you first press the button and then when the white leds turns on.)
reptile64 said:
YESSS!! I broke the record!!!
Branded - No
ROM - 3.0.A.2.181
Rooted - Yes
Bootloader Unlocked - Yes
Launcher - Stock
Time: 2' 31"
Really don't know what's goin' on here because sometimes it takes less than a minute to turn on! (The time measure is between the vibrations, when you first press the button and then when the white leds turns on.)
Click to expand...
Click to collapse
yes the Rekord off the Slowness
Branded - No
ROM - 3.0.A.2.184
Rooted - Yes
Bootloader Unlocked - Yes
Launcher - launcherpro
Time: 1' 26"
Thats from pressing the button to everything loaded
Edit: just tried again and 1'16" its getting quicker lol
Sent via noahs ark
Install all the apps to the SD for a fast boot
yes and delete or block all the bloatware so you can reach also 45second to boot up
I don't know what's the benefit but here is mine
Branded - No
ROM - 3.0.A.2.181
Rooted - Yes
Bootloader Unlocked - No
Launcher - Launcherpro
Time: 58 Seconds.
prathaban said:
I don't know what's the benefit but here is mine
Branded - No
ROM - 3.0.A.2.181
Rooted - Yes
Bootloader Unlocked - No
Launcher - Launcherpro
Time: 58 Seconds.
Click to expand...
Click to collapse
And we have a winner lol what a fun thread ;-)
Sent via noahs ark
Branded - No
ROM - 3.0.A.2.181
Rooted - Yes
Bootloader Unlocked - No
Launcher - Stock
Time 46 seconds
Lol. Winner???
Just trying to see how much variance there is and if any of the factors we're listing affect it..
Branded - Yes, Rogers branded
ROM - 3.0.A.2.181
Rooted - No
Bootloader Unlocked - No
Launcher - Stock
Boot time - 00:03:15.443
3 god damn minutes. It's Blackberry-esque :/
****ing 3 minutes..
Rooted & Deleted some bloatwares as well, using stock Home Launcher!!
Branded - No
ROM - 3.0.A.2.184
Rooted - Yes
Bootloader Unlocked - No
Launcher - Stock
Boot time - 48 seconds
Sent from my LT15i using XDA App
IntMD said:
Branded - No
ROM - 3.0.A.2.184
Rooted - Yes
Bootloader Unlocked - No
Launcher - Stock
Boot time - 48 seconds
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
ok so for those getting quick boot up times..
Is there anyting else you've done that might be helping??
im_iceman said:
ok so for those getting quick boot up times..
Is there anyting else you've done that might be helping??
Click to expand...
Click to collapse
I've a bunch of frozen apps in my Titanium Backup. Other than that, well I don't remember doing anything special
I think you should add the battery pull (remind me blackberry time) before trying to check how long is your reboot, because it happens to me to click on the ON button as soon as the screen went black and my phone took less than 20 secondes to reboot, it seems that everything is still in the RAM. Plus, when you flash by SEUS they say to turno off your phone during 30 seconds before relaunching it with.. So maybe guys who have like 30 seconds to reboot may try to pull their battery and then launch their arc...
im_iceman said:
ok so for those getting quick boot up times..
Is there anyting else you've done that might be helping??
Click to expand...
Click to collapse
Not really... Mine has always been about that. Removed a few things like the setup guide and whatsapp etc. I actually thought mine was quite slow until I read some times on here
Sent from my LT15i using XDA App
Related
Hi,my first post at xperia !!!
I am new at the Xperia modding but old from Galaxy s-1,2,3 etc.
I have these Queries to make things clear:
My phone came with 10.1.A.1.434
I un locked my bootlader and rooted with recovery exactly fine from the forums guides.
My question is If I flash the new updated rom, my root will be removed for sure, and also the bootloader will be re locked?
And If that happens, how can I root my phone again since there is no official CWM updated yet?
waiting for your reply guys
angry_machine said:
Hi,my first post at xperia !!!
I am new at the Xperia modding but old from Galaxy s-1,2,3 etc.
I have these Queries to make things clear:
My phone came with 10.1.A.1.434
I un locked my bootlader and rooted with recovery exactly fine from the forums guides.
My question is If I flash the new updated rom, my root will be removed for sure, and also the bootloader will be re locked?
And If that happens, how can I root my phone again since there is no official CWM updated yet?
waiting for your reply guys
Click to expand...
Click to collapse
Can't really say for sure about the bootloader since I haven't unlocked mine, but the root will be removed if you flash a new updated firmware through Flashtools (happened to me when I updated the original .434 with the .423 - with a full wipe - and when I flashed the brazilian .423 over the middle eastern/asian .423 without the full wipe).
My guess is that the bootloader with be re-locked when you flash the ftf with Flashtools, but you can unlock it again with Flashtools itself.
First, you'll need to use DoomLord's easy root tool (v15 worked for me with the .423 firmware, so my guess is that v17 should work as well). Then you can flash the dual TWRP/CWM and unlock the bootloader again.
Best regards.
Tiu Fiu said:
Can't really say for sure about the bootloader since I haven't unlocked mine, but the root will be removed if you flash a new updated firmware through Flashtools (happened to me when I updated the original .434 with the .423 - with a full wipe - and when I flashed the brazilian .423 over the middle eastern/asian .423 without the full wipe).
My guess is that the bootloader with be re-locked when you flash the ftf with Flashtools, but you can unlock it again with Flashtools itself.
First, you'll need to use DoomLord's easy root tool (v15 worked for me with the .423 firmware, so my guess is that v17 should work as well). Then you can flash the dual TWRP/CWM and unlock the bootloader again.
Best regards.
Click to expand...
Click to collapse
in this case do I just press the Flashtools unlock button or use the CMD ?
Also you are talking about this for Twrp right? http://forum.xda-developers.com/showthread.php?t=2225231
angry_machine said:
in this case do I just press the Flashtools unlock button or use the CMD ?
Also you are talking about this for Twrp right? http://forum.xda-developers.com/showthread.php?t=2225231
Click to expand...
Click to collapse
Actually, I was talking about this one: http://forum.xda-developers.com/showthread.php?t=2288118
Includes both TWRP & CWM. And I guess you can unlock the bootloader using the Flashtools button on 4.2.2 stock firmware, but I'm not 100% sure (again, I've opted to stick with my locked bootloader for now)
Tiu Fiu said:
Actually, I was talking about this one: http://forum.xda-developers.com/showthread.php?t=2288118
Includes both TWRP & CWM. And I guess you can unlock the bootloader using the Flashtools button on 4.2.2 stock firmware, but I'm not 100% sure (again, I've opted to stick with my locked bootloader for now)
Click to expand...
Click to collapse
Just one more question before I try, for this I keep on pressing repeating the volume up button just like cwm to enter the boot?
angry_machine said:
Just one more question before I try, for this I keep on pressing repeating the volume up button just like cwm to enter the boot?
Click to expand...
Click to collapse
When booting, after the initial Sony logo, when the notification led shows up in green you have 3 choices:
- press and hold the volume up button until the notification light turns purple to access CWM recovery;
- press and hold the volume down button until the notification light turns purple to access TWRP recovery; or
- don't press anything to boot normally (should be 3 or so seconds until the notification led turns off).
And that's it...
Tiu Fiu said:
When booting, after the initial Sony logo, when the notification led shows up in green you have 3 choices:
- press and hold the volume up button until the notification light turns purple to access CWM recovery;
- press and hold the volume down button until the notification light turns purple to access TWRP recovery; or
- don't press anything to boot normally (should be 3 or so seconds until the notification led turns off).
And that's it...
Click to expand...
Click to collapse
Done everything right. Good thing is my Bootloader has not relocked, Time to go some custom roms I guess.
THANKS A LOT FOR YOUR RESPONSES. loving my way back after such a long time since the early p1i.
Hi Guys
So heres what happened. I rooted my phone and installed the Beats Audio Driver from the Fantastic Audio Installer by motioncoding from the play store. It came to my understanding that the beats driver did not properly install. I opened the app and pressed install and the phone is now in a constant boot loop This is where the phone can boot into the lockscreen but then it automatically restarts and the whole cycle repeats over and over again.
Currently i can only get my phone into flash mode but not fastboot.
-The phone has had its network unlocked. 2 days ago i typed in a network unlock pin into the phone
-The sony flashtool (emma) doesnt work because i have a unlockable bootloader
-I did not install CWM because i only rooted my phone 3 hours ago and i did not know at the time
Does anyone know if flashtool by bin4ry will help me get out of the bootloop in my case
Thanks
itsbighead said:
Hi Guys
So heres what happened. I rooted my phone and installed the Beats Audio Driver from the Fantastic Audio Installer by motioncoding from the play store. It came to my understanding that the beats driver did not properly install. I opened the app and pressed install and the phone is now in a constant boot loop This is where the phone can boot into the lockscreen but then it automatically restarts and the whole cycle repeats over and over again.
Currently i can only get my phone into flash mode but not fastboot.
-The phone has had its network unlocked. 2 days ago i typed in a network unlock pin into the phone
-The sony flashtool (emma) doesnt work because i have a unlockable bootloader
-I did not install CWM because i only rooted my phone 3 hours ago and i did not know at the time
Does anyone know if flashtool by bin4ry will help me get out of the bootloop in my case
Thanks
Click to expand...
Click to collapse
Yes. It will save your phone.
skywalkerdroid said:
Yes. It will save your phone.
Click to expand...
Click to collapse
do i have to wipe my phone or can i just revert the system folder back to original?
itsbighead said:
do i have to wipe my phone or can i just revert the system folder back to original?
Click to expand...
Click to collapse
It's best to wipe everything in this case, wipe dalvik's cache too, make a clean install.
itsbighead said:
Hi Guys
So heres what happened. I rooted my phone and installed the Beats Audio Driver from the Fantastic Audio Installer by motioncoding from the play store. It came to my understanding that the beats driver did not properly install. I opened the app and pressed install and the phone is now in a constant boot loop This is where the phone can boot into the lockscreen but then it automatically restarts and the whole cycle repeats over and over again.
Currently i can only get my phone into flash mode but not fastboot.
-The phone has had its network unlocked. 2 days ago i typed in a network unlock pin into the phone
-The sony flashtool (emma) doesnt work because i have a unlockable bootloader
-I did not install CWM because i only rooted my phone 3 hours ago and i did not know at the time
Does anyone know if flashtool by bin4ry will help me get out of the bootloop in my case
Thanks
Click to expand...
Click to collapse
Just use flashtool with flashmode....
1.Press lightning icon on flashtool and select your rom.....
2.If you want to keep your data uncheck it in the selection menu.
3.Switch off your phone.Plug your phone with volume down key pressed..A green led should light up and flashtool will show your device
connected...
4. Flashing would start....
5.Wait for the rom to be flashed...
6. Device will reboot and it could take upto 2-5 mins approx..
THAT'S IT.....YOU NOW HAVE YOUR PHONE AS IT WAS..:highfive:
AND LET ME KNOW PLS..
HIT THANKS IF I HELPED YOU
A CLICK FOR YOU BUT REP FOR ME.......
XPERIA LT 26I
ROOTED WITH LOCKED BL...
Just to clarify to anyone who reads this thread in the future, you can use flashtool by bin4ry to unbrick your phone
1.Press lightning icon on flashtool and select your rom.....
2.If you want to keep your data uncheck it in the selection menu.
3.Switch off your phone. Plug your phone with volume down key pressed..A green led should light up and flashtool will show your device connected...
4. Flashing would start....
5. The device will reboot and the orange light will light up
6. Unplug the USB Cable and plug in your phone with volume down key pressed. A green led should light up and flashtool will show your device connected...
6.Wait for the rom to be flashed...
7. Device will reboot and it could take upto 2-5 mins approx..
Yeah ? LOL We know that already, your post is off topic, he knows how to flash, as we all do, his question was, well read again his post.Don't come in here and give us lessons on how to flash, smart ass. Are you clarified now?
skywalkerdroid said:
Yeah ? LOL We know that already, your post is off topic, he knows how to flash, as we all do, his question was, well read again his post.Don't come in here and give us lessons on how to flash, smart ass. Are you clarified now?
Click to expand...
Click to collapse
thank you everyone for your help. I got it fixed and i installed cwm recovery before doing anything else
Hey there guys, it's my first time here, so, have a little patience, ok?
So, my XPERIA ZL has been giving me a headache in the past two weeks. All of a sudden it rebooted and entered the loop that i'll show in the video. I'm unable to describe it properly as i've never seen anything like it before.
I've tried everythong i know, but the phone has debug off (and the third parties apps too). Here's the list of what i've tried:
- PCcompanion > updated firmware (it means that fastboot mode is ok and, somehow, PC companion can bypass the debug off limitation)
- Flashtools to install stock rom
- ADB (Does not recognize)
- Odin
- CWM
- Unlock Bootloader
- Root and Kernel from DoomLord
As you can see, none of those actions would work with debug off, and i'm kind of lost now. I'ts full stock.
Can anybody provide some insight?
Thanks in advance!
It is dead
I had this problem too, it is "imei and baseband unknown". Send it to warranty and they will have to replace it (remember to lock the bootloader first)
LimaBEERRE said:
I had this problem too, it is "imei and baseband unknown". Send it to warranty and they will have to replace it (remember to lock the bootloader first)
Click to expand...
Click to collapse
I tought as much...
Thanks anyway!
hi all and happy new year. im having trouble getting my sisters phone to boot up it wont boot past htc one screen. I have tried wipping cache and factory reset in stock recovery it goes to android is upgrading but when it gets to finishing boot it hangs there constantly. I an a sony man so have no experiance with htc. I have read a few threads and am still unsure about the prosess of flashing stock. It is stocked and locked and a uk device any help would be apreciated thanks
gavster26 said:
hi all and happy new year. im having trouble getting my sisters phone to boot up it wont boot past htc one screen. I have tried wipping cache and factory reset in stock recovery it goes to android is upgrading but when it gets to finishing boot it hangs there constantly. I an a sony man so have no experiance with htc. I have read a few threads and am still unsure about the prosess of flashing stock. It is stocked and locked and a uk device any help would be apreciated thanks
Click to expand...
Click to collapse
Post the output of fastboot getvar all after removing serialno and imei
Someone will guide you with those info
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Post the output of fastboot getvar all after removing serialno and imei
Someone will guide you with those info
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Here it is
gavster26 said:
Here it is
Click to expand...
Click to collapse
i didn't see any RUU for your device ( maybe there is but i didn't see it )
You can restore a stock TWRP backup from this thread
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
choose by version main ( 6.13.206.5 ) from post #3 and follow the instruction from OP
Sent from my HTC M8 using XDA Labs
gavster26 said:
Here it is
Click to expand...
Click to collapse
You have to wait a long time for bootup. Even after white HTC screen which can take a few minutes, it will optimise 165 or so apps on MM 6.0, and 265 or so in Lollipop 5.0, depending what you have. Try going away for a half hour while it boots.
Another thing you might try is when it goes on hanging in the 'finishing boot' for a long time so that you think it has completed optimizing of the apps, (wait 20 minutes some apps take minutes to optimize, and there are as I said over 160 at least) , turn it off again by holding the power button for 15-30 seconds or however long it takes to get it to power off. Then restart again it may come on.
*if the power off alone doesnt shut it off, power off+vol down should.
Can the bootloader is locked bro so don't think that would work
kruc Ire said:
You have to wait a long time for bootup. Even after white HTC screen which can take a few minutes, it will optimise 165 or so apps on MM 6.0, and 265 or so in Lollipop 5.0, depending what you have. Try going away for a half hour while it boots.
Another thing you might try is when it goes on hanging in the 'finishing boot' for a long time so that you think it has completed optimizing of the apps, (wait 20 minutes some apps take minutes to optimize, and there are as I said over 160 at least) , turn it off again by holding the power button for 15-30 seconds or however long it takes to get it to power off. Then restart again it may come on.
*if the power off alone doesnt shut it off, power off+vol down should.
Click to expand...
Click to collapse
Tried all that mate. When I hard reboot it (power vol+) it stays stuck at htc one screen left it for 30min or so and still no boot. I tried to logcat while its booting but it won't logcat either. I really need the stock rom but unable to find it I have tried a few zips but got error wrong footer
You need a ruu but unfortunately ruu is not available (afaik).
Worth a try ... flash htc signed firmware fw_6.13.206.5 that you can get from same link above on post #5.
Most important is too see whether the firmware can be successfully installed with no error. If there is error, I'm afraid that will be hardware.
ckpv5 said:
You need a ruu but unfortunately ruu is not available (afaik).
Worth a try ... flash htc signed firmware fw_6.13.206.5 that you can get from same link above on post #5.
Most important is too see whether the firmware can be successfully installed with no error. If there is error, I'm afraid that will be hardware.
Click to expand...
Click to collapse
which link mate. can the boot loader be unlock in this state
Link on post #4 above or directly here : https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Not so sure whether can be unlocked but you can try.
You need to get the unlock code from www.htcdev.com to unlock bootloader.
Good luck and good night .. gotta go now.
Hi All,
First time posting - hopefully I won't make to much of a mess of it.
I'm UK based - and 6 months ago I bought a phone via an Ebay store (1st mistake) that looked like it was based in the UK and their page, and listed the S6 as being "UK version - networked unlocked".
As soon as I had made payment and requested it - it became clear that it was being shipped from Hong Kong - and when it arrived I realised it was a Sprint SM-G920P that had been flashed with some UK firmware.
I worked fine for a few months, but about a month ago it started randomly restarting, often then getting stuck in a boot screen loop when trying to restart. This problem got worse - to the point where it would crash 5 - 10 seconds after boot, and would usually require me restarting it 3 or 4 times to actually get it to that point in the first place.
I followed a guide I found, and flashed it back to the Sprint Firmware version - thinking it might be an issue with the Firmware the seller had installed on it, but this didn't resolve the issue.
I now have a phone that continually gets stuck in boot cycle. When i try and boot into recovery mode, it crashes back to boot. The only mode i can get it to boot into is download mode - but in download mode it informs me that Custom ROM is blocked by FRP Lock.
I can't get Odin to install TWRP - due to FRP lock, and I'm not sure what, if any ROM is worth me trying to install at this point.
Is my phone bricked? I'm also concerned about how much time i want to spend on it - as even if i get it back up and booting - if it is going to have the same - crash to boot problem as before, then it is still basically useless.
Thanks in advance.
I would try pit file. If you have 32gig version, koop has the file posted in his thread. This should clear up bad partition blocks. Then I'd let the battery completely die.
Sent from my SM-G920P using Tapatalk
Ok - so flashing the PIT file and installing a stock ROM has got the phone rebooting - but i'm still getting the random crashes.
My big fear was that this could be a battery / hardware issue - is there anyway to check what is causing the random crashes? Phone rarely stays on more than 30 seconds.
stevepaul1982 said:
Ok - so flashing the PIT file and installing a stock ROM has got the phone rebooting - but i'm still getting the random crashes.
My big fear was that this could be a battery / hardware issue - is there anyway to check what is causing the random crashes? Phone rarely stays on more than 30 seconds.
Click to expand...
Click to collapse
Does the screen wig out before it reboots? Like does it just go blank or does it go through the power down animation as if you powered off the device?
Sent from my SM-G920P using Tapatalk
elesbb said:
Does the screen wig out before it reboots? Like does it just go blank or does it go through the power down animation as if you powered off the device?
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
It just goes black - sometimes there is a very brief flash like animation.
For reference - when i've had something playing - or been on a call when it happens it gives a short harsh buzz as well.
stevepaul1982 said:
It just goes black - sometimes there is a very brief flash like animation.
For reference - when i've had something playing - or been on a call when it happens it gives a short harsh buzz as well.
Click to expand...
Click to collapse
post your /proc/last_kmsg file. That should have the culprits listed in terms of panics.
Also, look at the tombstones directory -- that will have the errors as well.