So after getting the Nubia Red Magic 3, I was wanting to root it. But my first attempt was a failure and will have to flash my ROM again in recovery. Okay, whatever, no big deal. But here is something weird.
So I found out that there is a global ROM, a Chinese ROM, and an EU ROM for this phone. Apparently, I have the the EU ROM. When flashing the boot.IMG and the recovery.IMG from a global ROM I downloaded, the device would go into a bootloop (or sometimes go straight into fastboot). I figured I download the right ROM from Nubia's website. I clicked on the USA version.
Well then I have my suspicion that I was using the European ROM because I looked at the manual and it was referencing all this "compliance with the EU" regulations and stuff like that inside the manual.
So then I downloaded the EU version of the ROM and sure enough, I'm able to get into recovery again. So that means I download the right ROM. I can unbrick it now. Woop-dee-woop. But I'm still puzzled. Why did they give me a Nubia Red Magic 3 with the European stock firmware if I live in the US? Was the global ROM a separate ROM that didn't come from Nubia? Correct me if I'm wrong but, I'm assuming U.S. users get the EU version of the Nubia red magic 3??
I got a NA version of the phone. I'm not sure if you got the EU version or if through flashing yours ended up with the EU version.
It's always best to check before you start flashing your phone.
Realistically, all versions are the same, but for the roms that are installed on them. So, if you change it before checking, there's no way to tell what was originally on there.
Psyrecx said:
I got a NA version of the phone. I'm not sure if you got the EU version or if through flashing yours ended up with the EU version.
It's always best to check before you start flashing your phone.
Realistically, all versions are the same, but for the roms that are installed on them. So, if you change it before checking, there's no way to tell what was originally on there.
Click to expand...
Click to collapse
Actually I may be wrong. I might have had the NA because the recovery is not the same than the original. I'm going to try that version.
EDIT: I'm pretty much trying to get the NA version but the STOCK version. Aren't the global versions different? What does your recovery look like? Does it have the "update from local storage option" because that's what mine had.
EDIT 2: After looking at the manual, my certified version is NX629J_ENCommon_V2.04 and on another page, it says NX629J_ENCommon_V1.06. I searched for these versions on XDA but got nothing.
chocolote4444 said:
Actually I may be wrong. I might have had the NA because the recovery is not the same than the original. I'm going to try that version.
EDIT: I'm pretty much trying to get the NA version but the STOCK version. Aren't the global versions different? What does your recovery look like? Does it have the "update from local storage option" because that's what mine had.
EDIT 2: After looking at the manual, my certified version is NX629J_ENCommon_V2.04 and on another page, it says NX629J_ENCommon_V1.06. I searched for these versions on XDA but got nothing.
Click to expand...
Click to collapse
See your build number in About Phone.
alanzaki073 said:
See your build number in About Phone.
Click to expand...
Click to collapse
Can't. It won't boot at the moment.
EDIT: So it appears that my phone was using the NA version (not the global). I just need the stock version. I remember that I was on version 1.11 and updated to 1.15 (NOT THE EU VERSION AND NOT GLOBAL VERSION). But after searching everywhere on the Internet, the stock NA ROM hasn't been uploaded yet (or at least I couldn't find it). I searched everywhere. So I'll just have to wait for the NA stock ROM gets uploaded. Before I tried to root it, I remember using the recovery with the "apply update from local storage" option. I'm using the recovery where you have an option to pick two languages, and apply update from OTG.
From what I read here on XDA, you need a flash drive that is FAT32 with update.zip. But when I try to do that, it says something like "can't find OTG". So either it's not recognizing the phone in recovery or it's my flash drive. I'll try again tomorrow, but my best bet is to wait for my version stock ROM to be released. It stopped booting once I patched a different ROMs boot.IMG with Magisk. And yes, according to what some people said on XDA, you need to have the correct drivers for the Red Magic 3 and when I searched for the drivers, one website said to install the " Qualcomm Drivers" but I did that and the OTG still fails to read the USB.
I'll keep trying though. I never give up. I'll keep digging around on XDA for a possible solution.
Hopefully I am correct on all this. I could be wrong though..
chocolote4444 said:
Can't. It won't boot at the moment.
EDIT: So it appears that my phone was using the NA version (not the global). I just need the stock version. I remember that I was on version 1.11 and updated to 1.15 (NOT THE EU VERSION AND NOT GLOBAL VERSION). But after searching everywhere on the Internet, the stock NA ROM hasn't been uploaded yet (or at least I couldn't find it). I searched everywhere. So I'll just have to wait for the NA stock ROM gets uploaded. Before I tried to root it, I remember using the recovery with the "apply update from local storage" option. I'm using the recovery where you have an option to pick two languages, and apply update from OTG.
From what I read here on XDA, you need a flash drive that is FAT32 with update.zip. But when I try to do that, it says something like "can't find OTG". So either it's not recognizing the phone in recovery or it's my flash drive. I'll try again tomorrow, but my best bet is to wait for my version stock ROM to be released. It stopped booting once I patched a different ROMs boot.IMG with Magisk. And yes, according to what some people said on XDA, you need to have the correct drivers for the Red Magic 3 and when I searched for the drivers, one website said to install the " Qualcomm Drivers" but I did that and the OTG still fails to read the USB.
I'll keep trying though. I never give up. I'll keep digging around on XDA for a possible solution.
Hopefully I am correct on all this. I could be wrong though..
Click to expand...
Click to collapse
http://rom.download.nubia.com/Europe&Asia/NX629/NX629J_Z69_EN_WPJ0O_V115.zip
This is v1.15 NA. It's easily available on red magic's website
chocolote4444 said:
From what I read here on XDA, you need a flash drive that is FAT32 with update.zip. But when I try to do that, it says something like "can't find OTG". So either it's not recognizing the phone in recovery or it's my flash drive. I'll try again tomorrow, but my best bet is to wait for my version stock ROM to be released. It stopped booting once I patched a different ROMs boot.IMG with Magisk. And yes, according to what some people said on XDA, you need to have the correct drivers for the Red Magic 3 and when I searched for the drivers, one website said to install the " Qualcomm Drivers" but I did that and the OTG still fails to read the USB.
Click to expand...
Click to collapse
I had tried flashing to global 2.10 and got the same issue. I also had the 'can't find OTG' issue a few times, but eventually it found it.
Related
My phone is running build FRF33B (googling this build number returned no results at all). It was a non public build. I got the phone from Adobe as part of a (kongregate) promotion to get flash developers to edit some games so they could run on froyo, and hence I really don't know what was done to the phone before I got it (there's an unlocked symbol when it boots, and even though it's a t-mobile nexus I'm using it on AT&T's network).
FRF33B is nice and usable (but full of minor bugs which get irritating after a while), and I'd really like to update to the latest stable build, but it's not receiving any of the OTA updates, and trying to install any manually gives me a package signing verification failure.
Does anyone here know how I can update the phone? Do I need to downgrade it somehow? Do I need to root it? Any help would be appreciated.
Downgrade to erd79 would be my best suggestion and it will update to frf91 I hope that helps and if u need a update zip let me know and I can email it to u
Sent from my Nexus One using XDA App
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Option 3: Search around for the FRF91 Universal update.zip, copy it to your SD card, and flash it via stock recovery.
rohandhruva said:
Or just unlock your phone, put a custom recovery, and install whatever ROM you want. Look at the sticky in the development section for details.
Click to expand...
Click to collapse
ok I've done this, and flashed the universal FRF91, now the phone is stuck on the animated X, is this normal? Do I just have to wait or did I do something wrong?
edit: it looks like it just rebooted itself.... still not getting past the animated x part though
edit: wiped the phone and tried again, now it works... got to set up everything on the phone again though and download my apps again... oh well. thanks for the help
Fellow androiders,
I believe I am in a really rare brick situation that no matter how I try, it still does not show any turn around.
[Introduction]
I bought a Korean version Milestone(Moto Qrty, as they put], and I took it to China. Because the original phone did not support sending Chinese text message, plus, too much telco provided apps are making the phone sluggish, I decided to follow my friend advice, to switch to widely available open-sourced Froyo (I wanted the CM).
[Problem]
I thought that the flashing process would not be too difficult and I could handle it by myself. But, it turns out that I have become a victim of an overly simplified version of flashing guide. I don't know what exactly have done wrong, after successfully rooted the phone, I vaguely remember that I have used CM ROM for Droid, instead of CM ROM for Milestone.
And that made my phone a brick. My phone will turn on, but will restart again and again after M logo(So-called M boot loop).
[Background information of the Phone and my PC environment]
Phone Model: A853
Original Bootloader version: A0.20
Original Android System: Froyo
RSD lite version: 5.3.1. (later switched to 4.6 due to the suspicion of RSD bug)
Operating System: Windows 7 64 bit, English
[What I have tried so far]
I have tried to follow many tips on the internet. Tips from Korean websites, from Chinese websites, and from English websites. Basically, these tips will let you flash back to the original ROM by using RSD lite.
But, no matter what I try, it will not fix the boot loop problem.
I've tried to
1) Bring the phone to the original status [did not work.]
- flash the bootloader into A0.20 (the original bootloader) with RSD lite;
(bl_a020_umts_sholesumts_skt_consumer_replacer.sbf)
- flash with original Froyo sbf (following the advice from Korean websites, flashed Clair first, and then flashed Froyo) with RSD lite.
(A853_2.1(Eclair).SBF / A853_2.2.1(Proyo).SBF)
* According to what Koreans say, it would make your phone into the original status, will even remove signs of root.
2) Used many combination of following bootloader and ROMs
- flash the bootloader into 90.78ch
(BL_9078_umts_sholes_GC_HS_Consumer_replacer.sbf)
- flash the bootloader into 90.78
(BL_9078_umts_sholes_HS_Consumer_replacer.sbf)
- GOT221 ROM
(GOT_RTEU_2_2_1FULL.sbf)
- And some other un-name-able ROMs
SGC_U2_03.04.0_USASHLSGCB1B2B5008.0R_PDS06A_HWp2a_1FF.sbf
3) Used many different OpenRecovery Variations
OpenRecovery v1.46
OpenRecovery 3.3
OpenRecovery GOT mod v2.1
4) Restore Nandroid backup which I made right before I made my phone brick.
5) Cleaned data/cache/dalvic as I do every flash, and tried boot without SIM card and SDCard.
[Some discoveries and successes]
- With 90.78ch + GOT2.2.1, it will show "Android" screen, but it will reboot as soon as the phone OS interface show up.
- According to my friend, when he flashed back to the original bootloader A0.20 + original froyo Rom, it showed TelCo Symbol "T" once (which is the booting screen right after M).
[Final Comment]
What I really want to know is that is it the time I give up on it? or is there any value of pursuing other knowledge on bring this phone back?
I really need this phone, and it will take some times to save money to buy another smartphone, I would really really appreciate if you can help me bring this phone back to normal.
Thank you.
some users reported problems with sdcard. try to boot without sdcard, and wipe everything after or before the flash process.
and i don think it's hard bricked...
Sir, I have tried so, somehow, I did not have lucks other had.
roofghost said:
Sir, I have tried so, somehow, I did not have lucks other had.
Click to expand...
Click to collapse
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: http://android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
..... my bad
I have the same issue,
in recovery there is message when wiping data/factory reset:
E:Error in CACHE:fota/log
(no space left on device)
I am wondering, if I move CACHE to SD would it help??
Yesterday I have installed original Rom (shols~) and phone booted once to android and when I have rebooted it, there is M bootloop again.
Please help me
skadude66 said:
So you've tried flashing different bootloaders, with no success? I always thought flashing another bootloader version different from your own was risky.
If not, you can just try flashing the SBF from here: android.doshaska.net/rootable , then installing OpenRecovery, rooting the phone, flashing a custom ROM, etc.
Click to expand...
Click to collapse
Thanks, did not work.
I have a feeling that the "doshaska" will know how to solve this. Anyone know how to contact or PM him?
Thanks.
By the way,
in this case, is there anyway can fix the brick via "console" in the OpenRecovery?
Thanks.
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
zeppelinrox said:
So... you have open recovery and can get to the console...
What happens if you copy CM to the updates folder and flash CM?
Click to expand...
Click to collapse
Yes, I can enter OpenRecovery and can get to the console.
And,
sorry about the CM, I think I will have to try that again and let you know then.
Is there any CM ROM you want me to try? (Hopefully with a reliable instruction. If you are busy, you can just leave this part, I will look for myself about the instruction.)
Truly thank you and glad to see new reply under this topic.
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
zeppelinrox said:
Well, use OR's mount as usb function and plug into your computer.
Copy the latest CM7 (I think that's what you want - or any ROM really) to the updates folder.
Wipe all caches
Then apply the update
It should "just work"
I mean, the hardest part is getting into OR lol
I'm surprised that your battery hasn't died yet
Click to expand...
Click to collapse
Can I install CM7 on Froyo? I thought that was for the Android 2.3.
I have just flashed back to the original bootloader of A0.20 (it was 90.78 as I play around with it.), and flashed the original korean .sbf froyo. Just to follow your suggestion.
I will try to install vulnerable recovery. I think in this way, I can use OpenRecovery again.
About my batter, I purchased a separate battery charger.
I will keep my status updated as soon as I try this out.
Thanks.
same problem and flash so many rom My milestone can't acess sdcard on recovery mode and android os.
Sent from my Milestone using XDA App
guys same problem here, help us
I was working on getting 4.4 AOSP kitkat on my Atrix HD, and it was going great. While backing up with CWM, it failed on the data, but I figured I could just restore my files from a back up. When I went to put the rom on it, I got some no_contexts error and it said somethign about metadata. I tried to restore the backup and got a md5 fail. I used the advanced restore to let it skip the data part, but all parts gave a md5 fail. Now for somereason, I'm unable to connect through ADB, though fastboot still works, so I can't try pushing a stock rom. I tried adb sideload, but that didn't even remotely work. I also can't charge my phone, and it has a low battery. Does it charge in fastboot or recovery mode? Please help.
Phew
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
ace_case said:
Ok, so I was looking around for a way to get back to stock without adb, which, as I said earlier, I couldn't get working halfway through. I was looking around for a way to do it with fastboot, and found rsd lite. I downloaded the files I needed, but it always failed 1/23. I then thought to just do it manually, and it worked perfectly
On a side note though, is there a way to use fastboot to flash nonstock roms? Would I just follow the same commands I did for the stock version? Is there any specific version I should download to use fastboot with it? I am still wanting an as-close-as-possible stock version of 4.4 for atrix hd. Also, did I do anything wrong the first time, or was the download corrupt?
Click to expand...
Click to collapse
I'm glad to hear you got things back into working order! With regards to flashing any custom ROM, the safest way is to use a custom recovery. Currently, as far as I can tell, the only official recovery for the Atrix HD is CWM but that's fine. You do want to be sure that you have the latest, most up to date version of CWM installed. As of right now, I believe that is 6.0.4.4 (http://clockworkmod.com/rommanager, mine already might be out of date again) and that may be where your problems came from when you were wiping and getting errors.
With regards to a close to stock 4.4 for the Atrix HD, there is an official build of CM available here: http://download.cyanogenmod.org/?device=mb886 although the latest build is from February, I can assure you that from running it on my Atrix HD it is definitely much smoother than what Motorola has offered (to date) for this device. There have been promises of official 4.4 support but I haven't seen anything come from that as of today (see here for more info: http://goo.gl/oK34W0)
CORRECTION: The official support for Atrix HD is here: http://download.cyanogenmod.org/?device=moto_msm8960
It is a merged thread for all of the devices mentioned here: http://wiki.cyanogenmod.org/w/Moto_msm8960_Info
I can't vouch for it personally but others have said that it has fixed a lot of bugs since the single device support that ended in February...
I recently got my TF701T back from repairs and they of course factory reset it (they put a new battery in). We all know it needs factory reset for that right? Anyways. I do a check for updates and nothing. I know I was running 4.4 previously but updater says no updates and stuck on original. So I start reading and download the latest US 4.4 firmware directly from ASUS, unzip it and put in main directory (verified mine was US) and reboot. Says all is fine, would I like to update, yes, reboot and I get the Android gear guy for about 10 minutes then it reboots. He shows up again and dead android shows up.
Now it just loops forever to this. I spent about 5 hours reading forums here, attempted a restore, but 1. the recovery.img link is bad and 2. my tablet isn't rooted.
Any suggestions? I can access the fastboot screen that gives me "RCK, Android and "Wipe Data". I tried Wipe data 3 times, no good still getting dead guy. I tried copying the latestest zip file to an sd card with boot.img and blob and file and ran RCK and it says match then reboots then dead guy again...
the fastboot screen says "released by: "US_epad-10.14.1.45-20131014" which I believe is the original.
You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!
So, I had downloaded 3 different versions multiple times before with zero success. But, once I took one and renamed it to T4_SDUPDATE.zip bam!
You just so made my day!
Thank you! Thank you! Thank you!
Devan
I have a question along these lines. What is the difference between the software update and firmware update and when do you do each? I understand the difference between what they are I suppose just not sure if updating is the same. Should I update kernel too or is that updated in an SW or FW update?
Thanks
Anyone?
I have seen these terms used very differently on different device forums.
Here on the Asus tablet forums people mostly talk about firmware when they mean the whole stock package. The stock firmware always comes with everything: Bootloader, recovery, rom and kernel
On the HTC M8 forum for example, they make a clear distinction: Software is rom and kernel, firmware is bootloader, radios, baseband etc.
The recovery seems to fall somewhere in between
Your bootloader version determines everything else. You should only flash a recovery, kernel or rom compatible with that particular bootloader.
You can, or have to, update it if you want to run a rom that requires a later or newer bootloader. Asus encrypts their BLs, so bootloader updates can only come from them - so far only with the release of a new version of the OEM "firmware".
If you as an unlocked, custom rom'd user then want to install a rom based on that new firmware, you have to update the bootloader and possibly but not necessarily your recovery before flashing the new custom rom.
Custom recoveries get more frequent updates. CWM, TWRP or some enterprising dev release new versions every few months. Always make sure it is compatible with your bootloader and rom. In most cases you can easily skip a few versions. But if you update your rom, let's say, from JB to Lollipop you should also update your recovery.
The kernel is considered to be part of the rom. At least every rom I know of comes with a kernel, some even with several to choose from. And it is a popular sport to try the same rom with different kernels.
You update the rom whenever the developer releases a new, updated version - or not if you're happy with what you got.
The safest place to be is always up-to-date: The latest roms usually require the latest bootloader and it's best to run both with the latest recovery.
If you have a working combo you can stick with it for years if you like.
But if you've been away for a while, did not follow the latest development, and want to update, you always have to:
Check if your bootloader is still current. If not, update it
Update your recovery
Wipe data, cache and Dalvik
Flash the new rom.
Nice explanation, I knew all of this but there is no way I could have explained it.
berndblb said:
You did a good job on your research. What might have tripped you up could be just a bad download. Files do get corrupted during download once in a while.
The recovery seems to have initially recognized the digital signature of the update file and started to flash it. And then something went wrong....
Download the firmware again. Unzip it once (the result should be a ....user.zip) and place that file onto a microSD formatted fat32 and not into any folder on the card. Boot to recovery (RCK).
If that does not work, try to rename the ...user.zip on the microSD to T4_SDUPDATE.zip and boot to recovery and report back.
Good luck!
Click to expand...
Click to collapse
THANK YOU!!!! IT worked like a miracle... Thank you !!!! :good::good::good:
I have been searching for custom ROMs for a couple days, yet haven't come across any that are compatible with the G973W. I have noticed a few that don't specify, and just say "S10", but I would like confirmation.
I would also like to know if it is possible to create an image/ROM of my devices current state as a sort of restore point. I know it's kind of a nooby question, but I am having a hard time finding that information. Thanks!
Your phone has the same snapdragon processor as the G973U. I can't give a direct yes or no answer, but I have seen root options for that phone.
Now your task is to see if what works for G973U will work for G973W (I bet it would since it's basically the same phone).
If you can't find a definite answer, make backups and download Odin and copy of your firmware just in case you brick the phone and give it a try.
malcolmy said:
Your phone has the same snapdragon processor as the G973U. I can't give a direct yes or no answer, but I have seen root options for that phone.
Now your task is to see if what works for G973U will work for G973W (I bet it would since it's basically the same phone).
If you can't find a definite answer, make backups and download Odin and copy of your firmware just in case you brick the phone and give it a try.
Click to expand...
Click to collapse
Thanks for the reply! I was thinking the same thing. Perhaps only carrier specific software might break. I would just go ahead and try it, but I'm having a really tough time finding how to make a copy of my phone the way it currently is. It is currently rooted, with TWRP and Magisk. I also have Odin, and Android Studio with ADB. Just not sure how to pull the current firmware.
TacoDeMuerte said:
Thanks for the reply! I was thinking the same thing. Perhaps only carrier specific software might break. I would just go ahead and try it, but I'm having a really tough time finding how to make a copy of my phone the way it currently is. It is currently rooted, with TWRP and Magisk. I also have Odin, and Android Studio with ADB. Just not sure how to pull the current firmware.
Click to expand...
Click to collapse
Good you're rooted, when I wrote my reply all I had in mind was root.
However, backup is easier with TWRP. Just go into recovery and then to backup. Backup everything.
There's a bug I have read about with one version of TWRP that wouldn't backup to SD card. So if you face any issues there just backup to phone storage.
Since you're rooted, and can make a nand backup with TWRP, try the available ROMS for G973U. If anything goes south, restore in TWRP. Just make sure of the compatible versions of Android/BL/modem/TWRP between your current phone as it is, and the ROM you'll be using. Because your purpose now should be (I believe) is to test compatibility between S10 U and W versions. If all goes well, go nutz.
So I made a back-up and flashed a ROM for the U variant, but ended up in a boot loop. Wiping and restoring via TWRP also resulted in a boot loop. The only way out was to download stock firmware and flash via Odin. I had followed all of the relevant instructions to the letter, so if any one else wants to try a ROM made for U devices on a W variant, do so at your own risk and make sure you have the correct stock firmware and Odin ready. I might try again down the road just in case something went wrong on my part.