Database Info

had it for 5 hours and already bricked

i just got my inspire a couple hours ago and i was trying to flash a CM kernel using kernel manager and it froze right after it finished and was completely unresponsive so i did a battery pull and now it's stuck on the white htc screen
please help

Power up with vol down....orange light comes on power up wit vol up sends me to CM.

i did that and tried to reboot from there and it still didnt work but right now im trying to update from the p???????? left by the simple root method

search before you post please. Please take a look at the guide that is stickied, there is a guide and even a video..

this isn't about flashing anything it's about something with a kernel that i messed up but it's working now

hmmm interesting enough, though you are wrong! How exactaly do you think you get the kernel on the phone?
And since I wrote the guide and made the video, I assure you it is on there.

actually i used kernel manager to do this so i did it on my own buy i do like your guide and i'm sorry for any problems

It uses the same process as rom manager and, flashes the kernel via cwm. What causes the soft brick is an incorrect flash . Its the same process for any incorrect flash whether it is a rom or kernel.

Just be sure to try everything. I'm sure you'll find a solution.

When you use the simple root, in order to flash a custom rom you have to root then go back to the downgraded version without sound and flash a rom from there. So now to fix it just flash stock rom and start over but when u get to the downgraded version just flash instead

If you're trying to flash an Android 2.3 rom, you have to have CWM 3.0+, and if you're trying to flash an Android 2.2 rom, you have to have one of the 2.5 versions.
I had the same problem as I was trying to flash the wrong file (an Android 2.2 rom) as I had updated CWM to 3.0.0.6 at the time. I finally realized I was choosing the wrong file the entire time, and then I was able to flash the Android 2.3 rom with no problems.

Phone won't boot into ClockworkMod Recovery

Hi,
I currently have ClockworkMod Recovery 6.0.2.3 installed and am using ROM Manager Premium 5.5.1.5 to attempt to install CyanogenMod.
I have the correct rom downloaded for the Verizon version, but every time I try to boot into the ClockworkMod recovery, the standard Android Recovery screen comes up instead.
I have followed about 3 different tutorials, and each ended in the same result.
Any idea what could be going on?
Thanks!

Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.

Edgehood said:
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Click to expand...
Click to collapse
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM

CAKELIE said:
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Click to expand...
Click to collapse
How did it fail?
Sent from my LG spectrum (that's right) blazing fast on cm10!

I am having almost the same problem. I rooted my phone using this:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT6 - ZSLO2 Fixed for bootloop
ZCLSF (no bootloop fix, proper default.prop)
http://d-h.st/users/philz_touch/?fld_id=16061#files
taken from here: http://forum.xda-developers.com/showthread.php?p=31911620#post31911620
as it matches my phone make, build, kernel's date, model, etc. The trouble is when I go to recovery mode from ROM Manager it just stops on its way showing me this green little robot and a progress bar in the middle and it could stay like this for hours without moving anywhere. I have to press my power button and then it moves on and reboots into CWM. I have tried a whole lot of different rootings methods but ROM Manager v5.5.3.7 simply refuses to work with PHILZ-CWM6-DDLSC-ODD-5.06.1-SIGND.ZIP... I am completely lost...
Could anybody suggest / advise anything please? I would highly appreciate it Many thanks in advance!
I am on Android 4.1.2 Jelly Bean, Samsung Galaxy Note GT N7000, build number is JZ054K.N7000DDLSC, baseband version is N7000DDLS6, kernel version is 3.0.31 – 906407 March 6, 2013.

[Q] Stuck in endless Bootloop

i'm stuck in an endless bootloop after trying to upgrade the CM10 Beta 4 version on my Samsung Galaxy S Plus.
This is what i did
I'd upgraded from 2.3.3 to 2.3.6 some months ago. Then flashed CM10 Beta 4 by ivendor.
For this i first downloaded the CWM -> recovery-clockwork-5.5.0.4-ariesve.tar.md5 and flashed it using Odin.
Then the ROM file -> cm-10-20130324-ivendor-beta4-ariesve.zip
Was checking the updates on this and found much advances in the 2.5 release of 2 May 2013.
So downloaded the CWM -> CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5. When i tried to flash using Odin it gave me the MD5 error.
Saw somewhere on the forum to flash using zip file, so downloaded CWMRecovery-6.0.2.8-ariesve-kernel26.zip and tried to flash. This was when my phone got soft-bricked.
Removed the cable, battery etc. After some time, was able to go into Download mode but not Recovery.
Then i tried to flash to stock ROM (2.3.6) - I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5. This completed and Odin said PASS. But the phone now goes into a bootloop. Tried the Recovery mode but after the Android-out-of-the-box symbol it again said SAMSUNG and started the boot. This is repeating continuously. What should i do now? Please help.
This is the sequence of things...
1) 2.3.3 to 2.3.6 - Success !!
2) Flash with CM10-Beta 4.a) recovery-clockwork-5.5.0.4-ariesve.tar.md5 - OK
b) cm-10-20130324-ivendor-beta4-ariesve.zip - Success!!!
c) gapps-jb-20121011-signed.zip - Success!!​3) Flash with CM10-Release 2.5a) CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5 - MD5 checksum error !!
b) CWMRecovery-6.0.2.8-ariesve-kernel26.zip - Soft-bricked !!!​4) Flash stock ROM (2.3.6) a) I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5 - PASS
Bootloop
Cannot go into Recovery mode too (after Recovery mode icon appears SAMSUNG logo comes up and phone boots with the blue spiral, this goes into a continuous loop)​

anoopgkris said:
i'm stuck in an endless bootloop after trying to upgrade the CM10 Beta 4 version on my Samsung Galaxy S Plus.
This is what i did
I'd upgraded from 2.3.3 to 2.3.6 some months ago. Then flashed CM10 Beta 4 by ivendor.
For this i first downloaded the CWM -> recovery-clockwork-5.5.0.4-ariesve.tar.md5 and flashed it using Odin.
Then the ROM file -> cm-10-20130324-ivendor-beta4-ariesve.zip
Was checking the updates on this and found much advances in the 2.5 release of 2 May 2013.
So downloaded the CWM -> CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5. When i tried to flash using Odin it gave me the MD5 error.
Saw somewhere on the forum to flash using zip file, so downloaded CWMRecovery-6.0.2.8-ariesve-kernel26.zip and tried to flash. This was when my phone got soft-bricked.
Removed the cable, battery etc. After some time, was able to go into Download mode but not Recovery.
Then i tried to flash to stock ROM (2.3.6) - I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5. This completed and Odin said PASS. But the phone now goes into a bootloop. Tried the Recovery mode but after the Android-out-of-the-box symbol it again said SAMSUNG and started the boot. This is repeating continuously. What should i do now? Please help.
This is the sequence of things...
1) 2.3.3 to 2.3.6 - Success !!
2) Flash with CM10-Beta 4.a) recovery-clockwork-5.5.0.4-ariesve.tar.md5 - OK
b) cm-10-20130324-ivendor-beta4-ariesve.zip - Success!!!
c) gapps-jb-20121011-signed.zip - Success!!​3) Flash with CM10-Release 2.5a) CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5 - MD5 checksum error !!
b) CWMRecovery-6.0.2.8-ariesve-kernel26.zip - Soft-bricked !!!​4) Flash stock ROM (2.3.6) a) I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5 - PASS
Bootloop
Cannot go into Recovery mode too (after Recovery mode icon appears SAMSUNG logo comes up and phone boots with the blue spiral, this goes into a continuous loop)​
Click to expand...
Click to collapse
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it

Will try this
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
Thanks, will try this tonight
I already took the Nandroid backup before flashing CM10 Beta 4. But was not able to go into it after my phone was soft-bricked.

Solved - booted into 2.3.6 !!!
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
A million thanks!! It somehow started now into the 2.3.6.
Flashing the recovery-clockwork-5.5.0.4-ariesve.tar.md5 did not solve the bootloop. Then i flashed the Boot_loader.tar. That too did not solve the bootloop. Tried Recovery mode again but the SAMSUNG logo kept coming and going until i released my fingers after a full two minutes. Then before the android-out-of-the-box icon came it went straightaway into Recovery .
Wiped Data and Cache and rebooted. After a very very long time it started and asked if im okay with the Google data collection policy asked in Polish language.
Wow, going to update to 4.1.2 Release 2.5 in some time.
Thanks again man. :good:

Got CM10 Beta 4 again !
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
All went smooth. CM10 Beta 4 is back on my SGS+.
Thanks for the advises and help

anoopgkris said:
All went smooth. CM10 Beta 4 is back on my SGS+.
Thanks for the advises and help
Click to expand...
Click to collapse
U got it man:victory:
It's good that u posted the way u solved it! so that it would help others who face the same problem
BTW add the word [solved] in ur thread topic..
Hit thanks rather than typing it

[SOLVED] Bootloop problem after soft-brick
parkourkarthik said:
U got it man:victory:
It's good that u posted the way u solved it! so that it would help others who face the same problem
BTW add the word [solved] in ur thread topic..
Hit thanks rather than typing it
Click to expand...
Click to collapse
Sure, thanks !!
Also pasting here an easter egg that i saw after loading Gingerbread 2.3.6 before this CM10.
Putting this because i tried this for the first time in GB (the seven times click on android version)

[Q] Rogers Infuse 4G (i997r) help upgrading to kitkat

I have a Rogers Infuse 4G (i997r) and I have been trying to upgrade it to kitkat by using a unofficial Cyanogenmod rom. More recently have been trying to use Carbon rom to update it. I have been running into problem after problem, error after error and I have finally decided to post something on XDA in hopes that someone with more experience can help me out. More information about the errors and what I have done to the phone below.
About a year ago I got this Rogers infuse 4G from a friend. I messed around with it for a bit but what I really wanted to do with it was install a custom rom and update it to a more recent version of Android (It started out on gingerbread (2.3)).
I had a real hard time getting modified recovery 3e because there was not original recovery file in system>bin to replace.
I forget most of what happened but it ended with me using a application to convert the cwm recovery zip to a md5 because I couldn't get modified 3e to work.
I tried using odin to flash the files I made but odin got stuck (or was just taking forever) and I unplugged my Infuse.
The infuse was bricked and would only show "firmware upgrade encountered an issue please select recovery mode in kies and try again". The phone would'nt enter recovery or download mode. It was recognized by odin but seemed as if it was not responding.
About 3 days ago I finally decided to try to unbrick the phone again (I don't know why just felt like it) and I found GTG ultimate unbrick with a pit file. I tried uploading this using odin and the phone responded and downloaded the files.
The phone showed a AT&T splash screen and then the Samsung logo. It hanged at the Samsung logo for about 3 minutes then would turn off reboot, show the AT&T splash screen then the hang at the Samsung logo for 3 minutes again.
I decided that I didn't actually need to install working android because I just needed CWM Recovery and found a CWM Recovery that was flashable with odin.
Now that the phone would actually show a splash screen I could access download mode and the stock 3E recovery.
I went to download mode and flashed CWM Recovery 6 - Voodoo Lagfix with odin
In the CWM Recovery I clicked install update.zip
The phone said installing and when it finished it rebooted.
It showed the AT&T logo and then the Samsung screen then it started talking (which btw scared the **** out of me) and it said installing voodoo lagfix, estimated time remaining 2 minutes
After it was done installing it rebooted and I had the same problem as before. It would show the AT&T logo then hang at the Samsung screen for 3 minutes.
I reflashed the GTG unbrick with odin then I reflashed the CWM Recovery and I was back into the recovery. (It wouldn't just let me boot into it I had to reflash it which was weird)
This time instead of clicking install update.zip I installed the Cyanogenmod-11-infuse-4g-unofficial-2014(some build number).zip
I got (status 7) installation aborted.
when the phone rebooted it showed a cyanogen mod loading screen and I got really excited
after the loading screen it went straight to proper CWM Recovery then it instantly crashed with a little fallen over Android and a red triangle over it.
It kept boot looping like this so I asked for the unbrick files for a Rogers Infuse 4G and installed those.
Once I installed the Rogers Infuse 4G Rom I set it up but I ran into the same problem I had last time.
I can't install the modified 3E recovery because the recovery file is not system>bin. CWM Recovery also fails to install even though it says it has installed.
It turns out the recovery file is on the root of my phone not /system/bin
Im not really sure what to do and guidance would be appreciated.

It's because the CWM is not only device specific, but carrier specific (at least for the Infuse).
Flash the following file (extracted) with Odin. It will talk to you as well after reboot, but it will give you CWM red which you can use to move on to custom ROMs:
https://www.dropbox.com/s/t0kc92124jat6yt/CWM Infused Kernel.zip?dl=0
Be sure to disable Voodoo Lagfix before installing any ROM's, especially if shortcut'ing directly to CarbonROM (versus installing CM9, then CM10.1 and finally a KitKat ROM).
Good luck, let me know if you have any questions.

Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error

Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error. Accidentally Double Posted... Im a noob. If someone could delete this repost it would be appereciated

OnfireNFS said:
Thanks so much for both the Rogers stock rom and the help today. I left out one crucial piece of information earlier by mistake. I tried installing both cyanogenmod and carbon rom earlier using the voodoo fix version of CWM Recovery and I got another status 7 installation aborted. I deleted the assert part of the update-script. My problem now is I get status 6 installation aborted and I haven't been able to find a quick fix for it. I just tried again using the red version of CWM Recovery you gave me and I still get the same error
Click to expand...
Click to collapse
Just to be clear. With the original ROM file, did you try installing the ROM with this CWM and Voodoo Lagfix disabled? That is go into CWM's options menu, and disable there?
Just trying to pick the low hanging fruit, unfortunately I don't know where to go from there (as this is my only idea now, besides re-downloading the ROM).

I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.

OnfireNFS said:
I have no problem reflashing the roms are anything. I have a iPhone 5S (hoping to get a S5 or S6 in 2015 once my contract expires ) so I have no important files or anything on this phone. (In fact I just reflashed that rogers rom yesterday from a blank slate) I noticed you have (had?) a Infuse 4G running Carbon 4.4.4 and honestly that's all I want to get to. If you want me to reflash roms or files I have no problem doing so. I just would like my infuse to run Carbon 4.4.4.
Click to expand...
Click to collapse
It used to be that in order to get from Gingerbread to say, Jellybean, you needed to install the Ice Cream Sandwich ROM (CM9) first. This gives you a relatively new CWM in order to do your bidding. But you man need to install a Jellybean ROM (I suggest CM10.1) in order to get a CWM that will like the installation of KitKat.
So Stock (Infused CWM) -> CM9 -> CM10.1 -> CarbonROM 4.4.4
Of course, I did say used to. Apparently if you disable Voodoo lagfix in CWM you can go straight to CarbonROM. I never tried it, but it is worth a shot (avoids having to go on a scavenger hunt).
But if you already tried it with no success, now you know the classical way.

Thanks a lot. By upgrading to cm9 then cm10 then finally Carbon Rom I was able to get the phone to kitkat!
Cheers

[$20-donation giveaway] p5110 cannot go back to stock . Stuck in cm10.1

Hi guys. i've been searching and trying to solve this problem for the past two weeks. can't fcking deal with it anymore. $20 for anyone that can help me , PLEASE!
p5110 here. had cm10.1 working for more than 1 year. when i updated to cm.10.3-rc2 , problems appeared.
Tried flashing stock firmware via odin. Says successfull but still in cm10.3 after reboot. boots up , however, it reboots after 1-3 mins.
tried flashing different roms, error.
Please, how can i revert back to stock or any working state ???
thanks,
alex

Anyone ?!

Try installing Clockworkmod (newest version) and then flash the stock firmware with that. Be sure to clear cache and dalvik cache first, and also factory reset (all through clockwork mod)

Latest official CWM won't help as it's to old for anything (stopped at 6.0.2.7 if i am not wrong), better use latest TWRP.
But: it sounds like your emmc got read only because it reached end of lifetime.
Indicator for that:
- flashing a different recovery via Odin doesn't change the recovery - it still boots the old.
- factory reset inside recovery doesn't change anything
Only way i know to get back write access would be to update the emmc firmware via JTAG. If there's no one with a JTAG near your place, replacing the emmc will be the solution.
GT-P5110 16 GB or 32 GB?
What recovery (also recovery version) are you using?
Using a custom kernel?