Database Develop

[Q] Recovery doesn't "stick"?!

Hello guys,
I would like to flash a different version of CWM onto my N7000 but somehow it does not stick.
I currently run AOKP 4.1.2 and it has 6.0.1.5 as CWM which always gives you the md5 generation error when you do a nandroid backup.
I've installed Rom Manager and downloaded a different version of CWM and tried to install it both with Rom manager and also in CWM itself.
On the first boot after I flash some other recovery like the one from rom Manager (6.0.1.2) it actually loads the new recovery and lets me do a sucessful nandroid for example, but when i reboot into recovery another time the old recovery is back.
When I flash a new rom though, the CWM does get permanently replaced. I flashed a different rom which came with CWM 6.0.2.8 and then I permanently had that version. (same behaviour when I tried to overwrite it with the 6.0.1.2, wouldnt stick).
I even tried just partially restoring the nandroid and leaving boot out, but then phone will get stuck on boot.
Is there any way to permanently flash a recovery to the note without overwriting the whole boot.img? CWM and Rom Manager do not seem to be able. Maybe Heimdall or ODIN? Been so long since I had to use them..
Hope someone knows whats goin on with the recoveries.?!

because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms

nokiamodeln91 said:
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
Click to expand...
Click to collapse
thanks man, yea i got some tools installed that should be able to do a nandroid from running system, was just wondering if there is a way to permanently switch the recovery - it is sometimes booted, right after flash but then its gone - so there must be a way to stop the restore or?
Or are there any custom aokp kernels out there for the n7000? usually they only support TW or CM as far as I saw, or only older versions.

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!

[Q] GT-i9000, how to get old kernel & CWM back?

Hello, and first of all, sorry for being such a noob. I did try searching the forums but found nothing to match my situation.
I rooted my i9000 a while ago and installed a custom kernel with Odin. I'm not sure what that kernel was called, but it came with CWM recovery. Anyways, I then installed the newest CyanogenMod and after that the newest version as it came out. Everything was fine until I decided I wanted KitKat. I went onwards and flashed a new custom ROM, the Mackay ROM. It seems that Mackay came with it's own TWRP-based recovery and the Mackay Kernel. I tried flashing CyanogenMod 11 Nightlies with it but it just returned me to Mackay (factory reset, ofc). I've searched and searched but haven't found a noob-friendly guide on how I could get things the way they were.
So, my question here is that how could I get that old kernel and CWM back onto my phone? I haven't enjoyed using Mackay and want my CM back. My GT-i9505 is currently in repair due to a swollen battery and my trusty GT-i9000 is my daily driver right now, so I'd really appreciate the help. Thanks in advance and sorry if a thread like this already exists.

Recovery and kernel aren't always put together. Just find the recovery thread and read it's instructions. They can be flashed separately.
Sent from my HTC One using xda app-developers app

spitfire2425 said:
Recovery and kernel aren't always put together. Just find the recovery thread and read it's instructions. They can be flashed separately.
Click to expand...
Click to collapse
Thank you, but just to clarify, do you mean the TWRP or the CWM recovery thread?

Santorrr said:
.....So, my question here is that how could I get that old kernel and CWM back onto my phone?....
Click to expand...
Click to collapse
If Mackay ROM doesn't use different formatting than FAT32 or rfs (be sure of that) you can unbrick your i9000 upon my guide:
http://forum.xda-developers.com/showthread.php?t=2444308
It goes step by step from flashing a stock rom with re-partition (PIT file), root, installing cwm recovery and then you can go further with CM installation.
If you've done nandroid backup of your CM you will can restore it as soon as you flash the same rom, kernel and cwm version like when you've created it.

[Q] CWM to TWRP preserving ROM & data

Hello everyone.
Forgive me for asking how to change my recovery from CWM to TWRP once again, but all threads I have read so far don't answer my question, which is:
I would like to keep my PAC-Android with all data and just change CWM 6.0.3.1 to TWRP so that I can try other ROMs such as ViperOne or Revolution HD.
Most threads I've read point to Goo Manager which should be able to install OpenRecoveryScript. That gives me the notification that "no recoveries were found for my device". The next option is to use fastboot. For that, I need to unlock the bootloader of my device, which means that I will [theandroidsoul / htc-one-m7-bootloader-unlock-guide OUTSIDE LINK DELETED]lose all ROM data, apps, private data, just everything[/URL]. Since it's possible to flash TWRP over CWM via Goo Manager, I think it should be possible to do this without deleting all data.
I would appreciate any help.
For those of you who are wondering why I want to lose my PAC-Android:
Speakerphone does not work (works fine in Skype though) and I would like to try it on a custom ROM which is closer to stock.

I hope I understand your query correctly..
1. First of all, since you are initially using CWM. Backup your current PACAndroid using CWM.
2. Flash TWRP using your existing CWM recovery.
a. Here's the flashable zip: https://www.dropbox.com/s/716uhr84madvvjl/TWRP_2.6.3.4_m7.zip
3. Flash any ROM (Viper or ARHD)
If you would like to revert to PACAndroid.
1. Flash CWM recovery using your previously installed TWRP.
2. Restore backup.

double_ofour said:
I hope I understand your query correctly..
1. First of all, since you are initially using CWM. Backup your current PACAndroid using CWM.
2. Flash TWRP using your existing CWM recovery.
a. Here's the flashable zip: (outside-url deleted)
Click to expand...
Click to collapse
hum, didn't know it was that easy. thanks a lot for that. (I already had openrecovery-twrp-2.6.3.4-m7ul.img, I haven't flashed anything but zips yet. What about those .img files?)
double_ofour said:
3. Flash any ROM (Viper or ARHD)
If you would like to revert to PACAndroid.
1. Flash CWM recovery using your previously installed TWRP.
2. Restore backup.
Click to expand...
Click to collapse
So, just to be clear, that means that by flashing TWRP I only change my recovery and I will still be able to boot PAC-Android and I will not lose any data. Then, I can create a TWRP-based backup of my PAC-Android and dispose of all CWM-related stuff?

Everything OK. I flashed TWRP and will stick to it. Backup done.
Thank you a lot!

No problemo amigo!.. Hey hit thanks!..

FYI, you could have flashed the .img file without even rebooting (if you are rooted). The TWRP web site even has instructions--it just requires a single shell command. What happens in the background is very simple--the data in the .img is written to the phone's recovery partition.
This is how I last upgraded TWRP--it just works. (The command is called "dd", but I won't bore you by giving the full instructions.)

[Q] Trouble Downgrading ROMs

Has anyone else tried downgrading from Lollipop 5.1.1 to Kitkat 4.4.4? Because when I tried, and I did a complete wipe of my entire system, there supposedly was an encryption error. I have tried three 4.4.4 ROMs-- CM 11, CARBON ROM, and another CARBOM ROM- branch. They all came up with the same error when booting for the first time: "Error, encryption process has failed. You need to reboot to do a factory reset to [basically be able to use my device again]" This has never happened to me before. I was wondering if this had anything to do with the 5.1.1 Lollipop changes and stuff? I use TWRP 2.8.6 recovery.
Good thing I had a nandroid backup
Thanks for anyone's help
Edit: flashed 'Mokee" 4.4.4 ROM for kicks and giggles, and it came up with the same error like all of the other times

You cannot have done a complete wipe of your entire system. You cannot wipe boot, kernel and bootloader with recovery. The only way to do that is to flash back to stock ROM which replaces everything. To do that go to my CWM thread linked in my signature and make a new CWM SD per item 1a and flash a stock zip from item 6. Follow that with a factory reset with CWM. That takes it back to like it came out of the box and you can start over.
Sent from my BN NookHD+ using XDA Premium HD app

Okay, that's working! Thank you very much! I didn't know that you had a stock Nook HD ROM copy... that is cool. Thanks again for your guidance and for all of your work for the Nook-people everywhere!