Related
Hi Folks
I bought a Motorloa Defy XT535 over the internet from a company in Sydney, who imported the phone from China (I live in Australia). When I received the phone, everything was in Chinese and changing the language to English, made little difference. Google Apps was not installed on the phone, and the only App Store software, had only Chinese applications. In this state, the phone was pretty useless to me. I attempted downloading the gapps APK, and installed it succesfully, however, I was still unable to connect to the Google Play store, since the phone did not allow me to create a Google account. The only account that I was able to create, was for and Exchange Server, no other options were available.
I came here and after much searching, found a few links that described how to root the phone, I found an Australian Telstra Firmware update for Gingerbread 2.3.7 one this site, http://www.droidevelopers.com/f437/...-xt535-gingerbread-2-3-7-firmware-update.html. I was able to root the phone successfully using the instructions in the All-in-one-guide on the forum - http://forum.xda-developers.com/showthread.php?t=1216982.
I then needed to install a Custom Recovery and found this link to install ClockworkMod - http://forum.xda-developers.com/showthread.php?t=1827338. This is where things went wrong. After I followed the steps and successfully installed CWM (or so it seemed), the phone now does not boot up at all. When I switch it on, the Motorola Logo appears and then nothing further. By holding down both volume keys and switching on the phone, I can get into the stock recovery, but resetting the phone to factory default does not resolve the issue. I can also boot up into the bootloader by holding down the Up Volume key before I switch it on, but the White screen appears and four lines of text, then nothing. There are no options and the only action that does anything, is pressing the power button which then resets the phone.
The original firmware version was 2.3.6. and since I was unable to get past the custom recovery installation, I have not attempted flashing the rom with newly downloaded Telstra Ginderbread 2.3.7 firmware.
Please help if anyone has any ideas?
Thanks
JWinAus
XT535 rooting, and firmware replacement
JWinAus1969 said:
Hi Folks
I bought a Motorloa Defy XT535 over the internet from a company in Sydney, who imported the phone from China (I live in Australia). When I received the phone, everything was in Chinese and changing the language to English, made little difference. Google Apps was not installed on the phone, and the only App Store software, had only Chinese applications. In this state, the phone was pretty useless to me. I attempted downloading the gapps APK, and installed it succesfully, however, I was still unable to connect to the Google Play store, since the phone did not allow me to create a Google account. The only account that I was able to create, was for and Exchange Server, no other options were available.
I came here and after much searching, found a few links that described how to root the phone, I found an Australian Telstra Firmware update for Gingerbread 2.3.7 one this site, http://www.droidevelopers.com/f437/...-xt535-gingerbread-2-3-7-firmware-update.html. I was able to root the phone successfully using the instructions in the All-in-one-guide on the forum - http://forum.xda-developers.com/showthread.php?t=1216982.
I then needed to install a Custom Recovery and found this link to install ClockworkMod - http://forum.xda-developers.com/showthread.php?t=1827338. This is where things went wrong. After I followed the steps and successfully installed CWM (or so it seemed), the phone now does not boot up at all. When I switch it on, the Motorola Logo appears and then nothing further. By holding down both volume keys and switching on the phone, I can get into the stock recovery, but resetting the phone to factory default does not resolve the issue. I can also boot up into the bootloader by holding down the Up Volume key before I switch it on, but the White screen appears and four lines of text, then nothing. There are no options and the only action that does anything, is pressing the power button which then resets the phone.
The original firmware version was 2.3.6. and since I was unable to get past the custom recovery installation, I have not attempted flashing the rom with newly downloaded Telstra Ginderbread 2.3.7 firmware.
Please help if anyone has any ideas?
Thanks
JWinAus
Click to expand...
Click to collapse
Hi Folks
I just resolved this issue on my phone. Have a look at this post in another forum - http://simply-android.com/discussion/593/how-to-unbrick-or-flash-a-defy-firmware.sbf/p1. It worked, I used this version of RSD Lite http://forum.xda-developers.com/showthread.php?t=1348587. My phone is now up and running and all seems well.
I hope this helps someone ...
Cheers
JW
The device: Nook simple touch glowlight
This error happen when I return original state after rooting.
I know there are some stories about blacklisting, but let me finish.
The first time that happen, I contact nook support, they tell me that the device is not blacklisted, and probably i have wifi issues. But my nook perfectly connect to my wifi, so I just install an update and the problem was resolved... but. After that I root and return the original state again, and this error was there again... (this happen just after you successfully set up wifi at first use, and before terms and conditions screen).
I deside to root it again from this state - no registered device, no registered user, just rooted (I know is out standard procedure). And rooting works great. I skip the registration (there is a procedure about that) and I had a perfect working rooted not registered nook. I deside to use the app for registration and successfully register it from there, but the issue now is - nook have a perfect wifi connection and working internet, but the nook reader report that there is a connection issue.
SO -
nook support was maybe right to tell me that the nook can't see Internet for some reason
I am right to thing that the Internet itself is perfectly OK
The problem is fixed when an update is applied, but there is no more updates .
The question is - is there anybody with the same problem?
Can I go to some older version like 1.2.0 or 1.1.2, and to repeat the official update procedure after that?
Is there any other ideas?
Thank you
littleclown said:
The device: Nook simple touch glowlight
This error happen when I return original state after rooting.
I know there are some stories about blacklisting, but let me finish.
The first time that happen, I contact nook support, they tell me that the device is not blacklisted, and probably i have wifi issues. But my nook perfectly connect to my wifi, so I just install an update and the problem was resolved... but. After that I root and return the original state again, and this error was there again... (this happen just after you successfully set up wifi at first use, and before terms and conditions screen).
I deside to root it again from this state - no registered device, no registered user, just rooted (I know is out standard procedure). And rooting works great. I skip the registration (there is a procedure about that) and I had a perfect working rooted not registered nook. I deside to use the app for registration and successfully register it from there, but the issue now is - nook have a perfect wifi connection and working internet, but the nook reader report that there is a connection issue.
SO -
nook support was maybe right to tell me that the nook can't see Internet for some reason
I am right to thing that the Internet itself is perfectly OK
The problem is fixed when an update is applied, but there is no more updates .
The question is - is there anybody with the same problem?
Can I go to some older version like 1.2.0 or 1.1.2, and to repeat the official update procedure after that?
Is there any other ideas?
Thank you
Click to expand...
Click to collapse
How did you perform the restore procedure?
- use Method #2 to format all the partitions (other procedures only format /data/ partition)
http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
- set your home wifi to WEP
- try again
- post results
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Seriously???
pastorbob62 said:
Okay, I was able to get into pink screen by erasing the dload folder, removing the battery, and connecting to my PC via the USB cable. I then copied CWM 5.0.2.7 over and then flashed Stallion-51-ICS onto the phone. I now have a very fast, rooted and customized U8800-51, BUT no mobile service. IMEI and APN info is correct but it won't access the mobile service that our other phones access, SIM is the same one that I use in my current phone.
I know you are supposed to back up the IMEI partition and APN before flashing a custom ROM, but since my phone got broke trying to restore a full backup done with CWM I was caught off guard.
Still looking for any suggestions you all might have.
Click to expand...
Click to collapse
Not to be negative or anything but I think this is the least responsive forum on this site. I have spent hours searching for possible solutions to various problems I've encountered over the past several months, asked several questions and received little if any help. I was only able to get back from a bricked phone to where I am now by using information found on other websites. Pretty sad if you ask me.
In contrast, whenever I have asked a question on my tablet's forum I've received fast workable solutions/answers to my problems/queries. The threads are informative, well organized and contain answers to any situation I have encountered.
Granted, my current problem with my phone is my own fault for trying to customize it. And I suspect part of the problem is due to the age of this phone thus most of the "experts" have moved on to other ventures. It is also hindered by the lack of information available from Huawei and the service providers.
All of that said, if anybody has any suggestions for how I can repair the ESF partition or whatever is causing this lack of mobile service issue I would be extremely grateful. It isn't the end of the world since i have a new phone (Consumer Cellular) that I am currently using but it would be great to get this one working since it's much faster and more streamlined than my stock Consumer Cellular version.
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
Thank you very much for your reply. It seems that you have found the answer to my problem. But unfortunately, I don't have a copy of the original stock ROM. My phone is the -51 version and any links I have found to the stock ROM are broken. There is a version I found but it is for Venezuela and I don't think it will work. I am leery to try it and totally brick my phone. My backup is apparently corrupted. I backed up my new working phone with Disk Image and attempted to restore it to the broken phone but all that did was cause it to come up to the ATT logo screen for a few seconds and then shut down. It wouldn't do anymore than that. So I restored the Stallion 3.5 image I made and am back to a great fast tablet with no phone service. I also tried backing up my IMEI on the working phone and restoring it to the broken phone but that had no effect.
It is my understanding that the -Pro version of the ROM will work, but I don't have the stock image of that either. I suspect it work might since I was able to use the -Pro version of GB on it. All of my internet searches have only turned up custom ROMs and other desperate people looking for fixes for similar problems or worse. I agree 100% with your assessment of Huawei's lack of meaningful support. It really is a shame, because these phones aren't half bad when they have been customized and OC'ed a little.
I have just about given up on it and resigned myself to using it as an MP3 player for my car system. I have learned my lesson and am leaving the working phone stock. It is rooted and I have cleaned off all of the bloatware, and set it up so most apps run from my SD card, so it really isn't half bad. At least it works.
Again, thank you for your reply and advice.
Blefish said:
I have experienced something similar on my regular U8800, and it seemed like there was a baseband & modem partitions conflict. In stock 2.3, there should be some kind of hwefsupdate tool, it may be renamed though. This tool gets run on the first boot after 2.3 and it restarts the phone shortly after. Try to reinstall the stock ROM, see what happens. It can be fixed in strange ways - for example, my original U8800 got a USB failure, so I sent it to the repair. I had 2.3 installed. When I got it back, they tried to write over some old 2.2 firmware, which softbricked the phone. Being clueless, I wrote the 4GB image of some other phone's image on my phone, and got everything working again. Then, when I tried to write back my original IMEI, I got the same issue as you. The only way to get it right was to rewrite the "other phone's imei".
The baseband/modem errors are actually very hard to debug, hence no replies. And since it's a Huawei, these guys have even failed to provide a good update system, as seen from the IMEI getting nulled issues. The mmcblk0p5 stores the OEMInfo of the phone, it contains serial numbers & other information about the phone (like accelerometer position up/down for example). It also has the boot image (the very first splash screen). The data is loaded onto modem processor, which provides an API to let userspace access it.
Click to expand...
Click to collapse
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
ggunzio said:
@Blefish
hi there, can you please give me the exact steps do to so, because im experience the exact same problem.
I've lost the imei in the upgrade process, and them flashed the 4GB image from a user, and then when i try to update to gingerbread, i can't have 3G signal, only 2G.
in the past, i had made a backup of the imei after flashing that .img file, and i think that after update to gingerbread had restored the imei and the 3g was working nice. But this time i cannot acomplish the same, don't remember very well the exact steps that i've made.
I already tried with the B517 and B518, and can't get it to work...
Can you give me some help please?
Thanks in advance
Click to expand...
Click to collapse
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Blefish said:
In my case, I restored the full 4GB from some russian community's provided image (it was named Huawei_U8800_FullFlash.bin), which returned my device to stock 2.2. From there I installed 2.3, and everything still worked. The problem in my case was that I could not restore my own IMEI, it never gave me connection & failed to register to a network. The only solution was to use the "wrong" IMEI that came with the 4GB image.
Huawei has some sort of backup mechanism if they think the "data" is corrupted. I can't tell how it works, but it likes to break things that were working before.
Click to expand...
Click to collapse
i have exactly the same phone than you, because i installed that backup too. After installed it, the IMEI SV is 36, after installing B518 it says it is 18, but before it was 17, and i had 3g signal, but not now.
My question is, wich SV is your phone reporting?
Thank you
I also have a problem like this, but I think it's a bit more severe. My phone got stuck while charging. Couldn't reboot. Was getting stuck on the aurora loading screen(using DZO 5u20). Than reinstalled whole rom. But now I don't any signal and the phone doesn't even see a SIM card. Showing 'baseband unknown' and the IMEI and IMEI SV are also unknown. Not 0's but just unknown. Is this is a similar problem? And can something be done to fix it.
I had some backups on my sd card, untill the sd-card got fried in the phone a couple of months ago.
Hey all! so.. my friend came from U.S and he got me a used Galaxy 4 from AT&T, and the Wifi is just stuck on a green grey situation, its not on or off
i tried any solution online that i could find. i don't know what to do anymore. nothing helping the things that are only helping was changing the router settings to a different encryption mode from WEP and then its worked but when i connected my gs4 to a different wifi connection the problem happened again
the wifi can work days if I'm not switching wifi spots.
my only solution by now was just to change to a whole new custom ROM
the problem is, that i have NO IDEA how to do it due the fact that i have a mac and i couldn't find a Proper noob guide from scratch to do that. please help me! i am a graphic designer and an artist with a MA in fine arts and i would love to help u guys too
Thank you so much!
elirandahan.com
This is what I used to get adb/fastboot on my iMac. I am on MDL build, early version phone.
You will need to find you build number first. Under Settings/About Device to determine how to flash roms on the phone--a screen of that page may help also--
rugmankc said:
This is what I used to get adb/fastboot on my iMac. I am on MDL build, early version phone.
You will need to find you build number first. Under Settings/About Device to determine how to flash roms on the phone--a screen of that page may help also--
Click to expand...
Click to collapse
hey thanks i added a photo but apparently i need 10 posts at least so just add www i58.tinypic.com/v41bue.png
the wifi is working cuz i restart it to manufacture settings again but soon as i will disconnect him and join a different connection he will go grey again
From the PM photo you are on NB1 build--
If you are going to root to flash a custom rom you will need the below two links--
Read Op page of first link, I think it depends on how the phone got to NB1 as which steps you need.
http://forum.xda-developers.com/showthread.php?t=2616221
You will need SafeStrap in below link. So, read up on that.
http://forum.xda-developers.com/showthread.php?t=2448925
These are if you are going to root to flash a rom. You can only flash Touch Wiz roms and no custom kernels or recovries.
If you want to get back to stock status you will need to flash the appropriare firmware and use Odin on a PC and Heimdall on Mac. Will have to research that.
What carrier are you on and where you are at?
Was the phone ever rooted--
I never returned to stock or used SafeStrap, so someone with hands on experience will have to help on that.
Hiii....I am also having the same problem.My phone was unlocked by a guy and everything was working fine then.From next day the i could not turn on WiFi(It would go grayish for some time and then return to normal).I tried searching for it online and found the following soln
1)Reboot and check(Didn't work)
2)Factory Reset:After doing this it worked for that initial scanning but again was back to normal once wifi was switched off
3)Factory reset and installed root browser(my phone is rooted as i was able to install root explorer) and tried renaming the wpa-supplant config file
.This was worked for me for like 4 days.
After that again the problem is back and its even worse.It is immediately turning off as opposed to delay in previous case.When i tried to follow the same procedure the config files are not present.I could not on wifi even after factory reset even once
As i am a new around here detailed help would be appreciated;
My Device Features:
1)Andriod:4.4.2,SGH I337
2)Baseband:I337UCUFNC1
3)kernel Version:3.4.0-1125940
4)Build No:KOT49H.I337UCUFNC1
Hi all, I apologize for my low level of English. I want to tell that to write this report use the google translator.
I also thank in advance the help that you can give me.
Acontinuacion expose my problem:
I followed the steps in a tutorial, to release my samsung i9505 galaxy s4, exposed one of the most important forums, Htcmania.com my country, Spain.
By exposing my problem in the same forum that supra and receiving no response clarification about my problem, I turn to the more important to try to find a solution forum. I go to XDA-Developers.
I do a copy and paste of the report I wrote on the forum that I quoted earlier as I explained my problem well:
My s4 with Android 4.4.2 was completely "virgin" had installed the rom Stock samsung, was not released, was "Yoigo" any advanced recovery had not installed, and had no permits super user "root".
I wanted to release it (Unlocksim) seeking information HTCMania, and I found the following topic "Free S4 I9505 (Unlocksim) in 4.4.2" I followed all the steps in the tutorial. One of the "requirements" was to be root to do a backup of the EFS before touching anything, and to use the application "Region lock away"
So no, I did root, flashing by odin CF-Auto-Root 4.4.2 package.
Being root installed the advanced recovery "CWM" philz touch. And I found myself at this point I made a backup of the EFS system being completely "virgin" that is, with stock rom samsung and android 4.4.2. I followed the steps in the tutorial that I have made previously to unlocksim. One of the requirements to release the phone was change the modem to modem I9505_DXUAME2_MODEM, so I changed the phone modem and followed the guidelines set by the tutorial,
Region to use the application could lock away briefly display an error is possibly to blame for me as I'm seeing. This error could display for two seconds, but from that moment everything seemed to work well, the phone was released. So I changed the modem again for mine.
At this point I decided to choose to install a cooked rom based on stock, namely Omega rom v38.1 for s4 I9505.
And at this point is when my headaches begin to appear. I have experienced problems with the release ... see, the issue is that when the network coverage data is in H + the phone works perfectly, but only if H is not able to load websites etc. This has led me to the edge as I can not be aware every moment of the type of data coverage.
My questions are:
1. Is there a way to stop the phone as he was before unlocksim, ie leave it as it was originally being from Yoigo? (Remember to keep a copy of SAI realized when the system was completely untouched.)
2. How I can solve this problem with the network coverage data?
3. What do you advise me to do?
Please help. Greetings.
you might want to try searching sammobile to see there is a ROM you can download and flash that's for your country and ideally for your phone provider as well. I've run into issues like this on a couple of occasions. One was indeed that the country's ROM I flashed uses differant frequencies and I had the same mobile data connectivity issues you're talking about. This is rare for the international Samsung phones but it does happen. The other scenario I ran into was after flashing a port of the Google Play Edition onto tit, which gave it extended network options, and everything worked quite well but when I restored to stock from a backup on my sdcard I had connectivity issues, once again just like you're describing. In this scenario flashing a fresh stock ROM entirely solved the problem.
Note that in the second scenario I didn't redo the data partition. Presumably flashing the system fixed it or reflashing the firmware partition reinitialized things the way they are meant to work for me.
search for I9505 (or whatever the model of your phone is) where it says search for your device http://www.sammobile.com/firmwares/
Google around the codes if the results aren't revailing enough for what's stock for you and try reflashing in odin. If it persists then backup your apps, wipe the data partition, possibly backup your internal storage as well if you have a stock recover, and try again. Beyond that I haven't had to deal with further problems than that yet but I saw that no one else had responded...