Database Develop

[Q] Bootloop after Dalvik wipe and accidental reboot

Hi,
I have SlimICS 4.2 rom installed, and was working flawlessly. I wanted to flash Semaphore 1.3.0s kernel to try it, so I went into recovery to flash it.
I wiped Dalvik cache, but when I was going to wipe cache and flash, I accidentally rebooted the phone. Now it is stuck in a bootloop, and I can´t access recovery. I am able to enter Download Mode.
How can I fix it? I´m quite a noob at flashing, so a step-by-step guide would help me to avoid future mistakes.
Thanks in advance

pollopava said:
Hi,
I have SlimICS 4.2 rom installed, and was working flawlessly. I wanted to flash Semaphore 1.3.0s kernel to try it, so I went into recovery to flash it.
I wiped Dalvik cache, but when I was going to wipe cache and flash, I accidentally rebooted the phone. Now it is stuck in a bootloop, and I can´t access recovery. I am able to enter Download Mode.
How can I fix it? I´m quite a noob at flashing, so a step-by-step guide would help me to avoid future mistakes.
Thanks in advance
Click to expand...
Click to collapse
do you know how to use odin?
i cant post links here if u can pm me i will give you the link

nayantha said:
do you know how to use odin?
i cant post links here if u can pm me i will give you the link
Click to expand...
Click to collapse
Thanks Nayantha
I used Odin to flash Darky 10.1 some time ago, but I followed a step-by-step guide and I really don´t know what each step does. From what I´ve found in the forum, a solution would be to flash the kernel or a full rom via Odin, but I´m afraid of making it worse because I don´t know what I am doing. That´s why I´m hoping for a step-by-step guide.

i also had the same issue
so i flashed stock gb using odin
and root it
then flashed ICS333-2.0.1 rom
after that i flashed jb rom
problem fixed
i cant post my friends link here coz im new pm me i can solve

ODIN stuck
Hi
I tried flashing the semaphore kernel through Odin but it is stuck in "Setup connection". I want to restart everything and try again, but I´m afraid something worse will happen if I disconnect the phone now. ¿Is it safe to unplug it?
Thanks!

pollopava said:
Hi
I tried flashing the semaphore kernel through Odin but it is stuck in "Setup connection". I want to restart everything and try again, but I´m afraid something worse will happen if I disconnect the phone now. ¿Is it safe to unplug it?
Thanks!
Click to expand...
Click to collapse
I answer myself: I disconnected the phone and I got the dreaded exclamation sign. No fear, removed the battery and plugged it again. Back to download mode, connected it to the same port but this time using Odin 1.7, and worked perfectly!
Thanks for your support!

pollopava said:
I answer myself: I disconnected the phone and I got the dreaded exclamation sign. No fear, removed the battery and plugged it again. Back to download mode, connected it to the same port but this time using Odin 1.7, and worked perfectly!
Thanks for your support!
Click to expand...
Click to collapse
it calls software brick. can recover from it. i messaged you regarding your issue how to securely flash jb from beginning.

[Q] Bootloop + Recovery wont boot

So yeah i bricked my phone, its stuck in a damn bootloop and i cannot enter recovery no matter which one i install.
I even flashed stock rom via odin and tried both flashing twrp and cwm, none worked, whichever rom is installed i still get in a damn bootloop and i cannot boot into recovery (blank screen).
Is there anything i can do for my phone?
Thank you all in advance

Try to flash Dorimanx Kernel using Odin (v9.34 for JB Roms, v8. for Stock Roms)
I will upload a guide tomorrow for people facing problems with their recovery. I will edit this when its finished.
EDIT: Here it is: http://forum.xda-developers.com/showthread.php?t=2441940
Sent from my GT-I9100 using xda app-developers app
Hit Thanks please

OverkillSRB said:
So yeah i bricked my phone, its stuck in a damn bootloop and i cannot enter recovery no matter which one i install.
I even flashed stock rom via odin and tried both flashing twrp and cwm, none worked, whichever rom is installed i still get in a damn bootloop and i cannot boot into recovery (blank screen).
Is there anything i can do for my phone?
Thank you all in advance
Click to expand...
Click to collapse
can you tell me what did you do to caused that ? or do you have download mode ?
anyway it seems to me a hard break . probably you messed your boot . you got two options:
1.use "RescuePDA" (you can find the thread and every thing in galaxy mini II development)
2.take it to a service center

dlb4all said:
can you tell me what did you do to caused that ? or do you have download mode ?
anyway it seems to me a hard break . probably you messed your boot . you got two options:
1.use "RescuePDA" (you can find the thread and every thing in galaxy mini II development)
2.take it to a service center
Click to expand...
Click to collapse
Download mode is the only thing that works, as i said recovery wont boot and any rom i install is getting into a bootloop. ((
I used triangle away, the problems started after that. I had cwm and cm 10.1 08/18
Is there any way to factory reset using odin?

I have the same exact problem.
I follow the discussion with interest.

zeruel857 said:
I have the same exact problem.
I follow the discussion with interest.
Click to expand...
Click to collapse
Zeruel, i seem to have somehow fixed the problem, however not entirely.
I downloaded some random recovery rom, flashed it with odin and wiped everything (cache, factory reset, dalvik cache), and reinstalled cm 10.1.
Then i flashed back the thewhisp's recovery and booted into cm with no problem.
However now i cannot boot into recovery using volume+- and home and power button, i have to boot to it from the cm.
That i dont know how to solve, but at least my phone works fine

Thank you, but I think to have solved the problem with RescuePDA.
A big thanks go to dlb4all, thank you a lot mate.

zeruel857 said:
Thank you, but I think to have solved the problem with RescuePDA.
A big thanks go to dlb4all, thank you a lot mate.
Click to expand...
Click to collapse
no problem man . my pleasure :good:

[Q] [20a] stuck in cwm bootloop after installing 20b update

Hi,
i am stuck in a bootloop.
i have an unlocked bootloader and had CM10.1 previously.
i then went back to an old 20a backup i made some month ago.
that worked fine.
my phone downloaded an update to 20b then, and i installed it.
after that i am stuck in a bootloop now. normal booting gives me cwm.
i am not able to turn the phone off and charge it, as mentioned somewhere else, to clear the "boot to recovery" flag.
someone knows a way to clear this flag?
Its not important for me if i run stock or CM, but even when i install my CM backup now it still boots into recovery.
holding <down> while rebooting gives me "S/W Upgrade - Please wait while upgrading".
it seems the 20b update is still present and trying to boot into stock recovery, resulting in cwm getting loaded everytime.
(cwm works fine, i can upload a zip and execute it)
greetings

LamerDuck said:
Hi,
i am stuck in a bootloop.
i have an unlocked bootloader and had CM10.1 previously.
i then went back to an old 20a backup i made some month ago.
that worked fine.
my phone downloaded an update to 20b then, and i installed it.
after that i am stuck in a bootloop now. normal booting gives me cwm.
i am not able to turn the phone off and charge it, as mentioned somewhere else, to clear the "boot to recovery" flag.
someone knows a way to clear this flag?
(cwm works fine, i can upload a zip and execute it)
greetings
Click to expand...
Click to collapse
i had the same, if you want to install ota updates you should have the "original" recovery.
i flashed it back to stock with LG .kdz flasher. if i remember correct flashing a backup from sd card won't slove this problem.
Greetings
moneyvirus

moneyvirus said:
i had the same, if you want to install ota updates you should have the "original" recovery.
i flashed it back to stock with LG .kdz flasher. if i remember correct flashing a backup from sd card won't slove this problem.
Greetings
moneyvirus
Click to expand...
Click to collapse
hm, i remember having the same problem while installing CM. there was something i did to interrupt the loop, and yes, i think the original LG suite or kdz was involved. but i should not need to reflash the original rom.. its just a flag, i should be able to clear it with sideload/zip/button combination.
[edit] maybe i wasnt clear about that: i dont need the 20b upgrade, i would love to cancel the update process, if that makes my phone boot again.

LamerDuck said:
hm, i remember having the same problem while installing CM. there was something i did to interrupt the loop, and yes, i think the original LG suite or kdz was involved. but i should not need to reflash the original rom.. its just a flag, i should be able to clear it with sideload/zip/button combination.
[edit] maybe i wasnt clear about that: i dont need the 20b upgrade, i would love to cancel the update process, if that makes my phone boot again.
Click to expand...
Click to collapse
sorry but i can't help you with the flag... i solved it by reflashing but i have to admit it's quite drastic.

well..
i will reflash stock i guess.
do you remember which thread/tool/drivers you used to reflash?
i am on win7 and my PC isnt able to load fastboot nor LG mobile usb drivers.
i have them installed but get the yellow warning on both in windows hardware administration page

LamerDuck said:
well..
i will reflash stock i guess.
do you remember which thread/tool/drivers you used to reflash?
i am on win7 and my PC isnt able to load fastboot nor LG mobile usb drivers.
i have them installed but get the yellow warning on both in windows hardware administration page
Click to expand...
Click to collapse
it's allready a lot of months a go but i think i used this thread.
http://forum.xda-developers.com/showthread.php?t=2179126
Goodluck m8

LamerDuck said:
well.. i will reflash stock i guess.(
Click to expand...
Click to collapse
Easiest way to reflash stock is to force an update using the LGMobile Support Tool. Once your phone is connected (I suggest the S/W Update mode) look for the option somewhere in the upper right menu.
Edit: This will also revert to the stock recovery.

balloon27 said:
Easiest way to reflash stock is to force an update using the LGMobile Support Tool. Once your phone is connected (I suggest the S/W Update mode) look for the option somewhere in the upper right menu.
Edit: This will also revert to the stock recovery.
Click to expand...
Click to collapse
if i recall correctly, the LGMobile Support Tool tool wont recognize my phone, since i have a custom kernel, unlocked bootloader and a custom ROM.
i am trying to flash stock ROM now with kdz updater ( http://forum.xda-developers.com/showthread.php?t=2069723 ), and if this does not work i am going through every method thats there..
total overkill for a working phone thats just too stupid to boot the right option..
@moneyvirus: thx

LamerDuck said:
if i recall correctly, the LGMobile Support Tool tool wont recognize my phone, since i have a custom kernel, unlocked bootloader and a custom ROM.
Click to expand...
Click to collapse
Not sure about this, but the S/W mode might make a difference here. No harm in trying, right?

well. i was able to install stock 20a with kdz updater and link above.
cwm is gone now ofc, but everything at least works.
in some hours i will be rooted and cwm'ed again, but well... its always the same lesson: never touch a running system.
but maybe here's the wrong place to insist on this wisdom

phone stuck on att screen after cm11 installation

ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?

cantuluis said:
ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?
Click to expand...
Click to collapse
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.

cmerlyn said:
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.
Click to expand...
Click to collapse
I dont know what i was running originally. However i am back in business!!!
I found the superguide followed it regarding the RUU and luckily i got my phone to work again.
I want to try flashing the CM11 again, i am guessing that either i am doing something wrong or maybe TWRP is not working correctly on my phone and not flashing the rom as it should.
Any known issues with TWRP and the vivid? shall i try another recovery?
Are the following steps pretty much what i should do to flash it
1. factory reset
2. system reset
3. clearing caches
4. flash boot.img (i am s-on)
5. flash rom
6. flash gapps
any suggestion is welcomed

Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk

rignfool said:
Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
it is 1.85.0025
additional info:
After recovering the phone i decided to lock the bootloader and start all over again. I re-root and then, instead of installing TWRP i used CWM and obviously, got a nand backup.
O tried flashing again CM11 and got the exact same results. Stuck in the initial HTC screen forever. Tried to restore my NAND Backup and the result was also exactly the same as before, phone would get the htc screen, then the beats audio and att animations and then will stuck onthe att screen forever.
This is weird, i must be doing something wrong here...

Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.

"Small mistake"
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments

I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.

Yuskow said:
I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.
Click to expand...
Click to collapse
Yes i do have access to bootlader and recovery, i actually was able to bring back to life the phone using RUU. So the issue now is not that the phone is bricked but that anything i try to load on it fails, being CM11 or even the NAND backup that i took with this same phone just after installing recovery, nothing seems to work.
I was googling around and so another person that had similar behavior on his vivid but didn't posted if he was ever able to fix it...

Yuskow said:
Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.
Click to expand...
Click to collapse
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?

You tried reading the following post: http://forum.xda-developers.com/showthread.php?t=2642575,? It's different from what I showed above, there describes another way to recover your vivid by projectisaac:fingers-crossed:

cantuluis said:
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?
Click to expand...
Click to collapse
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.

Yuskow said:
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.
Click to expand...
Click to collapse
ok guys i am now officially an idiot.
Problem came down to be that i was using the wrong boot.img, i didnt know that the correct one is INSIDE the rom zip. I tried it once more and now i am running CM11
thanks for your suggestions and sorry for taking your time on this newb learning experience

alosegon said:
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments
Click to expand...
Click to collapse
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk

rignfool said:
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
thanks for clarifying that

Glad you're up and running.

Btw, this ROM is amazing, so much better than the stock at crap
Sent from my Vivid 4G using Tapatalk

[Q] Kinda odd bootloop (help ASAP, pls)

Sooo, I got a problem with my Galaxy Mini 2.
First, I wanted to flash Cm11 (by TheWhisp), but something went wrong during flashing process, and my device bootlooped.
I tried to go into recovery, but it didn't work.
Than I thought it might be a good idea to flash stock ROM via odin. I did it once in the past, with a succesful outcomes, so I fought it will work again.
This ended with a bootloop, only change was the logo during boot process. Than I tried to flash recovery but it didn't change anything.
So my phone is in bootloop, stock ROM flashing doesn't help, and I can't run recovery.
Any ideas how can I fix it?

Do a search before posting
myrczu said:
Sooo, I got a problem with my Galaxy Mini 2.
First, I wanted to flash Cm11 (by TheWhisp), but something went wrong during flashing process, and my device bootlooped.
I tried to go into recovery, but it didn't work.
Than I thought it might be a good idea to flash stock ROM via odin. I did it once in the past, with a succesful outcomes, so I fought it will work again.
This ended with a bootloop, only change was the logo during boot process. Than I tried to flash recovery but it didn't change anything.
So my phone is in bootloop, stock ROM flashing doesn't help, and I can't run recovery.
Any ideas how can I fix it?
Click to expand...
Click to collapse
You forgot to wipe data and now you got bootloop !
Find yourself a solution by read threads from here <click>
Or go here for solution !

Same issue here and ill the upper link to resolved the problem.Thanks for the link

Wonderful
Lodaserves said:
...Thanks for the link
Click to expand...
Click to collapse
Thanks button? :laugh:

Ok i will dont worry =)