Hello everyone,
First of all - great to become a part of this community of talented hackers. You guys really make wonders with software on mobile devices.
I have recently tried to flash new unofficial CM12 Lollipop custom ROM from novafusion site on Samsung Galaxy S3 Mini GT-l8190 device.
I've used Odin and proper recovery md5.tar image intended for use with Odin. Also I've installed drivers needed for the operation. I was running it all under Windows 8.1, as this is the only OS that can dual-boot with my Linux OS on a second HDD.
Everything went quite smooth to the step where Lollipop should boot. It did boot for the first time, asked for memory wipe, because internal storage was encrypted in previous version of android Jelly Bean, IIRC, it isi not my device].
I agreed, then device rebooted and since then it is stuck on TWRP screen, no matter how I boot it [vol+, menu and power keys brings device in supposed recovery, but recovery never boots into TWRP menu].
vol-,menu,power key combo works and it brings device into "downloading new firmware" mode properly. However, flashing of any of the firmware listed on novafusion site does not really change anything. I have also tried to flash CWM onto the device, but it goes to the blank screen after showing Samsung logo. "Downloading new firmware" works fine with CWM, too, just as in TWRP case.
Can anyone please suggest any way out here? I think I've done proper research before approaching this operation, but I don't really know what to do now, when the original instruction from the site failed to bring this device to Lollipop.
I tried to contact novafusion/maclaw team, but their mail server is bouncing off all messages.
I'd appreciate all advice.
Thanks in advance,
- marc
marc_smith said:
Hello everyone,
First of all - great to become a part of this community of talented hackers. You guys really make wonders with software on mobile devices.
I have recently tried to flash new unofficial CM12 Lollipop custom ROM from novafusion site on Samsung Galaxy S3 Mini GT-l8190 device.
I've used Odin and proper recovery md5.tar image intended for use with Odin. Also I've installed drivers needed for the operation. I was running it all under Windows 8.1, as this is the only OS that can dual-boot with my Linux OS on a second HDD.
Everything went quite smooth to the step where Lollipop should boot. It did boot for the first time, asked for memory wipe, because internal storage was encrypted in previous version of android Jelly Bean, IIRC, it isi not my device].
I agreed, then device rebooted and since then it is stuck on TWRP screen, no matter how I boot it [vol+, menu and power keys brings device in supposed recovery, but recovery never boots into TWRP menu].
vol-,menu,power key combo works and it brings device into "downloading new firmware" mode properly. However, flashing of any of the firmware listed on novafusion site does not really change anything. I have also tried to flash CWM onto the device, but it goes to the blank screen after showing Samsung logo. "Downloading new firmware" works fine with CWM, too, just as in TWRP case.
Can anyone please suggest any way out here? I think I've done proper research before approaching this operation, but I don't really know what to do now, when the original instruction from the site failed to bring this device to Lollipop.
I tried to contact novafusion/maclaw team, but their mail server is bouncing off all messages.
I'd appreciate all advice.
Thanks in advance,
- marc
Click to expand...
Click to collapse
reflash TWRP using odin & dl mode.
-if still cant get recovery,
reset thta phone --> means flash full system image, can be found on sammobile or other sites using odin & dl mode. there are plenty of tuts on the net just seach, same way for many samsung models
-> if you get twrp, its goood to make a full format ´,even more when u switch to new rom (like from JB to LP)
so: in TWRP format internal if possible, data (factory reset), cache & system. can make them f2fs btw if using nova's builds.
-install rom & gapps done. happy boting
bejunk said:
reflash TWRP using odin & dl mode.
-if still cant get recovery,
reset thta phone --> means flash full system image, can be found on sammobile or other sites using odin & dl mode. there are plenty of tuts on the net just seach, same way for many samsung models
-> if you get twrp, its goood to make a full format ´,even more when u switch to new rom (like from JB to LP)
so: in TWRP format internal if possible, data (factory reset), cache & system. can make them f2fs btw if using nova's builds.
-install rom & gapps done. happy boting
Click to expand...
Click to collapse
Thanks a lot, mate! I have flashed stock ROM and device is operational again with the old ROM. Now, I will hack some more to make it work with KitKat or Lolipop, this time correctly.
You guys rock.
UPDATE:
Ok, so I've managed to install CM12.1 onto this device and it works beautifully. The only major hickup is the fact that It is unable to encrypt device's internal storage. Any thoughts on that?
Also, I had to restore stock ROM and DECRYPT THE INTERNAL STORAGE FIRST, then boot into TWRP recovery and do wipe.
marc_smith said:
Thanks a lot, mate! I have flashed stock ROM and device is operational again with the old ROM. Now, I will hack some more to make it work with KitKat or Lolipop, this time correctly.
You guys rock.
UPDATE:
Ok, so I've managed to install CM12.1 onto this device and it works beautifully. The only major hickup is the fact that It is unable to encrypt device's internal storage. Any thoughts on that?
Also, I had to restore stock ROM and DECRYPT THE INTERNAL STORAGE FIRST, then boot into TWRP recovery and do wipe.
Click to expand...
Click to collapse
I have a somewhat different problem.
Rooted the phone, "installed" TWRP with rashr and now it's stuck in the samsung logo however i start the phone. power button + volume up + home button don't work, just the power button doesn't work, pluging it in the wall or the PC doesn't work and the PC doesn't even see it.
what can i do to fix this problem?
Related
Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!
zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions
Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers
zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10
Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???
I tried to flash CWM10 into my Samsung Galaxy I9000 Device And here's what happened:
I got into the CWM Recovery screen and chose install from sdcard (after a wipe data + wipe cache factory ofcourse).
Everything seem to go OK, no errors or special things, but when I restarted the device to boot into Android OS, it just came back to the CWM Recovery screen.
Since then, I have tried to install many other ROMS and the phone simply won't boot to android OS.
I have also noticed that usually after a successful ROM flash, folders are created in the internal SD card a thing which DID NOT happen this time.
The only difference that the new ROMS installation does is change the CWM Recovery version/Mod.
So basically, I am stuck at CWM Recovery Screen.
I am clueless and I will really appreciate any thing you can.
Any thoughts?
MPolo1989 said:
I tried to flash CWM10 into my Samsung Galaxy I9000 Device And here's what happened:
I got into the CWM Recovery screen and chose install from sdcard (after a wipe data + wipe cache factory ofcourse).
Everything seem to go OK, no errors or special things, but when I restarted the device to boot into Android OS, it just came back to the CWM Recovery screen.
Since then, I have tried to install many other ROMS and the phone simply won't boot to android OS.
I have also noticed that usually after a successful ROM flash, folders are created in the internal SD card a thing which DID NOT happen this time.
The only difference that the new ROMS installation does is change the CWM Recovery version/Mod.
So basically, I am stuck at CWM Recovery Screen.
I am clueless and I will really appreciate any thing you can.
Any thoughts?
Click to expand...
Click to collapse
cos of new partitions u have to install 1 ROM 2x. sometimes 3x. thats all.
so take ur cm10 zip and flash it. after reboot to recovery just flash the same file again.
Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?
Anyone?
I guess no one is using this phone anymore?
Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo
Hi everyone,
some who frequently read the forum may know already that there are issues with the latest official TWRP for the Galaxy S3 LTE. The recovery partition on the Galaxy S3 LTE is too small for the latest recovery provided by TWRP. The partitions are messed up, you won't be able to mount /system and /data. Some users couldn't even flash their preferred ROM. As of now the buggy recovery is getting fixed.
I am not responsible for any damage, losing data or weird behavior you encounter while doing one of the following steps. As reported by several users step 1 was the way for them to fix their phone. Be sure of what you're doing. Make sure you know how to boot into recovery/Download Mode to do these things mentioned here and how to use odin. If not, XDA users have provided several guides. Use the search.
If you already flashed the faulty recovery, flashed a custom ROM with it and your phone ends up in a bootloop there are several ways to fix this issue.
1. Via odin and official stock firmware - please note: You might lose all your data you have on your internal storage
Download the latest official Samsung firmware from sammobile or look on XDA for provided stock ROMs by the AMCHA team. Boot your phone into Download Mode and flash the official firmware via odin. If you're done, reboot into stock recovery (which will be provided after flashing the stock firmware), perform a factory reset and let your phone boot up once. First boot might take some time, so be patient. Although the first boot might not be needed, do it anyway to see if your phone is still in a bootloop or suffers from other damage. If the phone boots up fine reboot into Download Mode again, flash TWRP 2.8.5.0 or any other latest custom recovery (preferably the recovery the maintainers recommend in their development threads) and flash your preferred ROM. Your phone should now work as it should.
2. Via stock based custom ROM (if you haven't flashed any ROM via TWRP 2.8.7.0 already - please note: You might lose all your data in this process as well
Some users managed to get their phone working by flashing a stock based custom ROM like AMCHA or N4 Elite. If you only flashed the buggy recovery and didn't flash a custom ROM this way should be the step you should try first. Download any stock based custom ROM and flash it via the faulty one. If your phone boots up fine, boot into Download Mode and downgrade recovery or use any other recovery recommended for the ROM you're using. If you encounter issues or weird behavior with your phone go with step 1.
3. Via flashing a fixed TWRP 2.8.7.0 - please note: You might as well lose data
In this option you can flash a fixed version of TWRP which an user of XDA has provided. Many thanks to StdBarbarossa for his work. Unfortunately in his build you cannot mound your SD card via PC as it's not working at the moment. Make sure you have all the needed files already on your SD card. For some users this way was working for them. Boot your phone into recovery, click on install, change from .zip to .image, choose the Alpha17.img, install it by swiping and reboot your phone into recovery. Perform a wipe (preferably a factory reset, cache and dalvik cache might be working too) and see if your phone boots up fine. Here the same: if you're still facing issues go with step 1.
Link for the TWRP Alpha17 2.8.7.0 https://drive.google.com/file/d/0B-tlso-zNf9NMWlMMFpiYmYwTzA/view
I have gone through the same issue. In my case I only managed to get my phone working again with step one as I had flashed a custom ROM via the buggy recovery and ended up in a bootloop. As stated, others have managed to fix their phone with either option 2 or 3.
Link for the fixed TWRP is provided in the spoiler.
If you're not sure about something ask here first before you might brick your phone. If you know any other way to fix this issue feel free to post it here.
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/
Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan