Hello guys.
Recently I found out that the Bulletproof Kernel disabled the camera app and the flash.
I deleted the necessary files, I flashed the edited zip and the camera app was still broken.
So right now, I am thinking of flashing stock kernel and then re-flashing the edited zip so that the broken camera files don't remain.
Can someone provide tips to what I should do or links to stock kernel?
I am completely new to this and Android entirely. Got my AT&T HTC One 1 week ago.
Thanks in advance.
The scrosler stock rom has stock kernel. Download it find the boot.img inside. Flash with fastboot
gunnyman said:
The scrosler stock rom has stock kernel. Download it find the boot.img inside. Flash with fastboot
Click to expand...
Click to collapse
Do I need to factory reset the phone, or can I flash it with fastboot on the getgo (immediately after I download, deleting nothing on the phone.)
Fastboot flash. Then go to recovery and wipe cache and dalvik
Related
nop
mick1mouse said:
Hi all, thanks for viewing this thread
- I flashed my friend's Bell SGS2 i9100M to CM9 a while back, but now he wants to go back to stock and needs to make use of his warranty because of the battery charging problem even when it's is not plugged in
- I need to flash his phone back to Bell stock firmware UGKG2, but I do not have the necessary firmware (PDA) .tar file to flash back to stock via Odin. I've checked Intratech's thread but multiupload is down so I cannot download the .tar files
- However, I have the stock ROM in .zip file, the kernel, modem and CSC in .tar file
- Unfortunately, I did not make the nandroid backup before flashing CM9 on his phone
- I currently do not have his phone with me, but he will be coming over in a few hours
So my questions are:
1) Is it okay to just flash the stock ROM .zip file via recovery from CM9? (After the standard procedures of wiping system, data, cache, etc.)
2) Will the CM9 kernel recovery flash the stock ROM .zip file? I think it might give some e: (some sdcard) error, I'm guessing... If so, will flashing a custom Gingerbread kernel then flashing the stock ROM .zip file via CWM work?
3) If 1 & 2 don't work, does this mean I absolutely have to flash back to stock via Odin?
I've also got an usb jig prepared
Thanks in advance
Click to expand...
Click to collapse
Hey,
like u said, the .zip includes .tar files.
.tar files always must flashed via odin!
Only way to to it via phone is using odin on phone, but I'm not up to date how is the status and if it's really working.
So to be sure:
1) make a full wipe (like u said above with formatting system, cache etc.)
2) Put files in Odin and flash
3) Flash cf-root or kernel to get CWM back (if u want)
CHEERS
nop
mick1mouse said:
the .zip file does not have the .tar files, it is CWM flashable; it has the META-INF folder, system folder, zimage, etc.
Click to expand...
Click to collapse
Oh ok. Didn't read carefully, sorry.
So dunno where u got it from, but if it is a source u trust, it should work.
... should be like flashin CM or any custom Rom
Much success!
CHEERS
nop
Every ROM zip file I attempt to flash via CWM or TWRP doesnt work. I was on stock ICS (4.0.4) which I flashed using Odin. Every JB rom, stock or custom I attempt to flash with a recovery freezes either at boot up or first screen of initial setup. No errors are given on actual flash, it always looks good. . I wiped everything I can wipe, which is everything but emmc I think. What could be the problem? I have now flashed official JB through Odin twice with no issues.
Do you check that the ROM is downloaded properly by checking the md5 hash?
EVOO2 said:
Every ROM zip file I attempt to flash via CWM or TWRP doesnt work. I was on stock ICS (4.0.4) which I flashed using Odin. Every JB rom, stock or custom I attempt to flash with a recovery freezes either at boot up or first screen of initial setup. No errors are given on actual flash, it always looks good. . I wiped everything I can wipe, which is everything but emmc I think. What could be the problem? I have now flashed official JB through Odin twice with no issues.
Click to expand...
Click to collapse
Try flashing a new recovery using odin then try to flash the rom in recovery afterwards.
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
Try flashing a new recovery using odin then try to flash the rom in recovery afterwards.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ive flashed twrp 2.5 twice through odin and then tried to flash a rom with no improvement. Im really stumped 'cause flashing roms with odin works fine everytime, so it would seem nothings physically wrong with my device. Should I try a different recovery program? Using cwm and twrp give the same result, so Im skeptical a third recovery would be any different.
cheers
EVOO2 said:
Ive flashed twrp 2.5 twice through odin and then tried to flash a rom with no improvement. Im really stumped 'cause flashing roms with odin works fine everytime, so it would seem nothings physically wrong with my device. Should I try a different recovery program? Using cwm and twrp give the same result, so Im skeptical a third recovery would be any different.
cheers
Click to expand...
Click to collapse
Only thing i can think of is look at the file format that youre trying to flash.
Is it zip? tar?
I may be wrong but cwm only works for .zip files from my experience. not .tar md5 etc.
why do you need to flash it via cwm? if its flashing through odin whats the problem?
It sounds like what ^^^^ is saying. Recovery flashes zip files and Odin flashes tar files. Don't confuse the zip files your pc uses to download the files with these.
When using odin I have to use ROM s which are .tar, so this basically limits me to stock ROMS. The custom ROMS are .zip which I can only flash with a custom recovery like twrp or cwm. I'd obviously like to flash the custom ROMS which are .zip , however it isn't working for me as I mentioned in the opening post . Not sure how to fix this problem .
EVOO2 said:
When using odin I have to use ROM s which are .tar, so this basically limits me to stock ROMS. The custom ROMS are .zip which I can only flash with a custom recovery like twrp or cwm. I'd obviously like to flash the custom ROMS which are .zip , however it isn't working for me as I mentioned in the opening post . Not sure how to fix this problem .
Click to expand...
Click to collapse
extraxt the rom that your saying is .zip. it "should" extract a file that will be something odin will recognize
dweeezy said:
extraxt the rom that your saying is .zip. it "should" extract a file that will be something odin will recognize
Click to expand...
Click to collapse
Good idea. In a recovery zip file will be a couple of folders. One of them will have a tar file you can flash in the phone or pda a lot in Odin.
Thanks for the suggestion but I had no luck . I have tried extracting padawan JB and a debloated stock JB rom and they extract many files, folders, apks but no tar I could locate. Also I am not sure even if there was a tar i could use if it would be safe to use. If all this was good, it would still be a cumbersome workaround and wouldnt fix my problem of not being able to get a ROM installed via recovery to work.If I have no choice I'll use odin to flash custom ROMs (if there is a way) but Id rather get it to work with recovery.
EVOO2 said:
Thanks for the suggestion but I had no luck . I have tried extracting padawan JB and a debloated stock JB rom and they extract many files, folders, apks but no tar I could locate. Also I am not sure even if there was a tar i could use if it would be safe to use. If all this was good, it would still be a cumbersome workaround and wouldnt fix my problem of not being able to get a ROM installed via recovery to work.If I have no choice I'll use odin to flash custom ROMs (if there is a way) but Id rather get it to work with recovery.
Click to expand...
Click to collapse
If you're flashing between TW based to AOPS, or pretty much from a rom to a completely different rom, you will need to WIPE your data too, or better, do a complete wipe (factory reset). I had this issue when moving from Stock TW-based rom to Padawan JB rom. I did a factory reset (complete wipe) and it booted fine. But then again, I'm used to TW so I flashed that back.
fbauto1 said:
If you're flashing between TW based to AOPS, or pretty much from a rom to a completely different rom, you will need to WIPE your data too, or better, do a complete wipe (factory reset). I had this issue when moving from Stock TW-based rom to Padawan JB rom. I did a factory reset (complete wipe) and it booted fine. But then again, I'm used to TW so I flashed that back.
Click to expand...
Click to collapse
I've wiped everything I can wipe between flashes (includes factory reset), many times trying both TWRP and CWM for flashing and wiping with no luck unfortunately. The wiping doesnt seem to help, different custom recoveries don't help, so I'm stumped as to what the problem could be.
EVOO2 said:
I've wiped everything I can wipe between flashes (includes factory reset), many times trying both TWRP and CWM for flashing and wiping with no luck unfortunately. The wiping doesnt seem to help, different custom recoveries don't help, so I'm stumped as to what the problem could be.
Click to expand...
Click to collapse
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
dweeezy said:
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
Click to expand...
Click to collapse
Ive tried padawan JB, debloated rooted canadian JB rom, and debloated ATT rom.
dweeezy said:
What roms are you trying to flash? Sometimes ive seen where you must rename them or do specific things.
Click to expand...
Click to collapse
Ive tried padawan JB, debloated rooted canadian JB rom, and debloated ATT rom.
OP, are you still having this issue? Were you able to resolve it?
I have the exact same issue as you. Exactly the same.
513263337 said:
OP, are you still having this issue? Were you able to resolve it?
I have the exact same issue as you. Exactly the same.
Click to expand...
Click to collapse
Me too. Every rom freezes during the app optimization screen...usually at about 3/4th the way through. What's going on???
*edit* Tried to restore factory w/Odin. I'm bricked now. Time for some JTAG love.
Exactly the same issue here.
Every jelly bean ROM, 4.1 or 4.2, stock or custom, as long as I install them via recovery, it either doesn't boot up or gets stuck on the first screen.
If I use ODIN to install the stock ROM, it works fine.
Driving me nuts...
Just throwing suggestions out there but try sideloading the rom and see if itll install that way? Also are you odin flashing recovery? Maybe try to load twrp through goomanager and see if maybe recovery is corrupted?
Sent from my SAMSUNG-SGH-I717 using xda premium
Hey, I downloaded the CM 10.1 ROM uploaded by percy_g2. Then I downloaded the new kernel uploaded by him to remove OC and then finally downloaded Gapps for CM 10.1. My phone is rooted and the bootloader is unlocked as well. I have installed CWM Recovery also. Well, I know how to flash the ROMS but want to ask that:-
1. I have two "boot.img". One in the zip file of the ROM and second is the one which percy_g2 uploaded as "Kernel to remove OC". Which one to flash and when?
2. What is the order in which I need to flash things and clear cache?
Please help!
golu23 said:
Hey, I downloaded the CM 10.1 ROM uploaded by percy_g2. Then I downloaded the new kernel uploaded by him to remove OC and then finally downloaded Gapps for CM 10.1. My phone is rooted and the bootloader is unlocked as well. I have installed CWM Recovery also. Well, I know how to flash the ROMS but want to ask that:-
1. I have two "boot.img". One in the zip file of the ROM and second is the one which percy_g2 uploaded as "Kernel to remove OC". Which one to flash and when?
2. What is the order in which I need to flash things and clear cache?
Please help!
Click to expand...
Click to collapse
1)Extract the boot.img from the zip of the rom file and flash it via flashtool.
2)Enter in cwm wipe personal data, cache and dalvik cahe.
3)Install the rom and gapps.
4)|Reboot and set up everything. Now turn off the phone and flash via flashtool the boot.img without oc.
There is another method but don't sure that will work. Extract the boot.img from the file without the oc and place it on the one of the rom. Don't extract anything, just replace it with drag n drop from the file without the oc to the one with the rom. After that do steps 1-2-3, reboot and you are done.
DaRk-L0rD said:
1)Extract the boot.img from the zip of the rom file and flash it via flashtool.
2)Enter in cwm wipe personal data, cache and dalvik cahe.
3)Install the rom and gapps.
4)|Reboot and set up everything. Now turn off the phone and flash via flashtool the boot.img without oc.
There is another method but don't sure that will work. Extract the boot.img from the file without the oc and place it on the one of the rom. Don't extract anything, just replace it with drag n drop from the file without the oc to the on with the rom.
Click to expand...
Click to collapse
Thank You!
golu23 said:
Thank You!
Click to expand...
Click to collapse
You're welcome mate. Hope works.
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
tcornelis said:
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
Click to expand...
Click to collapse
You're definitely using a TWRP recovery made for JB hboot? @GtrCraft, did you put the right boot.img inside the zip?
Also, you can try flashing a custom JB kernel of your choice.
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
tcornelis said:
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
Click to expand...
Click to collapse
For booting that ROM a CM kernel is needed. As you have installed one (if it works like you said), you need to install a JB Sense kernel (just pick one from Original Android Development section). Then reinstall SuperSense and you should be fine.
I'll give that a go and let you know
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
tcornelis said:
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
Click to expand...
Click to collapse
That's a CM kernel as well. I told you to use a Sense kernel. Use this one for example: http://forum.xda-developers.com/showthread.php?t=2483489
and your recovery should work again as expected. Btw, which recovery did you install? Please give the link.
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
tcornelis said:
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
Click to expand...
Click to collapse
That one's made for ICS, if I recall correctly... Don't use it. Use this one instead: http://forum.xda-developers.com/showthread.php?t=2099513 But be sure to use a JB version.
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
tcornelis said:
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
Click to expand...
Click to collapse
No, it's not. You can however choose the kernel yourself as I said... But keep in mind that it has to be a JB Sense kernel (just read the OP of the kernel thread carefully, then you'll know). For recoveries, keep this in mind.
No Title Here
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
GtrCraft said:
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
Click to expand...
Click to collapse
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect :good:
Hello!
Sorry if this thread looks repetitive, but I'm new on this kind of thing and just want to make sure all goes right with my Xperia U! Tomorrow will complete one week of reading, researching and learning about ROMs, flashing, kernel, recovery, etc.
Can someone please just confirm if my steps are correct?
First of all, I have just unlocked the bootloader. Tryied to root too, but got some problems (ST25a, B154 stock kernel x.x) and later found root wasn't necessary as custom kernels already comes pre-rooted.
I want to use this Stock ROM:
http://forum.xda-developers.com/xperia-u/u-development/rom-stock-jellybean-4-1-2-v6-t2284394
Wich tells me I need to flash this kernel:
http://forum.xda-developers.com/xperia-u/u-development/kernel-experimental-v12-t2326515
Here are the steps I think I have to do:
- Move both .zips (kernel and ROM) to SD card
- On PC, extract the boot.img from KERNEL .zip file
- Flash boot.img with flashtool
- Reboot in CWM recovery mode (provided by the boot.img, i guess)
- Full wipe (cache, data, dalvik-cache)
- Flash KERNEL .zip via CWM
- Flash ROM .zip via CWM
- Reboot
Is this right? I really got confused when I saw every .zip has a boot.img on it x.x
Yes,Evert step is correct...But when you boot the phone in recovery,you don't need to flash the kernel zip...You already flashed it,don't need to do it again!
ilysomma said:
Yes,Evert step is correct...But when you boot the phone in recovery,you don't need to flash the kernel zip...You already flashed it,don't need to do it again!
Click to expand...
Click to collapse
Really? I don't understand exactly what each files in that .zip do, but, boot.img ins't just a way to boot? The kernel will be installed with just that? What about the other files in that .zip? Is it for the case of already having recovery mode?
PS: sorry about my bad english
Edit: Do I have to move the .zip file to SD-card without the boot.img? Or I just leave it there?
Ok, this is it. I'll try this proccess today.