Related
I'm trying to install android on my friends touchpad.
Everything looks like it goes fine, but when I get to the bootloader, there is no option to boot into clockwork mod.
The other options like boot into webos and boot into cm9 are there, but not clockwork mod.
Any reason as to why?
And how to install it?
Or is there another way to install clockwork mod on a touchpad?
IsaaKC said:
I'm trying to install android on my friends touchpad.
Everything looks like it goes fine, but when I get to the bootloader, there is no option to boot into clockwork mod.
The other options like boot into webos and boot into cm9 are there, but not clockwork mod.
Any reason as to why?
And how to install it?
Or is there another way to install clockwork mod on a touchpad?
Click to expand...
Click to collapse
Did you have the CWM image file in your CMInstall folder when you fflashed with the AcmeInstaller2?
Or you could also install GooManager and install TWRP touch recovery from the GooManager app. Not sure if there is an official recovery that you could flash via ROM Manager...
Sent from my cm_tenderloin using Tapatalk 2
You probably used the wrong clockworkmod zip file. I did the same thing the first time as well as many others. The file name should start with "recovery" and not "update." If your zip file starts with the word update, then find the other one. Its out there somewhere. And then just use ACMEinstaller to install that zip.
Im pretty sure thats right. I know there are two files out there and one doesnt work. I will have to make sure which one is the right one when I get home. Maybe I can upload it here.
jsgraphicart said:
You probably used the wrong clockworkmod zip file. I did the same thing the first time as well as many others. The file name should start with "recovery" and not "update." If your zip file starts with the word update, then find the other one. Its out there somewhere. And then just use ACMEinstaller to install that zip.
Im pretty sure thats right. I know there are two files out there and one doesnt work. I will have to make sure which one is the right one when I get home. Maybe I can upload it here.
Click to expand...
Click to collapse
That's exactly what the problem was.
I found the proper file, thanks!
IsaaKC said:
That's exactly what the problem was.
I found the proper file, thanks!
Click to expand...
Click to collapse
I'm glad you got it. I would have probably forgot to get back to this thread. lol
i'm having the same issue, but i am using the recovery-clockwork-tenderloin-1012.zip file so it's not the update one but i still can't find it in moboot, though i am able to boot in to CM9
---------- Post added at 12:33 AM ---------- Previous post was at 12:26 AM ----------
Fixed
for some reason i needed to use the update version to make it work...
I also had this issue when using ACMEinstaller2, i placed the 'recovery-clockwork-tenderloin-1012.zip' in the cminstall folder. The installer worked fine with moboot and cm9 but not clockwork, when trying on clockwork the installer would just thrown out a message about not finding any files starting with 'update' and ending in '.zip' so following some advice from another thread i renamed the zip file 'update-cwm_tenderloin-1012.zip' redid the process and it worked. I hope this helps anyone else getting this problem.
Hello,
Today for the first time I installed Android on my touchpad(I know I am very late to the party!). I first tried to install the Fat n Creamy ROM(12/02 build)sing ACMEInstaller2 with the ROM zipfile, moboot 0.35 and gapps zipfile in cminstall folder. After flashing the ROM, which I believe didn't properly happen due to some incompatibility or incorrect install method, and so on reboot after flashing I got no option for android in moboot, only webos, reboot and shutdown options were there. Then i retried by putting just the ROM in cminstall folder, which didn,t work either. So I ended up installing official CM9 ROM for now using the update tenderloin zip file, CM9 zip file, moboot and gapps fix in the cminstall folder, which worked perfectly and I am typing this from it! But now I want the Fat n Creamy ROM...how do I install it? Can I install it on top of this or do I have to format and reinstall? If so, how do I do it? Thanks!
lucky88shp said:
Hello,
Today for the first time I installed Android on my touchpad(I know I am very late to the party!). I first tried to install the Fat n Creamy ROM(12/02 build)sing ACMEInstaller2 with the ROM zipfile, moboot 0.35 and gapps zipfile in cminstall folder. After flashing the ROM, which I believe didn't properly happen due to some incompatibility or incorrect install method, and so on reboot after flashing I got no option for android in moboot, only webos, reboot and shutdown options were there. Then i retried by putting just the ROM in cminstall folder, which didn,t work either. So I ended up installing official CM9 ROM for now using the update tenderloin zip file, CM9 zip file, moboot and gapps fix in the cminstall folder, which worked perfectly and I am typing this from it! But now I want the Fat n Creamy ROM...how do I install it? Can I install it on top of this or do I have to format and reinstall? If so, how do I do it? Thanks!
Click to expand...
Click to collapse
Just DL the SGA Rom to your tablet and flash it with recovery .
more specific instructions please...
sstar said:
Just DL the SGA Rom to your tablet and flash it with recovery .
Click to expand...
Click to collapse
What do you mean when u say flash it with recovery? Isn't using ACMEInstaller method done in recovery mode? Can you be more specific?I apologize for my ignorance...
lucky88shp said:
What do you mean when u say flash it with recovery? Isn't using ACMEInstaller method done in recovery mode? Can you be more specific?I apologize for my ignorance...
Click to expand...
Click to collapse
No , I mean when you boot up among the choices you have will be either clockwork or TWRP that is the recovery I am referring to , either will give you the option to install a DL zip.
What are you using ?
sstar said:
No , I mean when you boot up among the choices you have will be either clockwork or TWRP that is the recovery I am referring to , either will give you the option to install a DL zip.
What are you using ?
Click to expand...
Click to collapse
I noticed I do not have any option for CWM or TWRP in the moboot at restart, only webos, webos recovery, cyanogenmod, reboot and shutdown. But I do have CWM installed as I just updated it, I can just go to the ROM manager in the apps and start CWM flash recovery from it...can I do it that way? Also can just flash the ROM on top of my current CM9 installation and will my apps be deleted?
lucky88shp said:
I noticed I do not have any option for CWM or TWRP in the moboot at restart, only webos, webos recovery, cyanogenmod, reboot and shutdown. But I do have CWM installed as I just updated it, I can just go to the ROM manager in the apps and start CWM flash recovery from it...can I do it that way? Also can just flash the ROM on top of my current CM9 installation and will my apps be deleted?
Click to expand...
Click to collapse
You can do that and if you flash without doing a system wipe you will retain all your apps.
Possibly an easier way for you would be to DL Goo manager from play store and then install open recovery script which will appear as shown in the screenshot below after you hit the 3 dots in the top right hand corner. Say yes to everything and it will install the latest TWRP for you.
You could then use goo to browse compatible Roms and DL SGA's and use it to flash the Rom/zip for you as shown in the second pic.
Which ever method you choose do make a backup before with your preferred recovery either CWM or TWRP.
I hope this helps.
Sent from my cm_tenderloin using Tapatalk 2
sstar said:
You can do that and if you flash without doing a system wipe you will retain all your apps.
Possibly an easier way for you would be to DL Goo manager from play store and then install open recovery script which will appear as shown in the screenshot below after you hit the 3 dots in the top right hand corner. Say yes to everything and it will install the latest TWRP for you.
You could then use goo to browse compatible Roms and DL SGA's and use it to flash the Rom/zip for you as shown in the second pic.
Which ever method you choose do make a backup before with your preferred recovery either CWM or TWRP.
I hope this helps.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
One last question, which one would you say is better, the latest Nightly from CM team as of today's release or the Fat n Creamy? And yeah, would you happen to know how to get the CWM recovery option in the moboot menu? Thanks a lot for all your help!
lucky88shp said:
One last question, which one would you say is better, the latest Nightly from CM team as of today's release or the Fat n Creamy? Thanks a lot for all your help!
Click to expand...
Click to collapse
Probably the nightly but only because it is the most recent. However whichever you initially go for make a backup then try the other and make another backup that way you can relatively easily switch between the two in order to decide which you prefer.
Have fun.
---------- Post added at 09:43 PM ---------- Previous post was at 09:37 PM ----------
lucky88shp said:
One last question, which one would you say is better, the latest Nightly from CM team as of today's release or the Fat n Creamy? And yeah, would you happen to know how to get the CWM recovery option in the moboot menu? Thanks a lot for all your help!
Click to expand...
Click to collapse
Just saw the edit, DL Rom toolbox lite and edit the default recovery but it should show up in moboot anyway.
Can you post a screenshot of your boot folder please.
sstar said:
Probably the nightly but only because it is the most recent. However whichever you initially go for make a backup then try the other and make another backup that way you can relatively easily switch between the two in order to decide which you prefer.
Have fun.
---------- Post added at 09:43 PM ---------- Previous post was at 09:37 PM ----------
Just saw the edit, DL Rom toolbox lite and edit the default recovery but it should show up in moboot anyway.
Can you post a screenshot of your boot folder please.
Click to expand...
Click to collapse
LOL, where is the boot folder? I searched via the File Browser, and couldn't find it....And how do I take a screenshot?
lucky88shp said:
LOL, where is the boot folder? I searched via the File Browser, and couldn't find it....And how do I take a screenshot?
Click to expand...
Click to collapse
Use Rom toolbox , screenshot should be an option when holding the power off button , you sound a little bit new to this lark (I only started 6 months ago) so don't worry if you can't find it.
Can/ have you actually gone into CWM as I am not sure that it's installed because it would/should show in the moboot menu.
Check and let me know. If its not I think Goo manager and TWRP may be an easier option.
sstar said:
Use Rom toolbox , screenshot should be an option when holding the power off button , you sound a little bit new to this lark (I only started 6 months ago) so don't worry if you can't find it.
Can/ have you actually gone into CWM as I am not sure that it's installed because it would/should show in the moboot menu.
Check and let me know. If its not I think Goo manager and TWRP may be an easier option.
Click to expand...
Click to collapse
Here are the screens for boot folder. And as I mentioned before I believe I have CWM installed as the first thing that popped after flashing the ROM was an update for CWM.
According to your screenshots (Well done). You don't as there is no ulimage called CWM/ clockwork or TWRP . I suggest the Goo route to install TWRP once done it is VERY user friendly, then you can make backups before proceeding any further, then if you wish and are not happy use is to install a CWM zip.
lucky88shp said:
Hello,
Today for the first time I installed Android on my touchpad(I know I am very late to the party!). I first tried to install the Fat n Creamy ROM(12/02 build)sing ACMEInstaller2 with the ROM zipfile, moboot 0.35 and gapps zipfile in cminstall folder. After flashing the ROM, which I believe didn't properly happen due to some incompatibility or incorrect install method, and so on reboot after flashing I got no option for android in moboot, only webos, reboot and shutdown options were there. Then i retried by putting just the ROM in cminstall folder, which didn,t work either. So I ended up installing official CM9 ROM for now using the update tenderloin zip file, CM9 zip file, moboot and gapps fix in the cminstall folder, which worked perfectly and I am typing this from it! But now I want the Fat n Creamy ROM...how do I install it? Can I install it on top of this or do I have to format and reinstall? If so, how do I do it? Thanks!
Click to expand...
Click to collapse
Can you post the acmeinstaller2 zip? I cannot find it
sstar said:
According to your screenshots (Well done). You don't as there is no ulimage called CWM/ clockwork or TWRP . I suggest the Goo route to install TWRP once done it is VERY user friendly, then you can make backups before proceeding any further, then if you wish and are not happy use is to install a CWM zip.
Click to expand...
Click to collapse
K thanks...I noticed too that there was no image file for CWM. I will go the goo manager route. Again, thanks a lot for all your help, really appreciate it!
ScottBroker said:
Can you post the acmeinstaller2 zip? I cannot find it
Click to expand...
Click to collapse
You should really upgrade to 3 available here http://goo.im/devs/jcsullins/cmtouchpad/testing/ACMEInstaller3
But here is 2 anyway https://www.box.com/shared/32e48b3b777f2bfc7866
ScottBroker said:
Can you post the acmeinstaller2 zip? I cannot find it
Click to expand...
Click to collapse
Here it is. Download the novacom drivers and its included with it.
http://tinyurl.com/brfuvqn
I recently got an S3 Mini and I wanted to install cyanogenmod on it. I have experience because I have cyanogenmod on my S4 and TWRP custom recovery.
After I use Odin to flash the TWRP custom recovery to the phone, whenever I try to boot into recovery the screen just freezes and these lines and green film start to appear on the screen.
I have uploaded the picture of the phone trying to boot into recovery
Can someone please help me?
Thanks
McMahonus4 said:
I recently got an S3 Mini and I wanted to install cyanogenmod on it. I have experience because I have cyanogenmod on my S4 and TWRP custom recovery.
After I use Odin to flash the TWRP custom recovery to the phone, whenever I try to boot into recovery the screen just freezes and these lines and green film start to appear on the screen.
I have uploaded the picture of the phone trying to boot into recovery
Can someone please help me?
Thanks
Click to expand...
Click to collapse
Did you flashed TWRP from maclaw?
---------- Post added at 08:19 PM ---------- Previous post was at 07:57 PM ----------
Which model is this phone, it's not a GT-I8910 right?
Clostry said:
Did you flashed TWRP from maclaw?
---------- Post added at 08:19 PM ---------- Previous post was at 07:57 PM ----------
Which model is this phone, it's not a GT-I8910 right?
Click to expand...
Click to collapse
you're right, it can't be a I8190. Look at where the camera is (right top side). On the original it's on the left top side
koragg97 said:
you're right, it can't be a I8190. Look at where the camera is (right top side). On the original it's on the left top side
Click to expand...
Click to collapse
The photo is not clear but the camera seems where it should be to me
Just telus is a canadian company, this made me think it could be a sm-g730...
Clostry said:
The photo is not clear but the camera seems where it should be to me
Just telus is a canadian company, this made me think it could be a sm-g730...
Click to expand...
Click to collapse
There's literalyl 390248230948023948 variants of the S3 mini, fairly certain it is the SM-G730 confirm it on the model or in settings. Maclaw's recovery or any other recovery is not compatible with your phone, and as far as I know your phone does not have a recovery yet hence why it bootloops. You need to revert back to stock: forum.xda-developers.com/attachment.php?attachmentid=2530506&d=1390328847 and all shall be well. There's no active development on your phone as far as I know but do give this thread a visit: http://forum.xda-developers.com/showthread.php?t=2469413&page=11
So can it be that I'm flashing the wrong twrp file? Because I'm flashing the wrong region?? Any suggestions on how to fix this issue and get it working?
McMahonus4 said:
So can it be that I'm flashing the wrong twrp file? Because I'm flashing the wrong region?? Any suggestions on how to fix this issue and get it working?
Click to expand...
Click to collapse
It's because there is no TWRP for your device, there are no TWRP or CWM builds for the TELUS S3 MINI the ATT&T S3 MINI and the VERIZON S3 MINI.(as far as I know) Only solution is to compile it yourself, and that's quite involved but there are numerous guides out there.
I see.... Thanks anyways, I may try to compile my own, if I do get it working I will upload it here
McMahonus4 said:
I see.... Thanks anyways, I may try to compile my own, if I do get it working I will upload it here
Click to expand...
Click to collapse
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
TWRP is easier to compile after you got a working CWM recovery, as you only need to add in a couple of TWRP flags.
You need to run ubuntu natively or through virtual machine (VMWare, etc) and download the CM source code which may take a while depending on your internet speed (it's quite large about 15gb i think or so )
The same thing happened to me when I tried to install CWM for my s3 mini sm-g730w8( this is the Canadian version for telus) Boot into download mode (VOL DOWN+HOME+POWER) then just choose reboot device and it should be okay. If it still doesn't work then boot into download mode and then flash the stock rom via odin. Also regarding the custom recovery for our phone, even if you did port a working custom recovery the works for our phone, you won't be able to install it because our bootloader is locked; which is also why your screen turned green after trying to boot into your custom recovery. I found 2 possible solutions for flashing scripts and mods: kn0x0ut Toolbox http://forum.xda-developers.com/showthread.php?t=2550120 and Flash Gordon http://forum.xda-developers.com/showthread.php?t=2250555 I haven't been able to try them yet but I think kn0x0ut toolbox is more reliable. I hope this helped
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
hello
first off cool but i think this needs to go some where else maybe wrong
sorry to be annoying i just dont want u to get yelled at if its in the wrong place
bnb25 said:
only issue so far is that it wont let you install custom ROM's, After flashing a Custom ROM it just reboots back into recovery.
Click to expand...
Click to collapse
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
RockasKane said:
Just don't reboot into recovery from any software.
Turn off the Tab and enter recovery with the 3 keys method (power+volume up+menu) and you will be able to flash anything in recovery and reboot into system.
Just DON'T EVER reboot into recovery using the "reboot into recovery" option on any software including power menu.
I have this issue for a long time, even when I was on 4.1.2 and that is how I got rid of the problem.
Click to expand...
Click to collapse
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
bnb25 said:
---------- Post added at 05:44 AM ---------- Previous post was at 05:41 AM ----------
[/COLOR]
those reboot options work just fine before Upgrade to kitkat. I booted into recover from the off position. the first time after reinstalling recovery.
Click to expand...
Click to collapse
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
chris1871 said:
Hello, yesterday I got for OTA (Samsung Tab 3 SM-T210R) upgrade to Kit Kat. I can´t do any test, but it gives the feeling that everything runs faster
Click to expand...
Click to collapse
I did the upgrade on my device no problems GOT ROOT then had issues. After root any changes ie: install zip, backup
The unit would get stuck in recovery mode. Recoveries tried TWRP, PhilZtouch, CWM
SDcard issues were fixed with Nextapp SDfix after root
Anyone having any other issues?
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
andrewhall said:
My [ROM] SM-T210R 4.4.2 Kitkat root via UPDATE-SuperSUv1.94.zip
Thanks for your tip I now can install zips without recovery boot loop.:good: That was a major issue with the new Samsung 4.4.2 update.
Next issue I'm working on is boot-animation. Tried [Aroma] boot-animation (no luck), ROM toolbox Pro boot-animation (no luck)
Since trying I now have no boot-animation. Next step I shall try and push the zip to get something..
The new 4.4.2 is very fast otherwise.:good:
Click to expand...
Click to collapse
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
RockasKane said:
But the first time you installed the update you rebooted via software command, right?
If you boot into recovery from off with the three buttoms... you can flash the 4.4.2 and it will load into system.
Just don't reboot into recovery via software command.
Test it.
Click to expand...
Click to collapse
no. I booted into recovery while the phone was off. 3 key Combo.
Ok, sorry to hear that.
The workaround seems to work with everybody, thats why I asked.
RockasKane said:
Give NoleKat a try... it is based on stock 4.4.2 and it has the kernel fix that brings back the boot animation.
You can find it here: https://www.androidfilehost.com/?w=files&flid=17472 Download V1.8
here's the topic: http://forum.xda-developers.com/galaxy-tab-3/development-7/rom-port-nolekat-v1-0-t210r-t2837338
Click to expand...
Click to collapse
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
andrewhall said:
Thanks Again RockasKane [NoleKat] is by far the nicest smoothest rom I have tried to date!
Click to expand...
Click to collapse
Great!
But you must thank @gr8nole... Great and hardworking guy and all the development crew that contributed with great fixes
I would install KITKAT on my Galaxy S i9000 using the TWRP recovery.
In the list of devices on which you can mount the TWRP not indicated the Galaxy S I9000.
It 'an error or you can not?
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I will choose the ROM later.
Now I have already choosed the procedure to save EFS files.
Now I'm choosing what type of recovery use.
I repeat: I would use TWRP but my smartphone does not appear in the list of supported devices.
On the contrary, in all the guides TWRP is indicated as an alternative to CWR.
Original TWRP is not available for i9000.
BUT: The CodeROM-Team managed to make it running onto i9000. Therefore, you need to extract TWRP from their ROM, convert it to an Imagefile and upload it with ODIN. This works!
Hello, I would like to also do this as stated in the OP. The image in the kernel.tar, that's what I have to flash the i9000 with Odin? Do I have twrp recovery then in the i9000?
Fragone said:
1. download http://forum.xda-developers.com/showthread.php?t=1644240
2. download CodeROM-5.1.1-20150825-galaxysmtd
3. extract boot.img and rename it to zImage
4. run tar.bat
Result attached for convenience. All credits go to the devs!
Click to expand...
Click to collapse
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
bronxboy1 said:
I downloaded the attached kernel attachment and flashed it with Odin. After doing this, the phone booted up in TWRP 2.8.7.0, but deleted the stock ROM. That's not all, I cannot do anything anymore with the phone, because the phone gives error with every ROM I try to install: "Unable to mount '/system'" and "Unable to mount '/data'". The phone does not boot in download mode either.
The big question is now, how to solve these errors? Can anyone help?
Click to expand...
Click to collapse
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
---------- Post added at 05:13 PM ---------- Previous post was at 05:08 PM ----------
Fragone said:
It seems that this Recovery with CWM does not support any other ROMs than CodeROM . Had the same problem lately, but in my case I expected it to be due to the fact that i changed the Filesystem of /system and /data to F2FS, but apparently that was not the main cause. (By the way- don't do that. It took me 2 days to get it back to EXT again).
The only way to solve it was to flash a complete Stock ROM with ODIN (I had to do it twice until everything was working again), using the files you'll find in the Stock-Rom-DB. I used this ones (sorry, no link atm, but you'll find it easily):
CSC_OXXJVC.tar.md5 3'778'609 20.04.2012 23:42 -a--
PDA_XWJW5_Sbl.tar.md5 285'562'932 20.04.2012 23:40 -a--
PHONE_XXJW4.tar.md5 12'585'010 27.04.2012 16:17 -a--
s1_odin_20100512.pit 1'744 06.08.2010 16:56 -a--
Luckily this did not affectet the area where the phones special data is located (IMEI and so on, donnot remeber the correct name for that).
I'm now back onto latest official CM10, because newer releases had quite a few issues, especialy bad connectivity (dont know why). With android 4.4.4 everything is working perfectly again.
Hope that helps to fix the problems my file did!
Click to expand...
Click to collapse
> The phone does not boot in download mode either
Did not see that before. I never had such an issue. Try it again, but do not push the power button more than 10 seconds, else the phone reboots again and again.
Sometimes, Download mode works even thought you cannot see anything on screen. try to connect the device to your PC and launch ODIN, you'll see if it can connect.
Tnx for your reply Fragone. It took me a while, had to wait on a USB jig for me to get the phone in download mode.
Unfortunately I did format to f2fs, how did you get back to ext? As for the other files, I did get my hands on an original rom, but I have to go look for the files you mentioned and try it with those, as the stock rom does not boot either. If you have the links, I'd be much abliged. Right now I go to sleep, just got home from the graveyard shift.
So someone finally returned my i9000 to me after a few years of use and I'm looking to put a current ROM on it so I can use it as a test phone. I keep seeing TWRP as the custom recovery used for the new ROMs. And yet like umberto, I've found there's no official custom TWRP for this phone. I'm pretty familiar with using TWRP on all my other devices.
So back to the original question of this thread - is there a way to get TWRP on the phone? It looks like Fragone's suggestion isn't the right way to go? The only thing I could find in my thread searches was a suggestion to use Mackay's ROM to get 2.8.1.0 and then (theoretically) it's on there so you could move to other ROMs. Any help?
D
@umberto santulli @dnaod
On the i9000, kernel & recovery share the same image, thus the recovery cannot be flashed separately. Therefore there is no i9000 on the TWRP site.
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
tetakpatak said:
@umberto santulli @dnaod
Yes, there are several kernels that feature TWRP, but you must be careful: kernel must be compatible with the ROM, otherwise, bootloop is result.
tetakpatalked from 1+One
Click to expand...
Click to collapse
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
dnaod said:
Thanks for this warning. I've flashed MacKay's ROM and am playing with it right now. I was planning on flashing OmniROM later using this same TWRP but I'm guessing I should read quite a bit more carefully with every ROM to see if they're compatible.
Click to expand...
Click to collapse
There should be no problem to change the ROM. Just mind that the kernel & recovery share the image. I was using Omni 4.4.4 by kasper_h and Mackay kernel with TWRP
tetakpatalked from Nexus 7 flo