[Q] How can i escape the BOOTLOOP? - Xperia Play General

..Without using Recovery mode? i did do a backup,but its pretty far away and i SERIOUSLY dont want to start again with the games i played -.-
How the bootloop caused : i used the Zeppelin SuperchargerV9 and i think i got the bootloop thanx to the KICKASSKERNELTEAK98'
so how can i escape it?its somewhere in INIT.D all i think i have to do is delete the script.
using the computer what can i do?if i do some reflashing like reflash the DooMK3 ,OR reflash my Firmware,will it solve it?

Cat_On_Droid said:
..Without using Recovery mode? i did do a backup,but its pretty far away and i SERIOUSLY dont want to start again with the games i played -.-
How the bootloop caused : i used the Zeppelin SuperchargerV9 and i think i got the bootloop thanx to the KICKASSKERNELTEAK98'
so how can i escape it?its somewhere in INIT.D all i think i have to do is delete the script.
using the computer what can i do?if i do some reflashing like reflash the DooMK3 ,OR reflash my Firmware,will it solve it?
Click to expand...
Click to collapse
You have 2 options. If you flash stock kernel.sin from fastboot. Thats has no init.d support so script wont be activated at boot. or if you can access adb from recovery. Just use the commands:
adb shell
rm /system/etc/ini.d/"name of script"
That will delete the script from your device. Or you could just try wiping the dalvik cache from recovery

AndroHero said:
You have 2 options. If you flash stock kernel.sin from fastboot. Thats has no init.d support so script wont be activated at boot. or if you can access adb from recovery. Just use the commands:
adb shell
rm /system/etc/ini.d/"name of script"
That will delete the script from your device. Or you could just try wiping the dalvik cache from recovery
Click to expand...
Click to collapse
what!! that simple?wipe dalvik and Poof,the bad script gone?
will that screw up the dalvik2CACHE Hack MOD?

Cat_On_Droid said:
what!! that simple?wipe dalvik and Poof,the bad script gone?
will that screw up the dalvik2CACHE Hack MOD?
Click to expand...
Click to collapse
No it wont remove the script, but the majority of bootloops are to do with issues with the dalvik cache

AndroHero said:
No it wont remove the script, but the majority of bootloops are to do with issues with the dalvik cache
Click to expand...
Click to collapse
yes it didnt work.
Okay,gonna try the Kernel.Sin
I thought it wouldnt work cuz i didnt know how could it possibly remove it
Ty Her0!

Cat_On_Droid said:
yes it didnt work.
Okay,gonna try the Kernel.Sin
I thought it wouldnt work cuz i didnt know how could it possibly remove it
Ty Her0!
Click to expand...
Click to collapse
flashing stock kernel.sin will defo work then delete scrip from init.d, and flash DL's kernel again

egh.i messed up badly..
i tried to RE-DO the SUpercharger script and that was a bad idea..
now i cant get the DALVIKHACKCACHEMOD to work for me i tried deleting it,re installing through recovery but it BOOTLOOPS with DK3...
Any suggestions? im kind of tired of re flashing,rebooting,and still getting the BooTLoOP

Cat_On_Droid said:
egh.i messed up badly..
i tried to RE-DO the SUpercharger script and that was a bad idea..
now i cant get the DALVIKHACKCACHEMOD to work for me i tried deleting it,re installing through recovery but it BOOTLOOPS with DK3...
Any suggestions? im kind of tired of re flashing,rebooting,and still getting the BooTLoOP
Click to expand...
Click to collapse
did you reflash doomlords kernel?

AndroHero said:
did you reflash doomlords kernel?
Click to expand...
Click to collapse
You mean twice flashing the DoomKernel? I didnt,but i can...

Cat_On_Droid said:
You mean twice flashing the DoomKernel? I didnt,but i can...
Click to expand...
Click to collapse
No just once. Hmmm try manually pushing the script to init.d folder
fire up adb. And type in
adb remount
adb push *nameofscript" /system/etc/init.d
adb shell
chmod 777 /system/etc/init.d/*nameofscript*
reboot

AndroHero said:
No just once. Hmmm try manually pushing the script to init.d folder
fire up adb. And type in
adb remount
adb push *nameofscript" /system/etc/init.d
adb shell
chmod 777 /system/etc/init.d/*nameofscript*
reboot
Click to expand...
Click to collapse
i dont know whats ADB... is it the SDK manager? Im gonna look it up..
eDIT: Even if i do push out the Dalvik HackMod,i still NEED it..so im gonna have to retry it then -.- ? im gonna try something else differenet...

Cat_On_Droid said:
i dont know whats ADB... is it the SDK manager? Im gonna look it up..
eDIT: Even if i do push out the Dalvik HackMod,i still NEED it..so im gonna have to retry it then -.- ? im gonna try something else differenet...
Click to expand...
Click to collapse
ADB stands for android debug bridge. It's part of the Android SDK. If you use android. ADB is really something you should learn. Here is a great start
http://dbhatesblogs.blogspot.com/2009/07/adb-for-dummies.html

Ah thats what i need

i did a factory reset data
after flashing from STOCK to DOOM3 i STILL in a BOOTLOOP!!
Why is this happening!?
If i did a Hard Reset i THINK the DalvikMOd,Supercharge should be wiped right?
STILL cant get to use...and i dont think ADB will help much now ..
edit: after hours of skull cracking,almost a tear in my eye,i got it working.
NaND solves everything...always

Related

Having trouble wiping

I managed to wipe data/factory reset but on dalvik-cache and SD: ext partition, it says theres an error and I have to run both of them via adb. This is my first time actually wiping and the only video I could find was for a mytouch3g. Any help would be grateful.
Does anyone know? Im trying to get his wiped and install a custom ROM asap because Ive already had my phone out of commission for a few hours now.
a bidet may help.
actually I read on these forums that even though you get the error on dalvik that it wiped successfully completed. don't know about the other.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
flash a new recovery image
works everytime
PawkChop said:
Having trouble wiping
Click to expand...
Click to collapse
Sounds like a personal problem.
Just kidding, try flashing another one like was already suggested.
Im currently on version 1.5.2 and I got it from a guide I followed earlier to root my phone. I dont know where I'd get another one from though
The guide for rooting in the sticky is the exact one I followed and that brings the version I have. Unless Im not looking in the right place. Im sorry that Im a total noob at this, just trying to finally use some custom stuff on my phone.
http://rapidshare.com/files/360288584/recovery-RA-heroc-v1.6.2.img
Thank you very much. Now this is where its get even noobier. Where exactly do I put the file. Ive never flashed a ROM or a recovery image unless that guide involved it so Im kinda at a loss here.
I sent you a PM
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
PawkChop said:
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
Click to expand...
Click to collapse
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
HeroMeng said:
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
Click to expand...
Click to collapse
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
PawkChop said:
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
Click to expand...
Click to collapse
In ADB. If it shows a $ sign after you type adb shell, then type su. That might be your problem.

[Q] HELP I have PROBLEM WITH MYTOUCH 4G rooted with virtuous fusion ROM

Hi i have a MyTouch 4G rooted with Virtuous Fusion ROM. Everything was working until when I tried to install Miui Music Player on it. I did adb push but after doing it when i unplugged the phone from my computer several Force Close came up then i rebooted my phone then the MYTOUCH Tmobile logo start up screen came then the HTC logo came then my phone will shut down. I tried to start my phone again the same thing happen. I did Hboot and tried recovery from there but it didnt work. I tried Factory Reset but it failed. I go to clockwork recovery mode if i do backup and restore or factory reset nothing happens. Does it mean my phone is gone? Is there anything i can do to fix it? Please anybody help
Try going into recovery again and just reflash fusion again.
coupetastic-droid said:
Try going into recovery again and just reflash fusion again.
Click to expand...
Click to collapse
I tried doing that i booted to clockwork recovery then on the menu any button i click like install from zip, backup and restore and so on. After i click it nothing happens its like clockwork recovery is not working. Does this mean my Phone is BRICK. I cannot fix it anymore
pching999 said:
I tried doing that i booted to clockwork recovery then on the menu any button i click like install from zip, backup and restore and so on. After i click it nothing happens its like clockwork recovery is not working. Does this mean my Phone is BRICK. I cannot fix it anymore
Click to expand...
Click to collapse
Im kind of a noob but did you reflashing cwm via adb? Do some research first though.
Also I think there is a trick to flash an older cwm via adb and then flash an older romm that needs cwm 2.xxx but I could be wrong
tjlawson09 said:
Im kind of a noob but did you reflashing cwm via adb? Do some research first though.
Also I think there is a trick to flash an older cwm via adb and then flash an older romm that needs cwm 2.xxx but I could be wrong
Click to expand...
Click to collapse
NO how do i reflash Clock work MOD through adb? Can you give me the steps to do it. I could try if it will work
pching999 said:
NO how do i reflash Clock work MOD through adb? Can you give me the steps to do it. I could try if it will work
Click to expand...
Click to collapse
Download a new copy of CWM from here. Rename the file "recovery.img" and put it in the root of your SD card. Then start ADB and enter:
Code:
adb flash_image recovery /sdcard/recovery.img
TeeJay3800 said:
Download a new copy of CWM from here. Rename the file "recovery.img" and put it in the root of your SD card. Then start ADB and enter:
Code:
adb flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
when i use the track pad it worked but what should i do next do i have to do a back up and restore or reflash the custom rom
pching999 said:
when i use the track pad it worked but what should i do next do i have to do a back up and restore or reflash the custom rom
Click to expand...
Click to collapse
See my post in your other thread. It sounds like your recovery is fine, so all you need to do is wipe and re-flash.
TeeJay3800 said:
See my post in your other thread. It sounds like your recovery is fine, so all you need to do is wipe and re-flash.
Click to expand...
Click to collapse
Hi im having problem with data connection 3G/4G (H) before i was getting H most of the time but now its 3G most of the time. Can you help me how to fix this. Also do you know what version of Miui Music Player is best for Mytouch 4G running on Virtuous Fusion ROM. I like the one with graphic equalizer when playing songs. Can you suggest something and how to install it
Thanks

Status 7

I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance
I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.
z1gackly said:
I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.
Click to expand...
Click to collapse
what ive been doing is not making any backups (nothing important to save) and just using nexus toolkit to flash back stock and starting over and trying new way every time
still nothing though after about the 20th time
No idea then sorry. Stick with rooted stock?
z1gackly said:
No idea then sorry. Stick with rooted stock?
Click to expand...
Click to collapse
i think I might have to, ive never had any issues with custom roms (to speak of)
oh well, at least im happy with stock, i just love miui.
anyone else have answers please chip in, i give thanks!
harecurtis said:
I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance
Click to expand...
Click to collapse
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
give me 5 minutes, while i try your method.
harecurtis said:
give me 5 minutes, while i try your method.
Click to expand...
Click to collapse
joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
its a no go
anyone else wanna help me?
ive tried almost everything:/
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"
harecurtis said:
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"
Click to expand...
Click to collapse
If you're going that route.. you might as well just use fastboot to reflash recovery instead of the app.
Download the same image i linked to earily. While in the bootloader issue this command
Code:
fastboot flash recovery name-of-recovery.img
Make sure you have the Command Prompt in the same directory as the recovery image.
So say its in your downloads folder on your computer open CMD and cd to that directory.
Code:
cd C:\Users\Name\Downloads
Or just open yoru downloads folder and Shift + Right click and select "open command window here" then issue the fastboot command.
ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
didnt work(
harecurtis said:
didnt work(
Click to expand...
Click to collapse
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??
ÜBER™ said:
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??
Click to expand...
Click to collapse
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3
harecurtis said:
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3
Click to expand...
Click to collapse
Stop... dont use that.. -_-. Do it manually..
ÜBER™ said:
Stop... dont use that.. -_-. Do it manually..
Click to expand...
Click to collapse
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!
harecurtis said:
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!
Click to expand...
Click to collapse
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.
ÜBER™ said:
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.
Click to expand...
Click to collapse
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?
harecurtis said:
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?
Click to expand...
Click to collapse
Keep it unlocked.... otherwise you'll have to re unlock it...

booting to recovery

hi,getting trouble booting to recovery,it worked first time to install PA but now im trying to install franco kernel but im just getting blank screen,ive tried teamwin now im trying on rom manager with no luck,any ideas
Terminal emulator - reboot recovery.
Adb - adb reboot recovery
You may need to install your recovery again. Sounds like something is borked.
ROM manager doesnt use TWRP.
TWRP uses goo manager.
zephiK said:
ROM manager doesnt use TWRP.
TWRP uses goo manager.
Click to expand...
Click to collapse
Absolutely. I think he is just trying to boot to recovery, though.
estallings15 said:
Terminal emulator - reboot recovery.
Adb - adb reboot recovery
You may need to install your recovery again. Sounds like something is borked.
Click to expand...
Click to collapse
cheers,i will go back to toolkit
estallings15 said:
Absolutely. I think he is just trying to boot to recovery, though.
Click to expand...
Click to collapse
well I'm not sure if ROM manager can boot to recovery (i know its the same command, but it may respond weirdly as ROM Manager is CWR) and generally speaking. you shouldnt be using ROM Manager with TWRP, it can lead to bad things. Not saying that it would, but I'd proceed with caution.
tonybhoy said:
cheers,i will go back to toolkit
Click to expand...
Click to collapse
Using toolkits will get you out of a jam here and there, but you won't learn anything. Get rid of the toolkit and use adb and fastboot. You'll be glad you did.
estallings15 said:
Using toolkits will get you out of a jam here and there, but you won't learn anything. Get rid of the toolkit and use adb and fastboot. You'll be glad you did.
Click to expand...
Click to collapse
+1 especially when you're having troubles in the first place. just figure it out, it's not very difficult so you will know how to resolve issues in the near future and not have to rely on the XDA forums to fix a simple problem.

Urgent help PLEASE!

I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.
Rizy7 said:
I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.
Click to expand...
Click to collapse
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.
Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
I used adb to push a file but I cant see it
thank god it worked
simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
gee2012 said:
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.
Click to expand...
Click to collapse
username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
Thanks for your help guys

Categories

Resources