Greetings fellow Earthicans!
I've been roaming these forums for several years now and have been able to fulfill all my custom rom needs by searching, trial and error. I've bricked all my phones at least once but have always managed to make the phone work better than when i first stardet modding it. This time i managed to do something i've never been able to do before and i'm therefor writing my first post here.
Yesterday i did a full wipe/format of everything available in CWM because the internal phone memory was close to full. In the process i managed to erase all my backups, which i thought was fine since i loaded my external sd with most of the custom roms and gapps available on this amazing forum.
However, when i tried to flash either one of the .zip files i get the same message "this package is for "m3", m3xxm i9305, gt - i9305 device; this is a "m0"." Even though i've had both avatar and miui ROM installed a few hour earlier. I was stuck on the boot screen, as so many other times with this and other devices.
So i searched around this forum and google and found out that m0 is the i9300 and my initial thought was "nice, perhaps i can install the custom roms of the i9300 by copying them to my ext sd and install through CWM" Which of course did not work and i realized i had to go back to stock through the download screen
So i downloaded my firmware (4.1.2 and 4.3) from sammobile.com to do a stock reset through odin 3.07. Both firmwares works fine and all of the phones functions work as intended, as far as i know.
I'm currently running 4.3 I9305XXUEMKC_I9305TLAEML1_I9305XXUEMK1_HOME.tar.md5 without any problem, but would love to be able to run custom ROMs again, but have no clue how to proceed.
I would be eternally thankful if someone know the solution to this problem i've encountered through my irresponsible actions.
/an open-source and android enthusiast
This is not i9305 q&a .
in recovery format system sdcard data and cache then boot to download mode and flash the correct stock rom for your phone via Odin .
JJEgan said:
This is not i9305 q&a .
in recovery format system sdcard data and cache then boot to download mode and flash the correct stock rom for your phone via Odin .
Click to expand...
Click to collapse
Thank you for your reply.
I've checked which of the stock rom to use and have done as you described, i can run the stock rom and currently am.
iIve rooted the phone and installed CWM through odin. When booting into CWM, and clearing as described in all guides, i still get the same error message given in my post above.
are you sure you do have the right recovery and that this is up to date?
Related
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Probably a dumb question on here but I couldn`t find it in searches..
I recently rooted my galaxy S3 and installed S4 revolution custom ROM. However after the installation it boots into what looks like a stock ROM.
The S4 ROM is supposed to be Android 4.2.2 but the ROM that is booted is 4.1.2. I installed it by copying it to the external card and putting the phone into recovery mode, I wiped cache and did a factory reset before I installed.
Can someone explain why it doesn`t boot into the new ROM and what I need to do?
Then you have not installed custom rom.
Go back to the rom and read and understand the instructions .
Multiple reasons why it failed user error the norm bad file wrong format less likely .
Use failed to install CWM recover is another .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts
Thank you! Worked now
Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).
Hi everyone
My sister updated her MEGA OTA last month. She cant remember which version she was on. I am assuming it was 4.3. shes doesnt know much,
Her phone got stuck in bootloop.
Initially a got a hard time even getting into restore mode. however after a lot of goggling and trials and errors here is where i am today :
1- I can install TWRP and/or Philz recovery and boot into them.
2- I can enter download mode
3- I have tried installing many ROMS and different versions. I was only partially successful with 4.4 versions because I get a passed message in Odin however upon restart the phone enters boot loop again.
4- I have tried multiple wipe data/dalvik cache/cache and restoring factory settings but i still get the same results.
5- Only in Philz recovery i can mount the external SD card and copy zip files. I was able to root the phone that was (but im not sure if it still is). However all ROMs zip files I tried to install (both from PC and from extSD card) wouldnt open in recovery mode.
Because I get a passed message when I install a ROM from Odin , I dont know what the issue could be. But there is something wrong that happens as soon as this phone boots up.
I seriously do not know what to do anymore. I just need this phone to be working again. At this point I dont care about warranties/ROM versions/stock or custom...
Please help and sorry for my bad English
It sounds like you need to download the stock rom and flash it in Odin (you gotta put the phone in download mode to flash in Odin). The stock rom can be found on the sammobile website in the firmware section. That should get you back to square one (stock rom, stock recovery, no root). Then you start over from scratch.
Sent from my SGH-M819N using XDA Free mobile app
Thanks
I did and I still get the same problem.
In fact after installing stock rom, i could not enter "stock" so I installed philz recovery, logged in philz and wiped cache a couple of time, did a factory reset.
and yet when i restart , the phone is stuck in bootloop.
Maybe she has a Galaxy Mega with a repaired screen. Starting with 4.4 Samsung only supports a digitizer with Synaptics brand chip. It's a big mess and there are countless screens and digitizers made worthless. I think unofficial 4.4 by Cyanogen and others might work, but not official Samsung. With some Galaxy Megas you get a bootloop. With others it boots however the digitizer and touch functions no longer work. I don't know how to go back after you are on official 4.4 because last I saw, there was no root for it. If I'm wrong, someone else please clarify and continue to help.
IMHO only one way out from such situation is try to flash MegaFire MJ2 which is derived from stock 4.2. It's only one 4.2 ROM which can be safely flashed onto KK.
Iformation about MegaFire you can find HERE
I'm trying to fix an ace gt-s5839i (rooted with stock ROM) that won't boot up, it always goes straight to recovery.
I've searched for fixes on this forum (and others) and the fixes i have tried so far have not worked, these include flashing a new recovery (clockwork), flashing a whole new custom ROM (razordroid and CM) and flashing stock ROM through Odin, also it won't even let me wipe data through recovery as it will just stick on formatting data.
Any idea what is up and how i can fix it? The phone belongs to a relative of mine and he said he woke up one day and the phone was in bootloop, he took out the battery and put it back it back in and ever since then it just goes straight to recovery.
fedor12 said:
I'm trying to fix an ace gt-s5839i (rooted with stock ROM) that won't boot up, it always goes straight to recovery.
I've searched for fixes on this forum (and others) and the fixes i have tried so far have not worked, these include flashing a new recovery (clockwork), flashing a whole new custom ROM (razordroid and CM) and flashing stock ROM through Odin, also it won't even let me wipe data through recovery as it will just stick on formatting data.
Any idea what is up and how i can fix it? The phone belongs to a relative of mine and he said he woke up one day and the phone was in bootloop, he took out the battery and put it back it back in and ever since then it just goes straight to recovery.
Click to expand...
Click to collapse
Ok , I did mention troubleshooting method for similar cases like you in many posts here mate ,, Just get yourself stock s5830i firmware compatible with your Region/Carrier and make a wipe / split packages with the help of splitfus2 or simply use one of the pre-made packages >> Follow my instruction @post#4 from the line :"1. Download one of the newest ,,," to the end of the post .
btw razordroid was obsolete and buggy at the best of the times anyway , try newer/more stable from development sub forums .
After resolving your boot loop and partition issues you may flash your newer s5839i stock fw from i,e: sammobile database on top of your s5830i over Odin ( normal flashing procedure ).
Hope I did Help you