I have searched xda and the WWW., and have not found anything similar to the issue that I am encountering.
1. I flashed stock rom UCLB3 (http://forum.xda-developers.com/showthread.php?t=1524081) and flashed Entropy512 Kernel
2. Flashed CM9 (http://forum.xda-developers.com/showthread.php?t=160184)
3. Flashed just fine
Here is the issue:
I wanted to put MIUI 2.3.2b Stable ROM and during the flash progress in CWM Blue/Red (CWM ver, doesn't matter), I get stuck at "checking BML/MTD" and all of the sudden the Samsung Logo flashes followed Cyanogenmod 9 flash intro, but then the phone just shuts down.
This only occurs when I try to flash MIUI ROMS, when before I was able to flash MIUI, prior to Cyanogenmod 9 flash.
The phone can be reverted back to stock UCLB3 and flashed with any ROM non MIUI based, but just not MIUI.
Has any one encountered this before or can lead me to possibly checking error logs to see what could be causing the issue?
Thank you in advance
If you really dis search www you should know the recovery you have does matter....
What I would do is Odin back to stock flash cm7 then flash miui ...
Flashing. Miui from red recovery wont work because
It red recovery uses voodoo partitions not compatible with cm7/miui
when you do flash from red cwm you should reboot back into recovery and reflash since.it converts your data partitions
(You should have blue 5.x.x recovery once you reboot into recovery again)
Or re download the rom and see if that's the issue
Sent from my SAMSUNG-SGH-I717 using XDA
Thank you for your response.
I reverted back to stock Froyo. I apologize but I neglected to say that I tried loading the MIUI ROM via the Blue recovery and still no go.
I have flashed CM but not CM7 instead CM9 and then tried flashing MIUI no go.
Not sure if CM9 is a completely different ROM from CM7 but I will give that a try.
Note that the 2.3.2 Stable MIUI rom is a ported ROM from I9000 models and currently I am able to flash non ported ROMS such as MIUI SHOCK & AWE.
I think where the issue may be residing is the fact that I am also getting an MBR Checksum Failure message when booting to Recovery.
Not sure if this whole thing is hopeless as no one seems to know how to get rid of the Checksum errors, but I am still able to flash ROM's on my phone just not ported MIUI Roms with file designation of i9000; ie miuiscotland_I9000-2.3.2b-Stable.zip.
Regardless. Thank you for your time reading and replying. I very much appreciate the input.
jayRokk said:
If you really dis search www you should know the recovery you have does matter....
What I would do is Odin back to stock flash cm7 then flash miui ...
Flashing. Miui from red recovery wont work because
It red recovery uses voodoo partitions not compatible with cm7/miui
when you do flash from red cwm you should reboot back into recovery and reflash since.it converts your data partitions
(You should have blue 5.x.x recovery once you reboot into recovery again)
Or re download the rom and see if that's the issue
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Thank you for being reasonable and for having a good reply
I like the way you replied it was very "grown up " to say unlike the little kids who just rant about BS. I appreciate it.
All I can say is try flashing other MiUi bulids
There is one who is very very stable but forbidden to post here on xda :cough: galnet :cough: I heard it was really good I tried it
Back when I had my infuse and its really stable ....apart from the regular MiUi bugs
But Google it since we can't really post links here on xda regarding galnet miui
Sent from my SAMSUNG-SGH-I717 using XDA
Since I want to flash the thalamus kernel on my Nexus S with JB, I have to be on a rom and given that no JB factory image is available yet I don't really get what I should do.
When the OTA came out I was on a deoxedex, zipaligned, etc. stock rom of ICS, so, in order to elude the error status 7 issue I flashed the 4.0.4 factory image from google and then flashed the OTA update.
If I want to flash a JB rom, do I have to re-flash an ICS rom? And if so, can it be a non-stock rom or I would get the error status 7 message again?
No. You just need to make sure you have a custom recovery, like CWM. I was on ICS and then flashed a JB ROM with no issues.
chronophase1 said:
No. You just need to make sure you have a custom recovery, like CWM. I was on ICS and then flashed a JB ROM with no issues.
Click to expand...
Click to collapse
Well, factory images just came out so it's fine now.
Haha. I was JUST about to post that. Good news for everybody.
Ok so im planning on flashing in cyanogenmod v9.1 and then up to ultragen v1.1 with the jb and tw5 taste, now if i do this do i still need to flash in a version of gapps or is there one in the ultragen rom, and in order to do the flashing can i use the cmw-based voodoo lagfix recover 5.0.2.7 to flash in the cm9.1 or do i need to use odin or something, im kinda new to all this, all ive done to the phone so far is recover from soft brick by using odin to flash back to stock and then using some off site instructions to root the phone which also apparently came along with the voodoo recovery, so im basically a noob at this
jimmy2989 said:
Ok so im planning on flashing in cyanogenmod v9.1 and then up to ultragen v1.1 with the jb and tw5 taste, now if i do this do i still need to flash in a version of gapps or is there one in the ultragen rom, and in order to do the flashing can i use the cmw-based voodoo lagfix recover 5.0.2.7 to flash in the cm9.1 or do i need to use odin or something, im kinda new to all this, all ive done to the phone so far is recover from soft brick by using odin to flash back to stock and then using some off site instructions to root the phone which also apparently came along with the voodoo recovery, so im basically a noob at this
Click to expand...
Click to collapse
No need to flash the gapps with Utragen ROM its included.
Use CM recovery to flash no need for Odin ... cm 5.0.2.x is fine.
I always go to cm 9 then work up never had a problem.
Ultragen is a very stable ICS based rom .. I used it for awhile.
Be sure you follow the OP`s flashing instructions.
If you want JB try slim 4.1.2 its very stable...if you can live
without GPS.
Sent from my Nexus 7 using xda premium
Thanks, everythings installed and its running beautifullyi thanked your post ill mark this thread as solved
I am trying to update my Radio/modem file with the JB Android 4.3 Radio file. It requires that I install CWM 6.0.3.7. Can I install this alongside my TWRP 2.6.3.0 installation or as I have read, it will overwrite my TWRP recovery mode? If it will overwrite, how do I switch between? Just reflash through ODIN using PDA? That seems like a lot of work and the possibilities of breaking might be high just overwriting Customer Recoveries?
If I would install this JB Radio for Android 4.3, how would I go back to GB? I can't find a single GB Radio/Modem. Could I use Radio files for GB instead of wiping and installing stock GB ROM [No Root, No Custom Recovery, but it includes the GB Radio/modem]. The reason I am worried about this, if I need to load my original stock GB 2.3.6 backup with root from my nandroid, I would need the original GB Radio and the nandroid backup/restore feature doesn't include that. All advice is greatly appreciated.
The Radio Does Not Get Backed Up By Cwm/twrp Backup(nandroid) Method.
Click to expand...
Click to collapse
[RADIO][UCMC1] For I727/I727R [09-APR-2013]
http://forum.xda-developers.com/showthread.php?t=2228292
[Q] I have CWM and TWRP installed, is that OK?
http://forum.xda-developers.com/showthread.php?t=2122152
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012] [It has ICS radio files, but no GB files]
http://forum.xda-developers.com/showthread.php?t=1754473
Just flash it with twrp. It'll work just like if you did it with cwm.
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Pick a recovery and use it. Backups are not cross compatible. If you make a backup with cwm it won't work with twrp.
You can flash radios with either. Just pick one.
Sent from my HTC One using Tapatalk 4
lowao said:
I have read that some of the zip files does work with TWRP as well. However I am interested in using the following Custom Rom [SuperLite AOKP JB 4.3 v1.0]. That installation requires CWM 6.0.3.7, because it will prevent the infamous black screen reboot issue. What about GB radio file & installing on top of or installing side by side TWRP & CWM?
[ROM][AOKP]SUPERLITE AOKP JB 4.3 V1.0| BYO | SLgapps | SEPT 30/13
http://forum.xda-developers.com/showthread.php?p=46066949
Click to expand...
Click to collapse
If you have not already installed a 4.3 ROM, then you are recommended (nay, required) to use CWM 6.0.3.7 to do the initial wipe and install, after that you can switch to TWRP for any flashing after that.There is something that 6.0.3.7 does to the data partition that TWRP doesn't, on the initial setup. Once that is done, it doesn't matter. Flash the JB radio when you flash the 4.3 ROM. And going back to GB if you need to is fairly simple, just follow Vincom's guide. There are lots of flashable zips of GB radios you can use.
I am still a bit confused regarding TWRP & CWM being installed at the same time or side by side. So, let me get this straight. If I want to install JB 4.3 ROM, I must first boot into ODIN, install CWM through ODIN, reboot, boot into CWM, wipe the system, reboot, boot back into ODIN, install TWRP, reboot, boot into TWRP, install the JB 4.3 ROM, and finally preform the last reboot. Is this correct & it won't break either of the custom recoveries? However rpr69 said "switch back to TWRP." Are you inferring TWRP & CWM can be installed side by side? If so, how do I access one over the other?
Regarding GB's radio files:
Which of the following links is the Radio/modem files? Is it the second one? I know of them is the official stock ROM and the other requires the OTA updates. However the poster didn't include the OTA updates yet...
ATT-UCLI3-odexed-cwm.zip http://d-h.st/rDZ
kernel-ucli3-sgh-i727-RD01-cwm.zip http://d-h.st/QfR
[ROM][ICS][UCLI3][09-NOV-2012] Stock odexed & deodexed UNTOUCHED
http://forum.xda-developers.com/showthread.php?t=1982467
Try this, wipe cache and dalvik.....no promises lol [Link is dead.]
https://dl.dropbox.com/u/60567424/modem-UCLI3.zip
http://forum.xda-developers.com/showpost.php?p=33344009&postcount=22
Sadly no link for UCLI3 [GB's Radio files.]
[ROM][ics][uclf5] •∞ EMBRYO •∞ 4.1 •∞ [08-jul-2012]
http://forum.xda-developers.com/showthread.php?t=1754473
The 1Stop post from Vincom:
http://forum.xda-developers.com/showthread.php?t=1785999
Sadly there are no more links for GB / UCLI3 radio files.
I know you posted but its confusing, let me simplify, I hope:
im assuming you have either cwm or twrp installed, if on stock read this.
you cannot have two recoveries installed at the sametime:
recovery install procedure:
if not on cwm6037 flash cwm6037 with what ever recovery you have now and reboot back into recovery.
then flash any custom jb4.3 rom, preferably latest cm10.2 nightly found here and reboot rom at least twice.
if you like cwm 6037 stay with it, I don't, or else just flash twrp 2.6.3.0 w/cwm 6037 and reboot back into recovery or rom.
now you can just stay w/the cm10.2 nightly you flashed with cwm 6037 or flash any other rom w/twrp 2.6.3.0 which is now your installed recovery.
that's it you should not have the reboot problems on any jb4.3 roms.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
above recovery install procedure is only if a jb4.3 rom on its 2nd reboot just has a black screen and wont boot into rom, but 2nd boot does usually take longer than normal upto a full minute.
if flashing a rom or restoring from nandroid(recovery backup) prior to jb4.3 and then later decide to flash a jb4.3 rom you need todo above recovery installation procedure b4 flashing a jb4.3 rom.
restoring backups only work with whatever recovery they were made with, you cannot restore a cwm backup w/twrp recovery and vice a versa.
newest versions of recoveries should restore backups made with their older versions.
why do u want an old radio, they will not work w/jb roms
old radios are linked in the 1stop sticky under "old stuff".
installing the radio has nothing todo with the recovery you are using.
flash jb radios for jb roms which happen to be all the current roms.
reread the radio section in the 1stop sticky.
I linked this post in the recovery section of the 1stop sticky
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
lowao said:
Thank you vincom for explaining the process of using both CWM 6.0.3.7 & TWRP 2.6.3.0 together. I am familiar with backups ONLY working with their original customer recovery. I didn't even think about older versions of backups (not) working with newer custom recoveries. Was there an issue working with older backups in the past?
The reason I need the old GB Radio/Modem files, because when I have to return the phone to stock & load up my old Gingerbeard nandroid, I will be able to return it back to AT&T with the original Radio files and the original Gingerbeard OS. Anywho, thank you for the GB radio. I really appreciate it!
Click to expand...
Click to collapse
u can return any phone that has any stock firmware, with our phones that would be stock jb4.1.2 and using odin would be the way to do it , link in my sig. this is assuming your carrier used the latest firmware as with att and rogers.
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
these are untouched full official stock firmwares( radio, recovery, kernel and apps/bloatware), just use odin and flash whatever version you want, all info is in the restore to stock sticky
lowao said:
I am with AT&T and I never got the official ICS or JB through updates. Actually, I thought ICS was discontinue, because it was bricking phones. Thus the stock ICS & JB Roms here were ported over?
Click to expand...
Click to collapse
nope, both are fine and are still available officially. You don't need gingerbread to return it.
Sent from my HTC One using Tapatalk 4
I have to go to Samsung's website and download their Kies software to upgrade to Jelly Bean right? It won't be pushed out through Settings > About Phone > System Update then?
Or you can use Odin.
Sent from my HTC One using Tapatalk 4
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
beachmiles said:
So if you're flashing 4.3 ROMs just use cwm? Went from twrp to cwm and back to twrp and am getting the same black boot screen on a slim 4.3 weekly.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
To properly set everything up, you need to use the recommended CWM for 4.3, do a full factory wipe, and make sure that data is formatted. Then install the ROM and boot it up. Reboot to verify it works properly. Then you can go to TWRP 2.6.0.1 or later.
I've been using twrp since release and not had any issues why do we need cwm? What's the technical reasoning.
Sent from my XT1080 using Tapatalk
Didn't work
I followed this procedure exactly and it still didn't work.
I gave it ten minutes between boots and ended up having to pull the battery each of the three times I rebooted.
Fortunately I've gotten into the habit of making a backup before flashing, so it was just a loss of 45 minutes of my evening.
I was trying to get the latest CM10.2 Stable build. Has anyone gotten this thing to flash and work as well as 10.1.3 RC2 or 10.1.3 Final? This issue started for me with the second 10.2 Nightly.
...
Just NOW began seeing the replies to the main post. I don't have ANOTHER fresh install in me: I've already had to do that twice with the 2012 Nexus7 and once with the Skyrocket in the last six weeks.
Hello.
I currently have my pico with stock rom, with sense 3.5. and i'm tryin to flash a new rom, but every time i try to flash one from this thread ( http://forum.xda-developers.com/showthread.php?t=1754876 ) i got stuck on htc logo screen. and i cant get passed it... i've wiped everything, reflashed kernel, reflashed stock, but still cant get it to work. maybe these kernels arent for stock roms, if they're not, can you point some kernels that work on stock?
thanks in advance.
Stock rom should have stock kernel too.
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Red Devil said:
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Click to expand...
Click to collapse
where can i find those gingerbread kernels? so if they're inside the "rom.zip" is it possible to "extract" them to a flashable zip? only the kernel withouth the rom itself...?
Gingerbread kernels are in the Index of all kernels..
From the ROM.zip if you want to extract them then just extract the boot.img normally and also extract the modules from the zip .. in /system/lib..
In fastboot mode flash boot.img via :
Code:
fastboot flash boot boot.img
and
then via adb push the modules. I suggest you search a bit and find some answers yourself . Its easier that way cause these questions have been answered millions and millions of times. So use the search function
i've searched, and believe me when i say that i havnt found anything about this... all the kernels i go for, on the thread only talks about the kernel itself and not the roms compatible... and i've tried that method and got stuck on htc green logo... thanks for answering
these kernels work on stock rom:
1- cranium kernel
2- ateeq kernel
3- garuda's kernel
search them in the development thread I hope you'll find them.
i've tried all those kernels... one by one and never got passed the htc green logo... always get stuck there... i tried flashing trough fastboot and trough recovery... nothing works... any other suggetions?
try to flash ateeq rom then ateeq kernel..it works for me.
but i dont want to have ateeq rom, i want to stay with my stock rom, but change the kernel... only that. but thats for answering. i'm getting used to the idea that i cant be changed (the stock kernel).
thanks
Need urgent help
i had rooted my pico months back and was on different custom roms......now i want 2 get back to the stock rom which i have downloaded Odexed Stock ROM Flashable Zip (With Link2SD Support)(Revision 3)(http://forum.xda-developers.com/showpost.php?p=40385554&postcount=76) and i have flashed this rom 5 - 10 times and everytime i reboot after flashing the rom.....i am stuck on htc boot logo.....can u plssssss help