Related
Does anyone know of any working Telecom NZ working ROMs? Stock won't flash and I'm stuck with a soft bricked Atrix 2.
System.img has an incorrectly permissioned build.prop and no system.img's will flash.
Webtop (grfs.img) is flashing wrong and creating the Invalivd CG OTV and CG Version errors.
I want to find a working (custom rom) that will hopefully work on my telecom atrix.
Any takers?
Hey mate,
williamguy said:
Does anyone know of any working Telecom NZ working ROMs? Stock won't flash and I'm stuck with a soft bricked Atrix 2.
Click to expand...
Click to collapse
Here's a link to a TNZ ROM: http://sbf.droid-developers.org/edison/5.5.1-EDEM-28-TNZ_cfc.xml.zip - haven't tried this one tho.
I had softbricked my TNZ atrix 2 recently and this rom worked perfectly for me: http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-MEARET_cfc.xml.zip. From there I Installed the JB Leak one which I currently use. For some strange reason, it would not boot up completely without installing the MEARET ROM beforehand.
Just in case - I have been using RSD Lite 6.15 for all my flashing needs (https://www.dropbox.com/s/2y92rn0xkeeuc36/RSDLite6.1.5.zip)
Cheers
hello all, my friend owned ATT atrix 2 , ithink it using
http://sbfdownload.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
Click to expand...
Click to collapse
he want to flash sbf asia verison
http://sbfdownload.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Click to expand...
Click to collapse
but when it flashing , "fail" error message appear
reach at Level 7 it Become "fail"
mean it can't flash the asia version
any help?
guffoe said:
hello all, my friend owned ATT atrix 2 , ithink it using
he want to flash sbf asia verison
but when it flashing , "fail" error message appear
reach at Level 7 it Become "fail"
mean it can't flash the asia version
any help?
Click to expand...
Click to collapse
You can't do that. AT&T phones can ONLY use AT&T firmware. This had been said repeatedly all over this forum. If you and/or your friend would have bothered reading a little you would know that already. Next time read everything related to your (or your friend's) phone. Then read it all again, and even if you think you understand, read it again. Make EXTRA sure you know what you are doing before you do anything. That being said, try to flash the FXZ from the first link you posted. That is, if the phone hasn't been bricked already. If that doesn't work then I'm afraid your friend now has an expensive paperweight. I hope your friend is a nicer guy than I am. Good luck!:thumbup:
Brought to you by time and relative dimensions in space.
You can flash that on AT&T.
!WARNING! This metod is only for advanced users... If don't know what is CID. Don't flash that files!!!
OLD MY POST (to prove that metod is working on AT&T A2): http://forum.xda-developers.com/showthread.php?p=42246899#post42246899
But I don't recomended that... And also DON'T TRY TO FLASH RETAIL A2 FW VIA RSD EVEN WITH ERASED CID!!!
turffe said:
You can flash that on AT&T.
!WARNING! This metod is only for advanced users... If don't know what is CID. Don't flash that files!!!
OLD MY POST (to prove that metod is working on AT&T A2): http://forum.xda-developers.com/showthread.php?p=42246899#post42 246899
But I don't recomended that... And also DON'T TRY TO FLASH RETAIL A2 FW VIA RSD EVEN WITH ERASED CID!!!
Click to expand...
Click to collapse
What exactly do you by the method is "working on AT&T A2"? I watched the YouTube video you linked in another post and saw the phone boot up, but then I appears that it is showing an error message.(possibly a force close of some sort. Sorry, I can't read whatever language that was in) Then the video stopped before showing the phone in a usable state. Can you provide verification that the phone is usable after doing what you are suggesting? I ask because to me there is a difference between booting up to endless force closures and booting up to a useable phone.
1BadWolf said:
What exactly do you by the method is "working on AT&T A2"? I watched the YouTube video you linked in another post and saw the phone boot up, but then I appears that it is showing an error message.(possibly a force close of some sort. Sorry, I can't read whatever language that was in) Then the video stopped before showing the phone in a usable state. Can you provide verification that the phone is usable after doing what you are suggesting? I ask because to me there is a difference between booting up to endless force closures and booting up to a useable phone.
Click to expand...
Click to collapse
First: Youtube video is about China 4.1.2 not working - if see youtube video name... (touchscreen not working)!!! ,2nd: Mearet ICS booted fine - if you also seen screenshots under my post. It's says on AT&T kernel builded in 08.31, but Mearet kernel build date is in August 20... JB is in JANUARY...
turffe said:
First: Youtube video is about China 4.1.2 not working - if see youtube video name... (touchscreen not working)!!! ,2nd: Mearet ICS booted fine - if you also seen screenshots under my post. It's says on AT&T kernel builded in 08.31, but Mearet kernel build date is in August 20... JB is in JANUARY...
Click to expand...
Click to collapse
I see. I must've misunderstood. Thanks for the clarification. So what are the implications of this exactly? Does this mean AT&T owners are not limited to AT&T firmware so long as they back up their CID?
Brought to you by time and relative dimensions in space.
1BadWolf said:
I see. I must've misunderstood. Thanks for the clarification. So what are the implications of this exactly? Does this mean AT&T owners are not limited to AT&T firmware so long as they back up their CID?
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
Yes, that means it's same like in RAZR - we can use any A2 (Indian MB865, China ME865 or any A2 kernel)... But different A2 models is different hardware (for example radio chip), so if we flashed ME865 fw via CID erasing we posible will have Wi-Fi disconnection issues & etc...
And also this means that we can convert AT&T MB865 to China ME865 and use Official MIUI on AT&T without battery issues (this is only hypothetic, tomorrow i'll test it).
Hi turffee!
Your device is AT&T Atrix 2?
The bootloader of your device is unlocked?
please put this command to terminal emulator, or adb shell with su
cat /proc/omap_dev_type
If this returns NS, can you share your mbm.img and mbmloader.img?
dd if=/dev/block/mmcblk1p1 of=/sdcard/mbmloader.img
dd if=/dev/block/mmcblk1p2 of=/sdcard/mbm.img
Thanks
My device is AT&T. It HS device. There's one thread with unlocked A2 it returns command to NS. That person also shared mbmloader.bin & mbm.bin for public (only for devs) - also if you'll find that files (thread) DON'T TRY FLASHING NS BOOTLOADER TO HS DEVICE (including all A2) or you'll hard bricked!!!
Also about CID erasing. Then you erase your CID, your device loosing region identification, so you can flash any A2 firmware. Bootloader is still locked, like & many others inxluding Jim's A2, it's just bypassing region...
Sent from my MB865 using Tapatalk 2
turffe said:
My device is AT&T. It HS device. There's one thread with unlocked A2 it returns command to NS. That person also shared mbmloader.bin & mbm.bin for public (only for devs) - also if you'll find that files (thread) DON'T TRY FLASHING NS BOOTLOADER TO HS DEVICE (including all A2) or you'll hard bricked!!!
Also about CID erasing. Then you erase your CID, your device loosing region identification, so you can flash any A2 firmware. Bootloader is still locked, like & many others inxluding Jim's A2, it's just bypassing region...
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Actually no, my dev phone is a NS device, and has the correct Efuses flipped, it is NOT just a region bypass, it also has writting all over it stating that it is not for resale.
turffe said:
You can flash that on AT&T.
!WARNING! This metod is only for advanced users... If don't know what is CID. Don't flash that files!!!
OLD MY POST (to prove that metod is working on AT&T A2): http://forum.xda-developers.com/showthread.php?p=42246899#post42246899
But I don't recomended that... And also DON'T TRY TO FLASH RETAIL A2 FW VIA RSD EVEN WITH ERASED CID!!!
Click to expand...
Click to collapse
thank for your advanced feedback , :good:
i'm on miuiv5 3.5.31 (china version)
now i want to flash leak3 JB china 4.1.2 to get access for miui v5 updating rom
which method that i'm gonna do?
honestly i'm super-noob motorola user here,
please help me
Hello,
I bought an Atrix 2 at ebay (the seller said it is new), unfortunately there is Cyanogen Mod with Android 4.1.2 installed. If there is any safe way to flash back to stock I would prefer this, instead of sending it back because I live in Europe and bought it in USA .
Could you recommend me an easy secure way to flash back to a stock rom? Unfortunately I don't know where to start.
Thanks,
c.
calualeaf said:
Hello,
I bought an Atrix 2 at ebay (the seller said it is new), unfortunately there is Cyanogen Mod with Android 4.1.2 installed. If there is any safe way to flash back to stock I would prefer this, instead of sending it back because I live in Europe and bought it in USA .
Could you recommend me an easy secure way to flash back to a stock rom? Unfortunately I don't know where to start.
Thanks,
c.
Click to expand...
Click to collapse
To be honest, the best thing you can do right now is read. All of this has been covered before, repeatedly, and all the information is readily available as well as easily accessible. What you don't want to do is start flashing things without knowing what you're doing and how to get yourself out of trouble should you encounter any issues. So take your time and browse around the forums and familiarise yourself with the various flashing procedures. You won't regret it.:thumbup:
Brought to you by time and relative dimensions in space.
1BadWolf said:
To be honest, the best thing you can do right now is read.
Click to expand...
Click to collapse
Ok, ok, you are right so I found these two threads, so I think I know now how to flash and where to find fxz. But I don't know which fxz Version is the right one, my Phone don't have a at&t logo on the cover. I expect that it is a US Version but I'm not sure.
Noob Guide: http://forum.xda-developers.com/showthread.php?t=1396650
ATT 4.0.4 http://forum.xda-developers.com/showthread.php?t=1961310
other 4.0.4 firmwares: http://forum.xda-developers.com/showthread.php?t=1934874
I've read about that it does matter if you have installed leak #1 or #2 or the OTA stock firmware. I don't know which was installed before the custom ROM.
Could you help with these two questions?
calualeaf said:
Ok, ok, you are right so I found these two threads, so I think I know now how to flash and where to find fxz. But I don't know which fxz Version is the right one, my Phone don't have a at&t logo on the cover. I expect that it is a US Version but I'm not sure.
Noob Guide: http://forum.xda-developers.com/showthread.php?t=1396650
ATT 4.0.4 http://forum.xda-developers.com/showthread.php?t=1961310
other 4.0.4 firmwares: http://forum.xda-developers.com/showthread.php?t=1934874
I've read about that it does matter if you have installed leak #1 or #2 or the OTA stock firmware. I don't know which was installed before the custom ROM.
Could you help with these two questions?
Click to expand...
Click to collapse
Post a screenshot of your about phone screen. The build date is the give away, on the kernel. When you post that one of us can point out if you have leak one installed.
I will be very honest here, and since you are not sure which stock version was on the phone before, you have a high chance of bricking the phone. If does not have the ATT logo, it does not tell us much. You could still have an HK version of the phone which is as locked down as the ATT one is, or you could have an Asian version, which would be good, since they are not as locked down...
I would tread very lightly here, and I would tell you to just flash another non-stock ROM from the dev section, on it, as that won't brick you.. But you really need to find a way to figure out which phone you have.
jimbridgman said:
Post a screenshot of your about phone screen. The build date is the give away, on the kernel. When you post that one of us can point out if you have leak one installed.
Click to expand...
Click to collapse
Attached you will find two screenshots, thanks for checking.
I will be very honest here, and since you are not sure which stock version was on the phone before, you have a high chance of bricking the phone. If does not have the ATT logo, it does not tell us much. You could still have an HK version of the phone which is as locked down as the ATT one is, or you could have an Asian version, which would be good, since they are not as locked down...
Click to expand...
Click to collapse
What would happen if I flash the ATT firmware, assuming that it is an asian or Hongkong Version will it result in a hard brick or a soft brick?
I would tread very lightly here, and I would tell you to just flash another non-stock ROM from the dev section, on it, as that won't brick you.. But you really need to find a way to figure out which phone you have.
Click to expand...
Click to collapse
As far as I can see, there is no custom ROM which has a working webtop, I would like to use webtop. Or do you know any ROMs with webtop? I searched a lot about finding out if it is possible to figure out which hardware is in the device to check which firmware version could be right but I found nothing .
You have AT&T 125 fxz kernel... It builded in 08.31. But you also need to check your imei... And does your phone have any AT&T logo? On box or on digitizer?? It also can be AT&T phone but with Retail Atrix digitizer.... or worse Retail A2 locked down from higher cdt.bin from AT&T fw.
calualeaf said:
As far as I can see, there is no custom ROM which has a working webtop, I would like to use webtop. Or do you know any ROMs with webtop? I searched a lot about finding out if it is possible to figure out which hardware is in the device to check which firmware version could be right but I found nothing .
Click to expand...
Click to collapse
As far as I know, NUMA, ICSupercharged V7, Swifty Trix, and Stocky Ed all have working webtop.
Brought to you by time and relative dimensions in space.
turffe said:
You have AT&T 125 fxz kernel... It builded in 08.31. But you also need to check your imei... And does your phone have any AT&T logo? On box or on digitizer?? It also can be AT&T phone but with Retail Atrix digitizer.... or worse Retail A2 locked down from higher cdt.bin from AT&T fw.
Click to expand...
Click to collapse
Thanks for the telling me the Kernel Version. Could you please explain, what do you mean by "check your IMEI"? I think you don't want me to post IMEI?
The Phone does not have any ATT Logo, not on the digitizer neither on the box. I saw that the Text on the box is only written in french.
So even with knowing that it's the ATT Kernel, it's not sure if I can flash the ATT firmware:
http://forum.xda-developers.com/showthread.php?t=1961310
calualeaf said:
Thanks for the telling me the Kernel Version. Could you please explain, what do you mean by "check your IMEI"? I think you don't want me to post IMEI?
The Phone does not have any ATT Logo, not on the digitizer neither on the box. I saw that the Text on the box is only written in french.
So even with knowing that it's the ATT Kernel, it's not sure if I can flash the ATT firmware:
http://forum.xda-developers.com/showthread.php?t=1961310
Click to expand...
Click to collapse
And also is the IMEI matches with one printed on box? Is the box orange color with AT&T logo or Motorola retail red like this - http://www.use.com/media/2013/0118/3075001/p_001.jpg?1 or http://asset2.cbsistatic.com/cnwk.1d...42_620x433.jpg
---------- Post added at 10:41 PM ---------- Previous post was at 10:20 PM ----------
Enter SN from IMEI sticker to this site: http://sndeep.info/en .It's completely safe, because it also confirmed by
4pda.ru, post:
Спойлер (+/-) ( НОМЕР МОДЕЛИ с sndeep.info)
MB865
AP3025AH4H8 - Черный
AP3025AD1H8 - Белый
ME865
AP3378AE7U2
AP127203051A - (возможно для белого)
ATT
00057NAATT
00058NAATSD
And post that model showed it...
turffe said:
And also is the IMEI matches with one printed on box? Is the box orange color with AT&T logo or Motorola retail red like this - ...
Click to expand...
Click to collapse
hm I think the box was a good hint, the IMEI on the box is the same as in phone. Attached you will find photos of the box, on the back of the box is a motorola.com.tw URL, am I right if I say ist is the Hongkong/Taiwan Version?
calualeaf said:
hm I think the box was a good hint, the IMEI on the box is the same as in phone. Attached you will find photos of the box, on the back of the box is a motorola.com.tw URL, am I right if I say ist is the Hongkong/Taiwan Version?
Click to expand...
Click to collapse
And also if the box imei matches with on phone screen imei (code: *#06#)?
turffe said:
And also if the box imei matches with on phone screen imei (code: *#06#)?
Click to expand...
Click to collapse
Yes, it is still the same .
calualeaf said:
Yes, it is still the same .
Click to expand...
Click to collapse
That's bad because it's hk phone with at&t fw.... You'll be unable to downgrade to hk fw version... Is your phone under warranty??
turffe said:
[/COLOR]Enter SN from IMEI sticker to this site: http*://sndeep.info/en .It's completely safe, because it also confirmed by
4pda.ru, post:
Спойлер (+/-) ( НОМЕР МОДЕЛИ с sndeep.info)
MB865
AP3025AH4H8 - Черный
AP3025AD1H8 - Белый
ME865
AP3378AE7U2
AP127203051A - (возможно для белого)
ATT
00057NAATT
00058NAATSD
And post that model showed it...
Click to expand...
Click to collapse
Oh I didn't saw that, the result of the check is strange:
Motorola MB860 Atrix 4G
Year: 2012
Month: March
Age: 1 year and 4 months
Model Number: AP3089AW2X3
The IMEI on the Box is not the same as the result of the check and Iam very sure that this is not an MB860.
BTW on the IMEI sticker is also a Model Number maybe this helps:
AP129501187B
calualeaf said:
Oh I didn't saw that, the result of the check is strange:
Motorola MB860 Atrix 4G
Year: 2012
Month: March
Age: 1 year and 4 months
Model Number: AP3089AW2X3
The IMEI on the Box is not the same as the result of the check and Iam very sure that this is not an MB860.
BTW on the IMEI sticker is also a Model Number maybe this helps:
AP129501187B
Click to expand...
Click to collapse
Try to flash this Retail Asian fw via RSD Lite - 6.7.2_EDEM-18-SEARET_cfc.xml.zip LINK: http://sbfdownload.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Does it failing on cdt.bin?? If yes does your phone is under warranty?
turffe said:
Try to flash this Retail Asian fw via RSD Lite - 6.7.2_EDEM-18-SEARET_cfc.xml.zip LINK: http://sbfdownload.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Does it failing on cdt.bin?? If yes does your phone is under warranty?
Click to expand...
Click to collapse
hm yes it fails on cdt.bin and shows now "flash failure", is it brick? I have warranty but I think I should restore the Custom ROM.
calualeaf said:
hm yes it fails on cdt.bin and shows now "flash failure", is it brick? I have warranty but I think I should restore the Custom ROM.
Click to expand...
Click to collapse
Reflash HK (with boot failure screen) fw & bring it to warranty & fool it (that it shuted off while charging & shows fastboot err. They'll try couple times flash Retail fw, but it will fail at cdt.bin & most likely they'll replace your board).
.
turffe said:
Reflash HK (with boot failure screen) fw & bring it to warranty & fool it (that it shuted off while charging & shows fastboot err. They'll try couple times flash Retail fw, but it will fail at cdt.bin & most likely they'll replace your board).
.
Click to expand...
Click to collapse
I think I send it back to the ebay seller to get my money back I tried to reflash several ROMs with recovery, but I get always "Signature Verification failed"
calualeaf said:
I think I send it back to the ebay seller to get my money back I tried to reflash several ROMs with recovery, but I get always "Signature Verification failed"
Click to expand...
Click to collapse
You have to disable signature verification in CWM.
Hello!
I am have some strange problem.
Have Atrix 2 MB865 and it is UAE, that i think. May be it mistake, but this photo of phone back.
Via RSD can successfuly flash only InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip (is off for ATT). Any other images not flash without errors including official for UAE. The are errors with cdt.bin and recovery.bin.
The phone not have any ATT logotypes and initially was have some 2.3.x firmware (I do not have more information about what was in store phone firmware)
I can flash JB leak 3 without cdt.bin and recovery.bin, and it work, but camera not.
I can flash MIUI v4 ,it work, but battery so short lifetime.
I can't flash Unofficial MIUI v5 , have boot loop.
WTF?
simplemad said:
Hello!
I am have some strange problem.
Have Atrix 2 MB865 and it is UAE, that i think. May be it mistake, but this photo of phone back.
Via RSD can successfuly flash only InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip (is off for ATT). Any other images not flash without errors including official for UAE. The are errors with cdt.bin and recovery.bin.
The phone not have any ATT logotypes and initially was have some 2.3.x firmware (I do not have more information about what was in store phone firmware)
I can flash JB leak 3 without cdt.bin and recovery.bin, and it work, but camera not.
I can flash MIUI v4 ,it work, but battery so short lifetime.
I can't flash Unofficial MIUI v5 , have boot loop.
WTF?
Click to expand...
Click to collapse
MB865 can only flash att firmware...Miui v5 is not for att.
atrix2man said:
MB865 can only flash att firmware...Miui v5 is not for att.
Click to expand...
Click to collapse
MB865 does not necessarily mean it's an AT&T phone. If it is an AT&T model it will be quite obvious since it clearly says AT&T on the front of the phone.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
1BadWolf said:
MB865 does not necessarily mean it's an AT&T phone. If it is an AT&T model it will be quite obvious since it clearly says AT&T on the front of the phone.
Click to expand...
Click to collapse
So...
EMEI say - is UAE, but RSD can't flash any other image include off UAE, but only ATT. Why. May be some modules or identificators was rewrote with ATT image. I have no idea, and already use forum search and google (
You wont be able to flash any firmware except at&t. Because you flashed at&t 125. cdt.bin number increased & you can't downgrade, but if it works good (no battery drain & etc) leave it. Still you will not be able to downgrade to UAE fw... RSD will keep throwing cdt.bin err...
turffe said:
You wont be able to flash any firmware except at&t. Because you flashed at&t 125. cdt.bin number increased & you can't downgrade, but if it works good (no battery drain & etc) leave it. Still you will not be able to downgrade to UAE fw... RSD will keep throwing cdt.bin err...
Click to expand...
Click to collapse
Thank you for answer.
What about ability to flash leak 3 or miui v5 or other Asian based firmwares?
That I wrote in first post I have some troubles (((
Not a good idea to post your IMEI number on a public forum... I've edited your post.
Hi all,
I am generally not a XDA active reply user. I worked on a lot of Android fixing project. And here is one of mine result.
Please read the whole thread before working on it.
I know everyone is frustrating in upgrading to 4.4.2 but brick during odin process (ext4 fail) and stuck in 4.4.2 bootloader.
PS: This method is currently work on HK note3, but i think this method would work on all note3, Please try this will your own risk, I would not be responsible to all trouble according to this method. Varied N9005 would require different N9005 4.3 Firmware, I personally use HK Firmware because Mine is 16gb Note 3.
Here is the method to solve this problem:
Before working on it, we have to prepare the following things:
1. Odin 3.07 (Yes, 3.09 does not work)
2. HK firmware odin pack (Pit, BL (DO NOT WORK WITH IT, AP, CP, CSC) (Sorry for it is a Chinese link)
OR Workable N9005 4.3 firmware
3. 4.4.2 leaked firmware
4. 4.4.2 rom (I used sweet rom v.7 to fix it)
5. 4.4.2 recovery cwm @Chenglu
5. Samsung driver (bullshxt)
Now lets get started:
1. Flash the 4.4.2 firmware BL by odin.
2. Flash the HK Firmware AP, CP &CSC (Do not use the HK firmware BL)
3. once it done, turn to Download mode again and flash 4.4.2 recovery cwm by odin
4. Run Recovery
5. Wipe everything
6. Flash 4.4.2 rom ( I flashed sweet rom v7 currently)
7. Boot to system and do all the setting ( The sound and the signal are not working)
8. Boot back to download mode
9. Boot the 4.4.2 leaked firmware's CP ( DO NOT WIPE AFTERWARD)
10. Prepare coffee and cookies
11. Enjoy your device!
karnavont said:
Hi all,
...
Click to expand...
Click to collapse
Please edit your title to reflect that (at least at this point) your fix should be considered primarily for the Hong Kong Note 3 bricked by writing XEO 4.4.2.
xclub_101 said:
Please edit your title to reflect that (at least at this point) your fix should be considered primarily for the Hong Kong Note 3 bricked by writing XEO 4.4.2.
Click to expand...
Click to collapse
Actually not, its to all varied Note3 but I do not have all sources given to it, it is generally working on all Note3 who fail in flashing to 4.4.2(to any error in progress during Odin upgrading)
And I did a lot of researches, This problem is not only reflect to HK Note 3 only, there are a lot of people would upgrading to 4.4.2 and stuck in Download mode with UDC start (Not able to downgrade).
karnavont said:
Actually not, its to all varied Note3 but I do not have all sources given to it, it is generally working on all Note3 who fail in flashing to 4.4.2(to any error in progress during Odin upgrading)
And I did a lot of researches, This problem is not only reflect to HK Note 3 only, there are a lot of people would upgrading to 4.4.2 and stuck in Download mode with UDC start (Not able to downgrade).
Click to expand...
Click to collapse
Well, if/when people will post in this thread reporting that the method (which is highly similar to methods that were already posted by other users, most notably Volrath and rinuvimal - which you have not credited anywhere) - then we will know that the method is applicable, and to which specific models!
In other words people using the method on untested models should be warned that they are just doing something that might have never been tested on their model.
xclub_101 said:
Well, if/when people will post in this thread reporting that the method (which is highly similar to methods that were already posted by other users, most notably Volrath and rinuvimal - which you have not credited anywhere) - then we will know that the method is applicable, and to which specific models!
In other words people using the method on untested models should be warned that they are just doing something that might have never been tested on their model.
Click to expand...
Click to collapse
Okay, i changed it, in term of a reference instead
Hi guys, I had the same issue with the 16GB Honk Kong version, and this is how I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flash bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flash bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flash AP from N9005ZHUBMI7 (Honk Kong version)
4.- Enter recovery mode and wiped system, cache and dalvik (just in case)
4.- Flash autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flash CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/show....php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
My friend wants to ask this question because he is unable to post a reply with a photos attached.
Is my N9005 32gb Baseband/Bootloader from Hong Kong also?
Kindly see my ScreenShots beloe please. I just don't know where my Note 3 came from.
Thanks in Advance & God Bless
AldrichDSaints said:
My friend wants to ask this question because he is unable to post a reply with a photos attached.
Is my N9005 32gb Baseband/Bootloader from Hong Kong also?
Kindly see my ScreenShots beloe please. I just don't know where my Note 3 came from.
Thanks in Advance & God Bless
Click to expand...
Click to collapse
I think you are using a Custom Rom so there is a posibility it won't be accurate kabayan. But according to your bootloader and baseband its the same as my Hongkong version. And my advice hide your IMEI nexttime.
maumarti2k said:
Hi guys, I had the same issue with the 16GB Honk Kong version, and this is how I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flash bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flash bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flash AP from N9005ZHUBMI7 (Honk Kong version)
4.- Enter recovery mode and wiped system, cache and dalvik (just in case)
4.- Flash autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flash CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/show....php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
Click to expand...
Click to collapse
What version of Odin did you used? For the past 24 hours is it stable and any FC's? Are all apps working? I wanna try your guide. Having problem on the O.P. guides.
I am in the exact same situation, all over methods have failed, im going to try this!
3. 4.4.2 leaked firmware is a dead link!
AldrichDSaints said:
My friend wants to ask this question because he is unable to post a reply with a photos attached.
Is my N9005 32gb Baseband/Bootloader from Hong Kong also?
Kindly see my ScreenShots beloe please. I just don't know where my Note 3 came from.
Thanks in Advance & God Bless
Click to expand...
Click to collapse
Fist dude you should never post your IEM EVERRRR
Second you can always hook the phone to Kies and it will tell you what you have
jetbruceli said:
Fist dude you should never post your IEM EVERRRR
Second you can always hook the phone to Kies and it will tell you what you have
Click to expand...
Click to collapse
Seems I have had some success. Although, I found a couple of the instructions difficult to understand. Thanks for posting this, as I no longer have a brick.
Cheers.
filchi756 said:
I think you are using a Custom Rom so there is a posibility it won't be accurate kabayan. But according to your bootloader and baseband its the same as my Hongkong version. And my advice hide your IMEI nexttime.
Click to expand...
Click to collapse
My friend didn't continue to flash the Poland's leak. He will just wait for the OTA on his phone because he is afraid to have a softbrick and I told him also that if he had softbrick his phone the only thing that he can use now is by flashing custom ROM
Samsung Note 3 Region Taiwan Softbrick UDC START
AldrichDSaints said:
My friend didn't continue to flash the Poland's leak. He will just wait for the OTA on his phone because he is afraid to have a softbrick and I told him also that if he had softbrick his phone the only thing that he can use now is by flashing custom ROM
Click to expand...
Click to collapse
does anyone with Samsung Note 3 Taiwan Region?
i got this "UDC START" thing while upgrade to 4.4.2 Region Poland Official ROM
but i dont want to trip knox, better i got back to shop and claim for warranty..
or should i just wait for Official Kit Kat Region Taiwan?
i am still waiting..
if anyone can help, thank you very much.
Samsung Note 3 Region Taiwan Softbrick UDC START
karnavont said:
Actually not, its to all varied Note3 but I do not have all sources given to it, it is generally working on all Note3 who fail in flashing to 4.4.2(to any error in progress during Odin upgrading)
And I did a lot of researches, This problem is not only reflect to HK Note 3 only, there are a lot of people would upgrading to 4.4.2 and stuck in Download mode with UDC start (Not able to downgrade).
Click to expand...
Click to collapse
does anyone with Samsung Note 3 Taiwan Region?
i got this "UDC START" thing while upgrade to 4.4.2 Region Poland Official ROM
but i dont want to trip knox, better i got back to shop and claim for warranty..
or should i just wait for Official Kit Kat Region Taiwan?
i am still waiting..
if anyone can help, thank you very much.
budi_west said:
does anyone with Samsung Note 3 Taiwan Region?
i got this "UDC START" thing while upgrade to 4.4.2 Region Poland Official ROM
but i dont want to trip knox, better i got back to shop and claim for warranty..
or should i just wait for Official Kit Kat Region Taiwan?
i am still waiting..
if anyone can help, thank you very much.
Click to expand...
Click to collapse
i also have the same problem. what should i do
Samsung note 3 Region Taiwan UDC START
sagsans said:
i also have the same problem. what should i do
Click to expand...
Click to collapse
Where do you come from?
i will try the solution given by members from Hongkong Region with flashing CWM recovery and SweetROM, but i just do not know will it work for Taiwan Region, cause Hongkong Firmware is ZHU and Taiwan is ZTU something unique there..
budi_west said:
Where do you come from?
i will try the solution given by members from Hongkong Region with flashing CWM recovery and SweetROM, but i just do not know will it work for Taiwan Region, cause Hongkong Firmware is ZHU and Taiwan is ZTU something unique there..
Click to expand...
Click to collapse
i have try sweetrom, it's not working on my note3 taiwan version. anything for me to try?
Samsung Note 3 Taiwan UDC START
sagsans said:
i have try sweetrom, it's not working on my note3 taiwan version. anything for me to try?
Click to expand...
Click to collapse
How do you flash the SweetROM what version? have you try locky guide?
Technology: The Ultimate Guide To Unbrick 16 Gb International Samsung Galaxy Note 3
http://forum.xda-developers.com/showthread.php?t=2627291
by: Locky Loki
Try this something else out
[ROM]N9005ZHUENB1 Android 4.4.2 Kitkat
http://forum.xda-developers.com/showthread.php?t=2636699
Or
[SOLUTION] Successful flash of leaked NA6 ROM on Hong Kong 32g N9005
http://forum.xda-developers.com/showthread.php?t=2613374
Actually i have started a question [Q] about Note 3 Taiwan UDC START at this forum but with no reply
[Q] Samsung Galaxy Note 3 SM-N9005 Region Taiwan Softbrick UDC START
http://forum.xda-developers.com/showthread.php?p=50061661
Lately i found out somebody posting That he is from Region taiwan anda he is able to flash firmware from region Hongkong and Taiwan Only..
So, i suppose Taiwan Region can seek help from Hongkong Region