[Q] Inescapable Bootloop So Far - Xperia Arc Q&A, Help & Troubleshooting

I tried to flash cm10.1 from 9.1 stable but nothing would boot after. came to believe that they stopped anzu development at 10.0 so then wanted to flash for just 10.0. but i cannot escape the bootloader and thus cannot load the zip to my sdcard. i have tried flashing lt15i v. 4.0.2.A.042 using flashtool like 10 or more times it says it completes successfully but everytime, bootloop. ive tried the remove battery for 30 seconds and restart computer. still no luck. so pretty stuck now. can anyone kindly point me in the right direction?
ps im right about the 10.1 not being available right? is this what has caused this problem? also forgot to mention i fastboot the 10.0 img as well in the hope this might work and i also fastbooted recoveryimg afterwards.
edit: tried seus it just says i have latest update. pc companion wont connect because phone just keeps looping.
edit 2: i loaded the doomkernel which has allowed me to access cwm i performed a restore from one i had but it just loaded to a black lit screen. at a loss for where to go from here.

cheetaa said:
ps im right about the 10.1 not being available right? is this what has caused this problem? also forgot to mention i fastboot the 10.0 img as well in the hope this might work and i also fastbooted recoveryimg afterwards.
Click to expand...
Click to collapse
Our device does not have a recovery partition! Recovery is included in the boot.img. And where did you get that from?

soumya_digi said:
Our device does not have a recovery partition! Recovery is included in the boot.img. And where did you get that from?
Click to expand...
Click to collapse
yeah that was actually my next course of action. to get the boot.img for 9.1 and flash that back on, see if that will get things working again. i got the cm from freexperiaproject. let me know if you have any further ideas for me or if you think this will work now when i give it a try. i will post back if i am successful or not.
thanks
edit: correction, i must have got 9.1 from cyanogen.org to be precise.
ps: once and if i get this back in working order, would you mind recommending which build i should go with for best solid usage. ie should i go with the nightly (probably not i would imagine) or like the 7.1.0 stable build or what have you. reason i was trying to go to 10.1 from the stable 9.1 was because of the wifi being dropped after a certain amount of idle time. i figured this had something to do with the build. anyways, let me know i would appreciate it.
edit 2: haha phone is back working, shouldve thought of that solution before, i guess im still learning the ins and out of these systems. do hope to hear back on what build you would suggest. thanks again

Tred to flash the kernel included?
Sent from my LT15i using xda premium

TheHaso said:
Tred to flash the kernel included?
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
yeah thats exactly what i did everythings working again. dont know why i didnt think of it earlier lol, been sick these past days brain isnt working fast enough.thanks for the help anyways man.

Related

[kernel] Root Stock Kernel

Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
Froyo only
Strock "root" Kernel -
boot.img only
http://dl.dropbox.com/u/8699733/inc2/boot.img
CWR Flashable with wifi module
http://dl.dropbox.com/u/8699733/inc2/inc2_stock_kernel_.zip
NOTE I will not be maintaining this thread
Amazingly fast work... part of me wonders how fast MIUI can get organized for this... that would be worth it all.
drtchocky said:
Amazingly fast work... part of me wonders how fast MIUI can get organized for this... that would be worth it all.
Click to expand...
Click to collapse
its 3 small changes, took 2 minutes max
Could u give a short intros for it?
Relay said:
Could u give a short intros for it?
Click to expand...
Click to collapse
its a stock kernel with presistant adb, and ""root"" adb
jcase said:
its a stock kernel with presistant adb, and ""root"" adb
Click to expand...
Click to collapse
LOL
niiiice
My kernel is ver 2.6.35.10-g20416a6, is it older than yours?
jcase said:
Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
I don't wanna sound like a noob here, I know how to use CWR, but in reference to fastboot, thats not the fastboot that makes the phone boot faster. But fastboot used in adb for back ups right?? Not asking for a description i just went through the entire life of my dinc 1 and thought I knew everything and never heard of fastboot. Wanna make sure I understand and read up on the right thing...
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
scumfromohio said:
jcase said:
Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
I don't wanna sound like a noob here, I know how to use CWR, but in reference to fastboot, thats not the fastboot that makes the phone boot faster. But fastboot used in adb for back ups right?? Not asking for a description i just went through the entire life of my dinc 1 and thought I knew everything and never heard of fastboot. Wanna make sure I understand and read up on the right thing...
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
fastboot as in fastboot commands.
Click to expand...
Click to collapse
Relay said:
My kernel is ver 2.6.35.10-g20416a6, is it older than yours?
Click to expand...
Click to collapse
Mine is 2.6.35.9
Relay said:
My kernel is ver 2.6.35.10-g20416a6, is it older than yours?
Click to expand...
Click to collapse
seems newever, and your software is much different than ours, is that an inc2 or S, or is it running on GSM or something?
HELP!!
I tried to flash the overclocked kernel and now Im stuck in a bootloop and can't load recovery or be recognized in fastboot usb. It seems like I may have bricked my phone any suggestions. PLEASE HELP
update - I fixed it lol almost thought my dinc 2 was a brick
I may be in the same situation and would like to know how you solved your problem.
I rooted successfully and was running the Gingersense rom with the stock kernel. I wanted to OC a kernel so I downloaded one that I think was intended to run with MIUI. I made a backup so I figured if the kernel didn't work I could always go back.
After installing the new kernel I went into a boot loop. I pulled the battery, got into recovery and tried to restore a backup, but now I freeze on the HTC screen. I've tried three different backups and none of them work -- all freeze on the HTC screen.
I am becoming desperate. Any help would be greatly appreciated.
Have you tried wiping everything (including /system under "mounts and storage") before restoring the backup? Or tried flashing a different rom? Probably happened because the kernels for AOSP roms and sense roms aren't interchangeable. I would think that restoring a backup would rewrite the boot partition though, which should fix it..
I wiped everything (did data wipe/factory resets as well as wiping everything individually, several times) and could never get any of my backups to work.
I finally copied CM7.1 beta onto the SD card and flashed that (after first having to scrounge to find a card reader and computer that would read an SDHC card) and that worked.
I tried restoring one of my previous backups over CM7.1 (with and without wiping) and went back to freezing on the HTC screen again on each one of them. Don't understand that, since everything was working fine when those backups were made.
Anyway, now I'm using CM7.1 and have a working phone again.
Thanks for your work on this. Much appreciated for helping to realize my dream of a fully-rooted Inc2.
/bow
Ihave the same issues with backup not restoring and getting the white screen. Might need a new SD card.
Sent from my ADR6350 using XDA App
jcase said:
Learn to use fastboot or clockwork recovery before reading further. This thread will not show you how to flash. Verified working.
Froyo only
Strock "root" Kernel -
boot.img only
http://dl.dropbox.com/u/8699733/inc2/boot.img
CWR Flashable with wifi module
http://dl.dropbox.com/u/8699733/inc2/inc2_stock_kernel_.zip
NOTE I will not be maintaining this thread
Click to expand...
Click to collapse
links dont work
dgm_mixtoon said:
links dont work
Click to expand...
Click to collapse
links 4years old

No Hboot!

tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
sumairmh said:
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
Click to expand...
Click to collapse
are you pressing any buttons to get into recovery? or is it just bootlooping into it? you tried flashing an ruu? on second thought to flash an ruu, dont you need to have a locked, or relocked bootloader? and that requires fastboot, which is in hboot. damn. maybe you can send it off to htc?
sumairmh said:
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
Click to expand...
Click to collapse
Try Flashing a Sense rom with APM, AKA MyOneV RC 3.0, and reboot into bootloader, and try Flashing an RUU
sumairmh said:
tried to flash the new paranoid android rom... went to bootloop... now trying to get back using my nandroid backup... and my Hboot has vanished, phone going straight to recovery... Help anyone???
Click to expand...
Click to collapse
First of all, the rom is fine. It boots fine, it installs fine. The partitions are fine (it has the same updater-script like CM9), so I VERY MUCH DOUBT that the rom deleted your Hboot or anything... Try downloading One V all in one tool and from there select reboot phone in bootloader. see if that helps.
Thanks,
1ceb0x
hey guys... thanks for all the help, i din say anything about the new rom doing this... but well i flashed rc3.0 and restored data, that fixed it... and sounding incredibly stupid it seems my battery was low... anyway its fixed now... i'm gonna try flashing paranoid once more when my battery is fully charged...:good:
sumairmh said:
hey guys... thanks for all the help, i din say anything about the new rom doing this... but well i flashed rc3.0 and restored data, that fixed it... and sounding incredibly stupid it seems my battery was low... anyway its fixed now... i'm gonna try flashing paranoid once more when my battery is fully charged...:good:
Click to expand...
Click to collapse
Glad it worked out for you!
1ceb0x said:
Glad it worked out for you!
Click to expand...
Click to collapse
hey i flashed yo rom, everything works fine (well whatever is working), except everytime i get a call android phone FC's, is this a known bug?
sumairmh said:
hey i flashed yo rom, everything works fine (well whatever is working), except everytime i get a call android phone FC's, is this a known bug?
Click to expand...
Click to collapse
Try to lower the DPI for the Phone.apk app. You can do this from Paranoid Android settings!
1ceb0x said:
Try to lower the DPI for the Phone.apk app. You can do this from Paranoid Android settings!
Click to expand...
Click to collapse
so i take it that its workin for u?
sumairmh said:
so i take it that its workin for u?
Click to expand...
Click to collapse
it was not tested completely. will need to do it so today! but try that fix. in general the FC's are from the DPI lowered...
looks like some prob with SU, it denies root access, tried updating it from play also tried changing default to prompt and allow, still doesn help... i loved the rom but if it doesnt let me make or take calls... well i guess i'll have to wait for the next update...
sumairmh said:
looks like some prob with SU, it denies root access, tried updating it from play also tried changing default to prompt and allow, still doesn help... i loved the rom but if it doesnt let me make or take calls... well i guess i'll have to wait for the next update...
Click to expand...
Click to collapse
easy fix for you....flash this in CWM http://download.chainfire.eu/204/SuperSU/CWM-SuperSU-v0.94.zip
it's a CM9 bug that i thought i had fixed....herp derp
As i've said. Didn't had enough time to test it but I'm glad someone is giving me feedback. I'll be working on it in the next days.

HurtSky' Kernel V3.3 problem .. plz help

hi ... i just downloaded the HurtSky' Kernel V3.3 on my galaxy wonder and did what exactly was said in this topic : http://forum.xda-developers.com/show....php?t=2204669
but my phone now refuse to work at all , after the samsung screen with cyanogenmod logo the device don`t show anything and keeps restarting ... i registered in the site to post about my problem in the topic above ... but because i`m new so i can not post ... please help me i don`t know what to do
Hum, try to flash the older kernel v3.2. You are using cm9 right?
ilusi0n_ said:
Hum, try to flash the older kernel v3.2. You are using cm9 right?
Click to expand...
Click to collapse
no i don`t ... should i ???
and now i formated everything .. but still the same and i can`t access to the phone
Your link doesn't work. I assume you were using this kernel right? http://forum.xda-developers.com/showthread.php?t=2204669
That kernel is just for cm9. There are different kernels for each version.
ilusi0n_ said:
Your link doesn't work. I assume you were using this kernel right? http://forum.xda-developers.com/showthread.php?t=2204669
That kernel is just for cm9. There are different kernels for each version.
Click to expand...
Click to collapse
this is the link : http://forum.xda-developers.com/showthread.php?t=2204669
sorry i don`t know much about these things ... so plz if u can tell me what to do step by step cause im really confused
You still didn't tell what version of cm you were using. As far as I know a wrong kernel flash can brick the phone. Though that stuff is beyond my knowledge so you should wait untill someone more qualified could answer you. I'm not sure if a simple flash rom would solve the problem.
ilusi0n_ said:
You still didn't tell what version of cm you were using. As far as I know a wrong kernel flash can brick the phone. Though that stuff is beyond my knowledge so you should wait untill someone more qualified could answer you. I'm not sure if a simple flash rom would solve the problem.
Click to expand...
Click to collapse
i was not using cm at all ... but i downloaded the CM9 rc9 .. and my phone start working again ... thnx for ur help
ah, so that was the problem. Glad everything worked out : D
Yes, that should fix. Bootloop occurs when our system crash. So, it cant be loaded. It is also called a softbrick. But it is not really dangerous, as we can simply flash back our rom back, as long it is save on your sdcard. Also you can restore nandroid backup. Nandroid backup is a backup for our system if our system crash. It can crash, if the rom we download did not aborted or something, our system should not be crash. That's why after every download, we need to verify the md5sum.
Sent from my CM10.1 Wonder using xda premium

[Q] Trouble Installing Bane of Speed V6

I have an R00x from Verizon (CDMA). I bought this phone from a co-worker just to use it for emulators.
Learned many things while rooting this Xperia Play. I cant unlock the bootloader with out paying so i have to stick to GB roms from what I understand.
Rooted by downgrading to 2.3.3 with Flashtool and then using SuperOneClick. Tried using X-parts to install CWM but it would never let me get into recovery so i used ClockWorkMod Recovery 5.0.2.6 Easy installation and succesfully installed CWM.
Copied over Bane of Speed, rebooted to recovery and wiped Data And Factory Reset.
The next step said to wipe /system so i did (I remembered that since my bootloader is locked the recovery is installed in the system. This worried me)
Flashed the zip
Wiped cache and davlik and booted
Couldnt get past the Sony Ericsson and i waited 10mins or so, pulled the battery and couldnt get into recovery because I think it got wiped in /system
Had a minor heart attack thinking that i bricked it.
Was able to reinstall 2.3.3 with Flashtool, and re rooted and reinstalled recovery.
Are there special install instructions for a locked bootloader? Do you see a step where i went wrong?
Suggest another rom for a locked CDMA R00x? I dont need a super fancy rom, just want to play emulators and play store games
Thanks for reading this novel, any help would be appreciated.
This Rom wony work the signal for CDMA only GSM but it will work for locked and unlocked, IT must have been a download error, redownload and flash then report back!
HOPE IT HELPED!!!
Sent from my R800i using xda app-developers app
sometitu Why
Pizza_Dox said:
This Rom wony work the signal for CDMA only GSM but it will work for locked and unlocked, IT must have been a download error, redownload and flash then report back!
HOPE IT HELPED!!!
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Redownloaded and followed the steps again, and i still got stuck at Sony Ericsson. =(
xDman11x said:
Redownloaded and followed the steps again, and i still got stuck at Sony Ericsson. =(
Click to expand...
Click to collapse
Ok, Now i dont know whats up as im unlocked and my tester Joeyxc tested it on his locked and it worked fine,
So i really dont know whats going on...
Its probably the kernel you have
Also why dont u unlock Via Testpoint and flash lupus or Dooms
Im sorry for bad support but if i had more experience in Locked BootLoaders then i would be able to fix it probably!
Any one else got any ideas?, please help him!
progress
Pizza_Dox said:
Ok, Now i dont know whats up as im unlocked and my tester Joeyxc tested it on his locked and it worked fine,
So i really dont know whats going on...
Its probably the kernel you have
Also why dont u unlock Via Testpoint and flash lupus or Dooms
Im sorry for bad support but if i had more experience in Locked BootLoaders then i would be able to fix it probably!
Any one else got any ideas?, please help him!
Click to expand...
Click to collapse
Made progress!
I believe i successfully unlocked my bootloader by using Sonys MEID unlock. Flashed Lupus! and got into the lupus recovery. Proceeded to attempt to install your rom. follow same steps and i go to reboot system. When it reboots it automatically goes straight back to Lupus though.
xDman11x said:
Made progress!
I believe i successfully unlocked my bootloader by using Sonys MEID unlock. Flashed Lupus! and got into the lupus recovery. Proceeded to attempt to install your rom. follow same steps and i go to reboot system. When it reboots it automatically goes straight back to Lupus though.
Click to expand...
Click to collapse
ok ive had that probelm be4 just format all paritions and if that dosent work, GOOGLE It, lol, sorry , im not at a pc
sent from my LOIC from mars
wipe
Pizza_Dox said:
ok ive had that probelm be4 just format all paritions and if that dosent work, GOOGLE It, lol, sorry , im not at a pc
sent from my LOIC from mars
Click to expand...
Click to collapse
So format /sd-ext ? and then mount it in usb storage and move the BOSv6.zip back on and try again?
thanks for all the help
xDman11x said:
-snip-
Click to expand...
Click to collapse
Last time I wiped cache and dalvik after flashing the zip, all hell broke loose on my phone. Try wiping your cache and dalvik, before flashing the zip, afterwards, just reboot, don't wipe anything.
Toasty Clown said:
Last time I wiped cache and dalvik after flashing the zip, all hell broke loose on my phone. Try wiping your cache and dalvik, before flashing the zip, afterwards, just reboot, don't wipe anything.
Click to expand...
Click to collapse
I think i got it. after reading into it more i was just using the command (fastboot boot lupus.img) when i should have been using (fastboot flash boot Lupus.img)
Finally got Bane of Speed Installed!
Last couple of questions,
1. Joystiqs dont work in GB?
2. Can I use any GSM rom? (i dont care if the radios work, this is just an offline games phone for me(CDMA verizon))
Thank you very much for all your help guys! Sorry I derped and thought i had flashed the boot image when i was only temp running it
Lol, it's ok, first tone flashing is always hard!
1.) joysticks should work!
2.) Yes u can use any GSM Rom - I think, but their will be no service
Sent from my R800i using xda app-developers app
Pizza_Dox said:
Lol, it's ok, first tone flashing is always hard!
1.) joysticks should work!
2.) Yes u can use any GSM Rom - I think, but their will be no service
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Not all GSM roms work. Moat will leave your homescreen blank and unusable. In addition the only fix is to install xdarkmarios cdma patch/fix. Sorry can't remember the name of it off hand. It essentially fixes the blank homescreen so you should be able to flash any GSM rom. That's what I used on my old Verizon xperia play before switching to the GSM model.
Sent from my R800at using xda premium

[Q] Failed to flash DoomKernelV14 on R800i

For some reason DoomKernelV14 refuses to boot on my phone.
From Stock GB (unlocked bootloader), I tried flashing it with fastboot by using
Code:
fastboot flash boot boot.img
(After re-naming the DoomKernelV14.img file to boot.img of course and putting it in my fastboot folder).
After that, fastboot reported that flashing was successful, so I went to turn my phone on so I could boot into recovery so I could install Dixperia 2, and all I got was a quick vibrate and a black screen of nothing. Having done that I did a battery pull so I could put the phone back into fastboot mode, and use the commands:
Code:
fastboot erase userdata
fastboot erase system
After this I could put the phone back into Flash Mode (which I was unable to do after attempting to flash DoomKernel. From here I flashed the Stock ROM so I could turn my phone back on again.
After this I tried the above again, using the erase userdata/system commands above before I flashed DoomKernel and had the same problem.
Could anyone offer any insight as to what I might be doing wrong?
My phone is using a -64 baseband, and a .62 build number.
BUMP
Have you tried redownload the kernel? Maybe your download is corrupted.
And after your phone vibrated and stayed dark, have you unpluged your cable and took out your batterie a few seconds and then tried to start it again? And you shoud always erase userdata, dalvik and perform a factory reset if you flash a new rom or use a new kernel.
EP35DS4 said:
Have you tried redownload the kernel? Maybe your download is corrupted.
And after your phone vibrated and stayed dark, have you unpluged your cable and took out your batterie a few seconds and then tried to start it again? And you shoud always erase userdata, dalvik and perform a factory reset if you flash a new rom or use a new kernel.
Click to expand...
Click to collapse
Yes done all that, to no avail Each time I have done this I have been going from Stock GB (unlocked bootloader). I also tried re-downloading the Kernel and that did not work. I have installed Cyanogenmod 7.2 in the past with no problems (before going back to Stock GB) so how come DoomKernel is causing no end of problems?
xenobia144 said:
Yes done all that, to no avail Each time I have done this I have been going from Stock GB (unlocked bootloader). I also tried re-downloading the Kernel and that did not work. I have installed Cyanogenmod 7.2 in the past with no problems (before going back to Stock GB) so how come DoomKernel is causing no end of problems?
Click to expand...
Click to collapse
It seems like many users have problems with DoomKernel v14 (just look at the last 10 questions). Maybe you could just try another kernel, like lupus. is this the first time you try dommkernel v14 or worked it in the past for you?
---------- Post added at 12:28 PM ---------- Previous post was at 12:22 PM ----------
And maybe this could help you:
psxpetey said:
The firat time you start doomkernel it will seem like your phone is bricked as soon as you press power atart pressing the back button and a screen will come up that will allow you to install a Rom off the sd card. I thought mune was bricked firat time. When doom starts the blue led starts its not flash its just what it does.
1. Turn on the phone
2. Press back button until Rom flashing screen pops up
3. Install Rom from sd
4. Boot rom
Click to expand...
Click to collapse
It's from one of those theards i mentioned [Q]Play bricked?
The only people who have trouble with kernels seem to not read the directions before they flash it they flash it and think omg im bricked it wont turn on . If the blue led shows doom is working you just need a Rom on you sd card and start pressing the back button as soon as you see the blue led and an installation screen will pop up. This is so you dont have to see the install screen everytime you boot. Before you install a Rom make sure its compatible with doom
psxpetey said:
The only people who have trouble with kernels seem to not read the directions before they flash it they flash it and think omg im bricked it wont turn on . If the blue led shows doom is working you just need a Rom on you sd card and start pressing the back button as soon as you see the blue led and an installation screen will pop up. This is so you dont have to see the install screen everytime you boot. Before you install a Rom make sure its compatible with doom
Click to expand...
Click to collapse
Except there was no blue light on, nor any light at all for that matter. Also, since I was not able to get as far as even installing a ROM, I should also note that I had done my research, and was going to be installing Dixperia 2 (and the author of that ROM says to use DoomKernelV14). I was going from Stock GB.
I ought to note that I never said it was bricked, as I have been able to get back to Stock GB, as noted in the original post.
Before you go walking into posts implying people didn't read the instructions you should probably read the original post.
Now does anyone have anything helpful to add?
psxpetey said:
The only people who have trouble with kernels seem to not read the directions before they flash it they flash it and think omg im bricked it wont turn on . If the blue led shows doom is working you just need a Rom on you sd card and start pressing the back button as soon as you see the blue led and an installation screen will pop up. This is so you dont have to see the install screen everytime you boot. Before you install a Rom make sure its compatible with doom
Click to expand...
Click to collapse
well just keep trying then there shouldnt be an issue. You wont break if from trying
Sent from my LT28i using xda app-developers app
psxpetey said:
well just keep trying then there shouldnt be an issue. You wont break if from trying
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
After ten attempts it still did not work, hence my original question.
Post the logfile from flashtool and the logfile for the install from your phone would make figuring this out easier.
Sent from my LT28i using xda app-developers app
psxpetey said:
Post the logfile from flashtool and the logfile for the install from your phone would make figuring this out easier.
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
How does one go about obtaining these?
Flashtool is a simple copy paste when you do the install. Im sure you can find the log in flashtools files. The logfile from the play should be in /cache. And is a. Log file. Maybe called lastinstall.log or something similiar.
I havent had a play for a while so dont quote me on that lol but if its not there im sure someone.in the forum knows where it is.
Sent from my LT28i using xda app-developers app
Are you on Windows 8 by any chance?
Sent from my LT28i using xda app-developers app
im having the same damn problem:crying:
Anyway if your on Windows 8 flashtool wont work properly.
Sent from my LT28i using xda app-developers app

Categories

Resources