Database Develop

CWM Recovery Boot Loop. Help!

Hi Everyone,
I have a GT-N7000 - it's been working great since I bought it 9 months ago. I was running RocketRom on it for months. I've been using RR 11 (I didn't like 12) and haven't had a problem with it. The CWM that comes with it appears to be 6.0.1.2 and I kept the stock kernel (OneNote??). Lately, my sms messages were being sent sporadically and I kept getting this same SMS pop-up over and over (every time I sent an SMS). I know it's probably a carrier issue but I thought I would boot into recovery and wipe the cache and Dalvik. I've done this several times in the past without problems.
I first wiped the cache, then I did Dalvik. For Dalvik, I got the error E:\ unavailable (I recall seeing this in the past). I select "Reboot" and the phone booted back into CWM. I've tried removing the battery and same thing.
I ended up trying to flash back to the pre-rooted GB using Odin. The flash completes and the phone reboots but, yep you guess it, CWM comes up. It's the same version. So apparently this is not being updated by Odin??? I read somewhere that this is a CW bug that does not clear a flag to boot back into Android but the fix seems overly complex and worries me (I'm not afraid of doing it if it will fix it).
I'm entertaining the idea of using Kies to do a "Firmware Upgrade" which looks like it will install the latest ICS. It successfully downloads the new firmware then asks me to connect the phone. Before I do this, I wanted to check here to see if this is my only (best) option. Or if I should try something else? Also, Kies says system and data will be initialized so will my sms logs, photos, etc be deleted as well? Not a huge issue since I save the photos to the external sd. I just want to know if the USB storage will be wiped too.
[EDIT] I wanted to add that I TRIED to install Abyss from CWM and it hangs. Same ting with installing RR again. It appears that the file system is locked or something. Pretty much nothing works in CWM. I even tried mounting the various partitions then installing Abyss. It just hangs on "installing." I suspect the problem occured when I wiped the cache or Dalvik. I just don't know what
I appreciate any input.
Thanks!

dont use abyss... try other like hydracore or speedmod 3-15

Im a noob and im afraid i may have this also..

Try to download Philz kernel for your built number, and flash the philz zip file from recovery.
or if can't flash from recovery, try to download the ODIN file for philz kernel (TAR file).
It should re-injected the CWM.
Sent from the corner of this rounded earth.

[Q] HELP - Softbrick Galaxy Tab 8.9 Telstra p7320

Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers

ragvaror said:
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
Click to expand...
Click to collapse
hey mate,
i was just caught out by this last night. all you need to do is re-flash on a stock rom with ether oden of heimdall and youre good to go. im sure there is a oden flashable rom on these forums
take it sleazy!

Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.

ragvaror said:
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
Click to expand...
Click to collapse
yeah, i think its becaute the cwm recovery doesnt know what to do with the update.
you need to have the stock recovery installed. dont take my word for it though.
just look up a tutorial for flashing a rom via oden. its really easy, just make sure the image you are flashing is of .tar.md5 extension.

You can get the stock rom at sammobile.com. down load the zip file then extract the .tar.md5 file out of it using 7-zip.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.

how ?
ragvaror said:
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
Click to expand...
Click to collapse
i currently have the same problem as you did, how did you flash with odin if you're stuck in recovery mode ?
please help, I'm racking my brain trying to figure this out.

[Q] Phone fails to start installing ROM

Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?

Anyone?

I guess no one is using this phone anymore?

Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo

Huawei P7, bricked, somehow restored, further assistance

Hello all my fellow Huawei P7 users. Last week, I finally decided to update my Huawei from EMUI 2.3 (B136) to "next level". For some reason, when I tried to download the rom through Updater, error was reported. something with "checksums". So I download rom, and tried "local update"... and it's gone (TWRP was installed, don't know if this could be reason). So yeah, our beloved bootloop became my second friend. So I tried to restore stock rom, with stock recovery 3.0, extracted from updater.app, recovery.img and boot.img, created dload on sd, started procedure, "Verifying install package" and at some point just "FAIL". Tried even with the first stock ROM (Because in manual there was no "previous versions") still got "FAIL". Tried to install "MyRom 1.2", again bootloop, as far I concerned it's because I don't have "stock rom". So I tried, X-Rom. and you know what, it worked without any problems. Even though I like it, I still want back to stock ROM. So I want to ask you my dear friend. how I can get back my stock ROM? If I again try "very first stock rom" and it will "FAIL", is there anything else I can to do bring back my stock? Or maybe someone knows, why it "fails" to verify package

RocketDoge said:
Hello all my fellow Huawei P7 users. Last week, I finally decided to update my Huawei from EMUI 2.3 (B136) to "next level". For some reason, when I tried to download the rom through Updater, error was reported. something with "checksums". So I download rom, and tried "local update"... and it's gone (TWRP was installed, don't know if this could be reason). So yeah, our beloved bootloop became my second friend. So I tried to restore stock rom, with stock recovery 3.0, extracted from updater.app, recovery.img and boot.img, created dload on sd, started procedure, "Verifying install package" and at some point just "FAIL". Tried even with the first stock ROM (Because in manual there was no "previous versions") still got "FAIL". Tried to install "MyRom 1.2", again bootloop, as far I concerned it's because I don't have "stock rom". So I tried, X-Rom. and you know what, it worked without any problems. Even though I like it, I still want back to stock ROM. So I want to ask you my dear friend. how I can get back my stock ROM? If I again try "very first stock rom" and it will "FAIL", is there anything else I can to do bring back my stock? Or maybe someone knows, why it "fails" to verify package
Click to expand...
Click to collapse
If I'm getting this right, you're currently on EMUI 2.3. If that's true, you'll need older version of TWRP like 2.8.1.0 for EMUI 2.3. Once in recovery you need to wipe ALL DATA by confirming YES. Once everything deleted you'll be able to flash stock recovery and force-update the stock ROM (EMUI 2.3). I had a similar problem until I realised that I was using wrong version of TWRP.

Install Stock Firmware (JB 4.1.2) without Odin

Hi everyone, I'm here because i have problems with my phone and i want to fully restore. To do this i would like to install a new ROM, but from what i've seen, to install a ROM is necessary to have the stock JB 4.1.2 on the device, while i have CyanogenMod 11 (4.4.4) running.
This wouldn't be a problem if i could use Odin, but apparently my USB port has something wrong, and i cant connect my phone to any PC, so i cant flash in that way. Luckly i can access to the custom recovery (CWM), so i 'd like to ask if there is a way to flash the stock firmware via CWM.
Instead, If I can install a ROM starting directly from CM11 without restoring stock JB, or if i'm missing something important, let me now, i would appreciate a lot
Thank you in advantage. (Excuse se for any misspelling, I'm not English)

What kind of problems do you have?
If you can access CWM recovery there's no need to install stock in order to flash a new ROM, just be sure to wipe caches and data before installing the new one to avoid related bugs; and you will probably need to update the recovery to TWRP if you want to flash one of the most recent ROMs
It's always recommended to create a backup before everything else.
Peace

Hi, thank you for then anwer Well, it would be a long list of problems ^^ The biggest one though is the fact that if I'm in AeroMode everything works as always, sometimes bugged but nothing exceptional, but in the moment i switch AeroMode off and digit the SIM pin, the phone turns off and then enters in a bootloop(vibrating every 1 minute like before entering the main window, but it remains stuck) that is solvable only pressing for 8/10 secs the POWER button and restarting it. I can't have a phone which is not able to make voice calls :/ Back to the problem, so if i'm not misunderstanding anything, I dont need to reverto to stock and then reflash the new ROM? Because, for example, in the main page of CM13 it's written:
ROM Firmware Required: Stock + CWM compatible with KitKat
and that's the origin of my post... But in case, which wipe should i do? Dalvik + wipe data/factory reset?

OK, the thing is that you need stock + CWM at minimum, it means you can't install it if you are on gingerbread; but if already installed something higher than 4.1 you can go from there.
First create a backup then wipe cache, wipe dalvik, factory reset and install your preferred ROM

Ohhh, that makes sense.... Ok, so i will wipe what you said and flash the new ROM! You saved me a lot of time, thank you so much!