Related
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Let's try this in order: if you are with Virgin Mobile, it is a CDMA. GSM phones take a sim card, both versions accept an sd card for storage.
Everything looks good until:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Good luck. If you have any more questions, feel free to ask.
pedantfool said:
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Click to expand...
Click to collapse
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
followup
FIRST: Just thought of something that might be very important, I only had a version of android 4.0 installed on my phone. Will that make a difference when installing roms intended for later versions of android? If so, I feel like a huge knuckle-dragging fool.
Update: Was able to install and boot using PACman, but ran into a boot-loop.
But to follow up to your questions:
MameTozhio said:
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
Click to expand...
Click to collapse
I'll admit I've had a hard time find a definitive version of PA or really any other Rom. I've tried going through their thread here and downloading one of the "stables" (http://goo.im/devs/gannon5197/paranoid/primoc/stables/). I've also used other unofficial versions of PA (http://forum.xda-developers.com/showthread.php?t=1799372). I'm currently downloading PACman to see if that will make any difference.
[email protected]@ said:
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
Click to expand...
Click to collapse
I did flash my boot.img using the method explained here:
Copy the kernel image (boot.img file you have extracted from zip file of ROM) to folder in which you have kept your fastboot files.
In the same folder, right click while holding shift button and select ‘Open command window here’.
A command window will appear on your screen. In command window type ‘fastboot flash boot boot.img’ and press enter.
On your screen you will get message ’OKAY/Finished’. You have successfully flashed kernel. Now you can disconnect your phone from computer.
http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
riggerman0421 said:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
Click to expand...
Click to collapse
I'd like to think I'd partitioned it properly, but I keep getting a "unable to mount sd-ext" or "unable to wipe sd-ext" message when I attempt a factory reset. I've tried formatting the the mini sd and set the file type to FAT32, but to no avail as the errors persist. I know you said not to be too concerned, but I keep failing the system wipe from your next suggestion because of that error.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Click to expand...
Click to collapse
Now how important is it that I flash the boot.img after I have flashed the rom? I've been doing it beforehand, but does doing it afterward make a difference?
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Click to expand...
Click to collapse
Those both match my radio and bootloader, what does that imply? I'm planning on flashing this rom: http://forum.xda-developers.com/showthread.php?t=1948034
Will that work?
No, it won't. You have the newer updated hboot and radio. That is the source of your boot loops. The only compatible roms at this time are MyOneV, ExtremeSemse, and RhythmicRom. You can also use Cyanprimo, but you'll have flash the boot.img from RhythmicRom.
Now I've downloaded RythmicRom and I'm still stuck in a boot loop. I'm sorry for being a bit thick, but could you link some roms that would be compatible or explain what I need to be looking for?
Version I downloaded: http://forum.xda-developers.com/showthread.php?t=2147407
You'll need to download the 1.2 update, then extract the boot.img from that. The boot.img in the Rom doesn't work with the new update.
So I've been reading up on the issue over here: http://forum.xda-developers.com/showthread.php?t=2018518&page=14
and while I don't claim to understand it all, I believe I get the gist of it.
I also've managed to get RythmicRom working thanks to riggerman. I guess I'll just play the waiting game until someone rolls out a fix or just replace my phone (though that's very much in the long-run).
Once again, thanks to everyone and hopefully this will be the last we see of this mess.
Glad you got it running, and glad I could help.
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.
Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.
svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.
Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.
I want to secure my phone from the recently discovered StageFright Android hack.
I want to remove the component/package that this bug is linked to.
I am running AT&T Rooted Stock (minus bloatware) 4.4.2 Baseband: I747UCUFNE4.
I want to remove the offending package with titanium backup until an Update can be issued.
Can someone let me know what package I need to remove?
You will be better off waiting for a xposed patch, stagefright (if you have been paying attention) is the media processor in android so if you take it out you loose most media playback
Sent from my Nexus 7 2013 using Tapatalk
crazymonkey05 said:
You will be better off waiting for a xposed patch, stagefright (if you have been paying attention) is the media processor in android so if you take it out you loose most media playback
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
AT&T is never going to release an patch for my Device.
mrnapolean1 said:
AT&T is never going to release an patch for my Device.
Click to expand...
Click to collapse
No they're not, but CM apparently has stagefright patched.
Maybe it is time to give a custom ROM a shot. :good:
jason2678 said:
No they're not, but CM apparently has stagefright patched.
Maybe it is time to give a custom ROM a shot. :good:
Click to expand...
Click to collapse
I have CM on my Captivate up until my screen took a ****.
Do you know any good tutorials for installing CM on the SIII?
mrnapolean1 said:
I have CM on my Captivate up until my screen took a ****.
Do you know any good tutorials for installing CM on the SIII?
Click to expand...
Click to collapse
There are some guides linked to these forums, but the ones I know of are pretty old and out of date. Samsung pushed Knox with the newer firmware updates, and that really changed how we have to handle this phone. The information you're after has been written all over this forum by many members, myself included, but I can't seem to find a decent post to link to right now. The problem is there is a lot of information, it is all fragmented across thousands of posts, hard to search (hard to find what you're after anyway), and some of the old information can be a little dangerous with the newer bootloaders.
The key to not bricking this phone is to know what bootloader and modem you're on and never, ever try to downgrade it (if you're on a newer one). First thing to do is install the Samsung phone info app from the play store and check your bootloader and baseband. Alternately enter this in a terminal:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
If your bootloader ends in MJB, NE4, or NJ1 don't ever try to downgrade it. The result is a hard brick that is very difficult to recovery from. That means never Odin back to stock if you're on MJB, NE4, or NJ1. The only stock Odin package AT&T allowed to be released is the "ancient", new bootloader bricking LK3 Android 4.1.1 firmware.
If your bootloader or modem end in NE4 or NJ1 you're good to go. You can flash any newer ROM you want. If you're on MJB you're probably ok too. If you're on anything else your mobile data probably won't work with CM 12.1. You'll have to look into updating.
Another good thing to know is that the i747/d2att bootloaders are not locked and have never been locked. Do not attempt to unlock them. Any GS3 bootloader unlock procedure you come across is probably for the Verizon variant, and if you try it on a d2att you'll likely have a hard brick.
Also be aware that the i9300 was marketed as Galaxy S3 as well, but it is a totally different device on the inside. Never flash an i9300 ROM on a d2att phone.
Once you've verified what bootloader/modem you're on, and that it is good to go with CM 12.1, these are the basic steps I'd take if starting with an unmodded phone:
1) Download a SuperSU TWRP flashable zip and store it somewhere on your phone.
2) Use Odin to flash the latest version of TWRP for d2att. Uncheck everything but f.reset time so the phone doesn't auto reboot. Upon success pull battery.
3) Replace battery. Boot straight into recovery by holding vol up + home + power until you see some tiny blue text in the upper left then releasing. If you mess up and accidentally boot into your stock ROM your custom recovery will likely get overwritten with stock and you'll have to repeat step 2 and try again.
4) Flash SuperSU in TWRP.
5) Reboot to stock ROM. Use play store to update your SuperSU binary. You'll probably have to reboot once or twice, but eventually you'll get working root and Knox disabled.
6) In stock ROM open a terminal and enter:
Code:
su
reboot nvbackup
Your phone will reboot. It will seem like a pretty normal reboot, but you'll see some quick flashes of blue text in the upper left if your looking for it. This fixes a Samsung derp and makes sure you have a working EFS backup. This was the only reason we rooted your stock ROM; sorry about all that work just to do this but if your phone ever panics from a bad flash and triggers its autorestore function you'll be happy you did it.
7) Download ROM for d2att and matching gapps. Store them on external SD if you have one. Otherwise verify you can copy files from PC to phone via USB when your phone is booted into TWRP. With TWRP up an running you should just have to plug it in and phone will be recognized by PC as a media device you can transfer files to.
8) Reboot to recovery. Make a backup in TWRP. Store copies on external SD and somewhere off phone for safekeeping. In fact, always keep a nandroid backup or two, a ROM you know works, and a gapps package on an external SD - just in case.
9) Do wipe -> advanced wipe. Tick dalvik, cache, system, and data.
10) Do wipe -> format data. This is why your new ROM and gapps need to be on external SD. Otherwise you'll have a blank phone and you'll have to copy something over via usb or push it via adb to have something to flash. You don't need to do this every time you flash a ROM, but you do need to do it when switching from touchwiz to AOSP and vice versa.
11) Flash ROM
12) Flash gapps
13) Reboot - be patient. 1st boot might take 10 - 15 minutes on a lollipop ROM with this phone.
14) Profit
This probably isn't detailed enough to use as a walkthrough. It will give you an idea what to search and do more research and reading on, and I think I flagged most of the hard bricking pitfalls owners of this phone run into.. Make sure you understand the whole procedure before proceeding. Wouldn't want you to brick your phone trying to deal with a potential vulnerability there's a remote chance you might be targeted with.
Good luck. I made it sound a little scary, but as long as it is handled properly this phone is a flashing beast. If I haven't flashed mine dozens of times, then its in the hundreds. Never had anything go so wrong to the point that I could boot up into recovery and restore or flash my way out of it.
I have NE4 bootloaders
mrnapolean1 said:
AT&T is never going to release an patch for my Device.
Click to expand...
Click to collapse
I never said att, I meant Xposed framework. People release security patches on their all the time
Sent from my Nexus 7 2013 using Tapatalk
Please help, ATT software update broke my phone
Yesterday AT&T pushed a software update for my Galaxy S3. After the reboot, when I tried to open the Settings app, it showed an error "Unfortunately, Settings has stopped." I backed up my data and did a factory reset (using the volume up/home key/power button recovery menu method). However, after reboot, when I start the Android setup process it shows the same "Unfortunately, Settings has stopped" error.
The phone is useless because I can't get past the Android setup process (it shows the error after the first step when I choose English for language). Are there any updated guides on how to flash a stock 4.4.2 rom? I'm not interested in custom roms. I just want my phone back to the way it was before yesterday. I've never done any phone rom flashing so I don't know what tools to use or where to get a stock rom (I would prefer a reputable source so I don't have to worry the rom has been modified). I did some research, but the guides I found seem very outdated, which is not surprising since this is an old phone.
Is your phone now on NJ2? If it is, you may have to install a custom recovery and flash the nj1 boot and system image from here: http://forum.xda-developers.com/showpost.php?p=62318344&postcount=113
audit13 said:
Is your phone now on NJ2? If it is, you may have to install a custom recovery and flash the nj1 boot and system image from here: http://forum.xda-developers.com/showpost.php?p=62318344&postcount=113
Click to expand...
Click to collapse
Yeah, I just checked the recovery menu and it's NJ2. Someone with the same issue started a thread in the other forum. I'll post my replies there so the discussion isn't split.
bitfoolishlogic said:
Yeah, I just checked the recovery menu and it's NJ2. Someone with the same issue started a thread in the other forum. I'll post my replies there so the discussion isn't split.
Click to expand...
Click to collapse
Can you link me to the thread you found? I'm having a very similar problem after that update..
Warning: This post is long, and probably full of grammatical errors due to my writing it late at night. a TL;DR is included at the bottom, but to fully understand my problem, I encourage you to read the whole post.
Hello, xdadevelopers community. I really need your help. So, recently I learned how to install custom ROMs myself and the experience has been really informative but also very struggling. To make a rather long story short, I bought a used G3 from my friend, had him root it, put a custom ROM on it, and everything was working fine. Only, that ROM was on Android 5.1.1, which was contemporary to when it was flashed. I wanted 6.0.1, so I went about getting it. I eventually got that up and running with Resurrection Remix, but the battery life was completely awful. Idle is okay, but using the device results in completely intolerable battery life. I asked Reddit what to do, and someone recommend crDroid for it's great battery life. I attempted to install that, and that's where I got the problems discussed in this post.
Post where I got the ROM and GApps from
Specific ROM and GApps I got:
- crdroid-6.0.1-20160118-vs985
- So I go the one for Android 6.0.1, and the most recent one at that, last updated on the 18th of January, for my G3 model the vs985
- for GApps, I selected "ARM", "6.0", and "Stock" from the menu
Could another problem be that the ROM is 6.0.1, and the GApps are 6.0? If so, open GApps version exists of 6.0.1.
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally. I navigated to the ROM folder it was located it, selected it, and swiped to flash the ROM. I got the following in response:
Installing '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Checking for BASEBAND version 35B
ERROR: It appears you are running an unsupported baseband. assert failed: h3.verify_baseband("35B:MPSS.DI.2.0.1.c1.13.4-00005") == "1"
E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Error flashing zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
So basically it failed to flash, apparently because of both an unsupported baseband version and a failure to execute a certain binary. Well, if you know how to fix the executing issue, that'd be great, although that's now what I'm focusing on here. I'm focusing on the baseband, because I believe that may be causing the failure to execute (although, as a newbie, I'm not sure if that's actually true). Apparently it was looking for version 35B, and that's not what I was running. When I set up my current ROM again just to be able to use the device, and checked for the baseband verion, it simply says "Unknown". Also, if you check out that link to the post above, it says:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
. Well, I never installed a custom kernel, but I assume my friend did, because when looking at the kernel version on my phone it says:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
.
I'm assuming if it was a non-custom kernel it would just have multiple numbers separated by periods, not have all that info, and it specifically says "CM" in there, so I assume that should work, but am not for certain.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
So that's it. I realize this post is incredibly long but feel like if it was shorter, potentially important information would be nixed. I have a TL;DR below for your convenience, but as I just said, to get all the important information, read everything above, please.
TL;DR:
Tried to install a new ROM
Failed
Failing apparently due to unsuppported baseband version
I can't determine my baseband version b/c my settings app returns "Unknown""
If baseband is unsupported, how do I know which are?
Also apparently "E:Error executing updater binary in zip '/sdcard/ROM/crdroid-6.0.1-20160118-vs985.zip' " is a thing. Caused by unsupported baseband version or entirely different problem all together?
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Please read the whole post to get all the detail needed.
NeatAndClean,
Thank you for providing the detailed information in this thread, so let's get to business.
First thing I want to straighten out is that you said your Baseband Version says "Unknown", i think you should check your IMEI information, if your IMEI is "null" then there is another problem to fix first.
If you have tried restoring from a backup after the "Baseband Unkown" issue and the Baseband Version still says "Unknown", then something happened whilst, or after you tried flashing CrDroid. At this moment I am not so knowledgeable about how to fix the Unkown Baseband issue, but it is a well known problem and usually coincides with the IMEI "null" issue. If you still are having that problem, I will try to find out how to fix it.
However, I will provide you with my full answer so this can hopefully get fixed at your preferred pace.
To start out, my questions are:
1. What ROM/Version of that ROM are you running right now? (I assume it is Resurrection Remix 6.0.1?)
2. Do you have a backup before trying to flash CrDroid? If so, I would suggest restoring from your backup to fix your "Settings Unkown" issue.
Once your Baseband "Unknown" problem is fixed, you can continue on to flash CrDroid (This time, it should work). Now I just downloaded the CrDroid zip file, that you used, on my PC. And just from opening it I can already tell that it is deeply based on CyanogenMod, but with some tweaks to make it CrDroid. Reason I mention this is because of this quote:
We're mainly based on CyanogenMod so use custom kernels compatible with them!
Click to expand...
Click to collapse
I'm not super knowledgeable on downloading Custom Kernels, but i do know that your Kernel:
3.4.0-CM-g74498f7
[email protected] #1
Mon Dec 14 09:48:16 EST 2015
Click to expand...
Click to collapse
is (I'm 99%sure) a CyanogenMod Custom Kernel, which comes when you flash a CM ROM.
Mine is:
3.4.0-CM-gc6520f1
[email protected] #1
Click to expand...
Click to collapse
and I'm running CyanogenMod 13, 6.0.1 on my vs985. Point is, you should be all set to flash CrDroid based on your Kernel.
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13.4-00005") == "1");
Click to expand...
Click to collapse
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
This procedure essentially gets rid of the Baseband/Model Check, ensuring a successful flash. Also as you can see in the code, it checks for the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Baseband/Modem version, I believe "xdabbed" makes a flashable version of the 35B:MPSS.DI.2.0.1.C1.13.4-00005 Modem, which should eliminate the need to edit the updater-script. However, I strongly recommend to do the "updater-script" fix rather than trying to flash a different Baseband, as I have heard flashing a new Baseband can easily brick your phone, and you really do not need to do it.
I have Baseband: MPSS.DI.2.0.1.c1.13-00008, which does not match the "Baseband Check" and my ROM still works like a charm after the updater-script fix.
However, before you flash the edited crdroid-6.0.1-20160118-vs985.zip with your TWRP seperately, with the Marshmallow (6.x) ROMs right now, if you plan on using GApps you need to flash the ROM AND the GApps file at the same time in your custom recovery. Otherwise you will most likely get errors and you will need to re-flash the ROM and GApps.
Also maybe the ROM being 6.0.1 and the openGApps being 6.0 is a problem? If so, no openGApps 6.0.1 exist.
Click to expand...
Click to collapse
To answer this, no it is not a problem, you were correct.
1. The LG G3 is an ARM device
2. GApps only uses the first two digits in the OS version (i.e. 5.0.x or 6.0.x) (<==That "x" variable is the third digit in the OS version, and does not matter in GApps
3. All in all you have the correct version of GApps, no you just need to flash it at the same time as your edited ROM.
The procedure you did to flash the ROM was all good:
Basically, I downloaded the two zip files, the ROM and the GApps. I then formatted my device, wiped it, did a real quick, skip through everything set-up of my current ROM, enabled USB debugging, copied the two zip files (ROM and GApps, both of which were inside a folder I made called ROM) onto my devices internal storage (I don't have an SD Card), and rebooted into recovery. I'm using Team Win Recovery Project (TWRP) v2.8.6.1 if that's helpful at all. Once in recovery, again I wiped the device (using the default wipe function in TWRP, then doing an advanced wipe and specifically selecting cache and Dalvik Cache, just to make sure), and went to flash the ROM, finally
Click to expand...
Click to collapse
This is great, again the reason it didn't work was because of the mismatch in the Baseband Check, which shouldn't persist after following the instructions in the "updater-script" fix.
Anyway, back to the baseband. It was looking for a baseband version 35B, which I apparently don't have. I have a few questions about this
1. How are you supposed to know your baseband version if your settings app returns "Unknown"?
2. How are you supposed to know what baseband versions work and what baseband versions don't work on the ROM you plan on flashing prior to doing so? I saw nothing about this from from start to failure to install.
3. If the ROM I intend to flash doesn't support my baseband version, can I install a custom baseband version?
I will admit, I don't even know what a baseband is, and I'm too tired to look it up as I write this.
Click to expand...
Click to collapse
1. The Baseband Version is not supposed to state "Unknown", as i said in the beginning, this is a problem that happens sometimes, I am not sure why, or exactly how to fix it, but if you do some research I'm sure you will find something, I will also do some research so I can try to help you with that if it is not fixed by a Factory Reset or a Restore from Backup
2. The Baseband Version that a specific ROM calls for will be in that "updater-script" I was talking about, at least that's how it is for CyanogenMod based ROMs. I think your stock Baseband Version will work with any custom ROM, as long as it is a ROM made for your specific phone. That being said, I do think that the latest Baseband Version for your specific phone does improve Network, Cellular and GPS Connectivity, but again I do not recommend venturing there yet, until you have alot of background on it and can do it safely.
3. If the ROM you intend to flash doesn't support your Baseband, chances are the ROM is not made for your phone or you somehow have a Custom Baseband that is not made for your phone. I say that because even though you get that Baseband error when flashing CM based ROM, it is still supported, it's just that you do not have the "latest" Baseband Version I believe.
I do believe I have answered all of your questions, at least I hope so. I'm sorry that some things I could not answer in great detail, but I tried my best so that you could continue on enjoying your device. I also have the VS985 so I'm familiar with the device.
Summary:
1. Before anything try to Restore from Backup to fix the Baseband "Unknown" issue, as fixing this is priority. If that does not work I will try to find a fix online, or you can try to beat me to it.
2. Once that is fixed^ you can carry on with the "updater-script" fix i included.
3. Then flash the edited ROM and your 6.0, ARM OpenGApps at the same time (one right after another, without a Reboot in between)
4. Then you should honestly be all set
5. Your Kernel is all set for CrDroid
6. The GApps you said you downloaded is all good for the CrDroid version you downloaded
7. You could also try to flash back to vs985 stock (10B) this will hopefully give you your Baseband back if you still need it after Restoring from Backup
7. You should get no errors now! Yay. Now you can enjoy a Battery Optimized beautiful Marshmallow ROM
Click to expand...
Click to collapse
Please let me know if you have any confusion, I would be happy to provide you with clarification, screenshots etc.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Edit: I'm not sure if Fastboot is actually working. I can't get it to do anything. It just hangs on whatever command I give it, and it continues to hang until I unplug USB, then fails.
I've run into a huge issue. My phone is semi-bricked now, and I don't know what to do. I was getting the baseband version error as well, and I removed the lines in the script and then it failed stating "wrong footer". I tried first installing CM, then like a fool, I installed Cyanogen Recovery over TWRP. Cyanogen Recovery can't do anything. But the install failed. I no longer have any version of Android on my phone, I can't install that baseband package with Cyanogen Recovery. Stock ROMs all come back "wrong footer" as well. I can't install anything. I have Fastboot/ADB installed. Please help!
Click to expand...
Click to collapse
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: forum.xda-developers.com/showthread.php?t=2785089 - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Edit: Sorry, I didn't reach 10 posts yet, so you gotta drag 'n drop the links
Williquah said:
First off, in my response to @NeatAndClean I said to have the Baseband error fixed before proceeding, which is probably what caused your error.
For your Fastboot issue;
1. Make sure you are using the original Slimport cable (over-suggested, I know, just making sure)
2. Try USB 2.0 ports if you got them, if not, give this a shot http://forum.xda-developers.com/showthread.php?t=2256359
3. Try updating the phone's drivers
4. Otherwise, reinstall fastboot/ADB drivers or SDK Tools
5. Alternatively try this http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Assuming you have a VS985, here are stock IMG files:
http://http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
(If you do not have VS985 just find your Model's stock IMG files)
Here are commands you can use in fastboot once you manage to get it working, which will hopefully bypass your "Wrong Footer" issue. Obviously use your stock IMG files.
I would normally recommend flashing full stock TOT with LGFlashTool, but I'm not sure if it may worsen your Unknown Baseband issue (i.e. You may erase your IMEI if you Factory Reset when you have the Unknown Baseband problem) Here is everything you would need for the TOT Method: http://lgflashtool.net/index.php/tot-method/ - Also the old .dll needed for LGFlashTool probably won't work, so search LGUP_8974.dll and use that alongside the TOT instead) <== This should work if nothing else does, however, I don't think it will fix you "Unknown Baseband" but it may... I am not sure.
Finally, if you have ever made a previous backup, and still have it, if you restore from that your Baseband should re-appear and the error should fix itself. (I just figured you tried this already)
I once got the Unknown Baseband and IMEI - null issue, you could try to flash the stock Modem.img file for your phone, and try an IMEI injector program using the IMEI number in the battery compartment (Under the physical battery) But to fix mine I ended up calling the Customer Service and they eventually pushed an update file to my phone. I assume it was a Modem update of some sort, but it was a long time ago so I honestly don't remember.
I wish you good luck, as I know how frustrating these situations are. And keep in mind, I am only trying to help.
Please, to anyone experiencing the "Unknown Baseband Version" issue, focus on that before anything else, as you will most likely worsen your problem the more you do with the issue persisting.
Click to expand...
Click to collapse
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
---------- Post added at 09:09 AM ---------- Previous post was at 08:37 AM ----------
Knux Kitsune said:
Up until this point, I've only had the phone stock with the OTA updates from Verizon. It was updated the day I got the phone, so the baseband must be official, even if not supported by CyanogenMod. I wanna say it's 23B. I tried everything to get fastboot to work. I'm using the original cable that came with the phone "LG Electronics DC1501" plugged directly into a USB 2.0 port on my motherboard. If fastboot doesn't work, I can't flash imgs. An OS doesn't exist. I don't have a versatile recovery (Cyanogen Recovery might as well be stock). You say there's a chance TOT method will erase my IMEI, but you say there is an IMEI injector that can restore it, correct?
At this point, I'm at a loss. I really don't know what else can be done. I'm going to give the TOT method a shot. The website you linked has been suspended, so I'm following the 2015 updated method here: http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Knux Kitsune said:
OMG! It worked! My phone's still activated, so no problems with IMEI. I may be coming on kinda strong, but I LOVE YOU! I spent several hours yesterday, and I've been stressing about it ever since. I even put in a repair request with LG...now I can cancel that request. Thank you thank you thank you!
Click to expand...
Click to collapse
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Williquah said:
@Knux Kitsune Haha I'm glad that you finally got it working, I apologize about the problem with the link... I think I messed up all of the links in my response I'll fix those for the future. But again I'm just glad you got it working with no more problems, thanks for being so patient, XDA is like the best forum out there IMO.
Also, just curious, if you don't mind responding.. I was just wondering, did you use the KDZ method from the link you posted? Just want to know so that I know how many solutions there are for problems like these.
Anyway, enjoy your "new" phone lol, and be careful in the future because I know how painful these situations can be!
Glad you got it fixed!
:good::good:
Edit: The LGFlashTool link literally just got it's domain suspended like minutes after I posted it.. quite ironic.
Click to expand...
Click to collapse
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
*Solution*
Knux Kitsune said:
I actually downloaded the KDZ, but I used the TOT method. I actually almost did it again, because in KitKat, my connection was very unstable, I did install the 35B baseband from XDABBEB, but that didn't fix the problem. I tried updating the firmware legitimately via LG Upgrade Assistant Utility (Verizon), but it kept giving an error everytime it got to 20%. I found no support online to get past this error, so I looked into stock ROMs and found XDABBEB (again) had built a flashable stock ROM for my phone, identical to what Verizon released last month, but with root access. I flashed TWRP 3.0 with Flashify, then flashed the ROM. The first time I flashed it, the phone showed that the phone service had stopped responding, a dialog box that only comes up once per cycle...super annoying. I managed to get back into Flashify and attempted installing the ROM again. I was actually prepared to do another TOT flash if it still had issues, but the second time wiping and flashing worked. My connection is solid, and I've had no errors (so far). It seems to run faster on Marshmallow than it did on Lollipop. It's pretty much the end result I was going for when I tried upgrading some 35 hours ago.
Update: Apparently, my baseband is fixed now. It did say Unknown before, even after flashing the 35B baseband from XDABBEB (initially anyways, reflashed after wipe just before flashing the ROM), but now it says "VS985-MPSS.DI.2.0.1.c1.13.4-00005-M8974AAAAANPZM-1"....so that's...good?
Click to expand...
Click to collapse
Awesome, well that's good that you eventually reached your goal. I can't say for sure why your connection was unstable on the Stock Kit Kat, but the 35B baseband is for 35B (5.1.1) Lollipop. The TOT method flashes back Stock Firmware, which is 10B (I believe 4.2.2) - KitKat so you would then need the Stock Modem IMG: (10B Modem File) but you are past that.. which is great. The Phone Service not responding is, I'm sure, a result of the incompatible 35B Modem mixing with 10B (4.2.2) Software Version. That's why flashing XDABBEB's Stock ROM fixed it (at least the second time around), because it includes all the stock IMGs, including the stock Baseband Version (10B).
But I'm so glad that you re-flashed and wiped again, because you have literally managed to return it to complete stock. Your baseband is official, and seems to me.. completely fixed!
Just confused with this:
It seems to run faster on Marshmallow than it did on Lollipop.
Click to expand...
Click to collapse
Are you running Marshmallow now? Or Kit Kat? I think I just lost you at some point haha.
But congrats on fully flipping your situation around! And in fact, because you fixed your Baseband issue, this thread is now completely answered! :good:
The TOT Method does wonders, doesn't it :victory:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Knux Kitsune said:
Sorry, the stock ROM I used is http://forum.xda-developers.com/ver...t/vs985-46a-stock-flashable-firmware-t3304365
It's identical to what Verizon sent out last month except it is rooted, which I don't know why phone providers are so against letting their customers have full access to phones they either own or are leasing. I own this phone. It's paid in full. I want root access... Anyways, yes, it's Marshmallow.
Click to expand...
Click to collapse
Ohhh, I see. I totally agree with you, it really makes no sense... the phone was built a certain way, it was meant to be used like that. Why the providers "nerf" them, I don't know. Even with the FM radio, they disable the receiver on the phones, I assume so that we are forced to stream instead, and they make more money. It's absolute sh**. But yeah, alright well that's cool, I might have to flash that myself actually, Marshmallow is lookin' really nice, as long as the battery life ain't too bad I'm gonna test it out myself!
Excuse me, first i´m sorry for my bad english language. I have same problem the unsupported baseband, but till now i just feel confused. I flash the Resurrection Remix Nougat on twrp and says unsupported baseband error. What should i do first? Flash the new baseband? If it yes, which baseband version is suitable for my device. Im using LG d855 and running android 6. Or i must unlock bootloader before flashing the new ROM? Thankyou, hope anyone will answer my stupid question.
I am using micromax q372 smartphone, had an android 5.0 stock ROM, and now i have installed resurrection remix 5.5.9, and my DEVICE OFFICIALY DOESN'T SUPPORT, and I garbed all of my luck and installed it, and now I have a fully working custom ROM on a unsupported device, the only problem I had was with the data connection, and I sorted it out, now everything is working, .............now I want to install resurrection remix 5.9.X , and my device doesn't is not on the support list, so ....can I do it , without any bugs? .......plz advice me