I had installed the kernel and CWM yesterday and it was working fine. I had updated, and was able to make backups to sdcard. This morning I tried to install the newest kernel from koush and I'm in a samsung bootloop. If I boot to recovery it takes me to the older version of CWM that can't read/write to sdcard. So basically I can't get to the nandroid backup I made yesterday. Also when in recovery I can't use adb to get into the phone at all to move the backups from sdcard to data so they can be used. Am I completely hosed here?
stanrc said:
I had installed the kernel and CWM yesterday and it was working fine. I had updated, and was able to make backups to sdcard. This morning I tried to install the newest kernel from koush and I'm in a samsung bootloop. If I boot to recovery it takes me to the older version of CWM that can't read/write to sdcard. So basically I can't get to the nandroid backup I made yesterday. Also when in recovery I can't use adb to get into the phone at all to move the backups from sdcard to data so they can be used. Am I completely hosed here?
Click to expand...
Click to collapse
Try flashing the stock kernel back. See what happens.
Edit - you did .tar that zImage2 for use with Odin right? You didn't just add a .tar extension?
It was just the zImage2 posted by koush, no file extension, and I used redband_ua to do it. I flashed the stock kernel and am downloading the stock /system to flash that as well.
stanrc said:
It was just the zImage2 posted by koush, no file extension, and I used redband_ua to do it. I flashed the stock kernel and am downloading the stock /system to flash that as well.
Click to expand...
Click to collapse
Ah, gotcha.. Haven't bothered with redbend yet.. Anyway, flash the stock kernel first, before /system.. No need to kamikaze that stuff.. one at a time, nice and slow..
I'm wondering if having an out of sync /bml7 and /bml8 is causing this. Angel's upload (~9.8MB or so) had both partitions.. Koush's new kernel I assume just touches /bml7..
if stock kernel DOESN"T work, try flashing the original "working" CWM kernel back.. not the newest one, but the second newest.
Ok boots now, trying to restore a backup now.
Ok its back up now. Thanks. I was really panicking when adb wouldn't work. I thought it was supposed to work in recovery?
stanrc said:
Ok its back up now. Thanks. I was really panicking when adb wouldn't work. I thought it was supposed to work in recovery?
Click to expand...
Click to collapse
It does, I'm doing it right now.. Something must've been up on your end.
Related
OK, I know this has been asked before but I can't actually find a working answer! Installed rom manager last night, didn't work I assume because of 3e recovery. Installed latest FW for SII and loaded CF-Root - still didn't work. Re-flashed (I assume that was OK?) with speedmod - still doesn't work. Is there a working solution to get rom manager working?
Sorry, I'm not an expert so it may well have been answered but I didn't understand the solution
IIRC Rom Manager needs CWM recovery.
So flash a kernel that contains the CWM recovery instead of the original (3e) one.
Like, for example, CF-Root (CF-Root doesn't work with Rom manager), my one (v sig v - but not sure if it works, never tried, would be cool if you could and tell me ) or the CWM kernel from the CWM-initramfs-template thread in the dev section.
//EDIT
a few corrections
It does indeed need CWM recovery. Installed CF-Root but as you say, it doesn't work. Also tried speedmod but that doesn't seem to do much either!
Now, if I flash with yours for example, can I literally just flash over what I have now? I did that this morning with CF->Speedmod and my phone has already crashed once. Or is there a correct way to re-flash, such as putting the phone back to stock first?
I **think** its working as your kernel allowed me to turn off image verification and so ROM Managers update.zip seemed to install OK. Backup started anyway.
So.... the phone rebooted after backup by itself, is that normal? And, I assumed the backup would be on the SD card - it appears to be on the phone though under \clockworkmod\backup\ - is that right? Is that everything on the phone backed up (apps, settings, layout)? Can I restore that if I trash the phone completely?
Edit: OK, don't think its worked. When I reboot its still trying to install update.zip and failing :-(
Yeah like other posters have said, you'll need to flash a CWM kernel. chainfires kernels have CWM so I'd guess you're not actually flashing the kernel..
m4rshall said:
Yeah like other posters have said, you'll need to flash a CWM kernel. chainfires kernels have CWM so I'd guess you're not actually flashing the kernel..
Click to expand...
Click to collapse
Its just finding a good one that works well!
rendez2k said:
Its just finding a good one that works well!
Click to expand...
Click to collapse
Any works>> well start with the last one if not working you are doing something wrong.
jje
JJEgan said:
Any works>> well start with the last one if not working you are doing something wrong.
jje
Click to expand...
Click to collapse
OK, put Hellcats kernel back on, didn't try and install any updates from Rom Manager and just got it to download a new rom. Rebooted phone and it instantly fails to install. Select install from zip, turn of verification and it worked!
Now, I see some features such as BLN support have now gone, I assume because the rom updated the kernel - can I now reflash the Hellcats kernal or could that screw the rom up?
To use rom manager flash this kernel
As it wont work with chainfires tweaked clockworkmod recovery in CF-root.
BLN is a kernel thing, if you want BLN use a BLN kernel, for example Ninphetamine (mysig) and use the CWM manager app you can find if you search the forum.
ROM manager will ONLY work with codeworx's kernel and that doesnt have BLN etc.
Thanks veyka - I'm a bit confused what Rom Manager is actually is doing (or needs to be able to do) now. Is it just trying to install a modified CWM?
As I say, using Hellcats kernel which has CWM built in already, I was able to use Rom Manager to download a new rom then manually install with CWM. So I'm not sure what Rom Manager 'working' would actually add to that?
And as per my question a few posts up, now I have a new rom installed (TK-Rom for now), can I happily change the kernel and have no issues?
Im currently using Speedmod kernel which is great for ICS but only problem is it uses the phones internal memory for backups and such which is a pain since if anything happens I want it to be on the SD Card in case so right now im moving the backups all the time
I am trying to flash a different recovery but I cant seem to get it to work. I tried via rom manager which says its done it but when I boot in recovery its the old one.
I tried ROM Toolbox Pro v4.6.1 and flashing the zip for recovery but that failed as well
I tried flashing the touch recovery from here
http://download.clockworkmod.com/recoveries/
and here
http://www.clockworkmod.com/rommanager
via the current recovery
but it didnt work gets stuck at
am I missing anything? I dont mind doing it via odin if you can point me to the right files and just give a basic info such as select pda and then the file etc
replacing stock recovery with ClockworkMod recovery
i think siyah or neak has tht option were u get to store on sd card....never felt this important thou
rocky23 said:
i think siyah or neak has tht option were u get to store on sd card....never felt this important thou
Click to expand...
Click to collapse
All other kernels by default will use the SD card for backups and also as default for when you want to flash a zip.
All my rom ZIPs and backups are stored on my SD in case my phone gets broken at least I have my data and backups.
Wont do me any good to have them on the phone if it is non functional
Recovery is part of the Kernel partition on the GSII, flashing other recoveries will at best be a temporary solution since they will be overwritten on the next boot when the kernel reloads it's default recovery. In order to get what you want you would have to flash a kernel with the appropriate support.
thracemerin said:
Recovery is part of the Kernel partition on the GSII, flashing other recoveries will at best be a temporary solution since they will be overwritten on the next boot when the kernel reloads it's default recovery. In order to get what you want you would have to flash a kernel with the appropriate support.
Click to expand...
Click to collapse
Is there any way for me to take the kernal files and change the recovery image in it and flash it via odin or something?
How do i go from a cm9 rom to a gingerbread rom with working camera, fm radio and bluetooth?
Flash ROM
heat361 said:
How do i go from a cm9 rom to a gingerbread rom with working camera, fm radio and bluetooth?
Click to expand...
Click to collapse
Basically, you flash a zip the same way you put on CM9. Find the ROM you want, make sure you are running the right kernal, usually entropy's, put the new ROM's zip file on your SD card, boot into clockwork recovery, wipe data and cache, insall zip from SD, reboot.
You may want to back up data beforehand with an app like Titanium backup.
Edit:unable to return to stock
tchen510 said:
Basically, you flash a zip the same way you put on CM9. Find the ROM you want, make sure you are running the right kernal, usually entropy's, put the new ROM's zip file on your SD card, boot into clockwork recovery, wipe data and cache, insall zip from SD, reboot.
You may want to back up data beforehand with an app like Titanium backup.
Click to expand...
Click to collapse
do i flash a gingerbread rom first then entropys kernel because i am running cm9 with ambrices kernel for cm7?
Edit: i tried flashing entropys kernel then flashing a gingerbread rom and was unable to get past samsung log so i went back to cm9 can someone tell me what i did wrong.
heat361 said:
do i flash a gingerbread rom first then entropys kernel because i am running cm9 with ambrices kernel for cm7?
Edit: i tried flashing entropys kernel then flashing a gingerbread rom and was unable to get past samsung log so i went back to cm9 can someone tell me what i did wrong.
Click to expand...
Click to collapse
Sorry, but I'm not sure what you should do. Someone more experienced will know.
if the 5.0 are anything like the 4.0's then flashing to CM7 or CM9 converts the partitions, you have to use heimdall to flash the stock recovery with a pit file to recreate the stock partitions. check the development threads for a "5.0 stock recovery" thread and follow directions, hope you have a good backup of your stock partitions, a CWM backup doesn't backup your efs and its been converted by flashing CM9, so if you don't have an EFS backup your gonna probably lose your lockscreen and power menu's, at least thats what happens on the 4.0, I imagine the 5.0 is similar.
daniel644 said:
if the 5.0 are anything like the 4.0's then flashing to CM7 or CM9 converts the partitions, you have to use heimdall to flash the stock recovery with a pit file to recreate the stock partitions. check the development threads for a "5.0 stock recovery" thread and follow directions, hope you have a good backup of your stock partitions, a CWM backup doesn't backup your efs and its been converted by flashing CM9, so if you don't have an EFS backup your gonna probably lose your lockscreen and power menu's, at least thats what happens on the 4.0, I imagine the 5.0 is similar.
Click to expand...
Click to collapse
Would this work http://forum.xda-developers.com/showthread.php?t=1389873&highlight=adamoutler
Edit: got it to work by just flashing a gingerbread ROM I did not have to flash pit files
So I finally tried some AOSP, but missed my camera immensely so I went to switch back to my backup that I made in TWRP.
Unfortunately AOSP roms use CWM recovery and it won't recognize my TWRP so I've tried to redo the Dual Recovery method but since I no longer have stock kernel it fails.
Now I've also tried to use fastboot to flash a boot.img which I thought was a stock kernel....but obviously I was wrong or it didn't want to work.
Either way as of now I'm using FlashTool to flash stock image, then root, then install DualRecovery again and THEN restore backup.
Does anyone know where I went wrong and hopefully provide a faster solution in case I go back to trying ASOP again? Maybe backup in CWM next time?
Now I do have to flashable DualRecovery.zip that I did try in CWM but it didn't work either, I'm guessing since I didn't have stock kernel...
Thanks in advanced. Why didn't Sony just have a dedicated recovery partition!
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Mr.R™ said:
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Click to expand...
Click to collapse
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
ZPaul2Fresh8 said:
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
Click to expand...
Click to collapse
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Envious_Data said:
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Click to expand...
Click to collapse
Well I did try to use the dual recovery but it didn't work. It says it is only for stock kernel so I didn't expect it to, but I had to try...
@ZPaul2Fresh8
EDIT: DON'T INSTALL IF YOU STILL WANT TO USE CM!!!
It won't boot the system of cm if you flashed the twrp img, just flash it if you want to go to a backup!
"
It was very easy for me, at the end i had a twrp 2.7.0.0 in my cm11'd Z2, you need pc, and usb cable, and fastboot and adb drivers, lol its way easier than flashing .ftf, go to http://forum.xda-developers.com/showthread.php?t=2764971 and download the zip and extract it, follow this tout: http://forum.xda-developers.com/showthread.php?t=1752270 and you will be all good...
I looked around for one but was unable to find one. Maybe Twi5sted's stock has the original kernel but encryption fails when I attempt it.
Any suggestions?
Yep, muinz_ri created a Stock De-Odexed ROM. I was successfully able to install Xposed by flashing everything through FlashFire and still have Knox 0x0.
http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676
Direct link to ROM download: https://www.androidfilehost.com/?fid=24052804347762756
TheAH said:
Yep, muinz_ri created a Stock De-Odexed ROM. I was successfully able to install Xposed by flashing everything through FlashFire and still have Knox 0x0.
http://forum.xda-developers.com/tmo...ow-to-update-to-stock-rooted-ob1-5-0-t3049676
Direct link to ROM download: https://www.androidfilehost.com/?fid=24052804347762756
Click to expand...
Click to collapse
That's awesome, wish I had known before I tripped Knox but oh well.
I'm getting a bootloop with a very bright split second tmobile splash screen just before it reboots. I have latest TWRP, link2sd and encryption... I wonder what the problem could be...
how to make stock recovery flashable?
I do have another question regarding this rom - would you happen to know how I may be able to make the embedded recovery image flashable? TWRP doesn't seem to be working at the moment with regard to decrypting and formatting /data but the stock recovery does. It can come in handy if there is a way to do it via mobile odin possibly or via some other program.
fishinpercolator said:
I do have another question regarding this rom - would you happen to know how I may be able to make the embedded recovery image flashable? TWRP doesn't seem to be working at the moment with regard to decrypting and formatting /data but the stock recovery does. It can come in handy if there is a way to do it via mobile odin possibly or via some other program.
Click to expand...
Click to collapse
Do you have twrp installed right now?
ShinySide said:
Do you have twrp installed right now?
Click to expand...
Click to collapse
Right now I have stock recovery as I recently reflashed the Rom. At some point however I plan to go back to TWRP.
If I run into encryption problems and need to do a reset, I would like to see if I can flash TWRP using TWRP app while booted in safe mode (if I am able to get that far).
What do you think?
fishinpercolator said:
Right now I have stock recovery as I recently reflashed the Rom. At some point however I plan to go back to TWRP.
If I run into encryption problems and need to do a reset, I would like to see if I can flash TWRP using TWRP app while booted in safe mode (if I am able to get that far).
What do you think?
Click to expand...
Click to collapse
Well encryption will be fine on stock recovery. I thought you had twrp and just wanted the stock recovery which I was going to tell you to post the stock recovery and I'll put it in a twrp flashable zip
ShinySide said:
Well encryption will be fine on stock recovery. I thought you had twrp and just wanted the stock recovery which I was going to tell you to post the stock recovery and I'll put it in a twrp flashable zip
Click to expand...
Click to collapse
I appreciate that... at some point I will be on TWRP though so I can post the stock recovery when I get home. Or how can I do it myself?
fishinpercolator said:
I appreciate that... at some point I will be on TWRP though so I can post the stock recovery when I get home. Or how can I do it myself?
Click to expand...
Click to collapse
Here, download this, extract the zip, put the recovery.img in the extracted folder, highlight meta-inf system and recovery.img and zip all three and flash it. Only use this zip for stock or custom recoveries
ShinySide said:
Here, download this, extract the zip, put the recovery.img in the extracted folder, highlight meta-inf system and recovery.img and zip all three and flash it. Only use this zip for stock or custom recoveries
Click to expand...
Click to collapse
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
fishinpercolator said:
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
Click to expand...
Click to collapse
Obvious question - did you reboot back to recovery after flashing?
fishinpercolator said:
Hey thanks! So I did as you said and flashed the stock recovery from the deodexed rom and it's still TWRP. Strange isn't it? It would make sense if the deodexed ROM came with TWRP but when I initially flashed it I can confirm it was stock android.
I'm confused....
Click to expand...
Click to collapse
Oh wait, I did something very wrong... fixing now...
Yay it worked, thanks a lot
I guess I should keep the stock recovery installed with this thing encrypted because TWRP seems broken (at least version 2.8.7.0). I emailed the developer about it.
Now I'm wondering for added flexibility, how I may be able to flash the stock recovery from MobileOdin. That seems to take .md5 files and not zips. Is this feasible to do?
fishinpercolator said:
Yay it worked, thanks a lot
I guess I should keep the stock recovery installed with this thing encrypted because TWRP seems broken (at least version 2.8.7.0). I emailed the developer about it.
Now I'm wondering for added flexibility, how I may be able to flash the stock recovery from MobileOdin. That seems to take .md5 files and not zips. Is this feasible to do?
Click to expand...
Click to collapse
Post the img I'll make you one tonight. It'll be 10x easier for me since I run Linux then telling you how on windows
ShinySide said:
Post the img I'll make you one tonight. It'll be 10x easier for me since I run Linux then telling you how on windows
Click to expand...
Click to collapse
Well thanks! Maybe you can point me toward the Windows way as I would like to do the same for the stock kernel, xposed, and the tethering addon.
fishinpercolator so are you having trouble with TWRP? What I did in FlashFire was flash the pre-rooted de-odexed ROM (that I linked earlier) then booted that. It was de-odexed and worked fine but boot took about 15 minutes (as it is de-odexed).
In FlashFire you need to hit the + and press Flash ZIP or OTA.
Then I installed FlashFire again (it was erased because I flashed a new ROM) and downloaded the Samsung 5.0 Xposed ZIP and flashed that in FlashFire using Flash ZIP or OTA. Basically since I have Knox 0x0, I use FlashFire as my "recovery" and it might be easier for you than finding a working TWRP image (although I am sure ShinySide is more than eager to help you). Then I installed the Xposed APK and had to reboot before it recognized the Xposed ZIP was installed.
After that, most Xposed modules started working for me.
TheAH said:
fishinpercolator so are you having trouble with TWRP? What I did in FlashFire was flash the pre-rooted de-odexed ROM (that I linked earlier) then booted that. It was de-odexed and worked fine but boot took about 15 minutes (as it is de-odexed).
In FlashFire you need to hit the + and press Flash ZIP or OTA.
Then I installed FlashFire again (it was erased because I flashed a new ROM) and downloaded the Samsung 5.0 Xposed ZIP and flashed that in FlashFire using Flash ZIP or OTA. Basically since I have Knox 0x0, I use FlashFire as my "recovery" and it might be easier for you than finding a working TWRP image (although I am sure ShinySide is more than eager to help you). Then I installed the Xposed APK and had to reboot before it recognized the Xposed ZIP was installed.
After that, most Xposed modules started working for me.
Click to expand...
Click to collapse
I haven't used flashfire but will look into it. I've already tripped knox a while ago so that's not my prime concern. I want this phone to be encrypted and would like to learn a way to fix on the fly while on vacation (and without a laptop) in the event a catastrophe happens. It seems TWRP may not be removing the crypto footer when I format data as I still get the encryption password prompt.
Seems like flashfire allows you to flash roms from USB? I will need instructions for that.... <pokes around>
::update::
For some reason I thought flashfire was command line driven... I have Mobile Odin and I read that it contains flashfire, something worth looking into.
Is there a way to flash roms using ADB from a usb stick?
(NOTE- I should clarify, is there a way to flash from a command prompt assuming custom recovery is not installed and the phone is soft-bricked).
fishinpercolator said:
Well thanks! Maybe you can point me toward the Windows way as I would like to do the same for the stock kernel, xposed, and the tethering addon.
Click to expand...
Click to collapse
Here https://www.androidfilehost.com/?fid=24052804347792016
ShinySide said:
Here https://www.androidfilehost.com/?fid=24052804347792016
Click to expand...
Click to collapse
Well thanks!