so i followed the ICS - catchall thread and flashed it to the blade.
normalt precautions taken.
And yet, after flashing it, it says "Baseband: unknown" under settings -> about
Also, the imei does not display.
This leads me to believe that the lir is shot, or is there something more at work?
and while im at it, i'm unable to flash a new baseband to it via the stock method of holding down vol- and MENU.
for posterity:
I solved it by installing the stock rom and then installing the same rom as before.
This has had to be the weirdest error i've ever come across.
So for others with the same issue:
reinstall stock rom (not restore from nandroid) and reflash the custom rom afterwards.
Does it work when you first flash froyo/gingerbread stock and then cm9 after that?
Sent from my ZTE Blade using Tapatalk 2
How do one get the correct baseband for India using cm9 kang. Thank you
Sent from my ZTE Blade using Tapatalk 2
U don't need to correct ur baseband everytime. Its just an odd issue sometimes.
I have tried Burstlam and ColdFusion and both don't have baseband issues in India
Related
Hi all,
I've posted here before but I'm after a definitive answer as to whether I will hit issues as far as CWM recovery is concerned.
I currently on stock 2.3.3 rom + kernel with JV7 modem (that means I'm from UK on the Orange network).
My phone has been unlocked from its carrier and rooted using super one click.
I'm going to flash CR-Root, which will give me CF-Root kernel running on my stock 2.3.3 rom.
*Wipe/factory reset phone*
Then after I've flashed CF-Root, I’m going to flash CM7.
After I've flashed CM7, I’m going to flash Glitch kernel.
HOWEVER, if I flash Glitch kernel (according to Chainfire’s CF-Root thread) I'm going to lose the CWM recovery that is provided with CF-Root...
1. Will this cause me any issues?
2. Will CMW actually be lost or have I got that wrong?
3. How can I keep CMW and switch to Glitch from CF-Root?
God bless XDA.
Almost every kernel has cmw by default on it (including glitch). I dont think yu wud face any issues.
ps. Wait for more pro replies.
Sent from my GT-I9000 using XDA
1. Will this cause me any issues?
★ NO
2. Will CMW actually be lost or have I got that wrong?
★ No. It will be replaced my a newer version of cwm probably cwm4 or cwm5. So you don't have to worry about anything.
3. How can I keep CMW and switch to Glitch from CF-Root?
★ cwm won't be gone. So this question isn't valid
Sent from my GT-I9000 using Tapatalk
hi to all. is anyone having issus with latest DLL7?
what i mean is that i made a clean install of LL7. after rooting with autoroot i installed TWRP 2.3.2.3 cause latest gave me only black screen.
but if i want to update from 2.3.2.3 to 2.3.3.1 it does never boot to recovery bur instead it gives broken Samsung n7100 screen.
it is the same if installing any CWM recovery. so Sammy has made some really weird changes with this update.
any other info. maybe bootloader downgrade just as in S3 thread. Advices
This is a little bit like my problems but I have random reboots instead. They occur almost immediately on a clean XLL7 install flashed from Odin without any root or apps installed.
Everything works perfectly in 4.1.1.
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
mariosraptor said:
sorry to hear that. but this is nothing like that. to me this looks pretty serious. it seems like plus in security from Sammy.
as for you you can try re-install the stock rom for your phone using Kies.
all you have to do is open kies go to tools- and sellect the 2 or 3 option with your phone not connected.
write GT-N7100 and right after the serial number from your phone, follow instructins on screen.
bear in mind. this will wipe your phone.
Click to expand...
Click to collapse
I will try that and see what will happen.
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Do not flash any recovery !!!!!!!!
They updated the bootloader so it is very dangers to flash untested mods and stuff.
Click to expand...
Click to collapse
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
JCVD_ said:
I've flash the last ARHD rom 8.o which have last dll7 firmware and after note2core kernel 2.21 and all works fine. Now I won't install anything else until it's proved working on dll7.
Click to expand...
Click to collapse
do not worry. he means with stock rom.
in ARHD and other custom roms bootloader is left ou of flash.
anyway. i think that sammy has changed the some partitions. twrp works but only 2.3.2.3
No the roms who are based on dll7 are safe.
The recovery imao needs to be updated.
Sent from my GT-N7100 using xda app-developers app
Do you mean that it is dangerous to flash the CWM recovery to the device when it runs XXDLL7?
I flashed the root and CWM package after flashing XXDLL7 and it seems to work (my random reboot problem is unrelated I guess since it happened even with just stock recovery in place).
Now, I have the new bootloader and radio and flashed BatteryPlus 0.2 from CWM without any problems. I flashed the CWM-root-package through Odin after flashing XXDLL7, also from Odin.
So the question is: is there a problem with CWM and other custom recoveries and the XXDLL7?
Or are we talking about flashing mods?
No it can be an issue. It's not recommended at this stage.
Sent from my GT-N7100 using xda app-developers app
If there is a problem with CWM and XXDLL7, that could perhaps explain my reboot problem in that case.
If so, I will hold off for a while and stay on my current configuration.
I have the new bootloader and radio already.
i have noticed that 4.1.2 isnt so friendly with custom recovery. I had cwm recovery and going into it, took a lot of time with 4.1.2 firmware. Maybe samsung is trying to make some higher security in 4.1.2 against custom recoveries and etc.
If they wanted they could have made it absolutely protected. No I don't think they actually wanted to increase security.
I just think the new bootloader isn't friendly with the old recovery.
Sent from my GT-N7100 using xda app-developers app
Ok, so previously with my S4, if we flashed a I9505 ROM onto a I337or I337M S4, all we had to do was flash our device models custom or stock kernel and the wifi and everything that was borked was then fixed. This doesn't seem to be the case here.
And now I can't figure out for the life of me how to get back wifi after flashing a 9005 ROM on my N900!
I'm sure it's something super simple, and I;ve searched for the solution, but clearly I'm looking in the wrong place.
Any assistance would be met with a "Thanks" and some karma points
Did you flash a custom firmware or a stock one?
Sent from my SM-N9005 using Tapatalk
RavenY2K3 said:
Did you flash a custom firmware or a stock one?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Custom. More specifically Fox Hound
TheSmokingAndroid said:
Custom. More specifically Fox Hound
Click to expand...
Click to collapse
Ok well that blows out what I thought you'd done it.
Have you tried wiping after flashing the correct ROM? The "incorrect ROM" didn't include any modern files didn't (not that I'm sure CWM will flash them on this phone however)
Strange question, but is your camera still working? Recording etc... also, in device settings, does it list the correct IMEI number?
Sent from my SM-N9005 using Tapatalk
Yup, camera works with stock kernel that the rom came with, imei is fine.
Just can't figure out which files to flash to get wifi and other radios working
Yup, camera works with stock kernel that the rom came with, imei is fine.
Just can't figure out which files to flash to get wifi and other radios working
Did you try a factory reset? After backing up of course...
Might work....
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
vish9 said:
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
Click to expand...
Click to collapse
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
joebob296 said:
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
Click to expand...
Click to collapse
Exactly, AOSP ROMs are booting up fine but not the Stock based ones.. I am not flashing any kernels, just the ROM, so I'm assuming it will run on either the stock kernel or the kernel included in the ROM zip?
Have you been successful in installing such ROMs? Am I missing something in the wiping part? Only been doing the factory reset in TWRP before installing any ROM.
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Oh, I hadn't thought about anything being wrong with the recovery.. Always assumed it gets the work done
How do I find previous versions of TWRP compatible with D800?
joebob296 said:
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yes I am on 10o.. Does it have issues with installing other Stock ROMs? If yes, I'll try to follow the thread on using LGFlash tools, I've never done that before. Hopefully its not much difficult to follow the instructions.
That is one of the easiest guides to follow. Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
joebob296 said:
That is one of the easiest guides to follow. Me sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Thanks.. I'll try to do it tonight and post my results here.
joebob296 said:
Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I'm stuck in the process! Can't change the com port number to 41. The guide is pretty easy to understand. But when I put my phone is download mode and try to change the com port number, it says I don't have the write privileges for this device's setting. I've tried it on both Win 7 and Win 8 laptops, with LG mobility drivers installed.
Is there something in the phone settings I need to enable so that I get the write privileges to change com port number?
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
SOLVED!
joebob296 said:
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yay!!! Finally did it!
Issue 1: If faced with write privileges for com port (tried successfully in Win 8)
Solution: After going in to com port properties, click "change settings" and there is the option to change com port number.
Issue 2: Once the port number was changed to 41, rest of the instructions are easy to follow on this thread http://forum.xda-developers.com/showthread.php?t=2633150
Once on D80010d, I rooted with ioroot22, and installed recovery using FreeGee. Just installed Rayglobe 3.2 minutes ago, and it finally booted up!!!
So, the bottomline is that go back to D80010d if you wanna play with Stock based ROMs! I flashed with TWRP 2.6.3.3, so the fault is not with the recovery. That much I can confirm
Thanks for the suggestions guys. Thread solved I guess.
Great. Glad to hear it.
Sent from my LG-D801 using Tapatalk
rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Thanks for the input. Before I flashed back to D80010d today, I installed older versions of Philz and TWRP but neither helped. So downgrading was sort of a compulsion, in my case at least.
and the moral of the story is, unless you are getting an android version upgrade in the update, do not take the update.
Hello, I have a new note 3 n900tmobile. I love it but, i cant live with touchwiz, i am rooted with twrp... i tried to flash cwm.tar through the lovely odin. But with the 4.4 bootloader i have learned that changes are permanent and cwm just throws me through a bootloop. I also get a bootloop through twrp flashing cm11 plz help! I also cant flash to 4.3 due to the bootloader? i think thats why.
I also flashed phillz cwm and tried flashing same issue I thought it might change due to not flashing on twrp with some devices namely the optimus , I'm gonna see if the latest nightly will flash correctly. If not the release candidate.
Sent from my SM-N900T using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2614461
This is what you need to know. For now wait and flash the latest nightlies and it will be fixed I have faith in cyanogenmod.
PS. I should have looked done some more research before starting a new thread thanks.
Sent from my SM-N900T using Tapatalk