[Q] In between ROM's N7000 - General Questions and Answers

Hi so I was running Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1 (this is a link to the specific ROM) http://forum.xda-developers.com/showthread.php?t=1970626
So today i decided i wanted to run 4.2.1 and found StuNNeR had a new one for 4.2.1 (Link to ROM) http://forum.xda-developers.com/showthread.php?t=2071669and it looked pretty good so went through the usual process.
There is a warning on the page saying "Make sure to run CM9/10 or an AOSP-based ROM : FLASHING/WIPING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
Now Ultimate is TW based so could posibly be considered based on a stock ROM but is not ICS its JB so I thought I was safe but now what happens when i go to actually flash the ROM (click on the .zip file) it very quickly runs a process for approx 2 seconds then shows a android man with his guts open and a red exclamation mark (I attached a image below I found off the net of the man for reference) and that's as far as i get obviously it hasn't correctly installed the new ROM and I have tried redoing the process 3 times i have attempted to let it boot but it doesn't it just sits on the initial Galaxy Note splash screen and goes no further. Unfortunately I had recently removed my Recovery so I cant use that.
Any assistance would be much appreciated on how to get my phone working again. The only option i can think off is using ODIN? But I would only like to do that as last resort.

Related

[Q] Rom Installation Problem

Hi,
I tried almost all the roms to see wich one fits me the most and when testing all the roms I came across a problem that I can't manage to solve myself.
Here is the problem:
I downloaded Elegancia rom (ICS) and it worked fine, installed fine, etc. But I saw that they had a rom Elegancia (gingerbread) so I thought what's the diffrence and wanted to put the gingerbread rom on my phone. But here starts my problem. After installing the rom like I always did and starting up my phone, it keeps booting (htc logo, elegancia logo, off, htc logo, elegancia,logo, off,...). So I tried many diffrent roms again to see where the problem lies and it seems that I can only use ICS based roms now. The gingerbread roms (wich I also tried before) doesn't work for me anymore and after installation of a gingerbread based rom it keeps starting up.
Can anyone tell me how to get the gingerbread rom back to work?
Greetings Crasherke
you had to install a other firmware, dont know the number but youll find it in the firmware thread use something under the newest it will help
edit: here it is download and install 1.17 and it will work
http://forum.xda-developers.com/showthread.php?t=1459767
EDIT2: And next time search! here are a lot of threads with the same problem! For example (Want back Gingerbread) it is too much work for you to search first than make a thread?
I found a firmware thread and read it. If I'm right, the I have the 3.24 version and I need the 3.12 version for gingerbread to work. It wasn't smart of me to assume that a higher version of firmware is compatible with all previous roms. Thanks for the quick reply and you point me right back into the right direction.
Greetings Crasherke

[Q] How to downgrade From ICS to Gingerbread?

I have a Nexus s with 4.0.3 flashed via bootloader.How can i downgrade to 2.3.x without root,cwm or debug(cause it isn't working) ?
i've tried several methods but none of them worked(Odin,Heimdall)
They all requires me to enter download mode with debug enabled.My debug mode is enabled but as far as i read on xda,the degub is not working in this version of ICS.
my question is : how can i downgrade to ANY firmware from this ICS version
P.S. Entering recovery mode is not an option...the phone simpli enters in a recovery/download mode - loop and keeps restarting.
Please respond fast.10x
The way I did it was to download Clockwork Mod app and scroll down to where it says stock... then 2.3.3. Once u flash that you'll lose root and an update to 2.3.x will be prompted to ya. If it doesn't then Google (Download) 2.3.4(x) and manually update. What model do u have btw?
- Google
You need to root is the basic moral here. Nothing else is really worth the effort of getting it done.
Hi
If the procedure for the nexus is the same as it is for the S2.
It should be straight forward.
Download your ROM, if its Orange you want here is a good link, I used it myself today:
http://androidromupdate.com/2012/02...-i9100p-firmware-updates-list-and-stock-roms/
The ROM I used was the NON WIPE type - I9100BVKJ4_I9100ORAKJ4_ORA
I include a picture of what I did.
I was initially on a custom ICS 4.0.3 XXLPH and have gone back to Orange stock rom.
Load the integrated Rom just into the PDA window - connect your phone in download mode and start, and that should be it!
Don't check re-partition or anything else.
Keep trying it will work.
I also had an initial prob whereby I installed the wrong kernel and the phone screen was messed up and seemed to be bricked and to get it back I loaded odin up.
Put phone in download mode.
Checked re-partition - unchecked 'auto reboot and f.reset'
Used a PIT (partition file)
Used a kernel file suitable for the S2 in the PDA window and pressed 'start'
This seems to have repartitioned and wiped the mistake and unbricked the phone.
This loaded and the phone booted - no messed screen.
Then I continued to accomplish the ROM switch over.
tsam19 said:
Hi
If the procedure for the nexus is the same as it is for the S2.
It should be straight forward.
Download your ROM, if its Orange you want here is a good link, I used it myself today:
http://androidromupdate.com/2012/02...-i9100p-firmware-updates-list-and-stock-roms/
The ROM I used was the NON WIPE type - I9100BVKJ4_I9100ORAKJ4_ORA
I include a picture of what I did.
I was initially on a custom ICS 4.0.3 XXLPH and have gone back to Orange stock rom.
Load the integrated Rom just into the PDA window - connect your phone in download mode and start, and that should be it!
Don't check re-partition or anything else.
Keep trying it will work.
I also had an initial prob whereby I installed the wrong kernel and the phone screen was messed up and seemed to be bricked and to get it back I loaded odin up.
Put phone in download mode.
Checked re-partition - unchecked 'auto reboot and f.reset'
Used a PIT (partition file)
Used a kernel file suitable for the S2 in the PDA window and pressed 'start'
This seems to have repartitioned and wiped the mistake and unbricked the phone.
This loaded and the phone booted - no messed screen.
Then I continued to accomplish the ROM switch over.
Click to expand...
Click to collapse
Don't do this. The method for the Nexus S is definitely NOT the same as the SGS2, or even the SGS. Although it may be possible to use Odin or Heimdall, it is not recommended. We already have enough freedom to do as we please.
I thought all android / samsung phones would follow the same procedure for flashing new roms or unbricking via Odin?
Kies is useless for updating as we all know.
So what other methods beside Odin or Heimdall can be used on the samsung nexus?
Cheers for clarifying though, I was only tying to be helpful
galaxy 2 ics to gingerbread
dear all
i am much upset that i upgrade my galaxy s2 to ics 4.0.3 , it is much laggy i want to downgrade it to gb 2.3.5 or 2.3.6 , can anybody help me to do this , with the all the steps and downloading links of the exact files , i tried alot many times and when it is done on odin with pass message , cell restarts and with error screen .
thanks in anitcipitation
Regards
Shoaib Hassan
i've just downgraded to 2.3.2 i used the rom wiper from bm and then simply flashed the oxygen rom over it
the only way and easily is odin.just go to downloading.make sure to download the correct modem ,baseband and needed files by cheking your nexus s version.ex.i9020t,i9023 .there are not the same version,and will use different modem,baseband ...
I also want to downgrade from ics to gingerbread too, by pure luck i managed to upgrade to ics (i'm completely new to this) but having had this on my phone for awhile, I want to return to gingerbread...
I'm currently grabbing kernel_I9100xwkj3 (couldnt find xwkj1 anywhere)
and
gt-i9100_o2i_i9100xwkj1_i9100o2ik11_i9100xxk14
to use with odin?
question is... is this all i need and is there anything i need to be aware of?
You need to make use of fastboot and flash the stock GB rom from factory images provided by google, then you can flash cwm and then flash any rom you want
it is because cwm can flash roms with android version up but not down means that you can flash 4.1 if u have 4.0.4 but if you are on 4.0.4 then you cannot flash 2.3.x
Hope it helps

[Q] Help with ROM flashing (bootloop problem)

Hello there,
I was tired of my phone (Samsung Galaxy 3 GT-I5800) and wanted to do something with it. I found out its possible to install different systems on it, so i did. I tested CM10 with succes, but i wanted something different, i downloaded AOKP (in the meantime i flashed I5800XWJPD and I5801DXJPC ## from samfirmware, which were ****). So now i have couple bugs i can't solve:
When i boot my phone it says "GT - I5801" not "GT - I5800" as it should, i have no idea why.
AOKP bootloops (intro animation starts - ding white screen for 5 seconds or so, and loop), but eventually boots
Home button doesnt works in AOKP
AOKP doesnt reads SIM card (probably because of bootloop)
I used Odin Multi Downloader v4.252, apollo_0531.ops file, and said ROMs. Oh and i rooted it, or at least i think i did
Just flash another ROM. Your phone should work as usual.
Sent from my GT-I5800
try froyo roms m12., kisad's, purumod., or stock roms.. everything works in good shape
fraunos said:
Hello there,
I was tired of my phone (Samsung Galaxy 3 GT-I5800) and wanted to do something with it. I found out its possible to install different systems on it, so i did. I tested CM10 with succes, but i wanted something different, i downloaded AOKP (in the meantime i flashed I5800XWJPD and I5801DXJPC ## from samfirmware, which were ****). So now i have couple bugs i can't solve:
When i boot my phone it says "GT - I5801" not "GT - I5800" as it should, i have no idea why.
AOKP bootloops (intro animation starts - ding white screen for 5 seconds or so, and loop), but eventually boots
Home button doesnt works in AOKP
AOKP doesnt reads SIM card (probably because of bootloop)
I used Odin Multi Downloader v4.252, apollo_0531.ops file, and said ROMs. Oh and i rooted it, or at least i think i did
Click to expand...
Click to collapse
^
You are getting GT - i5801 instead of GT- i5800 because you flashed a .TAR file that had a bootloader. Never ever flash a rom that contains bootloader in it! Most of the stock rom's in samfirmware contains bootloader in them, so I highly recommend you not to flash such roms!
What you're getting is not a bootloop, but just a minor bug. You can fix that by simply downloading any custom bootanimation and then pushing it to /system/media. You can find tons of them in the "Themes and Apps" sub-forum.
No clue, maybe reflashing should solve the problem.
You probably have Pin Lock in place. Simply disable it and your SIM should be working fine after that.
I'll try different ROMs, cause i tried reflashing AOKP and it always has that white screen bug. Thanks for answers, i'll try different things, hope it'll work.
Edit: Ok i disabled boot animation in options and it works now, but still home button doesnt work and i found out that usb connection doesnt work too, i searched the forums for the solution, but i cant find that MTF option or how it was called..
EDIT2: Okay, everything's fine by now what i've done is i downloaded rom from samfirmware, double checking it has bootloader for 5800, installed it, and then did the same with M12. Thanks for help!

[POLL + INFO REQUEST] Black screen CM10.1

So after all these black screen issues, I want to try and find a connection for those getting it. So, please answer the poll and if you got the black screen post the following info (example shown)
Phone model and version: MB865 ATT
ROM before attempted install: Stock ICS
Ever used a previous version of CM10: No
things tried to fix: back to stock, old version fisrt, etc.
any thing else you think might be helpful
Phone model: MB865 international (Claro, Argentina)
Rom: Stock ICS HongKong/Taiwan
CM10 before: Yes
Tried to fix: No, it worked the first time
I can't read all the answers in the rom thread, but, if i flash the rom and the gapps at the same times, i'll get the black screen. And, if you flash the rom, start your phone, use it and then flash gapps from cm recovery, then it have to work. Maybe it was coincidence, but in several phones it worked.
Phone model - MB865 Asia retail
ROM before installation - Stock ICS
Used previous version of cm10 ( you mean cm10.1?) - Used cm10 before , and now 3 different versions of cm10.1. ( the one before kexec and 2 kexec versions)
Black screen issue - No issue at boot. Boots properly everytime. Gives me black screen at random times like after a call, or while charging. I got it around 2-3 times, pulled the battery and rebooted.
After using the ROM for some days ( it's been a week now), no black screen issue.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
I haven't experienced the black screen problem but any how
Phone model and version: MB865 ATT
ROM before attempted install: CM10
Ever used a previous version of CM10: Yes,CM10
things tried to fix: Didn't have to try.Have rebooted atleast 10 times since and still haven't got the black screen.
brianmoyano said:
but, if i flash the rom and the gapps at the same times, i'll get the black screen. And, if you flash the rom, start your phone, use it and then flash gapps from cm recovery, then it have to work. Maybe it was coincidence, but in several phones it worked.
Click to expand...
Click to collapse
I flashed the ROM and the gapps together without rebooting and haven't experienced the black screen problem.
Sent from my MB865 using xda premium
deveshmanish said:
I flashed the ROM and the gapps together without rebooting and haven't experienced the black screen problem.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yea, me too. But, the guys who has the black screen problem, they solved it with that.
---------- Post added at 04:07 AM ---------- Previous post was at 04:06 AM ----------
PS: Did someone tried with another gapps?
Model : AT&T mb865
Rom before install : SCV7 leak#1 based
Previous CM :yes
Things i have tried to solve ; none
It black screened me right after coming out of deepsleep , like other posts before mine, i rebooted my phone several times without having to battery pull , this is my booting secuense : first is moto logo, then white screen (2 seconds) then black screen (2 seconds) then cm bootanimation idk if it might help at all
Sent from the gray stuff inside my skull
Phone model and version: MB865 ATT
ROM before attempted install: CM10 (original not CM10.1)
Ever used a previous version of CM10: Yes
things tried to fix: Tried flashing with last version (3/28 build) of kexec and the latest version (4/3 build). With Gapps and without Gapps. Tried installing the CM10 Rom, booting into this rom, and then flashing the Kexec. Tried different slots System 3 and System 6. Before you ask I have modified the Rom according to instructions provided for BMM. Nothing works. The only thing unusual maybe that this phone was a replacement for my original Atrix2 after the original phone was hard bricked. This version also is factory clocked at 1.0Ghz and 4 clock stages vs. the original 5. I am not sure if this is an indication of different hardware. I think it's definitely a hardware difference causing the black screen as some of the other posts indicate plenty of people having success booting Kexec version with ATT Atrix2/MB865.
Model: ATT MB865
Cm b4 : yes
Stock rom : ics
Flash process: I flash the rom and gappps together in bmm recovery.
I use the converted kexec thru bmm. I get 1st boot success and the subsequent boots as black screen, or at least that is what I thought. I have went and let it simmer and found out that it my take a minute but... Looky there it booted. I went and used the converted 4/2 version ti upgrade and hadto reboot 2 times to get it to fly. Gotta love the silky smooth feeling. I have a radio problem that acts up so that throws another kink in it.
Atrix 2/ ATT /Bmm
1. Stock 4.0.4
2. Miui
3. PA 3.1.5 4.2.2
4. CMPA 4.1.2
5. Kexec 4.2.2
My stock ICS clock speed is 1.2 gigahertz. I also require through the performance mod down to 1.0 gigahertz and it is booted every time that I have power down first. I have it installed in slot 6
Phone model and version: MB865 Retail
ROM before attempted install: Stock ICS, PA3+, cm10.1, miui (tried with all).
Ever used a previous version of CM10: Yes.
things tried to fix: back to stock, different devtrees (other devices', different region, the ones of ME versions, flashing different devtrees to device using fast boot and combinations, my own as well), different display drivers, and quite a lot more. None have helped (so far).
You may also want to include the stock ICS max clock speed, if it ever booted up (even once) if it did boot up, was it with bmm or stock CyanogenDefy.
Stock ICS max clock speed :1.2 GHz
Ever booted up: Yes about 6 times. Completely random. Booted up with both bmm and CyanogenDefy recovery.
UPDATE: AAAND out of nowhere it boots up again. No idea how or why this time. BTW, its a fresh install in bmm slot 3. Took logs of last_kmsg, kmsg and dmseg. Any one wants anything else before the phone reboots and this rom may or may not come up?
Sent from my MB865 using Tapatalk 2
Phone model: ME865 (HKTWN)
Rom: 4.0.4. ME HKTWN ICS (translated to Hungarian language + implement some battery saving scripts)
CM10 before: No
Tried to fix: No, it worked the first time
Everything works fine, but the HDMI not working . I flash backmy own rom which is based on the JB Leak 2 (transleted it too).
Phone model - MB865 Asia retail
ROM before installation - Stock ICS searet
Used previous version of cm10: No.
Black screen issue - No issue at boot. Boots properly everytime. Noticed black screen only one time when one of application I worked (do not remember exacrly what app it was) with became frozen and I received a call at the same moment. I am not sure about call, i haven't heard ringing and haven't seen any caller id, only icon of conversation in notification bar. I turned off screen and tried to turn it on but without success. It was only possible to light buttons. Hardware reboot solved the problem.
Hey guys just wanted to make one thing clear, the black screen issue being discussed here is something that occurs even before the boot animation. Just after the M logo. Whatever happens after the cyanogenmod boot animation is ROM related. You get a black screen implies you can't even get to the boot animation.
Sent from my MB865 using Tapatalk 2
Phone: MB865 ATT
ROM before: stock ICS
When I first installed the first kevec update I got the black screen couple of time then I read about undoing the default 1.2ghz oc so I went ahead and did that, set it to 1.0 GHz set it on boot and it fixed my problem. I updated my A2 to the last update doing a clean installation and I have not experience any black screen so far.
Sent from my MB865 using Tapatalk 2
Phone model and version: MB865 ATT
ROM before attempted install: PA 2.57.3
Ever used a previous version of CM10: Yes
Things tried to fix: None
Installed CM 10.1 like the instructions. Kept getting black screens, and pressed power+vol up+vol down to reboot, but continued to get the black screen. Got super annoyed so I restored the backup I made before installing CM 10.1.
Ravi did u try to reduce clock speed as well.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
amynjimmy said:
Ravi did u try to reduce clock speed as well.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
Click to expand...
Click to collapse
If you are talking about the contents 2 posts above, that dosent even make a difference. I mean, when you are on one rom, change max clock speed and set it on boot, its only for that rom. And the max clock speed changes after the phone boots up and the app like setcpu changes it. But all that happens after the phone boots up. If it is even related to max clock speed, the only way to do that is to make changes in kernel.
Sent from my MB865 using Tapatalk 2
If I mess up and reboot u will always get a black screen. If I battery pull after that, it will boot after an undermanned amount of time. I even got some weird blue screen at some point thus morning and my phone started heating up. Finally battery pulled and got back into kexec again. Any method I have tried to get past black screen without battery pull yields more black screen. Power off will boot every time. What changes are made when booting between the 2. It is weird that we all get different results. I cannot even reproduce the same 2 times in the row unless I power down first.
Atrix 2/ATT/BMM
1. STOCK 4.0.4
2. MIUI
3. PA 315 4.2.2
4. CMPA 4.1.2
6. KEXEC 4.2.2
Phone model and version: MB865 ATT
ROM before attempted install: MIUI for ATT
Ever used a previous version of CM10: Yes before MIUI
things tried to fix: Reflash and multiple battery pulls.
I've actually gotten pretty good at pulling and booting since I've done it so many times. On average it take me between 20-30min to get the phone back up after a black screen. I've had several random reboots at the worst times and without skipping a beat a get to pulling and booting (can't be good for the battery).
Phone model: MB865 Indian Atrix2
ROM: Was initially in JB leak. FXZ to ICS Asia Retail version 4.0.4 to flash CM10.1
Previously had CM 10 before moving to PA.
Tried a couple of battery pulls but it did not boot. I flashed back the ICS 4.0.4 Asia Retail version to restore to a working phone.
~
Sayantan
Well the black screen seeks to be only because of the display driver.. Nothing to do with kexec. I changed some drivers and some of the previous errors were no more..
Sent from my MB865 using Tapatalk 2

[Q] lost network and need help

ok lets start from the beginning,
flashed beanstalk, decided i liked vanilla rootbox better, i kept getting a error when trying to flash vanilla, used odin to unroot and flash back to stock (cell was functional at that time)
SOC failed (kept saying not responding) so i figured i had to flash a pre-rooted stock version had red CWM, then i flashed latest build of vanilla, when it booted, i noticed i had no connectivity, decided to try and flash avatarROM 6.5 that failed, so i restored from a backup i had of it, once it booted still no connectivity, decided to try and flash a modem to see if that was the issue, booted, and still nothing, my final hope was to go all the way back to the beginning to step 3 and flash a pre-rooted stock, guess what......now i have network......wtf! it looks like im stuck on 2.2.1 until i can get some help, anything at all is helpful yesterday my phone was perfectly fine now im stuck in this hell called froyo lol
Sounds like you lost your IMEI while working your way back up to Rootbox. In case you didn't know about it, check out andros11's guide to flashing JB. Follow it closely and you'll be up and running in no time.
--------- More info ----------
Beanstalk uses a new partition scheme. So you can't flash from Beanstalk to Avatar (or Rootbox) without going back to stock first and then working your way back up. At least until those ROMs are updated to the new partitions.
Thank you. I talked to andros And he said the same thing looks like i jumped the gun on things lol
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Fixed and solution
for anyone that finds heimdall confusing or wont work and can only use odin all you gotta do is....(this is what i used to get from froyo to JB)
follow these in the order that the links are shown
STEP 1: i lost the link to the rooted stock for froyo but you should be able to find one easily
heres the link for GB rooted stock http://forum.xda-developers.com/show....php?t=1613523
install the rooted stock via odin method and follow ALL instructions (READ THE WHOLE PAGE!)
ONCE YOU GET TO THIS POINT DEPENDING ON THE STOCK ROM YOU HAVE EITHER FROYO OR GB
IF YOU HAVE FROYO COMPLETE STEP TWO IF YOU HAVE GB AND A RED CWM SKIP TO STEP 4
STEP 2: http://www.youtube.com/watch?v=ozNVeGPUlU8 -custom recovery to get green 2.x CWM
STEP 3: http://forum.xda-developers.com/show...6&highlight=gb this is the gingerbread rom i used in my process to get to JB (DO NOT JUMP THE GUN READ THIS.......OPEN UP THE NEXT LINK AS WELL AND READ THE INSTRUCTIONS THEY APPLY FOR THIS AS WELL IT IS A MUST IF YOU WANT THIS TO WORK) supplemental video to help with instructions http://www.youtube.com/watch?v=ndC39t1AE-k
STEP 4: http://forum.xda-developers.com/show...&highlight=ics follow instructions again same as step 4
STEP 5: provided is the rom for ics i used (beware has new partion and cannot flash other roms such as avatarROM afterwards refer to location at bottom marked **1**) you can use any JB rom that you would like this just happens to be the one i used http://forum.xda-developers.com/show....php?t=2059535 once you get to ics you should have gotten the blue CWM and then just follow the instructions here http://forum.xda-developers.com/show....php?t=1878458
you should now be JB while retaining your IMEI
**1** please refer to this as there are new partions and not all roms use the different ones refer to this before you flash ANY new JB roms
http://forum.xda-developers.com/show....php?t=1387334
if you have any questions or see that i possibly missed a step feel free to pm
there are alot of similar posts, but i decided to add one with all steps that a normal non experienced user could use and get to where they need to go

Categories

Resources