[Q] Major help - G1 Q&A, Help & Troubleshooting

I was running cos-ds latest rom and accidently in rom manager hit install green rom now under about phone I dont have a firmware version or baseband. how do i restore these. the phone boots but always gives the error com.android.phone has stopped working and force close. i use this phone for work and it wont pick up a cell signal or let me into the network tab
Model: COS-DS
Android Version: 2.3.4
Baseband Version: unknown
Kernel Version: 2.6.36.4-s3-cos
Mod version COS-DS-07182011
Build #: GRJ22
where is the firmware version? the whole thing is missing?

Did you do nanodriod backup before you done that? If yes, just restore it back to the previous last backup.

or just wipe device and re-flash rom of choice
the firmware version would be 2.3.4... not sure why its called android version... but i don't think i flashed that rom so it may be different

Related

[Q] what happens if you flash a rom which incompatible?

Just wondering what will happen if a rom is flashed into a phone which has an incompatible baseband, kernel and/or OS version?
For example, my phone currently is using a kj4 baseband, and kj6 kernel and running android 2.3.5.
If I flashed a rom which is based on a kka baseband and kernel and android 2.3.6, what will happen?
Will the phone be bricked? Or will it still function but with weird results?
And is it advisable to upgrade my OS to 2.3.6 if I'm flashing to a rom based on that version, or can I just stay at 2.3.5?
Thanks.
galaa said:
Just wondering what will happen if a rom is flashed into a phone which has an incompatible baseband, kernel and/or OS version?
For example, my phone currently is using a kj4 baseband, and kj6 kernel and running android 2.3.5.
If I flashed a rom which is based on a kka baseband and kernel and android 2.3.6, what will happen?
Will the phone be bricked? Or will it still function but with weird results?
And is it advisable to upgrade my OS to 2.3.6 if I'm flashing to a rom based on that version, or can I just stay at 2.3.5?
Thanks.
Click to expand...
Click to collapse
It is advisable to upgrade with Kies, do not use odin.
If you have confidence then only use odin, safe is Kies.
galaa said:
Just wondering what will happen if a rom is flashed into a phone which has an incompatible baseband, kernel and/or OS version?
For example, my phone currently is using a kj4 baseband, and kj6 kernel and running android 2.3.5.
If I flashed a rom which is based on a kka baseband and kernel and android 2.3.6, what will happen?
Will the phone be bricked? Or will it still function but with weird results?
And is it advisable to upgrade my OS to 2.3.6 if I'm flashing to a rom based on that version, or can I just stay at 2.3.5?
Thanks.
Click to expand...
Click to collapse
you can flash the 2.3.6 ROM. Backup your data, clear your dalvik cache and factory reset, then flash the ROM in CWM recovery... restore your data.... and voilà!
Do you have CWM recovery? if no, then install a kernel from a thread in the 'android development forum', you'll find instructions in the thread.
Happy Flashing!
edit: If you have no idea what I'm talking about, say so, I'll explain the details.

SGS I9000 - Help for flashing

Hi everyone!
I have a SGS (GT-I9000) that I would like to flash with cyanogenmod7. But despite having read quite a lot of stuff about flashing and so on the internet, I have to admit I am a noob, this is why I would need some advice
I had the phone with 2.2.1. I rooted it with the one click utility and unlocked it with the market app few months ago.
Then I flashed it with Darky's 9.5. After a while, I decided to upgrade it with darky's 10 rc6 but something went wrong (and I have no idea what it could be). Honestly, it has been a while now and I could not say what exactly happened, I can just tell you what I can read on my phone:
Firmware version:
2.3.3
Baseband:
I9000XXJVK
Kernel Version:
2.6.35.7-I9000XWJVB-CL118186
[email protected] #Dark_Core_2.0
Build number:
FICETO.GINGERBREAD.XWJVB
I noticed something which I think is curious. I just intalled Kies in order to get the drivers for the phone, and I received a message:
A new firmware version is available...
current version: PDA:JVB / PHONE:JVK / CSC:JV3
(NEE)
latest firmware version: PDA:JVH / PHONE:JVO / CSC:JV3
(NEE)
But I always thought that when you flashed a custom rom, Kies could not update your phone anymore ?
So do you think that I can just flash the rom in recovery following the guide on cyanogenmod's wiki or should I revert back to stock ?
Thank you for your attention.
Just flash cm. Backup your application with TB, factory reset and follow flashing guide.
If you encounter any problems, you can always flash to stock then.
Kallilol said:
Hi everyone!
I have a SGS (GT-I9000) that I would like to flash with cyanogenmod7. But despite having read quite a lot of stuff about flashing and so on the internet, I have to admit I am a noob, this is why I would need some advice
I had the phone with 2.2.1. I rooted it with the one click utility and unlocked it with the market app few months ago.
Then I flashed it with Darky's 9.5. After a while, I decided to upgrade it with darky's 10 rc6 but something went wrong (and I have no idea what it could be). Honestly, it has been a while now and I could not say what exactly happened, I can just tell you what I can read on my phone:
Firmware version:
2.3.3
Baseband:
I9000XXJVK
Kernel Version:
2.6.35.7-I9000XWJVB-CL118186
[email protected] #Dark_Core_2.0
Build number:
FICETO.GINGERBREAD.XWJVB
I noticed something which I think is curious. I just intalled Kies in order to get the drivers for the phone, and I received a message:
A new firmware version is available...
current version: PDA:JVB / PHONE:JVK / CSC:JV3
(NEE)
latest firmware version: PDA:JVH / PHONE:JVO / CSC:JV3
(NEE)
But I always thought that when you flashed a custom rom, Kies could not update your phone anymore ?
So do you think that I can just flash the rom in recovery following the guide on cyanogenmod's wiki or should I revert back to stock ?
Thank you for your attention.
Click to expand...
Click to collapse
Download the latest CM7 + Google App
Copy into your internal SDCARD
Boot into recovery
Do a full wipe Including (dalvik)
Install CM7
You may face boot loop then remove battery put it back and boot into recovery
Install the same zip file one more time
Optionally flash GoogleApp
Enjoy flashing
For flashing Video Guide

Cant update my note OTA

So the thing is i had this baseband N7000XXKK5 i rooted my note then tried first custom ics rom didnt like it restored too default GB which i backed up before flashin a custom rom then again tried another rom this time paranoid android it changed my baseband to LQ3 didnt like it revert back to again my GB backup then tried the midteam which changed my baseband to N7000XXLPT but when this time i tried to revert back to my backup it didnt change the baseband back to N7000XXKK5 n now i cant flash any custom roms as well as the OTA update
Current Details
Android version
2.3.6
Baseband
N7000XXLPT
Kernel version
[email protected] #2
Build number
GINGERBREAD.XXKKA
Help as i just wanna have the OTA update of ics n root access nothing else
Bump
You need full stock to do that, and all matching parts of a stock version. And the same csc, in plain words the same setup your phone came with.
Anything else and no ota lol
Sent from my GT-N7000 using Tapatalk 2
So just a stock gb flashed through odin would do the trick? :victory:
Yes, as long as its same csc, efs is not corrupted.
Sometimes its needed to try different roms. Had it once one version didnt ota, and earlier did.
Sent from my GT-N7000 using Tapatalk 2

Lg Revolution recovery

I recently rooted my lg revolution that was running android version 2.3.6. I installed clockwork mod which later caused my phone not to boot past the verizon logo. I installed LGNPST and firmware to solve my issue. I later was stuck in test mode. After I found a piece of software that fixed that issue, I am now stuck on android version 2.3.4. Everything works fine, but my phone is not recognized by Verizon Wireless (for OTA updates). I assume this is because something is wrong with the phone's info. Can anybody help me with fixing my phone so that it is out-of-the-box like new? I need to be able to take the OTA update.
Phone info:
Model: VS910 4G
Android Version: 2.3.4
Baseband version: VS910ZV7-M7X30-AABBQMLYM
Kernal version: 2.6.35.7-perf [email protected] #1
Build number: GRJ22
SW Version: VS910ZV7
ExtraEme said:
I recently rooted my lg revolution that was running android version 2.3.6. I installed clockwork mod which later caused my phone not to boot past the verizon logo. I installed LGNPST and firmware to solve my issue. I later was stuck in test mode. After I found a piece of software that fixed that issue, I am now stuck on android version 2.3.4. Everything works fine, but my phone is not recognized by Verizon Wireless (for OTA updates). I assume this is because something is wrong with the phone's info. Can anybody help me with fixing my phone so that it is out-of-the-box like new? I need to be able to take the OTA update.
Phone info:
Model: VS910 4G
Android Version: 2.3.4
Baseband version: VS910ZV7-M7X30-AABBQMLYM
Kernal version: 2.6.35.7-perf [email protected] #1
Build number: GRJ22
SW Version: VS910ZV7
Click to expand...
Click to collapse
Try using lgnpst and flash zv8 then try to update to zv9. If that doesnt work then try using mts method and put stock recovery back on the phone then lgnpst to zv8 and update to zv9. Mts method is found in development i believe. If that doesnt work then i have no more advice cuz i dont have this pos phone anymore. Thats just what i did before sending in my revo
Sent from my DROID4 using xda premium

Reboot loop no matter which ROM I try

I have a Droid 3 unlocked for use on GSM networks (T-Mobile). It had an old version of CM on it along with Safestrap 1.08d. I recently deleted that ROM and upgraded to Safestrap 3.05. I've been trying to install CM 10.1 or 10.2 with no luck. It just goes into a reboot loop every time. The stock ROM is still working just fine (using modified build.prop for GSM support). I've tried using different build.props with CM but it doesn't help.
At one point I got CM 10.1 to boot, but then I installed gapps and it stopped working. I have not been able to repeat this since.
Any ideas?
Stock ROM Information
System Version: 57.1.60.XT883.ChinaTelecom.en.CN
Android Version: 2.3.4
Baseband Version: n_34.18.16s
Kernel Version: [email protected] #1
Build Number: SLNCT-57.1.60
Looks like this is only an issue with Jelly Bean ROMs. I got Minimoto 1.7 working without any issues.
unlimitedbacon said:
I have a Droid 3 unlocked for use on GSM networks (T-Mobile). It had an old version of CM on it along with Safestrap 1.08d. I recently deleted that ROM and upgraded to Safestrap 3.05. I've been trying to install CM 10.1 or 10.2 with no luck. It just goes into a reboot loop every time. The stock ROM is still working just fine (using modified build.prop for GSM support). I've tried using different build.props with CM but it doesn't help.
At one point I got CM 10.1 to boot, but then I installed gapps and it stopped working. I have not been able to repeat this since.
Any ideas?
Stock ROM Information
System Version: 57.1.60.XT883.ChinaTelecom.en.CN
Android Version: 2.3.4
Baseband Version: n_34.18.16s
Kernel Version: [email protected] #1
Build Number: SLNCT-57.1.60
Click to expand...
Click to collapse
. You should just sbf back to stock then root & install safestrap 3.05 and start again fresh.

Categories

Resources