Develop Bugs

Problem with flashing custom rom

Ive got this message in cwm when was restoring (jj's hybrid for locked bootloader): no app2sd partition found, any ideas?
Locked Bootloader Arc S.
When i want to format sd-ext --> same message.
Prince

Bump
Prince

That means that CWM didn't find a second partition in your SD card used by Link2SD.
Is it working fine, JJ ROM?

Im just wondering if i can flash it with this 'error'.
Prince

I presume jj's rom has app2ext built in, but it shouldn't affect the rom. But check on the rom thread.
sinkster©

I was asking, but no1 replied.
Prince

It will work. That "error" is just a check if a sd partition exists to make use of. Wont affect sysyem if missing.
Typed down from the sky with sexy LT15i

Thx then xd
Prince

hints that migh be helpful to prevent trouble when flashing custom roms & kernels
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i myself use 3 different devices, all rooted and running on pac 4.3, always latest nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks

Pulkit_i21 said:
hi ...i need your help...i am also using xperia arc s (2.3.4), rooted. i tried to install ultimate HD 5 around 6-7 times from different ways, all instructions on internet i followed, in my arc but always it stuck on sony ericson logo and i need to flash it again and again....please help me..why i a, not able to install ultimate hd ..waiting for your reply thanks
Click to expand...
Click to collapse
You must use ICS kernel, either unlock bootloader and install custom ICS kernel, or first install/update to stock ICS and then follow the same method.

i already did 6 times
i already tried 6-7 time to install custom rom when it stuck on sony logo i flashed it with orignal stock rom and tried again but every times same problem arise. now i am not understanding where i missed
Someguyfromhell said:
You must use ICS kernel, either unlock bootloader and install custom ICS kernel, or first install/update to stock ICS and then follow the same method.
Click to expand...
Click to collapse

Pulkit_i21 said:
i already tried 6-7 time to install custom rom when it stuck on sony logo i flashed it with orignal stock rom and tried again but every times same problem arise. now i am not understanding where i missed
Click to expand...
Click to collapse
Kernel. You must use appropriate kernel!

Already tried
i already tried flashing kernel too.....and also in ultimate HD there are option of instaling with locked boot loader.................................i just want to install ultimate HD..........
Someguyfromhell said:
Kernel. You must use appropriate kernel!
Click to expand...
Click to collapse

Pulkit_i21 said:
i already tried flashing kernel too.....and also in ultimate HD there are option of instaling with locked boot loader.................................i just want to install ultimate HD..........
Click to expand...
Click to collapse
Did you install full ICS firmware with kernel prior installing Ultimate HD ROM?

yes
yes i did around 6 times after bootloot i goot in my androing so i flash 2.3.4 gingerbread ftf file again in it
Someguyfromhell said:
Did you install full ICS firmware with kernel prior installing Ultimate HD ROM?
Click to expand...
Click to collapse

Pulkit_i21 said:
yes i did around 6 times after bootloot i goot in my androing so i flash 2.3.4 gingerbread ftf file again in it
Click to expand...
Click to collapse
First install stock ICS firmware, Android 4.0.4 (4.1.B.0.587 or 4.1.B.0.431), and then install the custom ROM. Did you do it so? Can you write the file, which you used?

no..i flashed only base version 4.0.2.A
i always flash "LT18i_4.0.2.A.0.58(2.3.4)_HK" after every bootloop, i not tried to flash 4.1.B.587....few month before tried it to flash but i think it is not able to flash because of system partition is is less because of 4.0.2.................well benifit of installing upgraded rom "4.0.4 (4.1.B.0.587 or 4.1.B.0.431)" and are you sure after that i will able to install it..?
Someguyfromhell said:
First install stock ICS firmware, Android 4.0.4 (4.1.B.0.587 or 4.1.B.0.431), and then install the custom ROM. Did you do it so? Can you write the file, which you used?
Click to expand...
Click to collapse

[Q] Flashing a rom...

Extract Rom and grab the boot.img
Make a Full Wipe (Factory Reset,System,Cache,and Davlik Cache)
Install ROM
Fastboot flash boot boot.img
REBOOT
Enjoy!!!
With these instructions *i've never flashed a rom before* I should download the rom, extract the boot.img where I have the fastboot.exe on my computer, do full wipe, put the zip file on my sd card and install in recovery, reboot and go into fastboot mode and flash the image, and then reboot again right? Or am I missing something? Sorry, as I said i've never done this before.

Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first

Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp

donhashem.dh said:
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Click to expand...
Click to collapse
atonz said:
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
Click to expand...
Click to collapse
Thanks for your help. I actually went ahead and tried mine first, to see because i'm impatient and it worked totally. Thanks everyone!!!

Ok, I'm having issues with this installing ROMs/kernels.
I entered fastboot
I flashed the boot.img for the kernel I want
I toggled to hboot
I went into recovery (twrp 2.2.0)
I did wipe -> Factory Reset, Cache, Dalvik Cache, System
I installed the zip for ROM I want to use [found here]
I flashed the zip for the kernel I want to use (to install the libs) [found here]
wiped dalvik/cache again
reboot system
Now my phone just bootloops. Not sure what I did wrong.
I should mention I did get it to boot once back when I first installed the ROM because I did a normal reboot not a reboot into fastboot (was doing the install the ROM then the boot.img approach at the time) and hadn't installed any boot.img (still had the stock) but ever since I overwrote it all i get is bootloops.
Also, I even tried the same steps using the boot.img included with the ROM as opposed to the other one.
To make things worse, backups are almost useless because with the phone being S-ON even if the boot.img is being backed up, it not getting restored. A point made extremely obvious by the fact that it still bootloops after restoring my backup.
I am currently running the RUU but am hesitant to try and install any ROMs without some idea of what I did wrong.
Any help is appreciated.
-----EDIT------
Ok, I think the problem was the recovery I used. I installed the CDMA TWRP from the OneV tool, and one linked in the cdma development thread and a couple CWM version found there as well. But what seemed to work was getting TWRP straight from the source. After running the RUU I installed version 2.3.1.0 and repeated the steps using the boot.img included in the ROM and it worked. If I'm feeling adventurous later I'll try my luck with the other kernel lol.

[Q] Can I return to stock Koodo?

Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.

If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.

arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).

Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.

arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!

Flashing JB Roms causes bootloops

Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.

I got a bootloop before when trying to flash JB roms and what I did was restore to original state (using the bad flash recovery technique), and then not rooting it but installing cwm through Odin and dirty flashing the Rom in cwm. Once it flashed I used it for a few to make sure that everything was working correctly. Then I got the goo manager app and got twrp. After that I followed all the steps in the OP (Jedi jelly) and flashed the Rom. Now I'm running Jedi jelly 3.1 perfectly. Hope this method helps.
Sent from my SAMSUNG-SGH-T989 using xda premium

djtreo said:
Hello guys!
As the title says, I keep on having boot loops after flashing any custom JB Roms (Jedi, LiquidSmooth, CM Nightly, Slimbean). I'm not new to flashing roms (I got LG units though, SU660 and KU5900). When I tried flashing ICS Roms, I don't have any problem. But I want JB that bad!
I followed KonstantinKeller's thread of restoring/recovering from a bad flash (going back to GB), rooted following Melvin's thread. Then did all the prerequisites..like the common wiping of data, clear cache & davlik. But then again after flashing JB roms listed above, I keep on having boot loops!
What did I do wrong? This ain't my first time flashing (first time on this phone -T989- though)
I read some posts with almost the same problem, but I don't think I found a solution for this. Any good soul that can extend their help is highly appreciated. Thank you in advance.
Click to expand...
Click to collapse
are you using darkside scripts to wipe? because they will cause bootloops

skinsfanbdh said:
are you using darkside scripts to wipe? because they will cause bootloops
Click to expand...
Click to collapse
is there any way to reverse the loop that the darkside wipe is causing?

it REALLY sounds like the recovery u are using is TOO OLD. Make sure u are using the latest version of twrp (2.3.3) to flash all jellybean roms.
TWRP is backwards compatible and touch capable, so if you're worried about flashing GB or ICS ROMs it'll do the trick just fine
it is however a requirement for flashing all 4.1 ROMs.
Basic install instructions:
make sure u have root
download goo manager from play
open > menu > install open script recovery
agree to everything, but make sure t989 is in the downloaded image name
reboot to recovery u should see twrp

[Q] [HELP] LT18i and CM9

I've been trying for the past two days to flash CM9 (cm-9.1.0-anzu) on my Arc S (LT18i), but with no success, as each time I try to install it through Recovery mode (which I installed using RecoverX, as xparts and CWM Rom Manager don't seem to work) I run into the Status 7 error.
I read all I could here about this error 7, but nothing seems to work to me (reinstalling this or that kernel, et cetera). And each time I have to flash the original ftf for the stock GB (lt18i_62.ftf). My bootloader is unlocked.
This is basically my procedure, and obviously something must be dead wrong with it:
1) After some failed attempt, I flash the stock ROM back via Flashtool.
>Now I'm on this setup:
Android: 2.3.4;
Kernel: 2.6.32.9-perf [email protected] # 1
Build: 4.0.2.A.0.62
2) I root succesfully via ERoot.
3) I install CWM through RecoverX.
4) I boot it to recovery, wipe data, cache, delvik, etc, and attempt to flash any custom rom (I've tried CM9, CM7 and some "PAC_iyokan_JB_4.1.2-v19.3.0"), all of which give me the Status 7 error.
What gives? Should I be flashing a specific kernel somewhere or something?
Thanks in advance.

Don't wipe /system, this causes the issue, as CM builds are made to check, that the correct firmware is being installed the phone (not the wrong phone model ROM).
Also, CM9 requires custom kernel, so instead of rooting and installing recovery, flash the custom kernel and use it's built-in recovery.

Which wipes should I do, then? None? I'm not sure which wipe wipes /system.
Which custom kernel is that? Surely not the boot.img included in cm-9.1.0-anzu.zip, right?
And this custom kernel, should I flash it using flashmode or fastboot mode?

zynphull said:
Which wipes should I do, then? None? I'm not sure which wipe wipes /system.
Which custom kernel is that? Surely not the boot.img included in cm-9.1.0-anzu.zip, right?
And this custom kernel, should I flash it using flashmode or fastboot mode?
Click to expand...
Click to collapse
Wipes - Same as earlier, but do not choose format /system.
boot.img is the custom kernel file. And it can only be installed in fastboot mode.

Someguyfromhell said:
Wipes - Same as earlier, but do not choose format /system.
boot.img is the custom kernel file. And it can only be installed in fastboot mode.
Click to expand...
Click to collapse
I don't think I was wiping /system (I'm not even sure how that is done), but installing the custom kernel and then installing CM through its own recovery did the trick, thanks a lot!
Though CM9 is pretty old, so I now itch to try CM10... Is this procedure (installing the boot.img kernel, running its recovery, flashing ROM+gapps) the same for all CM ROMs, or all LT18i ROMs, for that matter?
Thanks again!

zynphull said:
I don't think I was wiping /system (I'm not even sure how that is done), but installing the custom kernel and then installing CM through its own recovery did the trick, thanks a lot!
Though CM9 is pretty old, so I now itch to try CM10... Is this procedure (installing the boot.img kernel, running its recovery, flashing ROM+gapps) the same for all CM ROMs, or all LT18i ROMs, for that matter?
Thanks again!
Click to expand...
Click to collapse
Yes it's pretty much the same... And always use the kernel inside zip...
Sent from my Xperia Neo V using Tapatalk 2