Hi
Its a pretty noob question and i might not get the answer.
My phone has problems with DRK and if i flash the EPF1 firmware, the phone will boot but it will freeze during usage every 30 sec for 1 or 2 sec which is very annoying. I found out if i flash a custom kernel the phone will be ok. So i am wondering if someone has the time to tell a noob like me how to build a kernel from EPF1 without any changes from stock kernel but just removing the DRK verification so the phone could operate normally.
I know it has to do with boot.img, but i have not any idea how to extract, remove the DRK verification and re-pack for odin flash.
I don't have any idea of tools that are used, or where the code line of DRK verification actually is.
I just want to use my phone with stock kernel rather than custom kernel.
If someone has already done this please let me know because im looking all over the place.
If not, i would appreciate if someone can teach me how to do it.
Thanks
Related
Hey guys,
I've been working on rooting the new Captivate Glide, and unfortunately my kernel flash with ODIN failed (inexplicably). Now the device is complaining I need to perform an emergency recovery, but of course the device isn't listed in the KIES panel.
Apologies if this is covered elsewhere, but I searched and didn't find anything.
Can anyone explain how KIES works? What is a recovery code? Do I need to get one from Samsung? Is there any other way to force it to perform the recovery on my semi-bricked phone?
Wrong forum ...
There isn't a forum for him yet, so this is the best he could do.
Try going to download mode and flashing again! Try again, until it works, redownload the kernel.
Sent from my SGH-I897 using xda premium
Actually, strangely enough ... I entered 3e recovery (out of desperation) and rebooted, and it cleared the flag, allowing it to boot up normally.
I checked the kernel timestamp (cat /proc/version) and it appears to still be the stock kernel, so the NAND update completely failed.
I still would like to figure out how to force a KIES recovery, but at least for the moment I'm back up and running (till I take my next shot ).
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
studacris said:
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
Click to expand...
Click to collapse
Frustrating. The n900 flashing tool was so excellent (and cross-platform). Wonder why Samsung would release such a piece of junk.
Anyway, I'm back in business now and still working on it.
I'd love to try one of the other kernels, but since I don't have any recovery path (stock kernel / image / firmware), I'm really nervous now.
OK I took the update zip and made a bunch of changes to the updater-script
I removed all references to the recovery and deleted the recoverdirecotry
removed all references to thebootlaoder and boot image
I also removed
the recovery direcories
the bootimage.p
and the signature stuff. ( it would need to be loaded withe the signature toggled off from clockwork)
I also deleted bootloader.blob.
this is the part I am unsure about. i dont think we need to use this if we have clockworkmod BUT I DONT KNOW. please soemone smarter than me look, my google fu is strong but not perfect
my hope is the following.
it will not alter th ebootloader which we already unlocked.
it will not alter the recovery
it will not alter the recover.sh or delete it (required for clockwork mod to stay AND the sdcard swap to stay in place)
it will apply all the patches.
it will probably require a reroot but that could be added into the update.
now why have I not tried it yet.
if I brick it Iam not convinced I can unbricke it
https://dl.dropbox.com/u/5271399/custom Acer_AV041_A100_1.037.00_WW_GEN1.zip
now why have I not tried it yet.
if I brick it Iam not convinced I can unbricke it
Click to expand...
Click to collapse
dragons ahead, do not try this is untested, smart people please review.
feel free to fix alter or improve but let me know so we can reference it here.
reserved (I never needed to do this)
well I decided to give it a try. i fot an error on the verification
or assert (/system/bin/ip) so that file must have been changed.
I guess I will need to flash all the way back to stock
unrooted, first
stock boot laoder etc
Hi guys.. I tried installing jelly bean on this device (i8160p and it's not mine) using odin and a stock 4.1 rom I got from samsung updates(I have no root and I went from a never-touched stock)... All went fine, It's working and has all the features. Except that now its owner is asking me constantly to revert back to the original os, since he did find 4.1.2 very slow. So I went back the same path as in the first place in an attempt to get the original gingerbread : I downloaded a stock 2.3 from the site and then tried flashing it.. All again went smooth, with no problems, until I got stuck on the bootscreen and noticed that there was no way to access recovery(download mode working fine though)... So what I'm left with now is a non-booting gingerbreak or the possibility to stay in jellybean(flashing it still works), I'd prefer if I could go back to GB; I think the problem is that there was some conflict caused by jellybean which will require a reset that I can't of course do since I can't boot into recovery, and I don't see any way to install a custom recovery. So can this be done any other way, I'm afraid I'll break this phone before I'll even come up with anything since this is my first experience with roms and boot on an android;
info : as I mentioned There is no root (for now. I might however get into that from jellybean, but I'd rather not if it's possible) and the model is i8160P . an emphasis on the P here since it's the reason I can't find any custom roms, and all I'm left with is the stuff in here
Edit : got gingerbread back after following what angrybb has suggested
Flash the working JB, and after that root your phone like here: http://forum.xda-developers.com/showthread.php?t=2139263 Reboot to recovery and after that follow the howto: http://forum.xda-developers.com/showthread.php?t=2352064 just in step 8 use original gb firmware.
If you can't get adb root access from stock recovery then flash kernel with cwm, for jb for example this: http://forum.xda-developers.com/showthread.php?t=2304432 or this http://forum.xda-developers.com/showthread.php?t=2171054
After flashing one of those kernel, again follow: http://forum.xda-developers.com/showthread.php?t=2352064 , again in step 8 use gb fw
Ok I'll see
Thanks man I'll try what you suggested as soon a I can...
I have a question though: now I noticed that some people fixed this issue by dowloading some other parts (.pit and something else), but of course I'm unable to find these for the model with the P... Now If someone can please tell me if these files have anything to do with the re-partion option in odin(I heard that it does format everything and not just put things on top of things).... Is using it safe given that I don't mind losing data, or should I stay away from it ?
For angrybb : the phone still shows as i8160p in the about section and has access to network...
Here there is a lot talking about pit files, some tehniques with flashing one fw after another, but with no real explanation why this should be done this way. I dont like doing things like that, i want to understand what i am doing. I still haven found some in depth info about pit files.
Anyway, i upgraded from GB to JB with kies, after that i compared some parts of fw and pit file is not changed. Pit from GB and JB have same md5 in my phone, so it is the exactly same file.
I know that method i suggested is not short and plain easy but it is tested and working.
Thanks
Sorry for the delay... For anyone with same problem just follow what angrybb has suggested, but do not under any circumstances ignore backing-up CSPSA_FS and MODEM_FS if you care about your phone's ability to make calls !
hey, maybe you guys could also help me out? i came from a custom ROM that i was having problems with so I wanted to go to an official ROM instead. Originally i came from a GB stock ROM, then i went straight to CM 10.1 but i didnt have any signal on my phone so i tried flashing original stock 4.1.2, now im stuck on the boot screen and i cant access recovery mode. please help?
P.S. my phone is i8160
Hi there
FIrst of all sorry for the way i'm talking but well im a foreigner and sometimes make mistakes.
To the point. My Note 2 had Ditto DN4 flashed, it was working fine BUT today it just decided not to. It kept rebooting after 4 sec every time so i decided to reflash rom, i did it aaand still the same problem. Ok then, i grabbed this '3 files ROM with PIT file', sorry but i don't know the proper name. Either way, i tried to flash it using odin and thats when things started to go crazy. For some reasons it did not flashed and i was left with just DOWNLOAD MODE! I have no idea why but odin kept saying FAILED after NAND WRITE line. I panicked, flashed it like 45416165415 times but still did not work. After i read a few threads i thought, that i bricked the device BUT i thought what the hell, I'll flash recovery again aaand IT WORKED!
So now, what I'm asking for. Can anyone tell me what are the steps now? What ROM should i flash, if i had MJ5 bootloader? (well i think so, in Ditto thread they say that it works only on MJ5 but i don't really remember whether i did flash it or not). I'll be really really gratefull for any help. I just don't want to ruin it after that recovery flashed.
Unbelievable things happens frequently when using a custom rom or kernel ，especially on the device like N7105.......My pac-ROM got crashed when converting an app to system folder with Ti-backup and reboot，it blacked screen after the first logo screen， and failed enter recovery despite I pulled out battery. When I got crazy and was about to work it out with odin and it entered rec.....I think maybe the single tar.md5 file will help the most......If you a lucky enough
I learned about viper4android and that is what made me start this crusade. I literally spend all of yesterday researching and learning how to root and troubleshooting viper4android and I still can't seem to get it to work.
I rooted my phone and flashed the latest version of TWRP, and installed superSU as well. I initially had a lot of trouble getting the busybox drivers to install but I finally managed to get the latest version installed. The app busybox on rails verifies that the current version of the busybox drivers are installed.
I tried different methods of installing viper4android and I don't have any luck with any. I get the app installed but once I launch the app it asks me which drives I to install, I try to install the super quality drivers but the drivers will not install. I've done a lot of googling of what the problems could be but the "fixes" people suggest dont work. The latest thing I tried was installing SELinux and changing the mode to permissive before trying to install the the drivers but the drivers will still not install.
Any ideas on what to try next? I've granted all these apps permanent permission through superSU. The other thing I've been wanting to do is to remove all the ATT bloatware, but even the app I got for that called "uninstall" will not uninstall all the bloatware which makes me wonder if something is incorrect. However in the bootloader it says my phone is "modified" and "unlocked".
Any help would be appriciated, and I should also mention I have lolipop 5.0.2.
Your problem is the stock kernel. It has write protection enabled.
You need a custom kernel where the write protection is disabled.
Try ElementalX for a start : http://forum.xda-developers.com/showthread.php?t=2705613
or any Sense based kernel.
ckpv5 said:
Your problem is the stock kernel. It has write protection enabled.
You need a custom kernel where the write protection is disabled.
Try ElementalX for a start : http://forum.xda-developers.com/showthread.php?t=2705613
or any Sense based kernel.
Click to expand...
Click to collapse
Do I need to install skydragon before installing elementx? Or will installing elementX sense 5.0.2 version be ok?
Edit: I read on a blog that you need to install skydragon first, but I saw no mention of it in the official elemtnx thread so I ended up installing elementx and it worked by I kept getting hung on the HTC logo on boot, I did a reset and it fixed it with the eleX kernel running. viper works no but it looks like I've lost data. lol. Always something. Now it's time to figure this out.
Sep1911 said:
Do I need to install skydragon before installing elementx? Or will installing elementX sense 5.0.2 version be ok?
Edit: I read on a blog that you need to install skydragon first, but I saw no mention of it in the official elemtnx thread so I ended up installing elementx and it worked by I kept getting hung on the HTC logo on boot, I did a reset and it fixed it with the eleX kernel running. viper works no but it looks like I've lost data. lol. Always something. Now it's time to figure this out.
Click to expand...
Click to collapse
Did I mentioned any ROM ? I said and talked about ElementalX kernel only and your problem has nothing to do with ROM. I didn't ask what ROM that you have, right ? Because you already mentioned it has lollipop 5.0.2
ckpv5 said:
Did I mentioned any ROM ? I said and talked about ElementalX kernel only and your problem has nothing to do with ROM. I didn't ask what ROM that you have, right ? Because you already mentioned it has lollipop 5.0.2
Click to expand...
Click to collapse
Like I said in my edit it's something I read online. I am new to this stuff and at the time I thought you would need a new ROM in order to install a kernel. I was trying to research what I need to do so I dont go in screwing something up and there was a how to blog that specifically mentioned you need a new ROM inorder to install the element X kernel. But that turned out do be flawed information. Anyways I've since read a lot about ROMs, kernels and what not and now have a better understanding of what each piece of the puzzle does.
Anyways, the phone has been kind of unreliable. I had previously used the phone since it's launch before rooting it. I figured it might not be a bad idea to clean everything out hoping that would solve some of the problems. I relocked the phone and did an RUU. I then rooted the phone again and installed elementX. I cant send or receive multimedia texts, GPS does not work at all, and data works on and off. If I reboot the phone chrome will load any page but then after a few mins it stops and sometimes it will load certain websites and at other times it wont load anything at all. I am having good reception of course. Could elementX be the culprit here?
Sep1911 said:
Anyways, the phone has been kind of unreliable. I had previously used the phone since it's launch before rooting it. I figured it might not be a bad idea to clean everything out hoping that would solve some of the problems. I relocked the phone and did an RUU. I then rooted the phone again and installed elementX. I cant send or receive multimedia texts, GPS does not work at all, and data works on and off. If I reboot the phone chrome will load any page but then after a few mins it stops and sometimes it will load certain websites and at other times it wont load anything at all. I am having good reception of course. Could elementX be the culprit here?
Click to expand...
Click to collapse
I searched info on AT&T with ElementalX .. what I've found they worked.
So not sure why it didn't work for you. You tried ElementalX-m8-4.05-Sense, right ?
Your first post was asking about Viper4Android, you need a custom kernel with write protection disabled for it to work.
You can RUU it back and try different kernel and see how it goes.
BTW ... what's the RUU version no. ? 4.28.502.2 ?
ckpv5 said:
I searched info on AT&T with ElementalX .. what I've found they worked.
So not sure why it didn't work for you. You tried ElementalX-m8-4.05-Sense, right ?
Your first post was asking about Viper4Android, you need a custom kernel with write protection disabled for it to work.
You can RUU it back and try different kernel and see how it goes.
BTW ... what's the RUU version no. ? 4.28.502.2 ?
Click to expand...
Click to collapse
Yeah I was initially trying to get V4A to work, and flashing elemental X allowed me to resolve my problems with that, but now I'm having phone functionality problems. And yes, that is the RUU number that I used on my phone. Any kernels you recommend ? Also, as far as reliability and avoiding problems goes do I need to revert back to stock kernel everytime before flashing a new kernel or would clearing the caches and flashing a new kernel over another custom kernel suffice?
Can't help much on Kernel as I don't use custom Kernel.
You need to try some of them and find out which work best for your device.
Maybe asking in AT&T sub-forum will get you better respond.
The main point here is you need write protection disabled kernel to have that viper4android running and also to remove some bloatware that you want to get rid off.
ckpv5 said:
Can't help much on Kernel as I don't use custom Kernel.
You need to try some of them and find out which work best for your device.
Maybe asking in AT&T sub-forum will get you better respond.
The main point here is you need write protection disabled kernel to have that viper4android running and also to remove some bloatware that you want to get rid off.
Click to expand...
Click to collapse
Sorry for digging old thread but i have face the same situation like in the OP . My m8 has root access and ElementEX kernel installed but when i try to install viper4android it was asking to reinstall drivers again again . can you help me to figure this out ??????
I have finally found a method to get the Viper4Android working on HTC M8 (6.0)
1. Download viper4android apk from this Link - http://vipersaudio.com/blog/?page_id=48 (credit - zhuhang ) and install
2.Flash this zip in recovery Link - http://forum.xda-developers.com/showpost.php?p=64855827&postcount=5675 ( credit - Flar2)
3.Install drivers and reboot
4.Go to the system/etc and find the .conf file called "htc_audio_effects.conf" rename it to the "htc_audio_effects.bak" (this made file inactive but keep a backup in case something went wrong ) (Use Solid explorer or Root explorer for this )
4.Restart your device
5.Voila !! Now you have working Viper4Android
My Device Info
ROM - stock sense ( marshmallow)
Kernel - ElementX 7.0.0.11
Bootloader status - Unlocked (btw S-ON)