hello all
áfter downloading and running GB 2.3.5 on my u8800 device
i am no longer able to log through the pink screen to the boot image
actually the device is visible to my computer....further i am unable to root device even by using almost all rooting application
SuperOb=neClick...Zroot..superuser...it is all worthless
more..... the welcome screen keep running without booting to the system unless i format the device each time i turn it off?? is it related to the B258 version??
whats wrong and how i fix such issue?
Once more. Version 528 need a special way to be rooted. Search for: "B528 how to root" in developement section. If you read some threads about root, maybe you' ll find the link there to.
Also in all versions after 518 pink screen is locked, so you need to flash 518' s bootloader which is unlocked. All these infos are in the forum in multiple threads. Also there is a thread which explain how to flash the unlocked bootloader: "take your pink screen back"(or something similar).
Just search and you will find...
Related
[/FONT]
First of all Hello ! Hope your all good and I appreciate your time to help me.
This is where I'm currently stuck on with my HTC Glacier-MyTouch 4g problem.
View attachment 936086
View attachment 936087
I have tried these methods so far: download PD15img.zip on sd card and then update it takes hours and then suddenly screen goes black probally shuts down.
I read that you need to turn s=off first before you can download any roms or something like that but to do that either you have to download visionary which i can't because i cant pass the mytouch screen.
Also, there are other ways but for that you need to do things from your phone such as make sure phone is on usb debugging mode and stuff which i also cant do if i cant pass the mytouch screen.
So considering all that, can anyone please thoroughly tell me how to go about fixing this problem and get it to work. It doesnt matter how its done i just want it to work lol.
Thanks A million for your time.
Well, the version of PD15IMG.zip you are trying is important. There are 2 gingerbread versions. Download both and verify the MD5 sum on them. Try the original GB version first. If that doesn't work, try the newest one. Its possible you have a bad download or you are trying to install the older version over the newer. Following my instructions addresses both.
Report back.
Fastboot
Use adb and fastboot to push the rom.
If it crashes / hangs try a different sd card.
I had an issue with this and I swear it was the SD card.
Open Glacier Wiki, section "Troubleshooting". Read the guide and execute it. If it doesn't work for you - understand that your phone is done and there's nothing you can do.
Next time, try searching instead of opening yet another thread to ask a question that might have been answered zillion times before. That'll make sure you won't get answers like "use adb and fastboot to push the ROM", when you have no access to ADB at all, not having the OS booting, and fastboot won't allow you flashing /system because of the size.
I originally followed this:
http://www.modaco.com/topic/341011-ultimate-guide-to-the-huawei-u8800/
and rooted the phone
Then I followed this:
http://forum.xda-developers.com/showthread.php?t=1420728
and I read this:
http://forum.xda-developers.com/showthread.php?t=1492957
I thought that the phone had 2.3.5 on, and then after a while (After I flashed the new zip file), I realised that it only had 2.3.3 on and it won't get past the Huawei screen ie: it's stuck
I backed up the current ROM, but I've no idea on what to do now that it's bricked. I've tried fixing permissions, connected via USB and using the "adb logcat" command when I got the reply
/sbin/sh: exec: line 1: logcat: not found
And it's just stuck at the boot screen. Just wondering if any one can help?
Re-flash firmware.
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
Re-flash firmware.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
I haven't the foggiest as to why my last post didn't go through. Any way, I did do that and I tried to restore my current ROM as well - remember it hasn't had the 2.3.5 update
On another note, my post also serves as a "hello" post considering that I didn't realise that I had an account here with zero posts until recently. I must have made it a while ago so hello
Hi, I didn't notice it because I use tapatalk.
Sent from my U8800 using Tapatalk 2
That's not a bricked people. A bricked phone is one that does not turn on no matter what, does't react in any shape or form, no screen, no vibration, no sound, no led when plugging usb or charger, no pink mode, no pc access to the phone, no nothing.
Your phone goes to huawei loading screen! How is that a bricked phone? Just reflash The ROM and do triple wipes. Search the forum for that.
flash stock rom. 2.3 or 2.2
not bricked
i can trustly say that it's not bricked, a brick phone means "unusable hardware tools"
the implementation that you explained can not cause a brick operation, you only have to teach your phone to work - that its possible to install the original stock rom.
original stock rom images also contains hubbable hardware working scripts and images.
so you can get your system back and also imei.
fjsferreira said:
That's not a bricked people. A bricked phone is one that does not turn on no matter what, does't react in any shape or form, no screen, no vibration, no sound, no led when plugging usb or charger, no pink mode, no pc access to the phone, no nothing.
Your phone goes to huawei loading screen! How is that a bricked phone? Just reflash The ROM and do triple wipes. Search the forum for that.
Click to expand...
Click to collapse
Thanks for that. I'll go off to search for a stock ROM
EDIT: Which stock ROM do I use?
http://coraldrive.net/users/androidz/583/u8800 stock roms
Once I've got the correct ROM, then I'll probably follow this:
http://forum.xda-developers.com/showthread.php?t=1011527
I'm putting that link in, to help others and in case I can't find it. I'm from the UK if that helps
So today, I loaded the general overseas version stock ROM and formatted the Micro SD card to FAT32 and it loaded with android 2.2 on it (yay)
However, I can't download the official 2.3 ROM because the Huawei site is having problems with it's server, and every file sharing site I've seen has deleted it for "copyright infringement" Why the hell Huawei even requested for it's removal, when it doesn't even work from their own site, I have no idea
So, just wondering if there's any kind people out there that can send us the official 2.3 ROM either by email or a public dropbox link, which can then be deleted?
Thanks
EDIT: I may have found something:
huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDQzNTg=
Just an update to show what I've now done, in case any one else has the same problem. Go here:
huaweidevice.com/worldwide/downloadCenter.do?method=toDownloadFile&flay=softw are&softid=NDQzNTg=
(XDA forums won't allow me to insert external live links just yet)
Download the file from there. Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1011527
Follow step 12 and onwards from here:
http://forum.xda-developers.com/showthread.php?p=22682229#post22682229
I also deleted the dload folder, in case I accidentally revert it to stock ROM. I also had to run SuperOneBoot again because it was unrooted after I flashed the official ROM
To get clockword mod, go here:
http://forum.xda-developers.com/showthread.php?t=1420728
Once you've got clockword mod, a rooted phone etc... and if you follow the guide posted above, then you can also install custom ROM's on to your Huawei device
Thanks to the XDA people for providing these guides
Ok, well the title can be a little misleading. I have a U8800-51 and screwed up by putting the GB update on it that was listed on Huawei's website. Well not Im screwed lol the phone boots into GB fine but and I can make calls but it gets no data at all so I cant install clockwork or anything. it is rooted.
But when I hook it up to the pc in pink screen it doesnt see it, according to the device manager it can find the drivers and neither can i.
What to do?
This is normal, because huawei has lock this function on gb rom.
You can use remount and es file explorer to mount this partiton and made some changes from device. Also there is a thread "get pink screen back" on the forum in which you can flash(or copy via adb if you haven't access on recovery) the previous(518) unlocked bootloader.
Of course, because all these are for regular U8800, is better to try flash a rom suitable for your device. Maybe some of the above don't work for you, or worst lead to other problems.
Heres my story,
So I have had my Atrix since November, and I still would consider myself a noob when it comes to all this crazy unlocking stuff.
Last week I got the genius idea that I wanted to unlock the bootloader and followed a tutorial on doing it. In doing so, I think I missed a step and essentially gave up. Luckily for me, I never bricked the phone or anything. When I booted it back up, my phone began running slowly, lagging into apps and switching screens, so I factory reset it.
Ever since then, I have been getting extremely low RAM, like 200MB used with basic apps open, with only 20MB available. I tried contacting motorola for help, but they are certainly no help.
Just wondering if anyone here can help, as my phone is still way too slow to be bearable.
Thanks in advance
Looks like your Atrix is not AT&T version. Those international version of Atrix will have RAM issue after unlock. The RAM size will reduce from 1G to 350MB after the bootloader unlock process. Try search for RAM fix thread or proceed with the unlock process, install CWM and flash other ROM like CM7. Those ROM had RAM fix built in.
Sent from my MB860 using xda app-developers app
Sounds like you need the so-called "froyo RAM fix". I don't know how will you ever get it on there though, not having an unlocked BL or custom recovery. In fact I don't even know how did your phone even get messed up like that without these. It would be immensely useful if you could remember as much as you can about what you did and what was the result.
First off, "Q's" go in Q&A.
Are you sure you didn't unlock your bootloader? Do you see the word "unlocked" on the Motorola splash screen?
If you are not unlocked, this should be possible (in theory):
Get the ramfix zip, then extract the files and updater.script
Use a root level file explorer to put the files in the correct place and set permissions correctly
Run the script to enable the ramfix
Use updater.script as a guide to tell you where to place the files, what the permissions are, and which script to run.
upndwn4par said:
First off, "Q's" go in Q&A.
Are you sure you didn't unlock your bootloader? Do you see the word "unlocked" on the Motorola splash screen?
If you are not unlocked, this should be possible (in theory):
Get the ramfix zip, then extract the files and updater.script
Use a root level file explorer to put the files in the correct place and set permissions correctly
Run the script to enable the ramfix
Use updater.script as a guide to tell you where to place the files, what the permissions are, and which script to run.
Click to expand...
Click to collapse
It does not appear, no. I attempted to unlock it again today and got to the point where I typed in fastboot oem unlock or whatever, then I got the message << waiting for device >> but nothing further from there. I just unplugged and restarted my phone, and gave up once again.
Can you elaborate on the above? I am getting so frustrated with this low RAM because I can't even open a game or high RAM app without it lagging like crazy.
Trying typing "adb devices" instead and see if it shows your device. Maybe you are without the fastboot driver
Sent from my MB860 using xda app-developers app
first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
http://sbf.droid-developers.org/umts_jordan/list.php
ive tried the first and last one not sure witch one is for my phone
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram to bootloader
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
jimbob60 said:
sorry about pic i cant post them
they are on my fb my only public album
my fackbook url:
/jacob.g.shaffer
first off im not a noob at this kinda stuff ive rooted tablets and other phones before. so ive spent the past week or so every night for hrs searching around for an answer to my problems.
phone info
carrier:Straight Talk
MN: XT555C
AV:2.3.7
Base band vr: PCR
Kernel vr:Apps_2.6.38.6-perf
Build number:1_67D_1014
OK on to the proses i used:
first rooted phone with VROOT
pic 1(the pic with the Foreign letters)
gained root
pic2 (pic with root checker)
easy enough right
then tried 2int every vr of it witch said they installed just fine
but every time i would try to go in into the boot-loader nothing no blue light no auto boot loader screen just nothing.
so i searched for different kinda boot loaders witch lead me to twrp and only like two more
nothing couldn't get any of them to work on account of the fact that they needed a Boot-loader to install them.
then i decided i would try rsd lite
downloaded sbfs
when i hit VOL+ power i get this screen:
pic 3(white screen with blue letters)
and rsd reconised the phone but phone info came up mostly as
N/A and nothing would flash just kept giving me
error:failed flashing process. failed flashing process phone 0000 error sending ram
then when i had the phone try to just boot normaly with rsd open i got this screen:
pic 4(black screen with white letters)
all things aside i have gained root but to no avail can i get a Boot-Loader to work. im just looking for some one to help shed some light on this matter and help me get off of Ginger Bread
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=1743764
It worked for me.
i have now tried that and it was useful as far as the commands in the bat file but still nothing i did worked
i unrooted it the wipe cash and factory restore the Zerg Exploit did not work it would not root it so i used the commands to install bootloader it worked with no errors my led turned green to show success but still no blue light or Boot-loader. even when i use
E:\android\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
$ su
su
# reboot boot-loader
reboot boot-loader
it just reboots normally
any one else have some info?
so i still cant get a bootloader to come up ive been at this for a while and am still stumped i gain root and su but no custom boot loader just the stock one.
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps.
^
so this is just so people can see where im at in the chain of things here. im at the install 2ndinit
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
jimbob60 said:
nother update so i desided i needed to push the files from bootmenu.tar.gz onto my system and see if it changed anything(also did the same for twrp and a few vrs of other bootloaders)
so i went and got http://forum.xda-developers.com/showthread.php?t=1687590
witch worked well and after i used the program to send the files where they need to be and tryed to reboot into bootmenu the phone still just restarted normally.so now the files are where they need to be adn it should let me into the bootloader but no im at a loss i dont understand how sompthing so simple could turn out to be like this. every one else can get it and ive followed like every set of direction i could find on this site over and over agen then i started experimenting with it and still nothing no matter how the files get there still no bootloader all i want is to be able to install JB and get the hell off of GB. and its not like im getting any help from this post i hope a dev can come by here soon and help me shed some light on things. untill then ill keep updating the post
Click to expand...
Click to collapse
I don't think the XT555c has a JB or even a ICS ROM. You can debloat GB and stay on it.
Sent from my Nexus 7 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2392187
http://forum.xda-developers.com/showthread.php?t=1216982
http://forum.xda-developers.com/showthread.php?t=1768702
http://forum.xda-developers.com/showthread.php?t=1032212
ive read thru a few threads other than those also and other people with the same mn and build have done it......
thats from my understanding that they wer able to get a boot-loader to work witch i can not get into a bootloader at all.and RSD wont flash anything to the phone evern tho ive used diffrent vr of rsd and the moto drivers.
so am i to assume that it just cant b done? that i could understand but other people with this phone/67d have done it and ive sent them pms but no reply same with some of the devs here who have helped others get this phone going so i guess im at a loss with this straight talk phone at least with installing a custom boot-loader/ROM.at least the phone works.....just outdated.screw you motorola
just a reply
@jimbob it my feelings that the "USA Moto defy xt555c, Straighttalk" does not have a blue LED built in. There is no evidence of it other than i have never seen one during the last year or so of having the phone (yes i do a lot of bluetooth stuff). Also to shed some light on your situation it is my understanding that 67d firmware has patched an exploit with the older bootloader and now has been upgraded to bl7. if this is your bl ver number then it is slim you will find the answer to your problems here. the only option i can come up with is to get or make fixed sbf for the device and flash/ downgrade. fixing the sbf only lies to the phone and tells it you have a higher ver android than you really do.... go figure motorola would be good at burning bridges! LMAO
thanks for replying. not to sure how to make a fixed sbf and the ones i found would not work because i couldn't get the program to flash anything to the phone. but then agen i never made a custom one