Develop Bugs

[Q] Bell Desire Z stok Rom

Hi
I'm desperately looking for any Bell mobility stock 1.34.666.5 or Over.
The camera button is not working so I sent my phone to repair but they send it back because I do not have the right rom that was provided with my phone. I was able to unroot and put back 1.34.666.1 (the only one that is available it seems) but the technical support told me that my phone shipped with 1.34.666.5 and that they can't do anything unless I'm putting back this rom.
I tried getting OTA updates for 1.34.666.1 but it's not available. Minimum rom # to get OTA updates have to be 1.34.666.5
I'm screwed.
Regards

I have a nandroid backup of the stock ROM...it's rooted though.

Will I be able to flash using Clockwork Recovery? I can manage to remove root after flashing, I think.

Yes, flashable via Clockwork.
I'll let you know when I have it uploaded.

...and it's up.
https://xda:[email protected]/_xda/Bell.DZ.Stock.ROOTED.7z
Some notes:
- I only included the system and boot portions of the nandroid backup due to privacy concerns
- As such, you should do a system and boot restore (after a full wipe, of course) under "Advanced Restore"
- As mentioned earlier, this is rooted (so you'll need to unroot)
Hope this helps. Let us know how it goes.

Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.

Tonkadan said:
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Click to expand...
Click to collapse
That's good to hear. I'd recommend making your own nandroid backup immediately.
As for the bootloader, you're sure you flashed the ENG HBOOT during the rooting process? If that's the case, I'm not sure where you can find the stock HBOOT...

Yes, I installed the Eng HBoot.
I'm trying now renaming the OTA update.zip, put on the root of sdcard and make recovery to install that update but I got an error about getprop CID?? and the update failed...
Still looking for a solution.

How did you make out Tonkadan? I'm in the same boat. I heard that if you did apply this update that you would not be able to root your phone anymore.

I' still rooted. I'm unable to go back to stock. I'm using cyanogenmod 7 for now but would really want to go back to stock if somone have the official Bell rom over 1.34.666.5.

... Or any way to get OTA updates for RUU 1.34.666.1 that is available on shippedroms.com

Please help before i burn this phone

So, my issues just started today. I was rooted but went back to the MC2 rooted restore. After the successful restore I made a mistake and clicked yes for the System Update. Then the problems came. The phone was stuck in factory mode. I researched and it told me to go to efs under Root Explorer. I did that but it said the phone wasnt rooted. Tried to restore it again. Now I'm getting the Kies firmware upgrade encountered. Did my research and fixed that. How do I get back to a rooted phone?????? I still get the black box with yellow writing saying factory mode. Please help!!!!!!!!!!!!!!!!!!!!!

Need more info:
1. MC2 rooted restore?
2. What is factory mode?
3. Are you on 4.3?
You could try this......ODIN TWRP and follow @billard412 guide to getting back to stock unrooted. Then ODIN TWRP again and flash a custom ROM of your liking. Hope this helps in getting back to a rooted phone!

92bubble said:
So, my issues just started today. I was rooted but went back to the MC2 rooted restore. After the successful restore I made a mistake and clicked yes for the System Update. Then the problems came. The phone was stuck in factory mode. I researched and it told me to go to efs under Root Explorer. I did that but it said the phone wasnt rooted. Tried to restore it again. Now I'm getting the Kies firmware upgrade encountered. Did my research and fixed that. How do I get back to a rooted phone?????? I still get the black box with yellow writing saying factory mode. Please help!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Agreed with flynhawn2002 Where are you coming from with your phone setup. Did you just wanted to root the stock? Or what ROM did you wanted to flash? We need the specific so we know exactly what you were attempting to accomplish. Hang in there!

Sorry about that. Yes its now on 4.3 MK4 after I clicked yes for the system update by mistake. Yes Id like to go to the MC2 rooted restore. But Ive tried and it wont work. 20% into the download mode it'll say failed on the odin and back to the Kies firmware encountered bull****. Then I have to go to Kies and restore the firmware all over again.

I just want to go back to a rooted restore. After that Im good to go. Oh yea. I put TWRP recovery on it through ODIN successfully.

ok....if you had issues following my above recommendation then you can follow lorjay589's guide to get stock rooted. FYI, you need to remove KNOX before installing SuperSU or youll have issues.

fixed...thanks alot people!!!

ROMs Removes Modem - Cannot Restore Modem

Ill admit that Im not the best at this, but Im not too new to rooting, roming, or flashing (so now you know I might be the reason). Out of all, I've never done anything like the Sprint Note 2 where flashing a ROM removes all phone info, IE. IMEI, Baseband Unknown.
I tried restoring EFS and Modem (which I backed up beforehand); manually installed modems; all to no avail. Basically I have to recover by starting from scratch using http://forum.xda-developers.com/showthread.php?t=2591898.
What am I missing?

Anyone? I really hate the stock.

Personally I prefer using this stock MC2 unrooted ROM with flash count reset. Found here: http://forum.xda-developers.com/showthread.php?t=2086769
This will put you back at pre MK4 state as well as flash the modem. bootloader, etc. From there you can re root, flash Phil's recovery 6.07.9 and flash a custom ROM of your choice. This is how I would do this and IS how I do this from time to time. I never use the stock unrooted MK4 due to the KNOX crap.

tx_dbs_tx said:
Personally I prefer using this stock MC2 unrooted ROM with flash count reset. Found here: http://forum.xda-developers.com/showthread.php?t=2086769
This will put you back at pre MK4 state as well as flash the modem. bootloader, etc. From there you can re root, flash Phil's recovery 6.07.9 and flash a custom ROM of your choice. This is how I would do this and IS how I do this from time to time. I never use the stock unrooted MK4 due to the KNOX crap.
Click to expand...
Click to collapse
So the process in which I done this would cause such affect? The MK4 I used did restore everything; recovery, modem, etc.
I used Odin to load TWRP 2.7 recovery (let it root), booted to recovery again and installed Dr Katan's MultiTool to remove Knox, and then updated SuperSU. This is where I stand now and it's operating fine, just hate the crap Sung put in there.
Is TWRP no good for L900? is Phil's Recovery the defacto or just your experience? Just curious if Im doing something wrong or?
My goal is to have vanilla as I can have it with the exception of WiFi tether and a radio that doesn't suck.

nimrod.sixty9 said:
So the process in which I done this would cause such affect? The MK4 I used did restore everything; recovery, modem, etc.
I used Odin to load TWRP 2.7 recovery (let it root), booted to recovery again and installed Dr Katan's MultiTool to remove Knox, and then updated SuperSU. This is where I stand now and it's operating fine, just hate the crap Sung put in there.
Is TWRP no good for L900? is Phil's Recovery the defacto or just your experience? Just curious if Im doing something wrong or?
My goal is to have vanilla as I can have it with the exception of WiFi tether and a radio that doesn't suck.
Click to expand...
Click to collapse
Read the L900 TRWP thread for the last 6 months...and you will see issue after issue...and 6 months later it is still not fixed according to users. Funny thing, is this only effects L900 Note 2 users. AFAIK no other Note2s or other devices are effected.
Either use a 2.6.* TWRP build to flash 4.1 ROMs, or use PhilZ for AOSP ROMs.

I just wanted to point out that since you are back on the stock MK4 ROM you will not be able to use the built-in WiFi hotspot unless you subscribe and pay for it. You can't flash the MK4 hotspot hack on your current stock odexed ROM. You will need to flash a stock rooted deodexed ROM that has hotspot hacked already or you will have to flash the mk4 hotspot hack for a deodexed stock ROM.
I'm saying this because you did point out in your previous post that you wanted to be able to use the hotspot feature. There may be another tether app that will work without root but I'm not aware of any.

see my post in this forum
nimrod.sixty9 said:
Ill admit that Im not the best at this, but Im not too new to rooting, roming, or flashing (so now you know I might be the reason). Out of all, I've never done anything like the Sprint Note 2 where flashing a ROM removes all phone info, IE. IMEI, Baseband Unknown.
I tried restoring EFS and Modem (which I backed up beforehand); manually installed modems; all to no avail. Basically I have to recover by starting from scratch using http://forum.xda-developers.com/showthread.php?t=2591898.
What am I missing?
Click to expand...
Click to collapse
I made a post about my experience loading a custom rom. I hope it is of some help to you. I believe I also started with MD4. What I think they did starting with MD4 (possibly a bit earlier) is they have a partition for the carrier/radio, and that gets wiped out when you load other roms, so you lose your radio. If you go back to LJ4 and then load the other roms, you might have more luck.

[Q] Help!! ROM flashing problems

Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/

dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486

Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help

dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991

Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?

dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks

AT&T OTA update; stops at Samsung splash screen

I have been reading through many threads last night and today trying to figure out the best way to get rooted stock back on my AT&T S3 i747. I had hoped to figure it out myself, but have come to the realization that I need a little guidance.
In light of that, I'll try to give concise information. First of all, I am simply looking to end up with stock.
Series of events:
*Have had stock since given this phone in August; it was kept up to date with OTA and it was current (4.4.2) as of yesterday morning when att pushed the newest update to the phone.
*I rooted the phone in September using CF root and Supersu to both root and block Knox and it had been working very well until the attempted update yesterday.
*I no longer have a custom recovery backup
*yesterday my phone went through the update (download and install), but when it rebooted, it only made it through the Samsung splash screen and then went black.
*I am able to boot up both stock recovery and into download mode
*Using the stock recovery to reset the phone has not fixed the problem
Having never used Odin or installed a custom ROM, I am hesitant to flash anything to the phone until I verify that the new bootloader (that is now possibly there due to the OTA update) and anything I try to install won't conflict and make my problem worse.
It seems to me that I should use Odin to load a custom recovery, make a backup, and then flash a ROM. If that is correct, would the recovery ROM found in this thread be the correct one: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
If it is not the correct ROM, what would be the correct one?
Thank you,
M

For a custom recovery, flash the most recent tar.md5 file from here using Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Boot into recovery, create a backup, and flash a custom ROM. I recommend the most recent CM10.2 so you can determine the bootloader currently installed on your phone. Once you determine the bootloader, you can decide how you want to proceed.

Thank you so much for your response.
I did as you suggested and I do indeed have the UCUFNJ1 bootloader. That does help me determine which direction I can take. Although, now having tried out a non-Samsung ROM, I may have changed my mind about keeping stock on the phone. If I decide to go back to stock, I'll just keep my eyes open for a stock ROM that states it requires that bootloader, correct?
Again, thank you so much for your help!