Develop Bugs

[Q] Can I realy just flash to CM10.1 or do I still need to root first?

I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?

You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.

Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.

I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.

Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.

[Q] SGH-T989 Help Needed Please with Baseband!

Hello everyone i hope someone can help with my issue. I have done an extensive search in regards to my issue but can not find a true answer so i hope some one can help here. I was given a US based T-mobile SGH-T989. When I got it I could swipe to open phone but screen would be comepletly black. I did a wipe and restore but no luck. I used Odin to flash newest stock rom and had same result.. I then decided to flash it with stock shipped rom which was Gingerbread and phone was up and running except for one lil problem the Baseband, IMEI and such were all unknown. I have been searching to see if I could try and flash baseband but havent been able to find anything understandable or even for the T989. could anyone please advise me of what i could do to fix this problem? I do realize that maybe the Baseband chip itself could be the issue but i would like to try and flash it fresh first before i declare this phone toast. thank you all in advance. If this problem has been posted before my apologies i could not find a thread for the T989 with this issue non the less one with US T-Mobile baseband files.

Never-E-Nuff said:
. If this problem has been posted before my apologies i could not find a thread for the T989 with this issue non the less one with US T-Mobile baseband files.
Click to expand...
Click to collapse
Baseband=radio.
Try the radios from this thread:
http://forum.xda-developers.com/showthread.php?t=1895400
You will need a custom recovery(CWM, TWRP) to install them.

meekrawb said:
Baseband=radio.
Try the radios from this thread:
http://forum.xda-developers.com/showthread.php?t=1895400
You will need a custom recovery(CWM, TWRP) to install them.
Click to expand...
Click to collapse
Couldnt I use Odin to flash the baseband? the phone is not rooted it is stock. i would like to keep it that way if possible untill issue is resolved but if the only way to fix the problem is to root it let me know.

Never-E-Nuff said:
Couldnt I use Odin to flash the baseband? the phone is not rooted it is stock. i would like to keep it that way if possible untill issue is resolved but if the only way to fix the problem is to root it let me know.
Click to expand...
Click to collapse
You can take the two radio files out of the zip(amss.bin & mdm.bin) and tar them up with
tar -cvf name_for_tar_file.tar amss.bin mdm.bin
But you don't even need to root to install a custom recovery. Just Odin one of the tar files from here:
http://techerrata.com/browse/twrp2/hercules
And install the radios from the thread I linked earlier.

meekrawb said:
You can take the two radio files out of the zip(amss.bin & mdm.bin) and tar them up with
tar -cvf name_for_tar_file.tar amss.bin mdm.bin
But you don't even need to root to install a custom recovery. Just Odin one of the tar files from here:
http://techerrata.com/browse/twrp2/hercules
And install the radios from the thread I linked earlier.
Click to expand...
Click to collapse
So i did what was recomended and still same issue no IMEI or Baseband says Unknown. So is it possible that The radio I choose was not a good one or is my Baseband chip bad? when I installed the zip from recovery it said install successful but obviously it did not work. starting to think i have a paper weight at this point.

Never-E-Nuff said:
So i did what was recomended and still same issue no IMEI or Baseband says Unknown. So is it possible that The radio I choose was not a good one or is my Baseband chip bad? when I installed the zip from recovery it said install successful but obviously it did not work. starting to think i have a paper weight at this point.
Click to expand...
Click to collapse
It is possible that you have a hardware problem. I would try all the radios just to be sure though. Good luck.

[Q] CM10.2 MK3 build support?

I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!

WoodenDiamond71 said:
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
Click to expand...
Click to collapse
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3

joeyhdownsouth said:
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
Click to expand...
Click to collapse
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.

WoodenDiamond71 said:
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
Click to expand...
Click to collapse
You should be also getting a status 7 error, because the bootloader you currently have (MK3) is not listed as one of the "approved" bootloaders in the updater-script for any 4.3.x ROM based on AOSP. You will need to go into the updater-script and modify one of the lines to match your bootloader, or get rid of the assert lines altogether. Any KitKat 4.4.x ROM's will have your bootloader listed, so this is not necessary for the newest ROM's.

How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk

WoodenDiamond71 said:
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This is a tutorial I have put together on Android Forums for the rooted Virgin Mobile community (SGS3), since we have to always modify or delete the asserts in order to get Sprint ROM's to flash on our phones. Principle is the same for any Sprint user in your situation. I also just made a YouTube video showing how to do the relevant parts of my tutorial.
https://www.youtube.com/watch?v=IZnYSrUIXKM
Hope this helps! Feel free to PM me if need be for any clarification.

Sweet!! Thanks I'll check it out later once I get out of work. Thanks once again I'll pm if it worked
Sent from my SPH-L710 using Tapatalk

BRICKED... help?

Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.

Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.

BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock

Kies interferes with odin. Uninstall it from your computer and try odin again.

DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad

Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?

audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP

What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.

DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.

Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.

I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here

You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.

DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4

Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.

BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,

Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4

BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!

[Firmware][4.4.2] NE4/NE6/NF2/NH2 Recovery Flashable Firmware

Links removed while investigating the cause of a couple of bricks. Sorry, but don't want to have any more of these happen!
I747 and I747M 4.4.2 Firmware
NE4 / NE6 / NF2 / NH2
For use with TWRP, CWM or Philz Recoveries​
The following packages will flash the base 4.4.2 firmware to your device. This can be used to update to the latest build, or in the event that you need to reflash it for whatever reason. The following partitions will be flashed:
aboot - AP Bootloader
NON-HLOS - Modem/Baseband
rpm - Resource and Power Management
sbl2 - Secondary Bootloader 2
sbl3 - Secondary Bootloader 3
tz - Trust Zone​
This will NOT flash the system, cache, recovery or boot (kernel) partitions, so it will preserve your current Rom, Recovery and Kernel. There is no requirement that you be on a certain build prior to flashing this, though I will not make any guarantees you will not encounter some issues if making a large jump in versions, such as going from 4.0.4 or 4.1.1 straight to 4.4.2. It should be fine, but I'm just not making any promises.
General Disclaimer
As with everything you use here on XDA, you use this at your own risk. I would not release this if I felt it were unsafe, but things do go wrong, even with fully tested and vetted projects.
How It Works
Flash in the custom recovery of your choice. (Initially tested on TWRP 2.8.0.1)
Once the flash is initiated, it will run the "assert" checks we should all be getting used to by now. This is to prevent downgrading and bricking your device!
Next, each of the firmware files are checked for any corruption using the sha1 checksum. If it fails any of these checks the flash will abort without actually flashing anything.
After passing these checks, the flashing begins! The modem is flashed last! This is in case anything goes wrong, there is no way to end up with a 4.4.2 modem on 4.3 bootloaders!
Once complete, reboot and you are done!
I747M Unified Packages​"One Package To Rule Them All!"
You may notice that each I747M build is for each of its relevant carriers, rather than having individual packages for every build, every carrier. While rebuilding these packages, I noticed that they are identical regardless of the carrier. For example, the base firmware in Bell's NE6 is identical to Koodoo's, Sasktel's and Telus'. The same is true for both NF2 and NH2! So we only need one flashable zip for each version! In other words... One Package To Rule Them All!!
REMEMBER!!!​Once you update, there is no going back! You cannot flash older firmware, so once you flash to 4.4.2, that is the only firmware you can flash from now on!
DOWNLOADS
I747
UCUFNE4 - AT&T
I747M
VLUFNE6 - Bell, Koodoo, Telus
VLUFNF2 - Fido, Rogers
VLUFNH2 - Bell, Koodoo, Telus
​
I hope these prove useful for some of you! Good Luck!
Thanks to:
@Aerowinder - for his script I borrowed from a similar project for the T999 and helping fix some issues!
@enewman17 - for everything he does around here, and helping me to solve some problems along the way!
@mnasledov - for doing this the first time for the T999
everyone - for their patience while I got this working!

Reserved

never before, so here goes...
1st.
thank you doc
will ride this huckleberry-special from Fort Dodge to the end of the line. (still on mj2). had just downloaded the S3Rx from @enewman17
err on the side of kindness

Cool! Let me know how it goes!

flashed on my brothers S3 i747(my old S3). flawless.
:good:
err on the side of kindness

Right on! Thank you for trying it out and reporting back! Very much appreciated!

Corrupt
Been flashing the Koodo one and all I get is a corrupt error...

Did you check the md5 on the download?
If that matches up and youre still having issues copy the recovery log to sd and then attach it to your post.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Did you check the md5 on the download?
If that matches up and youre still having issues copy the recovery log to sd and then attach it to your post.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
DLed multiple times, checked the Md5 on my PC and the phone. Can't get the log as a file, this device has been hell. Koodo is an awful company, I've gotten two phones from them and they've both had countless hardware issues and incompatibilities with otherwise standard files, I don't know if they pay discount for Samsung's dropped merchandise or what. TWRP doesn't work at all, only CWM, when I boot TWRP it just can't find any storage medium whatsoever.
Anyway, all it says when I show it is that it verifies the checksum, finds corruption,and aborts. There's a bit below it as well, copied everything meaningful:
minzip: extracted "/tmp/sb12.mbn",
minzip: extracted "/tmp/sb13.mbn",
minzip: extracted "/tmp/tz.mbn"
verifying checksums...
FILE CORRUPTION DETECTED!!! Script result was [7]
aborting
cleaning up

Ok, ill double check it shortly. I know in twrp's advanced menu there is an option to copy log to sd. Are you sure cwm doesnt have the same? Id be surprised if it didnt.
Sorry for the trouble though. It is possible i made a simple mistake somewhere. If so i will find and fix it.

Everything checks out so far on my end. Im downloading the firmware again in case something went wrong there.
In the meantime, what recovery are you using? Maybe try using a different one ir a different version?

Ok, ive checked everything on the Koodoo firmware and i couldnt find anything wrong. Picked it apart twice, re-downloaded the original firmware and checked that nothing was corrupt. Other than the recovery, i cant think of any other reason itd be failing like that.
Might be best for you to flash the full firmware with odin if using a different recovery doesnt work.

mrrocketdog said:
flashed on my brothers S3 i747(my old S3). flawless.
:good:
err on the side of kindness
Click to expand...
Click to collapse
What recovery did you use?

twrp 2.6.3.1(att)
err on the side of kindness

Thanks. Kinda suspected as much. The update binary may not be compatible with the latest version.

DocHoliday77 said:
Everything checks out so far on my end. Im downloading the firmware again in case something went wrong there.
In the meantime, what recovery are you using? Maybe try using a different one ir a different version?
Click to expand...
Click to collapse
CWM 6.0.4.7. TWRP doesnt work for me.

JohnHorus said:
CWM 6.0.4.7. TWRP doesnt work for me.
Click to expand...
Click to collapse
So are you saying CWM worked for you then?

DocHoliday77 said:
So are you saying CWM worked for you then?
Click to expand...
Click to collapse
No, TWRP doesn't work AT ALL for me. It can't even locate my internal SD.
CWM 6.0.4.7 is all I've tried with.

I dont use cwm so im not sure about the version right off hand. If thats the latest, try a slightly older one, or if its older try the latest.

I got file corruption error in at&t i747. Did not tried to flash again. Using latest twrp recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app