Develop Bugs

[Q] Q about what to do after downgrade?

Hi all.
I was talking to someone yesterday, that also got a DHD like me, and he show me a lot of this that his phone could, and he told me about this website and talked about that i had to downgrade my phone to update it again to something else that i cant remember.
But anyways i found a guide on the net how to downgrade it to 1.32.405.6, and i succes with that, but now is the Q how do i update to something else? Eks this http://forum.xda-developers.com/showthread.php?t=1020637 can i put this kernel to the sd card and its updatet ?

well welcome to the ROOTed WORLD!, its beautiful here!
anyway, make sure you have ClockworkMod recovery. If you dont, the simplest way is to download ROM Manager and Flash the recovery (first option).
After that go into recovery (vol down + power button) and do a backup (also known as nandroid) so if anything goes bad, you can restore your ROM.
After that you can flash certain things, ROMs, Kernels, Mods, etc...
I personally havent flashed any Kernels over my ROMs kernel, because i believe that the Kernel for my ROM is the perfect one, so i dont know what will happen exactly if you flash the Kernel to your ROM.
But dont worry, if anything goes bad, you can flash a ROM/Kernel back to your phone (or restore your nandroid) and it will be fine (unless your phone is bricked! - in that can, im sorry!)
EDIT: That kernel is for CM7 ROMs only!!!!, so if you want that kernel, make sure you flash CM7 first!

Bricked: No Recovery Kernel

Hi guys,
A small problem here: I have no recovery/kernel anymore.
When booting up the phone, it starts directly in Download Mode, specifying: "Reason: No Kernel".
Moreover, if I want to boot in recovery mode, it goes into an infinite loop, listing the message:
Booting Android recovery
No recovery kernel ##
Booting Android recovery
No recovery kernel ##
Booting Android recovery
No recovery kernel ##
...
This happens after trying to flash (via CWM) a package which was wrongly created, and everything was erased. That is, all partions formatted.
I tried Odin-ing CWM again, but though without any error, CWM still doesn't start.
Does anybody know this problem (or solution)? Should I provide any additional info?
Any idea will be highly appreciated.

You could first try using Odin to flash a stock rom, seeing as you're missing a kernel which is part of android. Perhaps then flashing CWM will result in a working copy?
As a hail-mary In you could also give the oneclick ICS-leak a try, as it contains pretty much everything, a recovery and android.
If succesful, you should be able to Odin back CWM and restore any backups. You will lose everything presently on the phone, though.
Sent from my SAMSUNG-SGH-I927R using xda app-developers app

Using the leaked 4.0.4 update exe, you should be able to restore your phone, as it includes a kernel as well. Alternatively, if you're not interested in ICS, you could flash one of the gingerbread kernels, like this one, which should let you flash a working CWM and then the rom you wanted.

I am interested in ICS. Though, the first option didn't work either. I had to go for ardatdat's boot, which put by the CWM in order to flash ICS. Thanks a lot, much appreciated!

I'm glad something worked at least we got a lesson if it should happen again, thanks for sharing that something worked
I927UCLG9 Stock ICS 4.0.4
keyboard back light fix
super user 3.1.3 ARM Signed
CWMR Touch 6.0.0.1

need some moderating in these forums... this post dont belong here...

indeed. Reported the OP post, should be moved
For everyone:
DEVELOPMENT IS FOR DEVELOPMENT AND DEVELOPMENT ONLY! Questions and User Problems should go in General.
Thanks.

[Q] AT&T S3 (Flashed via s3 toolkit) question on roms

I have a AT&T samsung galaxy S3 rooted by using the samsung galaxy toolkit http://forum.xda-developers.com/showthread.php?t=1746665
I'm interested in flashing the following CM10 Nightly rom http://forum.xda-developers.com/showthread.php?t=1778270 to my phone but have a few questions before I proceed.
1) What precautions should I take before flashing a custom rom? I understand I first need to make a nandoid backup (which I have done) and verify that I have the correct rom for my specific phone model that I will be flashing to. If I were to choose the CM10 Nightly rom, the link from the post goes to http://get.cm/?device=d2att which appears to be correct for my AT&T Samsung Galaxy S3 SGH-1747.
2) Since I flashed with the samsung galaxy toolkit, it flashed the following recovery "CWM-Based Recovery v5.5.0.4 - Do I need to use a different recovery in order to use the CM10 Nightly roms or is this one compatible? If not, how do I go about changing to another recovery?
3) What is the steps for flashing properly? Would I need to update kernel or model or just simply download rom, save to SD card, boot to recovery, then flash the rom in zip form?
I appreciate any your responses in advance. I tend to over analyze and I feel i've read enough about the process of flashing custom roms but I want to be certain. Thank you!

It looks like you got all you ducks in a row, on behalf of the community thanks for being a smart user :good:.
1) You nailed it....make absolutely certain you are downloading the correct software for your device, flashing an incompatible ROM can leave you with a really sexy, expensive paper weight. The d2att identifier is unique to the AT&T variant of the SG3 (i747). Before you flash any new rom or kernel (or anything else for that matter in my opinion) make a nandroid or equivalent backup from your recovery. I do this even for the smallest mod, tweak, theme whatever if for nothing else incase i dont like it it an easy undo 'button'. Besides that i like to keep a fairly recent backup on something other than my phone.
2) For all intensive purposes that version of CWM will work, atleast currently. I would recommend you update it however as that version is several builds behind and there are sometimes updates in the more current ROM builds that may not play nice with older recoveries. The easiest way to do this is download Clockwork Rom Manager from the play store, on the main app screen at the very top is the option to install the latest recovery. It will download, preferably on wifi to minimize downloading errors as much as possible, and then install automatically. There is also atleast one other alternative recovery that i know of, TWRP, which is worth checking out in my opinion. Just keep in mind the backups from the different recoveries are NOT interchangeable.
3) It always best to follow any and all directions in the OP of whatever ROM you are installing as most differ. The generally accepted order for flashing goes something like this although everyone will have an opinion on this i'm sure. ROM > Gapps (if required by the rom) > Reboot > Kernel > Reboot. If you are really concerned you can always just flash one at a time allowing a full reboot in between each flash, personally i think this is overkill but thats just my opinion.
One last personal suggestion, I always keep a copy of my rom, kernel, and any required supporting software on my external sd just in case. It comes in handy if for some reason you try something that doesn't work out the way you had hoped and you are away from a computer and your phone is unable to boot into android. Some would argue that a nandroid makes this unnecessary but with 32 gigs in my current setup its not like im hurting for space. Hope this helps to clarify some things for you, good luck!

dntesinfrno, Thank you very much for your reply and kind words
A lot of the information has been posted on the boards but it can be a little confusing and too much information at once.
You mentioned that I can simply use Rom Manager then click "Flash ClockworkMod Recovery", are there any reports of there being problems in using rom manager to flash the recovery or is the S3 fully supported?
As for the kernel flashing.. I'm really only interested in flashing custom roms (CM10), is it necessary to flash the kernel as well when flashing custom roms? I didn't see anything on the other thread stating anything about flashing kernels so i'm guessing it's not needed?
I'm for sure going to take your recommendation and make a backup of current rom and kernel. Would you recommend Rom Manager to backup the current rom? I see an option that says "Backup current rom" in the application. How do you go about backing those up?
Thank you again! :fingers-crossed:

since I have the cwm-based recovery v5.5.0.4 i'm wondering if I were to use rom manager and flash the latest clockworkmod recovery, would it actually stick after the reboot?

found the following thread here and it looked almost identical to mine: http://forum.xda-developers.com/showthread.php?t=1801534&highlight=cwm-based+recovery
Ended up using rom manager to flash clockworkmod and after rebooting multiple times and booting into recovery, the official clockworkmod recovery is installed. (showing "ClockworkMod 6.0.1.2" now)
As for backing up kernel and everything else, will rom manager do that as well?
Thank you

Embarrassingly noob question..

I am embarrassed to have to ask this since I've had android phones for 3 years now.
But to install a new custom recovery... Is it really as easy as just flashing it with my current recovery? I ask of course because I am trying to get kitkat and I was getting error 7. Which, after research led me to believe I need to update my recovery. I've used Download mode before, but I don't know if that is necessary. I've never messed with it before because if it ain't broke, don't fix it kind of deal. Any instructions and/or recovery recommendations for me?

Yes, it is that easy. You can install zips for the newest versions of CWM, TWRP, or PHILZ from your current recovery.
Of course you may not be able to restore your old backups. But you can flash back to the old recovery to restore these too.
Most people are changing to different recoveries because of recent changes in Android that makes it trickier to flash the newer Roms.
I personally switched from TWRP to Philz. It is CWM based, but will also restore TWRP backups. Phil is very receptive to questions and had made his recovery available on a lot of devices, more being added every day.

Thank you, it's much appreciated! I am looking into Philz now!

[recovery]TWRP 2.8.0.0 v2 for e98x[TEMP CLOSED]

Temporarily forget it. Link removed.
TWRP 2.8 v2 for e980.
Fixed auto-loki support.(But there will be a weird floating loki option, i will fix the position of it when i have time)
Should be no longer have secure boot issue after flashing kernel.
Reboot-into-recovery-loop bug still presents, always prepare madmack's twrp for e986 hack, in case boot-loop happens!
When recovery-loop happens, please flash madmack's hacked TWRP 2.6 for e986(please see post #23), then reboot into madmack recovery(you can install back my recovery in this step), reboot system, the recovery-loop will stop.
I am not able to solve this bug, as with Philz touch also has this bug and never solved.
**This recovery will only cause recovery-loop. All other bootloop will not be cause by this recovery!**
**I held no responsibility for any damage due to the use of this recovery.**
Features:
1)Full nandroid backup is much faster on TWRP than on CWM / PHILIPS TOUCH.
2)Ability to format any partition into F2FS/EXFAT/FAT/EXT2/EXT3/EXT4, and read/write all these format partitions.(don't use F2FS format until a compatible kernel and rom come out.)(I am using stock at this moment, still love stock, but failed to make stock rom fully compatible with F2FS, what a pity!)
Download it from attachment.
Backup anythings important.
Flash through recovery.
Enjoy!
Wing
P.S. I am **not** a developer, so I **may not be able to** fix any bugs if you encounter!
P.S. Again, i am using phone network at home, which have data usage limit, so the source will be uploaded when i can use wifi.
P.S.I am not programmer, I used very long time to understand what is what, if you think this recovery is useful, consider make a donation!

Wow, thanks! Working great!

Wow .thank you so much .already flashed waiting for new build to test .will report back .thanks again
---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------
Keep this thread alive

Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing

Great job man .thanks

mukwing said:
Actually, the thing i actually want/try to do is to add F2FS support to CM kernel and whole CM rom.
Since i am not a developer, i use a lot of time try to figure out what need to patch and failed.
I used too much time and can't understand what make the compile fail and give up.
Then I do the next thing I want to do: compile a fully working twrp to replace the easily boot-loop PhilZ Touch recovery.
This TWRP is actually a side product of my failure attempt.
(ha, i still don't have right to post external links, so i will put the TWRP e980 compile method and source up later)
Wing
Click to expand...
Click to collapse
how did u build i could help i have linux on virtual mmachine on windows 8.1

bountyman334 said:
how did u build i could help i have linux on virtual mmachine on windows 8.1
Click to expand...
Click to collapse
Attached is the patch file for cm kernel to make it support F2FS.(I forget where to get)
Not all codes can be patched sucessfully, some I need to modify the kernel sources by hand.
It seems some codes will lead to compile error, but i am not programmer, I don't know how to adjust.
I am using up-to-date CM sources, without modification, i can compile unofficial cm build successfully for my own test.
Wing

Forget this patch. I think this patch might be outdated.
I am trying to investigate the commits about F2FS in Nexus 5 CM F2FS kernel sources.
Will try to merge these commits to see if it can compile.
If I sucessfully getting a F2FS supported CM kernel, will try to make a F2FS supported TWRP.
Making CM rom to support F2FS seems to be easy, there exists some tools ready to do it.
Wing

Thank you so much for you hard work

I finally learned how to correctly patch kernel commits!
Good news. A F2FS suppported kernel has been successfully compiled!
(need testing, but need to compile F2FS suppported TWRP and ROM before i can test.)
Next step, F2FS suppported TWRP.
Wing

I can't find resources of how to modify TWRP 2.8.0.0 to support F2FS for our device.
But the modified KT-TWRP from the following
http://forum.xda-developers.com/showthread.php?t=2778248
I can compile it successfully against e980 CM sources.
So, I get F2FS supported TW-TWRP working on my phone.
I still haven't try format partition to F2FS.
Will report if it works later.
I don't want to be another failure, used me sooooo much time to research.
Wing

version?
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.

mukuluppal said:
It says in the flash screen that it is madmack's 2.6.1.0 only.
I am confused..
Edit - but the recovery header says it is 2.8.0.0
XD
Edit 2 - It has messed up with the phone. Not able to get into the ROM. only boots into the recovery. Tried philz recovery and then tried to boot again but it isn't working anymore.
Click to expand...
Click to collapse
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Again, i am not programmer. I will try to find out reason to see if i can fix it.
Wing

mukwing said:
It say madmack's 2.6.1.0 because i use madmack's old zip and replaced the recovery.
If in the boot-into-recovery loop, install philz recovery, then install TWRP again should fix it?
BTW, is it caused by wiping of /data?
Wing
Click to expand...
Click to collapse
Yeah i tried that and it didn't work.
So i tried a bunch of my old recoveries and the twrp e986 hacked one worked.
Now i can see ext card too in twrp. But that's not your recovery. It's old one.
No it didn't happen coz of wipe data.. After flashing it,the recovery boot started.

Failed to find out why has this bug on this recovery. Sorry.
Btw, testing of F2FS gave me soft brick of my phone. When I returned to stock, I surely love the smoothness of original stock lg 4.1.2. So I may stay with stock for a while.
When I feel too boring with stock again, I will return to cm and try compiling something to have fun again.

recovery updated.
please test!
Wing

If anyone tests this out let me know if the Loki works because last time I tried it it made my phone soft brick. It was an easy fix to unbrick it but I'm hoping it doesn't do that anymore.

mukwing said:
recovery updated.
please test!
Wing
Click to expand...
Click to collapse
So..
If you go to install,there is a "Loki support" floating checkbox that won't go away...
If you try to Enable MTP and actually try to copy something to internal SD card, recovery reboots and copy fails (I noticed that you can still delete stuff).
It also got me a bootloop when flashing a rom, I had to recover through download mode and a KDZ...
Bunch of issues that are pretty noticeable, OP,are you even testing this on your phone before sending it out risking other phones?

The floating Loki doesn't affect the usage much.
And the boot loop have been mentioned using madmack 2.6 e986 to solved.
Sorry, will never share anything again.

Jeez....
2SHAYNEZ