[Q] Galaxy SIII mini toolkit - Galaxy S III Mini Q&A, Help & Troubleshooting

Hey there! First post here and it's filled with questions since my first attempt at flashing Maclaw's CM ROM went awry at best... So I downloaded the SIII mini toolkit, and proceeded to carry out the necessary tasks to root my phone( e.g installing TWRP, installing the drivers etc.) The problem initially arose when I couldn't find the Gapps and CM ROM zips in my root, all that after having wiped my data, dalvik and cache. I also couldn't mount the internal storage in order to place them somwhere where they would visible, but after reading up on the Internet I came across some posts that mentioned that it's a problem with TWRP and some 0 folder. Needless to say I was stuck in a constant bootloop and I had to revert to stock firmware. Whick brings me to the ultimate question: I ended up with JB 4.1.2 JZO54K.I1890XXAME1 which I'm unsure whether or not is supported by the toolkit itself. What process do I have to carry out to root my phone and install CWM (seeing my first experience with TWRP was unpleasant to say the least ) and from there have another go at flashing the custom ROM I initally tried to? Was the soft brick related to the fact that TWRP was not able to read my zip archives from the internal storage? Moreover, I wasn't able to find the fabled 0 folder...
P.S Since I'm a new user, I can't post at the original thread regarding the toolkit, so I thought this was a good place to start.

Related

[Q] Stuck on Samsung logo after a restart (did not flash)

Apologies if this is answered elsewhere but I've been looking around the forums and a lot of information/posts from people seem to conflict or the information is only valid for X kernel or Y kernel etc and it can still be a little overwhelming even after lots of nice people have posted guides.
I bought a German Note about a month ago and upgraded to 4.0.3 through the devices own update method (I have not flashed any ROMs on this device), leaving me on XX-LPY. I have since rooted the device, and did not perform any kinds of wipes doing this, this was the only time I even used CWM, I havent booted into CWM since (or used any of the normal recovery features).
The device has been working fine for around a week, I've restarted it several times without issue. However today after restarting it gets stuck on the Samsung logo and will not boot properly. The only thing I have used root for is to uninstall Kies and the SNS Push stuff (which seemed to save me a lot of battery life) and install ad-free android. I also installed the Carbon Tweaks app and applied the Carbon Booster stuff along with the Beats Audio and Bravia Engine stuff (nothing else).
I am able to get into recovery mode however I seem to be unable to put it into download mode (Edit: finally got it to do it once, wont do it every time though) so I have a few questions:
Can anyone tell me if its ruined or why its doing this?
Is it safe to just factory reset/wipe cache through normal android recovery (not CWM?).
Is it safe to try to flash another ROM through CWM (I'm on XX-LPY) and if so which one is safe for me to flash?
Is it safe to try to flash through Odin and if so which ROM should I flash?
I really dont care about the data on it or wiping it w/e. I just dont want to turn it into a paperweight if I can help it.
Thanks
Edit: Also if it makes any difference, this is the method I used to root the device:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
Nope, don't go around flashing stuff with CWM on that device.Also, you can't wipe as that may trigger the MMC_CAP_ERASE causing superbrick.Judging by what you say you've done, I'd say I don't know why it happened but it isn't ruined.
You can try to flash a stock GB rom of your country by following dr.ketan's guide in the dev section and then rooting it (if you want).Alternatively,you could just take it to a Samsung service center as there is no yellow triangle.But I'd try to flash the GB rom as flashing a stock kernel via PC Odin doesn't increase the flash counter.

[Q] To Brick or not to brick

ENVIRONMENT:
LG Optimus 2x (O2X) P990 .
Was running Android 2.3.4, and was Rooted nearly 2 years ago, and had CWM (Clockwork Mod).
Now running what ever is contained the the recovery img from the "[TOOL] Full Brick Repair (Clean & Easy)".
UPGRADES:
The AIO (All in one) tool recommend on multiple threads (within the O2X section), bricked my each time I followed the instructions on those articles.
Each time I tried to install one of the Download O2X ROM ZIP's via the CWM bootloader, it starts the install ok then aborts upon error (cant find path /system etc), and bricks the phone. Not sure if this relates to the partition compatibility, but I really have no way of knowing based on the info provided to me.
The only thing which has worked is: "[TOOL] Full Brick Repair (Clean & Easy)".
This appears to have installed Clockwork Mod 6.x, and JB (JellyBean) 4.1.2, (no idea what the partitions format or if it extended - but you can check the tool's batch script cfg fileif you know how to read the syntax).
After installing with the aforementioned unbrick tool, the phone was extremely fast to boot and to operate. But was missing Play and Gmail etc.
In the end I found that I needed to download the gapps zip, and install it off the SD card using Clockwork Mod recovery mode. However, after installation - the phone booted very slowly, and after it booted, the device experienced intermittent lockups for a few seconds at a time, and the keyboard kept crashing (would never show on screen at all), meaning I couldn't even download another via google play.
WHERE TO FROM HERE:
Please help - I need the correct tutorials and Firmware compatible with my device and its existing software/config.
Ideally I would like Jelly Bean version 4.2, with all the extra's.
Most importantly I want a stable build which doesn't have bugs preventing normal use of the phone (e.g. the In-call bug preventing audio, which requires and second step to apply the fix, or battery drain issues).
RESPONSES:
Please, no acronyms! Proper etiquette is that you put the full words brackets after the acronym, the first time you use it. Then you may use just the acronym on its own, throughout the rest of your post. This make each post self-sustained and useful. Not a breadcrumb of scattered information.
.

[Q] Newbie doubts on i9305t.

Hello everyone;
I'm all new to this rooting and flashing thing, and I've been reading lots of tutorials and wikis, but still some questions remain:
1. I have a carrier-unlocked i9305t (It came with carrier software and the carrier logo shows up everytime I start the phone, but it is unlocked to any sim-card in my country). Should I flash the device to CyanogenMOD 11 (which is available for i9305, not i9305t), would my phone brick? Or, in other words, what are the main differences between i9305 and i9305t and can I install a custom ROM for i9305 in i9305t?
2. What's the difference between rooting and installing a custom recovery (such as TWRP)? Will installing a custom recovery give me root acces to my phone?
[edit] 2.1. So I've found that I can root my phone through a custom recovery by flashing a SuperSu (super user) file on it. Where can I find a safe SuperSu file for i9305t?
3. I've found this tutorial (can't post the link thanks to forum rules, sorry!) for installing CyanogenMOD 11 in i9305 in which there's no mention to rooting the device: the process consists of installing a custom recovery in the phone and, from there, flash the CyanogenMOD 11 ROM. Is this correct and safe?
Then again, thanks for the help and sorry for the bad english, I'm not a native speaker.
Cheers!
You can flash any i9305 tom on your phone. The t just has to do with the frequency bands your phone uses. All you need to do is flash a custom recovery. Root is included in cm 11 so you only need to flash that
Sent from my GT-I9305 using xda app-developers app
I just got a i9305T too, rooted, downloaded latest CM 11 nightly, when tried to intall zip it gave me Status 7 error, something about my device being a 'm0' and so not compartible.
I somehow wiped the stock system and can't mount USB with the TWRP... Now I'm downloading things so I can flash the stock and get back to square one.
What's going on and what can I do? Will I always have the latest CM Roms? Otherwise I'm somehow giving up this phone. Please help me.
vicastro said:
I just got a i9305T too, rooted, downloaded latest CM 11 nightly, when tried to intall zip it gave me Status 7 error, something about my device being a 'm0' and so not compartible.
I somehow wiped the stock system and can't mount USB with the TWRP... Now I'm downloading things so I can flash the stock and get back to square one.
What's going on and what can I do? Will I always have the latest CM Roms? Otherwise I'm somehow giving up this phone. Please help me.
Click to expand...
Click to collapse
I am a CM i9305T user here. For me, TWRP gives me error codes but then changing to ClockWorkMod recovery (latest version) solved error code 7. I used everything for i9305 for my i9305T phone and I have no problems. Try installing ClockWorkMod and flash CM + GApps.:laugh:
dummiexx3 said:
I am a CM i9305T user here. For me, TWRP gives me error codes but then changing to ClockWorkMod recovery (latest version) solved error code 7. I used everything for i9305 for my i9305T phone and I have no problems. Try installing ClockWorkMod and flash CM + GApps.:laugh:
Click to expand...
Click to collapse
I have an I9305T running CM11, I found I had to use the TWRP for the I9305, as the one for the I9305T (which is not yet updated to 2.7) did not allow me to flash CM. CM works fine for me, and I flashed the modem.bin that I extracted out of the latest 4.3 update from Telstra (Aus) which gives me the same LTE network speeds as I was getting on stock.
1. No you will not brick your phone... difference between 9305 and 9305T is in the frequencies that the phone uses to connect to your mobile operator...95% is the same for all..but for a few countries is not...they use different frequencies to connect the phone to the network...so samsung releases a version of the phone with T at the end.
2. A custom recovery is for installing new ROMs on the phone...installing new mods...and stuff...you have access to internal parts of the device... it has a interface with different option....combo to access it: volume up+home+power
I recommend CWM recovery.
Root access is like administrator on windows...by default you can't access system files on your phone and other stuff...for safety reasons...rooting your phone enables access to that stuff...but if you are a newbie better not to root.
2.1 Here is the package: download.chainfire.eu/supersu - but at the moment i'm writing this the site is dowm.
3. Yes...the order of installing CM11 is:
a) Back-up first in case of failure - i don't do this cause it takes a lot of time and i don't have anything important on the phone...i use cloud storage.
b) Install custom recovery and enter custom recovery
c) do a full wipe - factory reset + cache partition + dalvik cache
d) install ROM
e) install GApps.
Every ROM has it's own install instructions...just follow them.

[Q] help needed

to be honest have been using samsung ace 5830 for more than 2 years but didnt face any issue before.
my friend had installed CWM and rooted the phone also.
but now it keeps restarting and i am unable to do anything.
kindly suggest what needs to be done in details.
also the above installation was done 1 year back .
so please let me know what all is needed to install or guide me for the same.
since my friend has gone abroad i cannot get much help from him.
brainstorm5 said:
to be honest have been using samsung ace 5830 for more than 2 years but didnt face any issue before.
my friend had installed CWM and rooted the phone also.
but now it keeps restarting and i am unable to do anything.
kindly suggest what needs to be done in details.
also the above installation was done 1 year back .
so please let me know what all is needed to install or guide me for the same.
since my friend has gone abroad i cannot get much help from him.
Click to expand...
Click to collapse
What Do you mean by "keeps restarting" Bro, Is it stuck on the bootanimation?
If your phone doesn't get pass boot animation and reboots, then there's only one way to fix it. Your personal files and data would be gone but I'm sure it's backed up with your google account. Watch this and follow the instructions. Installing a stock firmware using ODIN. Hope it helped
brainstorm5 said:
to be honest have been using samsung ace 5830 for more than 2 years but didnt face any issue before.
my friend had installed CWM and rooted the phone also.
but now it keeps restarting and i am unable to do anything.
kindly suggest what needs to be done in details.
also the above installation was done 1 year back .
so please let me know what all is needed to install or guide me for the same.
since my friend has gone abroad i cannot get much help from him.
Click to expand...
Click to collapse
Are you currently using a stock rom or a custom rom? Anyway you can solve this problem by just flashing back the stock rom using odin. Here is the link on how to install stock rom using odin along with all firmwares and drivers (check the "Preparations" section),
Flash stock rom on Samsung Galaxy Ace S5830 using odin
If your PC cannot recognize the phone, its usually the drivers. Once installed, go to recovery mode (hold power+ Home button) and do a wipe data/ factory reset & wipe cache (otherwise bootloop might occur). Then restart. Now you have successfully flashed the stock rom. Here is the link for rooting and installing CWM 5 on Samsung Galaxy Ace. Just flash them from the recovery mode (choose "install zip from sdcard" and then select the zip file from sdcard).
How To Root and Unroot Samsung Galaxy Ace?
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Hope I Helped
more details needed
i think so i havent given proper details since i dont know the details ...
details as per what i know...
cwm is installed (some 4.X) and phone is rooted
have apocalypse at start .... dont know what is it .. or what is it termed as ..
more over phone keeps restarting is like ... when i try to lock it ... instead of locking it keeps restarting ...
once restarted it waits thr and then when i again try to lock it .. it restarts
just now cleared all the data and cache partition .. but m tired of apocalypse or need to install it
so please tell me what is apocalypse and cwm
after installing the zip file i need no softwares in my phone since internal memory is damn bad in this phone.
dont wanna change the phone since its the 1st phone i took with my own salary ..
sorry to trouble you guys .. but i am clueless about my own phone
forgot to mention .. any application after a while force closes .. m tired of the phone but dont wanna replace it
brainstorm5 said:
i think so i havent given proper details since i dont know the details ...
details as per what i know...
cwm is installed (some 4.X) and phone is rooted
have apocalypse at start .... dont know what is it .. or what is it termed as ..
more over phone keeps restarting is like ... when i try to lock it ... instead of locking it keeps restarting ...
once restarted it waits thr and then when i again try to lock it .. it restarts
just now cleared all the data and cache partition .. but m tired of apocalypse or need to install it
so please tell me what is apocalypse and cwm
after installing the zip file i need no softwares in my phone since internal memory is damn bad in this phone.
dont wanna change the phone since its the 1st phone i took with my own salary ..
sorry to trouble you guys .. but i am clueless about my own phone
forgot to mention .. any application after a while force closes .. m tired of the phone but dont wanna replace it
Click to expand...
Click to collapse
The Apocalypse you are referring to is the custom rom that is installed in your phone. When you bought you phone, you had Samsung's version of Froyo/ Gingerbread installed in your phone. That rom is called stock rom. Custom roms are build by developers using cyanogen mod sources. Now you keep having restarts and since clearing data and cache from CWM didn't solve it, I suggest you install another rom. Now this is where you have to make a choice. You can either install a stock rom (stable, nice battery backup, etc) or a custom rom (fast, performance oriented, customizable, etc). Before you do install another rom, backup all app data using Titanium Backup. If you choose Stock rom, then follow my previous post on how to install stock rom on your phone. Now if you choose custom rom, then first we need to update CWM 4 to CWM 5.
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Download the CWM 5 zip file to SD Card and reboot your phone to recovery mode (Power off then hold Home+ Power button). Now choose "Install zip from SD Card" and choose the zip file. Done! You have successfully installed CWM 5. Now time for you to install a new custom rom. Refer the following guide for all the custom roms for our device,
Know your Device:Galaxy Ace GT-S5830 ~Root~Odin~CWM~ROM LIST
For time being use any Gingerbread roms. Download it to SD Card and then reboot to recovery mode. Now choose Wipe data/ factory reset, Wipe cache partitions, Advanced> Wipe dalvik cache, Wipe battery stats, Mounts & Storage> Format /system. Now select "Install zip from SD Card" and choose your rom zip file. Reboot and you can use your new rom. Whenever you want to install any new custom rom, just follow the same procedure. Now as for the low internal memory problem, we might have a solution. But the catch is it requires a rom with init.d support (something all custom roms have and stock roms doesn't ) and an ext partition on SD Card. First backup all the SD Card data. Now go to CWM> Advanced> Partition SD Card> Size (Max 1GB, anymore and system will lag)> Swap (0MB) and wait for it to say "Partitioning done". Now download and place CronMod script (try INT2EXT+ as it is the most stable of all) to SD Card. Now again go to CWM> Mounts & Storage> Mount /system then flash the Cronmod zip from CWM. Reboot and you are good to go. Now go to Settings>Storage to see the newly increased internal memory. Here is the link,
CronMod-INT2EXT
Hope I Helped
Wrong section mates!!
First of all, read the forum rules in order to post your questions correctly...
There's a great Q&A Thread please use it to ask for help, this the General Thread, we must all contribute to maintaining our forum in order.
Next time, post it in the correct section, thank you for understanding it
Follow @mahithm instructions to flash a fresh STOCK rom and the next tine DON'T USE CWM 4x, it's outdated, there are several recovery systems based on CWM 5x, they're the most stable for a daily usage and they're required to flash most of the custom roms

[Q] Phone fails to start installing ROM

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

Categories

Resources